Supplier invoice exception management: routing matrix

ininvoice: Between 20% and 30% of supplier invoices do not pass automatic three-way matching and fall into exception. Causes are six or seven recurring patterns: price variance, quantity variance, missing delivery note, no-PO invoice, potential duplicate, new supplier or amount out of range. Efficient handling is not about reviewing them all together, but about routing them by type to a single owner with a response SLA and automatic escalation.

The sales pitch for touchless AP is seductive: 70-80% of invoices approved without touching anything. The trap is the other side. What defines the team’s real productivity is the 20-30% that does NOT auto-approve. If those exceptions fall into a shared inbox, all the touchless savings evaporate in slow motion.

What an AP exception is (vs a reconciled invoice)

A reconciled invoice meets the three conditions of three-way matching without human effort: there is a PO, there is a delivery note and prices and quantities line by line fall within tolerance. It can be approved and scheduled for payment without anyone looking at it.

An invoice in exception is one that fails one of those conditions. Rarely is it a supplier error or fraud: most are operational artefacts (the delivery note was not recorded, the buyer did not warn about the rate change, the invoice arrives before the PO update). What defines them is that they require human context to resolve, and that context sits with purchasing, the warehouse or the budget owner, not with the person processing the invoice.

Typical statistic: 20-30% exception rate

Benchmarks published by IOFM and mid-market teams in Europe agree on a range: between 20% and 30% of received invoices fall into some exception state after the first automatic pass. Top-quartile organisations get down to 10-15%. Worst-in-class exceed 40%.

The distribution by type is stable. Out of 100 typical exceptions:

30-35 due to price or quantity variance against the PO.
20-25 due to missing delivery note not booked when the invoice arrived.
15-20 due to no-PO invoices (services, recurring spend).
5-10 due to potential duplicates needing review.
5-10 due to new supplier without validated setup.
Rest: amount out of range, inconsistent dates, miscalculated VAT.

Recurring exception types

Seven patterns cover more than 95% of cases at a mid-sized company. Below: detection signal and natural resolution owner.

Type	Signal	Owner	SLA
Price variance	Invoice unit price ≠ PO price out of tolerance	Purchasing	48h
Quantity variance	Invoiced qty ≠ ordered or received qty	Warehouse / receiving	24h
Missing delivery note	Invoice received with no booked receipt	Warehouse	24h
No PO	Invoice without locatable PO number	Requester / budget owner	48h
Potential duplicate	Partial match with prior invoice (SHA, number, amount, supplier)	AP / controller	24h
New supplier	Tax ID not in supplier master	AP / compliance	72h
Amount out of range	Invoice exceeds supplier or category threshold	Finance director / approver	48h

There is a quiet eighth type worth watching: invoice date earlier than PO date. It signals retroactive invoicing and usually hides an undisclosed rate change or a recreated invoice.

Routing matrix by type

Routing is the rule that turns an exception type into a task with owner, SLA and escalation. The operational matrix that works in mid-market is this:

Type	First owner	Level 1 escalation	Level 2 escalation
Price variance	Buyer assigned to the PO	Purchasing lead	Finance director
Quantity variance	Receiving / warehouse lead	Logistics manager	Operations
Missing delivery note	Receiving	Logistics manager	Finance director
No PO	Requester (cost centre)	Area approver	Finance director
Duplicate	AP controller	Finance director	—
New supplier	AP / compliance	Finance director	—
High amount	Approver per delegation matrix	Finance director	CEO

Three principles encoded in the matrix:

Single owner per type. If the buyer is on leave, escalate to their lead, not back to AP.
Automatic time-based escalation, not by button. If the first owner does not respond on time, the task moves up on its own.
AP never closes the exception on its own. It only logs and routes. Closing requires validation from the area with context.

SLAs by amount and urgency

Situation	Applicable SLA
Amount < EUR 500 and due date > 30 days	Standard SLA (24-72h)
Amount > EUR 5,000	SLA × 0.5 (half of standard)
Due date < 7 days	Max 8 business hours
Critical supplier (top 20)	SLA × 0.5 and notify finance director

