Invoice approval workflows that actually move

An invoice approval workflow decides who signs off a supplier invoice before it gets paid, and in what order. On paper it is a short list of steps. In practice it is where invoices go to wait.

Most finance teams know who should approve what. The trouble is practical: invoices that sit for days on the wrong person’s desk, approvers on holiday with no cover, and a month-end scramble to clear a backlog that built up quietly all month. The design of the workflow is what decides whether approvals move or stall.

What an invoice approval workflow is

An invoice approval workflow is the set of rules that route a supplier invoice to the people who need to authorise it, and the sequence they authorise it in. It answers a few plain questions. Who can approve an invoice of this size? Does it need a second approver above a certain value? Who covers when the named approver is out? And what happens when the invoice does not agree with its purchase order?

For a small team the workflow might be one person. As spend and headcount grow, it becomes a chain: a budget holder confirms the cost belongs to them, a manager signs off the value, and finance does the final check before posting to the ERP. The steps are rarely the problem. The delay lives in how the invoice travels between them.

Why approval workflows silt up

A workflow that looked sensible on a whiteboard silts up for a handful of predictable reasons. Each one is a place where an invoice stops moving and nobody notices until a supplier calls.

• Chasing by email. When approval happens over email, the invoice becomes an attachment in someone’s inbox. There is no queue, no reminder, and no record of who is holding it up. The AP clerk turns into a chaser, forwarding the same PDF and asking for a yes. The invoice moves at the speed of the busiest approver’s inbox.

• Delegation gaps. The named approver goes on holiday and their invoices stop. No cover was set, so the queue behind them grows for two weeks. When they return, they approve in bulk to clear the backlog, which turns a control into a formality.

• Everything routed the same way. If a £40 stationery invoice and a £40,000 subcontractor invoice follow the identical path through the same three approvers, the small stuff clogs the queue and the approvers stop reading carefully. Volume dulls attention, and the spend that warrants scrutiny gets the same tired glance as the spend that does not.

• No link to the match. An invoice that fails its purchase order match still needs a human decision. If the workflow treats a mismatch the same as a clean invoice, the exception hides in the general queue, and the person who can resolve it may never see it.

Designing an approval workflow that moves

A workflow that moves is built on a few design choices. None of them are complicated. They are decisions most teams never got round to making explicit.

• Approval thresholds. Set value bands and map each to the level of sign-off it needs. A low-value invoice within budget can clear on one approval. A high-value one needs a second, more senior approver. Thresholds keep small invoices out of senior queues and reserve scrutiny for the spend that warrants it.

• Exception-only routing. Send clean, matched invoices straight to posting and route only the ones that need a judgement call to a human. When an invoice agrees with its purchase order and receipt within tolerance, there is nothing for an approver to add. Keep their time for genuine exceptions: a price variance, a missing receipt, an invoice with no purchase order behind it.

• Delegation rules. Every approver has named cover, and the cover applies automatically when they are out. Approval authority follows the role, so a holiday does not freeze a queue. The rule is set once and holds through leave, illness and staff changes.

• Clear ownership at each step. Each invoice has one owner at any moment, and everyone can see who that is. A shared queue with visible ownership ends the "I thought you had it" gap that email approvals create.

• Reminders and escalation. An invoice waiting too long at one step chases itself. After a set period it nudges the approver, and after longer it escalates to their manager or cover. The clock does the chasing, and the AP team stops being a call centre for its own invoices.

A worked approval flow

Here is how those choices come together for a mid-market team processing a few thousand invoices a month. Take a single supplier invoice for £6,500 of materials raised against a purchase order.

1. The invoice is captured on arrival, whether it came in by email, PDF or post, and the line detail is read and matched against its purchase order and goods receipt.

2. The match clears within tolerance on quantity and price, so the numbers need no correction. The workflow still applies the value rule: anything over £5,000 needs a budget holder to confirm the cost is theirs.

3. It routes to the named budget holder for that cost centre. They see the invoice, the purchase order it matched, and the amount in one view, and approve in a click.

4. Because £6,500 sits in the band that needs a second sign-off, it routes on to the department head. They are on leave, so the delegation rule hands it to their named cover and the queue keeps moving.

5. The cover approves. The invoice now carries a complete authorisation trail: who approved, at what level, and when.

6. Finance runs the final check and the invoice posts to the ERP with its nominal codes, cost centre and tax treatment intact. Nothing is rekeyed, and the audit trail stays attached to the record.

A £40 stationery invoice in the same system never touches that chain. It matches, it falls under the threshold, and it posts straight through. The approvers only ever saw the invoice that needed them.

That flow depends on the invoice being read accurately and matched before it reaches a human, which is the job of the capture and matching layer underneath the workflow. It rests on the same foundation as how AP automation works: capture, extract, match, then route only what needs a decision.

Measuring an approval workflow

You cannot improve a workflow you are not measuring. Two numbers tell you most of what you need to know, and both are worth tracking every month.

Cycle time. This is how long an invoice takes from arrival to approved, or from arrival to posted. Measure it across the whole journey, and per step too, so you can see where invoices wait. A long average with one step accounting for most of it points you straight at the bottleneck, whether that is a single overloaded approver or a value band that routes too much to the top.

First-time approval rate. This is the share of invoices that clear their approval chain without being sent back, queried or reworked. A low rate means invoices are reaching approvers with something wrong: a bad match, a missing purchase order, the wrong approver in the chain. Every rejection is a lap of the track the invoice has to run again, so this figure often warns you sooner than cycle time alone.

Track both over time and watch what moves them. A threshold set too low, a delegation rule that never got updated, or a supplier who always invoices without a purchase order will show up in these two numbers well before it shows up as an angry phone call.