Dynamics 365 Readiness Assessment for EPC Contractors in the UAE and Saudi Arabia

Most EPC contractors evaluating Dynamics 365 ask the wrong question. They ask: "Can Dynamics 365 handle EPC?" The answer is yes, and most implementation partners will tell you so within the first ten minutes of a discovery call. The question that actually determines whether your programme succeeds or fails is different: Is your organisation ready to implement it in a way that changes how your commercial, procurement and finance teams actually work?

The evidence from the GCC market is stark. According to the PwC Middle East 2025 Capital Projects and Infrastructure Survey, 81% of regional project respondents experienced cost overruns in the past year. The root causes were not technology failures. They were poor capital planning, weak subcontractor governance and compliance gaps. Panorama Consulting's 2025 research places the broader ERP failure rate at approximately 68%, with Gartner citing a 55 to 75% range for projects that fail to meet their stated objectives. In the UAE and Saudi Arabia specifically, regional data shows that 70% of ERP projects are classified as challenged or failed, with average cost overruns of AED 1.3 million to AED 2.1 million and average delays of five to six months.

The technology is rarely the problem. The organisation almost always is.

This article gives EPC commercial, finance and project leaders a structured readiness framework covering the six domains that determine whether a Dynamics 365 implementation delivers genuine project control or simply adds a more expensive layer of complexity to existing problems. For a detailed view of what Dynamics 365 can do for EPC operations once your organisation is ready, see our guide to Dynamics 365 for EPC and Contracting Companies in the UAE and Saudi Arabia.

Who this is for: CFOs, commercial directors, project directors and procurement leaders at EPC and contracting firms in the UAE and Saudi Arabia who are evaluating Dynamics 365 or preparing to begin an implementation programme.

What EPC readiness actually means

Readiness is not a checklist your IT team completes before go-live. It is the organisational state that determines whether Dynamics 365 will be adopted by the people who need to use it every day: quantity surveyors, procurement managers, commercial directors and project accountants.

An EPC firm that goes live on Dynamics 365 without readiness will experience one or more of the following within the first six months:

• QS teams reverting to parallel spreadsheets because the system does not reflect how they raise and track CVRs
• Procurement teams bypassing approval workflows because thresholds were configured without understanding how the business actually approves spend
• Finance teams unable to close the period because project cost accruals were not mapped correctly to WBS elements
• Subcontractor payment disputes because retention and milestone controls were not configured before go-live

None of these are platform problems. They are readiness problems. And every one of them is preventable.

Terracez uses the Alignyx Transformation Intelligence Platform to assess EPC organisational readiness before a single line of Dynamics 365 configuration is written. The six domains below reflect the readiness dimensions that most consistently separate successful EPC implementations from the ones that stall.

Domain 1: Commercial Process Ownership

Before any Dynamics 365 configuration begins, your organisation must answer a set of commercial governance questions that have nothing to do with technology. When these questions surface during user acceptance testing instead of a readiness workshop, they become costly delays. When they surface after go-live, they become adoption failures.

The core questions that must be answered before configuration:

• Who owns the variation order process from instruction to approved budget revision?
• Who approves a purchase requisition above AED 500,000 or SAR 500,000?
• Who authorises a subcontractor payment application before it is submitted for payment?
• Who releases subcontractor retention, and against which contractual trigger?
• Who is accountable for the cost-to-complete estimate on each active project?
• Who approves a change to the project WBS structure once a project is live?

These are not IT questions. They are commercial governance questions. If your commercial director, QS lead, procurement manager and project accountant give different answers to any of these, your Dynamics 365 configuration will reflect one person's assumption rather than your organisation's agreed operating model.

The process ownership matrix

A practical readiness tool is a simple process ownership matrix that maps each EPC commercial workflow to a named owner, an approver and a system role before configuration begins.

If this matrix cannot be completed in a single workshop with the relevant stakeholders, it is a readiness signal. It means the commercial governance model is not yet defined clearly enough to configure a system that enforces it.

Readiness indicator: If your organisation can complete this matrix in a two-hour workshop with full stakeholder agreement, your commercial process ownership is ready for Dynamics 365 configuration. If it takes three sessions and still has open items, resolve those before scoping begins.

Domain 2: Variation Order and Contract Control Readiness

Variation orders are the single most common cause of margin erosion in GCC EPC contracting. Paul Hastings' 2026 EPC market analysis identifies uncontrolled scope change as a primary driver of financial strain across the region, particularly on FIDIC-based contracts where entitlement must be substantiated with documented evidence before a variation can be approved.

Dynamics 365 can enforce a structured variation order workflow. But only if your organisation has defined that workflow before configuration begins.

