Organisations running legacy ERP systems spend 70% of their IT budgets maintaining existing infrastructure rather than advancing transformation. When modernisation finally begins, they discover governance gaps, misaligned stakeholders, and process ambiguity that should have been identified months earlier. By that point, capital is already committed and the cost of course-correction is high.
If you are planning a Dynamics 365 implementation in Saudi Arabia, the answer to "where do I start?" is not a vendor demo, a module shortlist, or an implementation timeline. It is an honest assessment of whether your organisation is genuinely ready to transform.
The right sequence matters. Most implementations that struggle do not fail because of the software. They fail because the groundwork was never laid.
This guide covers the six steps every Saudi business should work through before going live on Dynamics 365:
- Assess organisational readiness
- Establish governance and stakeholder alignment
- Define scope and select modules
- Choose a partner with Saudi market experience
- Plan for ZATCA compliance and local regulatory requirements
- Structure your post-implementation support model
Each step builds on the last. Skipping the first one makes every step that follows harder and more expensive.
Why Most Saudi ERP Implementations Struggle Before They Begin
Saudi Arabia's ERP market is growing fast. The sector was valued at USD 416.7 million in 2024 and is projected to reach USD 1.6 billion by 2033, driven by Vision 2030 digitalisation mandates, ZATCA compliance pressure, and expanding industrial activity. That growth creates urgency, and urgency is where implementation programmes go wrong.
Organisations launch ERP projects under pressure from growth targets, regulatory deadlines, or boardroom directives. They move quickly into vendor selection and project scoping before the organisational foundations are in place. According to a PwC report on digital transformation in Saudi Arabia, 90% of respondents identified resource availability and timely decision support as key transformation challenges, with resistance to change cited by 80% and data availability issues by 70%.
The failure patterns that emerge are consistent:
- Weak governance: No clear executive ownership, decision-making authority, or accountability structure across departments.
- Fragmented requirements: Business units capture requirements independently, creating conflicts that surface mid-implementation.
- Poor data ownership: Nobody has defined who is responsible for master data quality before migration begins.
- Low stakeholder alignment: Finance, operations, IT, and compliance have different expectations of what the system will do.
- Underestimated localisation: ZATCA e-invoicing, Arabic language requirements, and VAT configuration are treated as configuration tasks rather than design decisions.
Industrial organisations face an additional layer of complexity. EPC companies, manufacturers, and oil and gas businesses typically operate across multiple entities, manage project-based revenue, run deep supply chains, and carry significant asset bases. Each of these dimensions adds implementation risk that a standard readiness assessment would surface, but that a rushed project start will miss entirely.
Step 1 - Assess Organisational Readiness Before Anything Else
Before you open a conversation with any implementation partner, before you request a product demonstration, and before you draft a project timeline, complete a structured readiness assessment. This is not a checklist exercise. It is a measurable evaluation of whether your organisation has the governance, alignment, and process clarity to support a transformation of this scale.
Alignyx is Terracez's AI-enabled ERP Readiness, Governance and Alignment platform, built specifically for this pre-commitment phase. It produces three core outputs that leadership can act on before any capital is committed.
Transformation Readiness Score (0-100)
A quantified assessment of organisational readiness across four dimensions: governance maturity, stakeholder engagement, process clarity, and transformation complexity. The score gives the board a single, defensible number to anchor the investment decision.
Why it matters: A score does not just tell you whether you are ready. It tells you exactly where the gaps are and what needs to be resolved before implementation begins. Organisations that enter implementation without this baseline regularly encounter the 30-50% budget overruns that characterise unprepared ERP transformations.
ERP Risk Heatmap Across Five Dimensions
A visual risk map that surfaces where implementation risk is highest across technical, organisational, process, governance, and programme complexity dimensions. It identifies the specific areas that need to be addressed before design work starts, not after the first project milestone slips.
Why it matters: Risk that is invisible at the start of a project does not disappear. It reappears as scope changes, timeline extensions, and cost overruns. Mapping it before commitment changes the decisions that follow.
Stakeholder Alignment Index
A measure of alignment across departments and entities. It identifies which business units are engaged, which are absent, and where the gaps between Finance, Operations, IT, and Compliance will create implementation conflicts if left unresolved.
Why it matters: In Saudi organisations with multi-entity structures or cross-functional operations, misalignment between departments is one of the most common reasons implementations stall. The Stakeholder Alignment Index makes that risk visible and addressable before it becomes a project dispute.
Together, these outputs give leadership the evidence base to make confident decisions about scope, sequencing, and investment, before a single implementation contract is signed.
Step 2 - Establish Governance and Stakeholder Alignment
Readiness assessment and governance design are not separate activities. Once you understand where the gaps are, the next step is building the structures that will carry the implementation forward. Alignyx structures this phase through a deliberate five-step workflow.
- Executive sponsor initiates. The CIO, CFO, or Digital Transformation Leader defines the scope of the assessment: which entities, which processes, which systems are in scope. This is the governance anchor point. Without a named executive sponsor, decisions stall and accountability fragments.
- Stakeholders are assigned and activated. Process owners across departments are formally assigned. The platform tracks participation from the start, giving leadership immediate visibility into who is engaged and who is not. Absent stakeholders at this stage are a reliable predictor of requirement gaps later.
- AI-guided discovery conversations. Rather than relying on workshops or manual interviews, the platform conducts structured conversations with process owners to capture operational challenges, current-state process flows, data quality issues, and regulatory requirements. The result is a consistent, auditable record of operational reality across every department.
- Insight structuring and conflict resolution. Requirements are organised into structured documentation. Conflicts between departments are surfaced and resolved collaboratively, before those conflicts become implementation disputes.
- Leadership dashboards. Executives receive real-time visibility into readiness metrics, stakeholder participation, decision progress, and emerging risks. Governance dashboards improve decision cadence and allow leadership to intervene before issues escalate.
In Saudi Arabia, where ERP decisions often cut across finance, operations, IT, and compliance functions simultaneously, this kind of structured governance is not optional. It is what determines whether the programme stays on track.
Step 3 - Define Your Scope and Select the Right Modules
Scope definition should follow readiness and governance work, not precede it. Organisations that define scope before they understand their processes, data quality, and stakeholder alignment consistently over-scope phase one, then spend the first six months of implementation renegotiating what was agreed.
The readiness phase produces a structured Business Requirements Document and a Gap-Fit Assessment that compare current-state processes against future-state requirements. These outputs are the correct starting point for module selection, not a vendor's feature checklist.
When defining scope for a Dynamics 365 implementation in Saudi Arabia, prioritise based on:
- Business priorities: Which operational areas carry the most risk or the highest potential for measurable improvement?
- Compliance obligations: ZATCA e-invoicing, VAT configuration, and Arabic localisation are non-negotiable. They belong in scope from day one.
- Operational pain points: Where are decisions being made in spreadsheets, manual workarounds, or disconnected systems?
- Future-state objectives: What does the organisation need the system to support in three to five years, not just at go-live?
For industrial organisations, this prioritisation is especially important. EPC companies, manufacturers, and oil and gas businesses often need to sequence carefully across finance, supply chain, project operations, field service, and asset management. Trying to implement all of these simultaneously in phase one is a common source of project failure. A validated scope, built on readiness outputs, prevents that mistake.
Step 4 - Choose a Partner With Saudi Market Experience
Partner selection is one of the most consequential decisions in a Dynamics 365 programme. It is also where many Saudi organisations focus too early, before they have the readiness data and validated scope that would allow them to evaluate partners meaningfully.
Once readiness and scope are clear, evaluate implementation partners against criteria that go beyond certifications and project portfolios.
- Governance capability: Can the partner structure executive governance, challenge unrealistic scope, and maintain programme discipline when internal pressures push for shortcuts?
- Saudi localisation knowledge: Does the partner have hands-on experience with ZATCA e-invoicing configuration, VAT setup, Arabic language requirements, and local regulatory processes, not just theoretical awareness?
- Industry depth: For EPC, manufacturing, or oil and gas environments, does the partner understand the operational complexity of project-based work, multi-entity structures, and asset-intensive operations?
- Support model: What happens after go-live? A partner who cannot clearly describe their post-implementation support model is a partner who has not thought past the delivery milestone.
Terracez operates the Microsoft Catalyst programme in Saudi Arabia, one of the few partners in the GCC executing these programmes locally. The Catalyst framework is designed to align transformation strategy with business outcomes before implementation begins, which makes it a natural complement to the readiness-led approach described in this guide.
Step 5 - Plan for ZATCA Compliance and Local Regulatory Requirements
Saudi Arabia's regulatory environment adds a layer of design complexity that cannot be treated as a post-implementation configuration task. Compliance requirements must be built into the initial scope and design decisions, not retrofitted after go-live.
ZATCA E-Invoicing
ZATCA's Phase 2 integration requirements have been in effect since January 2023 and are being rolled out in waves by taxpayer group. Wave 24, announced by ZATCA, requires VAT-registered businesses with turnover exceeding SAR 375,000 to integrate their e-invoicing solution with the Fatoora Portal by 30 June 2026. Phase 2 mandates real-time clearance of B2B tax invoices and reporting of B2C simplified invoices within 24 hours.
Dynamics 365 Finance includes a dedicated Saudi Arabian ZATCA submission feature that handles API endpoint configuration, Cryptographic Stamp Identifiers (CSIDs), QR code import, and submission workflows. This configuration must be completed as part of the implementation design, not added on afterwards.
Arabic Language Localisation
Per ZATCA's Detailed Guidelines for E-Invoicing, invoices must be presented in Arabic. Additional languages may be included, but Arabic is mandatory. Dynamics 365 supports Arabic language interfaces and localised reporting formats, but these must be configured and tested as part of the implementation scope.
VAT Configuration
Saudi VAT setup in Dynamics 365 requires correctly structured sales tax codes, sales tax groups, and item tax groups. For retail and point-of-sale environments, the prices-include-tax setting must reflect Saudi requirements. VAT configuration is a design decision, not a deployment checkbox.
The practical implication: any partner or implementation plan that treats these three areas as late-stage tasks is creating avoidable risk. Compliance design belongs in the readiness and scoping phase.
Step 6 - Structure Your Post-Implementation Support Model
Post-implementation support is not something to negotiate after go-live. It should be defined before implementation begins, so the organisation knows from day one who owns stabilisation, enhancement requests, user training, and issue resolution.
This matters more in Saudi Arabia than in many other markets. Regulatory requirements evolve. ZATCA continues to expand Phase 2 waves and update technical specifications. Arabic localisation and VAT rules require ongoing attention. Organisations that go live without a clear support model find themselves dependent on ad-hoc fixes, reverting to spreadsheet workarounds, and losing confidence in the system within months of launch.
A structured support model for a Dynamics 365 implementation should cover:
- Stabilisation support: Dedicated resource to resolve issues in the first 60-90 days after go-live, when user adoption pressure is highest.
- User adoption and training: Ongoing training aligned to role-based workflows, not a one-off pre-launch session.
- Regulatory updates: A defined process for applying ZATCA, VAT, and localisation changes as they are issued.
- Ongoing optimisation: A mechanism for capturing enhancement requests, prioritising them, and delivering improvements systematically.
Terracez provides Dynamics 365 support services with structured SLAs and a ticketing model designed for organisations that need consistent, accountable support after implementation. Defining this engagement before go-live, rather than after, is part of what a readiness-led programme looks like in practice.
How Terracez Guides Saudi Businesses Through Every Step
The sequence described in this guide is not theoretical. It is the order in which decisions actually need to be made: readiness first, then governance, then scope, then partner selection, then compliance design, then support planning. Each step depends on the one before it.
Terracez supports Saudi businesses across the full length of this journey, from the initial readiness assessment through strategy definition via the Microsoft Catalyst programme, through implementation, and into ongoing Dynamics 365 support. Every engagement starts with Alignyx because readiness is not assumed. It is measured.
The difference between a successful implementation and a costly failure in Saudi Arabia is rarely technology. It is preparation. Terracez starts every engagement with Alignyx to make sure your organisation is genuinely ready.
If you are planning a Dynamics 365 implementation in Saudi Arabia and want to understand where your organisation stands before committing budget, request an Executive Discussion with the Terracez team.
.webp)
