Paying the same invoice twice is one of those mistakes everyone assumes happens to someone else. In a small finance team it happens for dull reasons. A supplier chases a payment and resends the bill. Someone enters it again because they could not find the first one. The payment run goes out on a Friday afternoon and nobody has time to look at every line.
Most of the guidance on this topic comes from software vendors writing for larger companies, and it tends to start with three-way matching against purchase orders and receipts. That is a good control, but plenty of small and mid-sized businesses do not raise a purchase order for every bill, so it does not help them. This post is about the version of the problem those businesses actually have, and what can be done about it without adding a heavy process.
Where duplicates actually come from
The most common source is the supplier resending an invoice. A vendor sends a bill, hears nothing for a week, and sends it again with “second reminder” in the subject line. If the first copy is sitting in someone’s inbox or chat history and the second lands in a different one, two people can each do the right thing and still create two bills.
The second source is one invoice arriving through more than one channel. A supplier might send a blurry photo over WhatsApp, then email a clean PDF the next morning. Both are the same invoice, but they show up in different places, often to different people, and nothing connects them. If you accept invoices from several channels, a duplicate check has to look across all of them, not inside each one.
The third source is small differences in how the same invoice is recorded. One entry has the invoice number as INV-0042, another as INV 42, another as 0042. One has the supplier as “Al Noor Trading” and another as “Al Noor Trading LLC”. A basic duplicate warning in an accounting system generally looks for an exact match on supplier and invoice number, so any of these variations can slip past it. It is worth checking how your own system behaves here, because the rules differ between products.
The fourth source is documents that are not invoices being treated as invoices. Supplier statements, pro forma invoices, delivery notes, and reminder letters often carry the same amount as a real invoice. If someone keys one of those in as a bill, it looks like a legitimate payable and will eventually be paid on top of the real one.
Finally, there is the reissued invoice. A supplier corrects an error, cancels the original, and sends a replacement with a new number. If the credit note for the cancelled one never arrives, or arrives and is never applied, the original stays open next to the new one.
Why the problem grows with volume and mixed inputs
Ardent Partners’ State of ePayables 2025 report puts the exception rate, the share of invoices that need some kind of manual intervention, at 20.9% for the group it calls All Others, against 11.1% for Best-in-Class organizations. The same report shows a touchless processing rate of 29.0% for All Others and 51.0% for Best-in-Class. The report does not measure duplicate payments directly, so this is context and not a duplicate rate. But it makes a fair point about where duplicates tend to hide: in the invoices that get handled by hand, re-keyed, or set aside while someone finds a missing detail. The more of your invoices need that kind of handling, the more chances there are for the same document to be entered twice.
Checks that work without a purchase order process
Duplicate prevention is mostly about deciding what counts as “the same invoice” and then checking that consistently. A few checks cover most of the risk.
Compare invoices on more than the invoice number. Supplier, amount, and invoice date together are a much better test than the number alone, because a resent invoice will keep the same amount and date even when someone mistypes the reference. A rule that flags “same supplier, same amount, dates within a few days” will catch the entries an exact-number check misses. It will also flag some legitimate repeat charges, such as a monthly subscription, so the point is to prompt a person to look, not to block automatically.
Clean the invoice number before comparing it. Removing spaces, dashes, and leading zeros, and ignoring capitalisation, turns INV-0042, INV 42, and 0042 into the same string. Whether you do this in a spreadsheet, in your accounting system’s settings, or with a tool that does it for you, the goal is the same.
Keep one list of suppliers. Duplicate supplier records are a quiet cause of duplicate payments, because the invoice history is split across two records and neither shows the whole picture. A periodic tidy-up of the supplier list, merging obvious duplicates, pays for itself.
Decide in advance what happens to “urgent” and “second reminder” invoices. These are the ones most likely to be a resend. A simple rule works well here: a reminder never gets entered as a new bill. Whoever receives it first checks whether the original is already in the system and replies to the supplier with its status.
Look at the payment run before it is released. Sorting the batch by supplier and scanning for the same name appearing twice takes a couple of minutes and catches a surprising amount. It is also the last chance to stop a payment before it leaves the bank.
Reconcile supplier statements now and then. Asking your larger or more frequent suppliers for a statement and comparing it with what you have recorded shows both what you might have missed and what you might have paid twice.
Compare the bank account to the open bills on a regular schedule, weekly if you can. If a supplier appears twice in the bank feed for the same amount, you will see it within days instead of at year end.
What to do when one gets through
It will happen occasionally even with good checks. The quickest fix is usually to ask the supplier for a credit note against the overpayment and offset it on the next invoice, which avoids a refund transfer and keeps the supplier ledger tidy. If the supplier will not have further invoices soon, ask for a refund and record it against the original payment so the two entries stay linked. Either way, write down how it happened. Nearly every duplicate points to a specific gap, a channel nobody watches or a reminder that was treated as a new bill, and that note is what lets you close the gap.
Where automation helps and where it does not
Software can do the repetitive part well: normalising invoice numbers, comparing supplier, amount, and date across every channel at once, and flagging a probable match before a bill is created. That takes pressure off the person entering invoices, who otherwise has to remember what came in last week. It does not replace judgement on the borderline cases. A person still has to decide whether two similar invoices are a resend or two real charges.
Clearline reads invoices from WhatsApp, email, or upload without templates and posts approved bills into the accounting system you already run, so duplicate checks can happen at the point where the invoice comes in, before it becomes a bill and long before it reaches a payment run. If your process is small and all invoices arrive in one inbox, a spreadsheet log and the habits above may be enough. If invoices arrive from several places and the volume is climbing, checks that look across every channel start to matter more.
For related reading, our post on invoice fraud and bank detail warning signs covers the deliberate side of paying the wrong thing, and what accounts payable actually costs explains why manual handling gets more expensive as volume grows.