What variation order readiness requires

1. A defined variation order register

Your organisation must have a consistent register format for all variations, including instruction date, scope description, value estimate, approval status, contract entitlement basis and budget impact. If this register currently lives in multiple spreadsheets maintained by different project teams, it must be consolidated and standardised before it can be migrated into Dynamics 365.

2. A clear entitlement and approval chain

For each variation type, the approval chain must be defined: who raises the instruction, who assesses entitlement, who approves the budget revision and who notifies the client. On FIDIC contracts, the time limits for notification are contractual obligations. Your Dynamics 365 configuration should enforce those time limits through automated workflow notifications.

3. A separation between instructed and approved variations

One of the most common EPC accounting errors is absorbing uninstructed or unapproved variations into project costs before entitlement is confirmed. Dynamics 365 must be configured to hold unapproved variations as contingent commitments, not posted costs. This requires a clear policy decision before configuration, not a default setting.

Variation readiness self-assessment

Answer these questions before your implementation begins:

• Do all active projects use the same variation order numbering and classification system?
• Is there a single agreed process for raising, assessing and approving a variation across all project teams?
• Are variation registers currently reconciled against the contract sum at least monthly?
• Does your finance team know which variations are instructed, which are approved and which are disputed at any given time?
• Is there a defined time limit for variation notification built into your commercial management procedures?

If you answered no to two or more of these, your variation control process is not ready for Dynamics 365 configuration. The system will enforce whatever process you configure. If that process is inconsistent, the system will enforce inconsistency at scale.

Terracez assessment point: During an EPC Readiness Assessment, Terracez reviews your current variation register format, approval chain and contract administration procedures against the Dynamics 365 change-order configuration requirements. This identifies the process gaps that must be resolved before scoping begins.

Domain 3: Subcontractor Retention and Payment Control Readiness

In GCC EPC projects, subcontracted scope typically represents 60 to 80% of total project cost. That makes subcontractor payment governance the highest-value financial control in any EPC Dynamics 365 implementation. It is also the area where the most costly configuration errors occur when readiness has not been assessed.

Dynamics 365 supports milestone-based payment releases, automatic retention withholding and back-to-back billing controls. But these features require specific inputs from your organisation before they can be configured correctly.

The three subcontractor payment controls that must be defined pre-configuration

Retention percentage and release triggers

Saudi EPC contracts typically carry 5 to 10% retention clauses. UAE contracts vary by employer and contract type. Before configuration, your organisation must define:

• The retention percentage for each subcontract category
• Whether retention is withheld on labour, materials or both
• The contractual trigger for retention release: practical completion, defects liability expiry, client retention release or a combination
• Whether partial retention releases are permitted and under what conditions

If different project teams currently apply retention differently, this must be standardised before Dynamics 365 is configured. The system will apply one rule set. That rule set must reflect your agreed commercial policy.

Milestone payment conditions

Subcontractor payments released against progress milestones require your organisation to define what constitutes a completed milestone. This sounds straightforward. In practice, it creates disputes when the definition is ambiguous. Before configuration, define:

• Who verifies milestone completion (QS, project manager or site supervisor)?
• What documentation is required before a payment application is approved?
• What is the maximum number of days between milestone verification and payment release?
• How are partial milestone completions handled?

Back-to-back billing alignment

Back-to-back billing prevents paying a subcontractor before recovering the equivalent amount from the employer. This is a critical cash-flow protection mechanism. For Dynamics 365 to enforce it, your organisation must map each subcontract payment application to the corresponding employer progress claim. This mapping must be defined at the subcontract administration level before configuration, not assumed by the system.

Subcontractor data readiness

Beyond process design, subcontractor payment configuration requires clean data. Before implementation, you need:

• A complete subcontractor register with agreed scope, contract value, payment terms and retention percentage for every active subcontract
• A current status of all outstanding payment applications, approved milestones and withheld retention
• A record of all variation orders raised against each subcontract agreement
• Vendor master data in a format compatible with Dynamics 365 vendor records

If your subcontractor register is currently maintained across multiple project files with no central reconciliation, data cleansing is a pre-implementation requirement, not a post-go-live activity.

Request an EPC Readiness Assessment: Terracez conducts a structured review of your subcontractor payment processes, retention policies and subcontract data before recommending a Dynamics 365 implementation scope.

Domain 4: Project Data and Master Data Readiness

Data readiness is the domain that EPC firms most consistently underestimate. It is also the one that most frequently causes go-live delays. According to regional ERP implementation data, 41% of UAE projects and 39% of Saudi projects cite data quality issues as a primary implementation failure factor.

