Property Developer Accounting: IFRS 15 & Escrow

01
Introduction

Chapter 16 walked through how a development actually gets built — land, approvals, financing, construction, escrow, handover. This chapter opens the ledger behind that same project. When a buyer signs an off-plan SPA and hands over a post-dated cheque for 20% of the purchase price, has the developer earned that 20%? Not necessarily. The cash has moved. The revenue has not — not yet, and not automatically at the same pace.

This distinction is not a technicality. It determines a developer's reported profit in any given year, its financial statement quality, its ability to raise financing, and — for the investor reading this book — a genuine signal of financial discipline worth understanding, even as a buyer rather than an accountant.

02
Why Real Estate Revenue Recognition Is Different

Most retail transactions recognize revenue at a single point in time — the moment goods are delivered or a service is completed. Off-plan property is different: construction happens over months or years, buyer payments are staged across that same period according to a payment plan, and the two timelines rarely match exactly. IFRS 15 exists precisely to resolve this mismatch — to recognize revenue based on the value of work actually performed, not the timing of the cash that funded it.

03
The IFRS 15 Five-Step Model

IFRS 15 applies a common five-step model to determine how and when revenue should be recognized:

For a typical off-plan residential unit, the SPA is the contract, delivering the completed unit is generally the single performance obligation, the transaction price is the agreed sale price, and step 5 is where the real work happens: determining whether that obligation is satisfied at a single point in time (on handover) or progressively over time (as construction proceeds).

04
Point in Time vs Over Time Recognition

Many regulated off-plan structures in the UAE — where staged payments are tied to construction milestones and the underlying unit is effectively pre-sold and specific to that buyer — support over-time recognition using the Percentage of Completion (POC) method. Whether a specific project qualifies is a judgment that depends on the actual contract terms and should be confirmed with a qualified accountant.

05
The Percentage of Completion Method

The input method (costs incurred) is the most commonly used measure of progress in construction, though output methods (e.g., surveys of physical completion) can also apply depending on which best depicts the transfer of control. Whichever method is used, the principle stays the same: revenue tracks the work performed, not the cheque that happened to clear that month.

06
RERA-Style Escrow Accounting

Buyer payments for a regulated off-plan project are deposited into a project-specific escrow account, not the developer's general operating account. This restricted cash is released to the developer in stages, generally tied to independently verified construction progress rather than the developer's own say-so. The effect is twofold: it protects buyer funds from being diverted to another project, and it creates a natural audit trail linking cash releases directly to physical progress — the same verification chain covered from the investor's side in Chapter 13.

07
Contract Liability vs Contract Asset

Because cash collection and revenue recognition rarely move in perfect lockstep, IFRS 15 introduces two balance sheet items to capture the gap at any point in time:

Every off-plan unit moves between these two states throughout construction, depending on how the payment plan's timing compares with actual physical progress on site.

08
Worked Example — Project Assumptions

A single off-plan unit, used consistently through every journal entry in this chapter:

09
Entry 1 — Advance Receipt into Escrow

At booking, the buyer pays the 20% deposit, which is deposited directly into the project escrow account rather than the developer's general account.

No revenue is recognized yet — 0% of construction has occurred. The full amount sits as a liability, exactly as advance rent did in Chapter 15, but restricted to an escrow account rather than the developer's freely available bank balance.

10
Entry 2 — Recording Work in Progress

As construction proceeds, costs incurred are capitalized as Work in Progress (WIP) — materials, labour, contractor payments and directly attributable overhead.

At this point: Costs incurred to date = AED 350,000, against total estimated costs of AED 1,400,000 → % Complete = 25%.

11
Entry 3 — Escrow Release Tied to Progress

Once independently verified construction progress is confirmed, funds are released from the restricted escrow account to the developer's operating account, in accordance with the applicable escrow rules and release schedule.

This entry moves cash from restricted to unrestricted status — it does not itself recognize any revenue. The revenue recognition entry is entirely separate, and comes next.

12
Entry 4 — Revenue Recognition (25% Complete)

Cash collected to date (assume the booking deposit plus one construction-linked installment) = AED 800,000 (40% of price, per the payment plan). Since revenue recognized (AED 500,000) is less than cash collected (AED 800,000), the developer still holds a Contract Liability of AED 300,000.

Remaining Contract Liability after this entry: AED 800,000 collected − AED 500,000 recognized = AED 300,000, carried forward on the balance sheet.

13
Entry 5 — The Contract Asset Scenario

Construction later reaches 60% complete. Costs incurred to date total AED 840,000 (60% of AED 1,400,000). Applying the formula:

Suppose cash collected to date remains at AED 1,000,000 (50% of price), because the payment plan's next construction-linked installment has not yet fallen due. Construction has outpaced billing — recognized revenue (AED 1,200,000) now exceeds cash collected (AED 1,000,000), by AED 200,000.

The developer has now performed more work than it has been paid for — the AED 400,000 Contract Asset represents genuine, verified progress awaiting the buyer's next scheduled instalment. This is the scenario your notes specifically flag: recognized revenue outpacing cash collected, converting what was a liability into an asset on the same project's balance sheet.

14
Running Summary Table

Notice the sign flip in the final column — this single row is the entire "contract asset scenario" in numeric form: the same project moved from owing the buyer work (a liability) to having performed work it hasn't yet been paid for (an asset), purely because construction progress and the payment schedule fell out of step.

15
Handover — Final Revenue Recognition

At 100% completion and handover, the remaining revenue is recognized, matched against the remaining costs, and any outstanding contract asset or liability is cleared as the final instalment is collected and the unit is formally transferred — the accounting mirror of the handover process covered operationally in Chapters 12 and 16.

16
Disclosure Requirements

IFRS 15 requires developers to disclose disaggregated revenue, contract balances (contract assets and contract liabilities) and how they've changed during the period, significant judgments used in determining the timing of revenue recognition and measuring progress, and the methods applied to estimate costs to complete. Investors reviewing a developer's financial statements — as part of Chapter 6's Developer Intelligence™ due diligence — can learn a great deal from how transparently these disclosures are presented.

17
Common Accounting Pitfalls

18
Chapter Summary