Real estate: why reported revenue is the least useful number in the report

A residential developer has its best selling year in a decade - a record number of flats booked, collections pouring in, launches selling out - and its reported revenue falls. The next year it sells almost nothing new, and its reported revenue doubles. Nothing is wrong with the accounts. This is simply how real-estate revenue works, and it makes the single most-quoted number in the report close to useless for judging how the business is actually doing. illustrative

The cause is the recognition rule. A developer books revenue only when a project completes, not when it sells the flats - so the revenue in any year reflects which projects happened to finish, projects sold three or four years earlier, and has almost nothing to do with the current year's selling. A great selling year surfaces in revenue only on handover, years later; a weak selling year can still post record revenue if a big old project completes. The revenue line is a rear-view mirror pointed at construction timing, not a speedometer of the business. Read it and you will praise the developer in its worst year and doubt it in its best.

Two numbers replace the revenue line, and both lead it. Pre-sales - also called bookings - is the value of flats sold during the year: the developer's real activity, the thing the market instinct thinks "revenue" measures. Collections is the cash actually received against those and earlier sales: the real cash engine that funds construction and services the debt. A flat sold today produces no revenue until the whole project is finished and handed over, often three to five years on - but in the meantime the developer has taken the booking, is collecting the cash in instalments, and is spending it on concrete. So years of real business happen with no revenue to show, and then, in the completion year, several years of sales land at once as completion-based revenue. That is why the P&L line spikes and collapses on the rhythm of handovers rather than sales.

Read the two leading numbers together and the business is clear. Rising pre-sales means rising future revenue whatever the current P&L shows; falling pre-sales means future revenue will drop however good this year's completions look. Read alongside area sold and realisation per square foot - the price actually achieved - pre-sales tells you both volume and price. Collections should broadly track pre-sales over time; a gap opening between strong bookings and weak collections is a warning that sales are not converting to cash, perhaps because buyers are struggling or the flats were sold on soft terms.

And the leverage hides where the revenue does not show. Developers commonly hold project debt in special-purpose vehicles - a separate company per project, holding that project's assets and borrowing - and structure land through joint-development agreements, where a landowner contributes the land for a share of the finished project rather than selling it. So the parent's standalone net debt can look modest while the group carries far more one layer down, and the land pipeline sits in revenue-share arrangements rather than as owned inventory. The real leverage and the real land position are read at the consolidated and SPV level and in the joint-development notes - the same standalone-versus-consolidated lesson, applied to a sector built on project vehicles.

The instinct that revenue measures the year's selling is true for most businesses and structurally false for a developer. What separates the sectors is the recognition regime - when a sale becomes revenue - and the same word describes a live measure in one business and a lagging artefact in another.

The inversion is that for a developer, reported revenue and business activity can move in opposite directions, because revenue is recognised at completion while the activity is the selling that happened years earlier. A QSR (quick-service restaurant) chain's revenue is the activity, booked as each meal sells; a developer's revenue is a memory of activity, surfacing only when keys are handed over. The EPC (engineering, procurement and construction) contractor sits between them - its over-time recognition smooths the lumps but introduces an estimate, which is its own lever, taken up in the next module. Knowing which regime you are reading is the whole difference between judging a developer correctly and exactly backwards.

Read the composite developer's five years. Reported revenue runs ₹1,900 crore, ₹2,100 crore, then jumps to ₹4,800 crore in year three, falls to ₹2,600 crore, and recovers to ₹3,200 crore. On the revenue line alone this looks like a wildly volatile business having a blowout third year and a fourth-year slump - and that reading is almost entirely an artefact. Now read pre-sales: ₹3,200, ₹4,100, ₹4,600, ₹5,400, ₹6,300 crore - up every single year - with collections rising alongside, from ₹2,600 to ₹5,300 crore. The business grew smoothly and strongly throughout. The third-year "blowout" was several projects completing at once, surfacing sales made years earlier; the fourth-year "slump" was just a year with fewer handovers. Judged on the real activity and the real cash, this is a steadily compounding developer, and the revenue line's lurches are movement that wears the costume of information without carrying any. illustrative

