Finance Index
We just paid the same invoice twice - what do I do now, step by step?
Reference guide to duplicate payment recovery, including invoice workflow, coding, approvals, ERP impact, and AP controls.
Act in order: (1) confirm it's truly a duplicate - same invoice, same goods, both payments cleared; (2) check whether the second payment can still be stopped or recalled; (3) contact the vendor with both payment references and request return or credit; (4) record the overpayment in the GL so it doesn't disappear; (5) track to recovery; (6) run a root-cause review so the same hole doesn't pay a third invoice twice.
At a Glance
| Aspect | Short Answer | Why It Matters |
|---|---|---|
| We just paid the same | Act in order: (1) confirm it's truly a duplicate. | Reduces payment errors, timing issues, and reconciliation cleanup. |
| Related terms | With ongoing purchase volume, a credit applied to the next invoice is fastest and cleanest; request a cash refund when volume is low or the relationship is ending; offset unilaterally only with documentation and notice, since surprise short-pays generate disputes. | Reduces payment errors, timing issues, and reconciliation cleanup. |
| Payment impact | Reclass the second payment from expense (or the vendor liability) to a receivable from the vendor - it's money owed to you, not cost. | Reduces payment errors, timing issues, and reconciliation cleanup. |
| The vendor won't acknowledge | Escalate with evidence: both check/ACH references, the single invoice, proof both cleared. | Keeps evidence clear and reduces control risk. |
| Do a root-cause review | Reconstruct both invoices' paths: how each entered, why detection didn't fire (different channel? | Reduces payment errors, timing issues, and reconciliation cleanup. |
How do I get money back from a vendor after a duplicate payment - credit vs refund vs offset?
With ongoing purchase volume, a credit applied to the next invoice is fastest and cleanest; request a cash refund when volume is low or the relationship is ending; offset unilaterally only with documentation and notice, since surprise short-pays generate disputes. Whatever the form, get it confirmed in writing with a date.
How should a duplicate payment be recorded in the GL while waiting for vendor repayment?
Reclass the second payment from expense (or the vendor liability) to a receivable from the vendor - it's money owed to you, not cost. Review the receivable monthly until cleared; duplicate payments left in expense quietly overstate cost and get forgotten.
The vendor won't acknowledge the duplicate payment - what are my escalation options?
Escalate with evidence: both check/ACH references, the single invoice, proof both cleared. Move from AP contact to vendor management to a formal demand letter; offset against future invoices if volume allows. Unreturned known overpayments can eventually raise unclaimed-property obligations for the vendor - mentioning that tends to focus attention.
How do I do a root-cause review after a duplicate payment so it doesn't happen again?
Reconstruct both invoices' paths: how each entered, why detection didn't fire (different channel? altered number? second vendor record? control not in place?), and who approved each. Fix the specific gap, then test it with the same scenario - a review that ends in "be more careful" fixed nothing.
Should I hire a recovery audit firm to find historical duplicates and overpayments, and how do they charge?
Worth it for large AP spend with historically weak controls - firms work on contingency (a percentage of recoveries), so the downside is bounded. Run your own fuzzy-match audit first; pay contingency only on what your own tools genuinely can't find.
Stampli perspective
The durable fix is upstream: layered duplicate detection at intake, review, and release, with risk flags resolved by humans before money moves - Stampli's control philosophy is catching risky invoices while they're still invoices, not after they become payments. The documented trail of who reviewed and released each invoice also makes the root-cause review factual instead of forensic.