WPS and payroll: getting it right every month

Payroll compliance in Saudi has three clocks running at once: salaries through WPS, GOSI contributions, and the accounting entries that put the true cost on your P&L.

Trouble almost always comes from treating them separately — salaries paid but never booked, GOSI paid late because nobody owned the date, allowances handled in cash outside the file.

One monthly payroll close — file, pay, book, reconcile, same order every month — makes all three clocks tick together. It’s an afternoon of discipline that removes an entire category of penalties.

What WPS is actually checking

The Wage Protection System compares what you told the Ministry you would pay against what the bank says you actually paid. Two files, one comparison. Most failures are not about underpaying anyone — they are about the two files disagreeing.

The usual causes are mundane. An IBAN that changed and was updated in the payroll sheet but not in the portal. An employee who left mid-month and is still on the establishment file. A name spelled differently in two systems. A payment made from a second bank account that WPS is not looking at.

Why small mismatches escalate

A single flagged month is an administrative matter. A pattern is not. Because WPS status feeds into services you rely on — visa issuance, transfers, establishment standing — a payroll problem stops being a payroll problem and becomes an operations problem.

The businesses that get caught out are rarely the ones in financial difficulty. They are the ones where payroll is one person's undocumented routine, and that person took leave in a month when an IBAN changed.

The sequence that works

Run payroll against the establishment file, not against last month's spreadsheet. The file is the source of truth for who is on the payroll and what their details are; the spreadsheet is a copy that drifts.

Reconcile three numbers before you transfer: the payroll register total, the bank file total, and the WPS upload total. If all three agree, the month will clear. If any two disagree, find out why now — it is a five-minute check against a correction that takes weeks.

Then upload, transfer, and confirm the status actually posted. Do not assume a submission that did not error was a submission that matched.

The joiners and leavers problem

Most mismatches happen at the edges of the month. Someone joins on the 20th and is paid a partial month; someone resigns on the 5th and is paid to that date plus end-of-service.

Two rules prevent nearly all of it. First, update the establishment file before running payroll, not after. Second, keep final settlements — end-of-service, leave encashment, notice pay — separate from the WPS wage figure, since they are not the monthly wage the system is comparing against.

Making it survive a holiday

Write the routine down. Not a policy document — a one-page sequence with the portal, the bank, the deadline, the three reconciling numbers, and who signs off.

Then have someone other than the preparer look at the reconciliation. Payroll is the one process where the person who makes an error is also the person checking it, which is precisely why errors survive.