# Dubai off-plan payment plan amendments: the evidence chain (2026)

> A record-by-record guide to checking a Dubai off-plan payment-plan change across the SPA, signed annex, Oqood output, ledger and receipt.

Source: https://withlida.com/insights/dubai-off-plan-payment-plan-amendment-evidence

---

:::intro
Dubai Land Department lists 6 business days for its Oqood route to amend data in the real estate provisional register, but that service page does not supply the buyer's old schedule, new instalments or payment history. A defensible file therefore starts with the original signed SPA schedule, adds the amendment annex signed by both parties, then reads the DLD output, developer account record and receipt only for the separate facts each one actually shows ([DLD](https://dubailand.gov.ae/en/eservices/request-to-amend-the-initial-procedures-data/), accessed 29 September 2026).
:::

:::summary
- The signed amendment annex is the bridge between the original SPA schedule and a revised schedule because DLD names both documents in its amendment service requirements.
- Oqood is the official route on this service page; its named output is a provisional registration e-certificate sent to the purchaser by email.
- The DLD page does not say that the e-certificate reproduces revised instalments, records acceptance history or proves a payment was made.
- A developer account record and a receipt belong after the signed change in the evidence chain. Their displayed fields do not rewrite the contract by themselves.
- Percentages and dates can reconcile a schedule. Arithmetic cannot prove signature, registration or payment.
:::

## The signed annex connects the old schedule to the new one

The original signed sale and purchase agreement, or SPA, is the starting record. A revised schedule becomes traceable when a separate signed instrument identifies what is being changed and how the replacement terms connect to that original agreement.

DLD's current Request to amend the initial procedures data page names the **SPA** and **the amendment annex signed by both parties and the reason for the amendment** among the required documents. The same page states as a service term that the amendment annex must be signed by both parties ([DLD](https://dubailand.gov.ae/en/eservices/request-to-amend-the-initial-procedures-data/), accessed 29 September 2026).

That official page supports a narrow conclusion: the route expects the original agreement and a bilateral signed annex. It does not publish the wording of any buyer's annex. It also does not establish which instalments changed until the actual signed documents are read.

The practical comparison is therefore document against document. Copy the original event label, percentage or amount, due mechanism and date from the executed SPA. Then copy the replacement wording from the signed annex. Keep any proposal, email or unsigned schedule in a separate row. It may show what was discussed, but it is not the signed annex DLD names for this route.

The broader [project escrow and identity pillar](/projects/dubai-project-escrow-checks-official-route) handles the project-level checks around the account and registered project. This workflow stays with a narrower question: how one buyer's payment schedule moves from an original signed term to a signed change.

## What the DLD amendment route establishes

The DLD page establishes an official amendment route and its named output. It does not turn every document in the buyer's file into the same kind of evidence.

