Verify the Source Before Reviewing the File

Do not start with the appearance of a document; start with who issued it and how its validity can be checked. Obtain title, project, registration, licence and identity information through the relevant official or issuing channel. Use the MKDXB property directory to keep the unit reference consistent, then match the property number, owner or developer name, purchaser details and dates across every record. A clear scan is not proof if the source, current status or connection to the exact unit is uncertain.

• Verify issuer and current status, not document appearance
• Match property and party details across all records
• Keep one consistent unit reference throughout the file

Compare the Contract with Official and Issued Records

Read the reservation form, sale agreement, addenda and payment schedule as one connected file. Confirm that the contracting party matches the verified seller or developer, and that the unit, price, due dates, completion or transfer conditions, refund provisions and notice details are consistent. The MKDXB developer directory can help identify the correct development entity, but the executed contract and official records govern the transaction. Investigate any late change to a beneficiary, account, representative or signing link before acting.

• Read the contract, addenda and payment schedule together
• Match the contracting party to verified records
• Stop and verify any late change in instructions

Confirm Payment Instructions Through a Second Channel

Verify the beneficiary name, account details, currency, reference and purpose through a channel you obtained independently, not only through the message carrying the instruction. For off-plan property, confirm the designated project payment route and registration position through official records. For ready property, confirm the current trustee or registration process before arranging cheques or transfers. If an instruction conflicts with the contract, contact MKDXB and the relevant institution before sending funds.

• Use an independently sourced channel to confirm payment details
• Match every payment to the contract and exact unit
• Pause when instructions conflict or change unexpectedly

Build an Audit Trail That Another Person Can Follow

Save original files, signed versions, email headers, portal receipts, bank confirmations and the date and person who verified each critical instruction. Name files consistently and keep a simple transaction index showing what was received, what remains outstanding and which version is current. Before completion, reconcile the contract value, paid amounts, remaining balance, fees and issued receipts without relying on screenshots alone. A remote file is ready only when the evidence can be traced from source to payment and registration output.

• Save original files and verification evidence
• Maintain a version-controlled transaction index
• Reconcile contract, payments, fees and receipts before completion