Ask any payroll officer in the UAE what keeps them up at night, and sick leave calculations will rank somewhere near the top. The entitlement structure looks simple on paper — full pay, half pay, unpaid — but in practice, the interaction between leave tiers, daily salary methods, and end-of-service gratuity creates a web of calculations that most companies still manage in spreadsheets. Odoo’s UAE payroll localization now addresses this head-on with a formula-driven engine that handles all three tiers natively and lets companies choose exactly how daily salary rates are determined.
The Three-Tier Sick Leave Structure
UAE labor law under Federal Decree-Law No. 33 of 2021 establishes a stepped sick leave entitlement that applies once an employee completes their probation period. The structure is straightforward in theory but notoriously fiddly in execution:
The first tier grants 15 calendar daysat full pay. This is the employee’s baseline entitlement, and it resets annually. Once those 15 days are exhausted, the second tier kicks in: 30 additional calendar days at half pay. The daily payment drops to 50% of the calculated daily salary, and this is where most manual calculations start to drift, because payroll officers need to track exactly which threshold was crossed and on which date. Beyond that, the third tier provides up to 45 calendar days of unpaid leave. The employee retains their position, but no salary is disbursed.
Odoo applies a single formula across all three tiers: (Number of Leave Days × Gross Per Month ÷ 30) × Percentage. The percentage variable is what changes — 100% for tier one, 50% for tier two, and 0% for tier three. The system tracks cumulative days automatically, so when an employee crosses from full pay to half pay mid-absence, the payslip splits the calculation accordingly. No manual adjustment, no override required.
Two Ways to Calculate the Daily Salary
The daily salary figure that feeds into the sick leave formula isn’t always the same number, and this is where Odoo gives payroll teams a choice. The default method divides the employee’s monthly basic wage by 30 — a standard approach that works for most salaried positions and aligns with how MOHRE expects WPS data to be structured.
But not every employment arrangement fits that mold. Commission-heavy roles, part-time contracts, and employees with variable compensation components often need a different daily rate. For these cases, Odoo provides a Daily Salary checkbox on the employee contract form. When enabled, the system bypasses the automatic division and instead uses a manually entered daily salary figure. This manual rate then flows through to sick leave calculations, end-of-service gratuity computations, and any other payroll rule that references the daily wage.
The distinction matters more than it might seem. If a company calculates EOSG using the wrong daily rate, the error compounds over years of service. By making the calculation method explicit and configurable at the contract level, Odoo eliminates the ambiguity that previously required payroll teams to maintain parallel tracking in spreadsheets.
Where Daily Salary Meets End-of-Service Gratuity
The daily salary setting doesn’t just affect sick leave. It feeds directly into the end-of-service gratuity calculation, where the stakes are considerably higher. Under UAE labor law, gratuity accrues at 21 days of basic salary per year for the first five years, then 30 days per year thereafter, capped at two years’ gross salary.
When the daily salary checkbox is left unchecked, the system calculates the gratuity using the standard monthly-divided-by-30 figure. When it’s checked and a manual rate is entered, that manual rate becomes the basis for gratuity computation. This means a single checkbox can shift an employee’s end-of-service payout by thousands of dirhams over a multi-year tenure. Getting it right at contract setup, rather than discovering the discrepancy at termination, saves both money and legal headaches.
The WPS Reporting Connection
None of these calculations exist in isolation. Every payslip that processes sick leave flows into the Wage Protection System report that employers submit to MOHRE-approved banks. The SIF file generated by Odoo includes Employee Detail Records, Variable Pay Records, and Salary Control Records — and the sick leave calculations feed the variable pay component directly.
For companies that have previously submitted SIF files with manually calculated sick leave amounts, the shift to formula-driven calculations within Odoo means the numbers in the WPS submission now match the payslip records exactly. Discrepancies between internal payroll records and WPS submissions are one of the most common triggers for MOHRE compliance inquiries, and eliminating that gap is worth more than the time saved on the calculation itself.
Configuring the System Correctly
The setup process centers on two decisions. First, does the company use the standard daily salary calculation (monthly basic ÷ 30) or manual entry? This is set per employee contract, not globally, which accommodates organizations with mixed employment types. Second, are the sick leave rules configured in the time-off module to map correctly to the three-tier structure? Odoo’s UAE localization pre-configures these tiers, but companies that have customized their leave types need to verify that the percentage assignments match the legal requirements.
The employer ID and bank account details for WPS reporting should already be configured under Payroll → Configuration → Settings. Employee identification numbers need to be set on each employee record. Once these are in place, generating a WPS-compliant SIF file that includes the correct sick leave amounts is a single export operation.
Why This Matters Now
MOHRE has been tightening enforcement of WPS compliance consistently over the past two years. Companies that were previously able to submit corrected files after the fact are finding less latitude for errors. The combination of automatic tier tracking, formula-driven daily salary calculation, and integrated WPS export means payroll teams can submit accurate data the first time — which, increasingly, is the only time that counts.