DLD describes the service as allowing a real estate developer to modify details of procedures registered in the real estate provisional register. The published sequence begins when the developer logs into the Oqood portal and selects the provisional sale registration service. The developer then selects the property, enters details, attaches documents, selects a payment method and sends the application online. DLD says the purchaser receives the output by email ([DLD](https://dubailand.gov.ae/en/eservices/request-to-amend-the-initial-procedures-data/), accessed 29 September 2026).

The page names that output as a **provisional registration e-certificate** and lists the service time as **6 business days**. Those are exact-page claims. The page does not enumerate the fields printed on the e-certificate, say that it reproduces the revised schedule or describe it as proof that a particular instalment cleared.

::::steps
:::step{title="Start with the executed SPA"}
Record the original schedule exactly as it appears, including each event, percentage or amount, due mechanism, date and cross-reference.
:::
:::step{title="Read the signed annex"}
Identify the agreement it amends, the parties shown, signature status, stated reason, effective wording and every replaced or added schedule line.
:::
:::step{title="Retain the DLD output"}
Keep the e-certificate delivered for the actual transaction and record only the fields it displays. The general service page is evidence of the route, not a substitute for that transaction-specific output.
:::
:::step{title="Reconcile later records"}
Compare the developer account record, payment request, receipt and bank record with the signed schedule. Preserve their own labels and dates instead of rewriting them as contract terms.
:::
::::

## The evidence hierarchy keeps five questions separate

Each record answers a different question. The hierarchy is about scope, not a claim that every transaction file contains the same forms or fields.

| Record | Exact question it can answer | What to copy | What it cannot establish alone |
| --- | --- | --- | --- |
| Original executed SPA schedule | What payment terms did the signed starting agreement state? | Event label, amount or percentage, trigger, date and clause reference | That a later proposal became effective |
| Amendment annex signed by both parties | What replacement wording did the named parties sign? | Agreement reference, parties, signature blocks, annex date, reason and every changed line | That DLD completed the amendment route or that money moved |
| Oqood amendment output | What does the transaction-specific DLD output actually display after the official route? | The exact fields, references and issue date visible on the e-certificate | Any field the certificate does not display, including a schedule if none is shown |
| Developer account record | What obligation, charge, credit or balance does that issued record display? | Record date, event label, debit, credit, allocation, balance and reference | The signatures on an unseen annex or the contents of a DLD output |
| Receipt or bank record | What payment event and status does that particular record display? | Payer, payee, amount, date, reference, account and displayed status | Why the sum was contractually due or whether it was registered |

::figure{src="images/blog/dubai-off-plan-payment-plan-amendment-evidence/inline-1.png" alt="Five separate records in an off-plan payment-plan amendment evidence chain" caption="The original schedule, signed change, official output, account record and payment proof answer different questions."}

As a general record-reading principle, not a DLD rule, an account statement or receipt is read only for the fields its issuer returns. A line labelled paid, allocated, pending or reversed is not silently converted into another status. A bank record is treated the same way. Its exact displayed status matters.

The related [payment-plan clause worksheet](/projects/dubai-off-plan-payment-plan-clause-verification) goes line by line through the signed clause set. This article begins where that worksheet leaves off: an asserted change must be connected to the original schedule and then reconciled through later outputs.

## A declared illustration checks the schedule, not the signatures

The following schedule is wholly invented. It is not a developer payment plan, an offer, a market norm or evidence of a transaction. It assumes an illustrative AED 1,200,000 price and a signed amendment annex dated 15 December 2026 only to show how the arithmetic and evidence columns stay separate.

| Stage | Original schedule | Revised illustrative schedule | Code-checked effect |
| --- | --- | --- | --- |
| Signing payment | 10% on 1 October 2026, AED 120,000 | Unchanged: 10% on 1 October 2026, AED 120,000 | AED 120,000 paid in the illustration; AED 1,080,000 remains |
| Next instalment | 20% on 1 January 2027, AED 240,000 | 10% on 1 March 2027, AED 120,000 | Due date moves 59 calendar days; scheduled amount is AED 120,000 lower |
| Middle instalment | 30% on 1 July 2027, AED 360,000 | Replaced by 15% on 1 August 2027, AED 180,000, then 25% on 1 December 2027, AED 300,000 | The revised pair is 40%, AED 480,000 |
| Handover balance | 40% on 1 July 2028, AED 480,000 | Unchanged: 40% on 1 July 2028, AED 480,000 | Same illustrative amount and date |
| **Total** | **100%, AED 1,200,000** | **100%, AED 1,200,000** | **Both schedules reconcile to the illustrative price** |

The invented annex date falls 17 calendar days before the original next due date. That timing shows why the dated file matters, but it proves nothing about execution. A real file would need the actual annex, parties and signatures.

::figure{src="images/blog/dubai-off-plan-payment-plan-amendment-evidence/inline-2.png" alt="Original and revised illustrative off-plan payment schedules" caption="Both illustrative schedules total 100%, while the middle timing and amounts change."}

Now add an invented payment record dated 2 March 2027 for AED 120,000. The arithmetic can reduce the illustrative balance from AED 1,080,000 to AED 960,000. It cannot prove who signed the annex, whether DLD processed the application, what the e-certificate displays or how the developer allocated the money. Those are record questions.

:::aside{title="Method"}
Every amount, percentage total, remaining balance and date movement in the illustration was recomputed from saved inputs. The DLD route facts were audited separately against a clean fetch of the official page on 29 September 2026.
:::

## A reconciled file preserves differences instead of smoothing them

A clean amendment file makes disagreement visible. It does not force the SPA, annex, Oqood output, account record and receipt into one synthetic status.

| Comparison | Match on | If the records differ |
| --- | --- | --- |
| SPA to signed annex | Agreement reference, parties, unit, changed lines and effective wording | Record the difference by field; do not infer replacement wording |
| Signed annex to Oqood output | Transaction references and the exact fields returned | State what the e-certificate displays and what it does not display |
| Signed annex to account record | Instalment label, due date, amount, prior credit and balance | Preserve the issuer's labels; seek a current written explanation where interpretation is required |
| Account record to receipt or bank record | Amount, date, payee, reference, account and displayed status | Keep transfer, receipt and allocation as separate events until the records connect them |

This is the strongest evidence format for an off-plan buyer who needs another reader to retrace the change without relying on memory. It does not decide whether the project, price or revised timing fits that buyer. Those questions need their own evidence and, where contract meaning or rights are disputed, appropriately licensed legal review.

## FAQ, checked 29 September 2026

::::faq
:::faq-item{q="Does Oqood prove the revised payment schedule?"}
DLD's amendment service page proves that the official route runs through Oqood and names a provisional registration e-certificate as the output. The page does not enumerate the certificate's fields or say it reproduces a buyer's revised instalments, so the actual e-certificate and signed annex must be read as separate records ([DLD](https://dubailand.gov.ae/en/eservices/request-to-amend-the-initial-procedures-data/), accessed 29 September 2026).
:::
:::faq-item{q="Does a receipt prove that the payment plan changed?"}
A receipt can evidence only the payment event and fields it displays. The signed change belongs in the amendment annex, while the contractual allocation of the payment has to be reconciled against the signed schedule.
:::
:::faq-item{q="How long does the DLD amendment service take?"}
DLD lists 6 business days for Request to amend the initial procedures data, accessed 29 September 2026. That is the published service time, not proof that a particular application was accepted or completed within that period ([DLD](https://dubailand.gov.ae/en/eservices/request-to-amend-the-initial-procedures-data/)).
:::
::::

:::callout{variant="note" title="Follow the next record"}
Subscribe to withlida's weekly market brief for sourced Dubai property process updates, with no listings or sales pressure.
:::

:::callout{variant="info" title="Before you act"}
This guide is general information, not financial, legal, or investment advice. Fees, thresholds, and rules change; verify the current requirements with the Dubai Land Department (DLD), RERA, or your licensed agent before you commit.
:::