GCC WPS Payroll and Gratuity Pack

The problem

Gulf payroll fails on file formats and on leaving employees. Wage Protection System submissions are not a single national standard in practice: the record layout, the delimiter, the header and trailer fields, the employee identifier and the file naming convention all vary by country and by the bank or exchange house you route salaries through. A finance team that switches banks, adds a second entity in another emirate, or opens an entity in another GCC country discovers that its carefully built salary export no longer validates, and finds out at the point of upload rather than in advance.

End-of-service gratuity is the other half. Accrual depends on service length bands, the wage definition used for the calculation, whether the contract is limited or unlimited under the applicable labour law, and how resignation is treated differently from termination. Free zones add their own employment rules. Social insurance layers on top: GOSI in Saudi Arabia distinguishes Saudi nationals from expatriates with different contribution components, GPSSA covers GCC nationals in the UAE, and other GCC states have their own schemes and ceilings. Meanwhile expatriate staff who make up the bulk of the headcount fall outside the national scheme entirely but still accrue gratuity.

Zoho Payroll and Zoho People hold the employment data needed to compute all of this. What is missing is the country and bank-specific layer that turns that data into a file a bank will accept and an accrual a group auditor will accept.

What ECOSIRE builds

ECOSIRE builds this layer inside your Zoho org. It is a build-to-order engagement, not a product you download. We scope your entities, countries, banks and free zones, quote a fixed price, then develop and install it into your environment.

Bank-format WPS file generation

WPS output is driven by a file-format definition held as data in Zoho Creator, not hard-coded. Each definition captures the record layout, field order, padding and delimiter rules, header and trailer composition, employee identifier field, amount formatting and file naming convention for one bank in one country. Deluge functions build the file from the approved pay run against the selected definition. Adding a second bank or a second country is a new format definition plus validation, not a rewrite. Pre-submission validation checks the file before it leaves Zoho: missing labour card or establishment identifiers, employees without a registered IBAN, amount and headcount totals that do not tie back to the pay run, and format-level field length violations.

Social insurance computation

Deluge functions compute contributions per country scheme and per nationality class, reading employee master data from Zoho People through the REST API. Saudi entities compute GOSI with the separate treatment of Saudi nationals and expatriate employees, applying the contributory wage definition and ceiling held in configuration. UAE entities compute GPSSA for eligible GCC nationals while correctly excluding expatriates from the scheme. Scheme parameters, ceilings and contribution splits are versioned configuration records with effective dates, so a rate revision does not retroactively change a prior period.

End-of-service gratuity accrual and settlement

A gratuity engine computes both the ongoing balance sheet accrual and the final settlement figure. Rules are configured per country, per contract type and per free zone where applicable: service length bands, the wage base used, treatment of resignation versus termination, unpaid leave adjustments and any cap. Monthly accrual postings flow to the correct Zoho Books organization and liability account through the Books API. On separation, the settlement calculation runs against the same rule set and produces a documented breakdown showing service period, wage base, band applied and any adjustments, so the number given to the employee can be explained line by line.

Multi-entity and multi-country structure

Entity records carry country, labour law regime, free zone designation, establishment identifiers, bank routing and the applicable social insurance scheme. Employees inherit rules from their employing entity rather than from a global setting, so one Zoho tenant can run a Dubai mainland entity, a free zone entity and a Riyadh entity with different WPS formats, different social insurance and different gratuity rules in the same pay cycle.

Automation and review

Zoho Flow schedules the recurring work: monthly gratuity accrual runs, WPS file generation after pay-run approval, reminders ahead of submission deadlines per entity, and alerts when an employee's document identifiers are missing or a scheme parameter version is expiring. A Sigma widget in Zoho People gives payroll a per-entity readiness screen before submission: employees in scope, validation exceptions blocking the file, social insurance totals and current gratuity liability.

Reporting for finance

Gratuity liability reporting breaks the accrual down by entity, nationality class and service band for group consolidation. Social insurance summaries reconcile the computed employer and employee contributions against what was posted to Zoho Books for the period, so payroll and accounting agree before month-end close.

Who this is for

GCC employers running payroll on Zoho across more than one entity, country or free zone; companies routing salaries through more than one bank; groups that need a defensible gratuity liability figure for consolidation; and finance teams whose current WPS export is a spreadsheet macro maintained by one person. It also fits shared-service teams administering several GCC entities in one Zoho tenant.

How delivery works

Scoping call. We map your entities, countries, free zones, banks, nationality mix and current WPS and gratuity process, and review your live Zoho People and Zoho Payroll configuration. We ask for a sample of a currently accepted WPS file per bank, because the accepted file is the specification.

Fixed quote. You receive a written scope listing every bank format, country scheme and gratuity rule set included, with a fixed price. Additional formats or countries are quoted separately before work starts.

Build. We develop the format definitions, Deluge computation functions, Creator configuration, Flow automations and widget. Typical lead time is two to four weeks depending on the number of banks, countries and entities in scope.

Install in test. We install into your sandbox or test org, run a real pay period, and validate generated WPS files against your bank's specification and against a file the bank has already accepted. Gratuity accruals are compared to your existing schedule employee by employee. You sign off before production.

Install in production. We deploy to your production org, configure entities, formats and scheme parameters with your team, and run the first live submission cycle alongside you.

Support. A defined support window covers defect fixes and configuration help. Scheme rates and gratuity parameters are configuration your team maintains; a new bank format or a new country is a scoped addition.

ECOSIRE is not certified by or partnered with Zoho Corporation, any bank, or any government authority. This is custom development on Zoho's documented extensibility surfaces: Deluge, the Zoho REST APIs, Zoho Creator, Zoho Flow and Sigma widgets.