How to Build an Invoice Approval Workflow That People Follow
The short answer
A workable invoice approval workflow routes exceptions to humans and lets everything else through. Set a value threshold, require approval for first invoices from new vendors, any change in vendor bank details, purchase order variances beyond a tolerance and suspected duplicates. Everything below threshold from a known vendor with matching details posts automatically after review. The most common failure is requiring approval on every invoice, which produces a queue nobody clears and approvals that become reflex clicks.
Most small business approval workflows are one of two things: nothing at all, or a rule that says the owner approves everything. The first has no control. The second has the appearance of control, which is worse, because an owner clicking approve on ninety invoices a month is not reading any of them.
The useful design principle is that approval is a scarce resource. Spend it where it changes an outcome.
What approval is actually for
Three distinct things get bundled under the word approval, and separating them makes the design obvious:
| Question | Who can answer it | When it matters |
|---|---|---|
| Is this invoice accurate? | Whoever ordered the goods or service | When quantities or prices might be wrong |
| Should we spend this money? | Whoever holds the budget | Above a value threshold, or off-budget |
| Is this vendor and account legitimate? | Finance, by independent verification | New vendors and changed bank details, always |
Conflating them is why approval queues are slow. The person who can confirm the plumber actually did the work is not the person who should be verifying the bank account, and asking one person to do both means they do neither properly.
Exception rules worth setting
A small business workflow that works in practice:
- 1Value threshold. Anything above a figure you choose routes for approval. Set it where roughly 10 to 20 percent of invoices exceed it, which usually means somewhere between $1,000 and $5,000 depending on your size. If more than a third of invoices are hitting the threshold, it is too low and you have recreated approve-everything.
- 2New vendor. The first invoice from any vendor gets a human look, always, regardless of amount. This is where fake vendor fraud enters.
- 3Changed bank details. Any invoice where payment details differ from that vendor's previous invoice is held and verified by voice, using a phone number you already have on file. Never the number printed on the invoice.
- 4Purchase order variance. If the invoice exceeds the PO by more than a tolerance you set, typically five percent or a fixed dollar amount, route it to whoever raised the PO.
- 5Suspected duplicate. Hold it and show the matching invoice side by side rather than silently discarding it.
- 6Unusual amount for a known vendor. An invoice three times a vendor's typical amount deserves a glance even under threshold.
Sequential or parallel
Sequential routing sends the invoice to approver one, then approver two. Parallel sends it to everyone at once. Sequential is slower but produces a clean chain of authority. Parallel is faster and tends to produce diffusion of responsibility, where each approver assumes another looked properly.
For a small business, sequential with at most two steps is right, and one step is usually enough. Multi-level hierarchies are a mid-market pattern; importing them into a ten-person company creates delay without control.
Designing the thresholds
Pull your last twelve months of invoices and look at the distribution rather than guessing. In a typical small business, invoice value is heavily skewed: a large number of small recurring bills and a small number of large ones.
| Invoice band | Typical share of count | Typical share of value | Approval posture |
|---|---|---|---|
| Under $500 | 60 to 70% | 10 to 15% | Auto-post after review, known vendors only |
| $500 to $2,500 | 20 to 30% | 25 to 35% | Auto-post, spot check monthly |
| $2,500 to $10,000 | 5 to 10% | 30 to 40% | Single approver |
| Over $10,000 | 1 to 3% | 20 to 30% | Owner or director approval |
The point of this table is that approving the bottom band consumes most of the effort and controls almost none of the money. Moving it to automatic with a monthly spot check is not a loosening of control, it is a reallocation of attention to where the money actually is.
Segregation of duties without a finance team
Textbook segregation of duties requires different people to record, approve and pay. In a business with two office staff that is not achievable, and pretending otherwise produces a policy nobody follows.
Compensating controls that work at small scale:
- The owner reviews a monthly list of all new vendors added, which takes two minutes and catches the fake vendor scheme.
- The owner reviews all bank detail changes, separately from invoice approval.
- Bank statements go to someone who does not process invoices, even if that is the external accountant.
- Automated capture creates a record of what arrived and when, independent of what got entered, which is itself a control since a manual process leaves no such trail.
Why workflows get abandoned
- Everything requires approval, so the queue is always full and approval becomes a reflex click.
- The approver has no context. If the screen shows an amount and a vendor name but not the invoice PDF or what it was for, no real review is possible.
- There is no delegation. One approver on holiday stops payables entirely, so people route around the system.
- It lives in a separate tool from where the work happens, so it is one more login nobody opens.
- Nobody ever measures it. If no one tracks how long invoices sit in approval, the queue silently becomes the bottleneck the automation was supposed to remove.
Measure the queue
Two numbers, monthly:
- 1Average hours in the approval queue. If this exceeds a couple of days, your threshold is too low or your approver needs a delegate.
- 2Percentage of invoices requiring approval. If it is over about 25 percent, tighten the rules; you are spending attention on invoices that never get rejected.
A third number worth watching occasionally: how many approvals resulted in a change. If nothing is ever rejected or queried, the approval step is theatre, and the honest response is to either raise the threshold or accept that the control is not doing what you think.