In brief: Plan a Dynamics 365 implementation in Saudi Arabia from scope and team design through data, localisation, testing, training, go-live and support.
Implementing Microsoft Dynamics 365 in Saudi Arabia is not the same as rolling it out anywhere else. The Kingdom's regulatory environment — ZATCA e-invoicing mandates, 15% VAT reporting, Saudization (Nitaqat) requirements, and Arabic language obligations — means that a generic implementation playbook will leave critical gaps. Get those gaps wrong and you face compliance penalties, failed audits, and a system your teams simply will not use.
The good news: Dynamics 365 has deep, built-in localisation for Saudi Arabia. The platform supports ZATCA Phase 2 e-invoicing integration, Arabic UI, VAT at 15%, and Hijri calendar support out of the box. The challenge is configuring and sequencing those capabilities correctly from day one.
This guide walks through every stage of a successful Dynamics 365 implementation in KSA, from pre-project planning through go-live and post-launch optimisation.
Key facts before you start:
- ZATCA's 24th group of taxpayers (VAT revenues above SAR 375,000) must comply with Phase 2 e-invoicing integration no later than 30 June 2026
- Microsoft's Success by Design framework is the recommended methodology for all Dynamics 365 projects
- The average mid-market Dynamics 365 implementation in the region runs 4 to 9
Understanding the Saudi Arabia Business Context
Before a single configuration decision is made, your implementation team needs to understand the regulatory and cultural landscape. Saudi Arabia's business environment has distinct characteristics that directly affect how Dynamics 365 should be set up.
Regulatory Requirements That Affect Your D365 Configuration
Requirement
What It Means for Your Implementation
ZATCA Phase 2 e-invoicing
D365 Finance must be configured to integrate with the FATOORA platform, generating XML-format invoices with digital signatures and QR codes
VAT at 15%
Tax codes, reporting structures, and the chart of accounts must reflect Saudi VAT rules from day one
Saudization (Nitaqat)
HR modules must track Saudi national employment ratios by entity and activity sector
Data residency
Microsoft Azure's UAE North and Qatar regions serve KSA; confirm your data residency requirements with your legal team
Arabic language
System UI, reports, invoices, and customer communications must support Arabic as a primary language
Hijri calendar
Date fields used in HR, payroll, and official documents often need Hijri calendar support
Vision 2030 as a Tailwind
Saudi Arabia's Vision 2030 programme is actively driving digital transformation investment across both public and private sectors. Organisations that align their Dynamics 365 implementation with Vision 2030 goals — automation, data-driven decision-making, reduced reliance on manual processes — tend to secure stronger internal buy-in and, in some cases, government-backed incentives for technology investment.
The practical implication: frame your implementation business case around measurable outcomes (reduced reporting
Step 1: Define Your Scope and Choose the Right Modules
The most common implementation mistake in KSA is trying to go live with every module at once. Dynamics 365 is a suite, not a single product. Attempting a full deployment across Finance, Supply Chain, HR, Sales, and Customer Service simultaneously almost always results in delays, budget overruns, and poor adoption.
Which Modules Are Most Relevant for Saudi Businesses?
Dynamics 365 Finance & Operations (F&O) is a single, unified ERP product. Within it, you activate and configure functional modules based on your business needs. The key modules relevant to Saudi organisations are:
- Finance - Covers general ledger, accounts payable/receivable, fixed assets, VAT reporting, and ZATCA e-invoicing integration. This is the core module every KSA implementation starts with.
- Supply Chain Management - Handles procurement, inventory, warehouse management, and order fulfilment. Critical for manufacturing, retail, and distribution organisations.
- Human Resources - Manages employee records, leave and absence, and payroll integration. Essential for Saudization (Nitaqat) ratio tracking and Saudi Labour Law compliance.
- Project Operations - Covers project costing, billing, and resource management. Relevant for professional services, contracting, and government project-based businesses.
- Budgeting and Financial Reporting - Advanced budget control and consolidation capabilities, often prioritised by larger organisations with multi-entity structures.
All of these operate within the same F&O environment, sharing a single data model, chart of accounts, and security framework. Activating a new module does not require a separate deployment — it is a configuration and licensing decision.
The Implementation Journey: Learn, Orient, Evolve
Terracez structures Dynamics 365 F&O implementations around the LEO framework — a three-stage delivery model designed to keep implementations focused, measurable, and aligned with real business outcomes rather than technology milestones.
Learn — Define your business KPIs and OKRs before a single configuration decision is made. This stage maps the implementation against what the organisation actually needs to achieve: ZATCA compliance, faster financial close, better procurement visibility, or Saudization reporting accuracy. Well-defined KPIs prevent scope creep and give the project team a clear definition of success.
Orient — Configure and deploy D365 F&O with agility, not rigidity. This is where the system is set up, localised for Saudi Arabia, integrated with existing platforms, and validated against your defined KPIs. The Orient stage covers everything from ZATCA e-invoicing configuration and VAT setup through to data migration, UAT, and go-live cutover.
Evolve — Go-live is not the finish line. The Evolve stage ensures the organisation adapts to changing business needs, adopts new F&O capabilities as Microsoft releases them, and extends the platform — whether through Power BI reporting, Power Automate workflows, or additional functional areas — without disrupting core operations.
This cycle is continuous. A well-implemented F&O system should be evolving 12 months post go-live, not sitting static.
Critical decision point: If your organisation has VAT-liable revenues exceeding SAR 375,000, ZATCA Phase 2 compliance is not optional. Your Finance module configuration must include the Saudi Arabian Zatca submission feature (version 14 or later) before go-live.
Step 2: Build Your Implementation Team
A Dynamics 365 project fails or succeeds based on who is in the room, not just which software is being deployed. Microsoft's implementation guidance is clear on this: misaligned roles and vague statements of work are among the leading causes of project failure.
Core Team Roles and Responsibilities
Executive Sponsor
Owns the business case, resolves escalations, and ensures budget and resource commitment.
Project Manager
Provides day-to-day delivery oversight, manages timelines, scope, and stakeholder communication.
Solution Architect
Designs the overall technical architecture and makes decisions on customisation versus configuration.
Functional Consultants
Configure modules according to business requirements, including Finance, Supply Chain, HR, and CRM.
Technical Consultants / Developers
Build integrations, customisations, and data migration scripts.
Business Subject Matter Experts
Internal process owners who validate that the system reflects real business workflows.
Change Management Lead
Manages user adoption, training, and communication—often the most underestimated role in an ERP implementation.
The Partner Selection Question
For Saudi Arabia specifically, your implementation partner needs to demonstrate three things beyond general Dynamics 365 certification:
- ZATCA compliance experience - Have they configured Phase 2 e-invoicing integrations for Saudi clients? Ask for reference cases.
- Arabic localisation depth - Can they deliver bilingual training, Arabic reports, and Arabic-language UAT documentation?
- Local regulatory knowledge - Do they understand Nitaqat, Saudi Labour Law implications for HR configuration, and data residency requirements?
A partner who has only delivered D365 projects in Europe
Step 3: Plan Your Data Migration Strategy
Data migration is where implementations quietly go wrong. Most organisations in KSA are migrating from a legacy ERP, a collection of spreadsheets, or an older on-premise system. The quality of your migrated data will directly determine how useful Dynamics 365 is from day one.
The Four-Stage Data Migration Process
1. Audit and cleanse your source data Before mapping anything to D365, audit what you actually have. Duplicate vendor records, inconsistent customer data, and historical transactions with missing VAT information are common in organisations that have been running on legacy systems for years. Clean data in, clean data out.
2. Map to Dynamics 365 data structures Each module has a defined data model. Customer records, vendor accounts, item masters, chart of accounts, and open balances all need to be mapped from your source system format to the D365 structure. This is where functional consultants earn their fees.
3. Use Microsoft's Data Migration Toolkit Microsoft provides a Data Migration Toolkit for Dynamics 365 that includes templates, tools, and guides for common migration scenarios. Use it. It enforces data accuracy and completeness standards that reduce post-go-live data quality issues.
4. Run parallel testing in a sandbox environment Never migrate directly to production. Run full migration tests in a sandbox, validate outputs against your source records, and have business users sign off on data accuracy before go-live. This step is non-negotiable.
KSA-Specific Data Considerations
- Historical VAT records must be migrated accurately; ZATCA audits can cover prior periods
- Arabic and English dual-language records for customers, vendors, and items where both are
Step 4: Configure Saudi Arabia Localisation Settings
This is the section most generic guides skip entirely. Getting localisation right is not a cosmetic exercise; it is the difference between a compliant system and a liability.
ZATCA Phase 2 E-Invoicing Configuration
ZATCA's Phase 2 integration phase requires businesses to connect their invoicing systems directly to the FATOORA platform. In Dynamics 365 Finance, this involves:
- Onboarding with ZATCA to obtain Cryptographic Stamp Identifiers (CSIDs) — both Compliance CSIDs (CCSID) for testing and Production CSIDs (PCSID) for live transactions
- Importing the Saudi Arabian Zatca submission (SA) feature (version 14 or later) from the Globalization Studio repository
- Configuring the FATOORA API endpoint in the Feature parameters tab, including the ZatcaNumberSequence and response type mappings
- Setting up QR code generation for tax invoices, which ZATCA generates upon clearance and must be imported back into Finance
- Testing in ZATCA's compliance environment before deploying to production
Important: Businesses with revenues above SAR 375,000 in 2022, 2023, or 2024 face a Phase 2 compliance deadline of no later than 30 June 2026 (24th taxpayer group). Starting your implementation now gives adequate time to configure, test, and onboard properly.
VAT Configuration
Saudi Arabia applies VAT at 15% with specific rules for exempt supplies, zero-rated exports, and reverse charge mechanisms. Your chart of accounts and tax groups must reflect these distinctions. Common errors include:
- Applying standard 15% VAT to zero-rated export transactions
- Missing reverse charge configuration for imported services
- Incorrect VAT group assignments on item masters
Arabic Language and Bilingual Reporting
Dynamics 365 supports Arabic as a UI language and enables bilingual document printing (Arabic and English on the same invoice or report). This requires configuring language-specific templates for customer invoices, purchase orders, and financial statements. Do not leave this to post-go-live; bilingual invoices are a business expectation in
Step 5: Testing, Training, and Change Management
Going live with a technically correct system that nobody uses is a failed implementation. This stage is where the return on investment is either secured or squandered.
Testing Strategy
Run three levels of testing before go-live:
- Unit testing - Individual configuration elements tested by functional consultants as they build
- Integration testing - End-to-end process flows tested across modules (e.g. purchase order through to VAT-compliant invoice to ZATCA submission)
- User Acceptance Testing (UAT) - Business users test real scenarios from their daily workflows and sign off that the system meets requirements
For Saudi Arabia, UAT must specifically include:
- ZATCA e-invoice generation, submission, and QR code return
- VAT return report accuracy across transaction types
- Arabic document printing and bilingual invoice output
- Saudization ratio reporting (if HR module is in scope)
Training Delivery
Training in Saudi Arabia needs to be delivered bilingually. English-only training materials are not sufficient for organisations where a significant portion of the workforce operates in Arabic. Practical, role-based training sessions (not generic system walkthroughs) are far more effective at driving adoption.
Recommended training approach:
- Role-based sessions by department (Finance team, operations team, HR team)
- Hands-on practice in the sandbox environment before go-live
- Quick reference guides in both Arabic and English
- Designated "super users" in each department who can support colleagues post-launch
Change Management: The Real Risk
The technical implementation is rarely what causes a Dynamics 365 project to underdeliver. Resistance to change, lack of executive communication, and poor user adoption are the actual culprits. Involve department heads from the discovery phase, communicate clearly about what is changing and why, and treat the go-live as the beginning of adoption, not the end of the project.
Step 6: Go-Live and Post-Implementation Support
Go-live is a milestone, not a finish line. The first 30 to 90 days after launch are when real-world usage reveals gaps that testing did not catch.
Cutover Planning
A structured cutover plan prevents the most common go-live disasters:
- Define a clear cutover date and freeze period for legacy system transactions
- Migrate opening balances and outstanding transactions on a specific date
- Run the legacy system in parallel for a short period (typically 2 to 4 weeks) to validate that D365 outputs match
- Have your implementation partner on standby during the first week of live operations
Post-Go-Live Priorities for KSA
ZATCA monitoring - The first live ZATCA submissions should be monitored closely. Verify that invoices are being cleared by FATOORA, QR codes are returning correctly, and no submission errors are occurring. Address any API issues immediately; ZATCA non-compliance carries financial penalties.
VAT return preparation - The first VAT return period after go-live is the real test of your Finance configuration. Review the VAT report outputs against your accountant's expectations before submission.
User adoption tracking - Monitor system usage by department. Low login rates or high error rates in specific areas signal training gaps that need to be addressed quickly, before bad habits become entrenched.
Ongoing Optimisation
Dynamics 365 releases major updates twice a year (release waves). Organisations that treat go-live as the end of the project miss the ongoing value that these updates deliver. Build a post-go-live roadmap that includes:
- Regular review of new features relevant to your industry
- Expansion into additional modules as the team becomes confident
- Power BI integration for advanced reporting and management dashboards
- Power Automate workflows to eliminate manual processes identified after go-live
Common Implementation Pitfalls to Avoid
Across Dynamics 365 projects in the Gulf region, the same mistakes appear repeatedly. Knowing them in advance is one of the most cost-effective ways to reduce project risk.
Skipping ZATCA Onboarding Early
Many teams focus heavily on functional configuration and leave compliance activities until the end of the project. This often causes unexpected delays because ZATCA onboarding has dependencies and approval processes that require time. To avoid this issue, begin ZATCA onboarding activities in parallel with system configuration.
Over-Customising the System
Business users sometimes expect Dynamics 365 to replicate every aspect of their legacy system. This can lead to excessive customisations, increased costs, and future upgrade challenges. Before considering custom development, evaluate whether standard Dynamics 365 functionality can meet the requirement. Customise only when there is no suitable standard solution.
Treating the Implementation as an IT Project
A common mistake is allowing the IT department to drive the project without sufficient business ownership. ERP implementations are business transformation initiatives, not just technology deployments. Appoint business subject matter experts as co-owners and ensure User Acceptance Testing (UAT) is led by business teams rather than IT alone.
Underestimating Data Quality Issues
Data migration problems frequently emerge because organisations postpone data audits or skip them altogether to save time. In reality, data cleansing and validation often require more effort than expected. Conduct a comprehensive data audit alongside the design phase to identify and resolve issues early.
English-Only Documentation
Project teams often create documentation exclusively in English to accelerate delivery. However, this can reduce user adoption and training effectiveness in multilingual organisations. Establish bilingual training materials, user guides, and UAT scripts from the beginning of the project.
No Post-Go-Live Support Plan
Many organisations allocate their entire budget to implementation activities and overlook the support period after go-live. As a result, users struggle with unresolved issues during the critical transition phase. Include a dedicated hypercare period of at least three months within the project budget to ensure a smoother adoption process.
The customisation trap deserves special attention. It is tempting to configure D365 to mirror exactly how your legacy system worked. The better approach is to use the implementation as an opportunity to adopt Microsoft's recommended process flows, which are based on industry best practices. Heavy customisation increases upgrade complexity and long-term maintenance costs significantly.
Where to Start: Your First 30 Days
If you are at the very beginning of this journey, the first 30 days should focus on three things, not twenty.
Week 1-2: Internal alignment Secure executive sponsorship, define the business case with measurable outcomes, and identify your internal project champion. Without these in place, no implementation partner can save the project.
Week 2-3: Partner selection Issue a shortlist of certified Microsoft Dynamics 365 partners with demonstrable KSA experience. Evaluate them on ZATCA compliance delivery, Arabic localisation capability, and reference clients in your industry or a comparable sector.
Week 3-4: Discovery and scoping Engage your selected partner for a structured discovery workshop. The output should be a clear scope document covering: which modules, which business processes, data migration requirements, ZATCA compliance obligations, and a realistic project timeline with milestones.
Rushing past these steps to get into configuration faster is the single most reliable way to create a project that runs over time, over budget, and under-delivers on adoption.
Terracez is a certified Microsoft Dynamics 365 and Power BI partner based in Dubai, serving organisations across the Gulf region including Saudi Arabia. With experience across agile implementations, compliance
This guide walks through every stage of a successful Dynamics 365 F&O implementation in KSA, from pre-project planning through go-live and post-launch optimisation.
Key facts before you start:
- The average mid-market Dynamics 365 F&O implementation in the region runs 4 to 9 months depending on scope and data complexity
Before a single configuration decision is made, your implementation team needs to understand the regulatory and cultural landscape. Saudi Arabia's business environment has distinct characteristics that directly affect how Dynamics 365 F&O should be set up.
Requirement
What It Means for Your Implementation
ZATCA Phase 2 e-invoicing
VAT at 15%
Saudization (Nitaqat)
HR modules must track Saudi national employment ratios by entity and activity sector
Data residency
Arabic language
Hijri calendar
The practical implication: frame your implementation business case around measurable outcomes (reduced reporting time, improved VAT compliance, lower operational costs) rather than technology features alone.
The most common implementation mistake in KSA is trying to go live with every functional area at once. Dynamics 365 F&O is a single, unified ERP product — but attempting to configure all functional areas simultaneously almost always results in delays, budget overruns, and poor adoption.
Executive Sponsor
Responsibility: Owns the business case, resolves escalations, and ensures budget and resource commitment.
Project Manager
Responsibility: Provides day-to-day delivery oversight, manages timelines and scope, and coordinates stakeholder communication.
Solution Architect
Responsibility: Designs the overall technical architecture and determines when to use standard configuration versus custom development.
Functional Consultants
Responsibility: Configure Dynamics 365 modules to align with business requirements across Finance, Supply Chain, HR, and other functional areas.
Technical Consultants / Developers
Responsibility: Build integrations, customizations, extensions, and data migration scripts required for the implementation.
Business Subject Matter Experts
Responsibility: Represent internal business processes and validate that the configured system accurately reflects real-world workflows.
Change Management Lead
Responsibility: Drives user adoption, training, and communication efforts throughout the project. This role is frequently underestimated despite its significant impact on implementation success.
- Arabic and English dual-language records for customers, vendors, and items where both are required
- Hijri date conversions for historical HR and contract records
- Open purchase orders and invoices from the legacy system need careful cutover planning to avoid double-posting
- Testing in ZATCA's compliance environment before deploying to production
VAT Configuration
- Applying standard 15% VAT to zero-rated export transactions
- Missing reverse charge configuration for imported services
- Incorrect VAT group assignments on item masters
Dynamics 365 supports Arabic as a UI language and enables bilingual document printing (Arabic and English on the same invoice or report). This requires configuring language-specific templates for customer invoices, purchase orders, and financial statements. Do not leave this to post-go-live; bilingual invoices are a business expectation in Saudi Arabia, not a nice-to-have.
Testing Strategy
Run three levels of testing before go-live:
For Saudi Arabia, UAT must specifically include:
- ZATCA e-invoice generation, submission, and QR code return
- VAT return report accuracy across transaction types
- Arabic document printing and bilingual invoice output
- Saudization ratio reporting (if HR module is in scope)
Training Delivery
Recommended training approach:
- Role-based sessions by department (Finance team, operations team, HR team)
- Hands-on practice in the sandbox environment before go-live
- Quick reference guides in both Arabic and English
- Designated "super users" in each department who can support colleagues post-launch
Cutover Planning
A structured cutover plan prevents the most common go-live disasters:
- Define a clear cutover date and freeze period for legacy system transactions
- Migrate opening balances and outstanding transactions on a specific date
- Have your implementation partner on standby during the first week of live operations
- Regular review of new features relevant to your industry
- Expansion into additional functional areas as the team becomes confident
- Power BI integration for advanced reporting and management dashboards
- Power Automate workflows to eliminate manual processes identified after go-live
Common Implementation Pitfalls to Avoid
Across Dynamics 365 F&O projects in the Gulf region, the same mistakes appear repeatedly. Knowing them in advance is the cheapest form of risk management.
Pitfall
Why It Happens
How to Avoid It
Skipping ZATCA onboarding early
Teams focus on functional config and leave compliance to the end
Start ZATCA onboarding in parallel with configuration; it takes time and has dependencies
Over-customising the system
Business users want D365 to replicate the legacy system exactly
Map requirements to standard capabilities first; customise only when there is no standard solution
Treating it as an IT project
IT teams drive the project without sufficient business process ownership
Appoint business SMEs as co-owners; UAT must be led by the business, not IT
Underestimating data quality issues
Data audits are delayed or skipped to save time
Run the data audit in parallel with design; it always takes longer than expected
English-only documentation
Project teams default to English for speed
Mandate bilingual training materials and UAT scripts from the start
No post-go-live support plan
Budget is exhausted at go-live
Include a minimum 3-month hypercare period in the project budget
Week 3-4: Discovery and scoping Engage your selected partner for a structured discovery workshop. The output should be a clear scope document covering: which functional areas, which business processes, data migration requirements, ZATCA compliance obligations, and a realistic project timeline with milestones.
Terracez is a certified Microsoft Dynamics 365 and Power BI partner based in Dubai, serving organisations across the Gulf region including Saudi Arabia. With experience across agile implementations, compliance-driven rollouts, and Microsoft Catalyst programmes, Terracez brings the regional expertise that KSA implementations require. Contact the Terracez team to discuss your implementation requirements and get a structured project
A CEO and steering-committee starting checklist
- Agree the three to five outcomes the implementation must deliver.
- Name accountable process, data, technology and change owners.
- Separate mandatory Saudi localisation from optional process improvement.
- Assess data, integrations and decision gaps before fixing the price.
- Define stage gates for design, testing, readiness and go-live.
Score readiness before locking scope
Rate stakeholder alignment, process maturity, data quality, integration clarity, change capacity and governance on a consistent scale. Low scores should become funded preparation actions, not hidden implementation assumptions.
Use phased delivery gates
Each phase should produce an approved output: discovery creates the scope and risk baseline; design creates process and solution decisions; build creates tested configuration; deployment creates trained users and cutover evidence; stabilisation creates service ownership and an optimisation backlog.
.png)
%201.avif){kind=avatar}
.png)
.png)
.webp)
