31 locations. One payroll.
Taxes, social insurance, end-of-service, WPS variants and statutory reports, localized per country and consolidated in one platform.
One Solvait customer runs 31 locations on the platform. Another runs 35, worldwide. Ask for the two-country payroll walkthrough.
Sound familiar?
What we hear from group HR directors and payroll shared-services leads running people across borders.
A different payroll vendor or spreadsheet in every country, and month-end is spent chasing all of them.
Social insurance regimes that share nothing: GOSI, GPSSA, PASI. Different bases, different caps, no single system.
End-of-service, gratuity and leave differ by country and change without notice, so you hear it from an auditor.
Group reporting takes a week of Excel and still doesn't reconcile, because every country exported its own truth.
Every country has its own rules. You should have one system that knows them all.
A country is not a configuration flag. It is a rulebook: its own tax treatment, its own social insurance scheme. Solvait keeps each of those as a versioned country rule pack on one payroll engine.
- Tax and payroll deductions defined per country, not approximated from the neighbour.
- Social insurance as its own scheme, with its own base, caps and employer share.
- End-of-service and gratuity on the local formula, including how the country treats resignation.
Three neighbours, three regimes
Different bases. Different caps. Different filing dates. One engine.
Regulations move. Your payroll should not be the last to hear.
Rules are versioned, dated and shipped centrally.
- 01
The change is spotted centrally
Mutaba'aa watches regulatory and statutory change across every jurisdiction you run in.
- 02
A new rule version ships
The country rule pack is versioned and dated: made once, released to every entity.
- 03
Your next cycle picks it up
Rawatib applies the rule version that was in force on the pay date.
- 04
The payslip remembers
Every payslip records which rule version calculated it.
Deepest in the Gulf. Live in 13+ countries. Localized for 48.
The GCC six are where we go deepest, because that is where the compliance detail is unforgiving and where most of our customers file.
Saudi Arabia
GOSI contributions at Saudi and non-Saudi rates, WPS through Mudad, contract data consistent with Qiwa, Iqama expiries from Muqeem, Nitaqat banding and Hijri dating. Our deepest localization.
United Arab Emirates
GPSSA pension contributions for UAE and GCC nationals, end-of-service gratuity on the local formula for everyone else, and wage protection filing in the UAE format.
Kuwait
Social insurance for Kuwaiti and GCC nationals, terminal indemnity on the Kuwaiti calculation, and the local wage protection file produced by the payroll run itself.
Qatar
Social insurance for Qatari nationals, end-of-service gratuity on the Qatari formula, and the Wage Protection System file in the format the local banks expect.
Bahrain
Social insurance contributions for Bahraini and expatriate employees at their respective rates, leaving indemnity, and Bahraini wage protection filing.
Oman
PASI contributions, end-of-service on the Omani formula, and Omanisation reporting alongside the same leave and payroll engine every other country runs on.
Beyond the Gulf, on the same engine
Solvait is localized for 48 countries with 13+ country payrolls live today, across the wider Middle East and Africa. Entering a new market adds a rule pack, not a second system and a second vendor.
Your group numbers, without the week of Excel.
Local finance needs statutory output in the local currency and the local format. Group finance needs one comparable view. On one platform, both come out of the same data at the same time.
- One currency of record for the group, with each entity keeping its own for filing.
- Headcount, people cost and accruals comparable across entities because they share one definition.
- Real time, not month-end: the group number moves when the underlying entity does.
The regimes that share nothing
Neighbouring countries, incompatible rulebooks. Each one is maintained as its own rule pack.
GOSI (Saudi Arabia)
Contributions calculated per employee against your registered establishment, with Saudi and non-Saudi rates handled as the separate schedules they are.
GPSSA (United Arab Emirates)
Pension and social security contributions for UAE and GCC nationals, while expatriate employees accrue end-of-service gratuity under their own rules.
PASI (Oman)
Omani social insurance contributions and end-of-service treated as a country rule, not as a variation somebody bolted onto the Saudi setup.
WPS, in every local format
Wage protection is not one standard. Each country produces its own file from the same payroll run, on its own schedule, in the layout its banks and ministry accept.
End-of-service and gratuity
The formula, the qualifying service and the resignation-versus-termination treatment all differ by country. Each one is a versioned rule, not a spreadsheet formula.
Qiwa and Mudad
Saudi contract records and wage filing stay consistent with what the platforms hold, so a mismatch never surfaces mid-transaction.
Muqeem and Nitaqat
Iqama status, expiry and Saudization banding tracked per entity, visible before a renewal deadline or a band change becomes a blocked service.
Hijri and Gregorian
Entitlements, contract dates and end-of-service run in both calendars, because in this region half the paperwork uses one and half uses the other.
Global policy at HQ. Local law in the country. Both, with an audit trail.
Group HR writes one policy. Then Saudi law overrides the notice period, UAE law the gratuity, and Oman the leave accrual. Solvait makes the exception an object: scoped to a country, owned and dated.
- A global policy layer that every entity inherits by default.
- Country exceptions declared explicitly, with the legal basis recorded next to them.
- An audit trail on every change: what changed, who approved it, which entities it touched.
Four real products, not four regional labels.
One HCM core, two agents and an analytics layer. There is no separate regional edition to buy.
Solvait HCM
- Multi-country core on Microsoft Dynamics 365
- One employee record that survives a move
- Per-entity legal structures, pay calendars
- Group hierarchy that matches
Rawatib: payroll agent
- Runs each country’s cycle on one engine
- Applies that country’s rule pack
- Produces WPS and bank files
- Off-cycle, retro and correction runs
Mutaba'aa: compliance agent
- Statutory change across every jurisdiction
- Visa, permit and document expiries
- Contract, probation and renewal dates
- Raises the exception before the deadline
Solvait Wise
- Workforce analytics across every entity
- Headcount and people cost by country
- Comparable metrics on one definition
- Group answer first, drill-down
Organisations running people across borders on Solvait
Complex, multi-entity operations where one rulebook was never going to be enough.
Government-scale complexity across a multi-entity footprint, without being a government body.
Engineering group HR and payroll on one platform, wherever the projects are.
The 31-location and 35-location customers referenced above stay anonymous: we publish a client name only with written permission.
Questions buyers actually ask
Bring us your two hardest countries.
Book a demo and ask for the two-country payroll walkthrough. We will run two of your markets side by side on one engine.
