Who this is for: CFOs, Finance Directors, COOs, and Operations Leads in Saudi Arabia and the UAE evaluating Dynamics 365 implementation partners.
What it addresses: How to choose an implementation approach that reduces operational complexity, protects compliance, and produces measurable ROI — rather than creating more process debt than the legacy system it replaced.
Why implementation approach matters more than software selection: Dynamics 365 is a capable platform. Saudi Arabia already accounts for 21.8% of the Dynamics 365 footprint across Gulf markets, with the region recognised as the fastest-growing Dynamics 365 market globally. The platform is not in question. What determines whether a business ends up with simpler operations or greater complexity is how the implementation is sequenced, and whether the partner starts with business readiness or with software configuration.
This page explains the implementation approach that produces genuine process optimisation, the failure points that destroy ROI, what Saudi and UAE buyers should expect from a credible partner, and how to evaluate your options before committing to scope.
Why do Dynamics 365 projects simplify operations in some businesses and create more complexity in others?
The honest answer is that the software is rarely the variable. The variable is what the business looked like before configuration started.
Dynamics 365 is designed around structured processes, clear ownership, and defined data flows. When a business has those things, implementation accelerates them. When it does not, the platform exposes every gap at scale. Approval chains that were informal become bottlenecks. Reporting that was approximate becomes disputed. Reconciliation that was manageable becomes a weekly escalation.
"Treat Dynamics 365 as a way to improve a business process, not just deploy software." — Expert consensus from Dynamics 365 optimisation practice guidance
For a CFO evaluating implementation options, the question is not whether Dynamics 365 can handle finance, operations, or procurement. It can. The question is whether the implementation model will protect your ROI or quietly transfer your existing process problems into a more expensive, harder-to-change system.
The complexity trap most implementations fall into
A badly sequenced ERP programme typically follows the same pattern. A partner scopes modules, proposes a build timeline, and begins configuration before the business has agreed on process ownership, decision rights, or what "good" looks like in the new operating model. Workarounds appear during testing. Customisations are added to accommodate unclear processes. Go-live happens, but the business is running two systems in parallel for months because the new one does not yet reflect how work actually gets done.
The result is not simplification. It is a more expensive version of the original problem, with a software licence attached.
This is not a technology failure. It is a sequencing failure. And it is entirely avoidable when the implementation approach starts with business readiness rather than software configuration.
What should Saudi and UAE buyers expect from a proper Dynamics 365 implementation approach?
A credible implementation partner should be able to address all of the following before discussing module scope or build timelines. If a partner moves straight to configuration without covering these areas, that is a risk signal, not a sign of efficiency.
Why Saudi requirements deserve specific attention
ZATCA Phase 2 e-invoicing is not optional for affected taxpayers. Wave 23 applied to businesses with VAT revenues above SAR 750,000 from March 2026. Wave 24 extended compliance to businesses above SAR 375,000 by June 2026. Onboarding is mandatory and requires a Cryptographic Stamp Identifier from ZATCA before the system can generate compliant invoices. Any implementation that defers this to a post-go-live phase creates direct compliance and invoice validity risk.
How does Terracez approach business process optimisation before Dynamics 365 configuration starts?
Most implementation partners begin with a requirements workshop and a module list. Terracez begins earlier, with an assessment of whether the organisation is ready to transform. Technology configuration comes third, not first.
The delivery model follows four structured phases:
Phase 1: Transformation readiness and intelligence
Before any implementation scope is agreed, Terracez assesses the organisational foundations that determine whether a Dynamics 365 programme will succeed or stall.
This phase covers:
- Executive alignment and shared understanding of transformation intent
- Transformation governance: decision rights, accountability, and steering structure
- Operating model clarity: how the business intends to work after go-live
- Process ownership: who is accountable for each workflow and outcome
- Data readiness: quality, completeness, and migration risk
- Value measures: what success looks like in business terms, not project terms
The output is a Transformation Readiness Report that identifies risks, governance gaps, and the organisational conditions that need to be in place before configuration starts. This is the step most implementations skip. It is also the step that explains most post-go-live failures.
Phase 2: Business architecture and process design
With readiness established, Terracez works with business leaders and process owners to map current-state workflows, identify bottlenecks, and design the future-state operating model.
"Map baseline processes first and identify bottlenecks, rework, approvals, and data handoffs." — Dynamics 365 implementation practice guidance
This phase defines KPIs, control points, escalation paths, and cross-functional governance before a single screen is configured. It also determines where standard Dynamics 365 functionality fits the business model, and where low-code orchestration or integration is genuinely needed, rather than defaulting to customisation.
Phase 3: Dynamics 365 implementation
Only after the business foundations are established does configuration begin. Dynamics 365 is configured to support the agreed operating model, not to replicate the legacy system. Localisation requirements (ZATCA integration, Saudi VAT, UAE VAT, Arabic outputs, multi-entity controls) are treated as core scope, not post-go-live additions.
Phase 4: Adoption and value realisation
Go-live is the beginning of value creation, not the end of the project. Terracez tracks user adoption, process compliance, and business KPIs after deployment. If adoption is weak or a process is not performing as designed, that is identified and addressed through structured post-go-live review rather than left to accumulate as technical debt.
The Transformation Intelligence Framework: what it is and why it shapes every Dynamics 365 engagement
The four phases above are not a generic project methodology. They are grounded in the Transformation Intelligence Framework, a proprietary 15-domain model that Terracez uses to assess, govern, and execute enterprise transformation with measurably reduced risk.
The Framework operates on a single premise: the organisational conditions that determine transformation success exist long before implementation begins. Technology configuration is one domain. The other fourteen address the leadership, governance, and operational foundations that technology depends on.
The 15 domains are:
Strategic foundations
- Business Vision
- Transformation Strategy
- Executive Leadership
- Transformation Governance
Operational foundations
- Business Architecture
- Operating Model
- Business Processes
- People and Culture
Technical and data foundations
- Data
- Technology
- Artificial Intelligence
Execution and value
- Execution Management
- Benefits Realisation
- Continuous Intelligence
- Executive Decision Intelligence
In a Dynamics 365 engagement, the Framework is applied in Phase 1 to identify which of these domains are ready and which carry risk. A business with strong executive alignment and clear process ownership will implement faster and realise value sooner than one that starts configuration before those foundations are in place. The Framework makes that assessment explicit rather than leaving it to assumption.
The Framework is operationalised through Alignyx, the Terracez Transformation Intelligence Platform. Alignyx provides continuous visibility into transformation health, readiness signals, governance maturity, and value realisation progress throughout the programme lifecycle. For CFOs and Finance Directors, this means the programme's risk profile is visible before scope is agreed, not surfaced as an escalation after go-live.
This is documented further in the Execution Transformation Advisory methodology.
UAE e-invoicing and PINT AE: what Dynamics 365 users need to address before January 2027
For UAE businesses, e-invoicing is not a future consideration. It is an active compliance programme with hard deadlines, financial penalties, and operational dependencies that go well beyond enabling a software feature.
The UAE Ministry of Finance has mandated structured electronic invoicing under the PINT AE standard. The phased rollout is already under way:
Source: UAE Ministry of Finance, Ministerial Decision No. 244 of 2025. Confirm the latest deadline at theMinistry of Finance e-invoicing portalbefore acting on any partner's slide deck.
What PINT AE actually requires from your Dynamics 365 environment
PINT AE is the UAE localisation of the Peppol International Invoice model. Compliance requires structured XML invoice data, not a PDF. Every in-scope B2B and B2G transaction must be transmitted through a Ministry of Finance-accredited Service Provider (ASP), not directly from the ERP to the FTA.
Dynamics 365 Finance includes built-in UAE e-invoicing functionality from the 2026 Wave 1 release (public preview from July 2026, general availability from December 2026). This handles PINT AE XML generation and ASP communication for sales orders, free-text invoices, and project invoices. It does not, however, make the business compliant on its own. An external, MoF-accredited ASP is still required for validation, Peppol network transmission, and FTA reporting.
Dynamics 365 Business Central has no native UAE e-invoicing module. Compliance requires a custom AL extension mapping all 51 mandatory PINT AE fields and a separately configured ASP connection.
The five operational dependencies most businesses underestimate
The compliance risk for UAE businesses on Dynamics 365 is not whether Microsoft supports PINT AE. It is whether the organisation has enough time to address the operational foundations before enforcement begins.
- Master data quality. PINT AE requires complete, accurate supplier and customer identifiers, VAT registration numbers, Peppol Participant IDs, and line-level tax codes. Poor master data does not get corrected by the ASP. It generates rejected invoices.
- ASP selection and onboarding. Every in-scope business must appoint a Ministry of Finance-accredited, Peppol-certified ASP. For businesses above AED 50 million revenue, the ASP appointment deadline is 30 October 2026. Onboarding, certification testing, and integration with Dynamics 365 takes time. Starting this in Q4 2026 creates delivery risk.
- Exception handling design. The operating model must define what happens when an invoice is rejected, delayed, or inconsistent. Rejection queues, ownership, correction workflows, resubmission rules, and financial reconciliation all need to be designed before go-live, not discovered afterwards.
- Multi-entity and free zone complexity. Businesses operating across multiple legal entities, free zone and mainland jurisdictions, or intercompany billing arrangements must map e-invoicing scope and ASP connectivity independently for each entity. A single ASP configuration does not automatically cover group structures.
- End-to-end testing. Testing must cover more than a standard domestic invoice. Credit notes, cancellations, discounts, multiple tax treatments, foreign currency, advance payments, and rejection scenarios all need to be validated before the pilot window closes.
Penalties for non-compliance
Under Cabinet Decision No. 106 of 2025, businesses face AED 5,000 per month for failure to appoint an ASP, plus AED 100 per invoice (capped at AED 5,000 per calendar month) for late transmission. Penalties do not apply to voluntarily issued invoices before the mandatory go-live date, which makes the July 2026 pilot window a valuable testing opportunity for businesses that use it.
What this means for businesses implementing Dynamics 365 now
If your Dynamics 365 implementation is currently in scope or under evaluation, UAE e-invoicing readiness should be treated as primary implementation scope, not a post-go-live phase. The implementation partner should be able to confirm which version of Dynamics 365 Finance supports the UAE e-invoicing feature, how PINT AE fields will be mapped and approved, how ASP selection and onboarding will be managed, and what test scenarios will be executed before go-live.
For a full readiness checklist and implementation sequence, the Terracez UAE e-invoicing guide for Dynamics 365 covers each step in detail.
What failure points usually destroy ROI in Dynamics 365 transformation programmes?
Understanding where implementations go wrong is more useful than a list of features. These are the patterns that consistently produce poor outcomes, and the conditions that make each one more likely.
The compliance risk is not theoretical
For Saudi businesses, ZATCA Phase 2 compliance is a live operational requirement. The integration demands are specific: XML or PDF/A-3 with embedded XML format, digital signatures, real-time clearance or reporting depending on invoice type, and mandatory ZATCA onboarding to obtain the Cryptographic Stamp Identifier before any compliant invoice can be generated. A Dynamics 365 implementation that does not address this from the start creates direct invoice validity risk.
For UAE businesses, the e-invoicing mandate takes effect from January 2027 for large companies and July 2027 for smaller entities. That makes 2026 the preparation window. Businesses implementing Dynamics 365 now have the opportunity to build UAE e-invoicing readiness into the initial scope rather than retrofitting it under deadline pressure.
If your current or planned implementation has not addressed these compliance requirements as primary scope items, the Terracez go-live recovery guide for UAE and KSA businesses outlines the remediation path.
How should buyers evaluate cost, timeline, and implementation scope?
Implementation cost and timeline are not fixed variables. They are outputs of decisions made before scope is agreed. Buyers who understand the real drivers are better positioned to evaluate proposals and avoid the change requests that appear after contracts are signed.
Cost drivers
Timeline drivers
For smaller Business Central scopes, implementations in the region typically run two to four months. Enterprise Finance and Operations programmes with multi-entity structures, ZATCA integration, and complex data migration run considerably longer. The variable that most buyers underestimate is not partner capacity — it is internal decision speed, process clarity, and availability of business owners for design workshops and testing.
A proposal with an aggressive timeline but no readiness assessment is usually making assumptions about your organisation's readiness that will surface as delays or change requests later. The Terracez fixed-price proposal guide explains what to check before accepting a scoped proposal.
Key point: The cheapest proposal is rarely the lowest-risk one. Scope assumptions hidden in a low headline figure typically reappear as change requests, extended timelines, or post-go-live remediation costs.
What does a good partner-selection framework look like for CFOs and finance leaders?
Partner selection based on presentation quality and reference calls is not sufficient for a programme of this complexity. Use a structured scorecard that weights the criteria most relevant to your risk profile.
The most important question to ask any partner is this: do you start with a software demo, or with an assessment of our business risk, process ownership, and operating model? The answer tells you everything about their delivery philosophy.
For a deeper view of how to evaluate and select a Dynamics 365 partner in the region, the Terracez partner selection guide covers the failure patterns and the criteria that distinguish partners who deliver outcomes from those who deliver go-lives.
Why industry context changes the implementation approach, and what that means for Saudi and UAE buyers
Business process optimisation is not a generic exercise. The complexity of the problem, the sequencing of priorities, and the compliance dependencies all differ significantly by industry. In Saudi Arabia and the UAE, that is compounded by geopolitical and economic context: Vision 2030 sector priorities, localisation mandates, government procurement requirements, and the operational realities of industries that are simultaneously scaling and transforming.
A Dynamics 365 implementation designed for a professional services firm will not transfer directly to a construction EPC group or a manufacturing conglomerate. The processes are different. The governance structures are different. The compliance obligations, reporting requirements, and data complexity are different.
The table below outlines the primary operational challenges by industry and what a transformation-first Dynamics 365 implementation should address before configuration begins.
Why this matters for the implementation approach
The industry context determines which processes need to be redesigned before configuration begins, which compliance obligations are primary scope rather than optional add-ons, and where the highest-risk data and integration dependencies sit.
A construction group implementing Dynamics 365 without designing its project billing, subcontractor approval, and retention workflow before configuration starts will end up customising the platform to replicate its existing complexity rather than improving it. A holding group that does not design intercompany eliminations and entity-level controls upfront will face consolidation disputes every reporting cycle.
The Terracez Transformation Intelligence Framework is applied at the industry level, not just the organisational level. The 15 domains are assessed against the specific operating model of the business, so the readiness gaps that matter for an EPC contractor are not the same as those that matter for a distribution group. Industry context is not a marketing claim. It is a variable that changes what the implementation needs to address before a single screen is configured.
For industry-specific implementation guidance, the Terracez industries page covers primary sectors across Saudi Arabia and the UAE.
Why Terracez for Dynamics 365 implementation in Saudi Arabia and the UAE
Terracez is a Microsoft Solutions Partner for Business Applications. The distinction worth understanding is not the certification. Most regional partners hold one. The distinction is the delivery philosophy.
Terracez operates as an Execution Transformation Advisory. That means every Dynamics 365 engagement begins with a structured assessment of organisational readiness, executive alignment, and business architecture before implementation scope is agreed. Technology configuration follows business design. Go-live is treated as the start of value creation, not the conclusion of the project.
For buyers in Saudi Arabia and the UAE, this matters for specific reasons:
- ZATCA and VAT compliance is treated as primary implementation scope, not a post-go-live consideration
- Process ownership and governance are defined before configuration begins, reducing scope drift and decision delays
- Multi-entity and group reporting requirements are designed into the operating model, not bolted on after
- Adoption and value realisation are tracked after go-live through structured post-deployment review
The Alignyx platform supports this by providing continuous visibility into transformation health, readiness signals, and value realisation progress throughout the programme lifecycle.
The real promise is not a faster build. It is a lower-risk path to measurable business outcomes, with fewer post-go-live surprises than a software-first implementation would produce.
Frequently asked questions
How long does a Dynamics 365 implementation take in Saudi Arabia or the UAE?
Timeline depends on scope, not just partner capacity. Smaller Business Central implementations typically run two to four months. Enterprise Finance and Operations programmes with multi-entity structures, ZATCA integration, and data migration from legacy systems run longer. The most common cause of timeline overrun is not technical complexity — it is internal decision speed, unclear process ownership, and data that was not assessed before scope was agreed.
Does Dynamics 365 support ZATCA Phase 2 e-invoicing for Saudi businesses?
Yes. Dynamics 365 Finance supports Saudi e-invoicing including clearance and reporting workflows, XML and PDF/A-3 with embedded XML formats, digital signatures, and ZATCA system integration. However, this requires proper configuration of the Saudi legal entity, tax registration, and ZATCA onboarding to obtain the Cryptographic Stamp Identifier. It is not active by default and must be scoped as primary implementation work.
Is Dynamics 365 ready for the UAE e-invoicing mandate?
Dynamics 365 Finance includes built-in UAE e-invoicing functionality from the 2026 Wave 1 release, supporting PINT AE XML generation and ASP communication. However, compliance also requires appointing a Ministry of Finance-accredited ASP, completing PINT AE field mapping, and validating master data quality. Businesses with annual revenue above AED 50 million must appoint an ASP by 30 October 2026 and go live by 1 January 2027. Dynamics 365 Business Central has no native UAE e-invoicing module and requires a custom AL extension. Starting preparation now is strongly advisable to avoid deadline risk.
What is the difference between Saudi and UAE localisation in Dynamics 365?
Saudi localisation centres on ZATCA e-invoicing compliance, Saudi VAT configuration, and Arabic document requirements. UAE localisation addresses UAE VAT, bilingual reporting in some workflows, and preparation for the UAE e-invoicing mandate effective from January 2027 for large companies. Both markets require entity-level configuration; neither is covered by a generic Middle East setup.
How much customisation is advisable in a Dynamics 365 implementation?
As little as possible. Standard configuration should be exhausted before low-code orchestration is considered, and low-code should be used before custom code is introduced. Every customisation adds build cost, testing effort, and long-term upgrade risk. Customisation that compensates for unclear processes is particularly expensive — it locks in the problem rather than solving it.
What does a Terracez transformation readiness assessment include?
The assessment covers executive alignment, transformation governance, operating model clarity, process ownership, data readiness, localisation and compliance requirements, and value measures. The output is a Transformation Readiness Report with identified risks, governance gaps, and recommended conditions for implementation to proceed. It is designed to be completed before implementation scope is finalised, not after a contract is signed.
Request a transformation readiness assessment
Before finalising your Dynamics 365 scope, understand what your implementation actually requires.
A Terracez transformation readiness assessment identifies:
- Implementation risks specific to your organisation and operating model
- Business process gaps that need to be resolved before configuration begins
- ZATCA, VAT, and localisation requirements relevant to your entity structure
- Governance and ownership gaps that typically cause scope drift and delays
- Value measures and success criteria for the programme
Request your assessment. No obligation, no sales process. A structured conversation with a senior Terracez advisor about your transformation priorities and what a lower-risk implementation path looks like for your business.
.webp)
