Content authored by practitioners with experience at Amazon India, Intuit QuickBooks, and the Tata Group. Meet the team →
Most NBFC reconciliation teams treat NACH as a treasury task: confirm the batch credit landed in the collection account, mark the batch as settled, and close the day. The actual reconciliation — matching each mandate-level outcome to the borrower’s loan record and updating the DPD counter — is a separate process, often running 24 to 48 hours behind. For an NBFC with 10,000 active NACH mandates per batch cycle, that lag translates directly into understated portfolio risk and inaccurate NPA provisioning.
What NACH NBFC Lender Reconciliation Involves
NACH NBFC lender reconciliation is the process of matching every outcome in a NACH debit batch — successful debit, partial settlement, or return with reason code — back to the individual borrower’s loan record in the loan management system (LMS) and updating the DPD status accordingly.
The reconciliation equation has three parts: the batch submitted (total mandates presented, total amount), the batch settled (mandates honoured, amount credited to collection account), and the batch returned (mandates rejected, with NPCI return codes identifying the reason). The difference between submitted and settled is the return population — and each return must be classified and posted to the LMS before DPD counting begins.
This is an India-specific compliance requirement. Under RBI’s Income Recognition and Asset Classification (IRAC) norms, the DPD counter starts from the contractual due date, not the processing date. An NBFC that delays return posting by 5 days per cycle will understate DPD by 5 days per cycle — compounding over multiple billing periods before the error surfaces in audit or regulatory inspection.
The NACH Lifecycle for an NBFC
Step 1: Batch Preparation from the LMS
On D-1 (one business day before the scheduled debit date), the LMS or collections system generates the NACH batch file. Each row in the batch corresponds to one active mandate: UMRN, borrower account details, debit amount, and due date. The batch is submitted to the presenting bank in the NPCI-specified ACH file format.
Step 2: Settlement Confirmation
On the settlement date, the presenting bank confirms which mandates were successfully debited. A bulk credit for the settled amount arrives in the NBFC’s collection account. The bank’s transaction credit references the batch ID, not individual UMRNs — so the bank statement credit alone is insufficient for mandate-level reconciliation.
Step 3: Return File Processing
NPCI routes failed mandates back to the presenting bank within T+1 or T+2 business days. The return file contains each failed mandate’s UMRN and the NPCI return reason code explaining the rejection. The NBFC’s reconciliation system must parse this file and classify each return as retriable, non-retriable, or dispute before any LMS update occurs.
Step 4: LMS Update and DPD Posting
Each return code maps to a specific LMS action. Code 01 returns remain in an outstanding EMI status with a retry scheduled. Code 20 and 25 returns trigger immediate DPD posting and a mandate re-registration workflow. The DPD counter must start from the original due date on the first post, regardless of when the return file was received.
NACH Lifecycle Stage Reference
| Lifecycle Stage | Data Source | Match Key | LMS Field Updated | SLA |
|---|---|---|---|---|
| Batch submission | LMS export | UMRN + Loan ID | Batch submitted flag | D-1 before due date |
| Settlement confirmation | Bank credit advice | Batch ID + Date | EMI paid, collection amount | Same day as credit |
| Return file receipt | NPCI return file | UMRN | Return code, outstanding EMI | T+1 or T+2 from presentation |
| DPD posting (non-retriable) | Return file | UMRN → Loan ID | DPD counter, overdue amount | Same day as return receipt |
| Retry submission (code 01) | Collections queue | UMRN | Retry attempt count | Within 3–5 business days |
| Mandate re-registration trigger | Non-retriable flag | UMRN → Loan ID | Mandate status, collections escalation | Within 24 hours of return |
India-Specific Compliance: DPD Accuracy and NPA Provisioning
The connection between NACH reconciliation accuracy and NPA provisioning is direct and quantified. Under RBI’s IRAC norms, a loan becomes sub-standard (Stage 2 under Ind AS 109) when it is overdue for more than 30 days, and NPA when overdue for more than 90 days. Each day of DPD posting delay shifts these thresholds forward by exactly one day.
An NBFC running 50,000 NACH debits per cycle with 8% return rates and a 5-day reconciliation lag has approximately 4,000 accounts with understated DPD at any given point. At average loan sizes of ₹2–5 lakh, that represents ₹80–200 crore in loan book exposure where provisioning calculations are off by 5 DPD days each cycle.
RBI’s Supervisory Returns (NBS-7 and NBS-9) require NBFCs to report portfolio-at-risk figures derived from DPD data. Inaccurate NACH reconciliation flows directly into inaccurate regulatory filings.
For high-volume NACH EMI collection, NACH batch reconciliation with UMRN-level LMS matching eliminates the manual lag between return file receipt and DPD posting. Finance teams evaluating reconciliation software India for NBFC use should confirm that the system supports direct LMS integration and same-day return code classification.
The mandate specifications, batch submission formats, and return reason code standards are published by NPCI NACH product overview.
For broader NACH context, the NACH reconciliation guide covers the full debit lifecycle. The what is NACH in India article covers mandate structure and UMRN basics. For scenarios where the settled amount does not match the presented amount, partial payment reconciliation India describes the posting logic for net-settled collections.