Field notes · Saudi Arabia · 9 minute read
Saudi Arabia's new Social Insurance law: what it means for SAP payroll.
GOSI's framework has been reshaped: new contribution rates, new eligibility rules, new transition treatment for existing employees. For SAP customers running ECP in KSA, this is wage-type, contribution-rate, and audit-trail work. Here is what to configure.
What changed in the law
Saudi Arabia has reformed its social insurance framework, administered by the General Organization for Social Insurance (GOSI). The reform, passed in 2026 [VERIFY: confirm the exact effective date against the published Royal Decree], touches areas that show up directly in SAP payroll configuration.
Contribution rates
Employer and employee split rates have shifted on both the pension side and the occupational hazard side.
VERIFY ratesEligibility
Coverage thresholds, the minimum and maximum contributory wage, have been adjusted.
VERIFY floor and ceilingSaudi vs non-Saudi
Saudis stay on pension plus occupational hazard; non-Saudis on occupational hazard only. Rates and ceilings for each have moved.
VERIFY per categoryTransition
Employees already enrolled are transitioned, not re-enrolled. The mechanism is specific.
VERIFY mechanismNone of this changes the *structure* of how SAP ECP calculates social insurance for KSA. It changes the *parameters*, and parameters baked into wage-type configuration, contribution tables, and Saudi-vs-non-Saudi condition tables. Get those wrong and the payroll posts incorrect amounts. Get them silently wrong and the error compounds across cycles until GOSI flags the variance.
How GOSI calculates contributions
GOSI contributions are not arbitrary. They are calculated against a contributory wage, itself defined as a subset of the employee's total compensation. For Saudi nationals, the contributory wage includes basic salary plus housing allowance, up to the GOSI ceiling. For non-Saudis, the contributory wage is typically the basic salary only, for occupational hazard purposes. [VERIFY: confirm the current contributory-wage definitions against the 2026 GOSI rules.]
Exhibit · Integration flow
Category, rate and ceiling drive every GOSI contribution
SuccessFactors sets the category, ECP applies the rate and ceiling, GOSI reconciles the result.
SuccessFactors
Employee Central master data: Saudi or non-Saudi category
Employee Central Payroll
Applies rate, ceiling and wage-type GOSI flags
GOSI
Receives contributions, runs the variance check
SuccessFactors
Employee Central master data: Saudi or non-Saudi category
Employee Central Payroll
Applies rate, ceiling and wage-type GOSI flags
GOSI
Receives contributions, runs the variance check
What runs through the channel
Source: GOSI 2026 reform and SAP ECP KSA localisation pack. [VERIFY: rates, ceiling, floor and effective date against the published GOSI rules.]
The mechanism inside ECP:
Wage types feed the base
Each wage type carries a flag: does it contribute to the GOSI contributory wage. Wrong flag, wrong base.
The ceiling caps it
Above the GOSI ceiling the contributory wage stops accumulating. A new ceiling means new high-earner treatment.
The rate applies per category
Saudi or non-Saudi is read off the SuccessFactors master data; the rate is held in ECP configuration tables.
Employer mirrors employee
Both halves post to S/4 as separate cost lines, with the GOSI vendor as the receiver.
Impact on Employee Central Payroll
The reform reaches ECP in five places. None of them are surprising; all of them have to be configured correctly before the first cycle under the new law runs.
Constants table
New GOSI rates (employer, employee, occupational hazard, pension) entered with the effective date.
Ceiling and floor
Contributory-wage cap and minimum updated as country-specific constants in the KSA localisation pack.
Wage-type flags
Each wage type carries the correct GOSI-contributory flag; new allowance categories get the right treatment.
VERIFY new categoriesSaudi-vs-non-Saudi conditions
The condition routing a calculation down the Saudi or non-Saudi path is checked against the new treatment.
Schema and rules
Any custom rule that hard-codes a rate is updated. We read from the constants table, never hard-code.
Wage-type configuration changes
The least visible failure mode. A wage type that should contribute to the GOSI base (say, a new housing-equivalent allowance) but isn't flagged correctly, silently understates the contribution. Multiplied across the workforce, across cycles, the understatement compounds. GOSI's variance check catches it. The employer pays the corrected contribution plus a penalty.
What we do during the reform configuration:
Inventory the wage types
Pull the full catalogue from ECP. For each, decide whether it contributes to GOSI under the new definitions.
Compare against the old configuration
Any wage type whose flag flips between old and new rules is a transition risk. Note it.
Test against a parallel cycle
Run a representative payroll under both configurations on the same data. Reconcile, and investigate any variance over a de-minimis threshold.
Document the decision
For each wage type: the treatment, who decided, when. This is the artefact GOSI asks for in an audit.
The transition rules
The reform does not re-enrol existing employees. It transitions them. [VERIFY: confirm the specific transition mechanism, whether existing contracts continue under old rules or shift to new rules immediately.]
For ECP, the transition treatment lands in three places:
Effective-date tables
New constants apply from a specific date. ECP effective-date handling is standard, but the date must be set correctly.
Grandfathered cases
Any employee categories exempt from the new rules need an explicit schema condition to stay on the old treatment.
VERIFY exemptionsRetro calculation
A correction crossing the transition date applies the right rules either side. ECP's retro engine handles it when the effective dates are right.
The reform doesn't change what payroll is. It changes the rate the system multiplies by. The painful part is making sure every wage type, every condition, every constant knows it.
Audit trail and compliance posture
Three obligations sit on top of the configuration work.
Configuration change trail
Who updated the rate, when, against what published source. ECP's change log captures it; keep the source documents alongside.
Reconciliation to GOSI
Periodic reconciliation between ECP's calculated contributions and GOSI's accepted contributions. Variances above a threshold get investigated before the next cycle.
Saudi PDPL
Salary, nationality and contribution data are personal data under Saudi PDPL. The standard ECP-on-BTP tenant region treatment applies.
VERIFY tenant regionWhere to start
Three moves for any KSA enterprise running ECP in the wake of the reform:
Update the constants and ceiling
Against the published GOSI rates, effective on the regulator's date. Not before, not after.
Audit every wage-type GOSI flag
If the answer to whether an allowance contributes has changed, fix the flag before the first cycle under the new rules.
Run a parallel test cycle
Calculate one payroll under old rules and one under new on the same data. Reconcile. Find the variances before the regulator does.
The reform is solvable in standard ECP if the localisation pack is current and the wage-type catalogue is disciplined. The failure pattern we see is customers updating the constants and forgetting the wage-type flags, and discovering the gap three cycles later when GOSI sends a variance notice. Do the wage-type pass first. The rate update is easy by comparison.
Next step