Content authored by practitioners with experience at Amazon India, Intuit QuickBooks, and the Tata Group. Meet the team →
An NBFC with 38,000 monthly EMI NACH mandates that reconciles weekly understates DPD by five to seven days per failed mandate, loses up to a third of bounce-charge recovery because the LMS bills late, and remits the partner bank's co-lending share days behind the contractual SLA.
Disaggregate every NACH batch credit into mandate-level outcomes keyed on UMRN, post success or failure with the NPCI return code to the LMS the same business day, classify each return code into retriable, non-retriable, or dispute, and emit a separate bounce-charge billing event for each retriable failure.
UMRN-to-loan-account master, NPCI return-code library (codes 01 through 99) classified by action, same-day LMS posting SLA, two-retry cap per cycle, bounce-charge billing rule respecting the RBI October 2023 fair-lending limits, and a co-lending partner remittance rule.
A daily collections MIS with bouncing-borrower segmentation, accurate DPD and NPA classification under IRAC norms, recovered bounce charges billed within one cycle, and contractually compliant co-lending remittance to partner banks.
Most NBFC operations teams view NACH EMI reconciliation as a treasury reconcile-the-batch task that can comfortably run weekly. The reality is the opposite: every day the batch return file is not disaggregated to the borrower record, the Days Past Due (DPD) counter is wrong, the partner bank in a co-lending arrangement is short-paid, and the bounce-charge invoice that the loan agreement entitles the lender to recover is not raised. For an NBFC presenting 38,000 EMI mandates a month, the lost recovery alone is material.
What NACH EMI Reconciliation Involves
NACH EMI reconciliation is the daily process of breaking apart each NACH-Debit batch outcome into mandate-level results, posting those results to the loan management system (LMS), and producing the collections MIS that drives next-day action.
The batch has three possible outcomes per mandate: successful debit (the borrower’s bank honoured the presentation), return with reason code (the borrower’s bank rejected the presentation, with an NPCI-standard code explaining why), and partial settlement (rare, but it occurs when the borrower’s bank applies a partial debit). Each outcome triggers a different LMS update, a different DPD treatment, and a different downstream action — billing the bounce charge, scheduling a retry, deregistering a closed-account mandate, or remitting a co-lending share.
The Daily NACH EMI Reconciliation Cycle
Step 1: Batch Preparation from the LMS
The LMS exports the day’s EMI batch on D-1, keyed by UMRN. The export must reconcile cleanly against the active mandate master — every UMRN in the export must exist, be active, and not be in a deregistration workflow. NBFCs that skip this pre-flight check routinely present on cancelled mandates and absorb avoidable return-code 16 (mandate not registered) charges.
Step 2: Settlement and Return File Receipt
On D-day, the presenting bank confirms which mandates settled and forwards the NPCI return file containing failed mandates with their reason codes. The bank credit to the NBFC’s collection account references the batch ID, not individual UMRNs, so the credit alone is not a reconciliation — it only tells you the aggregate settled.
Step 3: Mandate-Level Disaggregation
The reconciliation engine joins the batch presented (from the LMS), the batch settled (inferred from the bank credit minus the return value), and the return file (with UMRN and return code). The result is a per-UMRN outcome row that drives the LMS posting.
Step 4: Same-Day LMS Posting and MIS
Each per-UMRN row is written to the LMS the same business day. The DPD counter starts from the contractual due date — not the date of return file receipt. The reconciliation MIS emits the daily collection numbers, the return code histogram, and the bouncing-borrower segmentation that operations uses tomorrow morning.
NACH Return Code Library
NPCI’s return codes for NACH-Debit are commonly grouped into action bands. The table below shows the codes most NBFCs see in production, the classification, and the LMS action.
| Return Code | Reason | Classification | LMS Action |
|---|---|---|---|
| 01 | Insufficient Funds | Retriable | Retry within 3 to 5 business days, bill bounce charge |
| 02 | Stop Payment | Retriable with caution | Confirm with borrower before retry |
| 03 | Refer to Drawer | Retriable | Single retry, then escalate |
| 08 | Payer Deceased | Non-retriable | Deregister mandate, escalate to recovery |
| 10 | Account Closed | Non-retriable | Deregister mandate, re-register workflow |
| 11 | No Such Account | Non-retriable | Suspend mandate, validate borrower data |
| 12 | Amount Mismatch | Investigate | Check LMS amount field, may be system error |
| 13 | Account Inoperative | Retriable with caution | Borrower contact, single retry |
| 14 | Amount Exceeds Limit | Investigate | Check borrower’s debit limit on mandate |
| 16 | Mandate Not Registered | Non-retriable | Stop further presentations, re-register |
| 17 | Account Frozen | Non-retriable | Escalate, monitor for unfreeze |
| 22 | Customer Withdrawal | Retriable with caution | Confirm with borrower, may indicate dispute |
| 25 | Invalid UMRN | Non-retriable | Stop presentations, mandate audit |
| 33 | Customer Refused Debit | Dispute | Escalate, may require physical EMI collection |
The full library extends to 99 codes; the codes above cover the large majority of production volume for retail-lending NBFCs.
Worked Example: NBFC with 38,000 Monthly EMI Mandates
A mid-size NBFC presents 38,000 NACH-Debit mandates per month, distributed across four presentation dates (1st, 7th, 15th, and 25th). Average ticket size is ₹14,200. Monthly presentation value is ₹54 crore.
Production bounce rate is 9.2 percent (3,496 failed mandates per month). Of those, 71 percent return with code 01 (insufficient funds, retriable), 8 percent return with codes 10, 11, or 16 (non-retriable, mandate dead), and the balance split across codes 02, 03, 13, 22, and 33.
Before daily reconciliation: returns posted to the LMS on T+5 (the weekly cycle close). DPD on retriable bounces ran short by five days for the half of borrowers who paid on retry; for the half who did not, DPD was understated by five days entering the next cycle. The bounce charge — agreed in the loan agreement at ₹590 per failed presentation, within the RBI October 2023 fair-lending envelope — was billed on the next month’s statement only for borrowers who eventually paid; the chronic segment never saw the charge in their billing. Effective bounce-charge recovery: 62 percent (about ₹12.8 lakh per month against an addressable ₹20.6 lakh).
Co-lending partner remittance ran on the same weekly cycle, putting the NBFC three to four days behind the contractual T+2 SLA on roughly 40 percent of partner-share amounts.
After daily reconciliation: returns posted same business day, with the return code and classification. The bounce charge is billed the same day on every retriable failure, regardless of whether the borrower eventually pays — recovery on the chronic segment moves to a separate write-off track, but the receivable is on the books. Recovery climbed to 94 percent (about ₹19.4 lakh per month). DPD posts cleanly from the contractual due date, so the bouncing-borrower segmentation MIS — clean / occasional / persistent / chronic — actually reflects the portfolio. Co-lending remittance moves to T+1, comfortably inside the contractual SLA.
Want to size the cost of weekly versus daily NACH reconciliation for your own EMI book? Run the three-way match exception cost calculator — the same exception-cost model applies whether the exception is a vendor invoice or a bounced EMI.
Bouncing-Borrower Segmentation
Daily reconciliation makes a meaningful borrower segmentation possible. On a rolling 90-day window, every active borrower lands in one of four bands.
The clean band has zero bounces in the window. These borrowers stay on auto-debit with no intervention. They are typically 78 to 84 percent of an NBFC’s book.
The occasional band has one bounce that was recovered on retry. These borrowers are reminded by SMS or WhatsApp two business days before the next presentation. The intervention costs almost nothing and lifts the next-cycle success rate by 3 to 5 percentage points.
The persistent band has two or more bounces but eventually pays within the cycle. These borrowers move to a pre-debit voice call from the collections team. The bounce-charge accrual is closely tracked because the recoverable amount is material.
The chronic band has a failed cycle with DPD greater than 30. These borrowers move off auto-debit and into manual field collections. The reconciliation engine continues to track presentations only to keep the LMS aligned with mandate status — it does not drive collection action for this band.
RBI Co-Lending Implications
In a co-lending arrangement under the RBI September 2018 framework, the originating NBFC collects the EMI in its own collection account and remits the partner bank’s share within the contractually defined window. Most arrangements specify T+1 or T+2 from settlement; some go to T+5.
Daily NACH reconciliation produces the borrower-level success and return outcomes that drive the partner remittance file. Without it, the NBFC either remits late (a contractual breach) or remits the gross presented amount and reverses on receipt of the return file (which creates float and reverses on the partner’s books, both undesirable). The reconciliation engine should emit the partner remittance file as a downstream output of the daily cycle, keyed on the co-lending product identifier in the LMS.
Common Pitfalls
Presenting on cancelled mandates: a borrower has closed the account or revoked the mandate, but the LMS has not deregistered. The presentation generates code 10, 11, or 16 with an avoidable bank charge.
Treating code 01 retries as fresh presentations: the DPD counter does not reset on retry. NBFCs that reset DPD on a successful retry are understating portfolio risk.
Skipping bounce-charge billing on the chronic segment: the loan agreement entitles the lender to the charge regardless of whether the principal is eventually recovered. Not billing it is a recovery write-off, not a customer benefit.
Aggregating co-lending remittance to the partner: the partner is contractually entitled to a borrower-level remittance file, not a lump sum. Aggregation hides which borrowers are paying and which are not, which the partner may treat as a material disclosure failure.
Closing Note
A 38,000-mandate book reconciled weekly is a book where the LMS lags the truth by five business days, the bounce-charge recovery is a third lower than the loan agreement permits, and the co-lending partner is reading week-old data on a T+2 contract. None of these problems require a new product or a new mandate type — they require the daily reconciliation cycle that NACH was designed to support. The accuracy returns are visible inside one billing month.