Content authored by practitioners with experience at Amazon India, Intuit QuickBooks, and the Tata Group. Meet the team →
An Indian originator (an NBFC on EMI collections, an insurer on premium debits, an AMC on SIP debits, a SaaS company on recurring subscription pulls) presents a NACH Debit batch on the fifth of the month for a portfolio of mandates. Two days later the NPCI return file arrives listing the rejected entries with their two-digit reason codes. One entry — an illustrative Rs 3.2 lakh EMI mandate on an NBFC book — returns with code R01 (Insufficient Funds). The books already posted the credit against the receivable on the presentation date; the bank statement now shows a debit reversal against that credit plus a Rs 4,500 dishonour fee. The reconciler has to reverse the book entry, keep the audit trail intact for a potential Section 138 NI Act or Section 25 PSSA 2007 escalation, route the mandate to the retry queue or the collections queue depending on the return code, and reflect the outstanding receivable back in the ageing report — all inside the Days 1 to 5 monthly bank reconciliation window.
Every NACH bounce reconciliation runs through six deterministic steps. Step one — parse the return file by UMRN and extract the two-digit reason code for each rejected entry. Step two — post a reversal journal that credits the receivable, debits the bank clearing account, and books the dishonour fee to bank charges, with narration referencing UMRN, presentation date, return date, and reason code. Step three — classify the return code as retriable (R01, R09 amount discrepancy after resolution, R11 payer bank refers to drawer) or non-retriable (R02 account closed, R25 mandate cancelled, R27 stop payment, R30 debit account frozen). Step four — for a retriable code, queue a re-presentation in the next NACH Debit batch inside the same billing cycle, subject to the two-retry policy cap. Step five — for a non-retriable code, route the UMRN to the mandate re-registration workflow or the collections workflow depending on whether the payer intends to continue paying or is disputing the debit. Step six — where the return is code R01 and the payer has failed to cure within the notice window, initiate the Section 138 NI Act demand-notice sequence (thirty-day notice, fifteen-day cure window, criminal complaint within one month of expiry) in parallel with the Section 25 PSSA 2007 route. The Section 80 NI Act eighteen per cent per annum interest clock runs from the presentation date until realisation.
Access to the presenting bank's NACH portal or SFTP endpoint for the daily return file. A return-code library keyed to the current NPCI R01 to R99 code set with the retriable/non-retriable classification. A UMRN keyed match table linking each mandate to the underlying receivable, the payer's contract terms, and the default rate (if any) that applies in place of the Section 80 NI Act eighteen per cent statutory rate. A reversal-journal template with mandatory UMRN, presentation date, return date, and reason-code fields on the narration. A retry queue with a maximum of two attempts inside three to five business days each. A collections queue keyed to non-retriable codes with a demand-notice template that references Section 138 NI Act and Section 25 PSSA 2007. A Section 138 timeline tracker — day zero on dishonour intimation, day thirty demand-notice deadline, day forty-five cure-window expiry, day seventy-five criminal-complaint filing deadline.
Every NACH bounce is reversed in the books on T+1 or T+2 with a full audit trail from the original mandate through the presentation and return to the specific reason code. The receivable ageing report reflects the correct outstanding position on the fifth of the following month with no phantom credits. The retriable queue clears inside the current billing cycle; the non-retriable queue is routed to mandate re-registration or collections within one business day of the return. The Section 138 NI Act and Section 25 PSSA 2007 escalation trail is defensible on any subsequent regulator or auditor sample. The RBI Master Direction on Digital Payment Security Controls audit-trail obligation is met without a manual reconstruction exercise.
You presented the NACH Debit batch on the fifth of the month. One of the entries — an illustrative Rs 3.2 lakh EMI mandate against a borrower’s savings account — was scheduled to hit that morning. Your books posted the credit against the receivable the same day. The receivable ageing report on the sixth showed the account current.
Two days later the return file arrives from NPCI. That specific mandate is listed with reason code R01 (Insufficient Funds). The bank statement shows the credit was reversed on the seventh and a Rs 4,500 dishonour fee was debited to the operating account. The receivable is back open. The books still show the credit. What do you actually do — and in what order?
The quick answer
Every NACH bounce reconciliation runs through six deterministic steps: parse the return file by UMRN (the twenty-character Unique Mandate Reference Number), post a reversal journal that restores the open receivable and books the dishonour fee, classify the reason code as retriable or non-retriable, queue a re-presentation for retriable codes or route to collections for non-retriable codes, and — where the code is R01 and the payer does not cure inside the notice window — initiate the Section 138 Negotiable Instruments Act demand-notice sequence in parallel with the Section 25 Payment and Settlement Systems Act 2007 electronic-payment offence route.
The one moment where reconciliations go wrong: the reversal journal has to reference the UMRN, the presentation date, the return date, and the reason code in the narration. A reversal booked without these four fields destroys the audit trail that the RBI Master Direction on Digital Payment Security Controls requires and that the eventual Section 138 complaint depends on.
Step 1 — Pull the return file and match by UMRN
The NPCI return file lands with the presenting bank on T+1 or T+2 from the presentation date. Depending on your integration, it arrives on your presenting bank’s NACH portal, on an SFTP endpoint your finance team polls, or as a mid-morning bank-generated attachment. Pull the file, parse it by row, and extract three fields for each rejected entry — the UMRN, the two-digit reason code, and the original presentation amount.
The UMRN is the primary match key. Every mandate you registered carries a UMRN assigned by NPCI at registration time; every presentation batch quotes that UMRN; every return file entry echoes it. Match each rejected UMRN to the underlying receivable in your loan management system, subscription ledger, or premium register. This is where you learn which specific EMI, subscription pull, or premium debit failed and which payer is on the other end.
The full NACH return code reference for R01 through R99 documents the approximately one hundred codes NPCI publishes and their retriable-versus-non-retriable classification. R01 (Insufficient Funds) is the single most common return by volume — often above forty per cent of all NACH bounces on a mid-market NBFC book — and is the code that triggers the Section 138 NI Act escalation ladder if the payer does not cure inside the notice window.
Step 2 — Post the reversal journal with full narration
This is the step where the reconciliation most often loses its audit trail. The instinct — reverse the credit and move on — leaves your books consistent with the bank but destroys the connection back to the specific mandate and the specific reason code that a Section 138 NI Act complaint later depends on.
The correct reversal journal for our illustrative Rs 3.2 lakh R01 return:
- Credit the receivable account for Rs 3,20,000 (restoring the open receivable against the payer)
- Debit the bank clearing account for Rs 3,20,000 (removing the credit that was never realised)
- Debit the bank charges account for Rs 4,500 (booking the dishonour fee)
- Credit the bank operating account for Rs 4,500 (matching the fee debit on the bank statement)
The narration on every line: “NACH Debit reversal — UMRN [20-char string] — presentation 05-Aug-2026 — return 07-Aug-2026 — reason R01 Insufficient Funds”. If you skip any of these four fields, you have booked a technically correct reversal but you have detached the reversal from the mandate lifecycle, and the mandate management reconciliation later cannot reconstruct which cycle contained which reversal.
The NACH mandate management reconciliation walkthrough covers the UMRN lifecycle end-to-end and shows why the UMRN-on-every-line discipline pays off when the same mandate returns twice in three months.
Step 3 — Classify the reason code as retriable or non-retriable
R01 (Insufficient Funds) is retriable — it reflects a temporary liquidity failure on the payer’s account rather than a defect in the mandate itself. You can re-present the same UMRN in a new NACH Debit batch, typically within three to five business days of the original return, subject to your internal retry policy (most originators cap at two retry attempts within the same billing cycle).
R02 (Account Closed), R25 (Mandate Cancelled by Account Holder), R27 (Stop Payment), R30 (Debit Account Frozen) are non-retriable. Re-presenting these UMRNs simply repeats the same return code in the next batch. The correct route is mandate re-registration under a fresh UMRN, a collections contact to understand whether the payer intends to continue paying, or — where the payer has actively disputed the debit — a dispute resolution workflow before any further presentation.
R09 (Amount Discrepancy) and R11 (Payer Bank Refers to Drawer) sit in a middle bucket — retriable in principle but only after the underlying issue is resolved with the payer’s bank. Simply re-presenting a mismatched amount produces the same rejection.
Step 4 — Queue the retry (or route to collections)
For a retriable code, add the UMRN to the next NACH Debit batch inside the current billing cycle. Track the retry attempt count against your internal cap (typically two). If the second retry also returns with R01, treat the mandate as effectively non-retriable for the cycle and route it to the collections queue rather than a third retry.
For a non-retriable code, route the UMRN to the appropriate downstream workflow — mandate re-registration for R02 and R25 where the payer intends to continue paying, dispute resolution for R27, and collections for the escalation cases. Update the receivable ageing report to reflect the failed collection so the unreconciled bank credit decision tree treatment of the corresponding bank line is closed out on the same day.
Step 5 — Where the payer does not cure inside the notice window, initiate the Section 138 sequence
Section 138 of the Negotiable Instruments Act 1881 was extended by the 2015 and 2018 amendments to cover electronic modes of payment. On a R01 return where the underlying obligation is a debt discharged through the mandate — an NBFC EMI, an insurance premium against an active policy, a subscription pull against a live contract — the Section 138 machinery applies to the failed NACH debit the same way it applies to a bounced cheque.
The three critical dates:
- Day zero — the dishonour intimation date (the day the return file arrives)
- Day thirty — the last day to serve a written demand notice on the payer under Section 138(b)
- Day forty-five — the last day of the fifteen-day payment window given to the drawer under Section 138(c)
- Day seventy-five — the last day to file a criminal complaint under Section 142
Section 25 of the Payment and Settlement Systems Act 2007 is the parallel electronic-payment offence — imprisonment up to two years or fine up to twice the amount of the failed transfer. Practice in Indian courts is to invoke both provisions in the same complaint where the facts support it; the R01 return file entry is prima facie evidence of insufficient funds under both statutes.
The interest recovery runs on Section 80 of the Negotiable Instruments Act at eighteen per cent per annum from the presentation date until realisation, where the underlying contract with the payer does not specify a separate default rate. On our illustrative Rs 3.2 lakh mandate, a ninety-day delay to realisation adds approximately Rs 14,200 in Section 80 statutory interest to the recoverable amount — separately from the Rs 4,500 dishonour fee already booked as bank charges.
The NACH bounce recovery and Section 43B(h) MSME cash-basis rule covers the parallel Income-tax Act treatment where the failed collection is against an MSME supplier and the payment-timing rule under Section 43B(h) interacts with the bounce.
Step 6 — Reflect the mandate cancellation window on the payer’s side
Under the NPCI NACH framework, the payer retains a statutory right to cancel a NACH mandate at any time by notifying their bank. The cancellation typically takes four to ten business days to propagate through NPCI to the originator, and a presentation submitted before the cancellation is fully propagated will return with R25.
Two treatments follow. If the payer cancels the mandate intending to continue paying (they are changing bank accounts, they are consolidating standing instructions on a new provider), the workflow is mandate re-registration under a fresh UMRN — the debt is unaffected, only the collection instrument has changed. If the payer cancels the mandate to stop paying (they are disputing the debt, they are exercising a subscription-cancellation right, they are moving into default), the workflow is a collections contact and, where the debt is undisputed, the Section 138 NI Act demand-notice route on the underlying contract.
The one to escalate first — the R01 return that reveals books certifying money that never arrived
The dangerous pattern behind every NACH bounce reconciliation is the moment between the presentation-date book entry and the T+2 return file. For those forty-eight hours, your books certify a credit that has not yet cleared. The receivable ageing report shows the account current. Any management review, any board pack, any investor report generated inside that window presents a picture that the bank statement is about to contradict.
The escalation-first discipline is not the specific R01 case — it is the class of R01 cases as a whole. A finance team that reconciles bank credits weekly rather than daily will book two, three, or five days of NACH credits that then reverse before the reconciliation catches them; the receivable ageing report on the weekly-close date is systematically overstated by the sum of every un-reversed bounce.
The Days 1 to 5 bank reconciliation runbook treats the NACH return-file pull as a Day-1 activity precisely because the certification risk during the T+1 or T+2 window is real. The HDFC bank reconciliation narration reference documents the specific narration patterns your presenting bank uses on the debit reversal and the dishonour-fee line — matching these two lines to the specific UMRN is what closes the reconciliation cleanly.
When the manual bounce cycle stops holding
One or two NACH bounces per hundred presentations is normal for a mid-market Indian originator. At five hundred active mandates per month, a single analyst can pull the daily return file, extract the UMRN and reason code for each rejected entry, post the reversal journal, route retriable codes to the retry queue, and hand non-retriable codes to the collections desk inside the Days 1 to 5 bank reconciliation window.
Above five thousand active mandates per month — the scale at which the R01 retry queue and the R25 mandate re-registration queue each need daily rather than weekly attention, at which the Section 138 NI Act notice-window tracker becomes a controller-signed weekly discipline in its own right, at which the receivable ageing report cannot afford to be forty-eight hours stale — the manual cycle stops fitting inside a Days 1 to 5 rhythm and becomes a rolling exception queue. Moving the return-file parsing, the UMRN match, the reason-code routing, and the Section 138 timeline tracker onto continuously refreshed detection — where Terra Insight’s NACH batch reconciliation treats the T+1 return file as first-class input and the reversal journal template as an automated posting — is what keeps the monthly close inside a five-day window rather than a two-week reconciliation firefight.
Go deeper
- NACH return codes R01 to R99 — the full reference and resolution guide
- NACH mandate management reconciliation — the UMRN lifecycle end-to-end
- Playbook Brief 9: the unreconciled bank credit decision tree
- Playbook Brief 1: the Days 1 to 5 bank reconciliation runbook
- NACH bounce recovery and the Section 43B(h) MSME cash-basis rule
- HDFC bank reconciliation — the narration reference for NACH reversals
- NACH batch reconciliation for Indian originators
Frequently Asked Questions
The bank statement shows my Rs 3.2 lakh NACH credit was reversed. Do I just delete the receipt entry in my books?
No. Reversing the receipt entry without matching it to the specific UMRN and return code destroys the audit trail that Section 138 NI Act, Section 25 PSSA 2007, and the RBI Master Direction on Digital Payment Security Controls all require. The correct book entry is a reversal journal that credits back the receivable account (restoring the open receivable), debits the bank clearing account (removing the credit that was never realised), and posts the Rs 4,500 dishonour fee to a bank charges account. The reversal journal narration must reference the UMRN, the presentation date, the return date, and the return reason code (R01, R02, R09, R11, and so on). This gives the eventual Section 138 demand notice a chain-of-evidence trail from the original mandate through the presentation to the specific return code — without which the criminal complaint is procedurally weak.
What is the difference between a retriable return code and a non-retriable one?
A retriable code — R01 Insufficient Funds is the classic case — reflects a temporary liquidity failure on the payer’s account rather than a defect in the mandate itself. The originator can re-present the same UMRN in a new NACH Debit batch, typically within three to five business days of the original return, subject to the internal retry policy (most originators cap at two retry attempts within the same billing cycle). A non-retriable code — R02 Account Closed, R25 Mandate Cancelled by Account Holder, R27 Stop Payment — reflects a permanent condition or an active dispute that will simply repeat if the mandate is re-presented. The workflow for a non-retriable return is mandate re-registration (fresh UMRN) or a collections contact, not a retry.
When does Section 138 of the Negotiable Instruments Act apply to a NACH bounce, and when does Section 25 of the PSSA?
Both apply. Section 138 NI Act was extended by the 2015 and 2018 amendments to cover electronic modes of payment, and the criminal-side machinery — demand notice within thirty days of dishonour intimation, fifteen-day payment window for the drawer, criminal complaint within one month of the expiry of that window — reads onto a bounced NACH mandate the same way it reads onto a bounced cheque. Section 25 of the Payment and Settlement Systems Act 2007 is the parallel electronic-payment offence, with penalties of imprisonment up to two years or fine up to twice the amount of the failed transfer. Practice in Indian courts is to invoke both provisions in the same complaint where the facts support it — the R01 return file entry is prima facie evidence of insufficient funds under both statutes. The interest recovery runs on Section 80 NI Act at eighteen per cent per annum from the presentation date until realisation where the underlying contract does not specify a separate default rate.
The mandate was cancelled by the payer between presentation and return. Which return code appears, and can I still recover the amount?
The return code is R25 (Mandate Cancelled by Account Holder). The payer retains the statutory right to cancel a NACH mandate at any time by notifying their bank; the cancellation typically takes four to ten business days to propagate through NPCI to the originator, and a presentation submitted before the cancellation is fully propagated will return with an R25 code. The amount is still recoverable — the mandate cancellation is a payment-mechanism withdrawal, not a debt cancellation — but the recovery route is contractual rather than a re-presentation. The originator must serve the demand notice on the underlying contract terms, offer the payer an alternative payment mode (UPI Autopay, e-NACH re-registration on the same or a different account, direct bank transfer), and route the residual balance to the collections queue if the payer does not respond within the notice window.
When does the manual NACH bounce reconciliation stop being sustainable?
The threshold most Indian originators hit is around 500 active mandates presented per month. Below that count, a single analyst can pull the daily return file, extract the UMRN and reason code for each rejected entry, post the reversal journal, route retriable codes to the retry queue, and hand non-retriable codes to the collections desk inside the Days 1 to 5 bank reconciliation window. Above 500 mandates — or above the point where the R01 retry queue and the R25 mandate re-registration queue each need daily rather than weekly attention — the manual cycle stops fitting inside a Days 1 to 5 rhythm and becomes a rolling exception queue. The finance team then either adds headcount or moves the return-file parsing, the UMRN match, and the reason-code routing onto continuously refreshed detection where the workflow queues update as each return file lands.
Content authored by practitioners with experience at Amazon India, Intuit QuickBooks, and the Tata Group. Meet the team →
- ▸ Section 25, Payment and Settlement Systems Act 2007 — Where an electronic funds transfer initiated by a person from a bank account maintained by him for the payment of any amount of money to another person cannot be executed on the ground that the amount of money standing to the credit of that account is insufficient to honour the transfer instruction or that it exceeds the amount arranged to be paid from that account by an agreement made with the bank, such person shall be deemed to have committed an offence and shall, without prejudice to any other provisions of this Act, be punished with imprisonment for a term which may extend to two years, or with fine which may extend to twice the amount of the electronic funds transfer, or with both. This is the electronic-payment equivalent of Section 138 of the Negotiable Instruments Act and the statute anchor for the criminal-side escalation on a NACH mandate returned for insufficient funds under code R01.
- ▸ Section 138, Negotiable Instruments Act 1881 (as amended) — Where any cheque drawn by a person on an account maintained by him with a banker for payment of any amount of money to another person from out of that account for the discharge, in whole or in part, of any debt or other liability, is returned by the bank unpaid either because of the amount of money standing to the credit of that account is insufficient to honour the cheque or that it exceeds the amount arranged to be paid from that account by an agreement made with that bank, such person shall be deemed to have committed an offence. The section is triggered on receipt of the dishonour intimation and requires a written demand notice within thirty days under sub-section (b), a fifteen-day payment window for the drawer under sub-section (c), and a criminal complaint within one month of the expiry of that window. For NACH debits, the Section 138 machinery reads together with Section 25 of the Payment and Settlement Systems Act 2007 following the 2015 and 2018 amendments that extended the dishonour regime to electronic payment instructions.
- ▸ Section 80, Negotiable Instruments Act 1881 — When no rate of interest is specified in the instrument, interest on the amount due thereon shall, notwithstanding any agreement relating to interest between any parties to the instrument, be calculated at the rate of eighteen per centum per annum, from the date at which the same ought to have been paid by the party charged, until tender or realisation of the amount due thereon, or until such date after the institution of a suit to recover such amount as the Court directs. The provision governs the interest recoverable on a dishonoured NACH mandate where the underlying contract with the payer does not specify a separate default rate — the finance team's recoverable ledger against the payer runs at the eighteen per cent statutory rate from the presentation date until realisation or a court-directed alternative date.
- ▸ NPCI NACH Procedural Guidelines and NACH Debit ACH File Format — The NACH Debit product operates on a T+1 or T+2 return cycle where the destination bank returns rejected mandates to NPCI, and the return file is made available to the presenting bank within one to two business days from the presentation date. Every mandate carries a Unique Mandate Reference Number (UMRN) — a twenty-character alphanumeric identifier assigned at mandate registration and used as the primary match key across presentation, return, retry, and cancellation. The return file entry for each failed debit carries the UMRN, the return reason code (R01 through R99 series covering approximately one hundred codes for insufficient funds, account closed, mandate cancelled, stop payment, invalid amount, and related conditions), and the original presentation amount. A mandate may be re-presented within the same billing cycle subject to the originator's retry policy, typically a maximum of two retry attempts within three to five business days of the original return.
- ▸ RBI Master Direction on Digital Payment Security Controls (February 2021, as amended) — Regulated entities operating payment systems (banks, NBFCs, PSPs) must maintain end-to-end audit trails of every payment instruction, return, and reversal, with tamper-evident logs retained for the period specified in the Prevention of Money-laundering (Maintenance of Records) Rules 2005 and the RBI's Master Circular on Fraud Risk Management. For NACH originators, the audit-trail obligation attaches to the mandate lifecycle end-to-end: registration, presentation batches, return files, retry attempts, mandate cancellations, and any Section 25 PSSA 2007 or Section 138 NI Act escalation letters served on the payer. A reconciliation working paper that cannot be reconstructed from source records fails the audit-trail requirement irrespective of whether the underlying dispute is eventually recovered.