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
Keep entity records, employment documents, visa workflows and payroll requirements together. Configure your HR setup around your free zone and workforce.
KNOWLEDGE LED. PEOPLE FIRST.THE EVERYDAY DIFFERENCE
Keep your entity, employee documents and payroll setup connected, with policies configured around your workforce.
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. Kled models the zone as a property of the entity, so the right process, document set and payroll treatment follow the employee automatically.
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
Explore the capabilities that support this part of your workday.
Each entity carries its authority, trade licence and establishment card, and every downstream process reads them from there.
Process templates per authority, because the stage list and document set differ between zones and between zone and mainland.
WPS obligations differ by zone. The payroll run resolves the regime from the entity rather than from a checkbox someone set once.
Offer letters, contracts and NOCs generated to the format the relevant authority expects, on your letterhead.
Trade licence, establishment card and lease renewals tracked alongside employee documents, with the same notice discipline.
One HR team, one login and one report across every entity, without pretending the zones behave the same underneath.

01 / IN PRACTICE
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.

02 / IN PRACTICE
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.

KNOWLEDGE LED. PEOPLE FIRST.
“What notice period applies to Reem?” has a different answer depending on the entity and the contract behind it. Ask HR resolves the question against the employee's actual entity and contract rather than against a general policy document, and shows what it used.
Explore Kled AIA LITTLE MORE CLARITY
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.
Yes. That's the common case, and it's the reason the regime is resolved from the entity rather than set globally.
LET’S FIND YOUR STARTING POINT
Join the Kled waitlist for launch updates and an invitation when early access opens for your team.
Join the waitlist