Definition
A supplier invoice that fails a check before payment, such as a price or quantity mismatch with the PO, a missing receipt, a missing approval or a suspected duplicate, and is held until someone resolves it.
Also called: match exception, AP exception, invoice hold
What it means
An invoice exception is a supplier invoice that fails a check before payment. The price does not agree with the purchase order. The quantity billed is more than the receiving team booked in. There is no approval on a non-PO invoice, or the approver is not the person with authority for that spend. Or the invoice looks like one already in the system. Whatever the cause, the invoice stops and waits until a person resolves it. Some teams call the same thing a match exception, an AP exception or an invoice hold.
What counts as a failure depends on how your company has set up its checking. A PO-backed invoice in a three-way match has to agree with the purchase order and with the receipt. Where an invoice tolerance exists, small differences inside the tolerance post normally and only invoices outside it become exceptions. Those tolerances are set by the company, often by vendor or by contract, so the same difference can be an exception for one supplier and routine for another. Country practice and local rules vary too, which is why the definition has to come from your own policy rather than from a general rule.
A held invoice is not a rejected invoice. The company still owes the money. The invoice is still sitting on the vendor record and still ageing, and the supplier still expects to be paid. What has paused is the payment, not the liability. That difference matters at month end, when the accrual is still real, and it matters when a supplier calls about an invoice your team cannot see a problem with.
How it works in practice
Every exception needs a named owner, and the owner follows the cause. A price difference belongs with the buyer who negotiated it. A quantity difference belongs with the receiver who booked the goods in. Non-PO spend belongs with the approver who should have signed it off. A queue where items sit without a name against them is a backlog, not a workflow, and it will be cleared by whoever is closest to it rather than by whoever can fix it.
There are two ways out of an exception. Someone fixes the cause, or someone overrides the check. Fixing means correcting the PO price to the agreed figure, posting the missing receipt, getting the right approval, or confirming with the vendor that the invoice is a duplicate and voiding it before payment. Overriding means paying the invoice while the mismatch is still there. Both routes close the item, and only one of them leaves the records correct.
Time runs against every item in the queue. An exception that ages past the supplier's due date puts early-payment discounts and supplier goodwill at risk. A discount lost because a receipt was never posted can cost more than the mismatch ever looked worth, and the supplier who has to chase payment remembers it at the next price review.
Where it goes wrong
The most common failure is a queue cleared by override rather than by repair. A clerk under pressure pays the invoice to make the exception disappear. The check did its job and then got waved through, and the overpayment leaves with a queue that looks clean at the end of the month. Nobody sees it because the evidence has been closed out.
Ownership is the second failure. Price exceptions land with AP because the buyer is not in the system or does not see the queue. The item sits with people who cannot change a purchase order. By the time it reaches someone who can, the due date has gone. Receipts cause the same problem in reverse, with AP chasing a warehouse that has no reason to treat the request as urgent.
Then there is the resolution that is not a resolution. A suspected duplicate gets marked resolved because nobody could find the original, when the check that mattered was against the vendor record for an unpaid invoice or an open credit. A missing receipt is treated as paperwork to chase later and then forgotten. An exception on the invoice is closed but the credit note behind it never reaches the vendor record. Each of these looks like a closed item and each one leaves money on the table.
What to check
Start with age. Pull the open exceptions and sort them by the supplier's due date, not by when they arrived. Anything past due needs a call today, and anything sitting inside a discount window needs a decision before the window shuts. That list is short enough to work through in a morning, and it tells you more than any count of open items.
Then look at overrides. Count how often checks are released rather than satisfied, by person and by vendor. A single approver releasing holds repeatedly is a training or authority problem. A single vendor generating exceptions repeatedly is usually a master data problem, with a stale price on the vendor record or a PO that was never updated, and it will keep producing exceptions until someone fixes the source.
Read the resolution notes on closed items. Each one should say what was actually fixed, not just who released it. For anything flagged as a possible duplicate, confirm someone checked the vendor record for an unpaid original or an open credit before the payment went out. And check who is allowed to release a hold. If the person who raises an exception can also clear it without review, the check is only a formality.
Questions
What is the difference between an invoice exception and an invoice hold?
In most teams they are the same thing. An invoice exception is the mismatch itself, and an invoice hold is the state the invoice is in while the mismatch is open. Some companies use hold for a broader block, such as a vendor on stop for a statement dispute, so check your own policy wording.
Who should resolve an invoice exception?
The owner depends on the cause. A price difference goes to the buyer, a quantity difference goes to the receiver who booked the goods in, and non-PO spend goes to the approver who should have signed it off. AP keeps the queue moving and chases, but AP cannot fix a purchase order it does not own.
Can we pay an invoice exception and fix the purchase order afterwards?
You can, and teams do it when the supplier relationship or a discount is at stake. Treat it as an override with a name and a reason attached, not as a way to clear the queue. If overrides become the normal route, the check is no longer doing anything and overpayments go out unnoticed.
Updated Nov 13, 2026. Figures on this page are calculated by ERPSav from the definitions shown. The explanatory text is drafted with AI from those figures and checked automatically before it is published. General information only, not legal, tax or financial advice.