GCC Payroll with Gratuity & WPS Files

Why Gulf payroll never fits a generic payroll module

NetSuite's standard payroll capabilities were not built for GCC labour law, and the gap is not cosmetic — it is arithmetic and it is legally binding.

End-of-service gratuity is the clearest example. It accrues per employee against basic salary, at rates that step by completed service years, with different treatment depending on whether the employee resigns or is terminated, and with unpaid-leave periods excluded from service. It has to sit on the balance sheet as a provision that moves every month, and it has to be recalculated the moment a basic salary changes. A spreadsheet maintained by one person in HR is the norm, and it is also the single most common audit finding in a Gulf ERP review.

Wage Protection System files are the second wall. Salaries must be filed electronically in a fixed-width or delimited layout that differs by country and, in practice, by bank. The record structure, header and trailer totals, employee identifiers (labour card, work permit, national ID, IBAN), salary breakdown fields and date formats are prescribed. One character out of position and the bank rejects the whole file, usually the day before payday.

Then there are the layers on top: GOSI contributions in Saudi Arabia with different rates for Saudi nationals and expatriates; GPSSA and equivalent pension schemes elsewhere in the Gulf; national-versus-expatriate split rules; air-ticket and housing allowance accruals; leave salary paid in advance; overtime at statutory multipliers; annual-leave encashment; and final settlements that combine gratuity, unused leave, notice pay and outstanding loans into one payable that must reconcile.

What ECOSIRE builds

We build a payroll localization inside your own NetSuite account — custom records, SuiteScript 2.1 logic, SuiteFlow approvals and generated bank files — delivered as an unmanaged bundle or SDF project you own.

Employee payroll profile

A custom record extends the NetSuite employee record with the fields Gulf payroll actually needs: nationality and national/expatriate classification, labour card or work permit number, national or resident identity number, IBAN and bank code, visa and contract dates, contract type (limited or unlimited term), joining date and any unpaid-leave periods that suspend service accrual. Salary structure is held as dated component rows — basic, housing, transport, other allowances — so a mid-year increase is a new effective-dated row, not an overwrite that destroys history.

Gratuity engine

A scheduled Map/Reduce script recalculates end-of-service accrual for every active employee each period. Calculation rules live in configuration records — daily-wage basis, service-year bands and their multipliers, resignation versus termination treatment, unpaid-leave exclusion, and any cap you apply — so a change in your legal interpretation is a configuration edit rather than a code change. Each run writes an accrual movement per employee and posts the aggregate provision as a journal entry to the accounts and subsidiary you nominate, with the employee visible via a custom segment or class so the provision is analysable rather than a single opaque number.

Payroll run and payslips

A payroll run record collects the period, subsidiary and employee population, then a Map/Reduce calculates each employee's gross: dated salary components, overtime at your configured multipliers, leave salary, allowances, plus deductions for statutory contributions, loan instalments, absence and any other configured deduction. The run posts to the GL as a journal entry per subsidiary with the mapping you define — expense by department, cost centre or custom segment, and liabilities to payable, statutory and provision accounts. Payslips generate as PDFs from an Advanced PDF/HTML template in your own branding and, where you want it, email to employees on approval. A SuiteFlow approval routing gates the run: draft, calculated, approved, posted — nothing posts to the GL or generates a bank file until it is approved by whoever your policy names.

WPS and bank file generation

This is the part that must be exact. We build a file-format definition per bank and per country you operate in — record layout, field positions and widths, delimiter, header and trailer with the control totals and record counts the bank expects, employee identifier fields, and date and amount formatting rules. Generation runs off the approved payroll run, validates every employee for a complete identifier and IBAN before writing, and refuses to produce a file with missing mandatory data rather than producing one the bank will reject. Files are saved to the File Cabinet against the payroll run, so what was submitted is always retrievable. Formats are configuration records, so when a bank revises a layout you change the definition — you do not wait for a code release.

Statutory contributions

GOSI, GPSSA and equivalent schemes are implemented as contribution rule records: employee and employer rate, the salary components each rate applies to, ceilings, and separate rate sets for nationals and expatriates. Contributions calculate inside the payroll run, appear on the payslip, post to their own liability accounts, and are extractable as a filing report.

Leave and final settlement

Leave balances and encashment feed the payroll run. A final-settlement record assembles gratuity to the leaving date, unused leave encashment, notice pay or deduction, outstanding loan balances and any other adjustment into one settlement figure with a full breakdown, releases the accrued provision, and produces both a settlement statement for the employee to sign and the payment for finance to process.

OneWorld and multi-entity

Every payroll run belongs to a subsidiary. Accounting periods, base currency, account mapping, gratuity configuration and WPS format are all resolvable per subsidiary, so a group operating in more than one Gulf country runs each country's payroll under its own rules in one NetSuite instance. Role and permission design restricts payroll data — the delivered roles let a payroll preparer work without giving them visibility of every employee's salary, and restrict approval to the roles you nominate.

Who this is for

Companies running NetSuite in the UAE, Saudi Arabia, Qatar, Oman, Kuwait or Bahrain that currently maintain payroll, gratuity provisions and WPS submissions in spreadsheets or a disconnected local payroll package. It particularly suits groups with several Gulf entities in one OneWorld account, businesses whose auditors have queried the gratuity provision, and finance teams tired of a rejected WPS file two days before payday.

How delivery works

1. Scoping call. We go through your entities and countries, headcount, salary component structure, gratuity policy and its legal basis as you apply it, statutory schemes in scope, each bank and WPS format you must file, your leave policy, GL account mapping and who approves what. 2. Fixed quote. A written scope naming every country, bank format, statutory scheme and report included. Fixed price against that scope; additions are quoted before work begins. 3. Build. We develop the employee payroll profile, salary component records, gratuity engine, payroll run, payslip template, WPS format definitions, contribution rules, settlement record and reports. Typical lead time is 2–4 weeks depending on how many countries, banks and entities are in scope. 4. Install in sandbox and parallel run. The bundle installs in your sandbox first. We then run your payroll in parallel against your existing method for at least one period and reconcile line by line — per employee gross, each deduction, the gratuity movement and the GL posting. WPS files are validated against the bank's published specification and, where your bank offers a test channel, submitted to it before go-live. 5. Production. After a reconciled parallel run, we install to production and support your first live cycle end to end, from calculation through approval, posting, payslips and WPS submission. 6. Support window. Post-go-live support covers defects, configuration adjustments and format changes within the delivered scope.

We build software that applies the rules you and your advisers specify. Legal interpretation of labour law, and the accuracy of the rates and bands you provide, remain yours — the calculation rules are held in configuration records precisely so you can adjust them when your advice changes.