Content authored by practitioners with experience at Amazon India, Intuit QuickBooks, and the Tata Group. Meet the team →
Indian finance teams that process NACH collections at scale and buy from a long tail of Udyam-registered MSE suppliers carry two leakage exposures that rarely show up on a single dashboard. NACH bounce charges aggregate quietly on the bank statement and erode the working-capital line. Section 43B(h) ageing on MSE supplier payables converts to a hard FY-end income-tax disallowance. Both are invisible without a structured per-code and per-supplier register. Both are recoverable with a defined operating cadence. Neither gets the audit-committee attention it deserves because the data sits in fragmented systems.
Decompose NACH bounce volume by return code with retry economics per code (probability of recovery and cost of retry against the leakage rupee). Run mandate hygiene as a monthly cycle to keep the active-mandate base aligned with the sponsor bank. Operate a monthly bounce dashboard with code-category cuts and a recovery-rate trend. For 43B(h), maintain a MSE-registered supplier subset with payable ageing, compute exposure at each month-end, escalate at the 30-day and 40-day pre-window warning, and produce a quarterly exposure pack with a hard quarter-four pre-FY-end cut. Combine both into the audit-committee leakage agenda.
NACH return-code dictionary with per-code recovery probability and cost-of-retry assumption. Mandate-master reconciliation against sponsor-bank active list, monthly. Bounce-code dashboard schema: total presented value, bounce rate by category, charge-line trend, top-counterparty bounce frequency. MSE-registered supplier flag in the supplier master driven from Udyam number capture. Payable ageing with statutory or contractual window per supplier. 43B(h) exposure summary with disallowance forecast at the marginal corporate rate. Monthly bounce review cadence and quarterly 43B(h) exposure-pack cadence.
A monthly NACH bounce dashboard with code-category recovery and charge-line trend. A weekly mandate-revival operating queue for codes 21 and 24. A quarterly Section 43B(h) MSE exposure pack with payable ageing, exposure summary, payment-acceleration recommendation, and residual disallowance forecast. A consolidated audit-committee leakage view that ties the NACH charge-line and 43B(h) exposure into the broader Seven Classes recovery program.
A CFO at a Bengaluru auto-component manufacturer with ₹120 crore of revenue opens the quarter-four review and sees two numbers that did not sit on the agenda twelve months ago. The first is the NACH bounce charge line on the bank statement — small per-event debits that aggregated into roughly ₹38 lakh over the year, none of it questioned at the time, none of it disputed against counterparties whose mandates kept failing. The second is the income-tax controller flagging ₹2.1 crore of supplier payables aged beyond 45 days at FY-end to Udyam-registered micro and small suppliers — a Section 43B(h) disallowance that will add roughly ₹53 lakh to the current-year tax line if the payables do not get cleared before 31 March.
Neither number was hidden. Both sat in the books all year. What was missing was the operating cadence that surfaces them monthly, routes them to the right desk, and pulls them into the audit-committee conversation before they harden into permanent leakage. This article walks the cadence — the NACH return-code retry economics, the mandate-hygiene cycle, the 43B(h) ageing trigger, the monthly bounce dashboard and quarterly exposure pack, and a worked example sized to the manufacturer in the opening paragraph.
Quick reference: NACH bounce categories and recovery probability
| Bounce category | Representative return codes | Typical share of total bounces | Recovery probability with structured program | Operating action |
|---|---|---|---|---|
| Insufficient funds | Code 1 (insufficient funds) | 45-60 percent | 55-70 percent on second-cycle retry within 5-7 days | Automated retry plus customer-side reminder |
| Mandate state failure | Code 21 (mandate not registered), Code 24 (customer to refer drawer), Code 25 (mandate cancelled) | 15-25 percent | 40-60 percent within 30-day mandate revival | Mandate-revival workflow plus e-mandate refresh |
| Account state | Code 2 (account closed), Code 3 (no such account) | 5-10 percent | 5-15 percent — largely structural loss | Counterparty contact and write-off classification |
| Customer-initiated stop | Code 6 (payment stopped by drawer), Code 8 (amount mismatch) | 8-15 percent | 30-45 percent with customer-success outreach | Dispute-resolution workflow with key-account lead |
| Technical bounce | Code 26 (invalid IFSC), signature mismatch, technical | 5-12 percent | 60-80 percent on re-presentation with corrected data | Master-data cleanup plus same-cycle re-presentation |
Bounce-charge leakage on a baseline 4 to 6 percent bounce rate typically lands at 0.3 to 0.7 percent of total NACH presented value annualised, before the recovery program runs. A structured program brings the bounce rate to 1.5 to 2.5 percent and the charge-line to under 0.2 percent of presented value.
NACH return-code analysis: what each code is telling the finance team
The return-code dictionary is the foundation. Without per-code decomposition, the bounce charge looks like an unavoidable bank fee. With per-code decomposition, it becomes a per-class leakage register routed to specific owners. The codes that matter most for a typical Indian collection book:
Code 1 insufficient funds. The largest category by volume in almost every book. Recovery economics are favourable because the underlying customer relationship is intact — the counterparty intended to pay, the timing failed. Automated second-cycle retry within 5 to 7 days recovers 55 to 70 percent without any customer-side intervention. A reminder workflow lifts recovery to 70 to 80 percent on the secondary attempt.
Code 2 account closed and code 3 no such account. Structural failures. The mandate base contains a stale account. Recovery probability is in the 5 to 15 percent band — largely write-off territory. The operating value of identifying these codes is not recovery, it is mandate-master cleanup that prevents the next cycle from re-presenting against the same stale account and incurring fresh charges.
Code 6 payment stopped by drawer and code 8 amount mismatch. Customer-initiated. These signal a dispute or a recent contractual change the master data has not caught up with. Recovery requires customer-success or key-account outreach within the standard 30-day dispute window. Without that outreach, the dispute compounds and the next cycle bounces against the same logic.
Code 21 mandate not registered and code 24 customer to refer drawer. Mandate-state failures. These are recoverable through the mandate-revival workflow — re-registration under e-mandate, sponsor-bank confirmation, sometimes a physical re-execution. Recovery is 40 to 60 percent within a 30-day window if the workflow runs; close to zero if it does not.
Code 25 mandate cancelled. Customer has formally cancelled. Treat as structural unless commercial relationship recovery is in progress. Cleanup the master immediately.
Technical bounces — code 26 invalid IFSC, signature mismatch on physical mandates, NPCI-side technical returns. The highest recovery probability of any category at 60 to 80 percent on corrected re-presentation. The discipline is data hygiene at the master rather than dispute work.
Retry economics: same-cycle versus second-cycle and the cost question
Retry economics turn on three quantities: the per-presentation bank charge, the probability of recovery on the retry, and the working-capital cost of the days between original bounce and successful collection.
Same-cycle retry — re-presenting within the same NACH cycle. Lowest delay, lowest working-capital cost, but limited to code categories where the underlying customer state has changed since the bounce (mostly technical bounces). Use sparingly and only against returns where the root cause has been confirmed corrected.
Second-cycle retry — re-presentation in the next NACH cycle after a 5 to 7 day gap. The workhorse retry for code 1 insufficient funds. Working-capital cost is the cost of one extra collection cycle, typically ₹0.20 to ₹0.40 per ₹1,000 of working-capital outstanding. Recovery probability of 55 to 70 percent makes this overwhelmingly economic.
Third retry. Diminishing returns. By the third attempt against the same instrument, the recovery probability falls below 20 percent for code 1 and below 10 percent for most other codes. The right operating rule is two attempts maximum on any single instrument before the workflow escalates to customer-success outreach or mandate-revival.
Mandate-revival workflow for codes 21 and 24 sits outside the retry cycle. It runs as a parallel 30-day workflow with mandate-master verification, sponsor-bank check, customer re-registration if required, and a fresh first-presentation against the renewed mandate. The economics work because the alternative — repeated re-presentations against a non-registered mandate — incurs charges without recovery probability.
Section 43B(h) 45-day MSME ageing: the FY-end disallowance trigger
Section 43B(h) of the Income-tax Act, effective from FY 2023-24, disallows the income-tax deduction on payables to Udyam-registered micro and small suppliers that remain unpaid at FY-end and that have aged beyond the agreed payment window. The window is the contractually agreed period, capped at 45 days where a written agreement exists, or 15 days where no agreement exists.
The mechanics. First, the finance team needs an MSE-registered subset of the supplier master, populated from Udyam registration numbers captured at supplier onboarding (and refreshed periodically because Udyam classification can change). Second, the payable ageing engine needs to mark each open invoice with the contractual or statutory window. Third, at every month-end and especially at quarter-four month-ends, the team computes the unpaid balance aged beyond the window — that is the standing exposure for the year if FY-end arrives without payment.
The FY-end trigger is a hard 31 March cut. Any balance aged beyond the window at the cut is added back to taxable income for the year. At a 25 to 30 percent marginal corporate rate, the tax cost is real and lands in the current-year P&L. The deduction recovers in the year of actual payment, but the timing difference flows through the current-year cash-tax line and the audit-committee reporting.
The operating consequence: quarter-four payable acceleration becomes a deliberate finance-team activity, not an afterthought. The exposure pack at the end of quarter three should list every MSE-registered payable aged 25 days or more, every payable expected to cross the 40-day mark before 31 March, and a payment-acceleration recommendation set with cash impact.
Board-level visibility: the dashboards that hold both threads
Monthly NACH bounce dashboard. Owned by the AR and treasury controller. Standard cuts: total NACH presented value for the month, bounce rate by code category (the five categories from the quick-reference table), recovery rate quarter-to-date by code, charge-line trend with a year-on-year comparison, top counterparties by bounce frequency, mandate-master health (active to inactive ratio and inactive-mandate ageing). The dashboard sits at the monthly finance-leadership meeting and feeds the quarterly audit-committee leakage agenda.
Quarterly 43B(h) exposure pack. Owned by the tax controller in coordination with AR. Standard cuts: MSE-registered payable ageing buckets (0-15 days, 16-30, 31-40, 41-45, beyond 45), exposure summary by ageing band with rupee value, year-on-year trend on the exposure line, payment-acceleration recommendation set with cash and tax impact, residual disallowance forecast for the year-end provision. The pack carries a hard quarter-four pre-FY-end cut that allows the AR and tax desks two months of runway to mobilise payments against ageing MSE balances before the 31 March cut.
The two artefacts meet in the audit-committee leakage view. NACH bounce charge-line and 43B(h) disallowance forecast become two columns in the broader Seven Classes recovery dashboard.
Mandate hygiene: the operating cycle that drives bounce rates down
Mandate hygiene is the discipline of keeping the active-mandate base aligned with bank-side state. The operating cycle:
Monthly reconciliation of mandate-master against sponsor-bank-confirmed active list. The gap reveals mandates the bank no longer treats as active — typically code 25 cancellations and ageing inactive mandates the customer has not refreshed. Anything in the gap drives the next cycle’s bounce volume; cleaning it pre-empts the charge.
Monthly identification of mandates returned with code 21 (not registered) and code 24 (refer drawer). These are recoverable through the revival workflow but recovery requires action inside a 30-day window. After 30 days the customer relationship has typically moved on and the mandate goes structural-cancelled.
Weekly refresh of mandate IDs flagged for renewal under the e-mandate framework. Most e-mandates carry a defined validity. Catching them before expiry keeps the bounce rate stable; missing the renewal triggers a code-21 bounce on the next presentation.
Quarterly mandate-base churn review. Net new mandates, net cancellations, code-21 and code-25 rate trend, e-mandate share of total active mandates. The metric to watch is active-to-inactive ratio — businesses with a healthy ratio (typically 85 to 92 percent active) see baseline bounce rates in the 2 to 4 percent band; businesses below 75 percent active see bounce rates in the 5 to 8 percent band.
The shift to e-mandate over the last several years has made the refresh cycle cheaper but no less necessary. The discipline is what compounds the bounce-rate reduction quarter over quarter.
Worked example: a ₹120 crore auto-component manufacturer
The Bengaluru manufacturer from the opening paragraph. Revenue ₹120 crore, supplier payables ₹8.4 crore on a normalised quarter-end, of which ₹5.2 crore is to Udyam-registered MSE suppliers. NACH collection volume — primarily dealer and distributor collections — averages ₹3.6 crore monthly with a baseline 4.2 percent bounce rate.
The 43B(h) exposure at FY-end before the program. Of the ₹5.2 crore MSE payable balance at 31 March, ageing decomposition shows ₹2.1 crore aged beyond 45 days. At a 28 percent effective corporate rate, the disallowance adds ₹58.8 lakh to the current-year tax line. The audit-committee reporting impact is permanent. The cash recovery in the following year when the payable settles does not undo the FY reporting.
The NACH bounce-charge exposure before the program. Annualised NACH presented value of ₹43.2 crore. Bounce volume at 4.2 percent baseline is ₹1.81 crore per year. With per-bounce charges in the ₹20 to ₹30 band plus interest and follow-on costs, the charge line aggregates to ₹38 lakh over the year. None of it is disputed because none of it is tracked at the per-code level.
The recovery program. Quarter-one focus on mandate hygiene and bounce-code analysis. Quarter-two operationalises the second-cycle retry workflow for code 1 and the mandate-revival workflow for codes 21 and 24. Quarter-three adds the 43B(h) MSE-payable register with quarterly exposure cut. Quarter-four runs the payment-acceleration mobilisation against MSE balances aged beyond 30 days.
Outcomes after the first full year. NACH bounce rate moves from 4.2 percent to 1.8 percent. Bounce-charge line falls from ₹38 lakh to ₹12 lakh — ₹26 lakh of recovered leakage. The 43B(h) exposure at the next FY-end falls from ₹2.1 crore to ₹0.45 crore — disallowance impact drops from ₹58.8 lakh to ₹12.6 lakh, a ₹46 lakh swing in the current-year tax line. Combined first-year recovery from the two threads — ₹72 lakh against a ₹120 crore revenue base. The audit committee sees a per-class register, a per-code dashboard, and a quarterly exposure pack where previously there was nothing on the agenda.
Size your NACH and 43B(h) leakage exposure
Plug in NACH presented value, baseline bounce rate, and MSE supplier payable share to project bounce-charge leakage and FY-end 43B(h) disallowance exposure under structured recovery.
Open the Revenue Leakage Calculator →Common pitfalls to avoid
Pitfall one: treating NACH bounce charges as an unavoidable bank fee. Without per-code decomposition, the charge line looks structural. With decomposition, 70 to 80 percent of it is recoverable through retry economics and mandate hygiene.
Pitfall two: retrying code 1 insufficient funds more than twice. Diminishing returns set in after the second attempt and additional cycles compound charges without recovery probability. Escalate to customer-success or restructure the collection cadence after two attempts.
Pitfall three: leaving the MSE-registered supplier flag uncaptured at onboarding. Without the Udyam registration captured in the supplier master, the 43B(h) ageing engine cannot identify the MSE subset and the exposure stays invisible until the year-end audit catches it — by which point the disallowance has crystallised.
Pitfall four: running the 43B(h) exposure pack only at quarter-four. By the time the quarter-four pack lands, the runway to mobilise payments against 40-day-plus ageing is too short. The pack should run quarterly with a pre-FY-end intensification in quarter three.
Pitfall five: treating mandate hygiene as a one-time cleanup rather than a monthly cycle. The mandate base churns continuously — cancellations, e-mandate expiries, account changes. A one-time cleanup degrades within 90 to 120 days. The discipline is the monthly cadence, not the periodic project.
Pitfall six: keeping the NACH bounce dashboard and the 43B(h) exposure pack in separate spreadsheets owned by different desks without a consolidated audit-committee view. Both are leakage classes within the Seven Classes framework. The audit committee sees the consolidated view; the operating desks own the per-class registers.
Closing: two classes, one operating discipline
NACH bounce-charge recovery and Section 43B(h) MSE compliance look like different problems — one is a bank-statement line, the other is a year-end tax adjustment. They share an operating shape. Both reward per-class decomposition. Both reward a monthly or quarterly cadence. Both reward the audit-committee discipline that turns a silent leakage stream into a tracked recovery line.
The umbrella view sits on the Stop Revenue Leakage pillar — the Seven Classes framework that places NACH bounce charges in the penalty-and-interest class and MSE payable disallowance in the working-capital and tax-exposure overlay. The operating model is in the Revenue leakage recovery playbook. The board case sits in Building the board case for revenue leakage recovery. Together they make the two threads in this article one item on the audit-committee agenda rather than two surprises at year-end.