A payment is made or received twice or for too much, and the excess sits in the books as income, expense or an unreviewed on-account balance.
Identify the cause, book the excess as an advance or on-account item, agree in writing whether it will be refunded or adjusted, and clear it with a traceable entry.
Bank statement with UTRs, the party ledger, the invoice or bill concerned, and a written agreement with the party on refund or adjustment.
Every excess payment is either refunded with a UTR on record or adjusted against a named future invoice, and no on-account balance sits unexplained.
An excess payment is owed back until it is refunded or adjusted. That is true whether you paid a vendor twice or a customer paid you too much. Book the excess as an advance or on-account balance, not as income or expense. Then agree the plan with the other party in writing.
This article covers business payments by bank transfer: NEFT, RTGS, IMPS and UPI between businesses. Double payments on website or marketplace orders work differently and are not covered here.
How does an excess payment arise?
| Cause | How it shows in the bank | How to confirm |
|---|---|---|
| Invoice paid twice, once by NEFT and once by UPI | Two credits or debits of the same amount, a few days apart | Two different UTRs against the same invoice number |
| Payment keyed twice in net banking | Two identical debits on the same day | Same amount, same beneficiary, consecutive references |
| Customer paid gross when TDS applied | Credit equals invoice total instead of total less TDS | Customer later deducts the TDS from another payment, or files TDS anyway |
| Credit note not applied | Customer paid the full invoice although a credit note was issued | Credit note date is before the payment date |
| Advance for the next order | Credit with a note such as “advance PO 4471” | Customer’s purchase order or email |
Only the last one is a genuine advance. The others are mistakes, and the money belongs to the other party.
Should I refund the excess or adjust it?
| Refund | Adjust against the next invoice or bill | |
|---|---|---|
| Best when | No next order soon, or the party asks for the money | Regular trading relationship, next order confirmed |
| Record to keep | Party’s request, refund UTR, ledger entry | Party’s written agreement naming the invoice to adjust |
| Risk | Refund paid to wrong account | Adjustment forgotten, balance sits for months |
| Time to close | Days | Until the next invoice is raised |
Never decide alone. A customer who expected a refund and finds the money “adjusted” will dispute it later. An email of two lines is enough.
Worked example: a customer pays ₹1,18,000 twice
You raised invoice INV-3307 for ₹1,18,000 (₹1,00,000 plus 18 percent GST). The customer paid it by NEFT on 3 October and again by UPI on 6 October. Your bank shows two credits of ₹1,18,000.
Steps:
- Match the first credit to INV-3307. The invoice is closed.
- Book the second ₹1,18,000 to the customer’s account as an on-account balance.
- Write to the customer with both UTRs.
- The customer has a confirmed order for next week worth ₹94,400 (₹80,000 plus 18 percent GST). They agree to adjust that and ask for the rest back.
- Raise the next invoice for ₹94,400 and set it off against the on-account balance. ₹23,600 remains.
- Refund ₹23,600 by NEFT and note the refund UTR against the ledger entry.
Check: ₹94,400 plus ₹23,600 is ₹1,18,000. The on-account balance is now zero.
The vendor case is the mirror image. If you paid a vendor’s ₹50,000 bill twice, book the second ₹50,000 as an advance to the vendor, send both UTRs, and get either a refund or a written promise to adjust it against the next bill.
What happens if on-account balances are not reviewed?
They pile up. A customer with three small excess payments of ₹2,400, ₹6,000 and ₹11,800 has ₹20,200 sitting on account, and nobody remembers why. A year later the balance gets written off to income or expense, and the reconciliation trail is lost.
Review every on-account and advance balance monthly. Any line older than 60 days typically needs a refund or a written adjustment plan.
What to read next
Next, read the partial payment reconciliation guide, which covers matching one payment to many invoices. For keeping old balances visible, see exception management in reconciliation. Related: did we pay the same vendor invoice twice? and the Seven Classes of Reconciliation Leakage.
TransactIG matches bank statement lines to your books and shows unmatched credits, such as a second payment for an already-closed invoice, in an exception queue.