Spanish Law 15/2010 on late payments: 60-day B2B cap

Payment terms are not voluntary. Law 15/2010, of July 5, sets a maximum of 60 calendar days for B2B operations (30 days default with no pact). The clock starts at invoice or goods receipt, whichever is later.

Direct implication: an invoice stuck in exception for more than 30-45 days compromises legal compliance with the payment term. Exception aging is not decorative; it is compliance.

Routing automation vs shared inbox

The most widespread antipattern in mid-market: a single “pending invoices” inbox where everything lands and admin filters by hand. Consequences are predictable: average cycle time of 7-10 days, first-touch resolution below 30%, and the finance director as a bottleneck approving everything doubtful by default.

Automated routing does not require replacing the ERP. It needs three layers:

Detection. Matching rules that classify the exception by type at intake.
Assignment. Table mapping type × cost centre × supplier to an owner with backup.
Escalation. Clock that moves the task up the next level when the SLA expires without human intervention.

What if we showed you on your real exceptions?

ininvoice classifies automatically by type, assigns an owner and applies an escalation SLA. Book a spot and measure how many exceptions you would have this month and to whom each would route.

Resolution KPIs: cycle time and first-touch resolution

Average cycle time (hours) between detection and resolution, by type. Reasonable target: < 24h on quantity and delivery note, < 48h on price, < 72h on no-PO.
First-touch resolution (%): exceptions resolved by the first owner without escalation. Target: > 70%.
Aging > 14 days (%): open exceptions over two weeks old. Target: < 5%.

30-day plan to improve management

Week 1. Manually tag last month’s exceptions with the seven canonical types. Calculate real distribution and current cycle time.
Week 2. Define routing matrix with owner and backup per type. Validate with purchasing, logistics and finance director.
Week 3. Implement rules in the system (email, alerts or dedicated tool). Configure automatic time-based escalation.
Week 4. Measure cycle time and first-touch resolution. Adjust tolerances and SLAs based on real data.

FAQ

What exception rate is reasonable for an SME?: Between 20% and 30% in the first touchless year. Below 15% means a mature team and clean masters. Above 35% usually points to PO-receiving flow problems, not to AP.
Who should resolve price variance exceptions?: The buyer who negotiated the PO. AP has no contract context. If the buyer does not respond in 48h, escalate to the purchasing lead automatically.
How are no-PO invoices handled?: They are routed to the requester or cost-centre owner, not to purchasing. Professional services and recurring spend do not go through a formal PO.
What is the maximum B2B payment term under Spanish Law 15/2010?: 60 calendar days from goods or invoice receipt with a pact. Without a pact, 30 days. The law allows automatic claim of late-payment interest when the term is exceeded.
How is the team’s efficiency measured?: Average cycle time per type, first-touch resolution and aging > 14 days. IOFM publishes benchmarks: top-quartile teams close > 70% on first touch and keep aging below 5%.
Is dedicated software needed or are email rules enough?: Below 50 exceptions/month, email rules and a manual Kanban suffice. Above 100/month, manual coordination cost exceeds the dedicated software cost.
What about exceptions the first owner rejects?: If the buyer says “this price isn’t ours”, the exception goes back to AP flagged as dispute and the supplier is notified for a correction invoice. It is never closed silently: it stays in the audit log.

What would your exception cycle time look like with automatic routing?

Connect Gmail or Outlook and measure exception rate, type distribution and real cycle time over 30 days. Get started.

Three things to remember

Touchless AP is not measured by the 70-80% that auto-approves, but by how the remaining 20-30% is handled.
A well-routed exception goes to a single owner with SLA and automatic escalation, never to a shared inbox.
Three KPIs govern: cycle time, first-touch resolution and aging > 14 days. Law 15/2010 turns aging into compliance, not a decorative metric.

If you want to see how the routing matrix looks on your own invoices, try ininvoice. Check the pricing and features.

Supplier invoice exception management: routing matrix by type