Why Ejari registrations get rejected — and how to fix each
Welcome back. I'm Stephen, and this is episode five of the ejaries.ae podcast. Today we're looking at rejections. Most ejaries registrations go through cleanly. Some don't. When a registration is rejected, it's almost always for one of a small number of recurring reasons. This episode is the catalogue of those reasons, the cause of each, and the practical fix.
Rejection one: landlord name mismatch
The most common rejection is the one we touched on in episode three. The name on the tenancy contract as landlord doesn't match the name on the title deed as owner. The system can't process a registration where the person renting the property to you isn't the registered owner of the property. The mismatch is flagged and the registration stops.
The cause is usually one of three. The contract was signed with a property manager, not the owner. The contract was signed with a previous owner whose sale hasn't completed. The contract was signed with an authorised representative under a Power of Attorney.
The fix depends on which of these is happening. If it's a property manager, the manager needs to produce a management agreement or a Power of Attorney from the owner. The registration then proceeds with the manager named as authorised representative and the owner named as the underlying landlord. If it's a previous owner, the new owner needs to either complete the title transfer first, in which case the new owner becomes the registered landlord, or produce the sale documentation that's pending. The registration may need to wait for the transfer. If it's a Power of Attorney, the POA itself needs to be valid, registered through the proper channel, and contain wording that authorises lease execution for the named property. We cover the wording requirements specifically on poaforproperty.ae.
Rejection two: Emirates ID issues
The second most common rejection relates to the tenant's identification. The system requires a valid Emirates ID. If the ID is expired and renewal is in progress, the registration may be paused. If the tenant has recently changed sponsors and the system shows a temporary gap, the registration may flag.
The fix is to ensure the Emirates ID is current and the residency record is clean before initiating the registration. Where renewal is in progress, the practical advice is to wait for the new card. Where the system flags a recent sponsorship change, the residency record usually self-corrects within days. Re-attempting the registration after a short pause is often enough.
Rejection three: missing or expired documents
A registration where a required document is missing, or where a submitted document is itself expired, will be rejected. This shows up in several forms. The landlord's commercial licence has expired. The title deed reference isn't current. The DEWA bill required by some registrations isn't recent enough. The Affection Plan is from a developer whose status has changed.
Each of these has a specific fix and the fix is always to update the document and re-submit. The preventive step is checking the validity dates on every document before starting the registration. The system catches missing or expired documents in seconds. The cost is the time it takes to obtain the replacement.
Rejection four: contract terms outside parameters
Some contracts are written with terms the ejaries system doesn't accept. This happens with unusually short tenancy periods — a one-month or three-month contract may not register as standard ejaries and may need a different category. It happens with unusual payment structures that the system doesn't recognise. It happens with contract clauses that contradict Dubai's tenancy law.
The fix in each case is to revise the contract to bring it within the parameters the system accepts, or to register through a different category — for example, holiday home rentals have their own system separate from standard ejaries. For unusual structures, a typing centre is more useful than the app because the typist can identify the issue and advise on the correct category.
Rejection five: rent calculator overshoot at renewal
We covered this in episode four. A renewal that proposes a rent increase above the lawful cap is flagged at registration. The system doesn't quietly accept the increase. It refuses to register the renewal at the proposed rent.
The fix is one of two things. Either the landlord reduces the proposed increase to within the cap, in which case the renewal proceeds. Or the parties cannot agree and the matter goes to the Rental Dispute Settlement Centre to resolve. For a tenant facing an unlawful increase, the rejection is your protection. The system is enforcing the rule on your behalf.
Most rejections are document problems. Most document problems are visible before you start the registration. The fix is preparation, not escalation.
Rejection six: title deed not registered
A small but recurring rejection happens with properties where the title deed itself isn't fully registered, or where the property is in a sub-registered category. This affects some off-plan properties before handover, certain free zone properties not covered by the standard DLD register, and properties undergoing strata or sub-division changes.
The fix is property-specific. Off-plan units before handover register through the Affection Plan rather than a full title deed. Free zone properties register through the free zone authority. Properties undergoing sub-division register once the sub-division is complete on the DLD register. For most tenants, this isn't a problem because most rented properties are fully registered standard residential units. For tenants in newer buildings or in free zones, it's worth checking the property's registration status before signing.
Rejection seven: identity verification mismatch
A subtler rejection happens when the tenant's identity information on the contract doesn't exactly match the identity information on their Emirates ID record. Sometimes a contract is signed with a slightly different spelling of the tenant's name, or with an old passport reference, or with a name in the wrong order. The system compares the contract against the ID record and flags the discrepancy.
The fix is to correct the contract to match the ID exactly. Names should match in spelling and order. Passport references, where used, should be current. Where the contract has been signed but contains an error, a correction document or a contract amendment can resolve it.
Less common rejections
A handful of less frequent rejections come up occasionally.
- Tenancies with multiple tenants where one tenant isn't a UAE resident may need additional documentation.
- Tenancies in properties subject to ongoing litigation may be flagged pending resolution.
- Tenancies where the landlord is undergoing bankruptcy or insolvency proceedings may not register through the standard channel.
- Properties with disputed boundaries or ownership claims may flag the registration.
Each of these is rare in standard residential tenancies. They show up more often in commercial contexts, or with high-value properties, or where the property has a complicated ownership history.
The pattern across all rejections
If you look at the list as a whole, there's a pattern. Almost every rejection is a documentation problem that was visible before the registration was attempted. The landlord name on the contract didn't match the title deed. That was checkable before signing. The Emirates ID was expired. That was checkable before starting. The commercial licence wasn't current. That was checkable before submitting. The rent increase exceeded the cap. That was calculable before proposing. The contract had unusual terms. That was reviewable before signing.
The implication is that the way to avoid rejection is preparation, not problem-solving after the fact. The thirty minutes you spend checking documents before starting saves the days or weeks you'd otherwise spend resolving the rejection.
What to take from this episode
The most common rejections are landlord name mismatch, Emirates ID issues, missing or expired documents, contract terms outside parameters, and rent calculator overshoot at renewal. Each has a specific fix. Each is almost always preventable by checking the documents and the contract before starting the registration. The system is designed to flag problems early rather than let unsound registrations into the register. Rejection is a feature, not a failure of the system. It's catching something that needs to be caught.
Coming next
In the next episode we look at the relationship between ejaries and DEWA. How the two systems connect, why the connection matters, and what to do when the connection goes wrong.
Thanks for listening. The full transcript is at transcript.ae. For ejaries registration support, ejaries.ae is the operational service.
Key takeaways
- Almost every rejection is a documentation problem visible before you start.
- The big ones: landlord name vs title-deed mismatch, Emirates ID issues, missing or expired documents, out-of-parameter contract terms, rent-cap overshoot at renewal.
- A rent-cap overshoot rejection is the system protecting the tenant — it enforces the lawful cap.
- Identity details on the contract must match the Emirates ID exactly — spelling and order.
- The way to avoid rejection is preparation, not escalation — 30 minutes of checks saves days or weeks.
Frequently asked questions
Why was my Ejari registration rejected?
Almost always a documentation issue — most commonly the landlord's name not matching the title deed, an expired Emirates ID, an expired document, out-of-bounds contract terms, or a rent increase over the lawful cap.
Is a rejection a bad sign?
No — it's the system catching a problem early; a rent-cap overshoot rejection, for instance, enforces the lawful cap on the tenant's behalf.
How do I avoid a rejection?
Prepare before you start — check the landlord matches the title deed, your Emirates ID is current, every document is valid, and the contract terms and any rent increase are within bounds.