Payroll that already agrees with your ledger and with GOSI.
Attendance and leave feed the payroll run. The run posts a balanced journal. The WPS file comes out of the same data, and the basic salary it carries is the one GOSI has registered. Not three systems reconciled monthly — one system that cannot disagree with itself.
- WPS file prepared from your payroll run
- GOSI-aligned basic salary by design
- Payroll posts straight to the ledger
Three numbers for one employee, kept in three places.
What the employee receives, what GOSI has registered, and what the wage protection file carries. When those drift apart, the compliance index notices before you do — and the fix is structural, not a monthly reconciliation.
Payroll is built in a spreadsheet, then the WPS file is assembled by hand from it each month.
The payroll run produces the WPS file. One source, so the file cannot drift from what you paid.
Commission is left out of the GOSI-registered wage because it varies — and it is counted as basic wage.
The contributory wage is calculated to the rules, so what is registered matches what should be.
A salary is raised in payroll and nobody updates GOSI, which is a counted violation even when everyone is paid in full and on time.
A change to a salary is one change, visible to payroll, to the WPS file and to the GOSI figure together.
Payroll is journalised later by finance, so the month closes on numbers HR produced days earlier.
Approving the run posts the entry. Finance is not waiting on HR to send a summary.
From clock-in to the posted journal.
Everything below shares the employee record, the chart of accounts and the approval rules with the rest of the platform.
Employee records and org
Contracts, documents with expiry tracking, iqama and ID data, reporting lines and branch structure in one register.
Attendance and leave
Shifts, timesheets, overtime and leave balances, with approvals that reach the person who should approve them.
Payroll runs
A run assembled from real attendance, with allowances, deductions and end-of-service calculated and shown before anyone approves.
WPS file preparation
The wage protection file built from the approved run, in the required structure, with the records that would be rejected flagged first.
GOSI alignment
The contributory wage calculated to the rules — including commission — so the registered figure and the paid figure do not quietly diverge.
AI checks before you approve
Agents surface what looks wrong in a run — a figure out of pattern, a record that will be rejected, a salary that no longer matches GOSI — while it is still a draft.
Compliance here is arithmetic, and the arithmetic is specific.
The index counts GOSI registrations
Your wage protection percentage is workers paid through WPS over workers registered with GOSI — not over the people you actually pay. A registered employee paid another way lowers it.
Commission is basic wage
GOSI treats commission and a percentage of sales or profits as basic wage. Leaving them out because they vary is the most common cause of a mismatch.
The 50% and 20% lines
Deducting more than half the GOSI-registered basic, or paying more than 20% above it, is counted against you — even when the wage was paid in full and on time.
Deadlines on a 15-day rhythm
Joiners and leavers notified within 15 days of the following month, and a delay period counted in whole months, so one day late is a month late.
HR is not a separate product here. It is one more department on the same data.
The payroll journal lands in the same ledger that issues your invoices and prepares your VAT return, under the same permissions.
- HR & Payroll
- WPS
- GOSI
- Accounting
- CRM
- Projects
- AI agents
Most of the work is in the data, not the software.
- 01
Employee data comes across
Records, contracts, balances and current salary structure, checked against what GOSI holds rather than assumed.
- 02
Contributory wages reconciled
Where the registered figure and the real structure disagree, you see the list before anything is filed.
- 03
Attendance rules configured
Shifts, overtime policy, leave entitlements and the approval chain that matches how you actually work.
- 04
A parallel payroll run
Your next month calculated both ways, compared line by line, before the old process is retired.
- 05
WPS file validated
The first file checked against the rejection rules before it goes to the bank, not after it bounces.
- 06
Then it is monthly routine
Attendance closes, the run is reviewed and approved, the file is produced and the journal is posted.
Everything you want to know before you start.
How is this different from ZenHR, Bayzat or Palm.hr?
Those are dedicated HR platforms, and they are good at being that. The difference is structural rather than feature-by-feature: they are HR products that integrate with your finance system, while in emerge the payroll run and the accounting entry are the same event in the same system. If you want best-of-breed HR and your finance side is already settled, a dedicated HRMS may suit you better. If the cost you feel is the gap between HR, payroll and the ledger, that gap is what we remove.
Does emerge submit the WPS file or file with GOSI for us?
No. emerge prepares the payroll run and produces the wage protection file from it, and keeps the contributory wage aligned with the GOSI rules. Submission to the bank or the portal stays with you — we do not claim automated filing, because we do not do it.
Can it handle Saudi and non-Saudi employees correctly?
Yes, and they are genuinely different. Saudi employees carry the pension branch and the unemployment branch alongside occupational hazards; non-Saudi employees carry occupational hazards only, paid by the employer, with no employee deduction. The system applies the right treatment rather than a single blanket rate.
What about the new social insurance system?
Employees first registered from 3 July 2024 fall under the newer rules, with pension contributions rising on a published schedule, while those registered before continue on the previous rates. One company can be running both at once, so the system distinguishes by first registration date rather than by hire date.
What happens to end-of-service calculations?
They are calculated from the contract and service record held in the same system, so the figure reflects actual recorded service rather than a separate spreadsheet, and the provision can be carried in the ledger rather than discovered at settlement.
We have multiple branches and commercial registrations. Does that work?
Yes. Branches, separate registrations and their own payroll cycles are supported, which matters for wage protection because the obligation and the compliance picture are per establishment, not per group.
See it run your payroll, not a sample one.
- Bring last month's payroll and we will run it through
- We will show you where your figures and GOSI's disagree
- A WPS file checked against the rejection rules, live
- Straight answers on what we do not automate
Or reach us directly