The 0.5% Revenue Leak Every Enterprise CFO Is Missing

At a ₹1,000Cr company, "0.5% revenue leak" sounds abstract — until you price it. That's ₹5Cr a year. Quietly. Every year.

It doesn't show up in any one place. It's spread across four buckets, and each one looks small in isolation.

1. Missed invoicing

Deliveries that didn't get invoiced because the delivery sheet got mis-filed, the PO closed early, or the customer changed the price mid-cycle and no one re-issued. Typically 0.05–0.10% of revenue at growing companies. At ₹1,000Cr: ₹50L–₹1Cr.

2. Unrecovered deductions

Customers net off scheme claims, quality adjustments, and short-pays that aren't valid. The team intends to dispute, but the queue grows, the dispute window closes, and the deduction becomes a write-off. Typically 0.10–0.20% of revenue. At ₹1,000Cr: ₹1–2Cr.

3. Unclaimed TDS credit

Customers deduct TDS but the wrong section, wrong PAN, or wrong period means the credit doesn't show up in your 26AS. By March, it's too late to chase. Typically 0.05–0.10% of revenue. At ₹1,000Cr: ₹50L–₹1Cr.

4. DSO borrowing cost

Inflated DSO from late cash application means working capital sits in receivables instead of in the bank. At a 10% borrowing rate, every extra day of DSO at ₹1,000Cr revenue costs ~₹2.7Cr/yr. Typically 0.10–0.20% effective leak. At ₹1,000Cr: ₹1–2Cr.

The team isn't missing it because they're bad

They're missing it because they're stretched thin on execution work. Every hour spent matching cash is an hour not spent chasing a disputed deduction or reconciling 26AS. The leak isn't a discipline problem — it's a capacity problem.

What recovery looks like

Fenmo's recovery model: surface what's leaking, own the chase, post what's recovered. In the first 90 days at most deployments, ₹Cr+ of previously-unowned items get surfaced and resolved. The platform pays for itself from what it finds.