Content authored by practitioners with experience at Amazon India, Intuit QuickBooks, and the Tata Group. Meet the team →
NACH-based collection and disbursement is the operational backbone of Indian lending, insurance, and subscription businesses. For NBFCs, banks, and any corporate running bulk payment workflows, NACH reconciliation involves a distinct set of terms — mandate identifiers, batch references, return codes, and settlement timing conventions — that differ materially from standard bank reconciliation. This glossary covers every term your operations and finance teams encounter in NACH processing and reconciliation.
NACH Fundamentals
NACH (National Automated Clearing House) — A centralised clearing system operated by NPCI that processes bulk debit and credit transactions between banks in India. NACH replaced ECS as the standard mechanism for recurring payments such as loan EMIs, SIP deductions, insurance premiums, and utility bills. All participating banks connect to NACH through NPCI’s infrastructure.
ECS (Electronic Clearing Service) — The predecessor to NACH, managed directly by the Reserve Bank of India. ECS operated as a series of regional clearing houses. It was formally discontinued by the RBI in December 2020, with all participants migrated to NACH. Legacy loan portfolios may still reference ECS mandate IDs that need to be mapped to NACH equivalents for reconciliation.
NPCI (National Payments Corporation of India) — The umbrella organisation established by RBI and IBA that operates India’s core retail payment systems — including NACH, UPI, RuPay, IMPS, and FASTag. NPCI sets the technical standards, return code framework, and settlement rules for NACH.
ACH Credit — A NACH transaction type where the initiating entity (sponsor bank) pushes funds to the beneficiary’s bank account. Used for payroll, vendor payments, subsidy disbursements, and loan disbursements. ACH Credits settle T+1. The consolidated credit arriving in the destination bank is identified by the sponsor bank’s reference number rather than an individual UTR.
ACH Debit — A NACH transaction type where the initiating entity (sponsor bank, acting on behalf of the destination institution or lender) pulls funds from the customer’s bank account based on a pre-registered mandate. Used for EMI collection, SIP deductions, and insurance premium collection. The customer’s bank account is debited on the presentation date if the mandate is valid and funds are available.
Reconciliation Lag (T+1 settlement on NACH credits) — The one-business-day delay between a NACH credit batch being submitted and the funds appearing in destination bank accounts. Lenders and corporates must account for this lag when reconciling disbursement records against bank statement credits. A disbursement batch initiated on a Friday will reflect in accounts on Monday (or Tuesday if Monday is a holiday), not Friday.
RTGS vs NEFT vs NACH — RTGS (Real Time Gross Settlement) processes transactions individually in real time, minimum Rs 2 lakh, suitable for large-value payments. NEFT (National Electronic Funds Transfer) processes in half-hourly batches throughout the business day, no minimum. NACH is a batch system for recurring, high-volume, lower-value transactions. Finance teams use all three systems; reconciliation must parse each system’s transaction reference format correctly.
Mandate and Processing Terms
Mandate — A formal authorisation registered by a bank account holder allowing a lender, insurer, or service provider to debit their account periodically for a specified amount and duration. Mandates are the legal foundation of NACH debit transactions. A valid, active mandate is a prerequisite for presenting a NACH debit.
eNACH (API-based mandate) — A digital mandate registration process where the customer authenticates and registers the debit mandate electronically — via net banking login, debit card OTP, or Aadhaar OTP — without physical paperwork. eNACH mandates registered via API are processed faster than physical mandates and are now the standard for fintech lenders and digital insurance players.
Physical NACH — A mandate registered using a signed paper form submitted to the customer’s bank. Physical NACH is still used where customers do not have internet banking access or where regulatory requirements mandate wet signatures. Physical NACH mandates take longer to activate (typically 10–30 working days) and are harder to track than eNACH.
eMandate via Net Banking / Debit Card / Aadhaar OTP — Three sub-modes of eNACH. Net banking eMandate requires the customer to log in to their bank’s netbanking portal to authenticate. Debit card eMandate uses the card number and PIN/OTP. Aadhaar OTP eMandate links the bank account to the Aadhaar biometric identity for authentication. Aadhaar-based eMandate is the fastest to process but requires the account to be linked to Aadhaar.
UMRN (Unique Mandate Reference Number) — A 20-character alphanumeric code assigned by NPCI to each registered NACH mandate. UMRN is the primary key for mandate lookup, amendment, and cancellation. Lenders store the UMRN against each loan account; it is required to present NACH debit instructions. Reconciliation of mandate status must reference UMRN as the unique identifier.
Sponsor Bank — The bank through which the institution (lender or initiator) submits its NACH batch files and receives return files. The sponsor bank is responsible for formatting the batch in the NPCI-prescribed format, submitting it within the cut-off window, and delivering return files to the initiator. Errors in the sponsor bank relationship (wrong format, missed cut-off) affect the entire batch.
Destination Bank (NACH) — The bank at which the customer’s account is held — the bank that receives and processes the debit instruction. The destination bank validates the mandate (via UMRN), checks the account balance, and either processes or returns the debit. Return codes are generated by the destination bank.
Presentation — The act of submitting a NACH debit instruction to be processed on a specific date. A presentation date is the date on which the debit is expected to hit the customer’s account. Lenders schedule presentations to align with EMI due dates. The difference between presentation date and actual debit date is typically zero or one business day depending on batch timing.
Batch File — A structured file (in the NPCI-prescribed format) containing multiple NACH debit or credit instructions submitted together to the sponsor bank for processing. Batch files have a header record, transaction records (one per mandate or beneficiary), and a trailer record with control totals. The batch reference number in the header is used to reconcile the batch-level credit or debit against individual transaction records.
Consolidated Credit — In NACH credit disbursements, the sponsor bank receives a single gross amount from the initiating entity and then credits individual beneficiary accounts. From the initiator’s perspective, a single debit from its bank account funds all individual credits. Reconciliation must map this single bank debit to each individual disbursement in the batch file.
UTR on NACH Credits — NACH credit transactions received by beneficiary banks carry a UTR assigned by the beneficiary’s bank upon credit. This UTR is different from the batch reference number at the sponsor bank level. Finance teams must use the beneficiary-side UTR when matching bank statement credits to disbursement records.
EMI (Equated Monthly Instalment) — The fixed monthly payment made by a borrower covering principal repayment and interest on a loan. NACH debit is the most common mechanism for EMI collection in India. Reconciliation of EMI receipts involves matching successful NACH debit confirmations against the expected EMI schedule for each loan account.
Repayment Schedule — The amortisation table for a loan, showing the due date, principal, interest, and total EMI amount for each payment period. NACH reconciliation verifies whether actual collections match the repayment schedule — identifying bounces, partial payments, prepayments, and excess collections.
Loan Disbursement — The transfer of sanctioned loan funds to the borrower’s bank account, typically via NACH credit or RTGS/NEFT for larger amounts. Disbursement reconciliation matches the disbursement record in the loan management system to the bank debit and the corresponding UTR or NACH batch reference.
Return Codes and Exception Handling
NACH Return — A NACH debit instruction that the destination bank was unable to process, returned to the sponsor bank with a reason code. Returns are received in a return file from the sponsor bank on T+1. Finance teams must process returns promptly to update loan management systems, trigger collection workflows, and adjust expected cash inflows.
Return Code — A two-character code assigned by the destination bank to identify the reason for returning a NACH debit. The NPCI framework defines codes R01 through R29. Key codes include:
- R01 — Insufficient funds. The account balance was below the debit amount at the time of presentation. The most common return reason and typically indicates temporary financial stress or poor timing.
- R02 — Account closed. The bank account specified in the mandate has been closed. Requires the lender to re-collect valid account details and register a new mandate.
- R04 — Invalid account number. The account number in the batch file is not found at the destination bank. Often caused by a data entry error at mandate registration. Requires verification and correction before re-presentation.
- R14 — Representative payee deceased or unable to continue in that capacity. Less common but significant for lenders managing estate-related collections.
Bounce Rate — The percentage of NACH debit presentations that are returned in a given period. Bounce rate is a key operational and credit health metric for NBFCs and banks. A high bounce rate in a specific cohort signals early-stage delinquency. Reconciliation systems must calculate bounce rate by loan product, geography, and mandate type to support collection analytics.