Saudi Arabia Overtime Rules in 2026: A Practical Guide
How overtime is calculated, where teams most often get it wrong, and how to make the rule enforce itself.
Overtime is one of the few areas of payroll where a small configuration error compounds every single month, across every affected employee, until somebody audits it. In Saudi Arabia it is also an area where the rule itself is relatively simple and the implementation is where things go wrong.
This guide covers the structure of the rule, the five places teams most often miscalculate, and how to configure a system so the policy enforces itself rather than depending on whoever is preparing the payroll that month.
Verify the current figures before you configure
This article explains structure and common failure modes. It is not legal advice, and rates, thresholds and exemptions are amended from time to time. Confirm every number against the current text of the Saudi Labor Law and prevailing MHRSD guidance, and take local counsel before changing how anyone is paid.
The baseline: what counts as normal hours
Everything about overtime depends on where normal hours end, so that boundary has to be right before anything else can be. The Labor Law sets a standard working day and a standard working week, with a reduced schedule applying during Ramadan for Muslim employees.
Two structural points matter more than the numbers themselves:
- The daily and weekly limits are separate tests. An employee can breach the weekly threshold without breaching any daily one. A system that only evaluates days will under-pay; one that only evaluates weeks will misstate which days were premium.
- Certain arrangements allow averaging across a longer period, which changes when the threshold is considered crossed. If you operate this way, it has to be configured deliberately — it is not the default behaviour of most systems.
How the premium is calculated
Overtime in Saudi Arabia is paid at a premium on the employee's wage for the additional hours. The mechanically important question is not the percentage — that is easy to look up and easy to enter — but what the percentage is applied to.
This is the single most common source of error. The base used for the overtime calculation is not always the same base used for other calculations in your payroll, and organisations frequently discover they have been applying a premium to basic salary alone when the applicable base is broader.
Before configuring anything, get a documented, counsel-confirmed answer to three questions:
- Which earnings components form the base for the overtime rate?
- How is the hourly rate derived from a monthly salary — what divisor is used?
- Does that divisor change during Ramadan or in months with a different number of working days?
Write the answers down. They will be the thing an auditor asks about, and they are the thing that gets lost when the person who configured the system leaves.
Rest days and public holidays
Work performed on a weekly rest day or a public holiday is treated differently from ordinary weekday overtime, and the treatment is not simply “overtime rate applied to more hours”. Depending on the arrangement, compensation may involve premium pay, a compensatory rest day, or both.
The practical implication for system design is that your calendar has to be correct. A rules engine cannot classify a day it does not know about, so public holidays — including ones announced at short notice — need to be maintained in the system, not in somebody's head.
Five places teams get it wrong
1. Ramadan hours are not applied automatically
The reduced Ramadan schedule shifts the overtime threshold for the affected employees. If the system keeps the standard threshold, hours that should attract a premium are paid as ordinary time for the whole month. This is the most frequently reported error, and it recurs annually because it is fixed manually each year rather than configured.
2. The eligible population is defined too broadly
Not every role is treated identically under the law. Applying a single blanket overtime rule to all employees is simpler to configure and is very likely wrong in at least one direction. Categories need to be defined explicitly and reviewed when job structures change.
3. Overtime is claimed rather than measured
Where overtime is self-declared on a form, the figure reflects what people remembered and submitted. Where it derives from actual clock-in and clock-out records, it reflects what happened. The gap between the two is usually material in both directions — some over-claiming, and a surprising amount of unclaimed time that becomes a liability later.
4. Approval happens after the fact
If overtime is only visible when payroll runs, the organisation has already incurred the cost and the conversation is about paying it, not about whether it should have happened. Pre-approval workflows move that decision to before the hours are worked.
5. Nobody reconciles the total
Overtime cost should be trended and reviewed monthly against budget and headcount. A team whose overtime is structurally elevated is usually understaffed, and paying a premium indefinitely is more expensive than hiring.
Making the rule enforce itself
The goal of configuration is that a correct result requires no judgement at month end. That means, concretely:
- Thresholds defined per employee category, with the Ramadan variant configured once and triggered by the calendar rather than by a person.
- Hours derived from actual attendance records, not from a submitted claim.
- Day types — working day, weekly rest, public holiday — resolved by the calendar, with holidays maintained centrally.
- Pre-approval required above a defined threshold, with the approval attached to the record.
- A direct feed into payroll, so no one re-keys a number between systems.
- An audit trail showing, for any given payment, which rule produced it and on what evidence.
If your month-end overtime figure depends on who prepared it, the rule is not configured. It is being remembered.
A short self-check
Take last month's payroll and pick three employees who were paid overtime. For each one, trace the payment back: which attendance records produced the hours, which threshold was applied, what base rate was used, and who approved it. If you can do that in a few minutes for all three, your configuration is probably sound. If it takes an afternoon and a spreadsheet, you have found your next project.
Applying rules like these to a live payroll is a job for software rather than a policy document; human capital management software holds the shift, the overtime rule and the resulting payment together.
