Orchestrate

The same invoice twice

Break-fix drill · Finance · about 6 minutes · starts after stage 11 of 11, "Pay and close the month", and the Pay the suppliers chapter up to "Enter the four invoices with their dates" (20 impellers from Tamsfield received on one order, Orrin's, Tamsfield's first and Ridgeline's invoices posted)

What the user reports

Calder's accounts payable inbox on 2026-12-21. Last week a letter from Tamsfield Foundry reminded Calder of TF-INV-2248, with a copy of the invoice stapled to it; the copy's header prints only "Invoice No. 2248", and the clerk keyed it as a new invoice. Today Tamsfield's second invoice, TF-INV-2263 for the other 10 impellers (3,350.00 USD, dated 2026-12-04), arrives, a day before Tuesday's payment run.

The error: TF-INV-2263 would post blocked for payment: "quantity: invoiced 10, received but not yet invoiced 0", although the order received 20 impellers and Tamsfield has sent only two invoices.

What you'll do

  1. See the problem as the accounts payable accountant: On Supplier invoices, post Tamsfield's TF-INV-2263 for 10 × CP-IMP200 at 3,350.00 USD, invoice date 2026-12-04, on the order item that received the 20 impellers.
  2. Find the cause: The order received 20 impellers and Tamsfield has sent two invoices of 10. Why is there nothing left to invoice?
  3. Fix it as the accounts payable accountant.
  4. Prove it: run the step that failed again.

Start the drill

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: Tamsfield's first invoice is in the books twice: once as TF-INV-2248 and once, from the reminder's copy, as 2248. The duplicate check compares the supplier's number, and 2248 isn't TF-INV-2248.

Supplier invoices lists three invoices on Tamsfield's order item: TF-INV-2248 and 2248, both for 10 impellers at 3,350.00 USD dated 2026-11-12. Same supplier, same date, same amount, same quantity, different number: one invoice entered twice. The check refuses the same number twice; it can't know that 2248 is the short form of TF-INV-2248. The receipt is for 20, no run has paid anything yet, and tolerances only judge the price.

Why it broke

A copy of an invoice was entered as a new invoice under a shorter number. The order still had 10 impellers received and not invoiced, so three-way match passed it: quantity, price and terms were all right. The duplicate check compares the supplier's number, and the copy's number wasn't the original's. The real second invoice then found nothing left to invoice.

How teams prevent it

Key the supplier's number exactly as on the original (Tamsfield's numbers start TF-INV-), never from a reminder's copy, and stamp copies and reminders as such before they reach data entry. Before a run, look for invoices from one supplier with the same date and amount: a duplicate looks like the original in everything but its number.

Across teams

Accounts payable keyed it; the buyer sees the impeller order as fully invoiced; treasury's cash forecast counts 3,350.00 too much going out; and had the run gone first, Tamsfield would have been paid twice and purchasing would be chasing a refund from a supplier it relies on.

Where AI fits

Predict and assist: a model scores each new invoice against the supplier's recent ones (same date, amount, order item, a number that contains another's) and flags likely duplicates before posting. Accounts payable decides; the reversal is a person's, with a reason.

Learn more: Procure to pay end to end

All drills · Back to the lab

Sign in to track your progress

We'll email you a one-time sign-in link. No password needed.

or

Tell us a little about you

Optional, every field. It helps us pitch answers to your questions at the right level and decide which topics to write next. It is never shown publicly, and you can change or clear it anytime from the account menu.

SAP areas you work in