How to Calculate Annual Leave in Saudi Arabia

Annual leave is one of the most frequently repeated calculations in any HR department, and one of the least forgiving. Get it wrong and you have either short-changed an employee or exposed the company to a claim — and in both cases you usually find out late, when a balance is queried or a final settlement is disputed.

For an HR leader, managing entitlements is not purely a legal obligation. It is one of the clearest signals a company sends about whether it is well run. Leave is the entitlement employees track most closely, because it is the one they personally plan their lives around, so errors here are noticed faster and remembered longer than errors almost anywhere else in HR.

This guide covers the statutory basis for annual leave in Saudi Arabia, how to turn an entitlement into a monetary value, and how to handle the cases that cause the most trouble: employees crossing the five-year mark, and leave still unused when someone leaves. It ends with what changes when the calculation is automated rather than maintained by hand.

1. The statutory entitlement

Before any arithmetic, the ground needs to be firm. The Saudi Labour Law treats annual leave as a defined right rather than a matter for negotiation, and sets its terms clearly enough to leave little room for interpretation. Article 109 is the reference point:

Two thresholds follow from this:

• 21 days per year for every employee.
• 30 days per year once an employee completes five consecutive years with the same employer.

Note the wording: not less than. These are floors, not fixed values. A company that offers more is free to do so, and once that offer is in the contract it becomes the entitlement you are obliged to honour and to calculate against.

The word consecutive also carries weight. The thirty-day entitlement attaches to continuous service with the same employer, so a break in service generally restarts that clock. For companies that rehire former employees — common in seasonal and project-based sectors — this is worth confirming case by case rather than assuming.

The same article states that leave must be taken in the year it accrues, and that an employee may not waive it or accept cash instead while still employed. That point is regularly misunderstood in both directions. An employee cannot ask to be paid out for leave they would rather not take, and an employer cannot offer payment as an alternative to releasing them.

The operational consequence is that a growing untaken balance is not a saving. It is an accumulating liability that gets settled eventually — either as time away from work you have to cover, or as cash when the employee leaves, calculated at whatever their wage is then rather than what it was when the leave accrued. A balance drifting upward across a department is a warning, not a convenience.

2. Valuing a day of leave

Leave is paid at the actual wage, which Article 2 defines as the basic wage plus all other due increases payable to the worker under the contract or the work regulations. In practice that normally means basic salary plus housing and any other fixed, contractual allowance.

A worked example. Salem's package:

• Basic salary: SAR 9,000
• Housing allowance: SAR 2,250 (25% of basic)
• Monthly actual wage: SAR 11,250

Case A — Salem has not completed five years (21 days)

• Daily rate: 11,250 ÷ 30 = SAR 375
• Leave value: 375 × 21 = SAR 7,875

Case B — Salem has completed five consecutive years (30 days)

• Leave value: 375 × 30 = SAR 11,250 — exactly one month's actual wage

Note what the five-year mark does: it raises the annual cost of that one employee's leave by SAR 3,375 without any change to their salary. If you hired a cohort around the same time — which most growing companies do — that step arrives for all of them at once, and it is far better forecast than discovered in a month's payroll.

Two details cause most disputes in practice. The first is which allowances belong in the actual wage: fixed contractual allowances count, while genuinely variable payments generally do not, and that distinction should be settled in the employment contract rather than argued at the point of calculation.

The second is the divisor. A month is treated as 30 days for this purpose regardless of its actual length, which is why the daily rate above is the monthly wage divided by 30 and not by the number of days in the particular month. Using the calendar length instead produces a different answer in eleven months of the year, and it is a common source of small, persistent discrepancies that employees eventually notice.

3. Balances, scheduling and pro-rated leave

Calculating the entitlement is the easy half. The work is in tracking what each employee has left, scheduling it so the business still functions, and handling the case where someone leaves part-way through a year.

Article 111 covers that last case:

The pro-rated calculation is:

So an employee who served 200 days of a year carrying a 21-day entitlement is owed (21 ÷ 365) × 200 ≈ 11.5 days, paid at their actual wage. The same employee past five years, on 30 days, is owed roughly 16.4 days. The difference between those two figures is precisely why service length has to be accurate in your records rather than approximated.

Doing this by hand for every employee, on every request and every final settlement, is where errors enter — and leave errors are visible ones. Employees check their balances, they compare them with colleagues, and a discrepancy that would pass unnoticed elsewhere in payroll gets raised within days.

There is also a scheduling dimension no formula covers. Leave must be taken in the year it accrues, but it also has to be taken without leaving a team unable to operate. That requires knowing in advance where balances are concentrated — a reporting problem rather than an arithmetic one, and the part most often left until someone requests three weeks in December.

How Ektefa handles it

Time spent recalculating entitlements is time not spent on the parts of HR that actually need judgement. Ektefa calculates each employee's entitlement from their hire date and years of service, and keeps balances current rather than reconstructing them when someone asks:

• Automatic accrual. Entitlement moves from 21 to 30 days on the five-year anniversary without anyone remembering to change it, and leave value is computed from the actual wage on record — so a salary change is reflected in the next calculation rather than requiring a manual revision.
• Built to the statute. The accrual and pro-rating rules follow Articles 109 and 111, including final-settlement calculations, so the answer does not depend on who in the team ran it.
• One place to manage it. Employees request leave through self-service and see their own balance; managers approve; the balance updates itself. Reports cover the whole workforce, which is what makes it possible to see a scheduling problem before it becomes one.

The point is not that the arithmetic is difficult. It is that doing it consistently, for everyone, every month, without drift, is exactly the kind of work software should absorb — and that the visible reliability of leave balances does more for how an HR department is regarded than most of the work that gets more attention.

Annual leave calculation is, in the end, a reflection of how seriously a company treats its obligations. Combining a clear reading of the Labour Law with a system that applies it the same way every time turns a recurring administrative risk into something you no longer have to think about.