NACH & eNACH · recurring debits
Agree once.
Debit every month.
A NACH mandate is a customer's standing permission for you to debit their bank account. This guide covers how mandates are registered, what each debit goes through, why debits bounce and what to do when they do.
- Runs on
- Bank accounts
- Operated by
- NPCI
- Best for
- EMIs, premiums, SIPs
- 02 JanMandate registered by eNACHUp to ₹8,000 · monthly · until cancelledActive
- 05 FebDebit presented · EMI 1₹6,450Paid
- 05 MarDebit presented · EMI 2₹6,450Paid
- 05 AprDebit presented · EMI 3Returned: insufficient balanceBounced
- 12 AprCustomer reminded, debit re-presented₹6,450Paid
- 05 MayDebit presented · EMI 4₹6,450Paid
- 20 MayLoan closed early; mandate cancelledNo further debits can be presentedCancelled
Who is involved in a NACH debit
A NACH debit passes through four parties. Knowing who does what explains most of the delays and bounce reasons you'll see.
- 01
You
The business collecting. You hold the mandate reference and decide when to present each debit.
- 02
Your sponsor bank
The bank that submits your mandates and debits into NACH on your behalf, and credits you.
- 03
NPCI
Operates NACH: routes mandates and debits between banks and settles between them.
- 04
The customer's bank
Approves or rejects the mandate, then honours or returns each debit from the customer's account.
Your sponsor-bank arrangement, including the identifier issued to you for NACH (often called a utility code), is set up during onboarding.
Registering a mandate: paper or eNACH
Before any debit, the customer has to approve a mandate. There are two ways to do it, and the choice mostly comes down to how many customers you onboard and how fast you need them active.
| Physical NACH | eNACH | |
|---|---|---|
| How the customer approves | Signs a paper mandate form | Approves online through their own bank |
| How it's checked | Signature and details checked by the customer's bank against its records | Authenticated by the bank, commonly with net banking or a debit card |
| Typical time to active | Days to weeks | Usually much faster |
| Common rejections | Signature mismatch, unclear form, wrong account details | Customer abandons the flow, or their bank doesn't offer eNACH |
| Fits | Customers without net banking or a debit card; in-branch sign-ups | Digital onboarding; most new customers |
Which registration methods are available on Peneu, and which banks support eNACH through them, is confirmed during onboarding.
What a mandate says
A mandate is precise about what you may and may not debit. Every debit you present is checked against it, so a mandate written too tightly causes bounces later, and one written too loosely worries customers at sign-up.
Set the maximum amount with some headroom for charges the customer has agreed to, choose a frequency that matches your schedule, and prefer an end date tied to the product (the loan tenure, the policy term) over “until cancelled” where the relationship has a natural end.
Debit mandate
Illustrative- Customer account
- Savings ••6621, and its bank
- Debit type
- Maximum amount (not fixed)
- Up to
- ₹8,000 per debit
- Frequency
- Monthly, or as presented
- From / until
- Jan 2026 to Dec 2028 (loan tenure)
- Collected by
- Your business name and identifier
- Reference
- Loan L-40217
The life of a mandate
A mandate has its own status, separate from any debit. You can only present debits while it's active, so your system should track the mandate status as carefully as the debits.
Submitted
Sent to the customer's bank for approval
Active
Approved; debits can be presented within its limits
Amended
Amount, dates or account changed, with the customer's approval
Suspended
Paused for a period, where the setup allows
Ended
Cancelled, expired, or rejected at registration
States described generically. Status names on Peneu are confirmed in the API reference.
Presenting a debit
Each debit is a separate instruction you present under the mandate: this amount, on this date. It travels from your sponsor bank through NACH to the customer's bank, which either honours it or returns it with a reason. Because NACH works in cycles rather than instantly, you learn the outcome later, not at the moment of presentation.
The date is the lever you control. Presenting just after customers are usually paid, and not on a bank holiday, does more for success rates than any retry. Remind customers a few days before, especially for amounts that vary.
Within the mandate. Amount at or below the maximum, date within the mandate period, frequency respected.
One reference per debit. Yours, unique, so a re-presentation is recognisably the same obligation.
Final answer before acting. Wait for the debit's outcome before re-presenting or collecting another way.
When the amount changes
Recurring amounts don't always stay fixed. A floating-rate loan's EMI moves when rates reset; a premium changes at renewal; a customer adds a service. Whether a new amount can simply be presented depends on how the mandate was written.
If the mandate is for a maximum amount and the new figure still fits under it, present it, after telling the customer the new amount and why. If it doesn't fit, the debit will be returned as exceeding the mandate, and the customer has to approve an amended mandate first. Plan that before the first higher debit, not after it bounces.
New amount under the maximum
Tell the customer, then present as usual.
New amount over the maximum
Customer approves an amended mandate first.
Fixed-amount mandate
Any change needs the mandate amended.
Bounces: why debits come back
A returned debit comes back with a reason from the customer's bank. Group them by what you can do about them. Only one group is worth re-presenting as it is.
| Reason (as commonly described) | What it means | Re-present? | What to do |
|---|---|---|---|
| Insufficient balance | Not enough money on the day | Yes, later | Remind the customer; present again on a better date |
| Account closed, frozen or dormant | The account can't be debited any more | No | Ask for a new mandate on another account |
| Mandate cancelled or expired | No valid permission any more | No | Collect another way, or register a new mandate |
| Payment stopped by the customer | The customer instructed their bank not to pay | No | Contact the customer; this is a dispute, not a failure |
| Amount exceeds mandate | Debit above the agreed maximum | Not as is | Present within the limit, or amend the mandate |
| Technical or bank-side issue | A problem outside the customer's control | Usually | Present again in a later cycle |
Return codes and their exact wording come from NPCI and the banks. How many times, and how soon, a debit may be re-presented is set by NPCI rules and your sponsor bank.
Getting more mandates approved first time
A mandate that's rejected at registration costs more than a bounce: the customer is often already onboarded, the first debit date is close, and now you need them to start again. Most rejections come from a handful of avoidable causes, and fixing them happens before the mandate is ever sent.
The most useful single step is checking the bank account before registration. A mandate on an account that doesn't exist, or isn't the customer's, will fail. See bank account verification.
Verify the account first. Account number, IFSC and name confirmed before the mandate is created.
Use eNACH where the bank supports it. No signature to mismatch, no form to lose in the post.
Match the name. The account holder must be the person agreeing; joint accounts can need extra care.
Set a realistic maximum. Too low and later debits bounce; too high and customers abandon the approval screen.
Say what they're approving. Show the maximum, frequency and end date in plain words before sending them to their bank.
Before each debit: tell the customer
A customer who knows a debit is coming keeps money in the account for it. A customer who's surprised by one calls their bank. A short message a few days before each debit, with the amount, the date and what it's for, does more for success rates than any retry schedule, and it cuts the “payment stopped by customer” returns that are really complaints.
A few days before
“Your EMI of ₹6,450 for loan L-40217 will be debited from account ••6621 on 5 May.”
If it bounces
“We couldn't collect ₹6,450 on 5 May. We'll try again on 12 May; please keep funds in ••6621 or pay here.”
When it's paid
“Received ₹6,450 for loan L-40217. Thank you.”
Illustrative messages. Card and UPI mandates have issuer notices built in by RBI rules; for NACH, your own messages do this job.
Reconciling NACH collections
For every debit you present, you should end up with one of two records: money credited to you, or a return with a reason. Anything without either is still open. Reconcile per debit, using your own reference and the mandate reference together, and keep bounced debits linked to their re-presentations so the customer's account shows one obligation, not three.
The money itself is credited to you by your sponsor bank after the NACH cycle settles. When it reaches your bank account depends on that arrangement. See how settlement works and reconciliation.
Ending a mandate properly
When the relationship ends (the loan is repaid, the policy lapses, the customer cancels), the mandate should end too. A mandate that stays active after nothing is owed is a risk to you and a worry to the customer: one stray debit and you're refunding money and answering a complaint.
Make cancellation part of closing the account: request it through your sponsor bank, confirm it to the customer, and mark it ended in your own records so no scheduled debit can be presented by mistake. If the customer asks to cancel while money is still due, cancel anyway and agree another way to pay; a debit on a mandate they've withdrawn won't be honoured.
An end date is a backstop, not a closing process. Loans are prepaid, policies surrendered and plans cancelled long before the date written on the mandate.
NACH, UPI AutoPay or a card mandate?
All three collect recurring payments with the customer's standing permission, but they sit on different rails with different rules. UPI and card mandates follow RBI's e-mandate framework; NACH follows NPCI's rules for NACH.
| NACH / eNACH | UPI AutoPay | Card e-mandate | |
|---|---|---|---|
| Debits | A bank account | The bank account behind a UPI ID | A credit, debit or prepaid card |
| Customer approves in | Their bank (or on paper) | Their UPI app | Their card issuer's authentication |
| Customer notified before each debit | Per NPCI and bank practice | At least 24 hours before, by the issuer | At least 24 hours before, by the issuer |
| Without extra authentication, per debit | Within the mandate's maximum | Up to ₹15,000 (₹1 lakh for insurance premiums, mutual funds, credit card bills) | Up to ₹15,000 (₹1 lakh for the same categories) |
| Customer can cancel | Yes | Yes, from the app, with authentication | Yes, with authentication |
| Suits | EMIs, premiums, SIPs, larger amounts | Subscriptions, smaller recurring bills | Subscriptions, global and card-first customers |
UPI and card figures are from RBI's Digital Payments – E-mandate Framework, 2026. Above those amounts, each debit needs the customer to authenticate. More in the subscription payments guide.
Where NACH is used
Loan EMIs
Lenders collect instalments over the loan tenure; a mandate is usually part of disbursal.
Insurance premiums
Monthly, quarterly or annual premiums without the policyholder remembering.
Modelling mandates and debits in your system
The most common NACH bug in lending and insurance systems is treating the mandate and the debit as one thing. They aren't. A mandate is a standing permission with its own status; each debit is a separate attempt with its own outcome. Model them separately and most edge cases become obvious.
Store return reasons as data, not free text, and map each to an action: re-present later, ask for a new mandate, or stop and contact the customer. That mapping is what lets a collections team work from a queue instead of reading bank reports.
Mandate record
Customer, account (masked), maximum amount, frequency, start and end, status, reference.
Debit record
Mandate, amount, due date, your reference, presentation date, outcome, return reason.
Return-reason map
Each reason linked to re-present, new mandate, or contact the customer.
Closing hook
When a loan or policy closes, the mandate is cancelled in the same step.
NACH questions
Can a customer have more than one active mandate with the same business?
Yes, for example one per loan. Keep each mandate linked to the obligation it covers, so a debit is always presented under the right one and ending one loan ends only its mandate.
What is a utility code in NACH?
An identifier issued for the business collecting through NACH, which appears on its mandates. It's set up through the sponsor bank as part of starting NACH collections.
Does a customer have to be told before each NACH debit?
Regardless of what the rules require of your setup, telling customers the amount and date a few days before each debit is good practice, and it's the single cheapest way to reduce bounces and disputes.
How far ahead should I present a NACH debit?
NACH works in cycles, so a debit isn't settled the moment you present it. Present with enough lead time for the cycle, and choose the debit date around when customers are likely to have funds. The exact timing depends on your sponsor bank's arrangement.
Can one mandate cover different amounts each month?
Yes, if it's written as a maximum-amount mandate. Each debit can then be any amount up to that maximum. Tell the customer the amount before each debit, especially when it changes.
What is NACH?
NACH (National Automated Clearing House) is a system operated by NPCI for high-volume, repetitive bank payments. On the debit side, a business uses it to collect recurring payments such as loan EMIs, insurance premiums and investment instalments directly from customers' bank accounts, under a mandate the customer has agreed to.
What is the difference between NACH and eNACH?
Both create the same kind of debit mandate. With a physical NACH mandate the customer signs a paper form, which is scanned and sent to their bank for approval. With eNACH the customer approves the mandate online through their own bank, usually with net banking or a debit card, which is typically much faster and avoids signature mismatches.
How long does mandate registration take?
Paper mandates can take days or weeks, because the form has to reach the customer's bank and be checked. eNACH registrations are usually confirmed much faster. Either way, don't present the first debit until the mandate shows as active.
Why did a NACH debit bounce?
The customer's bank returns a debit with a reason. The most common are insufficient balance, an account that has been closed or frozen, a mandate that was cancelled or has expired, a payment stopped by the customer, or an amount above the mandate's maximum. The reason decides what you do next.
Can a customer cancel a NACH mandate?
Yes. A customer can ask to cancel a mandate, and once the cancellation is processed no further debits can be presented under it. If money is still owed, collect it another way; don't try to present a debit on a cancelled mandate.
Can I retry a bounced NACH debit?
Usually, yes, but not immediately and not indefinitely. How many times a debit can be re-presented and how soon is governed by NPCI rules and your sponsor bank. Remind the customer first, and present again on a date when funds are more likely, such as just after salary day.
Is NACH the same as UPI AutoPay?
No. Both collect recurring payments, but NACH debits a bank account under a bank mandate, while UPI AutoPay uses a mandate set up in the customer's UPI app. UPI and card mandates follow RBI's e-mandate framework, including a notification to the customer at least 24 hours before each debit.
Does Peneu support NACH?
Which mandate types, registration methods and sponsor-bank arrangements are available on Peneu is confirmed during onboarding. This guide explains how NACH works generally so you can plan your flow.
Collect recurring payments with fewer bounces
Official sources
- RBI — Digital Payments – E-mandate Framework, 2026 (21 Apr 2026)UPI, card and PPI mandates: authentication at registration, 24-hour pre-debit notice, ₹15,000 / ₹1 lakh limits without extra authentication.
Last reviewed . Examples, amounts and screens marked illustrative are not Peneu figures.