Purchase order approval limits: where to set them in a small business
In short
Small businesses need two purchase order limits, a per-order limit that caps total exposure and a per-line limit that catches big items hidden in routine orders. Set both conservatively, then revisit them when approvals dry up or a spending problem slips through.
Most small businesses set one purchase order approval limit. They need two: a per-order limit that controls total exposure, and a per-line limit that catches high-value commitments inside orders that otherwise look routine.
Set your per-order approval limit at the lowest spend level where an unchecked mistake would noticeably affect your monthly cash position. The aim is a threshold low enough to catch purchases that could cause real damage, high enough that you are not signing off stationery orders. The person who should approve above that line is whoever owns the cash: in a business of 5 to 30 people, that is usually the owner or a senior operations manager. But one number is not enough. Most small businesses set a per-order limit and stop. The number they are missing is a per-line limit, and the two protect against different problems.
What a per-line limit does that a per-order limit cannot
A purchase order is often a document with multiple line items. A single PO for £1,800 might carry twelve lines - some at £20, some at £400. If your approval threshold is £1,000, that PO clears it and triggers a review of the full order. But if your threshold is £2,000 and the same commitment is split across two POs of £900 each - perhaps placed on different days or through different team members - neither one gets reviewed, even though the combined exposure is identical.
A per-line limit solves a different problem. It catches the single high-value item buried inside a larger, otherwise routine order. If your business regularly purchases materials and one line of a £600 PO is a £450 piece of equipment that has never been ordered before, a £400 per-line threshold flags that line for approval while letting the rest of the order proceed. Without a per-line limit, a routine-looking purchase order can hide a significant individual commitment.
The two limits work together. The per-order limit controls total exposure on any single supplier transaction. The per-line limit controls individual item risk within that transaction. A business that sets only one is leaving the other unchecked.
Per-order vs per-line
The per-order limit asks "how much am I spending with this supplier today?" The per-line limit asks "is any single item on this order worth a pause?" Both questions matter; they just catch different things.
How to calculate both numbers
The per-order threshold starts with a cash flow impact test: how much would a wrong purchase need to cost before it genuinely affected your ability to meet other payments that month? For a business spending £15,000 a month with suppliers, a £1,500 error is inconvenient. A £5,000 error is a real problem. The threshold should sit below the point of real damage - which for that business might mean somewhere between £1,000 and £2,000.
The per-line threshold is simpler to work out. Pull your last three months of purchase orders and find the line-item value at which you would want a second opinion before committing. In most businesses, that is the value at which you have no established supplier relationship, no price history, and no straightforward way to return the item if it turns out to be wrong. That value varies by sector: in promotional merchandise, where individual product lines carry lower unit values, a line threshold of £100 to £150 may be appropriate.
Set both thresholds conservatively at first. A threshold that generates more approvals than expected is straightforward to raise. One set too high that allowed a spending problem to develop unnoticed is harder to fix after the fact.
Start lower and adjust
After 60 days, review how many approvals were genuinely contested and how many cleared on the nod without comment. The ones that cleared without comment are below the threshold you actually need - raise it to that level.
Who approves, and when approval becomes theater
For a business with 5 to 20 staff, the approval matrix is usually two levels: self-approve below both thresholds, and route to a senior person when either is crossed. Adding a third level - owner sign-off for orders above a higher value, say three or four times the base threshold - makes sense when a single wrong purchase at that level would represent a meaningful portion of available working capital.
The risk is setting the threshold too low. An owner who approves every purchase over £50 is not running an approval process - they are running a permission process. Every purchase becomes a request, and requests slow operations down. The approval becomes theater: it happens, but it does not add judgment, because the amounts involved are too small to warrant genuine scrutiny. The GEP procurement guide for 2026 makes this point directly: small, routine purchases that comply with existing policy should move without climbing the full approval ladder. The value of a threshold is not that it captures everything - it is that it captures the purchases where a pause would actually change the outcome.
The UK government's payment practices reporting framework defines a large business as one with at least two of the following: £54 million in turnover, £27 million on the balance sheet, or 250 employees. Businesses below that scale operate under greater cash pressure per pound committed. A wrongly placed order that costs a large business £3,000 is a rounding error. At a business turning over £600,000 a year, the same amount is roughly two weeks of supplier spend. The approval threshold exists to reflect that difference in exposure, not to mirror what a larger organization does.
When to revisit your thresholds
An approval threshold is not a permanent setting. The right numbers for a business with six staff and £400,000 in annual revenue are not the right numbers for the same business three years later with fifteen staff and £1.2 million in revenue. Two signals should prompt a review.
The first is when the number of approvals reaching the threshold is consistently low. If weeks pass without a purchase being flagged, either spending has genuinely reduced or the threshold has drifted above the level where it does useful work.
The second is after any month where a purchasing problem - a wrong order, an unexpected invoice, a supplier dispute over quantity or price - went unnoticed until it reached accounts payable. That is the threshold telling you it was set too high.
Zigaflow's purchase orders feature supports approval routing linked to spend levels, so the workflow matches the policy once the thresholds are agreed. The mechanics of an approval threshold as a control mechanism, and the distinction between a purchase order and a purchase requisition as the two points in the process where limits can be applied, are both worth reviewing when building a formal spending policy for the first time.
Two thresholds are harder to explain to a team than one, but they protect against different failures. Get the per-order limit right and you control total exposure on any single transaction. Get the per-line limit right and you catch individual commitments inside orders that otherwise look routine. Neither number needs to be perfect on day one. It needs to be set, communicated clearly, and revisited when the business tells you through a spending problem that it has stopped working.
Sources
- Check when large businesses pay their suppliersGOV.UK · accessed 2026-09-11
- Ultimate Guide to Purchase Order Approval Process for 2026GEP · accessed 2026-09-11
- Purchase Order Approval Process for Small BusinessesinFlow Inventory · accessed 2026-09-11