Billed twice for one delivery
What the user reports
Calder's accounts payable inbox on 2026-12-21. Ridgeline Bearing Supply sent its statement of account RBS-SOA-1218 (dated 2026-12-18), listing RBS-INV-4466 for 100 seal kits, 4,800.00 USD, as open. A clerk keyed it as an invoice on the seal kits' order item; it posted blocked for quantity, and on Friday a colleague clearing the blocked list released it because the amount matched the order price. Tuesday's payment run is tomorrow.
The error: The Payables worklist shows two Ridgeline items of 4,800.00 USD for one delivery of 100 seal kits, both flagged Invoiced more than received, and Tuesday's proposal would pay Ridgeline 9,408.00 USD.
What you'll do
- See the problem as the accounts payable accountant: On Payment proposals, propose a run for CP10 on 2026-12-22 with the next run on 2026-12-29, after checking that every supplier item it would pay is for goods received.
- Find the cause: The seal kits' order item received 100 and Ridgeline has sent one invoice. Why are two Ridgeline items of 4,800.00 USD open on it?
- Fix it as the accounts payable accountant.
- Prove it: run the step that failed again.
The drill runs in the lab on its own prepared copy of the fictional Calder Pumpworks, saved in this browser apart from your company. All codes and values are fictional course labels.
Answer and explanation (open after the drill)
The fix: Ridgeline's statement of account RBS-SOA-1218 was entered as an invoice and released from its quantity block, so 200 are invoiced against 100 received.
Supplier invoices shows RBS-SOA-1218 as Released, with what it was blocked for: "quantity: invoiced 100, received but not yet invoiced 0". A statement lists invoices already sent; it is never an invoice of its own. The duplicate check compares the supplier's number, and RBS-SOA-1218 isn't RBS-INV-4466, so it passed; three-way match caught it with the quantity block, and a release overrode that. The order item received 100 (one receipt), and a cash discount never splits a payable.
Why it broke
A supplier's statement of account was entered as an invoice. The duplicate check didn't stop it (another number); three-way match did, by blocking it for quantity because the order item had nothing left to invoice. Then the block was released on the price alone, and the order item ended up invoiced 200 against 100 received. The payment run pays what is free for payment; it doesn't recount the goods.
How teams prevent it
Reconcile a statement of account against the supplier's open items; never key it as an invoice. Release a quantity block only after checking what the order item received since (a late receipt is the usual good reason), and read the worklist's Invoiced more than received flag before every run.
Across teams
Accounts payable keyed and released it; the buyer sees the seal kits' order as invoiced twice over; treasury's forecast counts 4,704.00 too much going out; and had the run gone first, purchasing would be asking Ridgeline for a refund while its next invoices quietly offset it.
Where AI fits
Predict and assist: a model reading the incoming document classifies it before entry (invoice, credit memo, statement, reminder) and flags a release that leaves an item invoiced above what it received. A person reverses, with a reason; the release stays a person's decision.
Learn more: Procure to pay end to end