Overtime Under UAE Labour Law: Rules, Rates and Ramadan

If we were asked to name the single payroll component most likely to be configured incorrectly in a UAE organisation, it would be overtime. It is not because employers are careless, and it is not because the legislation is obscure. It is because overtime sits at the intersection of three separate decisions, each of which is often made by a different person at a different time, and rarely written down together.

The three decisions are: what counts as overtime, what salary base the premium is calculated on, and what limits apply. Get any one of them wrong and every affected payslip is wrong, month after month, until somebody reconciles. Because overtime is variable, the error hides well. A fixed allowance keyed incorrectly is noticed within a cycle; an overtime rate applied to the wrong base can persist for years.

The framework: standard working hours

UAE Federal Decree-Law 33/2021 on the Regulation of Employment Relations sets the baseline. Standard working time is eight hours a day or forty-eight hours a week for most private-sector employees, with certain sectors and roles subject to different arrangements by ministerial decision.

Two points matter for configuration. First, the daily and weekly limits operate together, so an employee working nine hours on four days and four hours on the fifth has exceeded the daily standard on four occasions even though the weekly total is within range. How your policy treats that is a decision you need to make explicitly.

Second, time spent on-call or travelling between sites may or may not count as working time depending on the arrangement, and this is a common source of dispute in facilities management, logistics, and construction. Whatever position you take, document it in the employment contract rather than leaving it to custom.

Overtime premium rates

The law provides for a premium above the normal hourly rate when an employee works beyond standard hours. The baseline premium is twenty-five per cent above the normal hourly wage. Where overtime falls between ten in the evening and four in the morning, the premium increases to fifty per cent, reflecting the additional burden of night work.

Work performed on a designated rest day attracts different treatment again: the employee is entitled either to a substitute rest day or to a premium of fifty per cent above the normal wage. Note that this is an entitlement structure rather than an employer choice to be made after the fact, so the policy needs to state which applies and the employee needs to know.

The night-work provision is the one most often missed in configuration. A system that applies a flat twenty-five per cent premium to all overtime will systematically underpay anyone working evening or night shifts, which in practice means security, hospitality, healthcare, and logistics staff. Those are the populations least likely to challenge a payslip and most likely to be affected.

The salary base: where most errors originate

This is the heart of the problem. The premium is a percentage, so the amount depends entirely on the figure it is applied to, and organisations are inconsistent about what that figure is.

The statutory reference point is the employee's wage as defined in the law, and the practical question is which components of a typical GCC salary package are included. A UAE package commonly comprises basic salary plus housing, transport, and other allowances. Whether overtime is computed on basic alone or on a broader base materially changes the cost, often by a factor of two or more, because basic salary in the region is frequently around half of the total package.

Three positions exist in practice. Some employers calculate on basic salary only. Others calculate on basic plus specified allowances. Others calculate on total gross. Each has implications for both cost and compliance risk, and the position taken should be consistent with the contract and the applicable legal definition rather than with whatever the previous payroll administrator configured.

The important operational point is that this decision must be documented, reflected identically in contracts and in the payroll system, and applied consistently across the workforce. Where we find variance, it is usually because a policy changed at some point and existing employees were never migrated to the new basis. Two employees doing the same job on the same salary receiving different overtime rates is a dispute waiting to happen, and it is visible in any payroll audit.

Daily and periodic caps

The law limits overtime. Total working time including overtime is capped, and there are limits on how much overtime may be worked in a given day, with further constraints on consecutive days of extended work.

Caps have a compliance function and an operational one. In compliance terms, exceeding them is a breach regardless of whether the employee consented or was paid correctly. Operationally, an employee consistently at the cap is a scheduling problem, and it is usually cheaper to fix the roster than to keep paying premium hours.

A well-configured payroll system enforces caps at entry rather than reporting them afterwards. If a timesheet submission would breach the daily limit, the approval should stop and require explicit override with a reason recorded. Detecting the breach after payment has been made leaves you with an exposure you cannot unwind.

Ramadan and reduced hours

During Ramadan, working hours are reduced under the law, with the standard working day shortened by two hours. This applies as a general reduction in the private sector rather than being limited to fasting employees, which is a point of frequent confusion.

The payroll consequence is that the overtime threshold moves. If the standard day becomes six hours, then a seven-hour day during Ramadan generates an hour of overtime that would not have been overtime a month earlier. Systems that hold the eight-hour threshold as a constant will silently under-record overtime for the entire month.

There is a second-order effect on the hourly rate itself. If the monthly salary is unchanged while contracted hours reduce, the derived hourly rate rises, and the overtime premium rises with it. Whether that outcome is intended is a policy question, but it should be a decision rather than an accident of configuration.

Practically, this means Ramadan needs to be a configurable calendar event in the payroll system that adjusts thresholds automatically for the period, not a manual instruction someone remembers to issue. It occurs annually on a moving date, which makes it exactly the kind of task that gets missed in a year when the payroll lead is on leave.

Timesheet capture is the weak link

Even with correct rates and caps, overtime accuracy depends on the underlying hours being captured reliably. In our experience this is where the practical error rate is highest, particularly for site-based and shift workforces.

The failure patterns are consistent. Hours are recorded on paper and consolidated manually into a spreadsheet at month end, by which time nobody can verify a disputed entry. Approvals happen after the fact and become a formality. Biometric or app-based clock data exists but is not connected to payroll, so someone re-keys it. And overtime is approved by a supervisor with an incentive to complete the job rather than to control cost.

The fix is structural: capture at source, approve within the cycle, and feed payroll directly with no re-keying. Where clock-in happens through an employee self-service app with location verification, the data arrives already attributed and time-stamped, and the approval sits with the manager in the same system.

Configuring overtime properly: a checklist

If you are reviewing your own configuration, these are the specific items to verify:

• Standard daily and weekly hours defined per employee category, not globally
• Salary base for overtime documented, consistent with contracts, and applied uniformly
• Standard premium and the higher night-work premium both configured, with the correct time window
• Rest-day work handled per policy, whether by substitute day or premium
• Daily and periodic caps enforced at approval rather than reported afterwards
• Ramadan reduced hours applied automatically as a calendar event
• Timesheet data flowing from capture to payroll without manual re-entry
• Overtime visible as a separate line on the payslip, with hours and rate shown

That last item is worth emphasising. Transparent overtime reporting on the payslip prevents a substantial share of payroll queries, because the employee can verify the calculation themselves. It also surfaces configuration errors quickly, since employees who work the hours are usually the first to notice when the arithmetic is wrong.

Overtime as a management signal

Beyond compliance, overtime data is one of the more useful operational signals an HR platform holds. Sustained high overtime in one department is rarely a scheduling anomaly; it usually indicates understaffing, a skills gap, or a process problem upstream.

It is also a leading indicator for attrition. Employees carrying persistent overtime burn out, and predictive models weight it heavily for exactly that reason, as we discuss in predictive attrition versus the annual survey. Reviewing overtime by department monthly, alongside headcount and absence, converts a payroll cost line into a workforce planning input.

If you want a review of how overtime is currently configured in your payroll, our team can look at it with you. In most reviews we find at least one of the eight checklist items above is not set correctly, and the night-premium window is the most common.