GCC Payroll and End-of-Service Benefits

The problem

SAP Business One does not ship payroll for the Gulf. Companies running it in the UAE, Saudi Arabia, Qatar, Oman, Bahrain or Kuwait typically end up with payroll in a spreadsheet or a disconnected local package, and then re-key the monthly journal into SAP B1 as a summarised manual Journal Entry. That works until one of four things happens.

The bank rejects the WPS file, because the salary information record has to match the establishment registration byte for byte — the wrong record count, a labour card number that changed, a salary period expressed in the wrong format, and the file bounces with a code that means nothing to a finance team.

An employee resigns after six years, and the end-of-service gratuity has to be computed from a legal formula that depends on length of service, reason for leaving, and which components of pay count as the base — and nobody has been accruing for it, so a large expense lands in one month.

The auditor asks for the accrued leave liability at year end, and the leave balances live in a different system from the salary rates, so the number is an estimate.

Someone asks what payroll actually cost by department or by cost centre last quarter, and the answer is one summarised journal line per month with no dimension detail.

What ECOSIRE builds

This is a build-to-order add-on. There is no ready-made download. We scope your countries, your pay components, your bank's WPS specification and your accrual policy, quote a fixed price, then build and install into your company database.

Employee master and contract data

Employees are extended with User-Defined Fields and User-Defined Tables covering nationality, labour card and personal identification numbers, establishment and bank routing details, contract type, joining date, probation end, visa and permit expiries, and the cost centre or dimension the salary posts to. Contract history is versioned in a UDT so a mid-year salary revision is a new effective-dated row, not an overwrite — which is what makes retroactive calculation and correct gratuity bases possible later.

Pay component engine

A User-Defined Object holds the pay component definitions: basic, housing, transport, other allowances, overtime rates, deductions, loans and advances. Each component is flagged for whether it enters the gratuity base, the leave-salary base, and the social insurance contribution base, because those three bases are legally different and are the single most common source of wrong numbers. Formulas are configuration, evaluated through the Service Layer, so an allowance policy change does not need a rebuild.

WPS salary file generation

We generate the Wage Protection System file to your bank's and your country's specification — the salary information record and employee detail records, correct fixed-width or delimited layout, correct establishment identifiers, correct period encoding. Before generation the extension validates the run: employees missing a labour card number, an IBAN that fails the check digit, a total that does not tie to the payroll journal. You get the exceptions before the bank does.

End-of-service gratuity and accrual

Gratuity is computed from the statutory formula for the relevant country: service length in completed years and days, the reason for separation, the applicable rate bands, and the correct base components resolved from the effective-dated contract history. Crucially, the add-on also accrues monthly, posting a Journal Entry to a gratuity provision account so the liability grows as it is earned rather than appearing in the month someone resigns. At separation the settlement document nets accrued provision against the final computation, adds leave encashment and notice pay, and posts the difference.

Leave, encashment and settlement

Leave entitlement accrues per your policy, tracked against each employee in a UDT with carry-forward and expiry rules. Leave salary and air ticket entitlements — where your contracts provide them — are accrued and settled. The accrued leave liability is reportable at any date, which is the number your auditor wants.

Social insurance and pension contributions

GCC social insurance schemes apply to nationals of the country and, under the unified extension rules, to GCC nationals working across member states at their home country's rates. The add-on resolves the applicable scheme and rate from the employee's nationality and work location, splits employer and employee portions, applies contribution ceilings, and produces the contribution schedule for filing.

Posting into SAP Business One

Every run posts a real Journal Entry — not a summary you re-key — with lines dimensioned by cost centre, department or project, so payroll cost analysis works in your existing financial reports. Net pay posts to the payable account cleared by the WPS payment, and each accrual to its own provision account. Payslips are Crystal Reports, distributable as PDF by email.

Who this is for

Employers running SAP Business One 10.0 in one or more GCC states, particularly mixed-nationality workforces where expatriate gratuity and national social insurance run side by side. It suits companies with WPS obligations that are currently produced by hand, and groups that need one payroll process across several Gulf entities posting into separate company databases.

Technical framing

Built as a SAP Business One extension on the Service Layer (REST) for calculation, validation and posting, with DI API where an object requires it. Employee, contract, component, leave and run data live in User-Defined Tables and User-Defined Objects; master extensions are UDFs. Payroll run approval uses SAP Business One approval procedures. Payslips and contribution schedules are Crystal Reports. Compatible with SAP Business One 10.0 on Microsoft SQL Server and SAP HANA, on-premise or cloud-hosted, delivered per tenant.

How delivery works

1. Scoping call. Countries in scope, headcount, pay components, your bank's exact WPS specification, gratuity and leave policy as written in your contracts, and your chart of accounts. 2. Fixed quote. Written scope and fixed price before any build begins. 3. Build. Typical lead time one working week; multi-country scope sits at the longer end. 4. Install into test. Installed into your test company database with your real employee data, then we run a parallel payroll against a month you have already paid and reconcile it line by line with you. 5. Production install. After parallel-run sign-off, install into production, load opening gratuity and leave balances, and go live on a live payroll cycle we attend. 6. Support. A support window follows go-live, covering defects and the first live WPS submissions.