Construction Payroll Compliance in Saudi Arabia: Managing WPS, GOSI, and Multi-Nationality Rules at Scale - Blog
Construction Payroll Compliance in Saudi Arabia: Managing WPS, GOSI, and Multi-Nationality Rules at Scale

May 30, 2026

Construction Payroll Compliance in Saudi Arabia: Managing WPS, GOSI, and Multi-Nationality Rules at Scale

Ahmed ElazabAhmed Elazab

Running payroll for a construction workforce in Saudi Arabia isn't a monthly HR task — it's a multi-layered compliance programme that sits at the intersection of labour law, tax regulation, cost accounting, and project controls. When it fails, the consequences range from government fines to subcontractor disputes to project P&Ls that don't reflect reality.

Most GCC construction companies are compliant enough to avoid the largest penalties. But "compliant enough" and "accurate" are not the same thing — and the gap between them tends to sit in EOSB accruals nobody calculates, GOSI submissions that don't match actual headcount, and payroll data that never reaches project cost codes.

Why Construction Payroll Is Structurally More Complex

A standard commercial business might have 50 employees, two job grades, and a single pay structure. A mid-sized Saudi construction contractor running two active projects might have 800 people across 12 nationalities, four contract types — direct hire, secondment, company-supplied daily labour, subcontractor-supplied — and allowances that vary by trade, nationality, project location, and seniority.

Each element of the payroll stack has its own compliance requirement:

  • Wages → WPS bank transfer by the 7th of the following month
  • GOSI contributions → filed and paid by the 15th; rates differ for Saudi nationals vs. expats
  • EOSB → must accrue monthly; most contractors don't calculate it project-by-project
  • Annual leave encashment → must be processed when taken or bought out, not batched year-end
  • Overtime → Saudi Labor Law Article 107: 150% of regular rate for hours beyond 8/day or 48/week

Each gets its own reporting obligation, its own bank transaction, and its own exposure if it's wrong.

WPS Compliance: The Three Places Construction Contractors Get Caught

The Wage Protection System mandates that all workers receive wages through a registered bank on time, with a structured SIF (Salary Information File) submitted to MHRSD. Three recurring problems trip up construction companies:

Payroll cut-off vs. attendance data lag

Construction sites pay based on attendance. Attendance data from a remote desert site near Yanbu might reach the payroll team three days late. When it does, payroll runs against deadline pressure rather than verified data — and late WPS transfers trigger the first penalty tier: hiring suspension from Musaned and Qiwa portals.

Daily labour not on the WPS register

Many contractors use site-level cash payments for daily and piece-rate workers, especially non-national trades. These workers don't appear in the WPS file but do appear in any MHRSD inspection. The misalignment creates exposure regardless of whether the wages are real and paid.

Allowances excluded from the SIF base

Housing, transport, food, and project allowances must be included in the SIF if they are contractually guaranteed. Contractors who separate allowances into non-WPS payments to reduce the reporting base are technically non-compliant — and exposed in any GOSI audit where declared earnings differ from actual earnings.

GOSI: The Accrual Most Contractors Understate

GOSI contributions apply differently by nationality:

  • Saudi nationals: 10% employer + 9.75% employee contribution, assessed on salary plus most guaranteed allowances
  • Non-Saudi nationals: 2% employer contribution only, applied to gross earnings

The compliance issue usually isn't the rate — it's the base. GOSI is assessed on contracted earnings, not just basic salary. If a contractor has been reporting GOSI only on basic wages and excluding project allowances that are contractually guaranteed, the differential accumulates quietly for years. A GOSI audit looking back three to five years produces a retroactive liability plus 2% monthly penalties.

For a contractor with 300 Saudi staff at SAR 6,000 average monthly wage, a SAR 500/month allowance exclusion per person represents SAR 18,000/month in underpaid employer contribution — SAR 216,000/year before penalties. The fix: calculate GOSI on the base that includes all contractually guaranteed cash components, and reconcile the GOSI filing against actual payroll outputs monthly.

EOSB Accruals: The Cash Shock at Project End

End of Service Benefit accruals are where most GCC construction finance teams have an invisible problem. Saudi Labor Law mandates EOSB on a sliding scale: half-month salary per year for service under five years, one month per year for five or more.

Most contractors calculate EOSB at termination rather than accruing it monthly by project. This creates two problems.

The cash shock at project completion. If 200 workers finish a three-year project simultaneously, the EOSB liability — say SAR 1,800/month average basic salary × 1.5 months average accrual × 200 people — is SAR 540,000 in a single month. A project P&L that didn't carry this as an accrued cost will show a late-stage expense that wipes margin from a project the PM thought was profitable.

