Content authored by practitioners with experience at Amazon India, Intuit QuickBooks, and the Tata Group. Meet the team →
An NBFC with 40,000 active borrowers maintains a mandate register with 40,000 NACH mandate records. Over a 12-month cycle, a portion of those mandates will be cancelled by borrowers through their banks, amended due to account changes, or allowed to expire without renewal. The internal mandate register does not receive automatic updates from NPCI when these events occur. By the time the register has drifted 5–10% from NPCI reality, the lender is presenting mandates that cannot be honoured — generating avoidable return codes and understating the effective debit success rate.
What NACH Mandate Management Reconciliation Is
NACH mandate management reconciliation is the periodic process of comparing every active UMRN in the internal mandate register against NPCI’s mandate database to identify status discrepancies: mandates that appear active internally but are cancelled at NPCI, mandates that have expired but remain in active status, and mandates where the permitted debit amount or frequency has been amended without the internal record being updated.
In India, NPCI manages all NACH mandates centrally. When a borrower cancels their NACH debit instruction through their bank, the bank updates NPCI’s mandate database. The originator’s internal register is not automatically updated. The mismatch surfaces only when a debit presentation fails with return code 25 (Mandate Cancelled by Account Holder). Regular mandate register reconciliation prevents this by proactively identifying and removing stale mandates before the batch submission stage.
How Mandate Register Drift Happens
Borrower-Initiated Cancellations
A borrower can cancel their NACH mandate by submitting a request to their bank — without informing the lender. The bank processes the cancellation through NPCI within 2–3 business days. The lender’s mandate register continues to show the UMRN as Active. The next debit presentation returns with code 25.
Amendments Processed at the Bank, Not Updated in the LMS
When a borrower requests an amendment (frequency change, amount modification) through their bank, NPCI updates the mandate record. If the LMS team is not notified and does not reflect the amendment, subsequent batch presentations may exceed the amended mandate limit — generating return code 02 (Exceeds Arrangement).
Expired Mandates in Active Status
NACH mandates carry an end date. Mandates created with a fixed end date that passes without renewal remain in active status in many LMS configurations because the expiry check is not automated. Presenting against an expired UMRN generates a non-retriable return.
Mandate Register Reconciliation Process
Weekly UMRN-Level Status Check
The reconciliation system pulls the current mandate status from the NPCI portal or through the presenting bank’s API for each active UMRN in the internal register. Any UMRN where NPCI status differs from internal register status is flagged as a mismatch. The reconciliation output is a mismatch report classified by type: Cancelled, Expired, Amended, or Suspended.
Mismatch Resolution and Register Update
Each mismatch class has a defined resolution action. Cancelled mandates are removed from the active batch queue and a mandate re-registration workflow is triggered. Expired mandates are marked for renewal or loan-account review. Amended mandates have their register records updated to match NPCI’s amended terms before the next batch.
Mandate Status Mismatch Reference Table
| Mismatch Type | Cause | NACH Impact | Resolution Action | Timeline |
|---|---|---|---|---|
| Active in register, Cancelled at NPCI | Borrower cancelled via bank without notifying lender | Return code 25 on next presentation | Remove from batch queue; trigger mandate re-registration | Immediate on detection |
| Active in register, Expired at NPCI | Mandate end date passed; register not updated | Non-retriable return on next presentation | Mark for renewal; collect via alternative method during gap | Before next batch cycle |
| Active in register, Amount Amended at NPCI | Borrower reduced debit limit via bank | Return code 02 if presented above new limit | Update register to reflect amended amount; adjust batch debit | Before next batch submission |
| UMRN in register, Not Found at NPCI | Registration failed or UMRN entered incorrectly | Presentation rejected outright | Verify UMRN with presenting bank; re-register if needed | Before next batch cycle |
| Active at NPCI, Missing from register | Mandate registered by bank branch but not synced to LMS | EMI not collected despite valid mandate | Add UMRN to register; verify borrower account mapping | Within 24 hours of discovery |
India-Specific Compliance: Pre-Batch Mandate Validation
The Indian NACH framework does not build in automatic notification to originators when a mandate is cancelled or amended by the account holder. This is a known gap that RBI and NPCI have acknowledged in the context of recurring payment mandates more broadly. The practical consequence for lenders is that mandate register reconciliation is a pre-batch control, not a post-return correction.
Running NACH batch reconciliation without a pre-batch mandate validation step means a percentage of every batch will generate avoidable code 25 and code 02 returns — returns that a simple register check 48 hours before submission would have caught. For organisations managing multiple banks and large mandate books, reconciliation software India with direct NPCI mandate status integration removes the manual checking step entirely.
The standards for NACH mandate registration, amendment, and cancellation are defined by NPCI NACH product overview.
For the broader NACH reconciliation workflow, the NACH reconciliation guide covers the full debit-to-LMS lifecycle. The what is NACH in India article explains UMRN structure and mandate registration. For organisations that use virtual accounts to receive NACH settlement credits, virtual account reconciliation India covers the matching logic for pooled collection accounts.