The vendor can supply country functionality; only the enterprise can prove payroll will operate
Altivate | Published 19 April 2026 | Updated 26 July 2026
1. The question that decides the outcome is not the question being asked
Every HCM selection process in this region converges on the same shortlist and the same criteria: functional breadth, user experience, analytics, roadmap, price. Localisation appears as a line item – usually a single row in a scoring matrix, marked green by every vendor.
It is the row that determines whether the implementation lands.
A payroll platform that cannot produce a compliant Wage Protection System file does not have a gap in a feature matrix; it has a business that cannot pay people in a way the regulator accepts. The same is true of GOSI contribution handling in Saudi Arabia, gratuity accrual across the Gulf, and the Indian statutory set. These are not preferences. They are the conditions of operating.
The only defensible starting point is published product evidence. The comparison below uses the vendors’ own payroll documentation, then separates documented functionality from the operating proof an enterprise still has to supply.
Related: our three-way comparison of SuccessFactors against Workday and Oracle.
2. Evidence is not proof, and one document is never the product
Vendor documentation is inspectable and repeatable, but it is not a production proof. A field-mapping guide shows that data can move between systems; it does not prove that a product calculates, files or controls a statutory obligation natively. Statutory-capability claims require evidence at the payroll, filing or regulator-interface layer, supported by the relevant local version and release material.
| What we found | What it licenses |
|---|---|
| A capability documented in current product material | Evidence that the capability exists in the documented product and version |
| A capability absent from one guide | A reason to search the rest of the product documentation, not a product verdict |
| A statutory output shown in a scripted demonstration | Evidence that the configured product can produce it for the tested scenario |
| An accepted regulator or bank test | Evidence that the operating chain works, which documentation alone cannot establish |
Documentation establishes a starting point. The enterprise still needs a scripted demonstration, representative employee cases, accepted output and contractual ownership of legal change.
The selection decision is complete only when all three layers have an owner.
3. Where both vendors are strong, and it is not where people worry
| Requirement | SAP SuccessFactors (EC Payroll) | Oracle Fusion Cloud HCM |
|---|---|---|
| Saudi GOSI | Documented. A dedicated infotype (IT3252, Social Insurance – Saudi Arabia) carrying GOSI registration number, registration status, social insurance grouping and retirement-age exemption. | Documented in depth. An Employee GOSI Details calculation card created automatically at hire; three-component calculation (Annuities, Saned, Hazards); arrears management; salary-recalculation logic. |
| India TDS / Form 16 | Documented. A dedicated section on setting up Form 16, including the service configuration it requires. | Documented in depth. Form 24Q quarterly TDS returns plus a full Form 16 workflow – Part A and Part B, TRACES integration, digital signing, mass download. |
| India income-tax declarations | Documented. Form 12BB, income-tax declaration and tax-simplifier statement, with setup procedures. | Documented. Including Form 12BA perquisite detail, as part of Form 16 generation. |
One clarification on that last row, since the form numbers look parallel and are not: Form 12BB is the employee’s own investment and exemption declaration; Form 12BA is the employer’s statement of perquisites. We found each vendor documenting a different one. That is not evidence that either lacks the other – it is what each guide happened to cover, and it is the kind of near-miss that a feature-matrix comparison would silently record as a difference.
Both vendors have done this work. If your evaluation is anxious about whether a global platform can handle Saudi social insurance or Indian income tax, the anxiety is misplaced – that is the mature, well-documented end of both products.
Oracle’s India coverage is worth a specific note, because it is often assumed to be thinner than its on-premise predecessor: Provident Fund electronic challan and return, ESI monthly contribution returns with the two-step submit-and-pay process, and slab-wise Professional Tax computation configurable by state. That is read from Fusion Cloud’s own current documentation, not from the legacy E-Business Suite guides – a distinction that matters, because confusing the two is how the “Fusion is thin on India” impression persists.
Product detail: Employee Central Payroll.
4. The requirements that still need an operating proof
Here the symmetric result is the finding, and it is not the one anyone expects.
Nationalisation-quota tracking appears in neither
We searched both vendors’ payroll documentation for Emiratisation, Emiratization, Nitaqat, Saudization and Saudisation, plus general nationalisation and quota terminology.
Zero occurrences. In either.
We are stating that precisely, because precision is the whole point of this document: that is an absence from payroll documentation. Nationalisation-quota tracking is arguably a workforce-compliance function rather than a payroll-calculation one, so it may well exist elsewhere in either suite – a reporting module, a workforce-planning capability, a partner add-on.
The finding is that it takes asking. If quota position is a live constraint on your operating model – and in Saudi Arabia and the UAE it is, with financial consequences attached and direct implications for which entity a role can sit in – then the assumption that it arrives in the box is unsupported by either vendor’s payroll documentation. Put it in the RFP as an explicit requirement, and ask to see it demonstrated rather than confirmed.
WPS exists in the products; the operating chain still needs proof
The Wage Protection System is how salaries are legally paid in Saudi Arabia and the UAE. It is not an edge case; it is the mechanism.
Current official documentation closes two important gaps:
- SAP’s UAE local version documents automatic WPS file generation through Pre-DME and FI DME, including UAE-specific wage types and configuration.
- Oracle Fusion Cloud HCM documents the UAE Wage Protection System report and Salary Information File, including setup and refund handling.
That changes the procurement question. A green “WPS” cell is supported for those documented UAE flows, but it still does not prove the enterprise’s bank, legal entity, payroll calendar, file transport and failure recovery will work. For Saudi Arabia, require the vendor to demonstrate the current Mudad/WPS output and submission path for the exact cloud product and release proposed.
Ask how the complete chain operates, not only whether the feature exists.
5. Product capability and delivery scope are separate facts
Both SAP and Oracle document end-of-service capability. Oracle publishes UAE and Saudi implementation detail. SAP’s UAE local-version documentation identifies the UAE payroll schema and end-of-service subschema, and its UAE and Saudi pages document gratuity or end-of-service calculation and configuration.
The remaining question is not whether the calculation exists somewhere in the portfolio. It is whether it is included, supported and current in the exact cloud deployment, country version and commercial scope being proposed. Apply the same test to the Indian statutory set: ask the vendor to identify the product component, release, statutory update owner and evidence from a current representative calculation.
One genuinely contested item, recorded because pretending otherwise would be worse: India’s Section 89(1) relief calculation. A third-party source describes it as a gap in SuccessFactors. An SAP Knowledge Base article exists whose title implies the capability – but the article is behind a support login and is filed under the on-premise product rather than SuccessFactors. We could not settle it. If Section 89(1) relief matters to your Indian population, treat it as unresolved and get it in writing.
6. Workday, briefly and honestly
We did not read Workday’s payroll documentation to the same depth in this pass, so we are not going to present a three-way comparison we have not done.
The one thing we established from Workday’s own current materials: Workday payroll covers Australia, Canada, France, Ireland, the United Kingdom and the United States. Workday also describes Strada-provided payroll in more than 60 countries and certified integrations across more than 180 countries. Native payroll, a managed partner service and an integration are three different operating models; a selection must label them separately.
Date-stamped deliberately. Country coverage is the single most decay-prone claim in this document – a vendor can add a country in any release. If you are reading this materially later than that date, re-check it before relying on it.
For a group operating in Saudi Arabia, the UAE and India, that is not a disqualification – many organisations run exactly that model deliberately – but it is a materially different architecture from the two products above, and it should be evaluated as an integration question rather than a feature question. Ask who owns the payroll calculation, who owns the statutory updates, and what happens when a regulator changes something.
7. The RFP questions this produces
The practical output of the whole exercise. Each one is written to be pasted directly into a requirements document, and each exists because the documentation did not answer it.
On WPS (Saudi Arabia and the UAE) 1. Demonstrate the current WPS/Mudad or Salary Information File output for each country and legal entity in scope. Identify the product component and release that generates it. 2. Demonstrate submission, acknowledgement, rejection handling and reconciliation with the regulator, bank or WPS agent. Name who owns each interface and format change.
On nationalisation quotas 3. Where in the suite is Emiratisation / Nitaqat quota position tracked and reported? Please demonstrate it rather than confirm it. 4. Can it model the quota effect of moving a role between entities – which is what a shared-services design does?
On end-of-service 5. Show us gratuity accrual and settlement for a UAE and a Saudi employee, distinguishing fixed-term from unlimited contracts, with the calculation visible.
On India 6. Show Provident Fund, ESIC and Professional Tax processing in the cloud product – not the on-premise predecessor. 7. State your position on Section 89(1) relief: native, configurable, or not supported.
On the meta-question, which is the important one 8. For each statutory item above: is it documented in your published product documentation? If not, why not – and what do we rely on instead of documentation when the regulator changes the rules?
That last question is the one that separates vendors. Everything in this paper came out of published documentation or its absence. A vendor whose statutory handling is undocumented is asking you to depend on something you cannot inspect.
Adjacent: seven questions to future-proof your HR operations.
8. What leaders should not infer
This evidence does not rank the vendors. The SAP and Oracle documents have different scopes; Workday was not evaluated to the same depth; and SAP payroll-engine behaviour sits largely outside the field-mapping guide reviewed here. Section 89(1) relief remains contested.
Those are not reasons to abandon the comparison. They are reasons to change the procurement burden. Where documentation is asymmetric or silent, require a production-like demonstration, sample statutory outputs, named release ownership and acceptance criteria. An open question should become a test – not a reassuring assumption.
9. The executive agenda
- Replace the single localisation score with one row per statutory obligation, output and country.
- Ask vendors to distinguish native capability, configuration, partner extension and manual operation.
- Demonstrate WPS, GOSI, gratuity and the India statutory set with representative employee cases and regulator-ready outputs.
- Contract who monitors legal change, who updates configuration, how quickly it ships and who owns failed submissions.
- Retain a country regression pack as an operating asset after implementation.
Altivate provides SAP and SuccessFactors advisory and implementation services and therefore has a commercial interest in this market. That interest does not make an unsupported product verdict useful. Country evidence, operating proof and the signed service scope must decide.
Apply the dossier to SAP SuccessFactors, or return to White Papers.
Sources and verification status
Checked 26 July 2026. Coverage is version-sensitive; confirm the proposed product component, country version and statutory-update service during selection.
Vendor primary – [read in full]
- SAP, Country/Region-Specifics for Employee Central Payroll, 2026-07-15 edition, documents Employee Central-to-payroll mappings including Saudi GOSI, India Form 16 and Form 12BB. It is a mapping guide, not a complete description of the payroll engine.
- Oracle, Implementing Payroll for the United Arab Emirates (last modified 30 June 2025); Implementing Payroll for Saudi Arabia; Administering Payroll for Saudi Arabia; Implementing Payroll for India; Administering Payroll for India. Source for every Oracle finding, including the UAE Gratuity Payment element, the Saudi GOSI three-component calculation, the Indian PF/ESIC/ Professional Tax/Form 24Q reporting. Scope: payroll implementation and administration.
- SAP Help Portal, UAE Wage Protection System, documents automatic WPS file generation through Pre-DME and FI DME.
- SAP Help Portal, UAE End of Service Gratuity Calculation, and Saudi End of Service, document the relevant local-version calculation and configuration.
- Oracle, Wage Protection System Report for UAE, documents the Salary Information File and refund-report flow.
- Workday, Payroll overview, is the current source for country coverage. Vendor coverage changes by release; verify the live country list during selection.
Recorded as contested, not resolved
- SAP Knowledge Base article on Section 89(1) relief calculation – title and one-line symptom visible only; the body is behind an SAP support login, and it is filed under the on-premise product rather than SuccessFactors. Cited here as the reason the question is open, not as evidence either way.
A note on nationalisation tracking. The payroll documents reviewed do not establish Emiratisation or Nitaqat quota tracking. That does not prove the wider suites lack it; require the workforce-compliance capability to be demonstrated in the proposed configuration.
