What is a duplicate payment in accounts payable?

A duplicate payment is when accounts payable settles the same liability more than once. It happens in two main forms: (1) the same vendor invoice is processed twice — usually because the vendor sent a reminder copy that got booked as a fresh invoice, or the original was entered against two different purchase orders; and (2) two different invoices are paid for the same underlying delivery — a tax invoice and a proforma, or a re-issued invoice with a different number for the same goods. Both produce an overpayment to the vendor that the books treat as a valid expense until reconciliation surfaces it.

How do you detect duplicate vendor payments?

Detection runs along three signals. First, exact matches — same vendor, same invoice number, same amount, paid more than once. These are the easiest to catch and any AP system should block them at entry. Second, fuzzy matches — same vendor, same amount, similar invoice number (different suffix, different formatting), paid within a short window. These need a query report, not an automated block. Third, GRN reuse — the same goods receipt note matched to more than one invoice. The third signal is the most valuable because it catches the case where the vendor issues two genuinely different invoice numbers for the same physical delivery.

How do you recover a duplicate payment from a vendor?

The fastest route is to issue a vendor debit note for the duplicate amount and adjust it against the next legitimate invoice from the same vendor — most cooperative vendors accept this immediately. If the vendor disputes the duplicate, the recovery file should include: the two payment vouchers showing the same vendor and amount, the bank statement entries, the underlying invoice and GRN documents proving only one delivery occurred, and a reconciliation note. For non-cooperative vendors or where the relationship has ended, the file becomes a legal recovery matter — and recovery rates drop sharply. The lesson: detect and recover within 90 days while the vendor relationship is still active.

Duplicate Vendor Payments — How They Happen and How to Stop Them

Q: What should we do if the vendor refuses to return a duplicate payment?

Start with a formal demand letter citing the payment references, dates, and amounts — with bank statements as evidence. Most vendors will agree to adjustment against future invoices rather than a cash refund. If the vendor cooperates, issue a formal vendor debit note to document the recovery and adjust the vendor ledger. If the vendor does not cooperate, escalate to a legal notice. In practice, deduction from the next payment cycle is the most common resolution, but it must be documented through a proper debit note process — not an informal adjustment that leaves the ledger unclear.

Published: April 14, 2026

The bank reconciliation reveals an uncomfortable pattern. The same vendor was paid twice for the same invoice — once in the regular payment run, once through an urgent cheque request two weeks later. Or two separate invoices, each with a different number, were both paid for the same delivery of goods. The total overpayment: Rs 4.7 lakhs. The payment was made six weeks ago. Recovery will be difficult, slow, and embarrassing.

This is not rare. Industry estimates suggest 1-3% of all vendor payments contain some form of duplication or overpayment. PwC's 2024 Global Economic Crime Survey found that 59% of Indian organisations experienced financial fraud in the preceding 24 months, with procurement fraud identified as the number one threat by half of all businesses surveyed. Duplicate payments sit at the intersection of process failure and financial loss — and most go undetected for weeks or months.

1. What Happened — The Anatomy of a Duplicate Payment

Duplicate payments typically follow one of three patterns:

1.1 Same Invoice, Processed Twice

The vendor sends the invoice by email and also submits a physical copy. The email copy is processed by one person in accounts payable; the physical copy is processed by another. Neither checks whether the invoice has already been entered. The vendor receives two payments and — understandably — does not volunteer this information.

1.2 Different Invoice Numbers, Same Delivery

The vendor issues a proforma invoice at the time of dispatch and a tax invoice after delivery. Both carry different numbers. Accounts payable processes both as separate invoices against the same PO. The goods were received once; the payment goes out twice.

1.3 Invoice Paid Without Checking Receipt

The vendor submits an invoice referencing a valid PO number. Accounts payable checks the PO — it exists, the amount matches — and processes payment. But no one checks whether the goods were actually received. The invoice may be for a delivery that hasn't happened yet, for goods that were returned, or for a quantity higher than what was received.

2. Why It Happened — The Missing Control

Every one of these patterns has the same root cause: the invoice was processed in isolation, without being matched against independent evidence of receipt.

In a manual accounts payable process, the clerk has access to the invoice and perhaps the PO. But they have no systematic way to verify whether the goods referenced by the invoice were actually received, in what quantity, and whether another invoice has already been matched to that receipt. They rely on memory, on asking the stores department, on checking a shared folder — all of which fail under volume.

The structural fix is well-established in accounting practice: three-way matching. Every payment must be supported by three documents that independently corroborate each other:

Document	What It Proves
Purchase Order	The purchase was authorised, at this price, for this quantity
Goods Receipt Note	The goods were physically received, in this quantity, on this date
Vendor Invoice	The vendor is claiming payment for this delivery

When all three align, the payment is legitimate. When they don't, the discrepancy must be investigated before payment proceeds. This is not a new concept — it is standard practice in any organisation with mature procurement controls. The problem is that many organisations skip it, either because they don't have a system that enforces it or because the urgency of "clearing vendor payments" overrides the discipline of matching.

3. What to Do Now — Immediate Response

