GOSI payroll: what payroll software has to get right

What GOSI actually is

The General Organization for Social Insurance runs social insurance in the Kingdom of Saudi Arabia. If you employ people there, you register them with GOSI and remit a contribution every month for as long as they are on your payroll.

Two things about the scheme matter to a payroll system more than anything else. First, Saudi nationals and non-Saudi employees fall under different branches, so nationality is a payroll input rather than a piece of HR trivia. Second, the contribution is shared between employer and employee for some branches and borne entirely by the employer for others — so one pay run produces both a deduction from net pay and a cost that never appears on a payslip at all.

The contributory wage is not gross pay

This is the part generic payroll software gets wrong, and it gets it wrong quietly.

GOSI is calculated on a contributory wage — a defined subset of what you pay someone, set by regulation and subject to a floor and a ceiling. It is not gross pay, and it is not basic salary either. A system that lets you decide, component by component, what forms the base can be made correct. A system that multiplies gross by a rate cannot, and the error compounds every month until something forces a reconciliation.

Where it goes wrong in practice

The monthly figure tends to break in a small number of recognisable ways:

• Gross used as the base. Every allowance that should have been excluded inflates the contribution; every one that should have been included understates it.
• Mid-month joiners and leavers. Apportioning a contribution is not the same operation as prorating a salary.
• Allowances that change mid-period. A housing allowance that changes on the 15th belongs in that month's contributory wage, not the next one.
• Nationality or status changes. The branch changes, but the change was recorded in HR and never reached payroll.
• The ceiling not applied. Senior salaries quietly over-contribute.
• Backdated corrections. A retrospective raise changes months already closed, and nothing recomputes what was owed for them.

None of these announce themselves. They surface at an inspection, or when an employee queries their record years later.

What a payroll system must do

• Hold nationality, registration number and branch per employee, and treat a change to any of them as a payroll event.
• Let you mark, component by component, what forms the contributory wage — and change that definition without restating history.
• Apply the floor and the ceiling as rules separate from salary proration.
• Apportion correctly for part-months, on joining and on leaving.
• Recompute a closed period when something backdated changes it, and show what moved.
• Keep the employee deduction and the employer cost as two distinct figures, because only one of them belongs on a payslip.
• Post the employer's share to the general ledger as a cost, rather than leaving it in a spreadsheet to be journalled by hand.
• Show, for any month, how the figure was arrived at. The auditable trail is the point.

How Nova HRM handles it

GOSI is part of payroll here rather than a report bolted on afterwards. Salary components carry their own contributory flag, so the wage base is a property of your salary structure and not a hard-coded assumption. Nationality and registration live on the employee record and feed the calculation directly. Pay runs are recomputable, and every run leaves an append-only trail of what it calculated.

The employer's share posts into the general ledger with the rest of the pay run, so the cost lands in your accounts in the same movement that produced it — there is no export to re-key. The same applies to the other regimes Nova HRM ships with: GPSSA and WPS SIF files in the UAE, QPEN in Qatar, and EOBI, provident fund and income-tax slabs in Pakistan.

Common questions