For EPC businesses, the data challenge is more complex than for most industries because project data is multi-dimensional. It spans contracts, WBS structures, cost codes, subcontract agreements, vendor records, procurement commitments and compliance classifications. Each dimension must be clean, consistent and mapped to the Dynamics 365 data model before configuration can be completed.

The five EPC data categories that must be assessed before implementation

1. Project and WBS structure

Every active project must have a defined Work Breakdown Structure before it can be migrated into Dynamics 365. This means:

• A consistent WBS hierarchy agreed by commercial, engineering and finance teams
• Cost codes mapped to each WBS element
• Budget allocations confirmed at the WBS level, not just the project total
• A naming convention that will be applied consistently across all projects

If your WBS structures currently vary by project or by project manager, standardisation is a pre-implementation requirement.

2. Contract and subcontract master data

For each active contract and subcontract, you need:

• Contract reference, value, payment terms and retention percentage
• Current approved contract sum including all agreed variations
• Subcontract scope description and agreed deliverables
• Performance bond and insurance details

3. Vendor and supplier master data

Your vendor register must be cleansed before migration. This includes removing duplicate vendor records, confirming bank details, validating tax registration numbers (TRN for UAE, VAT registration for Saudi Arabia) and classifying vendors by ICV status where required for ADNOC-related contracts.

4. Procurement commitments

All open purchase orders and subcontract payment applications must be captured as committed costs against the relevant project and WBS element before go-live. If these commitments are not migrated, your cost-to-complete position will be incorrect from day one.

5. Historical cost data

For projects that are already in progress at the time of go-live, you need a confirmed opening balance for each project that reconciles:

• Costs incurred to date by WBS element
• Revenue recognised to date
• Retention withheld and outstanding
• Committed costs not yet invoiced

Data readiness assessment framework

If your QS and finance teams cannot produce a reconciled opening balance for each active project within two weeks, your data is not ready for implementation. This is not a technical problem. It is a commercial reporting discipline problem that must be resolved before go-live.

Domain 5: GCC Compliance Architecture Readiness

EPC firms operating across the UAE and Saudi Arabia are not managing two versions of the same regulatory environment. They are managing two distinct compliance frameworks simultaneously. This distinction must be designed into the Dynamics 365 architecture before configuration begins. Retrofitting compliance requirements into a live system is significantly more complex and costly than building them in from the start.

UAE compliance requirements for EPC firms

PINT AE e-invoicing (2027 deadline)

The UAE e-invoicing mandate requires structured digital invoices for all B2B transactions in PINT AE format. For EPC firms issuing high-value progress invoices, this affects every subcontractor payment application, client invoice and intercompany transaction. Dynamics 365 must be configured with a PINT AE-compatible connector before go-live. This is not a standard out-of-the-box capability.

In-Country Value (ICV) tracking

Contractors working on ADNOC-related projects must track and report ICV-qualifying procurement spend. This requires Dynamics 365 procurement data to be configured to classify vendors by ICV status and tag qualifying purchases separately. ICV reporting is a contractual obligation on many UAE public-sector and energy-sector EPC contracts.

Wage Protection System (WPS)

For EPC firms with large site-based workforces, payroll integration must align with UAE WPS requirements. This affects how labour costs are posted against projects and how payroll data flows into the finance module.

Saudi Arabia compliance requirements for EPC firms

ZATCA Phase 2 e-invoicing

All VAT-registered businesses in Saudi Arabia must integrate with ZATCA's Fatoora platform for real-time clearance of B2B invoices. For EPC firms with VAT revenue above SAR 375,000, integration was required by June 2026. Dynamics 365 must be configured with a ZATCA-certified connector. This is a specialist configuration requirement, not a standard Dynamics 365 feature.

Nitaqat labour compliance

Saudi projects require tracking the ratio of Saudi national employees under the Nitaqat programme. This must be built into HR and project resourcing workflows, which affects how project labour costs are classified and reported.

Hijri calendar and bilingual documentation

Project documentation and official correspondence on Saudi contracts frequently requires Hijri calendar dates alongside Gregorian dates. Bilingual document output in Arabic and English is a standard configuration requirement for Saudi EPC operations.

Compliance readiness checklist

Key insight: The compliance layer is the one domain where a wrong decision before go-live cannot be easily corrected after. A ZATCA connector that is not certified will not pass ZATCA validation. A PINT AE format that is not correctly structured will not be accepted by the UAE authority. These decisions must be made at the architecture stage, with a partner who has delivered compliant implementations in both jurisdictions.

