WPS payroll for Saudi workshops

What the Wage Protection System is

The Wage Protection System exists to answer one question with evidence rather than assertion: did this employer actually pay these employees, in full, on time? Before it, the answer lived in the employer’s own records. Now wages move through the banking system and the employer submits a monthly salary file describing what was paid to whom, which is matched against the employees registered to that establishment.

The mechanism is deliberately simple. If an employee exists on the establishment’s records but does not appear in the salary file, that is visible. If the amount paid does not match the contracted wage, that is visible too. If payment is late, the timing is visible. The system does not need to audit anyone; the gap between the two datasets does the work.

For an employer, the practical shift is that payroll now has an external deadline and an external format. It is no longer enough for the numbers to be right in your own system — they have to be right in a file that another party reads.

Source: Ministry of Human Resources and Social Development (hrsd.gov.sa)

Why compliance matters beyond the payroll run

WPS is not an isolated obligation. An establishment’s wage-payment record feeds into its standing on the national labour platforms, and that standing gates transactions the business needs in order to operate normally.

• Routine HR transactions — issuing work visas, transferring sponsorship, renewing work permits — depend on the establishment being in good standing.
• A workshop that cannot complete those transactions cannot hire the technicians it is short of, which turns a payroll administration problem into a capacity problem on the floor.
• Discrepancies are cumulative in effect: a single month with three employees missing from the file is a correction, but a pattern is a record.
• Because the data is matched rather than reviewed, errors that would once have been invisible — a wrong IBAN, an employee paid in cash, a contract amount never updated after a raise — surface as non-compliance.

Source: Qiwa (qiwa.sa)

What goes into a WPS salary file

The exact layout is defined by the banking channel the establishment uses, and employers should take the current specification from their own bank rather than from any third party. The content, however, is consistent, and it is worth understanding because every field is a place where payroll and HR records have to agree.

• Establishment-level identifiers — the employer’s registered labour identifier and bank details — plus the pay period the file covers.
• One record per employee, keyed on the national ID or Iqama number that identifies them on the establishment’s records.
• The employee’s bank account, as an IBAN, which must belong to that employee.
• Basic salary, housing allowance and other allowances, broken out rather than merged into a single figure.
• Deductions for the period.
• Net pay actually transferred — the figure the bank moves.
• Days worked or days on leave for the period, where the channel requires it.

Why workshop payroll is harder than office payroll

An office payroll is largely static: the same people, the same salaries, month after month, with occasional changes. A workshop payroll is not, and this is the real reason WPS filing goes wrong in this sector. The numbers change every month for reasons that originate on the workshop floor rather than in HR.

• Technician pay often includes a variable element — overtime, productivity, or a share tied to completed jobs — which means payroll depends on job card data being closed and accurate before the run.
• Attendance is genuinely variable. Shifts, absence, and leave move the days-worked figure that the file has to carry.
• Headcount turns over faster than in an office. A technician who joined on the 18th and one who left on the 9th both need correct partial-month treatment.
• Allowances differ by role and are frequently agreed verbally before anyone updates the employee file.
• End-of-service benefit accrues quietly in the background and is invisible until someone leaves — at which point it is a large, immediate cash number.
• A workshop’s payroll data therefore lives in two places at once: the HR file and the operational record of who actually worked on what. If those two are separate systems, the reconciliation is manual, monthly, and exactly where errors enter.

How MotorMind handles payroll and WPS

MotorMind runs HR and payroll inside the same platform as the workshop, which removes the monthly reconciliation described above. Attendance and technician time are captured against job cards as work happens, employee files hold contract terms and allowances, and the payroll run draws on both rather than on a spreadsheet assembled at month end.

From that run, MotorMind generates the WPS salary file ready for upload to the establishment’s bank, along with payslips for employees and payroll reports for management. To be precise about scope: MotorMind produces the file. The transfer itself is executed by your bank through its own channel, and MotorMind is not a submission agent and does not integrate with Mudad.

The rest of the HR module carries the paperwork the payroll depends on — employee files, contracts and documents with expiry tracking, leave balances, and end-of-service accrual so the liability is visible before it becomes a payment rather than after.

Where WPS filings usually go wrong

The failures are rarely exotic. Across small and mid-sized employers the same handful of causes account for most discrepancies, and all of them are records problems rather than payroll-calculation problems.

• An employee is registered to the establishment but paid outside the banking channel, so they are absent from the file entirely.
• The IBAN on record belongs to a relative, a former account, or a colleague — the transfer succeeds and the match fails.
• A salary was increased in practice but never updated in the employee file, so the paid amount and the contracted amount disagree.
• Allowances are merged into one figure, so the breakdown the file expects cannot be produced.
• New joiners and leavers are handled at the end of the month from memory rather than from dated records, producing wrong partial-month amounts.
• The file is produced from a spreadsheet that was copied from last month, carrying forward someone who has already left.

A monthly checklist

A workshop that runs these checks before generating the file will catch most of what would otherwise come back as a discrepancy.

• Reconcile headcount: everyone registered to the establishment is either in the file or has a dated leaving record explaining why not.
• Confirm that every IBAN belongs to the employee it is filed against, and re-verify after any account change.
• Check that contracted amounts in the employee file match what is actually being paid, including any raise agreed during the month.
• Close job cards and approve technician time before the payroll run, so variable pay is calculated on complete data.
• Verify partial-month calculations for joiners and leavers against their dated start and end records.
• Keep allowances broken out — basic, housing, other — rather than consolidated.
• Review the end-of-service accrual so the liability is understood before someone resigns.

Frequently asked questions