NACH Debit and Credit: Presentation, Settlement and Returns

A NACH debit presentation starts when the user institution prepares a file of all the debits due on a given date and submits it to NPCI, usually one working day before the debit date. NPCI validates the file, splits it by destination bank, and forwards each debit to the customer bank. The customer bank checks the mandate, the account balance, the account status and any stop instructions, and then either honours the debit or returns it with a reason code. The honoured debits are settled through the NPCI settlement account at the Reserve Bank of India, and the user institution receives the funds, usually on the same day or the next working day. The BA must document the file format, the cut off time for submission, and the response file that confirms which debits were honoured. Presentation and settlement follow a fixed cycle that the BA must capture in the operations calendar. The institution submits the presentation file on day zero, NPCI processes it overnight, the destination bank responds on day one, and settlement happens on day one or day two depending on the session. NPCI runs presentation and return settlement sessions during the day, and may create multiple sessions for the same product to give banks more time to process inward files; a debit presented after the cut off rolls to the next session. The exact session count and cut-offs are set by NPCI and vary, so an operations calendar must use the current NPCI schedule. Source: NPCI NACH Procedural Guidelines version 3, June 2018, section 10.4. The institution must not present a debit before the mandate start date, after the end date, or for an amount above the mandate maximum, because NPCI will reject the file. A BA should produce a calendar that shows the presentation date, the debit date and the expected settlement date for each product, so that the finance team can forecast cash flow accurately. Failure handling is where NACH knowledge becomes practical, because a failed EMI debit can damage a customer credit score and trigger penalty charges. Common return codes include insufficient funds, account closed, account frozen, mandate not registered, amount exceeds mandate limit, and signature mismatch for physical mandates. Each code has a different action. Insufficient funds may justify a retry after a few days, while account closed requires the customer to provide a new bank account and a new mandate. The system must store the return code, the return date and the retry count for every failed debit, and must never retry a debit indefinitely, because repeated presentations against a closed account waste processing fees and annoy the customer. The BA should specify the retry policy, the maximum retries, and the customer notification for each return code. NACH credit is the other side of the system, and it is used for bulk payments from one institution to many beneficiaries, such as salary payments, pension disbursements, dividend payments and government subsidies. The institution prepares a credit file with the beneficiary account details and amounts, submits it to NPCI, and NPCI forwards the credits to the destination banks, which credit the beneficiary accounts. Unlike a debit, a credit does not need a mandate, but it does need accurate account details, because a credit to a wrong account is difficult to recover. A BA working on a payroll or disbursement project must specify the file validation rules, the account number and IFSC checks, the handling of failed credits, and the reconciliation of the total file amount against the settlement amount. The NPCI guidelines a BA must know include the file formats, the session timings, the mandate registration timelines, the return code list, the dispute and complaint handling process, and the penalty for late submission or incorrect files. The guidelines also require the user institution to inform the customer before the first debit, to provide a mandate copy on request, and to stop presenting debits immediately after a mandate is cancelled. A BA should maintain a compliance checklist that maps each NPCI rule to a system requirement and a test case, and should include the NACH flows in the user acceptance test scenarios. For example, a test case for a loan EMI of 28,500 rupees from an HDFC Bank account should cover a successful debit, an insufficient funds return, a mandate cancellation, and a debit presented after cancellation that must be blocked by the system.