Invoice exception management in accounts payable

By Nicolau Matarrodona, founder · Published 28 April 2026 · Updated 24 October 2026

Supplier invoice exception management: routing matrix by type

In short: invoice exception management is the process of sending every supplier invoice that fails automatic matching against its purchase order and delivery note to one named owner, by exception type, with a response time, so it is resolved before payment. The guide is for AP teams and controllers. ininvoice holds each exception with its type and reason; a person approves, rejects or asks for clarification, and approved invoices go out as CSV or Excel for your ERP. Routing and escalation stay with your team.

The sales pitch for touchless AP is seductive: most invoices matching without anyone checking them by hand. The trap is the other side. What defines the team’s real productivity is the 20-30% that does NOT match at the first pass. 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 is ready for a person to approve without anyone checking the lines again.

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

Published benchmarks 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. See how to triage invoice and PO amount differences line by line.
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.

Invoice exception management by type: the routing matrix

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.
Time-based escalation, agreed in advance. If the first owner does not respond on time, the task moves to the next level without anyone having to argue for it.
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

Which lines of an invoice will turn into exceptions? The discrepancy checker matches them against the purchase order and the delivery note and shows price and quantity differences and lines without a purchase order, in your browser and with no signup. Open the discrepancy checker

Regional note: Spanish Law 15/2010 on late payments

This section applies only in Spain. The exception taxonomy, routing matrix and SLAs above are jurisdiction-neutral.

Payment terms are not voluntary. Article 4 of Spanish Law 3/2004 on late payment, as amended by Law 15/2010, of July 5, sets 30 days from receipt of the goods or services, which the parties can extend by agreement up to a maximum of 60 calendar days.

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.

Organised exceptions 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.

Organising exceptions 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.
Follow-up. A response time per type, and what happens when it expires.

In ininvoice, detection is automatic: every exception is held with its type and reason. Assignment and follow-up are your team’s process; ininvoice does not route or escalate tasks.

What if we showed you on your real exceptions?

ininvoice holds the invoice with its reason (price or quantity variance, missing delivery note, no PO, possible duplicate); a person approves it, rejects it or asks for clarification from the panel, and the decision stays in a history you can export to Excel. See it on your own exceptions.

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 the rules in your process (e-mail, reminders or a dedicated tool), including what happens when a response time expires.
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 year of automated matching. 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.
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?: Without an agreement, 30 days from receipt of the goods or services; with an agreement, 60 calendar days at most. It is set by Article 4 of Law 3/2004, as amended by Law 15/2010.
How is the team’s efficiency measured?: Average cycle time per type, first-touch resolution and aging > 14 days. 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 exceptions look like, by type?

Send a few of your invoices with their POs and delivery notes and see which ones are held, and why. Arrange a demo.

Three things to remember

Touchless AP is not measured by the invoices that match at the first pass, but by how the remaining 20-30% is handled.
A well-handled exception goes to a single owner with a response time and a backup, 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, see how invoice matching flags the exceptions it applies to. Pricing is tailored: a proposal built on your own invoices, within 48 hours.