Oracle: the Gulf is the deep end, and payroll is still the problem

45.3% of the Oracle professionals measured sit in Saudi Arabia or the UAE: the highest Gulf share of any family in the set. Financials runs 8.4 percentage points higher in the Gulf than in the UK, and Fusion 6.5 percentage points higher.

This matters because the corridor is usually described in one direction, as though the Gulf were short of everything and the UK had a surplus. On Oracle it is the other way round. The two ends of the corridor specialise; neither is simply the shallow end.

103 professionals across all three markets declare Oracle payroll: 46 in the UK, 29 in Saudi Arabia, 28 in the UAE. That is 2.0% of the Oracle pool, and the smallest named skill in the entire extract.

Payroll is also the workstream that cannot slip. It is legally dated, it touches every employee, and it is the one part of a Fusion programme where a missed date is visible outside the programme on the same day it happens.

So the planning consequence is specific rather than general. Finance can be staffed from the Gulf pool with confidence. Payroll cannot be staffed from any of these three markets on the assumption that a search will simply find someone, and a plan that assumes it will is carrying an unpriced risk in its most exposed workstream.

Treating payroll as a corridor role from day one means deciding, at business case, that the specialist will be engaged from outside the country and that someone has to be able to employ them there. That is entity and payroll friction, and it is precisely what an employer of record removes.

The connection is worth stating plainly because it runs the right way round: the data did not go looking for a service to justify. The scarcest skill in the set happens to sit in the workstream with the least tolerance for delay, and the mechanism for staffing it across a border already exists.