The Same Invoice Paid Twice Rarely Looks Like a Duplicate

An exact duplicate is easy to catch: same vendor, same invoice number, same amount, same date. The payments that actually drain a business rarely match that neatly. One copy arrives as invoice 10482 and the other as 010482. A hyphen moves, a vendor name is abbreviated, or the second payment covers the invoice minus a small credit, so every field looks close but none looks identical. Standard duplicate checks built on exact matches wave both payments through.

The vendor master file is usually where the second copy is born. When the same supplier exists twice — once under a full legal name and once under a short trading name, with different vendor IDs — an invoice can be entered against each record and paid twice without any single screen ever showing a conflict. The same pattern hides unapplied credit memos: a credit sits on one vendor record while the full invoice is paid on the other, and the refund the business was owed quietly ages away.

A second route in is the payment rail itself. An urgent invoice gets settled on a company card to keep a supplier relationship intact, then the original paperwork continues through accounts payable and is paid again by bank transfer weeks later. Neither payment is wrong on its own; together they are one purchase paid for twice, and reconciling card statements against the AP ledger line by line is exactly the manual work busy finance teams postpone.

That is why duplicate detection has to be rules-based and fuzzy, not a single exact-match report. ERPSav, a product of CloudVerg, runs 15 rules-based recovery engines across nine leak categories — duplicate supplier payments, lease overcharges, utility and telecom billing errors, padded card processing fees, denied warranty claims, parcel and freight overcharges, SaaS spend waste, chargebacks, and sales tax overcharges — for businesses in the US, Canada, the UK, Ireland, Australia, and New Zealand. The 14-day free trial includes every module and requires no card.