NACH Batch Reconciliation Software for NBFCs and Lenders

NACH batch reconciliation is the process of matching NPCI-prescribed batch debit files against loan management system records and settlement receipts at the mandate level. Each NACH batch contains a header record, individual debit records identified by UMRN and loan account number, and a footer with batch totals. When the sponsor bank processes the batch, it credits a single net settlement NEFT for all successful debits and returns individual records for failures. Reconciliation requires matching each debit record outcome — success or return — to the corresponding EMI schedule entry in the LMS, confirming that the net settlement NEFT equals the sum of successful debits, and classifying every return by code for recovery action. This is structurally different from standard bank reconciliation because the incoming settlement is a net figure, not a transaction-level credit.

TransactIG classifies all six primary NACH return codes and routes each to a configured recovery path. Code 01 (Insufficient Funds): balance below EMI amount at debit time — system flags for retry after salary credit date and triggers borrower notification. Code 05 (Stop Payment): customer instructed bank to stop the mandate — flagged for collections escalation and legal notice workflow. Code 20 (Account Closed): bank account no longer active — LMS is updated to invalid account status and the mandate requires re-registration with new account details. Code 25 (Account Blocked or Frozen): RBI order, court order, or bank-initiated freeze — routed to legal team; retry is not available until the freeze is lifted. Code 27 (Mandate Cancelled): borrower revoked the NACH mandate directly at the bank — triggers mandate re-registration workflow and loan health review. Code 09 (Signature Mismatch): physical mandate signature does not match bank records — routed for mandate re-submission with fresh signature.

A NACH batch submitted with 1,000 debit records may have 800 successful debits and 200 returns. The sponsor bank credits a single net settlement NEFT to the lender's account for the 800 successful debits — the NEFT value is the sum of 800 EMI amounts, not the full 1,000. The 200 return records arrive in a separate NPCI return file between T+1 and T+3 after the debit date. Reconciling this requires three steps: first, matching the net settlement NEFT to the total of individual success records to confirm no discrepancy in the bank's net calculation; second, matching each of the 200 return records to the corresponding debit record by UMRN and loan account number to confirm which mandates failed; third, updating the LMS with success confirmation for 800 accounts and return code classification for 200 accounts. If bounce charges are debited separately — ₹300 to ₹750 per return — these must also be matched to the corresponding return records. Without automation, the partial settlement creates an unresolved difference that ages as unexplained variance.

Yes. Prepayments and foreclosures require adjustments to the active NACH mandate schedule that standard batch reconciliation does not cover natively. When a borrower makes a partial prepayment, the scheduled EMI amount decreases from the next cycle. TransactIG tracks the expected EMI per UMRN from the LMS and flags any debit amount mismatch — whether the mandate collected the old EMI or the revised EMI — as a variance requiring review rather than treating it as an unexplained shortfall. For foreclosures, the NACH mandate must be cancelled after the final EMI is collected. TransactIG monitors mandate status against loan closure records in the LMS: if a debit attempt is made for a UMRN linked to a closed loan account, it is flagged immediately rather than posted as an unrecognised receipt. The UMRN lifecycle — from mandate registration through to cancellation — is tracked as a continuous record across the loan tenure.

NPCI specifies a fixed-width or delimited file format for NACH batch submission and return files — available on the NPCI NACH product documentation. The format includes a file header with sponsor bank details and debit date, individual debit records with UMRN, account number, IFSC, amount, and mandate reference, and a footer with record count and total amount. TransactIG's batch parser reads this format natively. On the input side, batch files are ingested from the sponsor bank SFTP or uploaded directly from the NPCI portal. Each debit record is parsed and matched to the corresponding LMS record using UMRN as the primary key and loan account number as the secondary key. Return files, which follow the same format with an additional return code field, are parsed and matched to the original debit records from the same batch. The parser handles both the T+0 batch submission confirmation and the T+1 to T+3 return files within a single reconciliation run.

TransactIG NACH reconciliation deployments typically complete in 2 to 4 weeks, with most NBFCs completing in 3 weeks. Week one covers UMRN field mapping from the LMS export, EMI schedule integration, and NPCI file format configuration. Week two covers integration testing with live batch files — ingesting historical NACH data and validating match rates against known outcomes. Week three runs the system in parallel with the existing reconciliation process. Week four, if needed, covers production cutover and LMS update workflow configuration. There is no code development in this timeline. Return code routing rules, retry eligibility logic, and LMS update triggers are configured through TransactIG's rule interface without software development. NBFC teams handling NACH in-house typically go live in 3 weeks; teams with more complex LMS integrations requiring structured export mapping may take the full 4 weeks.