Duplicate invoices: How to spot them and prevent double payments

Duplicate invoices drain cash, distort your financial statements, and create VAT compliance risks that can follow you for years. They usually stem from a supplier resubmitting an invoice, a data entry mistake during a busy close, or a fraud attempt. The result is the same: you pay twice for something you only received once.

According to FiscalTec, duplicate payment rates can reach up to 3% of total outgoing payments in high-volume environments, or up to £300,000 for an organisation processing £10 million annually. The good news is that most of the causes are predictable, and the controls that catch them are well understood.

This article is a guide, not legal or tax advice. If you are unsure about VAT treatment or accounting obligations related to duplicate payments, consult your accountant or contact HMRC directly.

What is a duplicate invoice?

A duplicate invoice is the same transaction as one you've already received, processed, or paid. Some duplicates are exact copies. Others carry small changes in formatting or supplier details that make them harder to catch, so you need checks that go beyond exact matching.

For any business managing invoice processing at volume, the problem is widespread. Research by the Accounts Payable Association, cited by UK providers, suggests that nearly two-thirds of UK finance professionals have received duplicate invoices, with about one-third of those leading to payment.

ICAEW guidance recommends duplicate invoice checks alongside standard practices such as three-way matching and limiting manual overrides. HMRC also notes in VATREC8010 that duplicate invoices create the possibility of claiming input tax twice.

Duplicate invoices typically fall into one of these forms:

• Exact duplicates carry identical invoice numbers, supplier details, amounts, and dates. The UK Ministry of Defence identified duplicate numbers as a specific rejection reason within suspicious invoice screening over three years.

• Near-duplicates involve the same underlying transaction with minor variations, such as a reformatted invoice number or a vendor name rendered differently. As Accountancy Age notes, simple rules-based systems often fail to catch these matches.

• Deliberately altered invoices carry the greatest financial fraud risk because they are designed to evade detection. According to Action Fraud data published through the NCA and NatWest's joint campaign, invoice fraud victims lost an average of more than £47,000 per case in reported incidents during September 2025 alone, often through altered payment details or convincing forgeries.

• Supplier resubmissions and internal processing errors account for most of the rest, typically caused by delayed payment confirmation or a system glitch.

The variety matters because your detection controls need to cover all four forms, not just exact matches.

Why do duplicate invoices happen?

Most duplicate invoices trace back to a handful of process gaps that compound under volume:

Manual processing at scale increases the risk of duplicates significantly. Manual invoice management takes time and leaves more room for data entry mistakes, missed checks, and duplicate payments. When your team is processing hundreds of invoices during a busy close, a resubmitted invoice looks identical to a legitimate one.

Multiple intake channels create entry points for the same invoice to arrive twice. When invoices arrive by email, post, supplier portal, and hand-delivery, the same invoice can enter your system through two different routes without anyone realising. Duplicate entry gets worse when different people in the team own different channels.

Vendor name inconsistencies allow duplicates past your checks entirely. Your accounting system may hold one supplier as "Smith & Sons Ltd" while their latest invoice reads "Smith and Sons Limited." Without fuzzy matching (identifying close matches despite minor differences), these register as separate vendors, and the duplicate bypasses your checks.

Weak system controls compound the problem when teams are under pressure to clear the queue. Duplicate payments slip through when your system doesn't check for matching invoice data before approval or payment. The time between receipt and review is where duplicates survive. If your team feels pressure to clear the invoice queue rather than question a suspicious entry, the duplication risk increases. This is especially common during month-end close, when there is more pressure than usual.

All four causes get worse as transaction volume grows, which is why mid-market teams outgrowing manual processes are the most exposed.

What are the VAT and compliance risks of duplicate invoices?

Left uncorrected, duplicate invoice payments can affect your VAT returns, statutory records, and fraud controls.

HMRC and VAT

HMRC states in VATREC8010 that there is no specific law on duplicate VAT invoices, but its policy recognises the risk that you may deduct input tax twice from a duplicate.

