Content authored by practitioners with experience at Amazon India, Intuit QuickBooks, and the Tata Group. Meet the team →
Indian CFOs frequently bring revenue-leakage recovery business cases to the board that get rejected, deferred, or approved as one-shot projects rather than sustained programs. The common failure modes are asserted (rather than measured) leakage rupees, over-claimed recovery rates, missing working-capital overlay in the payback calculation, weak internal-champion structure, and no defensible audit-committee reporting cycle. A defensible board case addresses each of these with a structured three-page memo, a measured per-class rupee build-up, a 60-75% year-one recovery target, a combined inflow payback model, and a three-layer ownership structure that creates succession depth.
Build the rupee number by class using the four-week baseline measurement output. Model year-one recovery at 40-55% and year-three at 65-75% with class-specific override (fee-deduction 70-85%, tax-deduction 60-80%, OEM short-pay 50-65%, ITC lagged 70-85% lagged plus 25-40% permanent). Include working-capital overlay computed per the days-recon-delay framework at the business's realistic cost-of-capital. Compute payback against combined recovered-leakage plus working-capital saving inflows against headcount-and-software-plus-setup outflows. Position three-layer ownership and audit-committee cycle. Carry sensitivity analysis on recovery rate, working-capital rate, and program cost.
Three-page memo template with rupee number page, operating model page, investment ask page. Appendix template with regulator-anchor table, per-class worked examples, baseline-measurement methodology. Sensitivity-analysis table with recovery rate, cost-of-capital, and program cost dimensions. Audit-committee reporting cycle template tied to the board memo. Three-layer ownership chart with named individuals and back-up. Payback calculator with year-by-year cash flow projection. Quarterly tracking dashboard for post-approval execution.
An approved board case for a sustained revenue-leakage recovery program with defined headcount, software-licence cost, one-time setup, expected year-one and year-three recovery rupees, and audit-committee reporting cycle. Quarterly leakage trend reporting in the standard audit-committee pack. An internal-champion three-layer structure with succession depth. A program review cycle that adjusts recovery targets and operating cadence based on observed performance.
A CFO at a Mumbai mid-market manufacturer with ₹240 crore of revenue takes a structured baseline measurement of revenue leakage across the seven classes (per the Seven Classes guide). Four weeks later, the numbers are on the table. Tax-deduction leakage: ₹18.4 lakh per year. ITC leakage under Rule 36(4): ₹78.6 lakh per year (₹49 lakh lagged, ₹29.6 lakh permanent). Fee-deduction leakage on the platform-settlement layer: ₹6.2 lakh per year. OEM short-pay leakage: ₹2.1 crore per year. NACH bounce-recharge leakage: ₹12 lakh per year. Working-capital leakage from a 16-day reconciliation cycle on a ₹38 crore receivable base at 11% cost-of-capital: ₹18.3 lakh per year. Total standing leakage: ₹3.34 crore — 1.4% of revenue.
The number is defensible because it is built per class from measured artefacts. Now the harder problem: getting the board to fund a sustained recovery program rather than a one-shot project. This is the playbook for that conversation.
Quick reference: the board memo structure
| Page | Content | Purpose |
|---|---|---|
| 1 — Rupee number | Total leakage, per-class decomposition, recovery targets | Quantify the opportunity |
| 2 — Operating model | Ownership, audit-committee cycle, infrastructure plan | Show the program is operatable |
| 3 — Investment ask | Headcount, software, setup, payback under sensitivity | Justify the spend |
| Appendix A | Regulator-anchor table by class | Defensibility |
| Appendix B | Worked recovery examples by class | Credibility |
| Appendix C | Baseline-measurement methodology | Reproducibility |
| Appendix D | Sensitivity analysis | Risk view |
| Appendix E | Quarterly reporting cycle template | Governance continuity |
Why most leakage business cases fail
Three failure patterns dominate the cases that get rejected or deferred at first hearing.
Pattern one — the asserted rupee. The CFO says “industry estimates put leakage at 2-3% of revenue, so we’re losing ₹6 crore a year.” A board that asks “how do you know” has no defensible answer. Industry averages are not a measurement; they are a prior. Board approval requires the per-class rupee built from actual artefacts — Form 26AS / Form 168 deltas for TDS, GSTR-2B reflection rates for ITC, per-transaction fee-column variance for platform fees, OEM debit-note reconciliation for short-pay, bank-statement NACH-charge audit for penalty-and-interest, days-recon-delay measurement for working-capital. The four-week baseline measurement is the price of admission.
Pattern two — the over-claimed recovery rate. The CFO promises 90%-plus recovery on standing leakage. The board reads this as either an indictment of prior management (“how was this rate ever 90% recoverable and we missed it”) or as an over-promise (“recovery rates that high are not realistic”). The defensible case models year-one recovery at 40-55% of standing leakage with class-specific overrides — fee-deduction 70-85% (high-contract-leverage class), tax-deduction 60-80%, OEM short-pay 50-65% (low-contract-leverage on structural component), ITC 70-85% lagged plus 25-40% permanent.
Pattern three — missing working-capital overlay. The CFO presents only the recovered-leakage inflow, missing the cost-of-capital saving from reduced days-recon-delay. On most business models the working-capital line is 12-30% of the combined inflow and tilts the payback period materially. A board case that omits it leaves money on the table and reads as analytically thin.
Page 1 — the rupee number
The first page of the board memo is the single most important page. It carries the total standing leakage, the per-class decomposition, the year-one and year-three recovery targets, and one chart showing the trend (where available — for first-time deployments, a single-quarter snapshot is acceptable).
Standard layout. Top half: a bar chart showing per-class leakage with the class label, the rupee number, and the recovery probability band. Bottom half left: a three-column table — leakage class, year-one recovery target rupees, year-three recovery target rupees. Bottom half right: a paragraph stating the total standing leakage as a percentage of revenue and the recovery target trajectory.
The rupee number page should fit on a single A4 sheet at readable font size. Boards read it in less than two minutes and form their first impression on whether the case is defensible.
Page 2 — the operating model
The second page establishes that the program is operatable — not a one-shot recovery sprint, but a permanent finance-team capability. Three components.
Component one: the three-layer ownership structure. CFO as executive sponsor. Controllership office (Financial Controller or Group Reporting head) as program operator. AR controller and reconciliation lead as operational team. Boards prefer the three-layer structure because it creates succession depth — a CFO transition or controllership change does not break the program.
Component two: the audit-committee reporting cycle. Quarterly four-to-six page leakage pack with rupees recovered, rupees in pipeline, rupees structurally lost, recovery rate trend, and recommendations. The audit-committee discipline is what sustains the program; without it, programs drift in 6-9 months.
Component three: the integration with reconciliation infrastructure. A reconciliation engine running on the 51% to 88% match-rate band automates the bulk of fee-deduction matching, rounding detection, short-settlement residual queueing, and unexplained-variance reduction. The playbook routes residuals to owners with SLAs. The board case explains the two-pronged investment (process and technical capability) and the year-one timeline for both.
Page 3 — the investment ask
The third page makes the explicit ask. Four numbers and a payback table.
Number one: incremental finance-team headcount. Typical deployment requires 1.5-2.5 incremental full-time equivalents — a senior tax/ITC desk operator, an AR-controller-level operator for fee-deduction and short-settlement, and a fractional controllership office allocation. Salary cost typically ₹35-65 lakh per year all-in for an Indian mid-market business.
Number two: software licence cost. Reconciliation engine licence based on transaction volume and module scope. Cost varies materially; the board memo states the budgeted range and notes that final cost will be confirmed through a procurement process. No pricing claims for specific products in the memo — instead, the structure of the cost (per-transaction, per-bank-statement, per-module) is explained.
Number three: one-time setup cost. Integration with ERP, AP/AR systems, payment-aggregator data pulls, bank-statement automation. Typically ₹15-40 lakh for an Indian mid-market business with standard ERP and three-to-five-platform settlement layer.
Number four: the payback. Year-by-year cash-flow projection. Year one: recovered leakage at 40-55% of standing, plus working-capital saving at 60-80% of target cycle improvement. Year two: recovery at 55-65%, working-capital at 90%. Year three: recovery at 65-75%, working-capital at full target. Net cumulative cash inflow crosses net cumulative outflow typically at month 10-16.
Payback sensitivity. Show ±20% on recovery rate, ±2 percentage points on cost-of-capital, ±25% on program cost. The board will ask; pre-empting the question signals analytical rigour.
Build the rupee number for your board memo
Enter revenue, receivable base, and rough class mix to project standing leakage, recovery targets, and the payback profile for your board case.
Open the Revenue Leakage Calculator →Worked example — the Mumbai manufacturer
Standing leakage: ₹3.34 crore per year, 1.4% of revenue.
Year-one recovery target. Tax-deduction at 70% of ₹18.4 lakh = ₹12.9 lakh. ITC lagged at 78% of ₹49 lakh = ₹38.2 lakh, ITC permanent at 30% of ₹29.6 lakh = ₹8.9 lakh. Fee-deduction at 76% of ₹6.2 lakh = ₹4.7 lakh. OEM short-pay disputable at 70% of ₹1 crore = ₹70 lakh, OEM short-pay structural at 25% of ₹1.1 crore = ₹27.5 lakh. NACH at 80% of ₹12 lakh = ₹9.6 lakh. Working-capital from cycle reduction 16-day to 8-day on ₹38 crore at 11%: ₹9.2 lakh. Year-one inflow: ₹1.81 crore.
Year-one outflow. Headcount: ₹52 lakh. Software licence: ₹40-65 lakh (budgeted ₹55 lakh midpoint). One-time setup: ₹28 lakh. Total year-one outflow: ₹1.35 crore.
Year-one net: +₹46 lakh. Payback indicated within month 9 of year one. Year-three recurring inflow at 72% recovery and full working-capital benefit: ₹2.45 crore against recurring outflow of ₹1.15 crore (headcount plus licence; setup not recurring). Year-three recurring net: +₹1.30 crore. NPV at 12% over 5 years: roughly ₹3.9 crore.
The board memo presents this with the sensitivity table and the audit-committee reporting cycle. The investment is approved as a sustained program rather than a one-shot project.
Internal-champion structure — getting the program through
Boards approve programs they trust will run. The three-layer champion structure communicates that trust.
Layer one — the CFO. Owns the board relationship, the audit-committee cycle, and the program-level approval authority. Reports to the board on quarterly leakage trend and any material reset to recovery targets or operating model.
Layer two — the controllership office. Owns the Discovered Money register, the SLA library, the dispute-template library, and the monthly recovery review. Reports to the CFO on operating performance.
Layer three — the operating team. AR controller for platform fees, short-settlement, and customer-side disputes. Tax controller for TDS, ITC, and statutory components. Reconciliation lead for engine residual handling and unexplained-variance reduction. Each runs the daily and weekly cycles per the Recovery playbook.
The structure creates succession depth and avoids the single-person-dependency risk that boards reasonably worry about.
Audit-committee positioning — getting the program sustained
The single biggest determinant of long-run program success is whether leakage recovery becomes a permanent audit-committee agenda item. The board memo should explicitly request that the audit committee receive the quarterly leakage pack and have the recovery program included in the external auditor’s review scope (the rupee figures are independently verifiable against Form 26AS / Form 168, GSTR-2B, platform settlement files, and bank statements).
Position the audit-committee cycle as a continuity mechanism, not an oversight burden. Boards typically accept it readily because revenue leakage of more than 0.6% of revenue is a material item for the audit committee’s responsibility scope.
Common board pushback and how to answer
Pushback one: “if this much is recoverable, why have we not done it before?” Honest answer: the per-class measurement infrastructure did not exist; the program now combines measurement, process, and technical capability that together make recovery operationally feasible.
Pushback two: “why now and not next year?” Answer: every year of delay is ₹3.3 crore of leakage that compounds with working-capital cost. Year of delay equals year of leakage permanently lost.
Pushback three: “why this program design and not a smaller project scope?” Answer: project-scope recovery has been tried (most businesses have run occasional Form 26AS audits or fee-disputes). The leakage returns as soon as the project ends. Sustained recovery requires permanent operational capability with audit-committee discipline.
Pushback four: “what is the downside if recovery targets are missed?” Answer: the sensitivity table shows payback under conservative recovery scenarios; the worst-case year-one net is still positive on most business models, and the program design includes a year-one review point that adjusts headcount and software scope if recovery materially under-runs target.
Continue reading on the leakage backbone
For the operating playbook that the board case approves, see Revenue leakage recovery playbook. For the framework that underpins the per-class quantification, see Revenue leakage and the Seven Classes framework. For the working-capital overlay arithmetic, see Working capital leakage from reconciliation delays. The Stop Revenue Leakage pillar page anchors the broader story.