Real estate: property buyers in the UAE and the UK
A suggested buyer onboarding setup for UAE and UK purchases, keeping the property, the buyer’s residence and their nationality apart.
This is a suggested setup. There is no ready-made UMNIII template for it: you build it in UMNIII Verify and can save it as your own template.
Who it is for: Estate agents, developers’ sales teams and conveyancers.
Scenario: A buyer has agreed to buy a property and you need their identity, details, declarations and documents.
The problem
Buyer files are pieced together from passports sent by messaging app, bank letters forwarded by email and declarations signed on paper. Overseas buyers make it slower still.
What can happen
- Sales are delayed while documents are chased across time zones.
- Buyer documents end up in personal inboxes and chat histories.
Legal and regulatory context
Estate agents may have customer due diligence obligations under anti-money-laundering law in the UK and the UAE. What applies to your business is for you and your compliance adviser to decide.
This is context, not legal advice about your obligations.
A better process
Send the buyer one link. They verify their identity, answer your questions and upload what you ask for, wherever they are, and the file is kept against one request.
How UMNIII Verify helps
UMNIII Verify lets you build one buyer workflow, save it, and send it to every buyer, with any check that genuinely applies added to the same request.
Which Verify features help?
- Identity verification
- Confirms the buyer is who they say they are.
Establishes: That a government-issued photo ID was checked for authenticity and matched to a live selfie of the person presenting it.
Does not establish: It does not establish an address, a right to work or rent, creditworthiness, a driving entitlement, or anything about a company. - Custom information forms
- The buyer’s details, source of funds, PEP and sanctions declaration and their declaration and consent.
Establishes: A structured record of what the recipient told you, filed against the request.
Does not establish: An answer is not independently verified because it was collected through Verify. It is what the recipient said. - Document requests and uploads
- Proof of address and the supporting documents your process asks for.
Establishes: That the recipient uploaded these files against this request, and when.
Does not establish: An upload does not establish that a document is genuine, valid, current or the recipient’s own. - Standard AML screening
- Screens the buyer against sanctions and PEP lists, where your policy requires it.
Establishes: Whether the person appears on sanctions lists or politically exposed person (PEP) databases at the time of screening.
Does not establish: It does not include adverse media, and a result is information for your own decision rather than a decision. - Residential records check
- Checks the buyer’s name and address against residential records for the country where they live, only where Verify offers that country.
Establishes: Whether the person’s name and address match official or licensed residential records for the country where they live, where Verify offers that country.
Does not establish: It is available only for the countries Verify offers, and it says nothing about a property, a nationality or an immigration status.
Optional, added separately
- Standard AML screening: When your policy requires sanctions and PEP screening of buyers.
- Residential records check: When the buyer lives in a country Verify offers for residential records. Chosen by where the buyer lives, never by where the property is or by nationality.
UAE property buyer Suggested setup
- Compose identity verification, the Individual Details, Source of Funds, PEP & Sanctions Declaration and Client Declaration & Consent forms, and a proof-of-address request.
- Add AML screening if your policy requires it.
UK property buyer Suggested setup
- Compose the same pattern for a UK purchase.
- UMNIII’s Property Buyer / Tenant KYC template is written around a UK letting, with rental offer, tenancy preferences and right-to-rent evidence, so for a purchase compose from scratch, or copy that template and adapt it.
A UK resident buying property in the UAE Suggested setup
- Use the UAE buyer setup: the property and the transaction are in the UAE.
- Because the buyer lives in the UK, you may add a residential records check for the United Kingdom where Verify offers it. That check concerns the buyer’s UK residential information. It does not verify the UAE property, or anything about the purchase.
Information that may be collected
- Name, contact details, date of birth and nationality
- Source of funds
- PEP and sanctions declaration
- The buyer’s declaration and consent
Documents that may be requested
- Proof of address
- Supporting documents your process asks for, with instructions
Countries and coverage
- Keep six things apart: the country of the property; the country where the transaction takes place; whether the person is buying or renting; the country where they live; their nationality; and the country a residential records source covers.
- A residential records check follows only the country where the person lives, and only where Verify offers that country. Where no source covers it, the check is not available, and Verify does not substitute another.
What Verify does not do here
- Verify does not verify a property, its title or its price, and does not carry out conveyancing.
How to create or adapt the workflow
- In UMNIII Verify, open the Dashboard. The request composer is headed “Send verification invite”. Leave “Start from a template” on “Compose from scratch”.
- Tick “Verify identity” where you need identity verified.
- Tick “Collect information (forms)” and choose the forms to send: the forms UMNIII provides, or your own under “Your forms”.
- Tick “Request documents”, choose each document, write its instructions, and mark it optional where the recipient may not have it.
- Add any optional check only where it genuinely fits your process. None is added by default.
- Enter the recipient in “Invitee Email”, choose how long the link lasts in “Link expires after” and, where offered, whether to “Send reminders”. Then press “Send verification invite”.
Create a reusable information form
- Owners, admins and members create forms under Custom Forms in UMNIII Verify: a name, then each question with its type, whether an answer is required, and any help text.
- Preview the form as the recipient will see it, save it, and it is offered under “Your forms” whenever a request is composed.
- One form can be attached to any number of requests and templates. Editing it changes future requests only; a request already sent keeps the questions it was sent with.
Save and reuse it as a template
- Once the composition is right, an owner, admin or member of the Workspace presses “Save as template”, gives it a name and, optionally, a description.
- From then on it appears in “Start from a template” beside the UMNIII templates. Choosing it fills in the request, every part stays editable for that one request, and choosing a template sends nothing on its own.
- To adapt a UMNIII template, choose it and press “Copy to this Workspace”. The copy is yours to change; the original is unchanged.
- A saved template is not edited in place. To change one, apply it, adjust the composition and save it again under a new name.
- Your Workspace’s own and copied templates are listed under Other / General in the credit calculator inside UMNIII Verify.
Templates, forms and guides
- UMNIII system template
- A ready-made workflow that UMNIII provides. It is labelled UMNIII in the product, and your Workspace cannot change it.
- Workspace template
- A workflow someone in your Workspace has saved for reuse. It belongs to your Workspace.
- Copied template
- A UMNIII template copied into your Workspace so it can be adapted. The copy is yours and the original is unchanged.
- Reusable information form
- A set of questions your Workspace writes once and attaches to any request or template.
- Workflow guide
- An explanation like these pages. A guide is not a template: unless it says a UMNIII template is available, it describes a setup you build yourself.
Next step
Build this setup in UMNIII Verify and save it as your own template. Current prices are shown in the product before you send anything.