If you claimed input tax twice on the same supply, VAT Notice 700/45 treats that as an error. A four-year correction limit applies in certain cases, such as corrections made using VAT652 for errors above the reporting thresholds. When you correct the error, you should include an explanatory note with the date, reason, and amount under that notice.

HMRC can refuse penalty mitigation if you already knew about the errors and disclosed them only because of an enquiry. More seriously, ICAEW warns that you could lose a VAT reclaim entirely if HMRC believes you knew, or should have known, of a connection to fraud.

HMRC's GFC8 guidance also expects you to confirm that VAT corrections don't duplicate earlier error notices and to fix the source of the error so it doesn't recur.

Companies Act 2006

Under Section 386, you must keep accounting records that disclose your financial position with reasonable accuracy. If duplicate payments stay in your records, you risk overstating expenses, understating cash, and misstating payables. Under Section 387, officers in default can face penalties, including a fine or even imprisonment.

How to spot duplicate invoices

Catching duplicate payments before they leave your business takes a combination of manual review for context and judgement calls, and system checks for volume and consistency.

Manual detection methods

Three-way matching. Compare your purchase order, goods receipt note, and supplier invoice. Check whether the purchase order has already been fully invoiced. A new invoice against a completed purchase order is a strong duplicate signal. Note that FiscalTec warns that duplicates and overpayments still slip through with three-way matching alone, so treat it as one layer of your checks, not the only one.

Visual inspection for near-duplicates. Check for invoice number variations ("INV1001" versus "INV-1001"), vendor name inconsistencies ("Ltd" versus "Limited"), and suspiciously similar amounts from the same supplier within a short date range.

Automated detection methods

The ICAEW AI report confirms that UK accounting professionals are already using AI tools for detecting duplicate invoices and suspicious changes on payables.

Fuzzy matching (identifying close matches despite minor differences) and AI-powered pattern recognition go beyond what rules-based systems can catch. If an invoice number has a hyphen added, a space removed, or a character transposed, a basic check misses it. Fuzzy matching applies similarity analysis to invoice numbers, vendor names, and amounts to surface near-duplicates that exact matching would clear. AI-enabled AP platforms take this further, using context to make intelligent matches even when the overlap isn't obvious, according to Accountancy Age.

Real-time duplicate flagging. The most effective platforms check for duplicates when the invoice arrives, before it reaches approval. Spendesk's help centre describes a two-stage check. First, the system compares file checksums at upload to catch exact file duplicates. Then, it compares invoice number, supplier ID, amount, currency, and due date. When a potential duplicate is detected, the system surfaces a warning panel so the submitter can cancel or proceed with justification, rather than allowing the duplicate through silently.

How to prevent duplicate payments

The strongest controls catch duplicate payments before money leaves your account. Recovering a duplicate payment after the fact costs time, goodwill, and often a VAT correction. Building checks into the process from the start is where the real savings sit.

Technical controls matter, but so does culture. As ICAEW puts it, your team should feel comfortable stopping a payment to double-check, not be afraid they’ll be for it.

Centralise your invoice intake

When every invoice flows through a single email inbox or supplier portal, your team has one place to check before entering anything new. Recording each invoice in a searchable register with vendor, invoice number, date, amount, and payment status makes that check fast. Make sure the person who sets up new vendors isn't the same person processing their invoices.

Resubmissions are one of the most common duplicate triggers, and they usually happen because a supplier hasn't received payment or confirmation. Paying within agreed terms and sending remittance advice promptly cuts resubmissions at the source.

Clean your vendor master file

Duplicate vendor records are one of the main reasons duplicate payments get through. If "ABC Ltd" and "ABC Limited" exist as separate entries, a second invoice from the same supplier can bypass every other check you have in place. Standardising naming conventions, verifying tax identification numbers and bank details during vendor management onboarding, and scheduling quarterly data cleansing to merge duplicates all close that gap. ICAEW advises implementing a double-check system before any bank details are changed. Requiring senior finance approval for bank account updates adds another layer of protection.

Implement automated duplicate detection

