Zone held on the entity
Each entity carries its authority, trade licence and establishment card, and every downstream process reads them from there.
By jurisdiction
Free zone employers
JAFZA, DMCC, DAFZA, SHAMS, RAKEZ and the rest: employment sits with the zone authority rather than MOHRE, and the paperwork, the visa route and the payroll obligations all follow from that.
A free-zone entity is not a mainland company with a different address. The employment relationship is registered with the zone authority, the visa route runs through the zone's own channel, and the contract, establishment card and renewal cycle all belong to that authority rather than to MOHRE.
Groups holding entities in more than one zone — which is most groups of any size — end up running several of these processes side by side. KLEDHR models the zone as a property of the entity, so the right process, document set and payroll treatment follow the employee automatically.
Zone-specific visa flows
Process templates per authority, because the stage list and document set differ between zones and between zone and mainland.
Payroll on the right regime
WPS obligations differ by zone. The payroll run resolves the regime from the entity rather than from a checkbox someone set once.
Documents per authority
Offer letters, contracts and NOCs generated to the format the relevant authority expects, on your letterhead.
Licence & card expiry
Trade licence, establishment card and lease renewals tracked alongside employee documents, with the same notice discipline.
Several zones at once
One HR team, one login and one report across every entity — without pretending the zones behave the same underneath.
What actually differs
The differences are procedural rather than conceptual, which is precisely why generic HR software gets them wrong: nothing about the data model is unusual, so the software assumes one process and hard-codes it.
- Registration and employment records sit with the zone authority, not MOHRE.
- Visa and permit stages differ by zone, including which documents are needed when.
- Some zones operate their own portals and file formats for employer submissions.
- Gratuity treatment follows the applicable regime for the entity — worth confirming per zone rather than assuming.
Multi-zone groups
The failure mode for a group is a second system: one zone gets the HR product and everyone else stays on spreadsheets, because the product could only model one authority. Modelling the authority as entity data avoids that split.
- Group-level reporting across zones and mainland entities together.
- Inter-entity transfers that preserve service history for accrual.
- Per-entity approval chains and leave policies under one org record.
Questions we get asked
- Do you support the free zone we're in?
- The zone is configuration, not code — authority, document set and process template are set up per entity, so a zone we haven't seen before is a setup task rather than a roadmap item.
- Can we run mainland and free-zone entities together?
- Yes. That's the common case, and it's the reason the regime is resolved from the entity rather than set globally.
This page is general information about UAE employment practice, not legal advice. Confirm the treatment of any specific case with your own counsel.
See KLEDHR on your own payroll month
A 30-minute walkthrough on a tenant we spin up for the call — bring your trickiest gratuity or WPS case.
Book a demo