Map the category once
Assign an approval set on the Claim Type. Future submissions use that mapping without updating each employee record.
New in eClaim · Claim Approval by Claim Type
The right expense goes to the right approver.
Send mileage to the Fleet Manager and travel to Finance. Give the same claim type a different approval set for Directors, Executives or other employee types, with one central configuration.
- Map each claim type to its approval set
- Add exceptions for selected employee types
- Show mapped approvers before submission
A practical example
One claim type. Different approval paths.
Set Air Ticket to Finance for all employee types, then add a Director exception for Board Approval. Everyone else follows Finance unless their own custom approval set takes priority.
Mileage · any employee typeFleet Manager
Specialist review for vehicle expenses
Air Ticket · DirectorBoard Approval
Employee-type exception
Air Ticket · ExecutiveFinance
Main approval set for this claim type
Add employee-type exceptions
Use a different set for selected employee types, such as Board Approval for a Director’s Air Ticket. Types left on “Same as above” follow the main claim-type set.
See approvers immediately
The Approval Table on the claim form switches to the mapped approvers as soon as the employee selects a claim type, before submission.
Keep one approval chain per claim
After the first claim line is selected, only claim types with the same approvers are offered. Claim types with different approval chains must be submitted separately. Web and mobile follow the same rule.
Preserve pending claims
Mapping changes apply from the next claim. Claims that are already pending keep the approvers they were submitted with.
Keep routing visible and traceable
The Claim Type list shows mappings and employee-type exceptions. Changes are recorded in the Audit Log, and an approval set cannot be deleted while a claim type still routes to it.
When more than one rule applies
A clear order for every approval.
The system uses the first applicable rule in this order. Existing personal exceptions retain priority.
- 1
Employee’s own custom approval set
A personal exception takes priority over all claim-type mappings.
- 2
Claim type × employee type
Use the exception configured for this employee type.
- 3
Claim type · all employee types
Use the main approval set assigned to the claim type.
- 4
Employee’s default approval set
Use the existing default when no higher-priority mapping applies.
Get started in three steps
Configure once. Apply it to the next claim.
Enable routing for your company, then map claim types to existing approval sets.
Each feature is switched on separately per company. Ask our team if you need help matching the settings to your policy.
Ask about your setup- 1
Enable claim-type routing
Go to Company Info › HRM › Claim and set “Claim Approval By Claim Type” to Yes.
- 2
Choose a set and add exceptions
Open e-Claim › Claim Type › Edit › Approval Routing and select an Approval Set. If needed, open “Different Approval Set by Employee Type” and configure the exceptions.
- 3
Confirm the approval table
Apply a claim and select the claim type. Check that the Approval Table shows the intended approvers before submitting, including any employee-specific priority.
Common questions
The details that matter to your policy.
What happens to unmapped claim types?
They continue to use the employee’s default approval set, unless the employee has a custom approval set. You can map only the categories that need a different route.
Can Mileage and Travel appear in the same claim?
Yes, if they resolve to the same approvers for that employee. If the approval chains differ, submit them as separate claims. The form filters the available claim types after the first line is chosen.
Will this override an employee’s custom approval set?
No. The employee’s own custom set has the highest priority, ahead of employee-type exceptions, the main claim-type set and the employee’s default set.
Do we need to change existing pending claims?
No. Pending claims keep the approvers assigned when they were submitted. Updated mappings apply from the next claim.
Does the mobile app use the same routing?
Yes. The mobile app uses the same routing priorities and one-approval-chain rule. Companies that leave the feature disabled retain their existing behaviour.
Put your expense policy into practice.
Show us your budget and approval requirements. We’ll walk you through the eClaim setup.