The project cost misallocation. EOSB is a project-level labour cost. If a worker spent 18 months on Project A and 18 months on Project B, their EOSB should be split between those projects — not charged entirely to whichever project they happen to finish on. Getting this right requires monthly EOSB accruals tied to project assignment, which requires timesheets that record project allocation.

Proper treatment: calculate EOSB monthly for every employee, allocate to the project by the same WBS codes as their timesheets, and carry the accrual as a balance sheet liability. When employment terminates, the cash payment clears against the accrual rather than appearing as a surprise P&L line.

Multi-Nationality Payroll on a Single Site

A typical GCC construction project at scale might employ nationals of Saudi Arabia, India, Pakistan, Bangladesh, Philippines, Egypt, Jordan, Yemen, Sudan, Sri Lanka, and Nepal. Each brings a different payroll structure:

  • Indian and Pakistani workers commonly have annual airfare as a contractual term — which must accrue monthly and appear in project cost
  • Filipino workers are covered by POEA standard terms — specific allowances, OFW remittance structures, and minimum wage floors set by the Philippine government
  • Saudi nationals attract GOSI employer contributions and affect the company's Nitaqat Saudization tier
  • Yemeni workers under bilateral agreements have specific documentation requirements under Musaned

The problem isn't that contractors don't know these rules. It's that when payroll is processed in Excel with separate files per nationality, there is no mechanism to enforce rules consistently, no audit trail, and no structured output for GOSI filings, WPS reconciliation, annual leave liability by project, or EOSB by employee.

Connecting Payroll to Project Cost

Payroll in construction serves two masters: HR compliance and project cost accounting. Most construction companies optimise for one and neglect the other.

A payroll system that generates a WPS file satisfies the compliance requirement. But unless those wages are also allocated to WBS cost codes by project and work package, payroll data doesn't reach the project P&L — and labour ends up as a central overhead line rather than a traceable project cost.

Where this breaks down in practice:

  • Site timesheets don't carry cost codes. They're submitted as attendance records for payroll, not as cost allocation records. Finance adds cost codes manually — two to four days at month-end, with transcription errors.
  • Allowances post to a single GL account rather than being split by project. Housing and transport allowances often represent 30–40% of total direct labour cost on a GCC site. Posting them centrally understates project labour cost by that margin.
  • Overtime premium isn't tracked at the task level. If a subcontractor crew works 12-hour shifts to recover a schedule delay, the premium pay should be coded to the specific WBS activity — and may be recoverable as a variation. Without WBS linkage, it disappears into the general payroll figure.

The Compliant Monthly Payroll Workflow

A construction payroll process that satisfies WPS, GOSI, EOSB, and project cost requirements in one pass:

  • Days 1–5: Timesheet close-out with mandatory project code and WBS code; payroll calculation covering basic salary, guaranteed allowances, overtime at 150%, and leave accruals
  • Day 5: GOSI declaration via Mudad/Muqeem portal on the correct earnings base; WPS SIF file generated and reviewed (greater than 5% month-on-month variance = exception flag)
  • Day 7: WPS bank transfer executed. Failure triggers Qiwa/Musaned compliance flag immediately
  • Days 6–10: EOSB accrual journal allocated to project WBS; allowance coding journals posting to project cost codes; overtime premium journals to WBS and cost code
  • Day 15: GOSI payment deadline. Late payment triggers 2% monthly penalty plus eventual suspension from government tender lists

Actionable Takeaways

Payroll compliance in Saudi construction is a monthly discipline that either builds or erodes both your regulatory standing and your project cost accuracy:

  • Audit your GOSI base. Pull the last three months of GOSI filings and compare declared earnings against actual payroll. The most common gap: guaranteed allowances excluded from the GOSI base. Quantify the exposure before the regulator does.
  • Start accruing EOSB monthly by project. Calculate the monthly accrual for each direct employee, allocate to the assigned project WBS, and carry the balance as a project cost line. At project close, the EOSB payout clears the accrual rather than appearing as a surprise.
  • Add WBS codes to timesheets at point of submission. Not retroactively by finance. The supervisor approving attendance knows the work location — make cost code mandatory on the timesheet.
  • Define a single GOSI cut-off date. Pick the 8th. Everything before is in that month's filing. Consistency matters more than perfection.
  • Run a nationality allowance audit. For every employee type with contractually mandated allowances beyond basic salary — Filipino OFW terms, annual airfare provisions, housing guarantees — verify the allowance appears in the WPS file and is included in the GOSI base where required.

Construction payroll done properly isn't just compliance. It's the data feed that makes your project P&L accurate. Every hour coded to a WBS, every EOSB accrual that reduces end-of-project cash shock, and every allowance that hits the right cost line improves the quality of the cost reports your project teams are actually managing against.

Did you enjoy reading this blog? Share it

Ready to find out more?