Skip to main content
How-To · 6 min read

Can I Present a Failed NACH Debit Again? Retry Rules for Small Collectors

Temporary failures such as low balance can be re-presented, typically up to two times a few business days apart. Cancelled mandates and closed or frozen accounts need a new mandate instead.

Terra Insight
Terra Insight Editorial Team Reconciliation Infrastructure

Content authored by practitioners with experience at Amazon India, Intuit QuickBooks, and the Tata Group. Meet the team →

Published 14 October 2026
Domain expertise
TDS Reconciliation GST Input Credit Platform Settlements NACH Batch Matching Bank Reconciliation Form 26AS Matching ERP Integrations Enterprise Finance Ops
Knowledge Card
Problem

Small collectors either never retry failed NACH debits or retry every failure, wasting fees on mandates that can never succeed.

How It's Resolved

Retry only temporary failures, such as low balance or technical errors, a few business days later under the same UMRN; route dead mandates to a new mandate or another payment mode.

Configuration

Return reason list mapped to retry or new-mandate, retry dates and count per UMRN, fee tracking, and customer messages before each retry.

Output

Higher recovery on temporary failures, fewer wasted fees, and a clean record of every attempt against each UMRN.

Yes, for temporary failures such as low balance or a technical error. Present the debit again under the same mandate, usually within the same billing cycle and your sponsor bank’s retry limits. No for dead mandates: a cancelled mandate, a closed or frozen account, or a debit above the mandate maximum needs a fresh mandate or another payment route.

Which failures can I retry?

Failure reason (in words)Retry or new mandateWhen to retryWhat to tell the customer
Insufficient balanceRetryTypically 3 to 5 business days later, or just after salary dateAmount, new date, request to fund the account
Technical failure at a bankRetryNext batch dateUsually nothing, or a short note
Debit above mandate maximumNew mandateDo not retryAsk for a new mandate with a higher cap
Mandate cancelled by customerNew mandate or other modeDo not retryAsk for a new mandate or UPI or NEFT payment
Account closedNew mandate on new accountDo not retryAsk for new account details
Account frozen or blockedWait for customerDo not retry until resolvedAsk customer to resolve with their bank
Details mismatchCorrect and re-registerAfter correctionConfirm account details

Read the reason in the return file from your sponsor bank, matched by UMRN.

How many retries, and how far apart?

There is no single rule for every collector. Practice varies by sponsor bank and by lender policy. A common pattern is up to two retries within the same billing cycle, three to five business days apart. Confirm the limit with your sponsor bank and write your own policy down.

Time retries well. If a customer’s salary lands on the 1st, a retry on the 2nd or 3rd of the next month may be too late for this cycle, but a retry soon after mid-month bonus or business receipts may work. Ask the customer when funds will be in.

Do repeat failures cost money?

Usually. Each rejected presentation can carry a fee from your sponsor bank, plus 18% GST on that fee. The customer’s bank may also charge the customer a bounce fee. Banks set their own charges, so check your schedule of charges. That is why retries should be selective: two failed retries on a dead mandate cost twice and still collect nothing.

For the customer, a debit returned for insufficient funds can also have legal weight under Section 25 of the Payment and Settlement Systems Act 2007, which treats it in a way similar to a cheque bounce.

Worked example: a low-balance EMI

A small lender’s ₹12,500 EMI was presented on 5 November and returned on 7 November for insufficient balance. The sponsor bank charges an illustrative ₹250 return fee plus 18% GST of ₹45. The lender messages the customer, who confirms funds by the 11th. It re-presents on 12 November and collects ₹12,500.

Entries:

DateEntryAmount
5 NovemberEMI due: debit customer, credit interest income and principal per schedule₹12,500
7 NovemberReturn: no receipt to post; customer stays overdue₹12,500 overdue
7 NovemberReturn fee: debit bank charges ₹250 and input GST ₹45, credit bank₹295
12 NovemberRetry collected: debit bank, credit customer₹12,500

Overdue days: 12 − 5 = 7. Total bank cost: ₹250 + ₹45 = ₹295. Whether the lender can recover a bounce charge from the customer depends on the loan agreement.

How do I keep track of every attempt?

Record each presentation against the UMRN: date, amount, result, reason and fee. A simple sheet with one row per attempt is enough for a small collector. It tells you how many retries each mandate has had, which reasons repeat, and what the failures are costing.

NACH reconciliation is on the TransactIG roadmap; see NACH batch reconciliation.

Primary reference: NPCI: NACH product overview — NPCI runs the NACH debit system through which failed debits can be presented again under the same mandate..

Frequently Asked Questions

Can I present a failed NACH debit again?
Yes, if it failed for a temporary reason such as low balance or a technical error. Present it again under the same UMRN within your sponsor bank's rules.
How many times can I retry?
Practice varies by sponsor bank and lender policy. Many lenders allow up to two retries in the same billing cycle, typically three to five business days apart.
Which failures should never be retried?
Cancelled mandates, closed or frozen accounts, and debits above the mandate maximum. Retrying gives the same return and can cost a fee each time.
Does each retry cost money?
Often yes. Sponsor banks may charge for each presentation or return, and the customer's bank may charge a bounce fee. Each bank sets its own charges.
Should I tell the customer before retrying?
Yes. A short message with the amount and new date improves the chance the account is funded and avoids a second bounce.

See how TransactIG handles reconciliation for your industry

Configuration takes 2–4 weeks. No code development required. ISO 27001:2022 certified.