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

A residential developer has its best selling year in a decade — it books a record number of flats, collections pour in, launches sell 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 — revenue — close to useless for judging how the business is actually doing. illustrative

The reason is the accounting rule. A developer recognises revenue only when a project completes, not when it sells the flats. So the revenue in any given year reflects which projects happened to finish that year — projects sold three or four years earlier — and has almost nothing to do with the current year's selling. A great selling year shows up in revenue only when those flats are handed over, 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.

So this module teaches the reader to ignore the revenue line and read the two numbers that actually measure a developer: pre-sales, the value of flats booked this year, which is the real activity, and collections, the cash actually received. Together they tell you whether the developer is selling and getting paid — the leading indicators of the revenue that will eventually be reported. Read pre-sales and collections and the business is clear; read reported revenue and you will praise the developer in its worst year and doubt it in its best.

The cash-flow module taught that profit and cash can diverge; real estate is the sector where reported revenue itself diverges from the business, by design, because of when the accounting recognises a sale. This module exists because a reader applying the ordinary instinct — revenue measures how much a company sold this year — will be systematically misled by a developer, whose revenue measures how much it finished this year.

Two ideas replace the revenue line. Pre-sales and collections are the developer's real activity measures: pre-sales (also called bookings) is the value of flats sold during the year, and collections is the cash received against those and earlier sales. These are the leading indicators — flats sold now become revenue years later on completion, and cash collected now funds the construction. And completion-based revenue is the lagging, lumpy figure the P&L reports, recognised only when a project is handed over, which is why it spikes and collapses on the rhythm of completions rather than sales.

