The ERP selection decision is the most consequential and longest-lasting technology investment a large enterprise makes. Unlike a BI platform or an automation tool, an ERP system shapes how the entire organisation records, processes, and reports every transaction for the next ten to fifteen years. Getting it right matters in a way that few other technology decisions do.
In the GCC and Egypt in 2026, this decision is being made at scale. Vision 2030 transformation programmes, Saudi Arabia’s ZATCA Phase 2 e-invoicing mandate, the UAE’s federal corporate tax framework, Egypt’s ETA mandate, IFRS 18 adoption, and the growing complexity of multi-entity regional group structures have all created conditions where organisations that were managing adequately on legacy ERP systems are now under genuine pressure to modernise. The demand is real, the investment budgets are real, and the stakes are high.
What is also real is the quality of advice available to CFOs and CIOs making this decision. Most of it is produced by the vendors whose systems are being evaluated, by implementation partners who have a commercial stake in the recommendation, or by global research firms whose GCC market knowledge is thin. The question of which ERP is right for a Saudi conglomerate navigating Vision 2030 reporting requirements and ZATCA Phase 2, for a UAE holding company managing multi-jurisdiction corporate tax, or for an Egyptian enterprise building a finance function that can support international investor reporting — is answered differently by Oracle, SAP, and Microsoft than it is by an independent firm with no commercial arrangement with any of them.
This guide is written by that independent firm. We have no partnership arrangement with Oracle, SAP, or Microsoft. We have implemented and assessed ERP environments across all three platforms in Egypt, Saudi Arabia, the UAE, Qatar, and Kuwait. Our recommendation in any advisory engagement is determined solely by the client’s requirements and operating context.
Why ERP Selection in the GCC Is Structurally Different From Anywhere Else
Generic ERP comparison guides evaluate on functionality depth, total cost of ownership, implementation complexity, and vendor support quality. These dimensions are relevant everywhere. In the GCC and Egypt, five additional dimensions shape the decision in ways that fundamentally change the ranking.
ZATCA Phase 2 Integration — The Baseline Requirement for Saudi Operations
Saudi Arabia’s ZATCA Phase 2 e-invoicing mandate requires every VAT-registered business to connect its invoicing system directly to the Fatoora platform. This is not a future requirement or a roadmap item — it is an active, enforced compliance obligation for the vast majority of Saudi enterprises in 2026.
For an ERP under evaluation for Saudi operations, the question is not whether ZATCA integration is on the product roadmap. It is whether a certified, production-tested ZATCA Phase 2 integration is available today, for the specific ERP version under consideration, with documented reference customers running it in a Saudi production environment. The distinction matters because three of the most frequently made ERP selection mistakes in Saudi Arabia in 2025 and 2026 involved selecting an ERP whose ZATCA integration was described in implementation proposals and vendor demonstrations as “available” or “in progress” — and discovering after contract signature that the integration required additional development, additional cost, or was not yet certified by ZATCA.
Arabic-Language Operation — The Full Requirement, Not the Marketing Claim
Every enterprise ERP vendor in 2026 claims Arabic-language support. The meaningful question is what that support actually covers in production operation.
Arabic-language ERP operation, as required by a GCC or Egyptian enterprise where the finance function works primarily in Arabic, has six specific dimensions: the user interface rendered in Arabic with correct right-to-left layout (not just Arabic text in a left-to-right interface); chart of accounts and master data in Arabic with bilingual labels; Arabic-language transaction input — purchase orders, invoices, journals — with correct character encoding and field alignment; Arabic-language system-generated documents — invoices, statements, remittances — meeting Saudi and Egyptian regulatory formatting requirements; Hijri calendar support for Saudi statutory and regulatory reporting; and Arabic-language user training and system documentation. Vendors who confirm “Arabic support” without specifying which of these six dimensions are production-ready, for the specific ERP version under evaluation, are confirming the marketing position rather than the delivery reality.
Vision 2030 Reporting and Multi-Entity Complexity
For Saudi enterprises participating in Vision 2030 programmes — whether as giga-project contractors, NEOM-adjacent suppliers, PIF portfolio companies, or National Transformation Programme participants — the ERP’s reporting architecture needs to support the specific KPI frameworks, project milestone tracking, and financial transparency requirements of the programme relationship.
This is a reporting design requirement above and beyond standard ERP functionality, but it is shaped by the ERP’s native project accounting, cost allocation, and management reporting capabilities. ERP systems with weaker project accounting modules require more customisation to meet Vision 2030 reporting requirements; those with stronger native project accounting produce a more reliable and maintainable solution.
UAE Corporate Tax and Multi-Jurisdiction Tax Architecture
The UAE federal corporate tax, effective June 2023, applies at 9% on taxable profits above AED 375,000. For GCC groups with UAE operating entities — which includes the majority of large regional conglomerates — the ERP needs to support UAE corporate tax calculation, multi-jurisdiction tax reporting (where group entities are subject to different tax regimes), and the transfer pricing documentation that inter-group transactions require.
This is an active requirement in 2026, not a future consideration. ERP systems whose UAE corporate tax configuration was still being developed at go-live of their clients’ implementations in 2024 and 2025 have created compliance gaps that their clients are managing through offline calculation. A system under evaluation should demonstrate a production-tested UAE corporate tax configuration, not a planned one.
Egypt ETA Mandate and Local Compliance Architecture
Egypt’s Electronic Tax Authority e-invoicing mandate applies to large and medium taxpayers and is progressively expanding. For Egyptian enterprises, the ERP must support ETA-compliant invoice generation and submission, Arabic-language invoice formatting to ETA standards, and integration with the ETA portal for electronic submission and status tracking.
Additionally, Egyptian statutory reporting under EGAAP has specific requirements for chart of accounts structure, financial statement presentation, and audit documentation that differ from IFRS in ways that the ERP’s localisation layer must accommodate. Vendors with limited Egypt-specific localisation investment — as distinct from Arabic-language support generally — typically produce implementations that require significant customisation to meet EGAAP and ETA requirements.
The Three ERPs: What They Are in 2026
Oracle Fusion Cloud ERP (Oracle Cloud ERP)
Oracle Fusion Cloud ERP is Oracle’s flagship cloud-native enterprise ERP — a full suite covering financials, procurement, project management, supply chain, HR, and manufacturing on Oracle Cloud Infrastructure. It is the successor to Oracle E-Business Suite (EBS) and Oracle PeopleSoft, and Oracle’s strategic direction for all ERP customers.
Oracle Fusion’s structural advantage in the GCC is ecosystem integration: it connects natively to Oracle EPM Cloud (Planning, FCCS, PCMCS, TRCS), Oracle Analytics Cloud (OAC), and Oracle’s broader supply chain and project management suite — which means organisations running Oracle ERP alongside Oracle EPM and Oracle Analytics have a genuinely integrated performance management environment rather than three products connected through custom integrations. For the significant proportion of large GCC enterprises already running Oracle EPM or Hyperion, this native integration is a material consideration.
Oracle’s ZATCA Phase 2 integration for Saudi Arabian entities is production-tested and ZATCA-certified. Oracle’s Arabic-language support in Fusion Cloud is mature — bilingual interface, Arabic transaction documents, Hijri calendar. Oracle’s UAE corporate tax localisation has been available since the tax’s introduction.
Oracle Fusion’s primary limitation is implementation complexity and cost: it is a deeply configurable, deeply integrated platform, and the configuration required to make it work for a specific organisation’s business processes — particularly in the GCC regional context — requires experienced Oracle Fusion consultants with genuine regional delivery experience. The shortage of that specific expertise in the GCC market is the most significant risk in an Oracle Fusion implementation.
SAP S/4HANA (Cloud and On-Premises)
SAP S/4HANA is SAP’s flagship ERP platform — the successor to SAP ECC — running on SAP’s in-memory HANA database and available both as cloud-hosted (SAP S/4HANA Cloud, both public and private) and on-premises deployment. SAP has the largest enterprise ERP installed base in the world and the deepest penetration in large Saudi enterprises, government-linked entities, and multinationals with GCC operations.
SAP’s structural advantage is maturity and depth: S/4HANA is the most functionally deep ERP platform across manufacturing, supply chain, and complex process industries. For Saudi enterprises with significant manufacturing, oil and gas, or industrial operations — where SAP’s industry-specific functionality has been refined over decades — S/4HANA provides capabilities that Oracle Fusion and Microsoft Dynamics 365 cannot match in those specific verticals.
SAP’s ZATCA Phase 2 integration is production-certified and broadly deployed across the Saudi enterprise market. SAP’s Arabic-language support is comprehensive and mature — SAP has been operating in the GCC market since the 1990s and the Arabic localisation reflects that depth. SAP’s UAE corporate tax and Egyptian ETA localisation are both available.
SAP’s primary limitations in the GCC context are cost and the ECC-to-S/4HANA migration pressure. SAP ECC support ends in 2027, and the migration to S/4HANA is a significant programme for the many large Saudi and UAE enterprises that implemented SAP ECC over the past fifteen years. The S/4HANA migration is not a version upgrade — it is a reimplementation on a different architecture, with data migration, process redesign, and change management requirements that are comparable in scope to a new ERP implementation.
Microsoft Dynamics 365 Finance and Operations
Microsoft Dynamics 365 Finance and Operations (D365 F&O) is Microsoft’s enterprise ERP — covering financials, supply chain, manufacturing, project management, and HR — hosted on Microsoft Azure and tightly integrated with Microsoft 365 (Teams, SharePoint, Power BI, Power Automate, Outlook).
Dynamics 365’s structural advantage in the GCC is Microsoft ecosystem integration and total cost of ownership at mid-market scale. For organisations that are already Microsoft 365 customers — using Azure, Teams, SharePoint, and Power BI — D365 F&O provides the most integrated technology environment, with Power BI as the native analytics layer, Power Automate for workflow automation, and Teams as the collaboration interface. The Microsoft-to-Microsoft integration reduces the custom integration engineering that connecting Oracle or SAP to the Microsoft productivity layer requires.
D365’s ZATCA Phase 2 integration for Saudi Arabia is available through Microsoft’s localisation and through certified third-party ZATCA connectors. The Arabic-language support in D365 F&O is functional — Arabic interface, Arabic transaction documents, Hijri calendar — though the maturity depth for complex GCC enterprise requirements is less than Oracle Fusion or SAP in specific areas. D365’s UAE corporate tax and Egypt ETA localisation are available.
D365’s primary limitation is functional depth for very large, complex enterprises: for organisations with highly complex supply chains, multi-tier manufacturing, or very large transaction volumes across many countries, D365 F&O has more implementation complexity and less native functional depth than SAP S/4HANA in the relevant verticals.
The Full Platform Comparison
| Evaluation Dimension | Oracle Fusion Cloud ERP | SAP S/4HANA | Microsoft Dynamics 365 F&O |
|---|---|---|---|
| ZATCA Phase 2 — production-certified, Saudi Arabia | Yes — Oracle-native ZATCA integration; production-certified; broad Saudi deployment | Yes — SAP-native ZATCA integration; most widely deployed across Saudi enterprises | Yes — via Microsoft localisation and certified third-party connector; growing Saudi deployment |
| ETA — Egypt e-invoicing integration | Yes — Oracle Egypt localisation; ETA integration available | Yes — SAP Egypt localisation; ETA integration available | Yes — Microsoft Egypt localisation; ETA integration via certified connector |
| Arabic-language UI — RTL interface depth | Strong — full RTL layout; bilingual interface; mature GCC Arabic UI | Strongest — deepest Arabic UI maturity of the three; 30+ years of GCC localisation investment | Good — Arabic interface available; RTL consistent; slightly less mature than Oracle/SAP for complex financial screens |
| Hijri calendar — statutory reporting | Yes — Hijri calendar native; Saudi statutory period support | Yes — Hijri calendar native; deepest Hijri integration of the three | Yes — Hijri calendar available; functional for Saudi statutory purposes |
| EGAAP — Egyptian statutory compliance | Yes — Egypt localisation covers EGAAP; chart of accounts structure | Yes — SAP Egypt EGAAP localisation available | Yes — D365 Egypt localisation; EGAAP coverage |
| UAE corporate tax — production-tested | Yes — Oracle UAE CT module; production deployments since 2023 | Yes — SAP UAE CT localisation; production deployments since 2023 | Yes — D365 UAE CT localisation available; production deployments |
| IFRS 18 readiness (effective Jan 2027) | Oracle roadmap includes IFRS 18 configuration; assessment engagement required for specific scope | SAP roadmap includes IFRS 18; industry-specific scope varies | Microsoft D365 roadmap includes IFRS 18; localisation timeline varies |
| Oracle EPM Cloud integration (PBCS, FCCS) | Native — direct integration; no custom pipeline required | Via certified connector or middleware; not native | Via middleware or Azure Data Factory; requires custom pipeline |
| SAP integration with BI / analytics | Via Oracle Analytics Cloud (native) or middleware to others | SAP Analytics Cloud is native; Oracle/Microsoft BI requires middleware | Power BI is native via Microsoft Fabric; Oracle/SAP BI requires middleware |
| Microsoft 365 / Teams / Power BI integration | Via Azure middleware; not native | Via Microsoft connectors; not native | Native — full Microsoft ecosystem integration; Power BI, Teams, SharePoint, Power Automate |
| Functional depth — manufacturing / industrial | Strong for process industries; less deep than SAP for discrete manufacturing at scale | Deepest — SAP’s primary strength; unmatched for complex manufacturing, oil and gas, mining | Good for mid-market manufacturing; less depth than SAP for complex industrial verticals |
| Functional depth — financial management | Strongest — Oracle Fusion Financials is the deepest finance module of the three | Strong — SAP Financial Accounting is mature and deep | Good — D365 Finance is comprehensive for most enterprise requirements |
| Project accounting — Vision 2030 programmes | Strong — Oracle Project Financial Management; mature for complex project accounting | Strong — SAP Project System; deep project accounting for large capital projects | Good — D365 Project Operations; adequate for mid-complexity project accounting |
| Multi-entity / GCC group consolidation | Strong — native integration with Oracle FCCS for group consolidation | Strong — integration with SAP Group Reporting; mature group consolidation | Good — integration with Dynamics consolidation module; less depth than Oracle FCCS or SAP Group Reporting at very large scale |
| ERP-to-EPM data flow for planning | Oracle Fusion → Oracle EPM: native, no middleware | SAP → Oracle EPM: certified connector; SAP → SAP Analytics: native | D365 → Oracle EPM: custom pipeline; D365 → Power BI: native |
| Implementation complexity — configuration scope | High — Oracle Fusion is deeply configurable; requires experienced Oracle Fusion consultants | High — SAP S/4HANA is deeply configurable; requires experienced SAP consultants | Moderate-High — D365 is configurable; Microsoft ecosystem familiarity reduces some complexity |
| Typical implementation timeline — mid-size enterprise | 12–22 months | 14–24 months | 10–18 months |
| Typical implementation cost — mid-size GCC enterprise | USD 400,000–1,200,000+ professional services | USD 500,000–1,500,000+ professional services | USD 280,000–800,000+ professional services |
| Annual licence cost (indicative, 200 users) | USD 150,000–400,000 | USD 180,000–450,000 | USD 100,000–280,000 |
| SAP ECC to S/4HANA — migration pressure | N/A | High — SAP ECC support ends 2027; all SAP ECC users face migration decision | N/A |
| Oracle EBS to Fusion — migration pressure | Moderate — EBS in extended support; Cloud Fusion is strategic direction | N/A | N/A |
| Partner ecosystem quality in GCC | Strong — significant Oracle Fusion partner base in KSA and UAE; quality varies | Strongest — largest and most experienced SAP partner ecosystem in the region | Growing — Microsoft partner base is large; D365 F&O finance specialists are less concentrated |
| Mid-market fit (500–2,000 employees) | Good — Oracle Fusion is full-enterprise but scalable down | Moderate — S/4HANA has a mid-market edition; implementation cost is the primary barrier | Strongest — D365 F&O is most cost-competitive at mid-market scale |
| Large enterprise / conglomerate fit (2,000+ employees, multi-entity) | Strong — Oracle Fusion + EPM + OAC is the most integrated enterprise performance stack | Strongest — SAP’s depth for large, complex enterprises is unmatched in manufacturing and industrial sectors | Good — adequate for most large enterprise requirements; depth ceiling is lower than Oracle or SAP for highest-complexity environments |
ERP Recommendation by Organisation Profile
Profile 1: Large GCC enterprise already running Oracle EPM or Hyperion
Oracle Fusion Cloud ERP — strong preference.
The native integration between Oracle Fusion and Oracle EPM Cloud — Planning, FCCS, PCMCS, TRCS — eliminates the custom middleware that connecting SAP or Dynamics to Oracle EPM would require. For organisations where the EPM layer is the finance function’s primary planning and reporting environment, this integration advantage is a material long-term operational benefit. The ERP-to-EPM actuals feed, the EPM-to-ERP budget writeback, and the consolidated reporting from FCCS all function more reliably on a native integration than on a middleware-mediated one. This is a recommendation based on systems architecture, not on Oracle brand preference.
Profile 2: Large Saudi or UAE enterprise with complex manufacturing, oil and gas, or industrial operations
SAP S/4HANA — strong preference in most cases.
SAP’s functional depth in manufacturing, supply chain, maintenance, and plant management is the highest of the three platforms — the product of four decades of development against the world’s most demanding industrial enterprises. For Saudi enterprises in petrochemicals, energy, manufacturing, and infrastructure — where the operational systems requirements are as significant as the financial management requirements — SAP’s vertical depth is a genuine differentiator. SAP’s ZATCA integration is also the most broadly deployed and most operationally mature in the Saudi market in 2026, which reduces go-live compliance risk.
The SAP ECC migration timeline adds urgency: organisations currently running SAP ECC who have not yet committed to an S/4HANA migration path should be actively planning it, because the 2027 support deadline is approaching faster than most GCC migration programmes are moving.
Profile 3: Microsoft 365 organisation, mid-market scale, non-industrial operations
Microsoft Dynamics 365 Finance and Operations — strong preference.
For organisations that are Microsoft-centric — with Azure infrastructure, Microsoft 365 productivity tools, Power BI as the analytics platform, and a finance team comfortable in Excel and Teams — D365 F&O provides the most integrated and lowest-total-cost-of-ownership ERP environment. The native Power BI integration eliminates the BI data pipeline engineering that Oracle or SAP would require. The Power Automate integration simplifies approval and workflow automation. The Azure hosting provides PDPL-aligned Saudi and UAE data residency with the Microsoft infrastructure the organisation already manages.
D365 is also the most cost-competitive at mid-market scale: the licensing model and implementation cost are meaningfully lower than Oracle Fusion or SAP S/4HANA for organisations with 200–1,500 users who do not require the highest-complexity vertical functionality that those platforms provide.
Profile 4: Egyptian enterprise — primary consideration
SAP S/4HANA or Oracle Fusion — with D365 relevant at mid-market.
Egypt’s ERP market has strong SAP and Oracle penetration among large enterprises, reflecting both vendors’ longstanding Egyptian operations and the depth of their EGAAP and ETA localisation. For large Egyptian enterprises with complex operations, both SAP and Oracle are well-established choices with mature local partner ecosystems.
Microsoft Dynamics 365 is the most appropriate choice for mid-market Egyptian enterprises that are Microsoft-centric and whose operational complexity does not require the full depth of SAP or Oracle. D365’s lower total cost of ownership is a meaningful advantage in the Egyptian market context.
Profile 5: Multi-country GCC group with mixed ERP history
Independent assessment required before any recommendation.
Organisations operating across Saudi Arabia, UAE, Qatar, Kuwait, and Egypt — with different entities potentially running different ERP systems or no ERP — present the most complex selection scenario and the one where independent advisory is most valuable. The decision involves not only platform fit but also the migration strategy for existing systems, the consolidation architecture across the group, the data governance requirements of multi-jurisdiction operation, and the sequencing of a programme that will run for two to four years.
A structured requirements definition exercise — conducted before vendor demonstrations, against the actual business requirements of the multi-entity group — is the only reliable basis for a selection decision in this scenario.
The SAP ECC and Oracle EBS Migration Decisions: What GCC Organisations Need to Know Now
SAP ECC: The 2027 Deadline and What It Means
SAP ECC mainstream maintenance ended in 2027. For the large number of Saudi, UAE, and Egyptian enterprises running SAP ECC — many of whom have been on SAP ECC for ten to fifteen years — this is not a future consideration. It is an active risk that requires a decision now.
The S/4HANA migration is not a version upgrade. SAP ECC and SAP S/4HANA have different data models, different process architectures, and different technical foundations. The migration requires a full reimplementation project — data migration, process redesign, custom development rebuild, integration redevelopment, and change management — at a scope and cost comparable to the original ECC implementation.
For GCC organisations on SAP ECC, the realistic migration timeline is 18 to 30 months for a mid-size enterprise and 30 to 48 months for a large multi-entity group. Organisations that have not started planning their S/4HANA migration are at material risk of an unplanned extended support extension — with its premium costs and increasing security risk — after 2027.
Oracle EBS: Extended Support and the Fusion Decision
Oracle E-Business Suite (EBS) is in extended support. Oracle’s strategic direction for all ERP customers is Oracle Fusion Cloud ERP. The situation parallels the Hyperion Planning extended support position for EPM customers.
The EBS to Oracle Fusion migration is similarly not a lift-and-shift. Oracle Fusion Cloud has a different architecture, a different data model, and different business processes from EBS. Customisations built on EBS — and most GCC EBS implementations carry significant customisation — need to be assessed individually: some can be replaced by native Fusion functionality, some need to be rebuilt in Fusion’s extension framework, and some no longer have a valid business requirement and should be retired.
For GCC organisations on Oracle EBS, the migration decision timeline is driven less by a hard support deadline and more by the widening gap between what Oracle is investing in (Fusion Cloud) and what is available on EBS (no new development). The organisations that migrate to Oracle Fusion Cloud now access the quarterly feature releases that are improving the platform continuously; those remaining on EBS are paying extended support fees for a platform that is not developing.
The ERP Selection Process: Seven Steps for GCC and Egyptian Organisations
The following process applies regardless of which platform is ultimately selected. It is the process that produces reliable selection decisions, as opposed to the accelerated process that produces vendor-shaped decisions.
Step 1: Define requirements independently before any vendor engagement. Specifically: how many legal entities, in which countries, under which GAAP bases, with which regulatory obligations (ZATCA, ETA, UAE CT), in which languages, connected to which EPM and analytics systems, with which Oracle or SAP or Microsoft heritage to migrate from. These answers constrain the selection before the vendor demonstrates anything.
Step 2: Include regional compliance requirements as mandatory evaluation criteria, not as checklist items. ZATCA Phase 2 integration — not “available” or “planned” but “certified and in production with these specific Saudi reference customers.” Arabic-language UI — not “supported” but “demonstrated live in a production environment matching our operational complexity.” These are binary pass/fail criteria for Saudi and Egyptian operations, not scoring dimensions.
Step 3: Build the total cost of ownership model from independent inputs, not vendor proposals. Professional services estimates from three independent implementation partners for the same scope. Oracle subscription or SAP/Microsoft licence modelled against your actual user count and module requirements. Integration costs for each ERP’s connection to your EPM and analytics platform. Arabic-language configuration scope. ZATCA and ETA integration scope. Post-go-live support model. Subtract the components vendors tend to understate before presenting to the board.
Step 4: Conduct a working session, not a demonstration. Ask each finalist vendor’s proposed delivery team — not the sales team — to work through one specific, complex requirement from your actual environment in real time. The quality of that session reveals delivery capability more reliably than any combination of reference sites, certifications, and slide presentations.
Step 5: Require implementation references specific to your scenario. For a Saudi enterprise: a ZATCA Phase 2 production reference with comparable industry and entity complexity. For a UAE holding company: a UAE corporate tax production reference with multi-jurisdiction structure. For an Egyptian enterprise: an EGAAP and ETA production reference. References that match your regulatory environment and structural complexity are informative; global references in different markets are not.
Step 6: Assess implementation readiness before committing to scope. Data quality in current systems. Process documentation maturity. Finance team capacity to participate in the implementation. Leadership commitment to the programme through its full duration. A readiness gap in any of these four areas will cost more to address mid-implementation than to close before the project begins.
Step 7: Design the ERP-to-EPM and ERP-to-analytics integration before finalising the ERP selection. The integration architecture between ERP, EPM, and analytics is a significant long-term cost driver. The platform combination that requires the least custom integration engineering for your specific EPM and analytics environment should be explicitly modelled in the TCO — not assumed to be comparable across platforms.
The Five Most Consequential ERP Selection Mistakes in the GCC and Egypt
1. ZATCA Integration Was Described as “Available” and Discovered as “In Development”
A Saudi enterprise selected an ERP based on the implementation partner’s confirmation that ZATCA Phase 2 integration was available. The contract was signed. The implementation began. Four months into the project, it emerged that the ZATCA integration for the specific ERP version and module combination in scope had not been certified by ZATCA and was still in active development by the vendor’s localisation team. The ZATCA integration was delivered eight months late, the go-live was delayed by six months, and the ZATCA compliance gap during that period required a manual submission workaround.
2. Arabic-Language Operation Was Confirmed and Not Demonstrated
A GCC group selected an ERP after the vendor confirmed Arabic-language support in the RFP response. The Arabic-language interface had not been demonstrated during the evaluation — only confirmed in writing. At UAT, the Arabic-language interface rendered most financial transaction screens with mixed RTL and LTR elements that the finance team found unusable. The Arabic-language configuration work required to produce a usable interface took twelve weeks of additional effort, added 18 percent to the implementation budget, and delayed go-live by ten weeks.
3. Oracle Fusion Was Selected Without Accounting for Oracle EPM Integration Cost for a Non-Oracle-EPM User
A UAE holding company selected Oracle Fusion for its financial management depth and its native Oracle EPM integration — despite running SAP Analytics Cloud as its analytics platform with no Oracle EPM in use. The EPM integration advantage they had prioritised in the selection did not apply to their environment. The integration between Oracle Fusion and SAP Analytics Cloud required a custom Azure Data Factory pipeline that cost USD 85,000 to build, took fourteen weeks to deliver, and required ongoing maintenance that was not in the original operating cost budget.
4. SAP S/4HANA Was Selected at Mid-Market Scale Where D365 Was the More Cost-Appropriate Choice
A mid-size Egyptian manufacturing enterprise selected SAP S/4HANA based on SAP’s market reputation and the recommendation of a Big Four implementation partner with a strong SAP practice. The total implementation cost exceeded the budget by 60 percent. The SAP S/4HANA implementation was technically successful. The annual maintenance and licence cost was 45 percent higher than a comparable Microsoft Dynamics 365 implementation would have been. The functional requirements of the business — standard financial management, basic manufacturing, and straightforward supply chain — did not require the depth that justified the SAP cost premium.
5. The ERP Was Selected Before the Multi-Entity Group’s Consolidation Architecture Was Defined
A GCC family conglomerate selected an ERP for the group’s primary operating entity. Two years later, the group decided to standardise ERP across all fifteen entities. The ERP selected for the primary entity was not the most appropriate choice for the holding company’s consolidation and multi-GAAP reporting requirements. The group now runs a heterogeneous ERP landscape — the selected ERP for some entities, legacy local systems for others — with a consolidation architecture that requires significant manual intervention at every close.
Frequently Asked Questions
Q: Which ERP is best for Saudi Arabia in 2026 — Oracle, SAP, or Microsoft Dynamics? The answer depends on three factors specific to the Saudi context. For large enterprises with complex manufacturing, oil and gas, or industrial operations — particularly those already running SAP — SAP S/4HANA is typically the most appropriate choice: its functional depth in these verticals is unmatched, its ZATCA integration is the most broadly deployed in the Kingdom, and its Arabic-language maturity reflects thirty years of Saudi market investment. For enterprises already running Oracle EPM — Hyperion Planning or Oracle Cloud EPM — Oracle Fusion Cloud ERP is the most architecturally coherent choice because the native ERP-to-EPM integration eliminates significant custom pipeline engineering. For Microsoft-centric organisations at mid-market scale with standard financial management requirements, Microsoft Dynamics 365 provides the lowest total cost of ownership and the most integrated Microsoft ecosystem experience. No single ERP is the best choice for all Saudi enterprises; the answer is determined by your specific operational complexity, existing technology landscape, and regulatory requirements.
Q: How much does an ERP implementation cost in the GCC? Professional services for an enterprise ERP implementation in the GCC range from approximately USD 280,000 for a focused Microsoft Dynamics 365 implementation at mid-market scale to USD 1,500,000 or more for a complex SAP S/4HANA implementation for a large multi-entity group. Oracle Fusion typically sits between these ranges at USD 400,000 to USD 1,200,000 for comparable scope. These figures are for professional services only; annual licence costs range from USD 100,000 to USD 450,000 depending on platform, user count, and module scope. The most consistently underestimated cost elements in GCC implementations are Arabic-language configuration, ZATCA and ETA integration scope, the post-go-live stabilisation period, and the cost of data migration from legacy systems.
Q: What does SAP ECC end of support mean for Saudi and UAE enterprises in 2026? SAP ECC mainstream maintenance ended in 2027. Enterprises remaining on SAP ECC after that date move to extended support — available until 2030 with customer-specific agreements — which carries premium maintenance costs and no new development. The practical implication for Saudi and UAE enterprises on SAP ECC is that the S/4HANA migration decision cannot be deferred much longer without committing to an extended support period of increasing cost. The S/4HANA migration is a full reimplementation — not a version upgrade — and the realistic timeline for a mid-size GCC enterprise is 18 to 30 months. Organisations that have not started the planning and scoping phase should start now to reach go-live before the extended support premium becomes the operating norm.
Q: Is Microsoft Dynamics 365 suitable for large GCC enterprises, or only for mid-market? Microsoft Dynamics 365 Finance and Operations is suitable for many large GCC enterprises — specifically those with financial management, standard supply chain, and project management requirements that do not involve the highest-complexity manufacturing, oil and gas, or industrial verticals where SAP’s depth is most differentiated. D365 is the right choice for large enterprises that are Microsoft-centric, whose operational complexity is within D365’s functional scope, and for whom the Microsoft ecosystem integration — Power BI analytics, Power Automate workflows, Teams collaboration — is a genuine operational value. It is not the right choice for large enterprises in complex industrial verticals where SAP’s thirty years of industry-specific development produces capabilities that D365 does not currently match.
Q: How long does an ERP implementation take in Saudi Arabia or the UAE? Realistic ERP implementation timelines for GCC enterprises: Microsoft Dynamics 365 for a mid-size enterprise — 10 to 18 months. Oracle Fusion for a mid-to-large enterprise — 12 to 22 months. SAP S/4HANA for a large enterprise — 14 to 24 months. Multi-entity group ERP standardisation programmes — 24 to 48 months. These timelines start from requirements sign-off, not from contract signature. The factors most consistently extending timelines in GCC implementations are data quality issues in source systems discovered after the project begins, Arabic-language configuration scope that was not explicitly included in the project plan, ZATCA or ETA integration complexity that was underestimated in the original scope, and organisational change management requirements that were not budgeted as a project workstream.
Q: Should we use Oracle, SAP, or Microsoft Dynamics 365 if we are already running Oracle EPM? If you are running Oracle EPM Cloud — Hyperion Planning, Oracle PBCS, FCCS, or PCMCS — Oracle Fusion Cloud ERP is the architecturally strongest choice for the ERP layer because the native integration between Oracle Fusion and Oracle EPM eliminates the custom middleware that connecting SAP or Microsoft Dynamics to Oracle EPM would require. The ERP-to-EPM actuals feed, the consolidated reporting from FCCS drawing on Oracle Fusion data, and the planning model in PBCS using Oracle Fusion actuals all function more reliably on a native integration than on a middleware-mediated connection. This is not a recommendation based on Oracle loyalty; it is a recommendation based on integration architecture. If other factors — functional depth requirements, existing SAP investment, Microsoft-centric environment — outweigh the integration advantage, the independent assessment should quantify the integration cost of each alternative before the selection is made.
About Loop Wise Solutions
Loop Wise Solutions is an enterprise performance consultancy based in Cairo, serving medium and large enterprises across Egypt, Saudi Arabia, the UAE, Qatar, and the broader Arab world. Our Business and Technical Consultancy practice provides independent ERP selection advisory — with no commercial arrangement with Oracle, SAP, Microsoft, or any ERP vendor or implementation partner.
Our ERP selection advisory engagements cover requirements definition, vendor evaluation framework design, total cost of ownership modelling, implementation partner evaluation, and readiness assessment — conducted before any vendor demonstration and constrained only by the client’s requirements and operating context. We have assessed and advised on Oracle Fusion, SAP S/4HANA, and Microsoft Dynamics 365 implementations across the GCC and Egypt, and our recommendations reflect that breadth of direct experience.
If you are making an ERP selection decision, managing an SAP ECC or Oracle EBS migration, or trying to understand whether a current ERP investment is delivering what it should, we are happy to have a direct conversation — starting with your requirements, not with a vendor’s demonstration.
Contact: Contact@loop-wise.com | Website: www.loop-wise.com
Where performance meets precision.
