Annual Leave, Sick Leave and Holidays Under UAE Labour Law 33/2021: Rules Your HRMS Must Encode
A practical evergreen guide to uae labour law leave rules hrms, covering requirements, workflows, system data, evidence, controls, exceptions and implementation readiness.
Annual Leave, Sick Leave and Holidays Under UAE Labour Law 33/2021: Rules Your HRMS Must Encode
This evergreen guide explains uae labour law leave rules hrms, the operational data and evidence organisations should maintain, and the workflow controls needed for reliable execution. Requirements vary by entity, activity, jurisdiction and effective date. Confirm current rules with MOHRE, assign an accountable owner to every obligation, retain source-dated evidence and obtain specialist advice before using the guide for a legal, tax, regulatory, certification or safety decision.
Operational control map
Use this map when translating the guide into system configuration or procedure. Replace every placeholder and add jurisdiction-specific rows before approval.
| Control area | Minimum requirement | Owner | Evidence |
|---|---|---|---|
| Scope and applicability | Confirm entity, jurisdiction, activity and effective date. | [ASSIGN] | [EVIDENCE LINK] |
| Authoritative requirement | Link the current source from MOHRE. | [ASSIGN] | [EVIDENCE LINK] |
| Master data | Define fields, identifiers and ownership. | [ASSIGN] | [EVIDENCE LINK] |
| Workflow control | Record submission, approval, rejection and correction states. | [ASSIGN] | [EVIDENCE LINK] |
| Evidence | Retain source documents, acknowledgements and versions. | [ASSIGN] | [EVIDENCE LINK] |
| Exception handling | Assign escalation, target and acceptance authority. | [ASSIGN] | [EVIDENCE LINK] |
| Periodic review | Set an owner and regulatory review date. | [ASSIGN] | [EVIDENCE LINK] |
Treat this as a maintained record. Store source publication, internal approval and next review dates, and preserve prior versions whenever a rule or workflow changes.
A company with employees in Riyadh, Jeddah and Dammam does not merely have three office addresses. It may have several commercial registrations, establishment files, Qiwa locations, GOSI branch records, bank arrangements, payroll groups and finance dimensions. Some align one-to-one. Many do not.
The common mistake is to create one field called branch and use it for everything. A manager changes that field when an employee moves city. Payroll reallocates cost, but the contract, work permit, GOSI record or Qiwa establishment remains unchanged. Reports look tidy while official systems describe another employment relationship.
This article explains the data and controls that keep multi-branch payroll coherent. Confirm current transaction requirements with GOSI, Qiwa, HRSD and other competent channels before executing a transfer.
Six records that must not collapse into one
Maintain separate identifiers for the employing legal entity, government establishment or file, GOSI establishment or branch subscription, Qiwa establishment and location, physical work location, and finance cost centre.
The employing entity answers who owes the contractual and payroll obligation. The official establishment identifies the employer population in government services. The GOSI record determines contribution reporting. Qiwa holds establishment, location, employee, contract, occupation, permit and transfer processes. Physical location determines where work occurs. Cost centre tells finance where expense belongs.
These relationships can coincide without being identical. A single legal employer may operate several cities and cost centres. A person may work temporarily at a client site while remaining employed and reported under the same establishment. A permanent move between two establishments owned by the same group may require a formal employee-transfer process.
Create a branch crosswalk with every identifier, Arabic and English name, address, economic activity, status, responsible owner, payroll group, bank or WPS mapping and effective dates. Never join systems by branch name alone.
Register branches before employees appear
GOSI’s public service description treats an establishment as the legal entity through which the employer conducts activity and provides for registration of a new establishment or branch. The HR project should not wait until the first employee starts.
Build a branch-opening checklist covering commercial and labour records, GOSI registration, Qiwa establishment and location setup, authorised users, payroll group, bank and WPS readiness, finance dimensions, medical insurance, address and document retention. The exact legal steps vary with structure and activity; assign each to the appropriate specialist.
Keep official identifiers and certificates in a controlled register. Store issue, expiry, status and authority. Alert before an official record becomes inactive, because downstream work-permit or transfer eligibility can be affected.
Test a synthetic or approved test employee through the mappings before volume hiring. Confirm that contract, payroll, GOSI, WPS and ledger outputs all resolve to the intended branch.
Assign an employee through effective-dated relationships
An employee needs several assignments: legal employment, government establishment, GOSI subscription, Qiwa location, work location, organisational unit, position, manager and cost centre. Give each a start and end date.
Do not overwrite the previous assignment. Payroll must know where the person belonged for each segment of a month. Reporting must reconstruct headcount at a historical date. A transfer should create a new row after an approved event.
Use controlled reasons: new hire, permanent establishment transfer, work-location move, temporary assignment, organisational restructure or cost reallocation. These reasons drive different workflows. A cost-centre change may need finance approval but no Qiwa action. An establishment transfer can require contract and government actions.
Prevent impossible combinations. The selected Qiwa location should belong to the mapped establishment. The payroll group should be valid for the legal employer. The GOSI branch should be open. Exceptions require documented approval rather than an unrestricted override.
Distinguish relocation from employee transfer
Moving desks from Riyadh to Jeddah is not automatically the same as transferring employment services between establishments. Before initiating a change, classify it.
A work-location change keeps the employing establishment but changes where the employee performs work. Check contract, policy, allowance, travel, housing and Qiwa location implications.
A temporary assignment preserves the home assignment while adding host location, dates, cost allocation and supervision. Avoid ending and recreating employment for a short project.
An inter-establishment transfer changes the relevant official establishment and follows the applicable Qiwa employee-transfer route. Qiwa’s guidance specifically supports transfers of non-Saudi employees between an employer’s own establishments and automatically checks eligibility.
A group-company transfer may change legal employer, contracts, service treatment and benefit obligations. “Same owner” does not mean the payroll event is merely internal.
Create a decision workflow that identifies type, target, effective date, employee consent or acceptance, official steps and payroll consequences.
The Qiwa transfer lifecycle
Qiwa guidance describes selecting the employee-transfer service, choosing the route for an employee from the employer’s own establishment, selecting the target establishment, reviewing available recruitment quota, selecting an eligible employee, reviewing data and contracts, and submitting the request. If a contract is absent, one must be created to continue. Contract requests have a validity window, and the employee’s acceptance is part of the process.
Represent the lifecycle as requested, eligibility checking, contract preparing, submitted, employee action pending, accepted, downstream Ministry of Interior action pending where applicable, completed, rejected, cancelled or expired. Use current platform statuses rather than inventing approximations.
Do not change payroll employer when HR starts the request. Use a future effective event that activates only after the required authoritative completion. If a request expires or is rejected, cancel the pending event without corrupting current payroll.
Store source and target establishment, employee identifier, contract version, request number, status timestamps, rejection reason and completion evidence. Notify payroll and access teams from the completed event, not email.
Iqama and work-permit dependencies
An Iqama is not a branch field in the HR profile. It is part of an immigration and work-authorisation lifecycle connected to the recognised employer and occupation.
Track Iqama number, issue and expiry, work permit, occupation, medical insurance and transfer status under restricted access. Set renewal ownership and alerts. A transfer may require coordinated actions and deadlines across Qiwa and Ministry of Interior platforms.
Do not treat an employee as transferred because the physical move occurred or a manager approved it. Equally, do not keep paying from the old establishment after authoritative completion because the payroll cut-off passed without an adjustment plan.
For each transfer, create a dependency checklist with contract, Qiwa, work permit, Iqama or Ministry of Interior completion, GOSI record, medical insurance, payroll, WPS, bank, access and finance. Close only when reconciled.
Payroll cut-off and split periods
Set rules for transfers completed before and after payroll cut-off. The legal and official effective date governs; operational cut-off determines whether the result appears in regular or off-cycle processing.
If the transfer changes legal employer during a pay period, determine whether separate payroll results, payments or reporting are required. Do not split casually because finance wants two cost centres. Conversely, a cost allocation across branches does not necessarily justify two legal payslips.
Use effective-dated pay components and assignment segments. Allocate basic pay, allowances, overtime, leave, deductions and employer cost using approved rules. Preserve rounding and reconciliation.
Avoid retroactively overwriting the entire month with the target branch. Historical reporting, GOSI and WPS outputs must reflect the authorised treatment for each period.
GOSI registration and wage reconciliation
GOSI establishment and contributor records should reconcile with HR and payroll. For every employee, verify national or resident identifier, employment status, establishment or branch mapping, contribution coverage, wage subject to contribution, joining and leaving dates and monthly contribution.
GOSI’s service materials include a wage-subject-to-contribution certificate and establishment or branch registration. Use the current GOSI rules and employee category when configuring contribution calculations; do not infer contribution basis from payroll gross.
Create a monthly person-level reconciliation: active in HR but missing from GOSI, active in GOSI but terminated in HR, wage difference, branch mismatch, joining or leaving date difference, duplicate record and rejected transaction. Assign and close each exception.
Keep submission, acknowledgement, correction and payment evidence. A portal total that equals payroll is helpful but record-level agreement is necessary.
Saudi and non-Saudi populations
Payroll logic differs by nationality and coverage. Saudi employees typically engage contribution requirements differently from non-Saudi employees, and GCC nationals can invoke extension-of-protection arrangements. Do not configure one GOSI percentage for the branch.
Store verified nationality, insurance category, scheme, contribution basis, rates, effective date and authoritative registration. Protect identity data and prevent casual editing.
Nitaqat and occupation-specific localisation also operate on establishment data. A transfer can improve one establishment’s ratio while weakening another. Run source-and-target scenarios before approval, using current Qiwa or HRSD results as authoritative.
Do not delay or fabricate employment changes to manipulate localisation. The recorded establishment must reflect genuine employment and official processing.
Location-linked pay without legal confusion
Multi-city employers may use housing, transport, remote-site, hardship, shift or project allowances. Tie each to an eligibility rule, location or assignment, start and end, approval and payroll component.
A location allowance should not alter legal employer. A temporary project premium should end automatically with the assignment unless extended. Housing and relocation support should distinguish reimbursement, benefit and wage treatment.
When a person moves, show the manager and employee which components start, stop or change before approval. Preserve contractual terms that cannot be reduced through an administrative move.
Review tax, social-insurance and end-of-service implications with specialists where the component treatment is uncertain.
Time, attendance and calendars
Cities and branches may have different shifts, weekend operations, client calendars and access systems. Assign the correct work pattern effective-dated. Do not derive it solely from location if employees at one site follow several schedules.
Integrate attendance using stable employee and location identifiers. Distinguish actual work location from payroll branch. A consultant visiting a site should not appear as a transferred employee.
Overtime approval should route to the accountable manager and cost owner while payroll applies the correct employment rules. Reconcile approved time with the assignment valid on the work date.
If a transfer changes manager during an open timesheet, define who approves which period. Avoid losing time because the old manager loses access immediately.
WPS, payment and bank reconciliation
Generate wage-protection output from the legal payroll result and current official specification. Map establishment, bank account and employee identifiers through the crosswalk. Validate totals before submission.
Reconcile approved payroll to WPS file, bank instruction and payment outcome by employee and branch. Track rejected or short-paid employees to correction. A successfully generated file is not completed payroll.
If branches use separate bank accounts, use maker-checker permissions scoped appropriately. Central payroll can process several establishments while preserving separate legal control totals and approvals.
Store file version, pay period, establishment, record count, total, submitter, acknowledgement and correction history under restricted access.
Finance reporting without distorting HR
Finance often wants payroll by city, project, department and profit centre. Use allocation dimensions rather than changing the employing branch to obtain a report.
Support percentage or dated cost splits with approval and total validation. Reconcile payroll expense, employer contributions, benefits and accruals to the ledger. Keep legal entity balanced before management allocation.
Report headcount using explicit dimensions: legal employer headcount, official establishment population, work-location population and cost-centre FTE. Label each. “Jeddah headcount” is ambiguous without a definition.
Preserve the organisation and assignment snapshot for month-end so later transfers do not rewrite reports.
Access and segregation of duties
Branch HR may maintain local time and documents but should not necessarily change legal employer, contribution wage or transfer completion. Configure role-based access by entity and function.
Separate request, approval, official transaction, payroll calculation and payment release. Prevent one user from creating a transfer, changing salary and releasing the resulting pay without review.
Central administrators need cross-branch access, but sensitive identity and bank information should remain purpose-limited. Log exports and bulk changes.
When an employee transfers, update access from the effective event. Preserve time-limited access for legitimate handover without leaving broad source-branch visibility indefinitely.
Monthly branch control pack
Produce one pack per establishment: opening and closing headcount, joiners, leavers, transfers in and out, Saudi and non-Saudi population, GOSI wage and contribution reconciliation, permit expiries, payroll and WPS control totals, payment exceptions and ledger reconciliation.
Add cross-system exceptions and ageing. Include pending transfers near expiry, completed transfers not reflected in payroll, employees at unmapped locations and assignments with closed branches.
Require HR operations, payroll and finance sign-off. The sign-off confirms exceptions are resolved or explicitly carried, not that a report was downloaded.
At group level, reconcile transfers out to transfers in. One establishment’s leaver must match the target event when the transfer is internal.
Common failure patterns
One branch code for every purpose. Government, payroll and finance identities diverge.
Changing payroll on request date. The official transfer may fail or expire.
Cost allocation treated as employment transfer. Contracts and official records are changed unnecessarily.
Physical move treated as enough. Work occurs in the target city while employer records remain unresolved.
GOSI totals without person-level reconciliation. Equal totals can hide two opposite errors.
Closing offboarding before official completion. Permits, GOSI or access remain open.
Reporting current branch historically. Transfers rewrite prior-month headcount.
A 60-day remediation plan
In days 1–15, inventory entities, establishments, GOSI branches, Qiwa locations, payroll groups, bank accounts and cost centres. Build the crosswalk and identify duplicates or unmapped records.
In days 16–30, reconstruct active employee assignments and reconcile HR, Qiwa and GOSI. Classify unresolved city moves and transfers. Correct through authorised processes, not database edits.
In days 31–45, implement transfer states, effective-dated payroll handling, cut-off rules, access changes and control reports. Test completed, rejected, cancelled, expired and mid-period cases.
In days 46–60, reconcile payroll, WPS, bank and ledger for every establishment; train users; establish monthly sign-off; and simulate opening a branch and closing one.
Where a system helps
AuraOS for HCM maintains separate legal, government, GOSI, Qiwa, location and finance dimensions, activates transfers from authoritative events, segments payroll by effective date and produces branch-level reconciliation. Multi-city growth then adds controlled mappings instead of more spreadsheets.
FAQ
Is moving an employee to another Saudi city always an Iqama transfer?
No. It may be a work-location change, temporary assignment or official inter-establishment transfer. Classify the event and check current contract, Qiwa and Ministry requirements.
When should payroll change the employee’s establishment?
On the authorised effective event after required official completion, not merely when a manager requests the move or the employee relocates physically.
Can one company have several GOSI branch records?
GOSI provides for establishment or branch registration. Maintain the authoritative registration structure and map it explicitly to payroll and Qiwa records.
Should cost centre equal payroll branch?
No. Cost allocation is a finance dimension. It may align, but changing it should not silently change legal employer or official establishment.
What should be reconciled monthly?
HR assignments, Qiwa employees and contracts, GOSI population and wages, payroll, WPS, bank outcomes and finance postings at employee and establishment level.
How are internal Qiwa transfers controlled?
Track source, target, eligibility, contract, employee acceptance, official completion and downstream actions as a lifecycle, using the current Qiwa service statuses.