Content authored by practitioners with experience at Amazon India, Intuit QuickBooks, and the Tata Group. Meet the team →
A business or customer sees a NACH debit returned although the account had enough money and assumes a bank error.
NACH return reasons cover the mandate and the account as well as the balance: amount above mandate maximum, mandate inactive, account frozen or closed, data mismatch or technical failure.
Return file with reasons by UMRN, mandate register with maximum amount and status, and a list of which reasons allow a retry.
Each return routed correctly: retry for temporary reasons, data correction for mismatches, and a new mandate for limit or cancellation reasons.
A NACH debit can come back even when the account holds enough money. Many return reasons concern the mandate or the account, not the balance: the debit was above the mandate maximum, the mandate was cancelled or had expired, the account was frozen or under a lien, or the account details did not match. The exact reason is in your bank’s return file, matched by UMRN.
What are the likely causes?
| Likely cause | What it means | Who can fix it |
|---|---|---|
| Balance low at presentation time | Money arrived after the bank processed the debit | Business can retry |
| Debit above the mandate maximum | EMI or bill is higher than the cap the customer approved | Customer must sign a new mandate |
| Mandate cancelled or expired | Customer revoked it, or its end date passed | Customer must sign a new mandate |
| Account frozen or under lien | Bank, court or tax order blocks debits | Customer must resolve with their bank |
| Account number or name mismatch | Mandate details differ from bank records | Business corrects data or re-registers |
| Bank-side technical failure | Processing error at a bank | Business can retry |
Return reasons are attached by the customer’s bank in words and as standard reason codes set by NPCI. Read the reason given in your file rather than guessing.
Which causes can the business fix, and which need the customer?
- Retry: low balance at presentation time, or a technical failure. Wait a few business days and present again within your sponsor bank’s rules.
- Correct the data: account number, IFSC or name mismatch. Fix the record and, if needed, re-register.
- New mandate: debit above the maximum, cancelled or expired mandate. Retrying gives the same return each time and may cost a fee per attempt.
- Customer’s bank: frozen account or lien. Only the customer can clear it.
Where do I see the exact reason?
In the return file or return advice from your sponsor bank or payment gateway. Match it to the customer by UMRN (Unique Mandate Reference Number), not by name. The bank statement narration usually shows only the batch credit or the return amount, never the reason.
Timing tip: banks check the balance when they process the debit, which can be early on the due date. A customer whose salary lands at 4 pm may still see a morning debit returned for low balance.
Worked example: the mandate cap
A customer has a loan EMI of ₹12,500 due on the 5th. Their mandate, signed two years ago for an older loan, has a maximum of ₹10,000. On 5 November the account holds ₹18,000.
- Debit presented: ₹12,500.
- Mandate maximum: ₹10,000.
- Excess over cap: ₹12,500 − ₹10,000 = ₹2,500.
- Result: returned, reason amount exceeds the mandate limit, even though ₹18,000 is more than ₹12,500.
Retrying will fail again. The lender asks the customer to sign a new eNACH with a higher maximum, for example ₹15,000, and collects November’s EMI by UPI or NEFT meanwhile. If the sponsor bank charges, say, ₹250 for the return plus 18% GST of ₹45, the lender books ₹295 as bank charges; whether it can recover that from the customer depends on the loan agreement.
Does a failed debit have legal consequences?
For a return due to insufficient funds, Section 25 of the Payment and Settlement Systems Act 2007 treats dishonour of an electronic funds transfer in a way similar to a cheque bounce under the Negotiable Instruments Act 1881. Returns for mandate-limit or data reasons are a different matter. This is one more reason to read the actual return reason.
How do I prevent the same return next month?
Keep the mandate maximum, end date and status in a register, and compare each upcoming debit with the cap before presenting. Present a day or two after the customer’s usual salary date where the contract allows. And if a reason repeats twice for the same customer, call them rather than presenting a third time.
What to read next
- What happens when a customer cancels a mandate
- NACH return reasons reference
- How do I reconcile a NACH mandate that bounced
NACH reconciliation is on the TransactIG roadmap; see NACH batch reconciliation.