How eNACH mandates work
The mandate is the quiet foundation of digital collections — and the step where sloppy setup creates months of bounce pain. Here is the whole mechanism in plain language.
What a NACH mandate is
NACH (National Automated Clearing House) is NPCI’s rail for recurring debits. A mandate is the borrower’s standing authorisation letting a lender debit their bank account — up to a cap, at a frequency, for a period. eNACH is the digital registration of that authorisation: instead of a signed paper form travelling to the bank, the borrower approves online via net-banking or debit card.
For a lender, an active mandate converts collections from a chase into a schedule: EMIs are presented automatically and the borrower has to do nothing on a good day.
The fields that decide success or failure
Most mandate pain traces back to three fields set at registration: the cap, the frequency and the account details. Destination banks validate these strictly, and errors surface either as registration rejections or — worse — as presentation failures months later.
- Cap (maximum amount) — must comfortably exceed any single debit you will present, including penalties after a bounce. Caps set exactly at the EMI strand the loan the first time a penalty accrues.
- Frequency — “Adhoc” (present as needed) is the flexible choice for lending, but some destination banks reject Adhoc and require a declared frequency like Monthly — the sponsor-bank rulebook matters.
- Account details — account number, IFSC and account type must match the bank’s records exactly; a penny-drop verification before registration catches most mismatches.
The lifecycle: register, present, reconcile
Registration: the borrower authorises via net-banking or debit card, the destination bank accepts or rejects, and the provider notifies the lender — typically by webhook. Presentation: on each due date the lender presents a debit under the mandate; success and failure again arrive as webhooks. Reconciliation: every outcome must land on the loan ledger, including the failures that trigger penalty accrual and follow-up.
Two operational rules separate clean books from messy ones: register the mandate before disbursal (leverage disappears the moment money moves), and never rely on webhooks alone — run a reconciler that sweeps for missed callbacks.
Re-loans and mandate reuse
Repeat borrowers are where mandate friction hurts most. If the existing mandate is on the same bank account and its cap covers the new schedule, reusing it removes an entire authorisation step from the re-loan journey. The care point is cancellation: when two loans share a registration, closing one must not cancel the rail out from under the other.
How Loano handles it
Loano derives cap, frequency and first-collection date server-side from the sanctioned terms — staff and borrowers only ever supply bank account details, so CRM and portal cannot disagree. Sponsor-bank quirks (like banks that reject Adhoc) are encoded once, penny-drop verification runs before payout, disbursal is gated on an active mandate, and umbrella reuse attaches qualifying mandates to re-loans with cancellation safety built in.
Rather see it than read it?
A 30-minute walkthrough with your own scenarios — from first lead to final rupee.
Book a demo