Duplicate Invoice Checker

How duplicate invoices happen in accounts payable

Duplicate invoices are the most common source of overpayment in accounts payable, and they rarely happen because someone is trying to commit fraud. The typical causes are far more mundane. A supplier emails an invoice and also posts a hard copy. The accounts team enters both. Or a supplier resends an invoice because they did not receive payment confirmation, and the second copy gets treated as a new invoice.

In larger teams, different staff members may enter the same invoice independently. This is especially common when invoices arrive through multiple channels: email, supplier portal, and post. OCR systems can compound the problem by capturing the same scanned document twice if someone re-uploads it or if the document sits in two folders. Corrected invoices create another risk. A supplier issues a revised invoice with a new number but the same amount, without formally cancelling the original. Both end up in the approval queue.

The result is straightforward: you pay the same bill twice. Recovery is possible but slow. Most suppliers will issue a credit note, but chasing it takes time your AP team does not have. The better approach is to catch duplicates before approval, not after payment. That is what this tool helps you do, and it is what a well-designed AP controls stack prevents at scale.

Worked example: catching duplicates in a distribution business

A Melbourne wholesale distributor processes around 400 invoices per month across 60 suppliers. Their AP clerk noticed that a steel supplier had been paid twice for the same delivery. Running the month's invoices through this duplicate checker surfaced the issue immediately.

The tool flagged rows 1 and 3 as high-risk: same vendor (Pacific Steel), same amount ($3,847.20), invoice numbers differing by only the "-R" suffix, and dates just 2 days apart. Without the check, that $3,847 would have been paid twice. The supplier had resent the invoice with a revised number after not receiving payment confirmation. One delivery, two invoices, one near-miss.

Common duplicate invoice patterns

Duplicates follow predictable patterns. Knowing what to look for makes prevention easier.

• Same invoice number, same vendor. The most obvious duplicate. Usually caused by the same document being entered twice from different channels (email and post, or two team members processing the same email).
• Same amount, same vendor, different invoice number. Happens when a supplier reissues an invoice with a new number. Common after payment disputes or when the original invoice had a minor error and the supplier sent a corrected version without cancelling the first.
• Same amount, similar vendor name. The vendor was entered as "Smith Bros" in one record and "Smith Brothers" in another. Both are the same supplier, but the system treats them as different vendors. This is a vendor master data quality issue. Using a standardised supplier onboarding process reduces this risk.
• Sequential invoice numbers with the same amount. Two invoices from the same vendor with consecutive numbers and identical amounts can indicate a data entry error where someone keyed the wrong invoice number, or it can be two genuine invoices for recurring services. Either way, it warrants a check.
• Same invoice across different entities. In multi-entity businesses, the same supplier invoice can be entered against two different entities if there is no cross-entity duplicate check. This is harder to catch without centralised AP processing.

Building a duplicate detection process

Check before approval, not after payment. That single principle eliminates most duplicate payment risk. Every invoice should be screened against existing records before it enters the approval workflow. If your current process only catches duplicates during the monthly bank reconciliation, you are finding them too late.

Set tolerance thresholds that match your business. An exact match on invoice number and vendor is a clear duplicate. But what about invoices with the same amount from the same vendor, 10 days apart? That might be a duplicate, or it might be a genuine recurring charge. A reasonable starting point: flag any same-vendor, same-amount invoices within 14 days of each other, and any invoice numbers within 1 character of an existing record. Adjust based on your false positive rate.

Manual checks work at low volumes. Above 200 invoices per month, the error rate on manual duplicate checking rises sharply. That is the point where automated fraud prevention pays for itself. Pulsify runs duplicate detection on every incoming invoice in real time, comparing against your full invoice history using fuzzy matching on vendor names, amounts, dates, and invoice numbers. Flagged invoices are held for review before they reach an approver. Read more about implementing duplicate detection workflows in our detailed guide.

Your invoice templates should include a unique invoice number format that makes duplicates easier to spot. And if your business operates across multiple entities, make sure your AP fraud controls include cross-entity checking.

Frequently asked questions

What counts as a duplicate invoice?

A duplicate invoice is any invoice that would result in paying the same vendor twice for the same goods or services. This includes exact copies with identical invoice numbers, reissued invoices with a new number but the same amount, and invoices where the vendor name was entered with a slight variation. The key test is whether paying both invoices would mean double payment for a single delivery or service.

Should I check for duplicates before or after approval?

Before approval. Always. Catching a duplicate after payment means chasing a credit note from the supplier, which takes weeks and creates friction. Screening at the point of entry means the duplicate never reaches an approver, and no money leaves your account. Most AP automation platforms including Pulsify run this check automatically when an invoice is first captured.

What is the average duplicate payment rate in Australian businesses?

Industry data puts the rate between 0.1% and 0.5% of invoices processed. That sounds small until you multiply it by your monthly invoice volume and average invoice value. A business processing 500 invoices per month at an average of $2,000 could be overpaying by $1,000 to $5,000 monthly. Many duplicates involve different invoice numbers, so they slip past simple number-matching checks.

Can duplicate invoices be detected automatically?

Yes, and automated detection is far more reliable than manual checking. Software like Pulsify compares every incoming invoice against your full invoice history using fuzzy matching on vendor names, invoice numbers, amounts, and dates. It catches near-duplicates that a human reviewer would miss, especially when processing hundreds of invoices per month across multiple input channels.

What should I do when a duplicate is flagged?

Hold the payment immediately. Compare both invoices against the purchase order or delivery docket to confirm whether the goods or services were delivered once or twice. Contact the vendor to verify whether the second invoice was intentional or a resend. Document your finding regardless of the outcome, and update the vendor master record if the flag was triggered by inconsistent vendor naming.