Automated duplicate detection runs checks in real time as invoices arrive. It compares invoice numbers, flags matching vendor-and-amount combinations, watches for suspiciously close dates, and catches duplicate purchase order references. NHS Wales Shared Services Partnership, which processes 1.8 million transactions a year across 11 NHS bodies, has prevented over £25 million in duplicates since deploying automated detection in 2016.

Connect your AP system to your accounting software

Data silos are where duplicate invoices go unnoticed. When your AP platform and accounting software operate as separate systems, the same invoice can exist in one and not the other. Connecting them creates a single source of truth for invoice and payment data. Bidirectional syncs with platforms like Xero, QuickBooks, or NetSuite mean that when an invoice is recorded in one system, the other reflects it immediately, closing the gap that lets duplicates through. Structured e-invoicing formats like Peppol reduce duplicate risk further by design, with unique identifiers and single-channel delivery eliminating several intake and formatting problems.

Run regular AP audits

Regular reviews catch the issues your frontline controls miss. Use data analytics to detect duplicate payments, unusual activity patterns, and other anomalies in payments or invoice processing. ACCA's combatting fraud research makes the case for full-population analytics over sampling. In one UK public sector case, four fraud cases went undetected for years under traditional sampling.

In practice, this means scheduling audit preparation cycles that cover invoice reconciliations, duplicate payment checks, vendor master file reviews, and broader AP process audits.

What to do when you discover a duplicate payment

Suppose your AP specialist spots that a £4,200 invoice from a facilities supplier was paid twice: once on 3 March and again on 10 March when the supplier resubmitted by email. Here is how you should handle it.

• Document and confirm. Gather both invoice copies, both payment records, and the relevant bank statements. Confirm the duplication internally and obtain authorisation from your finance manager to pursue recovery.

• Contact the supplier. Write formally, explain the error, and provide supporting documentation. Request a voluntary return within 14 to 30 days, or accept a credit note applied to a future invoice. Keep the tone professional because the error often starts on your side.

• Address VAT implications. If you claimed input tax twice, correct the error with HMRC within the four-year window using the appropriate method under VAT Notice 700/45. Proactive correction protects your position on penalty mitigation.

• Fix the root cause. Ask why the duplicate happened, whether that was a missing intake control, a duplicated vendor record, or a lack of automated detection, and close the underlying gap.

The longer a duplicate sits uncorrected, the harder the recovery conversation gets and the weaker your position is with HMRC if the VAT error surfaces later.

How to build a duplicate-proof AP process

No single control stops every duplicate. The value comes from layering intake discipline, clean vendor data, clear approval responsibilities, and automated checks so that each one catches what the others miss.

The goal also isn't a perfect system on day one. It's a process that gets better with time, so your team spends less time chasing corrections and more time on work that moves the business forward.

To see how these layers work inside one platform, explore Spendesk's AP automation and how it catches duplicates before any payment leaves your account.

Frequently asked questions about duplicate invoices

What is the difference between a duplicate invoice and an amended invoice?

A duplicate invoice represents the same transaction submitted more than once with no change to the underlying supply. An amended invoice corrects an error on the original, such as a wrong VAT rate or a revised total after a quantity adjustment. If the supplier is correcting a genuine error, you should receive a credit note against the original followed by a new invoice. If you receive a second invoice for the same supply without a credit note, treat it as a potential duplicate.

How do duplicate invoices affect your VAT returns?

If you reclaim input tax twice on the same supply, HMRC treats that as an error you need to correct within the relevant four-year window. The overclaim is one issue. Weak records and delayed correction make it worse, because HMRC can refuse penalty mitigation if you knew about the errors before disclosing them.

Which type of duplicate invoice is hardest to catch?

Near-duplicates with minor formatting variations are the most likely to bypass your checks. A hyphenated invoice number, a slightly different supplier name, or a rounded total can look like a separate transaction to both your team and your system. Fuzzy matching and AI-powered pattern recognition catch what exact-match rules miss.

How does AP automation prevent duplicate payments?

AP automation checks invoice data as it arrives, matches documents consistently, and flags exceptions before payment is approved. The combination of OCR extraction, real-time duplicate checks, and approval workflows reduces the manual review pressure that allows duplicates to slip through.