If your UAE business runs through several mainland companies, branches and licences, the hard part is usually not the headline target. It is figuring out which employee base actually counts against which quota, which company will be assessed separately, and where finance should expect exposure if one entity misses the 31 December 2026 checkpoint. The current urgency is clear. MOHRE is calling on private sector companies with 50 employees or more to achieve the 1% semi-annual increase in skilled Emiratisation before 31 December 2026, and the policy path still points to a 10% target by end-2026 for the in-scope population of private establishments. MOHRE home MOHRE Emiratisation targets guidance Employing Emiratis in the private sector, UAE Government For owners and CFOs, the practical question is narrower: if we have several mainland entities under common ownership, do they count together or separately? The short answer, based on the operative wording in the published rules, is that the quota is measured at the establishment level, not across a whole corporate group by default. The key calculation in Ministerial Resolution No. 279 of 2022 is based on UAE nationals working in "the establishment" relative to total skilled workers in "the establishment". That matters because many groups manage hiring centrally but are assessed in MOHRE records establishment by establishment.
01Start with the legal unit MOHRE actually measures
The safest starting point is to ignore your management reporting structure and look at the unit named in the employment and compliance rules. The published Emiratisation quota framework for employers with 50 or more workers applies to private sector establishments with 50 or more employees, and the calculation mechanism in Ministerial Resolution No. 279 of 2022 says the prescribed percentage is calculated using the number of UAE nationals working in the establishment against the total number of skilled workers in the establishment. Employing Emiratis in the private sector, UAE Government Ministerial Resolution No. 279 of 2022
That means a UAE group should assume separate quota measurement unless there is a specific official mechanism that combines those establishments in MOHRE systems. From the public sources reviewed here, there is no published rule saying separate mainland legal entities under common ownership can simply pool headcount or Emirati hires for quota purposes. The opposite is what the wording implies: each establishment is tested on its own registered workforce and its own registered skilled employees. Ministerial Resolution No. 279 of 2022
This is why group finance often gets surprised late in the year. A group can look healthy in aggregate, yet still have one trading company above target and another exposed because the Emirati employees, work permits and skilled headcount sit on different establishment files in MOHRE. If you want one operating view across entities, you need a data layer above MOHRE, not an assumption that MOHRE will net the positions for you. That is the problem to solve in your internal compliance reporting, similar to the cross-entity visibility issue covered in 31 Dec 2026 Emiratisation target across multiple UAE entities: how do you see quota risk in one view?.
- Treat each mainland establishment as separately exposed unless an official MOHRE record or ruling says otherwise.
- Test quota exposure against skilled workers, not total payroll headcount.
- Check where each Emirati employee's work permit is actually registered, not who benefits from the work operationally.
02What counts together, and what usually does not
In practice, the cleaner answer is this: workers count within the establishment to which their work permit and employment registration belong. If you operate separate mainland legal entities, separate establishment cards or separate MOHRE establishment records, you should expect the quota test to run separately for each one. That follows directly from the calculation wording in Ministerial Resolution No. 279 of 2022.
What may count within one measurement unit is activity housed under the same establishment record. If a business has one legal employer and one establishment in MOHRE for the relevant workforce, the skilled workers and Emirati employees inside that establishment are part of the same denominator and numerator. Similarly, if your business has multiple internal cost centres or departments but one employer record, those cost centres do not create separate quota entities by themselves.
What usually does not count together is the classic UAE group structure: HoldCo, Trading LLC, Services LLC, Contracting LLC, and a separate staff-supply company, all with common owners and shared finance. Common ownership does not, by itself, create a pooled Emiratisation quota in the public rules reviewed. Separate mainland entities should therefore be tracked separately, even if one CFO signs off the whole group.
Branches need more care. A branch may or may not be separate for Emiratisation tracking depending on how it appears in MOHRE systems and where the relevant work permits sit. Do not guess from the trade licence name alone. Pull the actual establishment records, establishment cards and employee permit locations. If you are already mapping other regulatory obligations across fragmented entities, the discipline is similar to building one control view for WPS payroll across multiple UAE entities: why one late file creates a group-wide mess.
- Counts together: employees and Emirati hires inside the same establishment record.
- Does not automatically count together: separate mainland legal entities under the same shareholder group.
- Needs verification: branches, related licences and operating units that finance treats as one business but MOHRE may store separately.
| Situation | Default tracking view | Why |
|---|---|---|
| One mainland company, one MOHRE establishment, many departments | Count together | The published quota formula is by establishment, and there is only one establishment record. |
| Two or more mainland LLCs under the same owners | Track separately | Common ownership is not the same as one establishment for quota calculation. |
| One company with branches | Verify in MOHRE records | The branch naming may not tell you where worker permits and skilled headcount are actually registered. |
| Shared services company employs staff used by operating entities | Track by employing establishment | Quota follows the establishment where the worker is registered, not the management charge code. |
| Free zone entity plus mainland entity | Track separately unless the mainland establishment itself is in scope | The public Emiratisation quota framework cited here is for private sector establishments registered with MOHRE. |
03Why owners get this wrong late in the year
There are three recurring causes of error. First, management reports usually roll up by beneficial ownership, while compliance is measured by establishment. Second, headcount reports often use total employees, while the quota for 50-plus companies is tied to skilled jobs. Third, groups assume an Emirati hire can solve a weak position anywhere in the group, even if that employee is registered under a different employing entity. Ministerial Resolution No. 279 of 2022
The minimum unit also matters. The same resolution states that at least one citizen shall be employed against every 50 skilled workers or part thereof for each year of implementation. So an entity does not need a huge workforce to create exposure. A company sitting just above a 50-skilled-worker threshold can still need an additional Emirati to remain compliant with the annual step-up path. Ministerial Resolution No. 279 of 2022
The year-end deadline is especially sensitive because non-compliant companies are not only exposed to the regular contribution mechanism, they are also exposed if MOHRE sees circumvention. MOHRE has published that companies found to have circumvented Emiratisation targets can face fines of AED 100,000 for the first proven violation, AED 300,000 for the second, and AED 500,000 from the third violation onwards. MOHRE also states that non-compliant companies face an AED 42,000 financial contribution for each Emirati not appointed according to the semi-annual targets for the 2026 cycle. Up to AED500,000 fines on companies that circumvent Emiratisation targets Employing Emiratis in the private sector, UAE Government
That is why aggressive November and December fixes can backfire if they rely on headcount reclassification, artificial transfers or paper-only alignment. MOHRE has explicitly flagged reducing employee numbers or modifying their classification as methods of circumvention. Up to AED500,000 fines on companies that circumvent Emiratisation targets
- Do not rely on group totals.
- Do not treat all employees as part of the denominator, only the skilled workforce relevant to the rule.
- Do not assume an intercompany transfer solves exposure unless the registration is completed in the right establishment and the move is genuine.
04A workable tracking model for CFOs and compliance owners
The cleanest way to track exposure is to build a register at establishment level, then roll it up to group level for management visibility. For each mainland establishment, capture: MOHRE establishment identifier, legal entity name, licence linkage, total skilled workers, total Emirati workers in skilled jobs, current target percentage, gap to target, contribution exposure if the gap remains open, and the names and permit IDs of Emirati employees credited to that establishment.
You will also want to separate legal facts from management assumptions. Finance should not maintain a column called 'belongs to group company X in practice'. It should maintain columns such as 'employing establishment', 'work permit establishment', 'skilled classification in MOHRE or payroll master', and 'branch or licence reference'. This stops the year-end discussion becoming a debate about who the employee really works for day to day.
Once that data exists, build two views. View one is the statutory view, establishment by establishment. View two is the owner's view, grouped by shareholder group, BU or sector. The statutory view tells you where the actual obligation sits. The owner's view tells you where to deploy recruiting effort, retention effort and leadership attention. If you need help building the data pipeline or control logic around that view, it usually sits between data engineering services, intelligent automation services and governance and compliance support.
- Create one row per establishment, not one row per legal group.
- Store evidence links for each counted Emirati employee.
- Freeze the denominator definition for monthly reporting so the same entity is not measured three different ways by HR, payroll and finance.
05What to ask HR, PRO teams and your external advisers this month
Before December pressure builds, ask direct questions that force an establishment-level answer. Start with HR and the PRO team: for every Emirati employee we are counting, which establishment issued the work permit, and does that same establishment hold the skilled workforce denominator used for the target? If the answer is not immediately available, your exposure model is not audit-ready.
Ask payroll and finance whether any entities rely on shared-service employment models. If one company employs staff who are operationally deployed into another, your compliance exposure still sits with the employing establishment unless the registrations are changed properly. That can create underperformance in one entity and overperformance in another.
Ask external counsel or compliance advisers for written confirmation on any branch structures or unusual setups, especially where one licence holder operates across multiple locations or where trade licence names create a false sense of consolidation. The question is not 'are these businesses related?' It is 'which establishment record does MOHRE use to calculate the denominator and numerator for this obligation?'
If you are engaging a technology or compliance delivery partner, ask for a simple output, not a slide deck: an entity map, an establishment-level risk register, a documented denominator rule, and a monthly control pack for the CFO and CHRO. That kind of practical control work is where a team such as SyncTrix can help, especially when the problem is fragmented systems and late visibility rather than uncertainty about the headline law.
- Which exact establishment record is in scope for each entity?
- How many skilled workers are registered in that establishment today?
- Which Emirati employees are being counted, with evidence?
- What is the current shortfall by establishment, not by group?
- What contribution exposure follows if no further action is taken before 31 December 2026?
06What to do between now and 31 December 2026
There is still time to make the position visible, but not much time to clean up bad assumptions. A sensible plan is: first, reconcile the establishment list. Second, reconcile skilled headcount by establishment. Third, reconcile Emirati employees actually credited to each establishment. Fourth, calculate the gap entity by entity. Fifth, prioritise entities where a single hire or retention issue changes compliance status.
Use MOHRE's own current messaging as the deadline anchor. The Ministry is actively calling on private sector companies with 50 employees or more to achieve the 1% semi-annual increase in skilled jobs before 31 December 2026. MOHRE home MOHRE news, 22 June 2026
Finally, do not let the group view hide entity-specific risk. The question that matters to year-end compliance is not whether the wider group employs enough Emiratis overall. It is whether each in-scope establishment can stand on its own numbers if MOHRE tests it. If you cannot answer that in one sheet today, build that sheet first. Everything else comes after.
- Week 1: confirm establishment inventory and owners.
- Week 1: pull skilled worker denominator by establishment.
- Week 2: match Emirati employees to the establishment that actually employs them.
- Week 2: quantify remaining shortfall and likely contribution exposure.
- Week 3 onward: act only on genuine hiring, retention and proper registration changes.
Sources
Topics
SyncTrix Editorial
SyncTrix · SyncTrix
Writes about the engineering decisions behind production systems - architecture, delivery and the trade-offs that only show up at scale.
Building something like this?
SyncTrix engineers AI, SaaS, platform and cloud systems for enterprises and high-growth teams. Tell us what you're shipping and we'll scope it with you.