Lesson 2 — First insured date: the field that decides the next thirty years
This is the field that quietly does the most damage when it is wrong, because nothing on the payslip looks broken.
The obligation. Which pension law applies is a fact about the person, not about your company. First insured date is the date the employee was first registered under any UAE social-insurance scheme — not the date they joined you. An Emirati who started with another employer in 2015, spent three years outside the country and joined you last month is in Cohort A, and stays there.
- first insured before 31 October 2023 → Law 7/1999: 5% employee, 12.5% employer, contribution salary capped at AED 50,000
- first insured on or after 31 October 2023 → FDL 57/2023: 11% employee, 15% employer, contribution salary banded AED 3,000–70,000
The mental model. The scheme and the date are two separate decisions, and neither is derived from the other. Social Security Scheme says which system a person belongs to. First insured date says which law inside that system applies to them. The scheme takes its initial value from nationality, and it is then never re-derived: changing an employee's nationality later does not change their scheme. That is deliberate, because a silent reroute of someone's pension is not something a nationality edit should be able to do. If a scheme genuinely needs to change, change it yourself, on purpose, and note why.
The click path. Open the employee, go to the HR Settings tab, find the UAE Payroll & Social Security group, and fill First insured date from the employee's own GPSSA registration rather than from your contract file. Ask the employee for their GPSSA registration details, or ask GPSSA. A hire date from your own HR system is the wrong source for this field, and it is the source people reach for.
Empty is not neutral. If you leave the date blank the system assumes the newer law and shows a notice on the employee form. That assumption is right for a recent hire and wrong for a long-serving Emirati — and being wrong here applies the wrong rates for years before anyone reconciles it.
The worked example. An Emirati finance officer with a contribution salary of AED 30,000, first insured on 12 March 2015, joins you and the date field is left empty. The system applies Cohort B. Here is what that produces every month.
| Payslip line | Applied with the date empty | Correct for a 2015 registration | Monthly error |
|---|---|---|---|
| Employee deduction | AED 3,300 | AED 1,500 | AED 1,800 |
| Employer contribution | AED 4,500 | AED 3,750 | AED 750 |
| Total on your payslip | AED 7,800 | AED 5,250 | AED 2,550 |
That is AED 2,550 a month, AED 30,600 over a year, and it repeats every year until someone opens the field. The employee is over-deducted by AED 1,800 a month from net pay they have already budgeted, and the correction is a payroll adjustment with an employee conversation attached to it. The government's 2.5% under Cohort A never appears on your payslip at all, which is why the totals above are your two shares only.
The failure mode. Two errors sit next to each other here. The first is filling the field from the joining date, which silently promotes long-serving Emiratis into the newer cohort. The second is a stopped payslip reading "... is set to the GPSSA scheme but has no nationality" — set the nationality on the employee record, because the scheme cannot be resolved without it and a silent zero on a pension is worse than a stopped payslip. Audit the field across your whole Emirati population before your next January run, not one employee at a time as payslips fail.