Content authored by practitioners with experience at Amazon India, Intuit QuickBooks, and the Tata Group. Meet the team →
Indian Group Treasurers and CFOs typically run the working-capital line and the leakage-recovery line on separate tracks. The treasurer sizes the cash-credit facility, manages drawdown, and reports utilisation. The controllership runs reconciliation, classifies residuals, and chases disputes. The two functions rarely share a number. The result is that unrecovered leakage sits on the balance sheet as a current asset funded silently by CC/OD facility at the prevailing rate — 9 to 11 percent in the current environment — without anyone treating it as a working-capital problem. A treasury playbook that connects the two functions through a joint committee, a monthly close cycle, and a working-capital release board pack converts leakage recovery into measurable balance-sheet management and equivalent debt reduction.
Treat every rupee of unrecovered leakage as a rupee of CC/OD facility consumed at the marginal cost of capital. Map the seven leakage classes to a conversion model that shows days locked and working-capital impact per class. Establish a joint working-capital-and-leakage committee with shared KPIs across treasury and controllership. Operate a five-business-day monthly close cycle (T+5 cut-off, T+8 register update, T+12 treasury impact, T+15 audit-committee delta). Report to the board as rupees released this quarter, rupees in pipeline, rupees structurally lost, and equivalent debt reduction with annualised interest saving. Integrate with the broader Discovered Money register and the existing reconciliation engine so the treasury view is a derived layer rather than a parallel record.
Per-class leakage-to-working-capital conversion model with days locked and CC/OD cost per rupee. Joint committee terms of reference covering chair, attendees, agenda, and shared KPIs. Monthly leakage close cycle calendar with T+5, T+8, T+12, T+15 milestones. Working-capital release board pack template with the four numbers and the trend chart. Equivalent debt reduction roll-forward register that ties recovered leakage to actual CC/OD movement or to opportunity-cost saving. Cost-of-capital rate sourced from the actual CC/OD facility and updated quarterly. Integration spec with the Discovered Money register and the reconciliation engine residual feed.
A monthly treasury view of leakage outstanding by class, leakage as a percentage of average CC/OD utilisation, and the annualised interest burden. A monthly five-business-day close cycle that produces the audit-committee delta on the same rhythm as the main treasury report. A quarterly working-capital release board pack with rupees released, in pipeline, structurally lost, and equivalent debt reduction. An annual treasury-and-controllership joint review covering KPI evolution, cost-of-capital movement, and the next-year leakage recovery target translated into a working-capital release target.
A Group Treasurer at a ₹420 crore manufacturer in Pune walks into the Monday morning credit review. The cash-credit facility is drawn to 78 percent. Operations is asking for a temporary enhancement to cover an OEM payment cycle. The CFO asks the question the treasurer has been quietly carrying for a quarter — how much of the working capital we are funding is actually leakage we have not recovered? The honest answer is nobody has measured. The implicit answer, after a four-week baseline, will turn out to be ₹14.2 crore — about one full month of CC/OD utilisation that the business is paying interest on without earning a corresponding receivable that will actually convert to cash.
This is the treasury playbook for that conversation. It connects the leakage-recovery program — described in the recovery playbook and the board justification guide — to the working-capital line that the Group Treasurer is held accountable for. The bridge is the conversion model that treats every rupee of unrecovered leakage as a rupee of CC/OD facility consumed at the prevailing cost of capital, and the operating model is the joint committee, the monthly close cycle, and the board pack that follow from that framing.
Quick reference: leakage-to-working-capital conversion model
| Leakage class | Typical days locked | Working-capital impact per rupee | Primary funding line |
|---|---|---|---|
| Tax deduction (TDS receivable) | 90-180 days | Full CC/OD cost for days locked | Cash credit / overdraft |
| ITC under Rule 36(4) — lagged | 60-120 days | Full CC/OD cost for days locked | Cash credit / overdraft |
| ITC under Rule 36(4) — permanent | Indefinite | Full opportunity cost of capital | Internal accruals or CC/OD |
| OEM debit-note dispute | 60-150 days | Full CC/OD cost for days locked | Cash credit / overdraft |
| Platform short-settle | 30-90 days | Full CC/OD cost for days locked | Cash credit / overdraft |
| NACH bounce penalty (unrecovered) | 30-60 days | Full CC/OD cost for days locked | Cash credit / overdraft |
| Unexplained variance | Until classification | Full CC/OD cost until resolved | Cash credit / overdraft |
Total-leakage-to-working-capital conversion — the arithmetic
The bridge is mechanical. An outstanding ₹1 crore TDS receivable sitting on the balance sheet because the deductor has filed Form 168 incorrectly and the credit has not flowed is a current asset. The business is funding it. Most Indian mid-market businesses operating in the ₹150 crore to ₹1,000 crore revenue band fund current assets out of a sanctioned cash-credit or overdraft facility at the prevailing rate — typically 9 to 11 percent in the current environment, with the exact margin tied to the consortium-bank rating of the borrower. That ₹1 crore of unrecovered TDS is consuming ₹9 to ₹11 lakh of annual interest cost. Recovered, it would either retire ₹1 crore of CC/OD principal or avoid a future drawdown.
The same arithmetic applies to every other class. An outstanding ₹1 crore ITC reflection lagged in GSTR-2B because vendor filings have not yet propagated is consuming the same ₹9 to ₹11 lakh per year. An OEM debit-note dispute of ₹1 crore that has been logged but not pursued is consuming the same. A platform short-settle of ₹1 crore on a Razorpay or Cashfree settlement layer that has not been cash-allocated and recovered is consuming the same. A NACH bounce penalty of ₹1 crore that the customer has not been re-billed for is consuming the same.
The only class where the arithmetic is partially different is the permanent ITC loss component (Rule 36(4) reflections that never come because the vendor never files). That component is not a working-capital problem per se — it is a structural P&L loss. But the lagged ITC component, where the reflection arrives 60 to 120 days late, is squarely a working-capital problem and is the larger portion in most operating businesses.
CFO-treasury collaboration model
The joint working-capital-and-leakage committee is the operating forum that makes the bridge real. Without it, treasury continues to size facility and report utilisation while controllership continues to chase residuals — and the two never share a number.
Committee design. Monthly forum, two hours, chaired jointly by the CFO and the Group Treasurer. Attendees — financial controller, AR controller, tax controller, reconciliation lead, treasury manager responsible for CC/OD drawdown, and the audit-committee secretariat for visibility. Standing agenda — opening per-class leakage position, in-month recovery, end-month working-capital impact, top three escalations, and the equivalent-debt-reduction roll-forward.
Shared KPIs — the five numbers the committee tracks. Total leakage outstanding by class. Leakage outstanding as a percentage of average CC/OD utilisation in the period. Annualised interest burden on outstanding leakage at the prevailing CC/OD rate. Recovered leakage trailing twelve months. Equivalent interest saving from recovery in the period.
The shared-KPI framing is the part that changes behaviour. Treasury, which would otherwise not be measured on recovery rate, now carries it as a line in the monthly review. Controllership, which would otherwise not be measured on cost-of-capital impact, now sees the interest burden of unrecovered residuals explicitly. The CFO has both lenses in one forum.
The monthly leakage close cycle
Five business-day rhythm wrapped around the main books close. The objective is to produce the audit-committee delta on the same cadence as the existing treasury and management reports, so leakage recovery becomes part of the standing financial reporting heartbeat rather than a separate project.
T+5 cut-off. Books close. Cash-allocation register, Form 26AS / 168 pulls, GSTR-2B reflections, platform settlement files for the period, bank-statement NACH-charge listing — all finalised for the prior month. This is the single non-negotiable milestone. Without it, the cycle slips.
T+8 per-class register update. The Discovered Money register described in the recovery playbook is refreshed per class. New identifications added. Status transitions (stuck → at-risk → recoverable → recovered → structurally lost) applied. Ageing bands updated.
T+12 treasury impact computation. The treasury manager pulls the closing leakage outstanding per class from the register, multiplies by the in-period CC/OD rate, and produces the interest-burden number for the month. The same computation produces the equivalent-debt-reduction number from in-period recoveries.
T+15 audit-committee delta. The audit-committee secretariat packages the month-on-month change in leakage outstanding, recoveries, structural losses, and equivalent debt reduction for the next audit-committee cycle. The pack is short — one page of numbers, one trend chart.
A reconciliation engine operating on the 51 to 88 percent match-rate band keeps the T+5 cut-off achievable across all the data sources. Without engine support, the cycle typically slips to T+10 cut-off and T+20 audit-committee delta — still useful but less synchronised with treasury reporting.
Board reporting — the working-capital release pack
Quarterly, four numbers and one chart. The pack is designed to slot into the existing treasury board section so leakage recovery is read in the context of the working-capital line, not as a standalone controllership initiative.
Number one — rupees released this quarter. Recovered leakage that retired CC/OD principal or avoided drawing additional facility. This is the headline number.
Number two — rupees in pipeline. Leakage in the recoverable or accepted-pending-settlement status — the treasury team’s forward view of release potential over the next one to two quarters.
Number three — rupees structurally lost. Leakage classified after SLA exhaustion as no recovery path. This is the honest disclosure the board needs to anchor the recovery rate.
Number four — equivalent debt reduction with annualised interest saving. Recovered leakage treated as a permanent retirement of CC/OD principal, with the saving stated at the prevailing cost-of-capital rate. The honest framing — recovered leakage of ₹X crore would, if applied to CC/OD reduction, save ₹Y lakh per year in interest at the current rate; the actual cash use is a separate treasury decision.
The chart — a four-quarter trend of leakage outstanding alongside CC/OD utilisation. Visually shows the working-capital release effect.
Equivalent debt reduction framing
The board appreciates this framing because it anchors leakage recovery to a line they already track. CC/OD utilisation is a standing treasury report item; equivalent debt reduction is the recovery program’s contribution to that line.
The arithmetic is straightforward. Recovered leakage of ₹8.4 crore over an 18-month program, if applied to CC/OD reduction at a 10 percent prevailing rate, saves ₹84 lakh per year in interest. Even if the recovered cash is held as excess balance rather than applied to facility reduction, the lost-opportunity framing produces the same ₹84 lakh number — the board reads it as the financial value of the recovery program regardless of the specific treasury cash-use decision.
The framing also matures the program funding conversation. The board justification guide presents the payback model based on recovered-leakage inflow and working-capital saving from days-recon-delay reduction. The equivalent-debt-reduction framing in this article is the cleanest way to communicate the working-capital component to the board on a continuing basis once the program is operational.
Worked example — a ₹420 crore Pune manufacturer
Customer-specific numbers, not industry aggregates.
Baseline measurement after four weeks produces standing leakage of ₹14.2 crore across the classes — ₹4.8 crore in tax deduction (Form 26AS / 168 gap), ₹2.6 crore in ITC (Rule 36(4) lagged and a small permanent component), ₹3.1 crore in OEM debit-note dispute (a tier-1 OEM customer with quality-claim deductions), ₹1.9 crore in platform short-settle (small but visible on the D2C side of the business), ₹0.9 crore in NACH bounce penalty unrecovered from dealer-distributor accounts, and ₹0.9 crore in unexplained variance pending class assignment.
Treasury cost computation. CC/OD facility is at 10 percent in the current consortium-bank arrangement. Standing leakage of ₹14.2 crore at 10 percent equals an annual interest burden of ₹1.42 crore. That is real money the business is paying to fund leakage it could be recovering. Sized this way, the recovery program payback becomes obvious.
Recovery program. Eighteen months. Recovers ₹8.4 crore across the classes — ₹3.4 crore of the tax-deduction position through structured deductor escalation, ₹1.7 crore of the lagged ITC through vendor follow-up, ₹2.0 crore of the OEM dispute through formal contract escalation, ₹0.8 crore of the platform short-settle through cash-allocation tightening, ₹0.4 crore of the NACH bounce through re-billing discipline, and the ₹0.1 crore unexplained variance dropping into resolved classes.
Equivalent debt reduction. ₹8.4 crore of recovered leakage applied to CC/OD reduction saves ₹84 lakh per year in interest at the prevailing 10 percent rate. The remaining ₹5.8 crore of standing leakage is a mix of in-pipeline (₹3.6 crore) and structurally lost (₹2.2 crore), with the structural component dominated by the permanent ITC loss and the long-tail OEM dispute that the contract review has accepted will not recover.
The treasurer presents this to the board in the standard quarterly pack. The recovery program’s contribution to the working-capital line is unmissable.
Size the working-capital release from your leakage baseline
Plug in revenue, receivable base, CC/OD rate, and rough class mix to project leakage by class, equivalent debt reduction, and the annualised interest saving from a structured recovery program.
Open the Revenue Leakage Calculator →Common pitfalls
Pitfall one — treating the program as controllership-only. Without treasury in the room, the working-capital framing never lands and the board never sees the CC/OD-equivalence number. The program risks being read as operational hygiene rather than balance-sheet management.
Pitfall two — using a stale cost-of-capital rate. The prevailing CC/OD rate moves with the policy environment and the consortium-bank pricing review. Refresh it at least quarterly; using last year’s rate understates the interest burden materially in a rising-rate environment.
Pitfall three — letting the monthly close cycle slip past T+15 audit-committee delta. Once the cycle slips a quarter, the leakage line decouples from the treasury reporting heartbeat and reverts to a separate update read by exception. The forcing function is the audit-committee secretariat receiving the delta on the published calendar.
Pitfall four — over-claiming equivalent debt reduction when the cash is not actually applied to CC/OD. The honest framing is the conditional one — recovered leakage of ₹X crore would, if applied to facility reduction, save ₹Y lakh per year. Over-claiming the actual cash application erodes board trust quickly.
Pitfall five — under-investing in the reconciliation engine that supports the cycle. The T+5 cut-off across Form 26AS / 168 pulls, GSTR-2B reflections, platform settlements, and bank statements is operationally heavy without engine automation. A cycle that slips to T+10 or T+12 cut-off pushes the audit-committee delta to T+20 and erodes the treasury reporting synchronisation.
Pitfall six — forgetting that the structural-loss number is part of the credibility story. Boards read the in-pipeline and structural-loss numbers together. A pack that only shows recoveries without the structural-loss disclosure reads as incomplete and triggers scepticism on the recoveries number.
Closing — connecting to the Seven Classes backbone
The Seven Classes framework on the Stop revenue leakage pillar page is the analytical backbone — fee deduction, tax deduction, discount, rounding, short settlement, penalty, unexplained variance. Each class converts to a working-capital impact through the days-locked-times-CC/OD-rate arithmetic in this article. The treasury playbook does not invent new categories; it adds the financing-cost lens to the existing classification.
The operating model — joint committee, monthly close cycle, board pack with the four numbers and the trend chart — is the connective tissue between the controllership-led recovery playbook and the CFO-led board justification. Together the three articles describe a fully operational program — measured leakage, structured recovery, sustained board funding, and a treasury line that releases working capital quarter after quarter as equivalent debt reduction.
For the working-capital arithmetic that sits alongside this treasury frame, see Working capital leakage from reconciliation delays. The Stop revenue leakage pillar page anchors the broader story.