3.1 Identify the Full Exposure

Don't stop at the one duplicate that was discovered. Run a systematic review of the vendor ledger for the past 12-24 months. Look for: same invoice number from the same vendor appearing twice, multiple payments to the same vendor within a short window for similar amounts, and payments that have no corresponding GRN.

3.2 Send Formal Demand

For each confirmed duplicate, send a formal letter to the vendor with payment references, dates, and bank statements as evidence. Request either a refund or written confirmation that the amount can be deducted from the next payment. Document everything — informal phone calls are not sufficient.

3.3 Issue Vendor Debit Notes

For each recovery — whether by refund or deduction — process a formal vendor debit note. This adjusts the vendor ledger correctly, provides an audit trail for the recovery, and ensures the GST implications are handled properly.

3.4 Review the AP Process

Identify how the duplicate entered the system. Was it a training issue? A system gap? Pressure to process payments quickly? The root cause determines the fix.

4. How to Prevent Recurrence — Structural Controls

4.1 Enforce Three-Way Matching

No invoice should be processed for payment unless it is matched to a specific PO and a specific GRN. The matching process verifies that the quantities invoiced do not exceed the quantities received, and that the rates invoiced do not exceed the rates on the PO. If the GRN has already been consumed by a previous invoice, the system blocks the duplicate.

4.2 Link GRN to Specific PO Lines

Each goods receipt is recorded against specific PO line items, with received quantities. This creates an independent receipt record that is separate from the invoice. When the invoice arrives, it is matched not just against the PO but against the GRN — and the GRN can only be matched once.

4.3 Gate Entry as Independent Verification

Before a GRN is even created, the delivery is recorded at the gate entry point — an independent record of what physically entered the premises, with vehicle details and challan references. This provides a third layer of verification: the gate register confirms the delivery happened, the GRN confirms the stores accepted it, and the invoice claims payment for it.

4.4 Vendor Debit Notes for Formal Recovery

When overpayments or duplicate payments are discovered, the recovery must follow a formal debit note process — not an informal adjustment. This keeps the vendor ledger accurate, the GST treatment correct, and the audit trail intact.

Companies lose 10-20% of projected savings to maverick spending each quarter. Duplicate payments are the most visible symptom — but they are usually part of a broader pattern of procurement transactions that bypass controls. Fixing duplicates without fixing the underlying process treats the symptom, not the cause.

5. Frequently Asked Questions

How does 3-way matching prevent duplicate vendor payments?

Three-way matching requires every payment to be supported by three independent documents: a purchase order (what was authorised), a goods receipt note (what was physically received), and a vendor invoice (what the vendor is claiming). Before an invoice is processed, the system verifies that quantities and amounts across all three align. If a GRN has already been matched to a previous invoice, any subsequent invoice for the same delivery is flagged as a potential duplicate. Without this triangulation, accounts payable relies on memory and manual checking — which fails at scale.

What should we do if the vendor refuses to return a duplicate payment?

Start with a formal demand letter citing payment references, dates, and amounts with bank statements as evidence. Most vendors will agree to adjustment against future invoices rather than a cash refund. If the vendor cooperates, issue a formal vendor debit note to document the recovery and adjust the vendor ledger. If the vendor does not cooperate, escalate to a legal notice. In practice, deduction from the next payment cycle is the most common resolution, but it must be documented through a proper debit note process — not an informal adjustment.

How common are duplicate vendor payments in Indian organisations?

More common than most CFOs assume. Industry estimates suggest 1-3% of all vendor payments contain some form of duplication or overpayment. PwC's 2024 survey found that 59% of Indian organisations faced financial fraud in the preceding 24 months, with procurement fraud the top threat for 50% of businesses. Duplicate payments are often process failures rather than fraud, but the financial impact is identical. Recovery audits routinely find six- to seven-figure amounts in duplicates going back just two to three years.

Can the system detect if the same invoice number is submitted twice by the same vendor?

Yes, if the invoice is processed within a structured system rather than manually. When each vendor invoice is recorded against a specific PO and GRN, the system can check whether the same invoice number from the same vendor already exists. It can also detect near-duplicates — same vendor, same amount, same date but slightly different invoice numbers. The key requirement is that invoice data enters a system with vendor-level uniqueness checks, not an email inbox or shared folder where invoices accumulate without cross-referencing.

What is the difference between a duplicate payment and an overpayment?

A duplicate payment is paying the same invoice twice — the full amount is repeated. An overpayment is paying more than the invoiced or contracted amount on a single payment — for example, paying for 100 units when only 80 were received. Both are prevented by the same structural control: matching the payment against the PO (authorised price and quantity) and the GRN (actually received quantity). Three-way matching catches both — duplicates by detecting that the GRN is already consumed, and overpayments by detecting quantity or rate mismatches.

Invoice Matching Guide Goods Receipt Vendor Debit Note Guide Procurement

Concerned About Duplicate Payments?

If duplicate payments have been found in your accounts or you suspect they're happening undetected, share a brief overview of your current AP process. We will assess what structured matching controls would involve for your organisation.

Book a Consultation