Terracez has delivered Dynamics 365 implementations with ZATCA Phase 2 and UAE e-invoicing compliance for enterprise clients across Saudi Arabia and the UAE. Our compliance architecture review is a standard component of the EPC Readiness Assessment.

Domain 6: Commercial Team Adoption Readiness

The most common failure point in EPC Dynamics 365 implementations is not the finance module. It is the commercial function. Regional data shows that 46% of UAE ERP projects and 44% of Saudi ERP projects cite low user adoption as a primary failure factor. In EPC specifically, the adoption risk is concentrated in the teams that the system is most designed to serve: quantity surveyors, procurement managers and project accountants.

These teams fail to adopt ERP systems for a predictable reason. The system was not configured to match how they actually work. It was configured to match how the implementation team assumed they work. The distinction matters because QS workflows, CVR formats and procurement approval habits are often deeply embedded in individual practice rather than documented procedure.

The four adoption risks specific to EPC commercial teams

1. QS teams reverting to parallel CVR spreadsheets

If Dynamics 365 does not produce a CVR report that matches the format your QS team currently uses, they will continue to produce it manually outside the system. The CVR format must be agreed with the QS team before configuration begins, not presented to them at user acceptance testing.

2. Procurement teams bypassing approval workflows

Procurement approval workflows configured with incorrect thresholds or approval chains will be bypassed within weeks of go-live. The most common cause is that the configured workflow reflects the organisation chart rather than how procurement decisions are actually made on live projects.

3. Project managers not posting costs against WBS elements

If the WBS structure is not intuitive to project managers, costs will be posted against the project total rather than the correct WBS element. This destroys the granularity that makes Dynamics 365 valuable for EPC cost control.

4. Finance teams maintaining shadow ledgers

When commercial teams do not trust the system data, finance teams maintain shadow ledgers to reconcile against. This creates a parallel reporting environment that defeats the purpose of the implementation.

What adoption readiness looks like before go-live

Adoption readiness is not about training volume. It is about system configuration that matches commercial reality. Before go-live, your implementation should include:

• CVR report format agreed with QS lead and signed off before UAT
• Procurement approval thresholds validated against actual approval practice, not the delegation of authority document alone
• WBS naming conventions reviewed and approved by at least three project managers
• A commercial team change management plan that addresses resistance, not just training attendance
• A defined parallel-run period with clear criteria for when the legacy system is switched off

Terracez adoption approach: The Alignyx platform continuously monitors adoption signals throughout the implementation lifecycle, not just at go-live. This means adoption risks are identified and addressed during configuration, not discovered six months after the system went live. It is one of the most significant differentiators between a Terracez EPC implementation and a standard Dynamics 365 go-live.

If your implementation plan does not include a commercial team adoption assessment before UAT, it is missing the highest-risk element of an EPC Dynamics 365 programme.

The EPC Readiness Assessment: What Terracez Reviews Before Scoping Begins

Terracez does not begin EPC Dynamics 365 implementations with a scoping document. We begin with a readiness assessment. This is not a sales exercise. It is a structured diagnostic that identifies the organisational, commercial and data gaps that will determine whether your implementation succeeds or stalls.

The assessment is conducted using the Alignyx Transformation Intelligence Platform and Terracez's proprietary Transformation Intelligence Framework, a 15-domain methodology that evaluates the organisational conditions that determine transformation success before a single configuration decision is made.

What the EPC Readiness Assessment covers

Commercial process review

• Variation order governance and approval chain
• Subcontractor payment and retention policy
• Procurement approval thresholds and delegation of authority
• Cost-to-complete ownership and reporting frequency

Data quality review

• WBS structure consistency across active projects
• Subcontractor register completeness and reconciliation status
• Vendor master data quality and compliance classification
• Opening balance reconciliation between QS and finance records

Compliance architecture review

• UAE PINT AE e-invoicing readiness
• Saudi Arabia ZATCA Phase 2 connector selection
• ICV vendor classification requirements
• Multi-entity legal structure and chart of accounts design

Adoption risk review

• CVR format alignment with QS practice
• Commercial team change readiness
• Procurement workflow validation against actual approval behaviour
• Parallel-run criteria and legacy system exit plan

Implementation scope recommendation

• Recommended Dynamics 365 module configuration for your EPC operating model
• Phased rollout sequence that minimises disruption to live projects
• Fixed-price implementation proposal with defined scope and governance

What EPC firms receive from the assessment

The output is a structured readiness report that gives your leadership team a clear picture of:

1. Which readiness domains are strong and ready for implementation
2. Which domains have gaps that must be resolved before configuration begins
3. The recommended implementation sequence and phasing
4. A fixed-price implementation proposal scoped to your actual operating model

