Buyers committing AED 1-3 million to an off-plan project they cannot yet enter physically rely on the escrow framework as the primary protection of their capital. The framework is robust by design — Law No. 8 of 2007 (the Trust Account Law for off-plan real estate development), supplemented by subsequent regulations, requires every project to:

The framework works when followed. The framework does not work when buyers route payments outside the escrow, when the escrow account is not actually a project-specific RERA-registered account, or when the project itself is not registered. Each of these failures has occurred in observed cases. Avoiding them requires the buyer to verify, before wiring funds, that the escrow is real, registered, and project-specific.

The verification, in one paragraph Look up the project on the Dubai REST app or the DLD's project register. Confirm the project shows as registered with a designated escrow account at a named approved custodian bank. The Sale and Purchase Agreement should reference the same escrow account name and account number, in the same registered name, at the same bank. Buyer payments must be made directly to the escrow account, not to a different developer account, not via cash, not via crypto, not to an intermediary. Each of these checks is independently necessary; missing any one breaks the protection.

The Three Layers of Verification

Layer 1 — Project Registration with RERA

RERA registration is the gate before any off-plan sales activity. The registration captures the project's developer identity, master plan, unit count, expected completion timeline, and escrow account designation. The Dubai REST application (released by the DLD) provides the consumer-facing project lookup interface; the DLD's online project register provides the same data through a web channel.

What the buyer should confirm:

A project that does not appear on the DLD register is not legally permitted to sell off-plan units. Marketing material with renderings, prices, and unit availability does not, by itself, mean the project is registered. Buyers should require evidence of registration before signing any document.

Layer 2 — Custodian Bank Verification

RERA-approved custodian banks (operating in compliance with the Trust Account Law framework) are the institutions permitted to hold off-plan project escrow. The list of approved custodian banks is published by the DLD and includes most major UAE banks. The escrow account must be held at one of these banks; an account at a different bank, or an unregistered branch, fails the framework.

What the buyer should confirm:

Layer 3 — Sale and Purchase Agreement Alignment

The SPA is the binding contractual document and must reflect the escrow registration accurately. Key clauses to verify:

A SPA that is silent on the escrow account, or that names a different account from the DLD registration, or that includes payment instructions to a different beneficiary — these are not minor administrative issues. They are signals that the framework is being routed around, intentionally or otherwise, and the buyer's protection is compromised.

The Five Red Flags

Red Flag #1 — Project Not on the DLD Register

Marketing material exists for the project. Renderings are professional. Pricing is published. The project does not appear on the Dubai REST application or DLD project register. This pattern indicates either pre-registration marketing (the developer is collecting expressions of interest before the project is permitted to sell) or active selling without registration (a violation of the Trust Account Law).

The fix: do not pay any deposit, even nominal, until the project shows registered with a designated escrow account. "Reservation fees" paid before registration go into a developer operating account, not escrow, and are not protected by the framework.

Red Flag #2 — Payments Routed to Non-Escrow Account

The DLD-listed escrow account is identified. The SPA references it. The agent or developer's accountant requests the buyer to make payment to a different account — typically a developer operating account at the same bank, sometimes at a different bank. The justification varies (administrative simplicity, payment processing speed, currency conversion).

The fix: the only permitted payment routing is to the project-specific escrow at the registered custodian bank. Any redirection breaks the framework. Bank transfers, where the receiving account name and number are visible to the buyer's bank, are the safest payment method. Cash, cryptocurrency, or third-party intermediaries that aggregate payments before remitting to escrow are red flags regardless of how routine they appear.

Red Flag #3 — Escrow Account Name Mismatch

The DLD registration identifies the escrow as "Project A Trust Account" at Bank X. The SPA references "Project A Escrow" at Bank X. The wire instructions reference "Project A Construction Account" at Bank X. The variations may be benign administrative descriptions of the same account, but they may also indicate that funds are flowing to an account that is not the registered escrow.

The fix: the buyer's bank can verify the destination account name when initiating the transfer. If the receiving account name does not match the registered escrow account name (subject to standard banking abbreviation), the transfer should not be initiated until the discrepancy is resolved with the developer and confirmed against the DLD registration.

Red Flag #4 — Missing Milestone Certifications

The SPA payment schedule ties installments to construction milestones (foundation, ground floor slab, structure complete, MEP rough-in, finishing, handover). Each milestone, in compliance with the Trust Account Law, requires RERA verification before the corresponding tranche can be released to the developer from escrow. Buyers receiving milestone-payment requests should confirm the RERA milestone certification has been issued before transferring.