Without this module, three errors follow. A reader judges a developer's year by its reported revenue and gets the direction wrong. A reader compares two developers on revenue when one is mid-completion-cycle and the other between projects, and reaches a nonsense conclusion. And a reader reads the parent's modest net debt as low leverage, missing that developers hold much of their borrowing in project-level special-purpose vehicles (SPVs — a separate company set up to hold a single project's assets and debt). The point is to read pre-sales and collections as the real business, treat reported revenue as a completion artefact, and look through to the SPV-level debt for the true financial risk.

Watch the three numbers move apart over time.

Why revenue lags and lumps. A flat sold today under a completion-based rule produces no revenue until the whole project is finished and handed over, often three to five years later. Meanwhile the developer has taken the booking, is collecting the cash in instalments, and is spending it on construction. So in the years between sale and completion, a great deal of real business happens with no revenue to show for it — and then, in the completion year, several years of sales land as revenue at once. The revenue line therefore has a rhythm set by construction and handover, not by selling, and it can move opposite to the actual business.

Pre-sales — the real activity. Pre-sales is the value of flats booked during the year, and it is the number that tells you whether the developer is actually selling. It leads reported revenue by years, so a rising pre-sales trend means rising future revenue, and a falling one means future revenue will drop regardless of what the current P&L shows. Read alongside area sold and realisation per square foot (the price actually achieved per square foot), pre-sales tells you both the volume of selling and the price achieved.

Collections — the cash. Collections is the cash actually received from customers, against both current and past bookings. It funds construction and services the debt, so it is the developer's real cash engine, and it should broadly track pre-sales over time. A gap opening between strong pre-sales and weak collections is a warning — bookings that are not converting to cash, perhaps because customers are struggling or the developer has sold on soft terms.

Where the leverage hides. Developers commonly hold project debt in special-purpose vehicles, one per project, and structure land through joint-development agreements with landowners — deals where the landowner contributes the land for a share of the finished project instead of the developer buying it outright. So the parent's standalone net debt can look modest while the group carries far more borrowing at the SPV level, and the land pipeline sits in arrangements that share revenue rather than showing as owned inventory. The real leverage and the real land position are read at the consolidated and SPV level and in the notes on joint-development agreements, not on the parent's face — the same standalone-versus-consolidated lesson, applied to a sector built on project vehicles.

The idea that revenue measures the year's selling is true for most businesses and structurally false for a developer. Set it beside the sectors whose revenue-recognition it most resembles and most departs from.

The inversion is that for a developer, reported revenue and business activity can move in opposite directions, because the 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, recognised as each meal is sold; a developer's revenue is a memory of activity, surfacing only when concrete is poured and keys 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. The reader must hold that revenue-recognition itself is a variable across these sectors: the same word, "revenue," describes a live measure in one business and a lagging artefact in another, and knowing which you are reading is the 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 the third year, falls back 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 slump in the fourth. That reading is almost entirely an artefact. illustrative

Now read pre-sales and collections. Pre-sales rose steadily every single year — ₹3,200 crore, ₹4,100 crore, ₹4,600 crore, ₹5,400 crore, ₹6,300 crore — and collections rose alongside them, from ₹2,600 crore to ₹5,300 crore. The business was growing smoothly and strongly throughout; there was no blowout year and no slump. The third-year revenue spike was simply several projects completing at once, surfacing sales made years earlier; the fourth-year "slump" was just a year with fewer completions. Judged on pre-sales and collections — the real activity and the real cash — this is a steadily compounding developer, and the revenue line's lurches are noise.

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 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 habit to build: for a developer, cross out the reported revenue line and read pre-sales and collections as the business — pre-sales for whether it is selling and at what price, collections for whether the cash is arriving. Then read the balance sheet at the consolidated and SPV level for the true leverage, and the joint-development notes for the real land position. Reported revenue is not wrong, but it answers a question — how much completed this year — that is almost never the one you are asking, which is how the business is actually doing now.

Pick a year and compare the three numbers — pre-sales, collections and reported revenue — for the same developer. Watch how far the reported revenue drifts from the real activity.

Land on the completion-spike year and the tool flags it: reported revenue jumps above pre-sales because old projects finished, not because selling improved — a reader trusting revenue would overstate the year. 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 around on completion timing. The tool makes the module's rule physical: for a developer, read pre-sales and collections, and treat reported revenue as an artefact of when projects happen to finish.

Pre-sales tell you what the developer sold, but not whether those sales will hold. Bookings can be cancelled, especially if they were made on soft terms or to speculative buyers who never intended to complete, and a developer under pressure can inflate pre-sales with easy cancellation policies that flatter the headline. The collections trend is the check — genuine sales convert to cash on schedule — but a gap between rising pre-sales and lagging collections can take a year to appear, and until it does, the pre-sales figure is a claim about demand that the cash has not yet confirmed.

Nor do pre-sales and collections reveal the quality of the land bank behind the growth. A developer can post strong bookings by selling in a hot micro-market while its larger land holdings sit in the wrong locations, mispriced or entangled in litigation and approvals. The 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 pre-sales number.

And the sector's reliance on project-level vehicles and joint arrangements means even the consolidated accounts can understate the risk. Debt guaranteed by the parent but held in an SPV, revenue-share obligations to landowners, and approvals that can be revoked all 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. Pre-sales and collections read the demand side of the business well; the supply side — land, approvals, financing structure — has to be read separately, and it is where the developers that fail usually fail.

How it comes up. When reported revenue jumps or slumps, a sharp analyst goes straight 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, verbatim-style.

"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 higher, around 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."

It dismisses the revenue headline, gives pre-sales with volume and price, confirms collections and cancellations, and owns the SPV-level leverage. It hands you the real business.

An evasive answer, verbatim-style.

"We're delighted to report record revenue growth this year, reflecting strong execution and healthy demand across our portfolio. 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."

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-level borrowing. "Pre-sales momentum remains robust" is an adjective where a number was asked for, and "record revenue" is precisely the completion artefact a serious analyst discounts.

The follow-up nobody asks. "What is group net debt including all SPV and guaranteed debt, and what was your booking-cancellation rate this year?" That forces the real leverage and the quality of pre-sales into the open. Watch what happens when it is not asked. If "record revenue, strong balance sheet" is allowed to stand, an investor credits a completion artefact as growth and a parent-only net-debt figure as low leverage. The silence is the tell — either the group leverage is uncomfortable, or the pre-sales are propped up by cancellations the developer would rather not quantify.

The first trap is reading reported revenue as the developer's performance. Because revenue is recognised only on completion, it lurches with the construction cycle and can move opposite to the actual selling — record revenue in a weak year, a slump in a strong one. A reader who judges the year, or ranks two developers, on the revenue line will get the direction wrong, praising a business whose sales are drying up because its old projects are finishing, and doubting one whose bookings are surging but not yet recognised. The revenue line is the number the sector cannot help reporting; it is not the number to read.

The second trap is trusting pre-sales without checking collections and cancellations. Pre-sales is the right measure of activity, but it is a booking, not cash, and bookings can be soft — made on easy terms, to speculative buyers, cancellable later. A developer can flatter pre-sales with generous cancellation policies, and the gap only shows when the collections fail to follow. Rising pre-sales with lagging collections, or a creeping cancellation rate, is the tell that the headline demand is not as solid as it looks, and reading pre-sales alone misses it.

The third trap is reading the parent's balance sheet as the group's leverage. Developers hold project debt in special-purpose vehicles, so the parent can show modest net debt while the group carries far more, guaranteed by the parent but sitting one layer down. The land, too, is often on joint-development terms that share revenue rather than showing as owned inventory. A reader who takes the parent's tidy net-debt figure at face value understates the financial risk, and 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.