Almadar A payroll error for staff at a company headquartered on King Fahd Road is visible to every employee the same day, which is exactly why this configuration deserves more scrutiny than a general ledger setting.
Payroll must reflect the Saudi Labor Law and the systems that surround it: GOSI contributions at the correct rates for Saudi and non-Saudi employees, end-of-service benefit accrual under the statutory formula, Hijri-aware leave entitlements, and Wage Protection System file generation in each bank's required format. Configuration and testing are inseparable here.
Earnings, allowances and the GOSI base
The basic-plus-allowances structure matters beyond presentation, because GOSI contributions and end-of-service calculations are based on defined elements rather than gross pay. Housing and transport allowances, overtime, and variable elements each need explicit treatment. Misclassifying an allowance produces a GOSI contribution error that repeats every month and accumulates into a material liability before anyone notices.
End-of-service benefit accrual
EOSB under the Labor Law depends on length of service and reason for termination, with different treatment for resignation and termination and different rates for the first five years and thereafter. Accruing this monthly rather than calculating it at departure gives the auditors a defensible liability figure and stops end-of-service payments from being an unpleasant cash surprise. Most legacy systems in use in Saudi Arabia do not accrue at all.
Leave and the calendar problem
Annual leave, sick leave and Hajj leave entitlements follow the Labor Law, and some entitlements interact with the Hijri calendar while payroll periods run on the Gregorian. The system must handle both without the finance team maintaining a parallel spreadsheet, which is what happens by default when leave accrual is not configured properly.
A common Saudi scenario
A Riyadh manufacturer with three hundred and forty employees runs payroll on a system configured in 2018 and never revisited. Review finds housing allowance excluded from the GOSI base for a subset of employees whose contracts were entered differently, understating contributions for over four years. The correction and disclosure are manageable but avoidable, and the underlying cause is that nobody had validated the configuration against a sample of actual contracts since go-live.
Parallel running before cutover
We run the new payroll alongside the existing one for at least two cycles, reconciling every employee line by line, gross, each allowance, GOSI, deductions and net. Cutover happens only when the two agree and any differences are explained and accepted as corrections rather than unexplained variances. Where payroll is outsourced instead, the same discipline applies to the provider's first parallel runs.
Payroll controls and confidentiality
Payroll carries the most sensitive data in most organizations, and access controls matter as much as calculation accuracy. We configure roles so that the person who can change a salary is not the person who can release the payment, restrict visibility of individual pay to those who genuinely need it, and ensure the audit trail records who changed what. This is a core internal control expectation, and it links to WPS accuracy since uncontrolled master data changes are a frequent cause of submission mismatches.
Riyadh service businesses more often have straightforward structures but larger populations of non-Saudi employees with different GOSI treatment.