Why HR and Payroll Problems Keep Coming Back
A single payroll error rarely looks serious: an allowance missed one month, overtime paid at the wrong rate, a sick day deducted in full. The trouble is that these errors repeat, build up retroactively and touch the one thing every employee checks carefully, which is their pay. In Saudi Arabia there is also a dense regulatory layer on top: the Labour Law and its amendments effective February 2025, GOSI with two different rate regimes for Saudis, wage protection through Mudad with a 30-day window, Nitaqat, contract registration on Qiwa and iqama management through Muqeem.
This article diagnoses twelve common problems in four groups: payroll and compensation, compliance, daily operations and strategy. For each one we explain the cause, the relevant rule as we have verified it, a hypothetical worked example where it helps, and how an integrated HR and payroll ERP fixes it.
Part 1: Payroll and Compensation
Problem 1: Recurring payroll calculation errors
Three errors dominate: overtime, linking absence and leave to pay, and mid-month changes such as raises and promotions.
On overtime, Article 107 of the Labour Law requires the employer to pay, for each overtime hour, the hourly wage plus 50% of the basic wage. Hypothetical example: an employee earns SAR 6,000 basic, SAR 1,500 housing and SAR 500 transport, so SAR 8,000 in total. On a 30-day, 8-hour basis, the hourly wage is about SAR 33.33 and half the basic hourly rate is SAR 12.50, so one overtime hour is about SAR 45.83 under the common reading of the article. Typical mistakes are paying 150% of the total wage (SAR 50) or 150% of basic only (SAR 37.50). For someone working 30 overtime hours a month, the difference runs from roughly SAR 125 to SAR 250 depending on the error, multiplied across hundreds of staff and many months.
The ERP fix: one approved formula per overtime type applied automatically, attendance and leave feeding payroll directly, and mid-month changes prorated by effective date.
Problem 2: Late salaries and Mudad alerts
Since 1 March 2025 the WPS file must be uploaded to Mudad within 30 days, down from 60. According to press reports on Mudad's alert mechanism, reminders go out on the due date, ten days later and on day 15, and an inspection may be requested if no file is uploaded within about 20 days. Violation alerts also appear when a basic wage looks illogical against other recorded data, or when deductions exceed 50% of the wage.
The causes are usually internal: payroll built in Excel and reviewed by hand, wrong bank account numbers for a few employees, and gaps between the wage in payroll and the wage in the contract. The ERP fix: staged payroll approval, bank account validation before payment, direct salary transfer through bank integration, and alerts when deductions approach the 50% line. Our article on WPS and Mudad compliance goes into detail.
Problem 3: End-of-service award mistakes
Article 84 sets the award at half a month's wage for each of the first five years and a full month for each year after, based on the last wage, with partial years prorated. On resignation, Article 85 applies: nothing below two years, one third from two to under five years, two thirds from five to under ten.
Hypothetical example: seven years of service, last wage including allowances SAR 10,000. Full award: five years at half a month is SAR 25,000, two years at a full month is SAR 20,000, total SAR 45,000. On resignation, two thirds: SAR 30,000. The usual error is calculating on basic salary alone, producing a lower figure that becomes a labour dispute.
The accounting error matters just as much. Without a monthly provision, the company is surprised by large payouts when long-serving staff leave. The ERP fix: automatic calculation from joining date, last wage and exit type, with a provision posted to the ledger every month.
Problem 4: Complex allowances and benefits
Every allowance carries its own rules. Is it in the GOSI base? In the end-of-service base? Paid during leave? The GOSI base is basic salary plus housing, capped at SAR 45,000 a month, while allowances such as transport are outside it. Project allowances such as site allowance change when the employee moves.
The ERP fix: a pay structure that defines each component once with its properties (GOSI-able or not, in the EOS base or not, fixed or variable, project-linked or general) and applies the rules to everyone automatically.
Part 2: Compliance
Problem 5: Nitaqat surprises
The Developed Nitaqat programme, in place since 2021, places establishments in five bands: Platinum, High Green, Medium Green, Low Green and Red. Each activity has a minimum Saudization rate per band that rises gradually with headcount. Falling into Red means no new visas, no issuing or renewing expatriate work permits and no transfers in.
Surprises usually come from unconnected decisions: several Saudi resignations in the same month that a new project hires expatriates. The ERP fix: a live view of the current rate, and a simulation of each hire or exit before it is approved.
Problem 6: Wrong GOSI rates
This is where many legacy systems and spreadsheets go wrong. Saudis under the previous system pay 9.75% as employees, with 11.75% from the employer. New entrants from 3 July 2024 with no prior contributions fall under the new Social Insurance Law: the annuity rate started at 9% each side and rises by half a point every 1 July, to 9.5% from July 2025, 10% from July 2026 and 11% by July 2028, with SANED unchanged at 0.75% each side and occupational hazards at 2% for the employer. For expatriates, the employer pays 2% for occupational hazards only.
Hypothetical example: a Saudi under the previous system with a contributory wage of SAR 10,000 has SAR 975 deducted, and the employer pays SAR 1,175. The ERP fix: classify each employee by GOSI regime and maintain rate tables with effective dates that roll forward each July.
Problem 7: Contracts and probation
Since the amendments took effect in February 2025, probation can last up to 180 days and must be stated in the contract. Notice for indefinite contracts is 30 days when the employee resigns and 60 days when the employer terminates. Contracts are registered on Qiwa. The usual failure is a probation period that ends without a review, so the employee is confirmed by default, or a fixed-term contract that expires without a decision.
The ERP fix: contract and probation dates on the employee record, alerts to the line manager in time to review before probation ends, and alerts 60 days before fixed-term contracts expire.
Part 3: Daily Operations
Problem 8: Leave chaos
Leave types are many and each has its rule. A summary of what we have verified:
| Leave type | Entitlement | Notes |
|---|---|---|
| Annual | 21 days; 30 days after five continuous years | Cannot be cashed out during employment |
| Sick | Up to 120 days a year | 30 days full pay, 60 days at three quarters, 30 days unpaid |
| Maternity | 12 weeks full pay | Per 2025 amendments |
| Paternity | 3 paid days | Per 2025 amendments |
| Marriage | 5 paid days | Article 113 |
| Bereavement | 5 days for spouse, parent or child; 3 days for a sibling | Article 113 |
| Hajj | 10 to 15 paid days | Once, after two years' service |
The classic sick leave error is either deducting it all or paying it all, instead of applying the three bands within the year. The ERP fix: leave types defined with their rules, balances updated automatically, requests and approvals through employee self-service, and a direct link to payroll.
Problem 9: Unreliable attendance and uncontrolled overtime
Normal hours may not exceed 8 a day or 48 a week, falling for Muslims in Ramadan to 6 a day or 36 a week. Overtime is capped at 720 hours a year unless the worker agrees to more. Work under direct sun is banned from 12:00 to 15:00 between 15 June and 15 September for private-sector outdoor workers. Contractors and maintenance firms working across many sites need more than a fingerprint reader at head office.
The ERP fix: mobile attendance with a geo-fence per site so clock-ins only register on location, shift patterns that respect Ramadan hours and the midday ban, and alerts as anyone approaches the overtime cap. See geo-fencing attendance.
Problem 10: Turnover and slow clearance
An exit triggers a chain: return of company property, settling advances, calculating the award and leave balance, revoking access and updating government platforms. Done on paper forms passed between departments, it takes weeks. Final dues may be paid before property is returned, or delayed until the case becomes a complaint.
The ERP fix: electronic clearance with parallel approvals, a final settlement calculated automatically from leave, award and advances, and a full audit trail.
Part 4: Strategic Problems
Problem 11: No reporting or analytics
When employee records live in one file, attendance in a device and payroll in Excel, basic questions become projects. What is labour cost per project? What was turnover over six months? How large is the current end-of-service liability? The ERP fix: reports from one database, covering payroll cost by department, project and nationality, turnover and its reasons, leave balances and provisions.
Problem 12: Disconnected from government platforms
Companies deal with Mudad for wage protection, GOSI, Qiwa for contracts and Nitaqat, and Muqeem for iqamas and visas. Any mismatch between internal data and these platforms generates notes or violations. The best-known example is an iqama that expires because nobody noticed the date.
The ERP fix: Muqeem integration for iqama and visa data, automatic alerts before documents expire, and WPS files generated from the payroll itself. See document expiry alerts.
A Ten-Point Self-Check
- Is overtime calculated with one written formula that everyone preparing payroll knows?
- Is the WPS file uploaded each month at least a week before the deadline?
- Is there an end-of-service provision updated monthly in the accounts?
- Does your system know which GOSI regime each Saudi employee is under?
- Do you know your current Nitaqat band and how your last five hires affected it?
- Are probation reviews done before probation ends?
- Are the three sick leave bands applied correctly within the year?
- Is attendance on outside sites recorded in a way that prevents buddy punching?
- Does clearance finish in days rather than weeks?
- Do you get iqama expiry alerts at least two months ahead?
Hypothetical Case: A 200-Person Contractor
A contractor has 200 employees across a head office and six sites, 50 of them Saudi. Payroll was built in Excel from paper timesheets sent weekly by site supervisors. A three-month internal review found:
- 14 Saudis who joined after July 2024 had contributions calculated at legacy rates.
- Overtime at two sites was paid at 150% of total wage; elsewhere it followed Article 107.
- There was no end-of-service provision, although 35 employees had more than five years' service.
- In one month the WPS file went up on day 27, uncomfortably close to the deadline.
None of this was catastrophic alone, but together it meant retroactive corrections, dispute risk and a large liability missing from the balance sheet. After consolidating into one system, GOSI rates follow each employee's classification, overtime uses one formula, attendance is captured on mobile inside each site's geo-fence and the provision posts monthly. Management also now sees true labour cost per project.
Before and After
| Area | Disconnected tools | Integrated ERP |
|---|---|---|
| Payroll preparation | Days of compiling and manual review | Calculated from attendance and leave, approved in stages |
| Overtime | Formula depends on who calculates | One approved formula |
| GOSI rates | A static table nobody updates | Rates by category with effective dates |
| End of service | Calculated only at exit | Monthly provision and automatic exit calculation |
| Leave | Balances in a spreadsheet, paper requests | Live balances, electronic requests |
| Documents | Expiry discovered afterwards | Advance alerts |
Implementation Roadmap
- Clean master data: employee records, joining dates, wage components as per contracts, bank accounts and GOSI regime for every Saudi.
- Pay structure and policies: allowances and their properties, overtime formulas, leave types, approval chains.
- Attendance: devices or mobile app, shifts, geo-fences for sites.
- Parallel run: one or two payrolls in both systems, every difference explained before relying on the new one.
- Self-service and reporting: launch employee self-service and build management reports.
For a detailed look at end-of-service and leave rules, read our article on end of service and leave under the Labour Law.
How Tranquil Helps
Tranquil includes employee management, time and attendance, scheduling and timesheets, payroll, employee self-service, document expiry alerts, geo-fencing, bank integration for direct salary transfer and Muqeem integration for iqamas and visas, all linked to financial accounting in one cloud system. See payroll management.
Frequently Asked Questions
How is an overtime hour calculated in Saudi Arabia?
Article 107 sets it at the hourly wage plus 50% of the basic wage for each overtime hour. With the worker's consent, paid compensatory leave can replace overtime pay.
What is the WPS upload deadline?
30 days since 1 March 2025, down from 60.
Do GOSI rates differ between Saudi employees?
Yes. Those registered before 3 July 2024 keep the previous rates, while new entrants with no prior contributions see the annuity rate rise each July from 9% to 11% per side by July 2028.
How long can probation be after the amendments?
Up to 180 days, and it must be stated in the employment contract.
Where should we start if payroll problems are widespread?
Clean wage data and GOSI classifications first, then standardise overtime and leave rules. To discuss your situation, contact the Tranquil team.