GCC Payroll, WPS & Gratuity

Human Resources in Dynamics 365 Finance & Operations handles workers, positions, jobs, compensation plans and leave enrolment well. What it does not handle is Gulf payroll. The payroll functionality that ships in the product targets the United States, and there is no Gulf localisation to switch on. So groups running legal entities in the UAE, Saudi Arabia, Qatar, Oman, Bahrain or Kuwait end up with the organisational structure in F&O and the actual pay run somewhere else - a spreadsheet, a standalone payroll package, or an outsourced provider - and then re-import a summary journal every month.

That split costs more than it looks. Headcount and position changes are entered twice. Cost centre and project dimensions on payroll cost are approximations, because the external system does not know your ledger dimension structure. End-of-service gratuity is accrued once a year on a spreadsheet rather than provisioned monthly, so the liability on the balance sheet is wrong for eleven months out of twelve. Wage Protection System files are assembled by hand, and a single malformed record gets the whole batch rejected by the bank. And nobody in the business can produce an Arabic payslip that satisfies a labour inspection without retyping it.

What ECOSIRE builds

A Gulf payroll module written in X++ as an extension, sitting directly on the Human Resources data already in your environment - HcmWorker, employment records, positions, compensation plans and leave enrolments. No parallel employee master, no synchronisation job between two versions of the truth.

Pay elements and the calculation engine

Earnings, allowances and deductions are configured as pay elements with a calculation type: fixed amount, percentage of basic, formula across other elements, or attendance-driven. Each element carries its own ledger posting setup and its own treatment for gratuity, social insurance and overtime bases, because in Gulf payroll the question is rarely how much an allowance is and almost always which bases it belongs to. Pay cycles and periods are defined per legal entity. The calculation itself runs in the SysOperation batch framework, so a multi-thousand-employee run is a batch job with a progress log and a re-runnable result set, not a foreground process that times out.

WPS and bank files

Wage Protection System files are generated through Electronic reporting, which means the layout is a configuration you can see and version rather than hard-coded string building. We implement the salary information file for the countries in your scope - the UAE fixed-width SIF, the Saudi format for the mandated wage protection channel, and the Qatar, Oman or Bahrain equivalents as required - to the specification published by the relevant central bank or labour authority, then validate the output against your own bank test facility before go-live. Employee payment files use the same Electronic reporting mechanism, so a change in bank format is a format update rather than a code change. ECOSIRE is not a certified payroll provider in any GCC country and does not file anything on your behalf; we build the files, you submit them.

End-of-service gratuity and provisions

Gratuity is calculated per the labour law of each country and per contract type - unlimited or limited term, resignation or termination, the service-year bands that change the accrual rate, and the eligible salary base as your legal advisor defines it. A monthly provision batch posts the movement to the general ledger with the right ledger dimensions, so the liability is current every month rather than an annual surprise. Final settlement pulls gratuity, unused leave, notice pay and outstanding loan balances into one settlement statement that the employee signs and the ledger posts.

Social insurance and statutory deductions

Contribution rules are configured per country and per nationality band - GOSI in Saudi Arabia with the split between Saudi nationals and expatriates, GPSSA in the UAE, PASI in Oman, the Bahraini and Qatari schemes - each with its own contributory base, ceiling, employer share and employee share. Contribution registers export in the layout each authority expects, again through Electronic reporting.

Arabic payslips and self service

Payslips render bilingually, Arabic and English, with correct right-to-left layout and Arabic labels, produced as an SSRS report or an Electronic reporting document depending on how you need to archive them. Employees see their own payslips in the Employee self service workspace, and where you want a phone-first experience we publish the same data through dual-write to a Power Apps canvas app.

Leave, air tickets and loans

Annual leave accrues against the F&O leave and absence setup with Gulf-specific rules: accrual during unpaid leave, leave salary paid in advance of departure, and encashment on settlement. Air-ticket entitlement accrues monthly per grade and family size, with a provision journal and a drawdown when the ticket is actually taken. Employee loans and salary advances are recorded with a deduction schedule that the payroll run honours automatically and that stops at the outstanding balance on final settlement.

Posting and multi-entity operation

Payroll results post as a general journal or as employee vendor invoices, whichever your finance team prefers, with ledger dimensions derived from the position, department, cost centre or project the worker is assigned to. Payroll runs are approved through the F&O workflow framework before posting. Groups run each legal entity on its own cycle and consolidate through standard cross-company reporting.

Who it is for

Groups with employees in one or more GCC countries already running Dynamics 365 Finance & Operations for finance, that are currently paying people out of a separate system and re-importing journals. It suits payroll managers, HR directors and financial controllers who want one employee record and a defensible monthly liability.

How delivery works

1. Scoping call. Which countries, how many legal entities, your bank or banks, contract types, allowance structure, current gratuity policy and who signs off the interpretation of it. 2. Fixed quote. Written scope, fixed price, lead time - typically two to four weeks, longer where several countries and banks are in scope. 3. Build. X++ extension plus Electronic reporting configurations, developed against a copy of your HR setup. 4. Install in test. Deployable package into your sandbox through LCS. You run a parallel payroll for at least one full cycle against your existing system and reconcile the difference line by line. 5. Production. Deployment in your change window, with the first live run supervised. 6. Support. A defect-correction window covering at least the first production cycles, plus a written handover.

What is out of scope

We do not provide legal or tax advice. Gratuity formulas, eligible salary bases and contribution rules are implemented exactly as your legal or HR advisor specifies them in writing, and that specification is part of the signed scope. Bank onboarding, authority registration and filing remain yours.