Terracez's fixed-price proposals typically range from USD 150,000 to USD 750,000 for full EPC implementations, depending on entity count, project complexity and compliance requirements. The readiness assessment ensures that scope is defined accurately before a price is agreed, which eliminates the scope creep that turns fixed-price proposals into open-ended engagements.

Ready to assess your EPC readiness? The assessment is structured, time-bounded and designed to give your leadership team the information needed to make a confident implementation decision.

How to Phase a Dynamics 365 Implementation Without Disrupting Live EPC Projects

One of the most common objections from EPC leadership teams is timing. Most EPC contractors have multiple live projects running at any point. The concern is legitimate: a poorly sequenced ERP go-live can disrupt project reporting, delay subcontractor payments and create commercial risk on active contracts.

The answer is phasing. A well-designed phased implementation allows Dynamics 365 to go live incrementally, with each phase delivering measurable commercial value before the next phase begins.

The recommended four-phase EPC implementation sequence

Phase 1: Foundation (months 1 to 3)

Establish the data architecture, compliance design and governance framework before any project data is migrated.

• Legal entity structure and chart of accounts
• Compliance connectors (ZATCA, PINT AE)
• Vendor master data cleansing and migration
• Approval workflow design and validation
• WBS naming convention and cost code standardisation

Phase 2: Finance and procurement (months 3 to 5)

Go live on finance and procurement for new projects only. Existing projects remain on the legacy system during this phase.

• Dynamics 365 Finance live for new project financial postings
• Project-aware procurement workflow active for new purchase requisitions
• Three-way match process validated on new vendor transactions
• ICV and compliance tagging active for qualifying procurement

Phase 3: Project controls (months 5 to 8)

Migrate active projects from the legacy system with reconciled opening balances. This is the highest-risk phase and requires the most careful preparation.

• WBS structures migrated and validated for each active project
• Opening balances reconciled and confirmed by QS and finance
• Cost-to-complete reporting active in Dynamics 365
• Subcontractor payment applications and retention tracking live
• CVR reporting validated against legacy format before parallel run ends

Phase 4: Reporting and optimisation (months 8 onwards)

Activate Power BI dashboards and executive reporting. Retire legacy spreadsheets and parallel systems.

• Power BI project-cost and cash-flow dashboards live
• CVR, cost-to-complete and procurement-commitment reports replacing spreadsheets
• Adoption monitoring through Alignyx with identified lagging users
• Post-go-live optimisation of workflows based on commercial team feedback

The parallel-run decision

The most important decision in EPC phasing is when to end the parallel run. Running Dynamics 365 and the legacy system simultaneously for too long creates data integrity problems. Ending it too early creates adoption risk.

Terracez recommends a maximum eight-week parallel run for each phase, with clear exit criteria agreed before the parallel run begins. Exit criteria should include: zero material discrepancies between Dynamics 365 and legacy CVR for three consecutive weeks, procurement approval workflow compliance above 95%, and QS team sign-off on the cost-to-complete report format.

Thinking about implementation timing? The EPC Readiness Assessment includes a recommended phasing plan tailored to your current project portfolio and legacy system.

Is Your EPC Organisation Ready for Dynamics 365?

The six readiness domains in this article are not a theoretical framework. They are the practical conditions that determine whether your Dynamics 365 implementation will deliver genuine commercial control or become another ERP programme that goes live without changing how your commercial teams actually work.

Most EPC firms that approach Terracez are ready in some domains and not in others. That is normal. The purpose of the readiness assessment is not to find reasons to delay implementation. It is to identify exactly which gaps exist, define the steps to close them and build a phased implementation plan that delivers value from the earliest possible point.

The question to ask your leadership team before selecting an implementation partner:

"Can we complete a commercial process ownership matrix, produce a reconciled opening balance for every active project and define our variation order approval chain in a two-week readiness workshop?"

If the answer is yes, your organisation is ready to begin. If the answer is no, or not yet, the readiness assessment will identify what needs to be resolved and how long it will take.

Take the next step

Terracez conducts EPC Dynamics 365 Readiness Assessments for contracting firms across the UAE and Saudi Arabia. The assessment is structured, time-bounded and designed to give your CFO, commercial director and project leadership the information they need to make a confident, low-risk implementation decision.

For a deeper understanding of how Dynamics 365 supports EPC project costing, procurement and subcontractor management once your organisation is ready, read our guide: Dynamics 365 for EPC and Contracting Companies in the UAE and Saudi Arabia.

‍

Speak directly with the Terracez EPC team about your current project portfolio, implementation timeline and compliance requirements. The conversation starts with your operating model, not a product demonstration.