Then look at the leverage. The parent's net-debt-to-equity looks modest, dipping to 0.44 in the completion-heavy third year as cash came in - but the composite flags that 52–60% of the debt sits at the SPV level and half the pipeline is on joint-development agreements. So the real leverage is higher than the parent's headline, held in the project vehicles, and the land position is partly revenue-share rather than owned. A reader trusting the parent's tidy net-debt figure would understate the financial risk exactly as reading standalone accounts understates a group.

The instrument below lets you pick a year and compare the three numbers for the same developer. Land on a completion-spike year and reported revenue jumps above pre-sales because old projects finished, not because selling improved. Move to a year where pre-sales run ahead of revenue and the message flips: the developer is selling more than its completion-based P&L yet shows. Either way, the pre-sales and collections bars are the steady, real measure and the reported-revenue bar is the one lurching on completion timing. The habit to build: for a developer, cross out the reported revenue line, read pre-sales and collections as the business, then read the balance sheet at the consolidated and SPV level for the true leverage.

When reported revenue jumps or slumps, a sharp analyst goes straight past it to pre-sales. The question sounds like this: "Reported revenue rose 130% on completions, but what were pre-sales and collections this year, how do they compare with last year, and what's your cancellation rate?" The analyst is refusing the revenue headline and asking for the real activity.

A good answer takes the question apart:

"Right to separate them. The revenue jump is three projects completing; ignore it for run-rate. Pre-sales were ₹6,300 crore, up 17%, on 5.2 million square feet at a realisation of ₹12,100 - so volume and price both up. Collections were ₹5,300 crore, tracking pre-sales, and our cancellation rate held at about 4%. Net debt looks low at the parent, but including SPV-level debt the group number is nearer 0.9x, which we disclose in the consolidated note. So the underlying business grew mid-teens; the revenue line just caught up on old projects." illustrative

It dismisses the revenue headline, gives pre-sales with volume and price, confirms collections and cancellations, and owns the SPV-level leverage. An evasive answer does the opposite:

"We're delighted to report record revenue growth this year, reflecting strong execution and healthy demand. Our pre-sales momentum remains robust and our balance sheet is among the strongest in the sector with low net debt. We remain confident in our growth trajectory."

It leads with the meaningless revenue record, gives no pre-sales figure, no collections, no cancellation rate, and cites the flattering parent net debt while ignoring the SPV borrowing. "Pre-sales momentum remains robust" is an adjective where a number was asked for. The follow-up that settles it - "What is group net debt including all SPV and guaranteed debt, and what was your booking-cancellation rate?" - forces the real leverage and the quality of pre-sales into the open. If "record revenue, strong balance sheet" is allowed to stand, an investor has credited a completion artefact as growth and a parent-only figure as low leverage. The silence is the tell.

Pre-sales are the right measure of activity, but they are a booking, not cash, and bookings can be soft - made on easy terms, to speculative buyers, cancellable later. A developer under pressure can flatter pre-sales with generous cancellation policies, and the gap only shows when collections fail to follow. So the second trap, after reading the revenue line itself, is trusting pre-sales without checking collections and the cancellation rate: rising bookings with lagging cash, or a creeping cancellation rate, is the tell that the headline demand is not as solid as it looks.

Nor do pre-sales and collections reveal the quality of the land bank behind the growth. A developer can post strong bookings by selling into a hot micro-market while its larger holdings sit mispriced, or entangled in litigation and approvals. Pre-sales measure this year's selling; they say nothing about whether the pipeline of future projects is worth what the balance sheet or the market implies - which depends on location, approval status, and the terms of the joint-development agreements, none of which is in the number. The demand side of the business reads well from pre-sales and collections; the supply side - land, approvals, financing structure - has to be read separately, and it is where the developers that fail usually fail.

Which is the third and gravest trap: reading the parent's balance sheet as the group's leverage. Debt guaranteed by the parent but held in an SPV, revenue-share obligations to landowners, approvals that can be revoked - these sit in the notes and the fine print, and a developer with a clean-looking consolidated balance sheet can carry obligations that only surface in a downturn. When projects stall and SPV debt still has to be serviced, that understated leverage is exactly what turns a slowdown into a solvency problem.