The fix: ask for the RERA milestone certification number before each installment payment. The certification can be cross-checked through DLD systems. Developers who resist providing the certification number — instead pointing to physical site progress photos or general progress communications — are circumventing the verification step that protects the buyer.

Red Flag #5 — Payments via Intermediary or Aggregator

Some sales channels — particularly those targeting non-resident buyers — route payments through real estate agents' client accounts, escrow service companies (not the project's designated custodian bank), or other intermediary structures before remitting to the project escrow. The buyer's funds therefore sit outside the protected escrow framework for some period.

The fix: pay directly to the project escrow account. If a payment intermediary is involved, the buyer should understand exactly when and how the funds reach the project escrow, and whether the intermediary has any legal entity protections equivalent to the custodian bank framework. In most cases, direct payment is preferable.

What the Framework Does and Does Not Protect

The escrow framework protects the buyer's principal in the event of project cancellation by RERA. Cancelled projects' escrow funds are returned to buyers, with timing and recovery depending on the cancellation type. The protection is structural and meaningful.

The framework does not protect against:

Understanding what the escrow does and does not protect against is part of the diligence. The framework is a meaningful guardrail; it is not a guarantee that the buyer's experience will be free of friction.

Verifying a specific off-plan project's escrow before signing?

The Investment Desk runs the DLD project lookup, custodian bank verification, SPA escrow alignment, and red flag check on specific Dubai off-plan projects. Independent — we don't sell off-plan, broker units, or take developer commissions on the editorial side.

Run the verification →

The Cancelled-Project Recovery Procedure

If a project is cancelled by RERA — typically because the developer fails to meet construction obligations or the project is otherwise non-viable — the recovery procedure for buyer funds operates as follows:

  1. RERA issues the cancellation order, which typically follows a period of investigation and developer notice
  2. The escrow custodian bank is notified and freezes further developer access to escrow funds
  3. Buyers are notified and provided documentation requirements for refund claims
  4. Buyers submit refund claims with supporting documentation: SPA, payment receipts showing transfers to the named escrow, identity documents, and the Oqood registration if available
  5. RERA processes claims and authorises the custodian bank to issue refunds
  6. Refunds are paid in nominal AED to the bank account the buyer designates

The procedure works. The procedure also takes time — typical refund cycles for cancelled projects run 6-18 months from cancellation order to refund receipt, depending on the cancellation complexity and the volume of claims to process. Buyers who relied on the protected funds for downstream commitments can experience meaningful cash-flow gaps during the recovery period.

The Buyer's Pre-Wire Checklist

Before transferring any payment to an off-plan project:

  1. Verify project registration on Dubai REST or DLD project register
  2. Confirm the listed escrow custodian bank is RERA-approved
  3. Match the SPA escrow account designation to the DLD-registered account exactly
  4. Verify the receiving account name and number through the buyer's own bank's transfer process
  5. Confirm the payment is routed directly to the project escrow, not to an operating account, intermediary, or aggregator
  6. For installment payments, confirm RERA milestone certification before transferring
  7. Retain payment evidence (SWIFT confirmations, bank statements, receipts) showing the funds reached the escrow

Each step takes minutes. Each step protects against a specific failure mode. The cumulative discipline takes 30-45 minutes per project and prevents the loss-of-recourse scenarios that occasionally still occur in the market.

For buyers evaluating the broader off-plan economics — payment plan structures (decomposed in our analysis of payment plan economics), and cash-flow profiles across the build cycle — the escrow verification is the foundational diligence that precedes the financial analysis. A project whose escrow framework is not clean is not worth the buyer's broader analysis time.

Closing Notes

UAE Law No. 8 of 2007 created one of the more robust off-plan buyer protection frameworks in the regional real estate market. The framework's robustness depends on buyer use. The buyer who verifies the escrow registration, the custodian bank, the SPA alignment, and the payment routing is fully protected by the framework. The buyer who skips the verification — relying on developer reputation or marketing assurance — exposes themselves to the failure modes the framework was designed to prevent.

The verification is procedural. It is not glamorous, it is not investment analysis, and it does not predict whether the project will deliver on time or on quality. It does ensure that the buyer's principal is protected by the framework that exists for that purpose. Five minutes per project; thirty minutes total across a five-project shortlist. The discipline is the single highest-leverage diligence step the off-plan buyer can take.

Primary sources consulted