Oracle Fusion Testing for GCC Teams: The ZATCA, WPS and PACI Compliance Guide

If you run Oracle Fusion in the Gulf Cooperation Council, your compliance testing requirements go far beyond what most Oracle testing tools — and most Oracle testing guides — address. ZATCA Fatoorah Phase 2 e-invoicing in Saudi Arabia, UAE Wage Protection System (WPS) SIF file submissions, Kuwait PACI Civil ID integration, and GOSI contribution calculations across multiple Gulf states each require dedicated testing that generic Oracle test libraries do not include. This guide covers what GCC teams need to test and how to structure a compliance-focused regression cycle.

Saudi Arabia: ZATCA Fatoorah Phase 2 Testing

ZATCA (the Zakat, Tax and Customs Authority) mandates that Saudi-registered businesses generate e-invoices in a specific XML format and, for Phase 2, integrate directly with ZATCA's FATOORAH portal for clearance and reporting. Oracle Fusion Financials includes ZATCA-compliant invoice generation functionality, but it must be correctly configured and — critically — tested after every Oracle quarterly update.

What to test after every Oracle quarterly update:

Validate that your Oracle Fusion Payables and Receivables configuration still generates ZATCA-compliant XML. ZATCA requires specific fields: the taxpayer's 15-digit VAT registration number, the buyer's VAT registration number for B2B transactions, a QR code, a cryptographic stamp, and a UUID for each invoice. Test that all of these fields populate correctly for a representative sample of transaction types — standard invoices, credit notes, debit notes, and self-billing invoices.

Test the clearance process for invoices above SAR 1,000: confirm that Oracle submits the invoice XML to ZATCA's FATOORAH portal and receives a successful clearance response before the invoice is posted to the GL. Test the reporting process for invoices below the clearance threshold.

For Oracle quarterly updates, pay particular attention to changes in the Payables invoicing engine. Any change to how Oracle generates invoice XML can invalidate ZATCA compliance. SyntraFlow's ZATCA test pack executes a full e-invoice lifecycle for multiple transaction types after every Oracle update, confirming ZATCA compliance before your next production posting run.

UAE: Wage Protection System (WPS) Testing

The UAE Ministry of Human Resources and Emiratisation (MoHRE) requires all UAE employers to submit salary payment data in a specific Salary Information File (SIF) format and upload it to the WPS system within defined timelines. Oracle Fusion Cloud Payroll generates SIF files, but the file format and validation rules are updated periodically — and Oracle quarterly updates can affect SIF generation.

What to test after every Oracle quarterly update:

After each quarterly update, run a test payroll cycle for a representative sample of UAE employees and generate the SIF file. Validate the file against the current MoHRE schema — specifically checking that employee bank account numbers, IBAN formats, salary amounts, and employer details are correctly structured. Submit the test SIF file through MoHRE's validation tool before your live payroll submission.

For 26A specifically, Oracle has updated the UAE WPS SIF generation process. GCC Oracle teams should validate that the new SIF output passes MoHRE validation before processing their next live UAE payroll run.

Kuwait: PACI Civil ID Integration Testing

Kuwait's Public Authority for Civil Information (PACI) requires employers to maintain accurate Civil ID data for all employees and ensure that payroll and HR systems correctly reference Civil ID records. Oracle Fusion HCM includes Civil ID fields and integrations, but these require testing after Oracle updates that affect the person record structure.

What to test:

Validate that Oracle Fusion HCM is correctly storing and displaying Civil ID numbers for Kuwait-based employees. Test any integrations that transmit Civil ID data to government systems or third-party HR platforms. Confirm that Oracle Fusion payroll processes correctly reference Civil ID data and that any Oracle updates have not disrupted Civil ID field mappings.

Bahrain and Oman: EOS and Gratuity Calculation Testing

End-of-service benefit (EOS) and gratuity calculations in Bahrain and Oman follow specific legislative formulae that Oracle Fusion Payroll must apply correctly. After quarterly Oracle updates, validate that EOS and gratuity calculations for a sample of employees — covering different length-of-service brackets — produce results that match the legislative formula. Run the calculations manually for three or four employee scenarios and compare the output to Oracle's calculation.

Building a GCC Compliance Test Calendar

GCC Oracle teams should maintain a compliance test calendar aligned to Oracle's quarterly update cycle. The calendar should include: ZATCA SIF test run and portal validation; UAE WPS SIF generation and MoHRE validation; PACI Civil ID record integrity check; GOSI contribution rate validation for Saudi and UAE entities; EOS and gratuity calculation spot-checks for Bahrain and Oman employees.

SyntraFlow's GCC compliance test packs execute all of these validations automatically as part of your Oracle quarterly regression cycle — with results reports that your compliance and finance teams can use as audit evidence.

The Challenge with Generic Oracle Testing Tools

Opkey, Tricentis Tosca, and most other Oracle testing tools are built primarily for the US and, to a lesser extent, Western European markets. GCC-specific compliance scenarios — ZATCA XML validation, UAE WPS SIF format checking, Kuwait PACI integration testing — are not included in their pre-built test libraries. GCC teams using these tools build compliance tests from scratch, maintain them manually across Oracle updates, and often lack the regional regulatory expertise to know what to test in the first place.

SyntraFlow was built with GCC market requirements from the ground up. Our team maintains the ZATCA, WPS, PACI, and GOSI test libraries in line with regulatory changes — so your team does not have to.

Contact SyntraFlow to discuss your GCC Oracle compliance testing requirements and see how our pre-built GCC test packs can integrate with your quarterly Oracle update cycle.