The mandate is registered. The UMRN is confirmed. The borrower’s bank has accepted the instruction. And then, on the first EMI date, the debit bounces. Every NBFC and fintech lender running collections in India has faced this scenario, and it is more common than most teams are comfortable admitting.
A registered eNACH mandate is not a guarantee of collection. It is a precondition. Between registration and successful debit sits a set of failure points that are largely predictable, mostly preventable, and almost always expensive when they are not caught early. Understanding why debits fail after a clean registration is the starting point for fixing collection rates that should be higher.
The Failure Reasons That Account for Most Bounces
Not all eNACH failures are equal. Some are borrower-driven. Some are bank-driven. A few are entirely systemic. But the distribution is not random, and lenders who track return codes at the portfolio level quickly see the same handful of reasons accounting for the overwhelming majority of bounced debits.
Insufficient funds is the most frequent cause by a significant margin. The mandate is active, the bank details are correct, and the borrower simply did not have enough balance on the date the debit was presented. This feels obvious, but the fix is not just “remind the borrower.” The fix is timing, which we will get to.
Tracking eNACH debit failures at the return code level reveals the next cluster. Account frozen, account closed, and mandate expired collectively account for a meaningful share of bounces that have nothing to do with borrower intent. A borrower whose salary account was migrated to a new branch, or whose old account was marked dormant after a KYC lapse, will generate a failed debit even if they have funds elsewhere and intend to pay.
Incorrect account details at the point of registration create failures that surface only at the first debit attempt. An IFSC code that was valid during registration but has since been merged or deactivated will pass mandate verification and fail at execution. These are data hygiene issues that compound across a large portfolio.
NPCI revised its rejection reason codes in late 2024, adding twenty new codes and modifying thirty-three existing descriptions to give lenders and banks sharper diagnostic information. Lenders still reading return codes through the old framework are missing the granularity they need to route failed accounts correctly.
Why Timing Is the Fix for Your Largest Failure Category
Insufficient funds is your biggest bounce reason, and the solution is not more reminders. It is better scheduling.
Most salaried borrowers in India receive their credit between the 28th of the month and the 5th of the following month. An eNACH debit presented on the 5th is competing with every other auto-debit, utility payment, and UPI mandate that fires on the same date. Balance probability drops sharply by the 7th or 8th, particularly for borrowers in the lower income segments where the salary-to-expense cycle is tightest.
Lenders who have shifted their eNACH presentation dates to the 1st or 2nd of the month, immediately after the most common salary credit window, consistently report higher first-attempt success rates than those presenting on the 5th or later. The borrower’s intent has not changed. Their balance on the specific day the debit hits has.
For borrowers paid on variable dates, configuring your collections system to attempt the debit based on observed salary credit patterns rather than a fixed calendar date is the next level of optimisation. Not every platform supports this natively, but the ones built for lending operations increasingly do.
The Fixes That Sit Between Registration and First Debit
A meaningful share of eNACH bounces are preventable before the first debit ever fires. The gap between mandate registration and the first collection attempt is where lenders lose money they should not be losing.
Pre-debit account validation should happen after registration, not just during it. An account active at origination can become dormant or frozen in the weeks before the first EMI date. Running a penny-drop or account status check in the days before the first scheduled debit catches these cases before they generate a bounce, a return code, and the penalty charges that follow.
Mandate health monitoring across the live portfolio is equally important. A mandate can be cancelled by the borrower’s bank for administrative reasons, KYC non-compliance at the bank level, or account restructuring, none of which generate a proactive notification to the lender. Lenders who discover mandate cancellation only when the debit fails are reacting to a problem that was detectable days or weeks earlier.
NPCI’s 2025 guidelines now require all participating banks to offer online mandate modification and cancellation services, with banks that fail to comply risking loss of access to the NPCI platform from June 2025 onwards. That regulatory push is improving mandate management infrastructure across the system, but lenders still need their own monitoring layer to catch issues before they reach the debit stage.
Building a Retry Strategy That Actually Recovers Revenue
A failed first attempt does not mean the money is unrecoverable. It means the timing, the channel, or the account was wrong on that particular day.
Effective retry strategy starts with the return code. An insufficient funds failure gets a retry within two to three days, ideally aligned with the next probable balance window. An account frozen or closed failure gets routed to a human follow-up queue because no amount of automated retry will succeed against a structurally blocked account.
Borrowers who bounced on insufficient funds but have historically paid within the first week are your highest-probability recovery cohort. Treating them identically to borrowers whose mandates have lapsed for structural reasons wastes agent time on accounts that will self-resolve and ignores accounts that need immediate manual attention.
Conclusion
A registered mandate creates the infrastructure for collection. It does not guarantee the collection itself. The gap between registration and successful debit is where most avoidable leakage sits, and it is a gap that better timing, pre-debit validation, eNACH mandate monitoring, and return-code-driven retry logic can close materially.
Lenders treating every bounce as a single category are leaving the most actionable data in their collections stack unread. The return codes tell you exactly what went wrong. The question is whether your eNACH infrastructure is built to listen.
