Why MENA payroll needs a specialist, not a global platform

I'm an actuary by background, not an HR professional. Ten years in UK pensions and insurance — pricing risk, modelling longevity, auditing schemes running into the hundreds of millions — teaches you to look at systems as a set of inputs, outputs, and failure modes. You ask: where does a bad number enter? Where does it get caught? Where does it escape?

When I turned that lens on how multi-country payroll works in the MENA region, two things stood out. First, the problem is structural, not cosmetic — it's not that MENA teams need better spreadsheets. Second, the companies currently trying to solve it are almost all pulling in the wrong direction.

This post is about the second thing. Global Kinect exists because there's a middle position in the market that almost nobody is occupying, and I think the reason is that getting it right requires a kind of attention to the region that generic global platforms have no commercial reason to give.

The shape of the market today

If you're an HR, finance or ops leader running payroll across two or more MENA countries today, your options are roughly these.

• A local bureau per country — fragmented, paper-heavy, strong on compliance but weak on technology and consolidation.
• A patchwork of spreadsheets and consultants — cheap to start, exponentially painful to scale.
• A global EOR platform that claims MENA coverage alongside 80+ other countries.

The first two are familiar and well-understood. The third is the one worth examining, because it's where most venture-backed companies expanding into the region end up by default.

Global platforms sell breadth. The pitch is: one system, every country, same workflow. For a company hiring one person in each of twelve countries, that's genuinely useful. But for a company operating meaningfully in MENA — six employees in Dubai, fifteen in Riyadh, a growing team in Cairo — the breadth is the problem, not the feature.

Where the breadth hurts

Here's what I mean by structural. MENA payroll is not an extension of European payroll with different tax rates. It's a different discipline with different mechanics, different cadences, and different failure modes.

A few examples, each of which I've seen generic platforms handle badly or not at all.

End-of-service benefits aren't a single formula

Every GCC country accrues end-of-service benefits differently. UAE is 21 days of basic salary per year for the first five years, then 30 days thereafter. Saudi Arabia is half a month per year for the first five years, full month after that — based on last drawn salary, which creates a salary-bump trap that UAE's formula doesn't have. Qatar is a flat three weeks per year, no tier transition. Oman's tier transition is at three years, not five. Bahrain, Kuwait, Egypt — each different again. We have a guide that walks through each country's EOSB formula with the specific mistakes we see operators make.

A platform that calculates EOSB by picking a generic accrual rate and applying it across the region isn't wrong in the sense of producing a number. It's wrong in the sense that the number is unauditable.

Social insurance depends on nationality

In Saudi Arabia, GOSI is 11.75% employer on Saudi nationals and roughly 1-2% occupational hazard on expats. That nine-to-eleven-percentage-point gap is the structural cost difference behind Saudization, and a workforce cost model that averages the two rates is materially wrong — the kind of wrong that shows up as a budget variance three quarters into the year. Most generic platforms treat social insurance as a country-level rate. The nationality split is the actual model.

The working week isn't aligned across the region

The UAE moved to Monday-Friday in January 2022. Most of the rest of the GCC still runs Sunday-Thursday. That's four overlapping working days per week across the region. A payroll cut-off calendar designed in Europe that assumes a five-day week alignment will miss bank processing windows in at least one country every month. This isn't exotic — it's the operational reality of every multi-country GCC payroll close.

WPS and its regional variants aren't "just a file format"

The UAE's Wage Protection System reconciles every submitted SIF against the salary agreed in each employee's contract. Late payment triggers work permit suspensions after 15 days. Mudad in Saudi works on similar principles with different file specifications. Qatar, Bahrain, and Oman each run wage protection through separate administrative mechanisms. Treating "GCC WPS" as a single concept is one of the most common mistakes multi-country operators make.

A platform that calculates EOSB by picking a generic accrual rate and applying it across the region isn't wrong in the sense of producing a number. It's wrong in the sense that the number is unauditable.

Social insurance depends on nationality

In Saudi Arabia, GOSI is 11.75% employer on Saudi nationals and roughly 1-2% occupational hazard on expats. That nine-to-eleven-percentage-point gap is the structural cost difference behind Saudization, and a workforce cost model that averages the two rates is materially wrong — the kind of wrong that shows up as a budget variance three quarters into the year. Most generic platforms treat social insurance as a country-level rate. The nationality split is the actual model.

The working week isn't aligned across the region

The UAE moved to Monday-Friday in January 2022. Most of the rest of the GCC still runs Sunday-Thursday. That's four overlapping working days per week across the region. A payroll cut-off calendar designed in Europe that assumes a five-day week alignment will miss bank processing windows in at least one country every month. This isn't exotic — it's the operational reality of every multi-country GCC payroll close.

WPS and its regional variants aren't "just a file format"

The UAE's Wage Protection System reconciles every submitted SIF against the salary agreed in each employee's contract. Late payment triggers work permit suspensions after 15 days. Mudad in Saudi works on similar principles with different file specifications. Qatar, Bahrain, and Oman each run wage protection through separate administrative mechanisms. Treating "GCC WPS" as a single concept is one of the most common mistakes multi-country operators make.

The middle position

None of the above is a secret. Anyone running MENA payroll already knows it. The question is what a platform does about it.

A generic global platform treats these as configuration edge cases — things its account managers handle on the side, or that get flagged as "local requirements" outside the main product. That works at the margins. It breaks as soon as you scale enough that the edge cases become the main workflow.

A local bureau handles these correctly but builds no technology around them. Each one is a black box. You get accurate numbers and no visibility.

The middle is what we're building Global Kinect to occupy — a payroll, HRIS and EOR platform that treats MENA complexity as the primary design constraint, not an afterthought. GOSI by nationality, EOSB by country formula, WPS file generation per jurisdiction, Arabic interface where required, multi-currency by default, working-week-aware cut-off calendars. All of that sits in the core product, not in the "how we accommodate your region" addendum.

This has a commercial implication I should be honest about. Global platforms reach for breadth because breadth is how the SaaS category rewards capital-efficient growth. A regional specialist makes a different bet: deeper in fewer markets, better unit economics on each, slower to expand outside the region. I think that bet is the right one for the buyers we're building for. Time will tell whether it's the right one commercially. But I'm not writing this post to defend our commercial model — I'm writing it to explain why we think the category as it currently exists is failing people.

Tell me where I'm wrong

This is the first post on this blog, and I'd rather have it be a view that someone wants to argue with than a view that everyone nods along to and forgets. If you're running HR, finance or ops in MENA and the above describes your life, tell me. If it doesn't — if the generic global platform is working fine for you, or if you think I've mischaracterised the problem — tell me that too. Every subsequent post on this blog benefits from hearing where this one is wrong.

We have a hundred-odd operational guides covering every country, every compliance regime, and every structural trap mentioned above. This blog will be where we write the things the guides deliberately don't — opinions, observations, and the occasional argument.

Welcome. More soon.