Revenue games

Revenue is the first number everyone reads and the easiest to bend, because recognising it is a judgement — a decision about when a sale has really been earned — and judgement is where games live. A company that wants to look bigger or faster has a menu: recognise a sale before it is complete, book one that never happened, ship product to distributors and call the shipment a sale, invoice goods the customer has not taken, route sales through entities it secretly controls, report the gross value of things it merely brokered, or lean on the discretion inside long-contract accounting to pull tomorrow's revenue into today. The names differ; the effect is the same — reported revenue rises faster than the business earns it. illustrative

What makes this tractable is that nearly every one of these games leaves the same fingerprint. A real sale becomes cash now or a receivable collected soon. A recognised sale that is not yet real cannot become cash, so it has to sit somewhere — and it sits in trade receivables or unbilled revenue, swelling year after year while the cash actually collected lags behind. The forensic move of the last module — tie the reported number to the one that must move with it — has a precise target here: tie revenue to cash collected, and watch the gap. Revenue growing much faster than collections, with receivable days stretching, is the signature that some of the growth has been recognised but not earned. It works because revenue recognition runs on the accrual basis: revenue is booked when earned, not when the money arrives — correct and necessary, but it opens the gap the games operate in.

The twist that makes revenue games hard is that the very same "revenue ahead of cash" pattern is a scandal in one business and the normal state of affairs in another. In an FMCG company, where the cycle is short and cash-collected, a swelling receivable is an alarm. In an EPC or real-estate project, where percentage-of-completion recognises revenue as work is done and milestone billing follows later, revenue running ahead of cash is how the accounting is designed to work. So the whole module is one habit — tie revenue to cash, then read the gap against the sector. The tie is universal; what a broken tie means depends on the business it breaks in.

The games are many; the tie is one. Recognise the signature first, then learn the mechanisms it catches.

Recognise early, or recognise nothing. Premature recognition books a genuine sale before it is earned — before goods ship, before the service is delivered, before the return right lapses — pulling next period's revenue into this one. Fictitious recognition books a sale that does not exist at all, invoiced to a customer who never ordered. Both fail the same test: no cash arrives, so the "sale" lands and stays in receivables. Premature recognition tends to reverse — collected late, or the goods come back; fictitious recognition never collects, because there is no real customer behind it.

Move the goods without moving the demand. Channel stuffing ships more to distributors than they can sell through and books each shipment as a sale. Real goods leave, a real invoice is raised, and for a while it looks like demand — but the distributor has not sold it on, cannot pay until they do, and orders less next period, so the receivable swells and future revenue is cannibalised. Bill-and-hold is its cousin: the company invoices and books the sale, but the goods never leave — they sit in the seller's own warehouse "on the customer's behalf." Both recognise revenue on inventory that has not truly changed hands, and both outrun collections.

Route the money, or gross it up. Round-tripping sells to an entity connected to the promoter, books the revenue, and — often in the same period — sends cash back out to that entity as a loan, advance, or purchase, so the "customer's payment" is really the company's own money making a loop. The tell is a related-party sale sitting beside a related-party outflow of similar size. Grossing-up is different in kind: an agent earning a commission reports the entire transaction value as revenue instead of the commission it keeps, inflating the top line without earning a rupee more. It does not break the cash tie the way the others do — it breaks comparability, because a grossed-up number cannot sit beside a net one.

Lean on the estimate. In long-contract businesses, aggressive percentage-of-completion is the game of discretion: revenue is recognised in proportion to progress, and progress is an estimate — so overstating completion or front-loading cost pulls revenue forward. This is the hardest to catch, because the accounting is legitimate and the abuse is in the input. Its signature is the same as the rest — revenue ahead of cash, here landing in unbilled revenue — which is exactly why it cannot be read by the signature alone. The tie tells you revenue has outrun cash; whether that is the honest shape of a project business or an inflated estimate is the sector question the next section answers.

The tie — revenue against cash collected — is run the same way everywhere, but the reading of a gap flips completely, because in some sectors revenue is designed to run ahead of cash and in others it must never.

Tell a reader "revenue running ahead of cash is a red flag" and they are right about FMCG and badly wrong about EPC, where percentage-of-completion is built to recognise before the billing milestone lets any cash in. A real-estate developer's reported revenue is so shaped by recognition policy that the top line is nearly meaningless and the real tie is to buyer collections; an IT firm sits in the middle; a capital-goods maker's revenue is anchored to a harder fact — a machine either left the factory or it did not. A reader who learns one sector's rule as the rule will condemn honest project accounting and wave through channel stuffing in the sector where the tie should have closed. The tie is constant; the threshold at which a gap becomes a game is what you relearn for each business. The question to carry is always: in this sector, how far ahead of cash is revenue allowed to run before the accounting stops explaining it?

Take a composite consumer-goods company that reported a great year: revenue up 34%, profit up 41%, the commentary full of new distributors and deeper rural reach. On the headline it is a fine result, and most of the market read it that way. The forensic reader runs the tie before reading the story. Revenue rose 34%, but cash from operations was roughly flat, and trade receivables jumped from ₹210 crore to ₹400 crore — up 90%, so receivable days stretched from about 30 to ~43. For an FMCG business that is the tell, because the whole point of the sector is a short, cash-collected cycle where days stay near a month; days rising by about half alongside flat cash means most of the incremental revenue never became money and is sitting as a claim on distributors. The most likely explanation is channel stuffing — extra primary sales pushed to the trade to hit the growth number, with secondary sell-through lagging well behind. It is not yet proven; a genuine, disclosed move to longer modern-trade credit terms could stretch days too. But the tie has broken in the sector where it almost never should, so the growth is a question, not a result. illustrative

