Jurisdiction on the entity
ADGM entities are configured as their own regime rather than as an exception layered on the mainland rules.
By jurisdiction
HR software for ADGM employers
Manage employee records, contracts, leave and payroll with policies scoped to your ADGM entity. Keep approvals and employment history easy to review.
KNOWLEDGE LED. PEOPLE FIRST.THE EVERYDAY DIFFERENCE
One place for the work that matters.
Give your ADGM entity a clear home for employment records, policies and approvals, alongside the rest of your group.
A closer look at your setup
ADGM is a common-law jurisdiction with its own employment regulations, its own registration and its own treatment of end-of-service benefits. An employer with entities inside and outside it is running two distinct sets of rules over one workforce.
Kled keeps them distinct. The entity carries the jurisdiction; leave policy, end-of-service treatment and reporting all resolve from it. Nobody has to remember which rule applies to which person at the moment it matters.
Your size. Your setup. Start with included Core HR, switch optional modules on or off, and choose whether to use AI. For larger organisations, we build custom features around your requirements. Find your fit.
WHAT YOU CAN DO
The details, brought together.
Explore the capabilities that support this part of your workday.
Separate end-of-service treatment
Accrual and settlement follow the arrangement that applies to the entity, calculated and shown separately from mainland gratuity.
Its own leave policy set
Entitlements, notice and working-week rules configured per entity, so ADGM staff aren't administered under mainland defaults.
Consolidated reporting
Group reporting across both regimes, with the jurisdiction available as a dimension rather than buried in a note.
Data handling for regulated groups
Per-tenant isolation, UAE residency and audit logging: the questions ADGM-based financial firms ask first in procurement.
Evidence for audit
Every calculation shows its basis and every change is logged, which is what an auditor or a regulator actually asks to see.
01 / IN PRACTICE
Two regimes, one workforce
The risk in a mixed group is not that the ADGM rules are hard; it's that someone applies the wrong ones because the system only knew about one. Keeping the regimes separate at the data level is what prevents that.
- End-of-service accrual computed on the regime that applies to the employing entity.
- Transfers between regimes handled explicitly, with the effect on accrual made visible.
- Policy documents and contract templates held per jurisdiction.
- Reports that can be run per regime or consolidated.
KNOWLEDGE LED. PEOPLE FIRST.
The Explainer shows which regime it used
For an ADGM employee, the End-of-Service Explainer states the arrangement it calculated under and the basis it used, rather than producing a number that looks like mainland gratuity and inviting a dispute about why it differs.
Explore Kled AIA LITTLE MORE CLARITY
Your questions, answered.
Do you handle DIFC as well?
Yes, DIFC entities run on the DEWS arrangement, which is again configured on the entity. The two financial free zones don't share a regime with each other or with the mainland.
Can group HR see everything in one place?
Yes, scoped by role. The jurisdictional split is in how rules are applied, not in how the workforce is viewed.
Keep exploring.
LET’S FIND YOUR STARTING POINT
Your next workday, made simpler.
Join the Kled waitlist for launch updates and an invitation when early access opens for your team.
Join the waitlistOr speak to our team