Fusion is a large, capable suite, and that breadth is both its strength and its risk. Implemented with discipline, it gives a multi-entity group a single ledger and reporting layer, with procurement running as one process.

Implemented as a straight lift of global templates, it produces a system that technically works but fights Saudi accounting, payroll and e-invoicing. Our practice covers the Fusion modules a Riyadh group typically needs, starting with Financials and procurement, then SCM, projects and HCM.

Designing the enterprise structure for Riyadh

The decisions that matter most are made in the first weeks. First, how legal entities, ledgers and business units map to your actual corporate structure. Second, how the chart of accounts is built so Zakat and VAT reporting come from standard ledgers instead of side calculations. Third, how intercompany is configured so multi-entity consolidation is automatic. These are difficult to change after go-live, which is why we spend disproportionate time on them up front.

E-invoicing, payroll and local requirements

Fusion's Saudi localization handles Arabic reporting, Hijri calendars and VAT. ZATCA Phase 2 e-invoicing integration, GOSI and WPS payroll connectivity and bank file formats for the major Saudi banks each require deliberate configuration and, in some cases, integration components. We specify these in the design phase and test them against actual transactions, not sample data, before cutover.

Implementation approach

Fusion projects are run in phases aligned to business risk. Core financials and procurement typically go first, establishing the ledger and control foundation. Supply chain, projects and HCM follow once the finance backbone is stable. Each phase has its own conference room pilot, user acceptance testing with your transactions, and a cutover plan sequenced around Saudi fiscal, payroll and reporting deadlines.

A hypothetical example

Imagine a Riyadh-headquartered holding company with subsidiaries in contracting, real estate and trading that consolidates several systems in spreadsheets. In Fusion, one primary ledger per entity, a shared chart of accounts with segment values for each business and intercompany rules would replace manual elimination entries.

Ongoing operation

Oracle releases quarterly updates to Fusion Cloud. Managing these updates is a discipline in itself: testing that your configuration and integrations still work, and adopting new functionality without disrupting operations. That is why implementation is followed by structured support for your Oracle environment instead of a hand-off and departure.

Data migration as its own workstream

Moving history into Fusion is not a technical task to leave for last. Open balances, open purchase orders, customer and supplier masters, fixed asset registers and, for groups migrating mid-year, year-to-date transaction detail all need extraction, cleansing, transformation and reconciliation. We run migration as a separate workstream with its own plan and acceptance criteria, because it can drive the go-live date.

Choosing an implementation partner

Oracle licenses the software, but partners implement it, and the quality of the partner shapes the outcome as much as the product does. Assess any partner on completed Saudi Fusion projects you can speak to. Look at the specific consultants who will work on your project, not the firm alone, and at its ability to support you inside the Kingdom after go-live.