Skip to content
HRKnowledge led. People first.Join the waitlist
Moving to Kled

By jurisdiction

HR software for UAE free zone companies

Keep entity records, employment documents, visa workflows and payroll requirements together. Configure your HR setup around your free zone and workforce.

Colleagues planning together in a sunlit UAE officeKNOWLEDGE LED. PEOPLE FIRST.

THE EVERYDAY DIFFERENCE

One place for the work that matters.

Keep your entity, employee documents and payroll setup connected, with policies configured around your workforce.

A closer look at your setup

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

The details, brought together.

Explore the capabilities that support this part of your workday.

Zone held on the entity

Each entity carries its authority, trade licence and establishment card, and every downstream process reads them from there.

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.

Hands organising an employee document folder at a sunlit desk

01 / IN PRACTICE

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.
A finance professional reviewing paperwork and payroll figures

02 / IN PRACTICE

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.
A colleague consulting an assistant on a laptop

KNOWLEDGE LED. PEOPLE FIRST.

Ask HR knows which entity the question is about

“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 AI

A LITTLE MORE CLARITY

Your questions, answered.

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.

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 waitlist
Or speak to our team