...

Users who join in claim payment approvals are required to have “Approval payments” permission and approval limits configured in Limit Groups. Users who have “Approve payments” permission but are not configured in Limit Groups will not be able to approve payments. See Limit Groups

...

Approver selection process

...

1. Once a payment is saved successfully, system will initialize the random approver selection process. User is selected randomly by system as an approver based on:

   1. User has“Approve payments” permission. (Must have)

   2. User has suitable Approval Limit on a specific product which is got from Claim Settings - Limit group. (Must have)

   3. User is in the same organisation of the user who creates the payment. (Must have)

   4. If more than 1 user satisfy all the above criteria, select user who has the least number of current assigned payments pending for approval.

   5. If more than 1 user satisfy all the above criteria, select user who has the nearest higher approval limit, compared to payment transaction amount.

   6. If more than 1 user satisfy all the above criteria, select randomly.

   7. Notes: system won’t evaluate users in parent organisation if cannot find any user in the same organisation of the user who creates the payment (point 1.d).

2. If no qualified approvers selected, "To be approved by" in Pending Payments list shows "N/A" and show button Reassign for the transaction (Reassign action will initialize the random approver selection process in point 1 above).

3. If a user has roles that have been added to several limit groups, user will get the highest limit.

4. If the approval assignment is done successfully, toast message will pop up “Payment <ref. no.> has been assigned to <user name> for approval.”

5. If the approval assignment is failed, toast message will popup “Cannot find the approver for Payment <ref. no.>.”

...