It is the Tuesday before the payment run. The AP lead exports the list of blocked invoices from the ERP and it is longer than last week's. Almost all of them are three-way match exceptions: invoices that do not agree with the purchase order, the goods receipt, or both. A handful point to a real problem with a vendor. Far more come down to a receipt that nobody has posted or a price the buyer agreed by email and never put on the order.
The queue grows because each exception belongs to someone outside accounts payable, while AP is the team that sees it.
Why three-way match exceptions pile up
The match compares what was ordered, received and billed. Each comparison can fail for ordinary reasons.
Late goods receipts. The invoice often arrives before the site has recorded the delivery, so the ERP blocks it for quantity. Many clear on their own once the receipt is posted, which is why they get ignored and why they clog the list.
Tolerances set once and left alone. Price and quantity tolerances are usually configured at implementation and rarely revisited. Too tight, and they block invoices over freight rounding. Too loose, and real overcharges pass unseen. Tolerances are a control decision and belong with the controller.
Service purchase orders. Services have no physical receipt. A requester whose day job is not AP has to confirm the work was done, and open-ended service orders give the invoice nothing specific to match.
Partial deliveries. A vendor ships in three loads and invoices twice, or bills the full order early. Small residual quantities then sit open for months.
Unit-of-measure differences. The order is in cases and the invoice is in units, so the price looks wrong by a factor of twelve. The fault is usually a missing conversion in the master data.
Price changes. A contract price that moved, a surcharge, or a freight line nobody put on the order.
Ardent Partners' State of ePayables 2025, vendor research underwritten by sponsors with no sample stated on the page, reports an average exception rate of 18.4%. Time on block also counts against payment timing. For cycle time from receipt of invoice until payment is transmitted, the APQC Open Standards Benchmarking (cross-industry median, all companies) figure is 15.0 days, across 2,226 companies.
Who owns each type of exception
AP should coordinate and keep time on exceptions, not resolve most of them. When AP accepts a price variance on its own, it makes a purchasing decision without the authority to do so.
| Exception | Usual cause | Owner who can fix it | What AP needs back |
|---|---|---|---|
| Quantity: receipt missing | Delivery not yet recorded | Receiving or site lead | Receipt posted, or confirmation goods did not arrive |
| Quantity: billed ahead of delivery | Vendor invoiced the full order early | Buyer, with the vendor | Corrected invoice or a delivery date for the balance |
| Price variance | Contract change, surcharge, order not updated | Buyer or procurement | Order amended, or a credit note requested |
| Service order not confirmed | Requester has not accepted the work | Requester or budget holder | Service confirmation or acceptance |
| Unit of measure | Missing or wrong conversion | Master data team | Conversion fixed, invoice reprocessed |
| Same variance recurring | Tolerance too tight or too loose | Controller | Tolerance reviewed and the decision documented |
How to triage the queue
Sort first by the payment due date, or the discount date if there is one. Then sort by cause, because each cause has one owner and can go as a batch.
Late receipts are the quickest win. One list per site, sent each morning, tends to clear more blocks than chasing invoices one by one. Price variances go to the buyer with the order and invoice side by side. Set an age limit after which an exception moves to the owner's manager, and keep to it.
Then count open exceptions by cause, owner and age every week. A rising count in one cause shows where the process needs work. That is designing work around what needs a person, applied to payables.
Where AI helps, and where people decide
When Gartner surveyed 183 CFOs and senior finance leaders in May and June 2025, AP process automation ranked among the top AI use cases at 37%. Exceptions suit it, because most of the effort is reading: the invoice, the order, the receipt history, the blocking reason.
Classifying the exception. ERP blocking reasons say what failed, not why. A model reading the invoice text and order history can separate a late receipt from a genuine short delivery.
Suggesting the cause. Take an invoice priced at exactly twelve times the order price, on an order in cases of twelve. The suggestion should say so and show both lines, so the reviewer checks evidence rather than a label.
Drafting the vendor query. A first draft asking for a credit note or corrected invoice, which a person reads and sends.
Releasing a block, accepting a price, short-paying and changing a tolerance stay with people. A model can misclassify or put the wrong amount in a draft, so keep it read-only and show the source for every suggestion.
What AI on the exception queue will not fix
Receipt discipline stays a people problem. If a site does not post receipts, AI tells you sooner and that is all. The fix is a posting standard and someone at the site who owns it.
Purchase orders raised after the invoice arrives are outside its reach too. That is a procurement compliance issue, and it needs a policy conversation with budget holders.
Frequently asked questions
What is a three-way match exception?
A three-way match exception is an invoice that does not agree with its purchase order and goods receipt on price, quantity or receipt, so the ERP blocks it for payment until someone resolves the difference.
What causes most three-way match exceptions?
Usually timing and data rather than vendor error: late goods receipts, tolerances that do not fit, unconfirmed service orders, partial deliveries and unit-of-measure differences.
Who should resolve a price variance on an invoice?
The buyer or procurement owner should resolve a price variance, because accepting a different price is a purchasing decision. AP should send it with the evidence and track the answer.
Should we widen tolerances to reduce exceptions?
Only after you know which exceptions the tolerance causes and what a wider one would let through. The controller should make and document that decision.
Can AI release blocked invoices automatically?
In our view it should not. Releasing a block is a decision for a person with the authority to make it; AI prepares the evidence.
Where CFOLogic fits
We design and build purchase-to-pay exception tools that sit over the ERP a team already uses. They read the data without writing to it, and a person signs off anything sent outside finance. The P2P demo, built on a fictional company, groups invoices by status and owner and drafts nudges for people to send. CFO Success Partners explains how we work with CFOs.