What counts as an invoice exception
An invoice exception is any invoice that stops in the process because something does not match or is missing, so a person has to review it before payment.
Count an invoice once, even if it has several problems. An invoice that fails the price check and is also missing a receipt is one exception with two causes. That keeps the rate comparable with published benchmarks and with your own past months. For background on how teams handle them, see our exception handling glossary entry.
How to calculate your exception rate
Exception rate = invoices with at least one exception in a period ÷ total invoices processed in that period × 100.
| Measure | Value |
|---|---|
| Invoices processed | 1,250 |
| Invoices with at least one exception | 230 |
| Exception rate | 18.4% |
| Invoices approved with no human touch | 443 |
| Straight-through rate | 35.4% |
Measure monthly and keep the definition stable. If you change what counts as an exception, restate earlier months so the trend stays honest.
Invoice exception rate benchmarks
Ardent Partners reports an 18.4% average exception rate, 11.1% for Best-in-Class AP teams and 20.9% for everyone else.
| Benchmark | All organizations | Best-in-Class | All others |
|---|---|---|---|
| Invoice exception rate | 18.4% | 11.1% | 20.9% |
| Invoices processed straight-through | 35.4% | 51.0% | 29.0% |
| Invoices linked to a PO | 65.4% | 84.0% | 47.3% |
Best-in-Class teams link far more invoices to purchase orders. A PO gives the matching step something to check against, which is one reason their exception rate is lower. More sourced figures are on our AP automation statistics page.
Common causes of invoice exceptions
Most exceptions come from a short list of causes: no PO, price or quantity differences, missing receipts, suspected duplicates, vendor data problems and missing coding.
| Cause | What happens | Usual fix |
|---|---|---|
| No PO | Nothing to match, so the invoice needs an approver to confirm it | Require POs for goods; route non-PO spend by budget owner |
| Price variance | Invoice price differs from the PO | Update the PO for agreed changes; request a credit note otherwise |
| Quantity variance | Billed quantity exceeds quantity received | Record late receipts; ask the supplier to reissue |
| Missing receipt | Goods arrived but receiving was not recorded | Make receiving part of the delivery process |
| Suspected duplicate | Same supplier, amount or invoice number as an earlier bill | Confirm and reject, or release if it is genuinely new |
| Vendor master data | Unknown supplier, wrong remit-to or tax details | One clean record per supplier, with change controls |
| Coding | No GL account, department or job can be assigned | Default coding by supplier; capture the reference on the PO |
How to reduce your exception rate
Find your biggest causes, fix them at the source with POs, receipts, tolerances and clean vendor data, then automate the checks that remain.
- 1
Step 1
Measure your exception rate for the last three months and tag every exception with one cause. - 2
Step 2
Rank causes by volume and fix the largest first; one or two causes usually account for most exceptions. - 3
Step 3
Require POs for goods and recurring spend, and record receipts promptly so matches do not fail for missing data. - 4
Step 4
Set price and quantity tolerances per supplier so rounding and freight differences stop creating exceptions. - 5
Step 5
Clean the vendor master: one record per supplier, correct remit-to details and tax IDs. - 6
Step 6
Send recurring supplier errors back to the supplier with the reason, and track whether they fall.
Matching rules matter most for the price and quantity causes. Our three-way matching guide covers tolerances and partial deliveries.
What exceptions cost
Exceptions take people time, so they push up cost per invoice and processing time.
Ardent reports an average all-in cost of $9.84 per invoice, and $2.65 for Best-in-Class teams, which also have the lowest exception rates. Work out what exceptions cost your team in our cost per invoice guide or with the cost per invoice calculator.
How Aequo AP handles exceptions
Aequo AP matches invoices to POs and receipts within per-supplier tolerances, flags duplicates, and puts everything else in an exception queue with a suggested resolution.
Partial invoices are checked against the PO's remaining amount so installments are not treated as overbilling. See exception management in Aequo AP.
Frequently asked questions
What is an invoice exception in accounts payable?
An invoice exception is any invoice that cannot be approved and paid without someone stepping in, for example because it does not match the purchase order or receipt, has no PO, looks like a duplicate, or is missing data needed to code it.
What is the average invoice exception rate?
Ardent Partners' State of ePayables 2025 puts the average invoice exception rate at 18.4%. Best-in-Class AP teams averaged 11.1%, compared with 20.9% for all other organizations.
How do you calculate invoice exception rate?
Divide the number of invoices that had at least one exception in a period by the total number of invoices processed in that period, then multiply by 100. For example, 230 exceptions out of 1,250 invoices is an 18.4% exception rate.
What causes most invoice exceptions?
The usual causes are invoices with no PO, price or quantity differences from the PO, goods not yet received, suspected duplicates, vendor master data problems, and missing coding information. Measure your own causes, because the mix differs by company.
What is a good invoice exception rate?
Ardent's Best-in-Class group averaged 11.1%, so a rate near or below that is strong. A falling trend matters more than a single number, because exception rates depend on how much of your spend runs through POs.
How is exception rate related to straight-through processing?
They move in opposite directions. Straight-through invoices need no human touch; exceptions always do. Ardent reports 35.4% of invoices processed straight-through on average, 51.0% for Best-in-Class teams and 29.0% for all others.
Automate matching, approvals and exception handling
Aequo AP captures invoices, matches them to purchase orders and receipts, routes approvals and flags duplicates and exceptions, then syncs with QuickBooks Online, Xero, FreshBooks or Zoho Books.
Related guides and tools
- Three-way matchingWhere most match exceptions start.
- Cost per invoiceWhat exceptions add to processing cost.
- Preventing duplicate paymentsCatch duplicates before they are paid.
- AP exception management guideRunning an exception queue day to day.
- AP automation statistics 2026All sourced AP benchmarks in one place.
Sources
Checked on October 22, 2026. Vendor capabilities and prices change; confirm current details with each vendor.
- Ardent Partners, The State of ePayables 2025: AP's Unfinished Journey — Tables 1 and 2: 18.4% average exception rate; 11.1% Best-in-Class vs 20.9% all others; 35.4% straight-through, 51.0% vs 29.0%
- Ardent Partners, State of ePayables (Part Nine): AP Benchmarks and Best-in-Class Performance — 18.4% average exception rate; Best-in-Class 47% lower exception rate