Invoice exception handling that fixes the cause once and releases every blocked invoice before the supplier hold
Blocked invoices released before late fees and supplier holds, every fix checked twice.
See one case, screen by screen ↓Invoice Exception Management is invoice exception handling by root cause. Seven AI agents read the blocked invoices from your ERP, group them by the cause they share, trace each cause to the contract, PO or receipt behind it and propose one fix for every invoice that shares it. A separate checker re-runs the three-way match, and anything over tolerance is released only after a named approver signs with a reason code.
How to choose AI solutions for back-office and enterprise work →
Updated
The ERP blocks an invoice when the invoice, the PO and the goods receipt disagree beyond tolerance, and one bad line blocks the whole invoice. An AP specialist then opens each blocked invoice on its own, from a worklist sorted by supplier or date, and compares the invoice line with the PO line and the receipt across two or three screens and the PDF. When fourteen invoices block for the same reason — a contract price rise that never reached the PO, a dock scanner that was down, a blanket PO that ran out — the same cause is worked fourteen times, and the same email goes to the buyer fourteen times.
Meanwhile the money keeps moving against you: late charges under each entity's law or contract, early-payment discounts that expire, and, worst, a supplier's letter that stops deliveries. When someone finally releases the block by hand, the PO is often still wrong, so the next delivery blocks again, and the override log shows who released it but not whether the cause was ever fixed. That is the evidence an auditor tests on the three-way match.
Estimated split, in days, for a blocked invoice worked by hand at a shared-services AP hub, and with the solution.
Seven agents find each block's root cause, propose one fix, check it independently and carry it out; a named approver signs anything over tolerance.
Wednesday 14 October, 09:40, at Kestrel & Vane's AP hub in Dayton, which serves five entities. 137 invoices are blocked. Fourteen of them come from Halvorsen Fasteners, and Halvorsen stops deliveries on Monday. Here is how Priya Raman, the AP lead, works it with the agents, screen by screen, in the working solution.
Priya's home is a short briefing the agents wrote between 07:00 and 09:40: 137 invoices blocked across five entities, $1,248,658.82, in 11 shared causes and 26 one-offs, and 4 decisions that need her today. The first card is from the resolver and the exposure watcher: 14 Halvorsen invoices are blocked for one reason, and Halvorsen stops deliveries on Monday. Each card carries its sources, its status and one next step.
“4 decisions need you today; the rest are moving.”
In the box at the foot of the briefing Priya asks: “Why are 14 Halvorsen invoices blocked?” The answer comes back with its sources: amendment 3 to price agreement PA-7720 raised three fastener prices by 3.2% from 2 Sep, and PO 4500118842 still carries the prices of 12 Aug, so all 14 lines are 3.2% over — $8,412.60 in all. One button walks her through it.
“The PO is out of date, not the invoices.”
The cause opens as five steps: what the agents found, the evidence, the fix they propose, the independent check and her decision. The cause finder is 96% sure the PO is wrong, not the invoice. The exposure watcher adds Halvorsen's letter of 9 Oct: deliveries stop if more than $100,000 is overdue on 19 Oct. Six invoices are overdue, $122,317.80, and late charges reach $1,168.93 by Sat 24 Oct.
“That is why this comes first.”
Three items changed price on 2 Sep. The hex flange bolt HF-M12-40 is $31.25 per 100 on the PO and $32.25 on the contract and the invoice; the M10 nut HF-N10-ZN $43.75 against $45.15; the M16 bolt HF-M16-60 $118.75 against $122.55. The PO has had no price change since 19 Aug, every receipt equals the invoiced quantity, and 3.2% is over the 2.0% and $150 a line tolerance, so the invoices stay blocked.
Every figure carries a mark; click it to read the source.
Priya opens the mark on the contract price. Price agreement PA-7720, amendment 3, signed 28 Aug and effective 2 Sep 2026, page 2, clause 4.1: the Schedule A prices are replaced to reflect the zinc-nickel coating and wire-rod surcharge, with the three new prices highlighted. The clause also shows who signed for Kestrel & Vane Motion Systems: Daniel Okafor, the buyer.
The resolver recommends asking the buyer to amend the PO price, for all 14 invoices. It ruled out a credit note — the contract allows the price billed, so Halvorsen would refuse — and accepting within tolerance, because 3.2% is over 2.0% and the PO would stay wrong for future deliveries. Priya asks the agents “Why not ask Halvorsen for a credit note?” and gets the reason with its sources. The outreach agent's note to Daniel Okafor is drafted, editable, and goes only when she approves.
“This goes to Daniel Okafor, with the PO change prepared, only when you approve.”
The checker is a separate agent from the resolver. It re-ran the three-way match from the ERP lines, never from the resolver's notes, against the policy tolerance: 14 of 14 lines match after the fix. Priya can open the line-by-line result or run the checker again.
“I am a separate agent from the resolver.”
The variance, $8,412.60, is inside her $25,000 limit; anything over it would go to Henrik Aalto, the group controller. She sees what happens if she approves, then signs with reason code PC-02 · PO corrected to the contract price, a note for the record, and a tick that she has seen the evidence and the checker's re-match (14 of 14). She could also send it back, reject it with a reason or reassign it.
“Over tolerance: a named approver must sign.”
The outreach agent sends Daniel the prepared change. He posts PO 4500118842 version 4 at 09:51 under his own name, and the checker re-matches 14 of 14 on the posted PO. Only then does the block reader release the 14 invoices, $271,306.35, to the payment run on Thu 15 Oct. Halvorsen's overdue falls to $0 on Thursday, so the hold of 19 Oct is avoided.
“14 invoices released · $271,306.35 to Thursday’s payment run”
Each action, by a person or an agent, is on the audit trail with its evidence and a chained record id: Priya's signature with PC-02, the note sent to Daniel, the posted PO version 4, the checker's re-match, the release. The prevention reporter closes the loop: contract price changes that never reach open POs blocked 41 invoices in 12 weeks, so it proposes sending each signed amendment to the open POs it covers, for the buyer to confirm.
“Every action by a person or an agent, with its evidence, chained so it cannot be changed.”
The same blocked invoices, seen by the five people who clear them — what their week looked like, and what it looks like now.
Seven agents find each block's root cause, propose one fix, check it independently and carry it out; a named approver signs anything over tolerance.
Pulls every blocked invoice from the ERP every 30 minutes with its PO, receipts and PDF, and posts the release after a signed decision and the checker's re-match on the posted data.
Groups blocked invoices by the cause they share and traces it to the event behind it — a contract amendment, a scanner outage ticket, a used-up blanket PO — with its sources and confidence.
Weighs the fixes for each cause and proposes one for every invoice that shares it, with why it ruled out the others.
Re-runs the three-way match on each proposed fix, from the ERP data, before anything moves — and again on the posted PO or receipt.
Drafts and sends the requests to buyers, receivers and suppliers with the change prepared, chases on the service level and reads the replies and credit notes.
Works out late charges under each entity's rule, early-payment discounts that run out and supplier holds for the next 10 days, and suggests the order to release in.
Finds causes that keep coming back over 12 weeks, names the process owner and the fix at the source, then measures it.
Sign over tolerance; buyers and receivers post their own changes. The agents propose; a named person decides.
On every screen there is a box to ask about what is in front of you. Every answer points to its source, and some offer the next step.
What needs me first?
Halvorsen. Six of its 14 invoices are overdue, $122,317.80, and Halvorsen stops deliveries on Mon 19 Oct if more than $100,000 is still overdue. The fix is ready and the checker re-matched 14 of 14. Then Northmere (Wed 21 Oct), then the Ashcombe, Pellworth and Quillon batches.
Why are 14 Halvorsen invoices blocked?
The PO is out of date, not the invoices. Amendment 3 to price agreement PA-7720 raised three fastener prices by 3.2% from 2 Sep. PO 4500118842 still carries the prices of 12 Aug, so all 14 lines are 3.2% over: $8,412.60 in all.
Why not ask Halvorsen for a credit note?
Because Halvorsen billed what the contract says. Amendment 3 sets $32.25, $45.15 and $122.55 per 100 from 2 Sep, exactly the invoiced prices. A credit-note request would be refused and would push payment past Monday's hold. The PO is the record that is wrong.
What do we lose in 10 days if nothing moves?
$5,257.20, and two supplier holds. $2,671.08 of late charges under each entity's rule and $2,586.12 of early-payment discounts that run out. Halvorsen stops deliveries on Mon 19 Oct, and Northmere stops booking loads on Wed 21 Oct.
13 screens from the working solution, on its sample data. Pick one to see it large.
The rules the agents work to are settings. Every change is a new version, and tolerance or authority changes need the group controller.
| Setting | Default | Choose from |
|---|---|---|
| Price tolerance | 2.0% and $150 a line (group policy 4.3) | Rows per entity or supplier group; an ERP setting stricter than policy is flagged |
| Quantity tolerance | 0% for goods; services need a confirmed service receipt | Per entity overrides, such as 0.5% for bulk chemicals |
| Release a clean three-way match by rule | On | On · Off |
| Apply one fix to every invoice that shares the cause | On | On · Off — each invoice is still re-matched |
| Over tolerance, the checker's agreement, and a person before any supplier message | Always | Fixed by policy 4.3 |
| Who signs what | AP lead up to $25,000 variance a batch; group controller above it and for PC-07 | AP specialist · AP lead · group controller, with delegation that never exceeds the delegator's limit |
| Service levels for requests | Buyer 24 h · receiving 8 h · requester 48 h · supplier 48 h | Reminders and escalation to the manager, site logistics lead, budget owner or buyer |
| Late-payment rules by entity | EU: reference rate + 8 points and €40 · UK: base rate + 8 points and £40 / £70 / £100 | EU Directive 2011/7/EU · UK 1998 Act and 2013 rules · supplier contract |
Every figure is labelled: a target the solution is built to, an estimate, a typical published result, or a proven one.
“demo” = seen in the working solution, on its sample AP data · “target” = the design goal, measured in the live solution · “estimated” = our estimate · “typical” = published figures (Ardent Partners, AP Metrics That Matter 2025, as reported in published summaries — exception rate 9% best-in-class, 14–22% average, processing time 9.2 days against 3.1; Ardent Partners, The State of ePayables 2025, as reported in a published summary — 48% name high invoice exceptions a key barrier) · Late-payment context: EU Directive 2011/7/EU; UK Late Payment of Commercial Debts (Interest) Act 1998 and 2013 Regulations. Kestrel & Vane Group, its suppliers and the people named on this page are fictional — characters and sample data in the working solution.
Invoice Exception Management is invoice exception handling by root cause. Seven AI agents read the blocked invoices from your ERP, group them by the cause they share, trace each cause to the contract, PO or receipt behind it and propose one fix for every invoice that shares it. A separate checker re-runs the three-way match, and anything over tolerance is released only after a named approver signs with a reason code.
The cause finder traces each price or quantity variance to the event behind it, such as a contract amendment that never reached the PO, receipts not posted while a dock scanner was down, or a blanket PO that ran out. The resolver weighs the fixes and says why it ruled out the others, and the checker re-matches every line from the ERP data before anything moves.
No. Inside tolerance a clean match can be released by rule. Over tolerance, a named person always decides, with a reason code: the AP lead up to $25,000 of variance a batch, and the group controller above that or for an over-tolerance acceptance for a business reason.
The exposure watcher works out late charges under each entity's rule or contract, early-payment discounts that run out and supplier stop letters for the next 10 days, and suggests releasing supplier holds first, then penalties. In the working solution it flagged Halvorsen's hold of 19 Oct, and the 14 invoices were released to the payment run before it.
No. The agents prepare the change — the PO amendment, or the receipts with the counted quantities read from signed delivery notes — and the buyer or receiving clerk posts it under their own name. The checker then re-matches on the posted data before the release.
Yes. People approve, edit, send back or reject every fix that needs a signature, nobody signs a batch they prepared, and nothing goes to a supplier until a person presses Send. Every action, by a person or an agent, is on a chained audit trail with its evidence.
The prevention reporter counts causes over 12 weeks, names the process owner and proposes the fix at the source. In the working solution, contract price changes that never reached open POs blocked 41 invoices in 12 weeks, so it proposed sending each signed amendment to the open POs it covers, for the buyer to confirm.
The Agentic Solution Engine builds and deploys it from your requirements and documents — your matching policy, approval limits, supplier terms and a sample of past blocked invoices — and it goes live once every quality gate has passed. A new entity can be trialled on 30 days of past blocks before it goes live.
Every bank change proven by a call-back before a single dollar moves.
1-min demoExpense Report AuditEvery report checked, not a sample, and no forged receipt paid without proof of payment.
1-min demoDuplicate Payment Detection & Recovery AuditTwins stopped before the payment run, paid ones recovered in house, every claim signed.
1-min demoWe'll run Invoice Exception Management on a sample of your own blocked invoices, POs and receipts.