AP Exceptions: Why They Happen and How to Clear Them
An AP exception is an invoice that can't be approved or paid automatically because something on it doesn't match or is missing. Most exceptions come from a few upstream causes, and each clears fastest when it goes to the person who owns that cause.
AP teams usually treat the exception queue as their own backlog to work harder at. But AP is where exceptions get noticed, rarely where they start. A price variance starts in purchasing, a missing receipt on the loading dock, and a bad bank account in the vendor master.
Key Takeaways
An AP exception is any invoice that stops short of automatic approval or payment because data is missing, doesn't match, or breaks a rule.
Most exceptions are price and quantity variances, missing or closed POs, missing receipts, duplicates, vendor master mismatches, tax and coding errors, or approval stalls.
AP should own the queue and the clock, while the person who caused each exception owns the fix.
Approval workflow automation matches invoices against POs and receipts within tolerances, passes clean invoices straight to approval, and routes the rest to the right owner with a reason code.
Exception rate, first-pass match rate, exception age, and repeat causes by vendor show whether the queue is shrinking.
What is an AP exception?
An AP exception is an invoice that can't move to the next step without a person stepping in. The invoice may be missing a PO number, may not match the goods received, or may break an approval or payment rule.
An error is something wrong, like a mistyped amount. An exception is the process stopping to ask a question, which is often the right outcome, since a price variance can be legitimate when the PO was stale. Treating every exception as someone's mistake pushes people to work around the controls.
Exceptions can surface at any stage of the accounts payable process, from intake and matching through coding and approval to the final check before payment.
Why do AP exceptions happen?
AP exceptions happen because records that should agree were captured by different people at different times, and each mismatch surfaces when the invoice arrives.
Buyers raise POs at one price and vendors invoice at another because a contract changed. Receiving confirms partial shipments late. Vendor records drift as vendors change banks and remit-to entities, and approvers go on vacation without a delegate. None of that starts in AP, which is why exceptions keep coming back when AP fixes them one invoice at a time.
What are the most common types of AP exceptions?
The most common AP exceptions fall into seven types, and each has a typical cause, fix, and owner.
Exception type | What triggers it | Usual root cause | Fix | Owner of the fix |
Price or quantity variance | Invoice differs from PO or receipt beyond tolerance | Stale PO price, partial shipment, freight or tax not on PO | Correct PO or approve variance; set realistic tolerances | Buyer or requester |
Missing or closed PO | No PO number, wrong number, or PO fully consumed | Off-contract buying, PO closed early | Raise or reopen PO, or route as non-PO with approval | Requester or procurement |
Missing receipt | Goods or services not confirmed received | Receiving lag, services with no receipt step | Confirm receipt or service acceptance | Receiving or requester |
Duplicate invoice | Same vendor, number, amount, or date as a prior invoice | Resent invoice, multiple intake channels | Reject duplicate; confirm with vendor | AP |
Vendor master mismatch | Name, remit-to, tax ID, or bank details don't match the record | Vendor changes, unverified updates, fraud attempts | Verify by callback; update master data | Vendor master team |
Tax or coding error | Missing GL code, wrong cost center, tax rate mismatch | Unclear coding rules, missing W-9 data | Apply coding rules; collect tax documents | AP with the budget owner |
Approval stall | Invoice sits with an approver past the deadline | No delegate, wrong routing, unclear threshold | Escalate, reassign, fix the routing rule | Approver's manager |
Owners shown are typical; set your own in a written exception policy.
What causes price and quantity variances?
Price and quantity variances happen when the invoice, the PO, and the receipt disagree by more than your tolerance allows. The usual causes are stale PO prices, partial deliveries, and charges like freight that were never on the PO.
The fix starts with tolerances. A three-way match set to zero tolerance flags every rounding difference, and the team learns to approve variances without reading them. Use a small percentage or dollar band per line, with a separate rule for freight and tax.
Freight lines are a familiar case. When the PO never includes fuel surcharges, every invoice from that carrier comes in a few dollars over and sits in the queue for weeks, because nobody told AP the tolerance could cover freight. One rule change clears that vendor for good. When the PO price is the problem, the buyer owns the fix.
What happens when a PO is missing or closed?
A missing or closed PO stops an invoice because there's nothing valid to match it against. It usually means someone bought outside the PO process, quoted the wrong number, or the PO was already fully invoiced.
Send these back to the requester, who either raises a retroactive PO under your policy or confirms the purchase for a non-PO approval path. Services are a frequent source, and a defined path for non-PO invoices with service acceptance takes many of them out of the queue entirely. A missing PO is often a habit, so track repeat offenders by department.
Why are receipts missing?
Receipts go missing when goods arrive but nobody records them, or when a service has no natural receiving step, so the invoice can't complete a three-way match.
A warehouse that books receipts at the end of the week will generate an exception for every invoice that arrives first. A receiving report entered on delivery, even a partial one, prevents most of these.
How do duplicate invoices slip through?
Duplicate invoices slip through when the same bill arrives through more than one channel or with a slightly different number, date, or amount. Exact-match checks miss those near-duplicates.
A vendor may resend an unpaid invoice by email and by mail, and each copy can enter AP separately. Good checks compare vendor, normalized invoice number, amount, and date together, then hold near-matches for review, as duplicate payment detection explains in more depth. Run that check at the invoice level, before a payment method is chosen, so the same bill can't go out once by card and again by ACH or check. That matters most when one approval flow pays by several methods, as when Corpay pays suppliers by virtual card, ACH, or check.
What causes vendor master mismatches?
Vendor master mismatches happen when the name, remit-to address, tax ID, or bank details on an invoice don't match the vendor record. Some are honest vendor changes, and some are fraud.
Treat every bank-detail mismatch as a possible attack until verified. According to AFP's 2026 Payments Fraud and Control Survey, 74% of organizations were affected by business email compromise in 2025, and the FBI's 2025 Internet Crime Report puts reported BEC losses at $3,046,598,558. A fake bank-change request often arrives as an invoice exception that someone clears just to get the vendor paid.
The fix is a callback to a known contact on file, never to the number in the email, before any change is saved. Vendor bank-account validation can automate part of that check, and Nacha's fraud-monitoring rule amendments, phased in on March 20 and June 22, 2026, give ACH payers another reason to formalize it.
Protect cash flow with modern AP
Modernize AP to cut costs, speed approvals, and mitigate payment risk — gaining the real-time visibility to protect cash flow and scale with confidence.
Download the whitepaper
Where do tax and coding errors come from?
Tax and coding errors come from invoices without a valid GL code, cost center, or tax treatment, or from vendors with incomplete tax records. They're often slow to clear because the answer sits with a budget owner.
Clear invoice coding rules and default codes by vendor or PO line remove most of them. Tax ID problems need a different fix. The IRS says a payer may have to withhold at the backup withholding rate of 24 percent when a payee's taxpayer identification number is missing or incorrect, so a missing W-9 carries a real cash cost. Running TIN matching when you onboard a vendor stops these exceptions before the first invoice.
Why do invoices stall in approval?
Invoices stall in approval when the assigned approver doesn't act, usually because they're away, overloaded, or the invoice was routed to the wrong person. A stall is an exception even though nothing on the invoice is wrong.
Most stalls are a routing problem that delegates, escalation dates, and realistic thresholds prevent. If one approver accounts for a large share of stalls, the routing rule probably needs to change.
Who should own the AP exception queue?
AP should own the exception queue and its clock, while the person who caused each exception owns the fix. AP's job is to classify, route, chase, and close each item.
Most teams don't run that split. AP clerks end up correcting POs and chasing warehouses themselves because it's faster this week. It's slower every week after, because the upstream cause never learns it caused anything. Write the ownership into an exception policy, give every exception a reason code, and report exceptions by owner each month.
What SLA should exceptions run on?
Most exceptions should clear within three to five business days, with tighter clocks for anything that threatens a discount or a due date. Set the SLA by type.
Exception type | Suggested SLA | Escalate to |
Duplicate invoice | Same day | AP supervisor |
Vendor bank or remit-to change | Hold until verified by callback | Controller |
Price or quantity variance | 3 business days | Buyer's manager |
Missing or closed PO | 3 business days | Department head |
Missing receipt | 2 business days | Receiving lead |
Tax or coding error | 5 business days | Budget owner |
Approval stall | 2 business days past due | Approver's manager |
Starting points to adjust to your payment terms and discount programs. A bank-detail change stays on hold until verified, however loud the vendor gets.
How does invoice approval workflow automation handle exceptions?
Invoice approval workflow automation checks each invoice against the vendor record, the PO, and the receipt as it arrives. Clean invoices go straight to approval, and anything that fails a rule goes to the person who can fix it, tagged with the reason.
The sequence looks like this in most systems.
Capture. The system reads the invoice from email, a portal, or EDI.
Validate. It checks the vendor's tax ID, remit-to, and bank details against the master record.
Match. It compares invoice lines to the PO and receipt within your tolerances.
Route clean invoices. Passing invoices go to the approver your rules name, or post directly against a pre-approved PO.
Route exceptions. Failed invoices go to the owner for that type, with a reason code and the conflicting data side by side.
Escalate. Aging rules notify the next person when an SLA is missed.
Check before payment. A final duplicate and bank-detail check runs before the payment run.
Matching only works if PO and receipt data arrive without re-keying. Corpay's AP automation connects to more than 100 ERPs, including NetSuite, Sage Intacct, Business Central, and Acumatica, so open POs and receipts are available at the moment an invoice is matched. Thresholds and approval matrices belong to invoice approval workflow design. Every routing decision and override should land in an AP audit trail so you can show an auditor who cleared what and why.
What can automation clear without a person?
Automation can clear any exception a rule can decide, such as variances within tolerance, exact duplicates, and receipts that arrive after the invoice.
Automation can't decide whether a vendor's new bank account is real or whether a price increase was agreed. Those need a person with the evidence attached. The more invoices that pass untouched, the closer you get to touchless invoice processing, and the more attention the hard cases get.
How do you know your exception process is working?
Your exception process is working when the exception rate falls, items clear inside their SLA, and the same causes stop repeating. Track these monthly.
Exception rate. Invoices that needed manual handling divided by total invoices received.
First-pass match rate. PO invoices that matched without intervention divided by all PO invoices.
Average and oldest exception age by type, since the oldest item tells you more than the average.
Exceptions by reason code and owner, which shows where the upstream fixes belong.
Repeat-exception vendors, the short list of vendors that generate most of your holds.
Late payments caused by holds, the exceptions that cost money or vendor goodwill.
Published averages for exception rates vary widely by survey and definition, so benchmark against your own last quarter. Payment errors at scale are expensive. US federal agencies alone estimated about $186 billion in improper payments across 64 programs in fiscal 2025, according to GAO's report on payment integrity. Read these next to wider AP KPIs such as cost per invoice.
How should you judge exception handling in AP software?
Judge AP software on how well it prevents exceptions and routes the rest. A tool that only gives AP a nicer queue leaves the causes upstream.
Ask vendors to show these on your own invoices.
Tolerances set per vendor, line, and charge type, including freight and tax
PO and receipt data synced from your ERP, with no re-keying
Reason codes and routing to the owner of each exception type
Aging alerts and escalation tied to your SLAs
Duplicate checks that catch near-matches as well as exact ones
Vendor bank-change verification built into the workflow
Invoice matching software evaluations often stop at match rates. I'd weight routing and vendor verification higher, because they decide whether an exception gets fixed at the source or quietly approved to make it go away.
Clear exceptions faster with Corpay AP automation
Exceptions cost AP time and open the door to fraud. According to AFP's 2026 Payments Fraud and Control Survey, 76% of US organizations experienced attempted or actual payments fraud in 2025.
Corpay AP automation captures and matches invoices against your ERP's POs and receipts, routes exceptions to the right owner, and checks for duplicates before anything is paid. With fully managed AP, Corpay pays each vendor by virtual card, ACH, or check from one approval flow, and AP teams save about 40% of the time they spend on processing. Corpay connects to NetSuite, Sage Intacct, Business Central, Acumatica, and other ERPs, and most customers are live in weeks.
Frequently Asked Questions
What is an exception in accounts payable?
An exception in accounts payable is an invoice that can't be approved or paid automatically. Something is missing, doesn't match the PO or receipt, or breaks a rule, so a person has to review it before it can move forward.
What causes invoice exceptions?
Invoice exceptions come from mismatched data across purchasing, receiving, vendors, and AP. Common causes are stale PO prices, late receipts, invoices without POs, duplicate submissions, outdated vendor records, missing GL codes, and approvers who don't act on time.
Who should resolve AP exceptions?
AP should own the exception queue and track every item, but the person who caused the exception should fix it. Buyers fix PO prices, receiving confirms deliveries, the vendor master team verifies vendor changes, and budget owners settle coding questions.
How long should it take to clear an invoice exception?
Most invoice exceptions should clear within three to five business days. Duplicates can clear the same day, while a vendor bank-detail change should stay on hold until it's verified by a callback to a known contact.
What is a good AP exception rate?
A good AP exception rate is one that falls quarter over quarter. Published averages vary widely by survey and definition, so measure invoices needing manual handling against total invoices, then track the trend by reason code and vendor.
How does invoice approval workflow automation work?
Invoice approval workflow automation captures each invoice and validates the vendor, then matches lines to the PO and receipt within set tolerances. Clean invoices route to the right approver, while exceptions go to their owner with a reason code and escalate when an SLA is missed.
Switch to Corpay
Discover how making the move to Corpay streamlines payments and strengthens your business.
Talk to an ExpertSmarter payments. Stronger growth. Keep business moving.
Corpay powers payments for 800,000+ businesses worldwide. Let’s build what’s next for yours.