NACH Bounce Rate Analysis by Bank, Date and Channel
Last reviewed: November 2026
NACH bounce rate analysis is the breakdown of returned National Automated Clearing House (NACH) equated monthly instalment (EMI) debits by return reason, destination bank, presentation date, sourcing channel and loan vintage. Without it, a single bounce percentage in the monthly report hides the fact that empty accounts, dead mandates and badly timed EMI dates each need a different fix.
This guide is for heads of collections and chief operating officers (COOs) at non-banking financial companies (NBFCs), housing finance companies (HFCs), banks and fintech lenders. It covers how to calculate the bounce rate correctly, how to group return codes, a six-step analysis workflow, the patterns that point to specific fixes and the metrics to track.
Key Takeaways
- Split every bounce into technical returns (account or mandate problems) and funds returns (no balance), because they have different owners and fixes.
- Report first-presentation bounce rate separately, or re-presentations will inflate the number and hide real trends.
- The most useful cuts are destination bank, EMI date, sourcing channel and vintage; one blended rate shows none of them.
- NPCI limits re-presentations and penalises high return percentages per utility code, so bounce analysis protects your mandate franchise as well as your collections.
What Is NACH Bounce Rate Analysis?
NACH bounce rate analysis turns return files from your sponsor bank into a diagnosis. It answers why EMIs bounced, where the bounces cluster and which of them a process change can prevent.
Building the debit files is covered in our guide to NACH presentation file generation. What happens to the borrower after a bounce is covered in our bucket-wise collection strategy; this guide sits between the two.
How Do You Calculate NACH Bounce Rate?
Calculate NACH bounce rate as returned debits divided by debits that reached the borrower's bank, that is, successful plus returned debits. Debits rejected before reaching the destination bank, for example for an inactive mandate reference, should be tracked as a separate reject rate.
Compute it by count and by value, and always separately for first presentations. A loan that bounces three times in a month is one problem, not three.
Why Does NACH Bounce Rate Analysis Go Wrong?
NACH bounce rate analysis goes wrong for five reasons: a single blended rate, counting re-presentations as new bounces, mixing rejects with returns, ignoring the date dimension and never linking bounces to sourcing. Each one hides a fixable cause.
| Cause | Effect | Prevention Check |
|---|---|---|
| One blended bounce rate | Technical and funds problems look the same | Group every return code into a class |
| Re-presentations counted as new bounces | Rate rises when retries increase | Tag presentation sequence (1st, 2nd, 3rd) |
| Rejects mixed with returns | Mandate setup errors counted as borrower stress | Separate reject and return files |
| No EMI date dimension | Salary-timing bounces blamed on borrowers | Cut by EMI date and pay cycle |
| No link to sourcing data | Weak channels keep sending bad loans | Join returns to channel, branch and vintage |
What Is the Right NACH Bounce Rate Analysis Workflow?
The right NACH bounce rate analysis workflow has six steps: collect, classify, slice, compare, diagnose and act. Run it every cycle, not only when the monthly number looks bad.
- Collect return and reject files for every presentation cycle.
- Classify each return code into a cause class with an owner.
- Slice bounces by destination bank, EMI date, channel, product and vintage.
- Compare each slice against its own baseline and the portfolio average.
- Diagnose whether a spike is technical, timing, sourcing or genuine stress.
- Act through mandate fixes, date changes, sourcing feedback or collections, then track the result.
Step 1: Which Data Fields Does Bounce Analysis Need?
Bounce analysis needs ten fields per debit: loan ID, Unique Mandate Reference Number (UMRN), presentation date, presentation sequence, amount, destination bank and branch code, return code, mandate type, sourcing channel and disbursal month. Most lenders hold all of them, but in three different systems.
The mandate type matters more than teams expect. Physical, net banking and Aadhaar-authenticated mandates often fail in different ways, and our guide to NACH mandate form processing explains where paper mandates go wrong.
Step 2: How Should NACH Return Codes Be Grouped?
Group NACH return codes into four classes: account problems, mandate problems, funds problems and account status problems. Commonly used codes include 01 (account closed), 02 (no such account), 04 (balance insufficient), 05 (not arranged for), 08 (mandate not received), 11 (invalid IFSC or MICR code) and 68 (account frozen or blocked); confirm the full list with your sponsor bank.
| Return Class | Example Codes | Owner | Usual Fix |
|---|---|---|---|
| Account problems | 01, 02, 11 | Operations | New mandate or corrected branch code |
| Mandate problems | 08 | Operations | Re-register the mandate |
| Funds problems | 04 | Collections | Contact, re-present after confirmation |
| Account status problems | 05, 68 | Collections with borrower | Borrower resolves with their bank |
Steps 3 and 4: Which Cuts Reveal the Real Cause of Bounces?
Four cuts reveal most real causes: destination bank, EMI date, sourcing channel and vintage. Compare each against its own history, because a 15% rate may be normal for one product and alarming for another.
A spike at one destination bank on one date usually means a bank-side or branch-code problem, often after a merger, not a sudden wave of borrower stress. If code 11 rises at one bank, check whether its branch codes changed before calling a single borrower.
A gap between EMI date and pay date shows up as a high funds-return rate on early-month dates for salaried borrowers. Moving EMI dates to two or three days after the main salary date can cut these returns without any collections effort.
A high first-EMI bounce rate from one channel or branch is a sourcing signal. It belongs in credit and risk reviews, and our guide to vintage analysis of the loan portfolio shows how to read it by disbursal cohort.
Step 5: How Often Should a Returned EMI Be Re-Presented?
A returned EMI should be re-presented at most twice, and only after the borrower confirms funds. According to NPCI circular NPCI/2023-24/NACH/007 (18 August 2023), returned transactions are limited to one presentation plus two re-presentations, made only after three days from the return and after the customer confirms the balance.
The same circular, and later NPCI circulars that revised its phases, set extra charges for user institutions with high return percentages and finally a bar on registering new mandates on the utility code. So blind re-presentation is not just wasteful; it can put your ability to onboard new borrowers at risk.
Which Bounce Patterns Point to Which Fix?
Six bounce patterns account for most diagnoses, and each points to a different owner.
| Bounce Pattern | Likely Cause | Fix |
|---|---|---|
| Code 11 spike at one bank | Branch codes changed after a merger | Update branch codes, re-present |
| High 01 and 02 returns in older loans | Borrowers changed banks | Mandate swap queue |
| High 04 returns on early-month EMI dates | EMI date before salary credit | Offer date change at next cycle |
| High first-EMI bounces from one channel | Weak sourcing or wrong mandate data | Channel review with credit and risk |
| 08 returns on recent physical mandates | Poor mandate form quality | Fix form checks at login |
| Rising 04 returns across vintages | Genuine borrower stress | Early collections contact |
What share of your bounces last month were technical, and who owns fixing them?
Talk to Our Lending Platform Specialists
Visit Digiqt to see how a lending platform can turn NACH return files into a clear bounce diagnosis.
How Much Can NACH Bounce Rate Analysis Save?
Bounce analysis saves money by removing bounces that never needed a collector. In this illustrative scenario, a lender presents 1,00,000 EMIs a month, sees a 12% first-presentation bounce rate and spends about ₹250 on calls and handling per bounce.
Assume a quarter of bounces are technical and half of those are fixed, and EMI date changes prevent a tenth of funds returns. These are assumptions to show the method.
| Measure | Before Analysis | After Targeted Fixes |
|---|---|---|
| First-presentation bounces a month | 12,000 | 9,600 |
| Technical returns | 3,000 | 1,500 |
| Funds returns | 9,000 | 8,100 |
| Follow-up cost at ₹250 per bounce | ₹30 lakh | ₹24 lakh |
The lesson for leadership: the cheapest collections call is the one you never make. Bounce analysis finds those calls before the collections budget is spent on them.
Where Does Digiqt Lending Platform Fit in NACH Bounce Rate Analysis?
The Digiqt Lending Platform is built to help lenders launch custom lending products or platforms in a matter of weeks. It handles onboarding, disbursement and repayments through APIs, and for NBFCs it offers APIs for onboarding, payments and other financial products.
The platform page does not name a bounce analytics module, so bounce analysis would be built on top of the repayments layer. Typical components include:
- Return file ingestion that matches every return and reject to the loan and its mandate.
- Return code classification into account, mandate, funds and status classes, with an owner for each.
- Slicing and baselines by destination bank, EMI date, channel, product and vintage.
- Re-presentation rules that respect NPCI limits and wait for borrower confirmation.
Digiqt's delivery process starts with problem understanding, suggests a technological solution after validating return on investment (ROI) and solution fit, and then delivers through prototyping, agile sprints, launch and ongoing optimisation. Digiqt is ISO 9001:2015 certified; test any build on several months of your own return files first.
Digiqt's early-stage collections AI agent shows how bounce insight can drive the first contact after a return.
Which Response Fits Each Return Reason?
The right response depends on the return class and how often the loan has bounced.
| Situation | Recommended Approach |
|---|---|
| First technical return | Operations fixes mandate or branch code before next cycle |
| First funds return, good history | Reminder and one re-presentation after confirmation |
| Second funds return in three months | Early collections contact and date review |
| Account frozen or not arranged for | Borrower contacts their bank; hold re-presentation |
| Repeated returns across rails | Collections strategy, not another mandate |
Bounce results also belong in leadership reporting. Our guides to collection efficiency and NBFC MIS reporting show where these numbers should appear.
Which Metrics Show NACH Bounce Rate Analysis Is Working?
Five metrics show whether the analysis is working: first-presentation bounce rate, technical return share, same-month cure rate, re-presentation success rate and utility-code return percentage. Review them monthly by bank, date, channel and vintage.
| Metric | Formula | What a Weak Number Signals |
|---|---|---|
| First-presentation bounce rate | First-presentation returns ÷ first presentations reaching banks | Sourcing, timing or stress problems |
| Technical return share | Technical returns ÷ all returns | Mandate setup or branch code issues |
| Same-month cure rate | Bounced EMIs paid in the same month ÷ bounced EMIs | Slow or poorly targeted follow-up |
| Re-presentation success rate | Successful re-presentations ÷ re-presentations | Retries without borrower confirmation |
| Utility-code return percentage | Returns ÷ (successful + returned) by utility code | Risk of NPCI charges or mandate bars |
Call lists built from bounce classes work better than one list for all. Our guide to collections dialer list management covers how to build them.
Which Mistakes Weaken NACH Bounce Analysis?
Four mistakes weaken NACH bounce analysis, and each is a reporting choice.
- Reporting one bounce rate for the whole book. It hides which problem is growing.
- Sending technical returns to collectors. Borrowers get calls for problems they did not cause.
- Re-presenting without confirmation. It wastes attempts and raises your return percentage.
- Never sharing first-EMI bounces with credit. The same channel keeps sending the same loans.
What Is Changing Next?
The rules for following up on bounces are tightening for NBFCs. According to the RBI (Non-Banking Financial Companies – Responsible Business Conduct) Third Amendment Directions, 2026 (RBI/2026-27/230, 6 August 2026, effective 1 January 2027), recovery contact is allowed only between 08:00 and 19:00 unless the borrower asks otherwise, and recovery call records must be kept for six months.
So bounce analysis will also need to feed calling windows and call logs. Plan bounce-day outreach now so the first contact after a return fits the new hours.
Want every bounce routed to the right fix before the next EMI cycle?
Talk to Our Lending Platform Specialists
Visit Digiqt to see how the Digiqt Lending Platform can break down NACH returns by reason, bank, date and channel.
Sources
- RBI: NBFC Responsible Business Conduct Third Amendment Directions, 2026 (RBI/2026-27/230, 6 August 2026)
- TeamLease RegTech: NPCI Circular NPCI/2023-24/NACH/007 on Penalty for High Percentage of ACH Debit Returns
- Juspay LotusPay Docs: ACH Debit Rejection and Return Codes
- Juspay LotusPay Docs: ACH Debit Penalty Charges for High Percentage of Returns
- Digiqt: Lending Platform