Now put the same numbers on an EPC company — revenue up 34%, cash well below profit, the gap sitting in unbilled revenue rather than trade receivables. The reading flips. Percentage-of-completion recognises revenue as certified work progresses, ahead of the milestone that permits billing, so unbilled revenue rising with the order book is exactly what an honest, growing contractor's accounts look like. The forensic question is not "why is revenue ahead of cash" — that is the model — but "does the unbilled balance convert?" You tie unbilled revenue to subsequent billings and collections: if this year's unbilled becomes next year's billed receivable and then cash, on the normal milestone cycle, the recognition is real. It turns into a warning only when unbilled revenue keeps outgrowing billings quarter after quarter, never converting. illustrative

So the habit is: run the tie first, read it against the sector second. Set revenue growth beside operating-cash growth and beside the growth in receivables and unbilled revenue; compute receivable days over two or three years. Then ask what the sector permits. Where the tie closes in a sector that demands it, the growth is corroborated. Where it breaks — or where, in a project business, the unbilled balance never converts — you have found the one question to ask before you believe the top line.

The tie locates a broken revenue number; it does not tell you which game broke it, or whether a game was played at all. Revenue ahead of cash with a swelling receivable is equally consistent with channel stuffing, premature recognition, a fictitious sale, a deliberate and honest extension of credit to win a large account, and a genuine late-year order booked in the final week. The signature is a prompt to investigate, not a proof of manipulation, and the answer comes from the ageing, the related-party note, the segment detail, the sell-through, and the concall. Reading a broken tie as a verdict is the paranoid error — it stops the investigation where it should start.

Worse, the tie cannot tell you that revenue which does convert to cash is clean. Round-tripping is built precisely to keep the cash tie closed: the company sends its own money out to a related party and brings it back as a customer receipt, so revenue and cash appear to move together and the signature never shows. Only a different tie catches it — sales to the independent cash of independent customers, related-party inflows set against related-party outflows. This is why the forensic reader adds ties rather than resting on one: a game engineered to satisfy the revenue-to-cash check usually betrays itself on the who-is-the-customer check or the tax check instead. And disclosure is no defence — round-tripping is often fully disclosed in the related-party note, because it is legal on its face. Disclosure records that a transaction happened, not that it was real or priced at arm's length. The same discipline strips every grossed-up top line back to its net economics before any comparison: the number that fools you is the one you never converted to the same basis as everything beside it.

Finally, the tie cannot set the sector threshold for you. It tells you revenue is a certain distance ahead of cash; it cannot tell you whether that distance is normal for a project business or abnormal for a consumer one — that comes from knowing the sector's accounting and its honest peers. A reader who has not built a feel for an ordinary EPC unbilled balance or an ordinary FMCG receivable will either cry wolf on healthy project accounting or miss a stuffed channel because the absolute receivable "did not look that big." The tie is universal; the threshold is learned, and no signature substitutes for the sector knowledge that calibrates it.

When a company posts strong revenue growth that has not turned into cash, the forensic analyst does not challenge the revenue head-on — she puts the tie on the table and asks the company to close it: "Revenue grew 34% but operating cash was roughly flat and receivable days went from 30 to about 43 — can you break the receivable down by ageing and by distributor, give us primary versus secondary sales, and say how much of the growth was sell-through to end-customers?" The question names the broken tie and asks for the decomposition that would close it.

A good answer accepts the gap and reconciles it with specifics you can hold it to:

"Fair to press on it — the receivable did build this year. About ₹120 crore of the ₹190 crore increase is our shift of modern-trade and e-commerce accounts to 45-day terms, which is contractual and current, and we can show you the ageing: over 90% is under 60 days. Secondary sales grew 26% against primary of 34%, so yes, roughly eight points of the primary growth is pipeline fill into new distributors, which normalises next quarter as they reorder at sell-through. We'd guide you to read underlying growth closer to the secondary number." illustrative

It splits the receivable into named and aged pieces, distinguishes primary from secondary sales, quantifies the pipeline fill, and points to the more honest underlying number. The evasive answer reassures without reconciling:

"We're very comfortable with the health of our channel and the strength of the demand environment. Receivables can move around quarter to quarter with the timing of dispatches, and we manage the business for the full year. Our distributor relationships have never been stronger and our auditors are comfortable with our revenue recognition. We remain confident in our growth momentum."

"Comfortable with the channel" and "receivables move around" are assertions, not the ageing and the primary-versus-secondary split the question asked for; it names no distributor, no sell-through figure, no terms, and reaches for the auditor and "momentum" in place of the numbers that should agree. The follow-up that settles it is the one nobody asks: "What were your secondary sales — actual sell-through — versus primary billing this year, and how many days of inventory are sitting in the channel?" If "healthy channel, strong momentum" is allowed to stand, the analyst has capitalised primary billing as if it were end-demand. The silence is the tell — a company whose channel is genuinely clean usually volunteers the sell-through, because it flatters them.