Purchase Approval Limits by Amount and Department: How to Set Them Up

Done well, it speeds up small purchases and puts senior attention where the money is. This guide covers what a matrix contains, an example by amount and department, how to set the limits, the rules that stop people getting round them, and a worked example.

What is a purchase approval matrix?

A table that answers one question for every purchase request: who has to say yes before we commit the company's money? It is sometimes called a delegation of authority for purchasing.

A practical matrix has five parts:

• Amount bands. Value ranges, such as up to AED 5,000 or AED 25,001 to 100,000. Decide once whether they include VAT; most companies use the amount before VAT.
• Department or cost centre. Who is spending, so the right manager approves.
• Purchase type. Stock for resale, operating expenses and capital items often follow different paths.
• Budget status. A budgeted purchase may need fewer approvals than an unbudgeted one.
• Approving roles. Roles, such as finance manager, rather than names, so the matrix survives staff changes, plus a named deputy for each role during absence.

Approvals are usually cumulative: a purchase in a higher band needs the lower approvers as well as the higher one, so the department manager always sees what their team buys.

What does an approval matrix look like by amount and department?

Here is a starting point for a mid-sized Gulf distributor. Amounts are before VAT. Each cell names who approves; "plus" means that approver signs in addition to those in the band above.

Stock purchases for resale often get a separate, higher set of limits for the purchasing manager, because they are frequent, budgeted and checked against reorder levels. Unbudgeted purchases move up one band.

The numbers matter less than the shape: few approvals for the many small purchases, more for the few large ones.

How do you set the approval limits?

From your own purchase history, not from a template. Six steps:

1. Export last year's purchase orders. Amount, department, supplier and type for each one.
2. Look at the distribution. In most companies, a large majority of orders are small, and a small number of orders make up most of the spend.
3. Set the bands so senior approvers see the spend, not the volume. A good target is for the general manager to approve under 10% of orders but well over half of the spend.
4. Assign roles and deputies. One approving role per band and department, and a deputy for each.
5. Link approvals to budgets. Check each request against the remaining budget for its cost centre, and move unbudgeted requests up a band.
6. Write it down and set it up in the system. A one-page policy, approved by management, and the same rules configured in the ERP.

Review the matrix once a year, and whenever approvers complain of too many small requests or auditors find large purchases with too few approvals.

Which rules stop people getting round the approval limits?

A matrix only works if it cannot be sidestepped. These rules close the usual gaps:

• No split orders. One need is one request. The system should flag several orders to the same supplier within a few days that together cross a band.
• Approve the whole commitment. For contracts and recurring services, approve the annual or total contract value, not the monthly invoice.
• Nobody approves their own request. If the requester is the approver for that band, it goes to the next level.
• Approve before ordering. A purchase order is issued only after approval; an invoice that arrives without an approved order is held.
• Changes go back for approval. An increase above a small tolerance, such as 5% or AED 1,000, sends the order back through the matrix.
• Emergencies are approved after the fact, quickly. Allow urgent purchases by phone, but record them and get formal approval within two working days.
• Payment matches the order. Finance pays only when the order, the goods receipt and the supplier invoice agree.

The first and last rules are the ones auditors test most often.

What difference does a matrix make? A worked example

A food distributor in Sharjah issued about 1,800 purchase orders a year, and its general manager approved every one above AED 1,000. Requests waited on average three days, and the general manager spent hours a week on cleaning supplies and stationery. This example is a composite, with details changed.

The finance manager exported a year of orders and found that most were small, while a few large stock and equipment orders made up most of the spend. The company adopted a matrix like the one above. The effect:

In the second month, the system flagged two orders of AED 24,000 each to the same packaging supplier on the same day. Together they crossed the AED 25,000 band, so they went to the finance manager, who negotiated a single order at a better price.

The general manager now approves about one order in sixteen, but still sees the purchases that decide the year's costs.

What does HYP see when companies set up approval limits?

Two patterns. Some companies start with too many levels, so a request for printer paper needs three signatures and staff find ways round the system. Others have a matrix on paper that the system does not enforce, so purchase orders go out first and approvals are collected later, if at all.

The matrices that work are simple enough to fit on one page and are built into the ordering screen. The requester sees who must approve before submitting, approvers get the request on their phone, and the order cannot be printed or emailed to the supplier until the last approval is in.

Approved orders are also cash you have committed. Feeding them into a 13-week cash flow forecast shows when that cash will leave. See how HYP routes purchase requests, approvals and orders on our Procurement & Supplier Management page.

Last updated: 27 October 2026