Why do approvals break when people change roles?
Approvals break when they are tied to a named person instead of a position. If the purchase approval rule says "send to Ahmed", it stops working the day Ahmed moves to another branch, goes on leave or leaves the company. Documents wait in an inbox nobody checks, suppliers wait for payment and the team starts approving by email to keep things moving.
A role-based design solves this at the root. The rule says "send to the Procurement Manager", and the system looks up who holds that role today. When a new person takes over, you change one assignment and every rule that uses the role picks it up immediately.
What is a role-based, multi-level approval chain?
A role-based, multi-level approval chain is a sequence of approval steps where each step is assigned to a role and only applies when certain conditions are met, such as the amount, department or branch. A small purchase might need one approval, while a large one passes through two or three levels.
The same idea works across the documents that usually need a second pair of eyes:
- Purchase requests and purchase orders. Confirm the need, the budget and the supplier before money is committed.
- Expense claims. Check receipts and policy before reimbursement.
- Sales invoices and credit notes. Review pricing, discounts and credits before they reach the customer.
- Supplier bills and payments. Confirm that goods were received and the amount matches the order before paying.
- Delivery notes and stock transfers. Confirm that stock leaving a warehouse is authorised.
How should you set approval thresholds by amount?
Set thresholds so that routine, low-value items move quickly and only larger or unusual items reach senior people. A practical way is to group your recent transactions by value and choose limits that send most documents through one level, with a smaller share needing extra review.
A few guidelines help:
- Keep the number of levels small. Two or three levels are enough for most SMEs. More levels slow things down without adding much control.
- Use separate limits per document type. A AED 5,000 expense claim and a AED 5,000 purchase order carry different risk.
- Add conditions beyond amount where useful. New suppliers, discounts above a set percentage, or spend outside the budget can trigger an extra step regardless of value.
- Review limits once a year. As the business grows, limits that were right last year may send too much to the top.
How do you design an approval matrix?
An approval matrix is a single table that shows, for each document type and amount band, which roles must approve and in what order. It becomes the reference for your team, your auditors and the system configuration.
Here is a sample matrix for a growing trading company. The amounts are only an illustration; set your own based on your volumes and risk.
| Document | Amount (AED, excl. VAT) | Level 1 | Level 2 | Level 3 |
|---|---|---|---|---|
| Purchase order | Up to 10,000 | Department Head | ||
| Purchase order | 10,001 to 50,000 | Department Head | Finance Manager | |
| Purchase order | Above 50,000 | Department Head | Finance Manager | General Manager |
| Expense claim | Up to 2,000 | Line Manager | ||
| Expense claim | Above 2,000 | Line Manager | Finance Manager | |
| Sales credit note | Any amount | Sales Manager | Finance Manager | |
| Supplier payment | Up to 25,000 | Finance Manager | ||
| Supplier payment | Above 25,000 | Finance Manager | General Manager | |
| Stock transfer or delivery | Any amount | Warehouse Supervisor |
To build your own matrix:
- List the documents that commit money, change what customers owe, or move stock.
- Name the roles, not the people, who are best placed to judge each one.
- Set amount bands and decide how many levels each band needs.
- Separate duties. The person who raises a document should not be the one who approves it, and the person who approves a payment should ideally not be the one who records it.
- Write down exceptions, such as urgent payments, and who may approve them.
- Share the matrix with the team and configure it in your system so the rules and the document match.
How should delegation work during leave?
Delegation should let an approver hand their authority to a named backup for a fixed period, with the system switching it on and off automatically. The approver sets the start and end dates, and documents route to the delegate during that window.
Good delegation follows a few simple rules:
- Delegate to a role at the same level or above wherever possible, so limits stay sensible.
- Set an end date so authority returns automatically after leave.
- Keep the original approver informed. Accountability stays with the person who delegated, so they should be able to see what was approved on their behalf.
- Escalate if nobody acts. If a document waits longer than an agreed time, route it to the next level so work keeps moving.
Why does an audit trail matter for approvals?
An audit trail matters because it shows who approved what, when and at which amount, without anyone having to search through emails. Each approval, rejection, comment and delegation is stored against the document.
This helps in several ways. Auditors can test controls quickly. Managers can see where documents wait longest and adjust limits. And when a question comes up months later, the answer sits on the document itself. It also supports your VAT and corporate tax record keeping, as approvals are kept with the invoices and bills they relate to.
Key takeaways
- Link approvals to roles, not people, so staff changes need only one update.
- Use two or three levels with amount thresholds per document type.
- Keep the approval matrix in one table that your team and system both follow.
- Set delegation with start and end dates, and escalate items that wait too long.
- Let the system keep the audit trail on each document.
How Omegamatrix can help
NeatAccounts offers multi-level approvals as an add-on module, switched on when you need it, for purchases, invoices, deliveries and expenses, set by role and amount, so approvals keep working when people change jobs, with a full record of who approved what. If your approvals span several systems, our workflow automation services can design and set up the process with you.
Frequently asked questions
What is a role-based approval workflow?
A role-based approval workflow routes each document to a position, such as Finance Manager, rather than to a named person. The system checks who currently holds the role, so approvals keep working when staff join, leave or move.
How many approval levels does an SME need?
Most SMEs need two or three approval levels at most. Routine, low-value documents usually need a single approval, while larger amounts or sensitive items such as credit notes add a finance or management review.
What is an approval matrix?
An approval matrix is a table that lists each document type, the amount bands and the roles that must approve at each level. The approval matrix serves as the reference for staff, auditors and the system configuration.
How should approvals be handled when a manager is on leave?
Approvals during a manager's leave are best handled through time-bound delegation to a named backup. The delegation should have start and end dates, the original manager should remain able to see decisions made on their behalf, and overdue items should escalate to the next level.
Why is segregation of duties important in approvals?
Segregation of duties is important because it separates raising, approving and recording a transaction between different people. That separation reduces errors and gives each transaction an independent check.
How often should an approval matrix be reviewed?
An approval matrix should be reviewed at least once a year and whenever the business restructures, opens a branch or changes its budget process. Regular reviews keep amount limits in line with current volumes, so senior managers only see the items that need them.
Sources
- Princeton University Office of Finance and Treasury, Departmental financial controls (segregation of duties and delegation of approvals)