Running payroll in the UAE means navigating a compensation landscape that looks nothing like most other markets. There is no personal income tax, but there are mandatory end-of-service gratuity calculations, Wage Protection System requirements, and a growing web of nationalization mandates. On top of that, many UAE-based employers provide benefits that are uncommon elsewhere — annual plane tickets for expatriate employees being one of the most widespread. Odoo’s 19.3 release addresses three distinct gaps in its UAE payroll localization, each targeting a different pain point that HR teams in the Emirates deal with regularly.
Plane Ticket Allowances: From Informal Tracking to Contract-Level Configuration
For most private-sector employers in the UAE, providing annual return airfare to an employee’s home country is a standard contractual obligation. The specifics vary — some companies offer one ticket per year, others provide tickets for the employee’s entire family, and the allowance amount depends on the class of travel and destination. Despite how common this benefit is, payroll systems have historically treated it as a manual add-on rather than a first-class payroll component.
Odoo 19.3 changes that by building plane ticket allowances directly into the employee contract. Under the Payroll tab of the contract form, payroll administrators can now set a per-ticket monetary value that reflects the company’s airfare policy. This value becomes part of the contract’s compensation structure rather than floating as an untracked side benefit.
When it comes time to actually process the allowance, the workflow lives in the Salary Inputs section of the payslip. The payroll officer enters the number of tickets being claimed during that pay period, and the system multiplies the quantity by the per-ticket value defined in the contract. This two-step approach — configuration at the contract level, application at the payslip level — keeps the process clean. The contract defines what an employee is entitled to, while the payslip captures what is actually being disbursed in a given period.
The design also handles the reality that ticket allowances are not always paid out monthly. Some employees claim their tickets once a year during a home leave period. Others receive a monthly pro-rated amount. By separating the per-ticket value from the timing of disbursement, the system accommodates both patterns without requiring different configuration approaches.
Employer Other Costs: Tracking What Doesn’t Appear on the Payslip
Every expatriate employee in the UAE comes with a set of employer-borne costs that never show up on a payslip but significantly affect the true cost of employment. Medical insurance is mandatory across all emirates. Work permits and employment visas require periodic renewal fees. Some companies carry additional costs for dependent visas, Emirates ID processing, and occupational health screenings. These expenses are real, recurring, and often substantial — yet most payroll systems ignore them entirely because they fall outside the traditional salary-to-net-pay calculation.
The new Employer Other Costs section in Odoo addresses this by creating a dedicated space within the employee record to capture these additional expenses. Payroll administrators enter yearly values for medical insurance premiums, work permit fees, employment visa costs, and any other employer-side expenses relevant to that employee. The system then calculates the monthly equivalent automatically, giving finance teams an accurate picture of the total monthly cost of each employee.
The critical design decision here is that these costs are strictly employer-side. They do not affect the employee’s gross pay, net pay, or any deduction lines. They do not appear on employee-facing payslip documents. They exist purely as an internal cost tracking mechanism that feeds into management reporting and budgeting. This distinction matters because mixing employer costs into the payslip calculation would create confusion for employees and potentially trigger compliance questions about undisclosed deductions.
For companies with large expatriate workforces — which describes the majority of private-sector employers in the UAE — this feature turns what was previously a spreadsheet exercise into a system-managed process. Instead of maintaining a separate tracker for insurance and visa costs alongside the payroll system, everything lives in one place with consistent monthly calculations.
Emiratisation Compliance Report: Measuring What the Government Mandates
Emiratisation — the UAE government’s policy requiring private-sector companies to employ a minimum percentage of Emirati nationals — has moved from a soft encouragement to an enforced mandate with financial penalties. Companies that fall below the required thresholds face fines that increase with each non-compliant period. Tracking compliance manually is tedious and error-prone, especially for organizations with hundreds or thousands of employees spread across multiple entities.
Odoo 19.3 introduces an Emiratisation Compliance Report that calculates the percentage of Emirati employees within the workforce automatically. The report follows the methodology defined by the Ministry of Human Resources and Emiratisation (MoHRE), which specifies that only employees in positions with skill levels of 5 or below count toward the compliance calculation. Employees at skill level 6 and above are excluded from the denominator entirely. This distinction is important because it prevents companies from inflating their compliance numbers by hiring Emirati nationals into senior positions that are already excluded from the mandate’s scope.
Getting accurate numbers from the report requires three pieces of configuration to be in place. First, Emirati employees must have their nationality correctly set in their employee records. Second, every employee needs a properly assigned job position. Third, each job position must have its skill level configured according to the MoHRE classification system. When all three elements are set up correctly, the report produces a compliance percentage that mirrors what the ministry calculates during inspections.
The report also tracks Emirati employee growth over time, which is significant because MoHRE does not just look at the current snapshot — it evaluates whether companies are making progress toward their targets. A company that is below the threshold but showing consistent quarter-over-quarter improvement faces a different regulatory conversation than one whose numbers are stagnant or declining. Having this trend data inside the payroll system eliminates the need to reconstruct historical headcount figures from scattered records when an audit occurs.
What This Means for UAE Payroll Operations
These three features address fundamentally different aspects of UAE payroll management, but they share a common theme: bringing into the system things that previously lived outside it. Plane ticket allowances were tracked in contracts but processed manually. Employer costs were maintained in spreadsheets. Emiratisation compliance was calculated by hand or through standalone tools. Each of these workarounds introduced opportunities for errors and created information silos that made it harder to get a complete picture of workforce costs and compliance status.
The employer cost tracking and Emiratisation report are particularly relevant for companies operating across multiple emirates or managing large expatriate workforces. When these data points live inside the payroll system alongside salary calculations and WPS reporting, the total cost of employment becomes visible without needing to reconcile multiple data sources. For HR directors preparing workforce budgets or responding to MoHRE compliance inquiries, having everything in one system is the difference between a quick report pull and a multi-day data gathering exercise.