Content authored by practitioners with experience at Amazon India, Intuit QuickBooks, and the Tata Group. Meet the team →
The same vendor invoice is paid twice through different routes or under slightly different invoice numbers, and the excess sits unnoticed in the vendor ledger.
Normalise invoice numbers, then flag payments with the same vendor and amount within 30 days, the same invoice number, or the same UTR across the bank statement and payment register.
Bank statement export, payment register or vendor ledger, and a vendor master with consistent names.
A list of suspected duplicates with both bank references, ready for a recovery request to the vendor.
A duplicate payment is one vendor invoice paid twice. It usually happens when the invoice is paid by two routes, such as an NEFT batch and a manual cheque, or when a re-sent invoice is keyed in with a slightly different number. You catch it by matching invoice numbers, amounts and UTR numbers across the bank statement and your payment register.
On the Seven Classes of Reconciliation Leakage, a duplicate that nobody chases ends up as Unexplained variance: money gone with no explanation on file.
How do duplicate vendor payments happen?
| Likely cause | How it happens | What you see |
|---|---|---|
| Invoice keyed twice | ”AB/241” and “AB-241” entered as two invoices | Two open bills, both paid |
| Payment run plus manual payment | Vendor chases, someone pays by cheque, the run pays too | NEFT and cheque for the same amount |
| Reminder copy paid | Vendor’s reminder or duplicate copy treated as a new invoice | Same amount, same vendor, later date |
| Advance plus final payment | Advance paid, then full invoice paid without adjusting the advance | Vendor ledger in debit |
| Two vendor codes | Same vendor created twice in the master | Payments split across two ledgers |
How do you check last month’s payments in fifteen minutes?
- Export last month’s payments from the bank statement, with date, amount, payee and UTR.
- Export the vendor payments from Tally or Zoho Books with invoice numbers.
- Remove spaces, slashes, hyphens and leading zeros from invoice numbers.
- Sort by vendor, then amount. Flag the same vendor and same amount within 30 days.
- Flag the same normalised invoice number paid more than once.
- Flag any UTR appearing twice in the books, which shows one bank payment booked twice.
- Check each flag against the invoice period. Monthly rent is not a duplicate.
Worked example: ₹1,86,400 paid twice
Invoice AB/241 from Anand Steel Supplies for ₹1,86,400 was received on 28 May.
- 4 June: the weekly NEFT run pays ₹1,86,400. The bank statement shows “NEFT DR ANAND STEEL SUPPL” with a UTR.
- 15 June: Anand Steel sends a reminder copy, keyed in as “AB-241”.
- 19 June: the purchase head approves the reminder, and a cheque for ₹1,86,400 is issued. The statement shows “CHQ PAID 004821”.
The vendor ledger now shows two invoices, AB/241 and AB-241, both paid, and the ledger looks balanced. Only the normalised invoice number gives it away: both become “AB241”.
The vendor statement, when it arrives, shows ₹1,86,400 received in excess. If nobody asks for it, the amount stays as an advance until it is written off at year-end.
TDS can double up too. If 2 percent was deducted under Section 194C on both payments, ₹3,728 was withheld twice, so the second deduction must be sorted out with the vendor before the quarterly TDS return is filed.
What happens after you find one?
Finding it is the first half. Next you write to the vendor with both bank references, agree a refund or an adjustment against the next bill, and fix the vendor master so the same mistake cannot repeat. A monthly bank-to-books match surfaces payments that do not tie to a single open invoice; TransactIG matches bank statement lines to the books and routes unmatched items to an exception queue.
What to read next
- We paid a vendor twice or a customer paid too much: refund or adjust the excess?
- Reconciliation errors: missing and mistimed entries
- Reconciliation errors from carelessness
- Stop revenue leakage
Content authored by practitioners with experience at Amazon India, Intuit QuickBooks, and the Tata Group. Meet the team →