Running HR and payroll across the UAE and Egypt

A company running HR in both the UAE and Egypt is, in practice, running two entirely different compliance systems side by side — different payment rails, different severance logic, different social insurance schemes, different currencies and payroll calendars — with no regulatory bridge connecting them. Most multi-country HR tooling treats this as "the same problem, twice"; it isn't. The UAE and Egypt don't share a legal family, a payment infrastructure, or even the basic assumption of what "final settlement" means. This guide lays out exactly where the two systems diverge, because the gap is where compliance mistakes happen.

WPS vs. Egypt's bank-transfer law — not the same mandate

The UAE's Wage Protection System (WPS) is a universal mandate for mainland private-sector companies: every eligible employee, every month, through the government-monitored electronic system, with penalties starting at AED 1,000 per affected worker for late or non-compliant payments (full breakdown in HR & Payroll Compliance in the UAE).

Egypt has no equivalent. Law No. 18 of 2019 requires bank-transfer payment only once a company crosses a size threshold — more than 25 employees, or a monthly payroll above EGP 100,000 — and even then, it's a bank-transfer requirement, not a government-monitored real-time system like WPS. Non-compliance carries a 2–10% fine on the value of cash payments made, proportional rather than fixed. A company running both markets needs two separate payment-compliance logics, not one rule applied twice: the UAE side is a hard universal mandate with a fixed per-worker penalty, and the Egypt side is a threshold-triggered requirement with a proportional one. (The full operational comparison — reconciling both payment rails inside one payroll close — is in WPS vs Egypt's Bank-Transfer Law.)

End-of-service gratuity vs. NOSI severance — different safety nets entirely

This is the single biggest conceptual gap between the two markets, and it's where most cross-border assumptions break. In the UAE, every employee who completes one year of service is entitled to end-of-service gratuity under Article 51 — 21 days' basic salary per year for the first five years, 30 days per year after, capped at 24 months. It's unconditional: it applies whether the employee resigns, is dismissed for cause, or the contract simply ends.

Egypt runs on a completely different model. There's no unconditional gratuity — severance is a triggered payment tied to specific termination scenarios, sitting on top of a pension-based social safety net (NOSI, at a combined 29.75% contribution rate) rather than replacing it. A standard resignation in Egypt carries no severance at all; unlawful dismissal pays at least 2 months per year of service; economic redundancy pays 1–1.5 months per year; retirement pays 0.5–1 month per year — four different formulas depending on the scenario (the full matrix is in End-of-Service Pay in Egypt).

The practical consequence: a company with mirrored HR policies across both offices — "everyone who leaves after a year gets X" — is applying a UAE-shaped assumption to a market where it doesn't hold. Egypt's final settlement isn't a smaller or simpler version of UAE gratuity; it's a structurally different mechanism, and treating it as a translation problem rather than a different system is where the compliance gap opens.

Each side in full: EOS & Gratuity in the UAE, Explained and End-of-Service Pay in Egypt.

Two currencies, two payroll calendars, one company

Running payroll for both markets means maintaining separate calendars, separate statutory rate tables, and separate currencies (AED and EGP) that don't move together — Egypt's insured-salary base for NOSI increases by 15% every January under a scheduled seven-year Prime Ministerial resolution, while UAE's GPSSA contribution bands and Emiratisation salary floors move on their own separate timeline. Neither market's regulatory calendar is aware of the other's.

This is exactly the scenario where a single spreadsheet-based or manually maintained system starts to break down in a way that's invisible until it isn't: a rate table updated for Egypt's January change but not cross-checked against the UAE's own concurrent updates, or a payroll closing date that assumes both markets run on the same cycle when their statutory deadlines (WPS submission timing vs. Egypt's Form 6 filing window) don't actually align. Running both markets on one platform, with country-specific rate tables that update independently on their own effective dates, removes the manual cross-checking step entirely — which is the difference between "we happened to catch it" and "the system caught it."

What actually needs to be handled per-country, not once

Five areas where "one policy, two markets" fails in practice:

1. Payment rails — WPS (universal, UAE) vs. bank-transfer law (threshold-triggered, Egypt). Different triggers, different penalty structures.
2. Termination payouts — unconditional gratuity (UAE) vs. triggered severance under four distinct formulas (Egypt).
3. Social insurance — GPSSA (UAE nationals only, expat exemption) vs. NOSI (universal, 29.75% combined rate, annually indexed base).
4. Localization quotas — Emiratisation (2%/year toward 10% by end of 2026, 50+ employee threshold) vs. Egypt's foreign-worker cap (10% of headcount, opposite direction — capping foreigners rather than mandating locals).
5. Statutory deadlines — WPS submission cycles and visa/work-permit renewal windows (UAE) vs. Form 6 NOSI deregistration (≤7 days of termination) and payroll tax filing deadlines (Egypt).

None of these five map onto each other cleanly. A platform (or a spreadsheet, or a person) treating them as one rule applied to two countries will eventually apply the wrong one to the wrong market — usually the first time an edge case shows up, not during routine operation.

Country by country: HR & Payroll Compliance in the UAE — Complete 2026 Guide · HR & Payroll Compliance in Egypt — Complete 2026 Guide.