...
Company Settings:
Includes Business Registration Numbers (BRNs), company codes, and invoice upload configurations: Used for associating claims with the correct legal entity, ensuring compliance with regulatory and tax requirements.
Relevance to Claims: Ensures claims are tied to the correct legal entity, facilitating proper financial tracking and audit compliance.
Company Codes: Ensure claims are routed and processed under the appropriate company within the e-Claim module.
Invoice Upload Configurations: Allow automated linking of invoice-related claims, improving efficiency in processing.
Entity-Specific Permissions: Define which employees or approvers have access to claims submitted under a specific company entity.
Branch Information:
Each branch is listed under its parent company with specific details such as branch code, address, and contact information.Branch Codes: Used to link claims to specific branches, ensuring that expenses are accurately attributed to the correct location.
Approval Hierarchy: Approvals can be set up at the branch level, allowing claims to be reviewed and authorized by managers responsible for those branches.
Claim Filtering: Reports and claim listings can be filtered by branches for granular analysis and accountability.
Branch-Based Permissions: Users may only have access to submit or approve claims for branches they are associated with.
Approval is based on:
Both:
Branch-Level Approval: Typically used when branch-specific managers or teams are responsible for approving claims.
Company-Level Approval: Used when claims require review by higher-level management or finance teams overseeing multiple branches.
Hierarchy: Many workflows allow for a combination of both, starting with branch-level approval and escalating to company-level approvers for final authorization
Relevance to Claims:
Claims can be processed and tracked based on branch-specific data.
Approval workflows can be configured at the branch level.
Permissions and Access
Permissions for claim submissions can be linked to specific branches or companiesare often tied to branches to ensure that only authorized personnel can submit, approve, or view claims related to a specific branch.
Approvers for claims are often designated based on branch-level hierarchies.
Example: A branch manager may be configured as an approver for all claims within their branch, while employees in that branch are restricted to submitting claims only.
Reporting and Reimbursement
Branch-level reports provide detailed insights into claims submitted, approved, or reimbursed.
Reports can be filtered by branch to focus on specific operational units.
Reimbursement Process:
Branch-Level Reimbursements: Claims are
often processed and reimbursed at the branch level to ensure alignment with local operations.
Company-Level Consolidation: In some cases, claims from all branches are consolidated at the company level for reimbursement.
Bank Details Integration: Employee payment configurations (set up in the Employee Maintenance Applet) ensure funds are transferred to the correct account.
Finance Department Role: Verifies claim data and initiates reimbursements through pre-configured payment workflows linked to the Organization Applet.
This is how the Organization Applet interacts with the Claim Applet and supports the overall claim submission, approval, and reimbursement process
Example Use Cases
Claim Submission
...
|
|---|
TODO LIST:
...
need to find out what are the settings of a company in the organization applet that are being used in the claim applet?
...