NACH Mandate Processing in Depth: From Creation to Activation

NACH is the centralised bulk payment system run by NPCI that allows banks and institutions to collect recurring payments from customers through mandates, and to make bulk credit payments such as salaries and dividends. A mandate is the customer authorisation that allows a specific institution, called the user institution, to debit a specific bank account for a specific amount on a specific frequency, such as monthly. The mandate carries the customer name, the bank account number, the IFSC, the maximum amount, the frequency, the start date and the end date, and it is registered with the customer bank, called the destination bank. Without a registered mandate, no NACH debit can be presented, which is why mandate processing is the foundation of the whole system. The mandate lifecycle has clear stages that a BA must model as a state machine, creation, submission, validation, activation, amendment, cancellation and expiry. Creation happens when the customer fills in the mandate form or completes an electronic mandate on the institution website or app. Submission is when the institution sends the mandate to the destination bank through NPCI, either as a scanned physical form or as an electronic record. Validation is when the destination bank checks the account number, the name, the signature or the electronic authentication, and either accepts or rejects the mandate with a reason. Activation is when the mandate becomes live and the institution can start presenting debits, and the customer receives a confirmation message with the mandate reference number. A physical NACH mandate is a paper form that the customer signs, and it follows a slower, manual path. The customer fills in the bank details and signs the form, the institution scans the form and uploads it to NPCI, NPCI forwards it to the destination bank, and the bank verifies the signature against its records before accepting or rejecting it. This process can take seven to ten working days, and rejections are common when the signature does not match, the account number is wrong, or the form is incomplete. The BA must specify the scanning quality, the image format, the rejection reason codes, and the customer communication for each rejection, because a customer whose EMI mandate is rejected may not know until the first EMI bounces. An electronic NACH mandate, known as e-NACH, replaces the paper form with an online authentication using net banking, a debit card, or Aadhaar based e-sign. The customer selects the bank, logs in to net banking or authenticates with a debit card and OTP, reviews the mandate details on the bank page, and confirms, and the bank registers the mandate almost immediately. E-NACH is faster, often activated within two to three working days, and it reduces signature mismatch rejections because the authentication is done by the bank itself. A BA must document the bank coverage, because not every bank supports every e-NACH mode, and must specify the fallback to physical mandate when the customer bank does not support e-NACH or when the online authentication fails. From a requirements perspective, the mandate module must store the mandate reference, the customer and account details, the amount and frequency, the status history with timestamps, and the source of the mandate, whether physical or electronic. It must support amendments, such as changing the amount or the end date, and cancellations initiated by the customer, the institution or the bank. It must also enforce the rule that a debit can never exceed the mandate maximum amount, and that a debit cannot be presented after the mandate end date. A real example is a home loan EMI of 45,000 rupees per month from a State Bank of India account. The mandate must carry the exact amount, the monthly frequency, and the loan account as the reference, so that the customer and the bank can both identify the collection.