AP invoice processing is the sequence a supplier invoice follows from arrival through matching, coding, approval, and payment. Invoices stall at exceptions, which Ardent Partners measured at 18.4 percent of invoices for 2025. Those stalled invoices set cost per invoice, cycle time, and most of the workload in accounts payable.
Key takeaways
- Close to one invoice in five stops for a human decision. Two averages hide that split, the cost of $9.84 per invoice and the cycle time of 8.2 days. Both mix cheap invoices with a smaller population that consumes hours each.
- Route exceptions by who can resolve them, never by who received them. The team that finds an exception is rarely the team that can close it.
- Attach a service level and a reason code to every exception class. Without cause data, you cannot tell whether one supplier, one buyer, or one tolerance generates a third of the rework.
- Some exceptions are worth keeping. Widening tolerances lowers the reported rate and buries the exposure in the paid population.
Ardent Partners published the exception figure in its State of ePayables 2025 benchmarks, released in January 2026, and reported that its top performing group runs 47 percent below that average. The distance between those two numbers is not a software gap. It is a routing and ownership gap.
Why exceptions decide everything else in AP invoice processing
An invoice that matches, codes, and approves cleanly costs almost nothing to process. Ardent reported an average cost of $9.84 and an average cycle time of 8.2 days for 2025. Both are blended figures. They mix a large population of cheap invoices with a smaller one that consumes hours each.
Most accounts payable (AP) teams show the same pattern. An exception is found, and the invoice goes to the AP shared mailbox, because that is where every unresolved thing goes. The processor cannot resolve it, since procurement, receiving, tax, or a budget owner has to settle the disagreement. So the processor becomes a messenger, chasing the resolver and answering the supplier who now calls weekly.
That default is expensive. Ardent found that 21.9 percent of AP staff time goes to supplier inquiries. Many of those inquiries exist because an exception is open somewhere with no owner and no clock. The supplier calls because nobody told them anything, and AP is the only number on the invoice. At enterprise scale, each status question takes eight minutes. Together they cost a week per person each month.
How to think about routing an exception
Two principles produce most of the gain.
Route by who can resolve the exception, and never by who received it. The team that finds an exception is rarely the team that can close it. A price variance needs the buyer who agreed the price, and a missing receipt needs whoever took delivery. Sending both to AP guarantees a second hop and doubles elapsed time.
Attach a clock to every class. Without a service level agreement (SLA), an exception ages until a supplier escalates it. The invoice then jumps the queue for reasons unrelated to materiality. Set the target by class, and measure aging by owner rather than in aggregate.
Then insist on a reason code at closure. Most teams record that an exception was resolved and never why it happened. Without cause data, you cannot tell whether one supplier, one buyer, or one tolerance setting generates a third of your rework.
Decide in advance which exceptions block payment and which let the invoice post with a flag. Treating every exception as a hard block creates late payments, and blocking none of them makes the check ornamental.
The AP invoice processing exception taxonomy
Each type below has a trigger, a rightful owner, a resolution path, and a characteristic failure mode when it is routed to the wrong queue.
Price variance
This exception triggers when the invoiced unit price falls outside tolerance against the purchase order (PO). The buyer who agreed the price owns it. Resolution means comparing invoice to contract, then amending the PO or requesting a credit. Misrouted to AP, this exception lets the supplier reprice the same way next month, because nobody told procurement the contract is being ignored.
Quantity variance
This exception triggers when the invoiced quantity exceeds what was received. Receiving and the requester own it, since only they know what arrived. Resolution means confirming the physical receipt, then posting the missing quantity or rejecting the excess. The failure mode is AP posting a receipt on someone's word, which collapses the split between receiving and payables.
Missing goods receipt
This exception triggers when three-way matching finds a PO and an invoice with no receipt posted. The requester owns it. Resolution means requesting the receipt and holding payment when the goods have not arrived. Misrouted, AP posts receipts at period end to clear the queue, which turns a control into a formality.
Missing or invalid purchase order
This exception is triggered by a blank PO reference, a closed PO, or one already fully consumed. Procurement and the requester own it. Resolution means retrofitting a PO where policy allows, or routing the invoice down the non-PO path for coding and approval. Misrouted, AP raises the PO itself, which authorizes nothing.
Duplicate suspicion
This exception is triggered by a near match on vendor, amount, invoice number, or date, and often by the same invoice arriving through two channels. AP owns this type outright. Resolution means comparing against paid and in-flight invoices, and checking channel history. The failure mode is releasing the payment on the supplier's assurance. The Washington State Auditor reported in 2022 that duplicate payments run between 0.8 percent and 2 percent of total payments.
Unknown or unmatched vendor
This exception triggers when no vendor master record matches, or several match loosely. The vendor master team owns it, and never the processor who received the email. Resolution means running the onboarding checks with independently verified bank details. Misrouted, somebody creates a vendor record from details in the invoice email. A business email compromise (BEC) attack needs exactly that path.
Tax and VAT mismatch
This exception triggers when a tax code, rate, or value-added tax (VAT) registration number disagrees with the treatment expected in that jurisdiction. Tax owns the rule and AP applies it. Resolution means determining the correct treatment, then requesting a corrected invoice where recovery depends on it. Misrouted, AP overrides the code to release the block, and you lose the input VAT recovery.
Coding failure
This exception triggers when a non-PO-backed invoice arrives with no general ledger (GL) account, no cost center, or a description nobody recognizes. The budget owner owns the decision. Resolution means proposing coding from the vendor and prior treatment, confirming it, and capturing the answer as a rule. Misrouted, AP codes to a catch-all account, and spend reporting quietly stops being true.
Currency or rate mismatch
This exception triggers when the invoice currency differs from the PO currency, or the applied rate differs from your rate table. AP owns it under a treasury policy. Resolution means applying the policy rate and booking the difference as exchange variance. Misrouted, somebody rekeys a converted amount, and the audit trail back to the source document breaks.
Missing approval
This exception triggers when no approver exists for that cost center or amount band, or a delegated authority has lapsed. The controller owns it, as the holder of delegation of authority. Resolution means escalating through the substitute chain and correcting the routing table. Misrouted, AP chases the approver by email, and the escalation leaves no record.
Blocked for credit or dispute
This exception is triggered by an open credit note, a rejected delivery, or a supplier on payment hold. The party in dispute owns it, with AP holding the block. Resolution means settling the dispute or netting the credit, with a documented release. Misrouted, AP lifts the block to stop the calls, and you pay for rejected goods.
Ownership and service levels in practice
Write the taxonomy down as a routing table. The four columns are exception type, resolving role, target resolution time, and escalation path. Publish it to the resolvers as well as to AP, since most have never seen the queue they create.
Set different clocks by class. A missing receipt is a same-day fix on a delivered order, and a cross-border tax determination takes longer. Report aging by owner, and let each owner see their queue.
Keep the supplier informed at every state change. Most inquiries are requests for status. Send a message when the state changes, and the supplier has no reason to call. That one change does more for the 21.9 percent figure than any extraction improvement.
Exceptions you should keep
Not every exception is waste. Sometimes a supplier bills above contract. A price variance check catches that, and it has paid for itself. A duplicate flag stops a second payment, and it saves the recovery project.
Once exception rate becomes a target, the temptation is to widen tolerances until the number falls. That works on the report and buries the exposure in the paid population. A supplier can bill 4 percent over and stay under a 5 percent variance tolerance. It clears every time, and repeats monthly.
Some exceptions should stay manual by design. Keep a human decision for first-time vendors, bank detail changes, and invoices above a materiality threshold, whatever your automation can do. Aim to reduce how many exceptions arise, since seeing fewer of them on a report is a different outcome from having fewer of them. Our companion piece on automated invoice processing covers what automation changes at each stage.
Where current approaches fall short
Most exception handling lives in a shared mailbox and a spreadsheet. That setup cannot answer basic questions, including how many exceptions are open, how old the oldest is, or which cause recurs most. The queue is invisible, so it is never managed.
Workflow tools process invoices inside the enterprise resource planning (ERP) system and stop at the mailbox door. The conversation that resolves the exception happens in email, outside the audit trail, and the ERP records only that the block cleared. When an auditor asks who approved the variance and on what evidence, the answer is in somebody's sent folder. Our guide to the invoice processing stages sets out the terms behind each step.
How we approach exception resolution
We treat the AP mailbox as a service center rather than a dumping ground. Our AP Inbox Service Center reads every incoming message, classifies it, and matches it to the invoice or the vendor. It then routes the message to the owner who can resolve it, with the full thread attached.
Our AI Agents resolve the recurring classes directly. The Payment Status Responder answers status questions without a person reading the email. The Bank Change Verification Guardian runs the verification steps before a bank detail change is written to the vendor master. The Duplicate Invoice Gatekeeper checks submissions across channels before a duplicate becomes a payment. Our overview of AI Agents in the AP inbox describes each one.
Customers see a 60 percent reduction in email processing time. Every Agent action is logged with the evidence behind it, so the resolution has an audit trail that an email thread never had.
The bottom line
Sort your last month of exceptions by cause and by who actually resolved them. Most teams find that a few causes generate the bulk of the work, and that AP resolved things it had no authority to decide. Fix the routing for the largest causes first, and set a clock on each.
Frequently asked questions
What is an invoice exception?
An invoice exception is any invoice the workflow cannot complete without a human decision. Common types include price and quantity variance, a missing goods receipt, an invalid PO, suspected duplicates, unknown vendors, and coding failures. Ardent Partners reported an average exception rate of 18.4 percent for 2025.
What is a good invoice exception rate?
Ardent Partners put the 2025 average at 18.4 percent, with its top performing group running 47 percent below that average. Judge your rate by cause, since wide tolerances produce a low rate and leave the variances unexamined.
Who should resolve invoice exceptions?
The role that owns the underlying disagreement should resolve it. Price variances belong to the buyer, receipt issues to receiving, tax mismatches to tax, and coding decisions to the budget owner. AP owns duplicates, currency application, and the routing itself.
How do you reduce exceptions without weakening controls?
Work on causes rather than tolerances. Clean the vendor master, fix suppliers who invoice against expired contracts, and enable receipt posting at delivery. Then automate the resolution path for exceptions that recur with a known answer, keeping human review for bank changes and high-value invoices.