1. Identify the reporting company before using its numbers
IFRS 10 describes consolidated statements as presenting a parent and its subsidiaries as one economic entity. That scope matters when someone uses a group's figures to explain a particular development.
DR recommends recording three names separately: the company issuing the financial report, the developer identified in the project record and the seller named in the proposed contract. Then document the relationship between them. A shared brand should prompt that check rather than fill it in.
Ask whether the quoted information concerns a group, subsidiary, business segment or individual project. If a presentation relies on support from another company, request the document explaining that support and obtain qualified review of its effect.
The practical output is a short identity map. It should show which entity each document concerns and where the connection remains unresolved. This gives a buyer, broker or adviser a common starting point before discussing financial strength.
References: IFRS Foundation — IFRS 10; identity-map method is DR analysis
2. Read a real disclosure without combining different measures
Emaar Development's release dated 7 August 2026 reports H1 property sales of AED22.4 billion, revenue of AED13.3 billion and revenue backlog of AED127.7 billion at 30 June. Its investor-relations page corroborates sales and backlog and labels sales as including joint ventures and joint development agreements.
These are historical issuer disclosures, not October results. The example illustrates why a number needs its label, period and reporting scope. It is not a recommendation concerning Emaar or a finding about a particular project.
DR's reading rule is to preserve the source's distinctions. Do not add sales and revenue as if they were two independent cash receipts. Do not subtract revenue from sales and label the difference unpaid customer money. Those operations need a reconciliation that the three headlines alone do not supply.
| Reported measure | Period or date | Question before using it |
|---|---|---|
| Property sales | A reporting period | Which transactions and entities are included? |
| Revenue | A reporting period | Which accounting policy and activities produced it? |
| Revenue backlog | A stated date | How is the remaining amount defined and reconciled? |
References: Emaar Development — H1 release, 7 August 2026 · Emaar Development — Investor-relations cross-check
3. Check how revenue is recognised
Under IFRS 15, revenue follows the satisfaction of contractual performance obligations. Recognition may occur over time or at a point in time, depending on the applicable requirements. For recognition over time, an appropriate progress measure is used.
DR therefore recommends locating the actual revenue-policy note before interpreting a developer's revenue figure. Ask which activities it covers and whether different activities use different recognition approaches. Avoid assuming that every dirham of revenue represents either a newly signed sale or a completed handover.
Keep the accounting question separate from your unit's contractual question. A group revenue announcement does not identify the evidence required under your SPA for the next instalment. Record the relevant clause and supporting project documents in their own file.
If the policy is technical or its application unclear, take the complete note to a qualified accountant. A shortened marketing explanation may omit the conditions needed to understand the reported amount.
References: IFRS Foundation — IFRS 15 revenue-recognition principles
4. Follow cash separately from profit
IAS 7 separates operating, investing and financing cash flows. Its indirect method adjusts profit for non-cash items and relevant timing differences. Profit and cash flow therefore answer different questions.
For a practical review, DR suggests tracing the movement from opening cash to closing cash using the statement and its notes. Identify the stated sources and uses rather than inferring the explanation from the closing balance alone.
Ask where borrowing, asset purchases, customer collections and other material movements appear in the actual report. A larger closing balance needs an explanation of how it arose. Equally, a reduction should be examined before drawing a conclusion about its cause.
Next, record restrictions or qualifications disclosed beside cash balances. Keep the amount, reporting entity and relevant date together. Do not calculate a universal safety score by dividing a headline cash number by a separate project's estimated costs.
References: IFRS Foundation — IAS 7; review sequence is DR analysis
5. Worked example: backlog and uncollected money can differ
Every input in this example is invented. Assume one contract portfolio with total consideration of AED100 million, cumulative recognised revenue of AED40 million and cumulative customer receipts of AED55 million. Assume no cancellations, variations, financing adjustments or other differences.
For this model only, define backlog as contract consideration not yet recognised as revenue. Backlog is therefore AED60 million. The amount not yet collected is AED45 million. The two results differ because recognition and collection have different assumed positions.
Neither result calculates the cash currently available. Some receipts may already have been spent, and the model provides no opening bank balance, expenditure record or restrictions. It also provides no estimate of remaining construction costs.
Use this exercise to test a claim such as the backlog fully funds completion. The missing questions concern collection timing, remaining obligations and usable resources. For an actual company, use its published definition and reconciliation; do not impose this simplified model on its accounts.
| Invented input or calculated result | AED million |
|---|---|
| Total contract consideration | 100 |
| Cumulative recognised revenue | 40 |
| Cumulative customer receipts | 55 |
| Modelled backlog: 100 − 40 | 60 |
| Not yet collected: 100 − 55 | 45 |
| Current available cash | Not established |
6. Build a comparison sheet that preserves missing information
DR proposes the following worksheet for reviewing two disclosures or successive reports from the same developer. It is an organising tool, not an accounting standard or developer rating.
Give every figure a document reference. Record whether the material is a press release, presentation or financial statement, and preserve any auditor or reviewer report supplied with it. Do not describe a document as audited merely because it appears in an investor-relations section.
Compare equivalent periods and scopes. If one figure includes joint ventures and another does not, retain that difference prominently. If a definition changed, request the explanation before calculating growth. Missing information should remain a question, not become a zero.
| Field | What to record | Follow-up question |
|---|---|---|
| Entity and scope | Exact issuer; consolidated, separate or segment reporting | Does this cover the entity relevant to the project? |
| Dates | Publication date, reporting period and balance-sheet date | Are the observations comparable? |
| Document status | Document type and attached assurance report | What work does the accompanying report actually describe? |
| Sales and backlog | Definitions, coverage and reconciliation | Are reservations, changes or joint arrangements treated consistently? |
| Revenue | Relevant policy and activity breakdown | What recognition basis applies? |
| Cash | Cash-flow statement and balance notes | What explains the movement and any restrictions? |
| Obligations | Relevant borrowing, commitment and maturity disclosures | Which payments and conditions need specialist review? |
| Project connection | Document linking the corporate evidence to the development | What remains unproven at project level? |
References: IFRS Foundation — Consolidated reporting scope; worksheet is original DR analysis · IFRS Foundation — Cash-flow reporting context
7. Connect the corporate review to project-specific evidence
DLD describes escrow as a project account and explains that it is used for developing the relevant project. Its separate Project Status Enquiry provides project details and completion information. These sources address a different level of evidence from corporate financial reporting.
DR recommends placing the corporate worksheet beside the precise project record, relevant registration evidence and documented payment instructions. Identify what each record establishes and avoid carrying an answer from one column into another.
For an incoming investor considering a stalled development, the next task is a project-specific review of remaining scope, costs, timing and funding conditions. A corporate backlog figure cannot fill those fields without supporting project evidence.
For an existing owner, retain the dated financial update as background and make the next enquiry specific: which record supports the proposed project action? This approach keeps a useful company disclosure connected to the question you actually need answered.
References: DLD — Project escrow guidance · DLD — Project Status Enquiry
8. Finish with questions supported by documents
A useful review ends with a short list of supported observations and unresolved questions. For each question, name the missing document and explain how it would change the assessment. Avoid turning the number of unanswered questions into an invented probability of default or delay.
If public financial information cannot be obtained, record that limitation. Non-access is not a finding of insolvency or misconduct. Request appropriate information through authorised channels and seek qualified accounting, legal or financial advice where the decision requires it.
This article reviewed public issuer pages, IFRS Foundation summaries and DLD guidance. The historical corporate example was checked against the issuer's release and investor-relations page; a full current financial-statement review was not performed. No private account, company data room or individual project was inspected.
Development Resolution helps organise evidence for delayed or distressed project assessments. This guide does not certify accounts, guarantee funding or completion, or recommend an individual property or securities investment.
References: Emaar Development — Public disclosure used within the stated review limits · DLD — Separate project-information scope
Questions about reading developer financial disclosures
Are developer sales and revenue the same?
Do not treat them as interchangeable. Preserve the issuer's sales definition and read the accounting policy supporting recognised revenue.
Does revenue backlog show cash available for construction?
No. Establish the issuer's backlog definition, then examine collections, expenditure, restrictions and project obligations separately. The article's hypothetical example shows why the amounts can differ.
Do group accounts establish funding for my project?
They provide corporate context. A project-specific funding conclusion needs evidence connecting the relevant entity, resources, conditions and remaining project obligations.
Does missing public financial information prove a developer is in difficulty?
No. Record the access limitation and the information still required. Do not infer insolvency or misconduct from a failed search or unavailable document.
Does this guide rate Emaar or another developer?
No. The dated issuer example illustrates reporting labels. DR did not conduct a full financial-statement review or assess an individual company's financial condition.
Primary and official sources
Project status and procedures can change. When a decision depends on current information, verify the live primary source rather than relying only on a secondary summary.