ReferralKnow a company that should run on Procura? Refer it and get rewarded for every signed client.Refer a company, get rewardedDiscover the programmeDiscover
Resources / Approvals · Procura team · 17 November 2026 · 8 min read
Approvals

Purchase approval workflow: how to design one, with an approval matrix example

A purchase approval workflow decides who must say yes before the company spends money, in what order, and how fast. Designed well, it is invisible on routine purchases and firm on risky ones. Designed badly, it either rubber-stamps everything or makes people wait a week for a box of printer paper, and they learn to go around it. This guide gives you the design principles, a sample approval matrix, worked routing examples and the controls auditors look for.

01Five design principles

  1. The fewest approvers that cover the risk. Every extra step adds waiting time and dilutes responsibility. Two approvers who read the request beat four who click through it.
  2. Approve against a budget. The budget owner is the natural first approver, and the system should show them what is left before they decide.
  3. Thresholds, not titles. Route by amount, category and risk. A $300 software subscription and a $300 office chair do not carry the same risk.
  4. Nobody approves their own spending. A requester cannot approve their own request, even if their authority level would allow it.
  5. Approve once, at the right moment. Approve the requisition, before commitment. Approving the invoice again after a matched PO adds delay without adding control.

02A sample approval matrix

An approval matrix, also called a delegation of authority (DoA) matrix, lists who may approve what. The amounts below are illustrative; set yours according to your size and risk appetite, and have them approved by your leadership or board.

Amount (per request, before tax)Within budgetOver budget or unbudgeted
Up to $1,000 / €1,000 / £800Budget ownerBudget owner and finance
$1,000 to $10,000 / €1,000 to €10,000 / £800 to £8,000Budget owner, then department headDepartment head and finance
$10,000 to $50,000 / €10,000 to €50,000 / £8,000 to £40,000Department head, then financeFinance and CFO
Above $50,000 / €50,000 / £40,000CFO, then CEOCFO, CEO, and board if your bylaws require it

Add category rules on top of the amount bands:

  • Software and data: IT or security review for any tool that stores company or personal data, whatever the amount.
  • Contracts longer than 12 months: legal review, and the amount is the total contract value, not the monthly fee.
  • Capital expenditure: finance review for capitalisation, whatever the band.
  • New suppliers: supplier onboarding (identity, tax ID, bank details) completed before the first PO.

03Worked routing examples

Example 1: software renewal, $7,800 a year. The requester is in the sales team; the annual value falls in the $1,000 to $10,000 band and the line is budgeted. Routing: sales budget owner, then head of sales, plus an IT review because the tool holds customer data. The two approvals and the review run in parallel, so the request is not waiting on one person at a time.

Example 2: production equipment, €45,000. Budgeted capital expenditure. Routing: head of operations, then finance (who confirms the capitalisation and the budget), and three quotes are required before the PO. Expected time to decision: under three working days if approvers respond within their deadline.

Example 3: a two-year consulting contract at £3,000 a month. The monthly fee looks small, but the commitment is £72,000. It is approved in the top band: CFO, then CEO, plus legal review. Routing on the monthly figure would have sent a £72,000 commitment to a single budget owner.

04Keeping it fast

  • Set a deadline per step, for example one working day, with an automatic reminder and an escalation to the approver's manager when it is missed.
  • Let people approve from email or mobile, with the document in front of them. An approval that needs a VPN and a desktop waits until Monday.
  • Delegate during absences. When an approver is away, their authority passes to a named delegate for a fixed period, recorded in the audit trail. A delegate never approves their own request.
  • Measure approval cycle time per step and per approver. The bottleneck is almost always one or two people, and the data makes that conversation easier. See our guide to procure-to-pay KPIs.

05Stopping split purchases

When a threshold is inconvenient, someone will eventually split one purchase into several smaller ones to stay under it: three requests of $9,500 instead of one of $28,500. Look for:

  • the same requester and the same supplier, several requests within a short window (for example 7 days);
  • amounts clustered just below a threshold;
  • consecutive invoice numbers from the same supplier on separate POs.

When the pattern appears, add the amounts together and route the total as one request. If it keeps happening in one team, the threshold may genuinely be too low for their work; review it rather than only policing it.

06Changes after approval

An approval covers the request as approved. If the purchase order later increases, it needs a new approval above a small tolerance, for example more than 10% or more than $1,000 / €1,000 / £800, whichever comes first. The same applies when the supplier changes, or when the delivery moves into a different budget year. Without this rule, a $9,000 approval can quietly become a $14,000 order.

07What auditors look for

  • A written approval matrix, approved by leadership and reviewed at least once a year.
  • Evidence that the system enforces it, not just that it exists on paper.
  • No self-approvals, including through delegation.
  • A complete trail: who approved, when, which version of the document, and any comments.
  • Exceptions (emergency purchases, purchases without a PO) listed and reviewed.

If the requisition record holds all of this, the audit request becomes a report rather than a week of searching through emails.

08Templates and tools

To run the workflow in a spreadsheet first, start with the free Purchase Request Tracker, which records each request with its approved, rejected or pending status, and the free Budget vs Actual Tracker to see what each budget owner has left. When routing, reminders and delegation become a part-time job, see how approval workflows work in Procura. For the documents being approved, read purchase requisition vs purchase order.

09Approval workflow checklist

  • A written approval matrix by amount, budget status and category.
  • Thresholds based on total commitment, not monthly amounts.
  • The budget owner sees remaining budget before approving.
  • No one can approve their own request, including as a delegate.
  • A deadline, reminder and escalation for every approval step.
  • Delegation during absences, time-limited and logged.
  • Split purchases detected and routed as one request.
  • Re-approval when a PO increases beyond a set tolerance.
Free Excel templates

Start with a spreadsheet.

Excel template

Purchase Request Tracker

Free purchase request Excel template for startups: every spend requested, approved and traced before commitment, with approved, rejected and pending totals.

Download free →
Excel template

Budget vs Actual Tracker

Free Excel budget vs actual tracker by department: annual budget, budget to date, committed, month-by-month actuals, available, percentage used and an automatic alert at 80% of budget.

Download free →
FAQ

Frequently asked questions.

It is the sequence of approvals a purchase request must receive before the company commits to a supplier. It is usually driven by an approval matrix that sets who can approve which amounts and categories.
A delegation of authority is the policy that grants spending authority to roles, usually approved by leadership or the board. The approval matrix is the table that puts that policy into practice: role, amount band, category and the resulting approvers.
As few as the risk requires. Many companies use one approver for small budgeted purchases and two or three for large or unbudgeted ones. Adding levels beyond that slows purchases without making each approval more careful.
Not when the invoice matches an approved purchase order and the goods receipt within tolerance. The approval happened at commitment; a second approval adds delay. Invoices without a PO, or with a variance, do need an approval.

See Procura on your real data.

From request to payment, your purchasing cycle in a 30-minute demo.