GOSI Contribution Cohorts: Reconciling a Saudi Payroll File

The compliance changelog entry ksa-gosi-cohorts-2024 records the change with an effective date of 3 July 2024 and the authority given as “GOSI — gosi.gov.sa; mercans.com”. Its statement:

“Saudi employees who first joined GOSI before 3 July 2024 remain on the earlier contribution schedule; those who joined on or after that date follow the phased new-law rates.”

The dataset row the entry cites — the Saudi Arabia line of the social-security table, verified 2026-08-22 — states the rates:

“GOSI: Saudis hired before 3 July 2024 — employer 11.75%. Saudis under the new system (hired on/after 3 July 2024) — employer 12.75% from July 2026 (stepping annually). Non-Saudis: employer 2% (occupational hazards). Contributory wage cap SAR 45,000/month.”

Three things follow from reading it closely. First, the discriminator is the date of first GOSI registration, not the date of the current contract, so an employee who left and rejoined is decided by the earlier record. Second, the new-system rate is described as stepping annually, with the row naming the figure that applies from July 2026 — which means the rate a payroll file applies is a function of the period being paid, not a constant. Third, non-Saudi employees sit outside the split entirely on the occupational-hazards rate.

The entry and the row are both on the hub: the changelog entry and the social-security table. Figures that are not in that row are not published here; the schedule is GOSI's to state, and the row names it as the authority.

Applying the right schedule is a data problem before it is a calculation problem. Three fields decide the answer for each person, and if any of them is absent or stale, the calculation is confidently wrong.

GOSI registration date

The date the employee first joined GOSI is what places them in one cohort or the other. It is not derivable from the hire date at your company, from the contract start date, or from the Qiwa record — a mid-career joiner may have registered with GOSI a decade before joining you. This field has to be captured at onboarding and stored, not inferred at payroll time.

Nationality

The row separates Saudi nationals from non-Saudis, and the two sit on entirely different bases — the cohort split applies only to the Saudi population. Nationality also drives Nitaqat counting, which is a separate obligation running on the same employee record.

Contributory wage basis

The wage GOSI contributions are computed on is a defined basis, and the row records a contributory wage cap. What matters operationally is that the components included in that basis are stored as components — basic, housing and the rest, each tagged — rather than as a single gross figure, because a gross figure cannot be re-derived into a contributory wage after the fact.

A fourth field is worth carrying even though it does not change the rate: the period each line covers. The row's description of an annually stepping rate means the applicable figure is tied to the month being paid, so a retrospective adjustment for an earlier month is not computed at this month's rate.

Saudi payroll maintains several parallel wage definitions at once, and reconciliation is the work of keeping them consistent rather than identical. The wage-protection row for Saudi Arabia states the relationship directly:

“Mudad wage protection mandatory. Monthly wage files are reconciled against the Qiwa-authenticated contract wage and the GOSI contributory wage.”

So one employee carries at least three figures in the same month: the contract wage authenticated on Qiwa, the contributory wage GOSI contributions are computed on, and the wage actually paid and filed through Mudad. The end-of-service calculation adds a fourth basis — the gratuity row states “Half a month's wage per year for the first 5 years, one month per additional year (Labour Law, Art. 84)”, with settlement “within one week of employer-initiated termination, two weeks on resignation”.

None of those four is a copy of the others, and none of them can be reconstructed from a single gross number. That is the structural reason the checklist below is per-employee rather than per-total: a file whose grand total matches the ledger can contain two offsetting per-employee errors, and the systems that receive it check people, not totals.

The Nitaqat obligation runs on the same record. The Saudi nationalisation row records that “From 15 April 2026 a Saudi employee counts toward Nitaqat only if the contract is electronically documented and authenticated on Qiwa” — an unauthenticated contract is therefore both a Nitaqat problem and a reconciliation problem, because the contract wage the Mudad file is reconciled against is the authenticated one.

Each check is one question, answered per employee, against the file you are about to upload.

1. Every Saudi employee on the file has a stored GOSI registration date, and none of them is blank or defaulted to the hire date.
2. Each Saudi employee is assigned to the pre-3-July-2024 cohort or the on-or-after cohort by that stored date, and the assignment is recomputed rather than carried forward from last month.
3. Rejoiners and internal transfers are assigned by their earliest GOSI registration, not by the most recent one.
4. Every employee's nationality on the file matches the nationality on their GOSI record, because the Saudi and non-Saudi bases are different.
5. Non-Saudi employees are on the occupational-hazards basis only, and none of them has been swept into a Saudi cohort by a default rule.
6. The contributory wage for each employee is built from tagged components rather than a single gross figure, and the components included match your documented definition of the basis.
7. Any employee whose contributory wage sits at or near the cap recorded in the dataset row is checked individually, since a capped wage does not move with a salary change.
8. Every line's pay period is the month being filed, and any retrospective adjustment for an earlier month is computed on the schedule that applied to that month, not this one.
9. The contract wage on Qiwa, the contributory wage, and the wage on the Mudad file are compared per employee, and every divergence is explainable by a documented difference in basis rather than unexplained.
10. Joiners and leavers in the month are present exactly once — a joiner with no GOSI registration date and a leaver still on the file are the two failures this check exists to catch.

Run these before the upload rather than after a rejection. The Saudi penalties row records that “Mudad/WPS violations draw HRSD fines and service suspensions; low Nitaqat bands block visa and transfer services”, so the cost of a bad file is not confined to payroll.

Wage protection filing in Saudi Arabia is monthly and it is a file: the payroll system produces the salary file, and a human uploads it to Mudad, where it is reconciled against the Qiwa-authenticated contract wage and the GOSI contributory wage. Treating it as a file step rather than as an integration has two practical consequences.

The file is the artefact you can check

Because the upload is a file, everything in the checklist above can be run against that file before it is submitted — the same discipline a UAE team applies to a WPS Salary Information File before the bank sees it. A file is inspectable; a submission is not.

Nothing here is an API claim

This article makes no claim that any payroll system posts contributions to GOSI programmatically or writes into Mudad through an interface. NeuralHR.AI calculates GOSI contributions on the contributory wage by nationality and prepares the Mudad salary file from the same payroll run, and the upload remains a person uploading a file. Where a vendor describes something stronger than that, ask which endpoint, and ask to see it.

For the end-of-service side of the same employee record, our Saudi GOSI and end-of-service calculator applies the Labour Law formula quoted above.

The rates in this article are the ones written in the social-security row of our GCC compliance dataset, quoted rather than paraphrased, with the authority recorded as “GOSI — gosi.gov.sa; mercans.com” and a verification date of 22 August 2026. No other rate appears here, and no rate for a future period is projected beyond what that row states.

That is a deliberate limit rather than a gap. Contribution schedules are amended by the authority that publishes them, and an article that restates a rate in its own words becomes wrong silently. The dataset table carries a verification date for exactly this reason: if the date is old, treat the figure as needing a re-check against GOSI before you rely on it.

Nothing here is legal or tax advice, and none of it substitutes for GOSI's own published schedule or for advice on your specific establishment. Where your circumstances differ from the plain reading of the row — multiple establishments, seconded staff, employees registered outside Saudi Arabia — the row does not answer the question, and neither does this page.