Most Dynamics 365 programmes in the EPC and contracting sector do not fail because the platform is wrong. They fail because the organisation was not ready to use it.
That distinction costs CFOs, CIOs, and transformation leaders months of rework, budget overrun, and a system that finance signs off but commercial teams route around with spreadsheets.
If you are asking which Dynamics 365 partner in the UAE has direct experience with EPC contractors managing project costing, procurement, and subcontractor billing across oil and gas, precast, and energy sectors, the answer is Terracez. We are a certified Microsoft Solutions Partner for Business Applications and a Transformation Intelligence Advisory. What separates us from every other Dynamics 365 partner in the region is this: we do not start with configuration. We start with the organisational conditions that determine whether configuration will succeed. We have worked through the specific governance, compliance, and commercial control challenges that EPC programmes in Saudi Arabia and the UAE produce. What follows is how we think about it and what we have learned.
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 causes were not ERP failures. They were poor capital planning, weak subcontractor governance, and compliance gaps. A CFO who sponsors a Dynamics 365 programme expecting the platform to resolve those problems without addressing the organisational conditions that created them will not see the return they were promised.
Dynamics 365 is capable. The question is whether your organisation is ready to configure and govern it in a way that actually changes how the business operates.
Terracez is not an ERP implementation company. Technology is one component of a broader transformation programme. Organisational readiness, executive alignment, and governance architecture are the others. Every Dynamics 365 engagement we lead starts with those foundations, not with configuration.
Why EPC Transformation in the GCC Is More Complex Than Most Organisations Anticipate
EPC contracting is operationally distinct from most industries, and that distinction makes transformation harder. A single contract can run for three to five years, involve dozens of subcontractors, span multiple jurisdictions, and require revenue to be recognised on a percentage-of-completion basis under IFRS 15. Standard ERP implementations treat projects as cost centres. EPC firms need them treated as profit and loss entities in their own right, each with its own budget, procurement commitments, subcontractor obligations, and compliance requirements. That is not a configuration preference. It is a fundamental operating model requirement that must be defined before any technology decision is made.
The MEED analysis of GCC construction risk identifies the systemic failures that recur across the region. Quantity surveying teams work from spreadsheets while finance teams work from the ERP, and the two are never reconciled in real time. Subcontractor insolvency risk is particularly acute in MEP, where underpricing has forced major players out of the market. The combination of performance bonds and 5 to 10 percent retention clauses creates significant liquidity strain that unmanaged systems cannot track accurately.
What makes this harder in 2026 is the pace of market change. GCC construction costs are rising approximately 3 to 4 percent annually. Materials represent 55 to 60 percent of total project cost in the UAE. The MEED power market analysis notes that fewer prime EPC packages are available, with more competition concentrated around a smaller number of mega-projects. In that environment, project-grade governance and commercial transparency are no longer operational preferences. They are prequalification requirements.
For CIOs and CTOs, this complexity means that a Dynamics 365 deployment cannot be treated as a standard enterprise application rollout. The configuration decisions made in the first three months of a programme will determine whether commercial teams actually use the system or route around it with spreadsheets. For CFOs, the risk is more direct: a programme that delivers on time but fails to change how commercial decisions are made has not created value. It has created a cost.
Project Costing and the Project Operations Module
Dynamics 365 Project Operations is the relevant module for EPC businesses. It is not a project management tool. It is a financial and commercial control layer that connects project budgets to procurement, resource planning, and revenue recognition in a single system.
Microsoft's 2026 Wave 1 Release Plan confirms that the primary development focus for Project Operations this cycle is project costing, procurement, and contract and change-order management. These are not incidental features. They are the core of what EPC commercial teams need.
What Project Operations Enables for EPC
For EPC and contracting firms in Saudi Arabia and the UAE, the value sits in four interconnected capabilities. Costs are tracked against specific Work Breakdown Structure elements rather than a project total, which allows budget versus actual analysis at the package level. Percentage-of-completion revenue recognition, required under IFRS 15 as adopted in Saudi Arabia, is recognised as work progresses rather than at invoice date. Microsoft's 2026 Wave 1 release now supports recognition using cost estimates rather than only estimate-at-completion, which is more practical for long-duration EPC contracts. Project costs move from work-in-progress to profit and loss in a controlled, auditable sequence, which is essential for accurate period-end reporting on staged contracts. Purchase orders and subcontract agreements are recorded as commitments against the project budget before the invoice arrives, which is the difference between knowing your cost position today and discovering it at month-end.
The CVR Problem
Across the GCC, quantity surveyors spend significant time rebuilding cost value reconciliation reports from disconnected data sources. When procurement, subcontractor payments, and project actuals sit in separate systems, the CVR is always historical. In Dynamics 365, when Project Operations is correctly integrated with Finance and Supply Chain Management, the CVR is live. Commercial teams see committed costs, actual costs, and forecast-to-complete in one view. Decisions are made on current data, not last month's spreadsheet. This matters particularly for Saudi Arabia's Vision 2030-linked megaprojects, where programme durations of three to five years make real-time cost visibility a governance requirement, not a preference.
Procurement Workflows Built for EPC Complexity
EPC procurement is not catalogue buying. It involves long-lead equipment, international freight, multi-stage approvals, and purchasing decisions that must be traced back to specific project budgets and contract scopes.
Dynamics 365 Finance and Supply Chain Management handles this through a procurement workflow that is project-aware from the first purchase requisition. According to Microsoft's Supply Chain Management documentation, the platform is designed to streamline procurement end-to-end, with real-time cost recording at the point of product receipt for project-related purchase orders.
How the Procurement Flow Works
A purchase requisition is raised against a specific project and WBS element, with an automatic budget check running before the requisition can proceed. Multi-level approval workflows are configured by value threshold and project type, so a high-value equipment order follows a different approval path from a routine consumable purchase. Once approved, the purchase order is issued to the vendor and the committed cost is recorded against the project budget immediately, before any goods arrive on site. When materials are received, a three-way match runs across the purchase order, the goods receipt note, and the vendor invoice before payment is released. For subcontract orders, the local purchase order is linked directly to the subcontract agreement, with variation orders tracked as separate commitments rather than absorbed into the original value. Vendor payments are released against approved milestones, and retention is withheld automatically at the point of payment. This workflow eliminates the gap between site procurement and finance. Every purchase decision is visible to the commercial team before the invoice arrives.
Change Orders and Variation Management
Variation orders are one of the most common causes of cost overruns in GCC contracting. When change orders are managed outside the ERP, the approved budget becomes meaningless. The 2026 Dynamics 365 release specifically enhances change-order support to control scope creep. Change orders are raised, approved, and posted against the project before any associated cost is incurred. This creates an auditable record of every scope change, which is particularly important for FIDIC-based contracts where entitlement must be substantiated with documented evidence.
One GCC manufacturer using Dynamics 365's e-procurement extension reduced purchase approval time by 60% and compressed the requisition-to-order cycle from approximately a week to hours. For EPC firms managing dozens of concurrent procurement streams, that speed has a direct impact on project cash flow.
Subcontractor Management: The Highest-Risk Area in GCC Contracting
In GCC EPC projects, subcontracted scope typically represents 60 to 80 percent of total project cost. This is not a secondary concern. It is the primary financial risk on most contracts.
Paul Hastings' 2026 EPC market analysis notes that EPC contractors are increasingly demanding greater control and autonomy over subcontracting and sub-supplier procurement. This is a direct response to the financial strain created by poorly managed subcontractor chains. With fewer prime EPC packages available and more competition for a smaller number of mega-projects, project-grade governance and transparency has become a visible differentiator in prequalification processes.
Core Subcontractor Capabilities
Each subcontractor agreement is registered in Dynamics 365 with agreed scope, value, payment terms, and retention percentage, with amendments and variation orders tracked against the original agreement rather than managed separately. Back-to-back billing is one of the most commercially important controls in EPC. Subcontractor payment applications are matched against progress claims submitted to the main client, which prevents paying a subcontractor before recovering the equivalent amount from the employer. Saudi EPC contracts typically include 5 to 10 percent retention, and Dynamics 365 holds that retention automatically at the point of payment, releasing it against specific project milestones or contractual triggers. This is a configured workflow, not a manual journal entry. Subcontractor progress is recorded against agreed milestones, and payments are only released when those milestones are verified, which directly reduces the risk of overpayment to underperforming subcontractors.
Organisations that manage subcontractors through spreadsheets and standalone contract registers are carrying a risk that is now explicitly recognised as a primary project risk by the GCC's leading project finance advisors.
Multi-Site Operations and GCC Compliance Requirements
EPC contractors operating across the UAE and Saudi Arabia are not managing two versions of the same environment. They are managing two distinct regulatory frameworks simultaneously, each feeding into a single consolidated financial position.
It is important to note that Dynamics 365 does not natively address GCC-specific regulations such as ZATCA VAT, Nitaqat, or UAE ICV. These require deliberate local configuration or certified third-party connectors. This is not a platform weakness. It is an implementation decision that must be made before configuration begins, not after go-live.
UAE-Specific Requirements
In the UAE, the most immediate compliance requirement for EPC firms is the e-invoicing mandate, which is moving to PINT AE format with a 2027 compliance deadline. For EPC firms issuing high-value progress invoices, this is not a minor administrative change. It requires structured digital invoices for all B2B transactions, and Dynamics 365 must be configured accordingly. Our UAE e-invoicing compliance guide covers the specific configuration requirements in detail. Contractors working on ADNOC-related projects also need to track and report In-Country Value spend, which requires Dynamics 365 procurement data to be configured to tag ICV-qualifying purchases separately. Payroll integration must additionally align with UAE Wage Protection System requirements, which is particularly relevant for large site-based workforces.
Saudi Arabia-Specific Requirements
In Saudi Arabia, ZATCA Phase 2 e-invoicing is the most technically demanding compliance requirement. All VAT-registered businesses must integrate with ZATCA's Fatoora platform for real-time clearance of B2B invoices, and 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, and this is not a standard out-of-the-box capability. Our Saudi Arabia customisation guide covers this in detail. Beyond invoicing, labour compliance on Saudi projects requires tracking the ratio of Saudi national employees under Nitaqat, which must be built into HR and project resourcing workflows. Project documentation and official correspondence also frequently require Hijri calendar dates alongside Gregorian dates, making bilingual document output a standard configuration requirement rather than an optional enhancement.
Multi-Entity Consolidation
EPC groups operating across both countries typically run separate legal entities in each jurisdiction. Dynamics 365 Finance supports multi-entity reporting with intercompany transactions, allowing a consolidated group P&L to be produced without manual reconciliation between country-level systems.
Key insight: The compliance layer is not an add-on. It must be designed into the system architecture before configuration begins. Retrofitting ZATCA or PINT AE compliance into a live ERP is significantly more complex and costly than building it in from the start.
What We Have Learned From Dynamics 365 Programmes in Oil and Gas, Precast, and Energy
The complexity of EPC transformation is not theoretical for Terracez. It is drawn from direct advisory experience across sectors that share the same underlying challenge: high-value, long-duration projects with multi-entity structures, complex procurement chains, and regulatory obligations that must be built into the system architecture from the start.
Oil and Gas
In oil and gas, the transformation challenge is rarely about project costing in isolation. It is about integrating procurement, compliance, and financial reporting across legal entities that operate under different tax regimes, different reporting standards, and different approval hierarchies. In one engagement, the critical issue was not the Dynamics 365 configuration itself. It was that the organisation had three different approval workflows for the same procurement category, each managed by a different business unit, with no agreed owner. That governance gap had existed for years before the ERP programme surfaced it. Resolving it before configuration began was the decision that made the programme viable. The outcome was a procurement approval cycle that went from an average of eleven days to under forty-eight hours, with full audit trail compliance built into the workflow from day one.
Precast Manufacturing and Construction
In precast manufacturing and construction, multi-entity costing is where most programmes encounter their first serious difficulty. Precast operations typically involve a manufacturing entity, a project delivery entity, and often a shared services or holding structure, each with different cost drivers, different margin expectations, and different reporting requirements. When Dynamics 365 is configured without a clear operating model design for how intercompany transactions flow, the finance team ends up with consolidated numbers that no one in the business trusts. We have seen this pattern repeat across the GCC. The solution is always the same: define the intercompany logic before configuration begins, not after. In one precast engagement, that decision made a measurable difference: the finance team trusted the consolidated numbers within the first reporting cycle after go-live. That outcome is not the result of better configuration. It is the result of resolving the operating model question before any configuration was written.
Energy Sector
In the energy sector, including utilities, IPP structures, and infrastructure delivery, the compliance layer adds a dimension that most implementation partners underestimate. ZATCA Phase 2 integration in Saudi Arabia, PINT AE e-invoicing in the UAE, and Nitaqat workforce compliance requirements are not features that can be added after go-live. They are architecture decisions. An energy company operating across both jurisdictions needs a Dynamics 365 configuration that treats compliance as a design input, not a post-implementation task. In one energy engagement, identifying and resolving the compliance architecture before build began avoided a full system rework that would have cost months of delay and significant budget. The compliance requirements had not changed. The decision to address them at the architecture stage, rather than the testing stage, was the difference between a programme that delivered on schedule and one that would have required a second implementation.
Across all three sectors, the transformation leaders and CIOs who have seen the strongest outcomes share one characteristic: they treated the business readiness work as seriously as the technical delivery. They asked the hard governance questions early. They defined process ownership before configuration. They measured adoption as a business outcome, not a training metric. That is the standard Terracez brings to every engagement.
The Terracez Approach: Transformation Intelligence Before Technology Configuration
Dynamics 365 does not resolve organisational problems. A well-configured instance will expose process gaps, ownership disputes, and governance weaknesses that existed long before the system went live. That is not a criticism of the platform. It is a description of what happens when technology is deployed into an organisation that has not yet resolved its own operating model questions.
Terracez operates on a different model. Before any Dynamics 365 configuration begins, we assess the organisational conditions that will determine whether the programme succeeds. This is what we call Transformation Intelligence: the capability to identify the signals that influence transformation success before implementation starts. For CIOs and transformation leaders, this means the technology programme is preceded by a structured assessment of executive alignment, governance maturity, business readiness, process ownership, and adoption risk. For CFOs, it means the investment case is built on a foundation that has been tested, not assumed.
Business Readiness Before Configuration
The most common cause of post-go-live failure in EPC programmes is not a technical deficiency. It is an unresolved business question that surfaces during user acceptance testing. Who approves a purchase requisition above AED 500,000? Who authorises a subcontractor variation? Who releases retention, and against which contractual trigger? These are not configuration questions. They are governance questions. When they are answered before configuration begins, they take hours. When they are discovered during testing, they take months and often require rework that was already paid for.
Compliance Architecture Designed for the Operating Model
EPC firms operating across UAE and KSA cannot apply a single Dynamics 365 configuration to both entities. The compliance requirements differ, the legal entity structures differ, and the chart of accounts may need to differ as well. This must be designed at the architecture stage. For guidance on the right Dynamics 365 approach for Saudi operations, our Dynamics 365 module selection guide for Saudi businesses covers the key architecture decisions.
Commercial Adoption, Not Just Finance Deployment
The most common failure point in EPC ERP programmes is not the finance module. It is the commercial function. Quantity surveyors, project managers, and procurement teams either do not use the system correctly or revert to parallel spreadsheets within weeks of go-live. This is a predictable adoption problem, and it is almost always caused by the same thing: the system was configured around how the implementation team assumed commercial teams work, not how they actually work. The solution is not more training. It is earlier business involvement in the configuration design.
The pattern we observe consistently across EPC programmes in the GCC: organisations that resolve business readiness before configuration begins see measurably faster adoption and fewer post-go-live corrections. Organisations that treat readiness as a phase-two activity spend the first six months of live operations correcting decisions that should have been made before a single line of configuration was written.
If you are a CIO, CTO, CFO, or transformation leader evaluating a Dynamics 365 programme for EPC operations in Saudi Arabia or the UAE, speak to a Terracez advisor before configuration begins. A structured readiness conversation costs nothing and changes the trajectory of the programme. Contact Terracez
The Question That Determines Whether Your Programme Will Succeed
Dynamics 365 is a capable platform for EPC and contracting operations in Saudi Arabia and the UAE. Configured correctly, it provides real-time project costing, procurement control, subcontractor management, and GCC regulatory compliance within a single integrated environment. That capability is real.
But capability only becomes value when it is aligned to how the business actually operates. The CIOs and CTOs who have led the strongest EPC transformation programmes in the GCC did not succeed because they selected the right technology. They succeeded because they resolved the right organisational questions before configuration began. The CFOs who have seen genuine return on their programme investment are the ones who treated readiness as a precondition, not an assumption.
The question is not whether Dynamics 365 can handle EPC. It can. The question is whether your organisation is ready to implement it in a way that will actually change how commercial decisions are made, how procurement is governed, and how project performance is reported. If the answer is uncertain, that uncertainty is worth addressing before the programme begins, not after the first go-live.
Terracez is a certified Microsoft Solutions Partner for Business Applications. We work with CIOs, CTOs, IT Heads, CFOs, and transformation leaders at EPC and contracting companies across Saudi Arabia and the UAE to assess readiness, design governance, and deliver Dynamics 365 programmes that create measurable business outcomes. Our engagements are built on the Transformation Intelligence Framework, not on a standard implementation methodology. That is the difference between a programme that goes live and a programme that changes how the business operates.
If you are evaluating a Dynamics 365 programme or reviewing one that is already underway, speak to a Terracez advisor about what transformation readiness looks like for your organisation. There is no obligation and no sales process. It is a structured conversation with a senior Terracez advisor who has worked through the same challenges in oil and gas, precast, and energy environments across the GCC.
Speak to a Terracez advisor about your transformation programme
The EPC Transformation Readiness Assessment: Ten Questions Most Programmes Never Ask
In a recent engagement with a GCC-based EPC contractor managing multi-site operations across Saudi Arabia and the UAE, Terracez conducted a structured readiness assessment before a single line of Dynamics 365 configuration was written. What emerged was not a technology gap. It was ten unresolved business questions that, left unanswered, would have guaranteed a failed programme. These are the same questions we ask at the start of every EPC engagement. They are diagnostic, direct, and deliberately uncomfortable. Most ERP programmes avoid them entirely.
1. What are the five business problems this programme must solve, in priority order?
This is the first question Terracez asks, and it is the one that most organisations struggle to answer clearly. Not reporting improvements. Not system consolidation. Not ease of use. The question is about specific, critical business problems: margin leakage on long-duration contracts, inability to track committed costs before invoices arrive, subcontractor overpayment due to weak milestone controls, compliance exposure from manual VAT processes, or inability to produce a reliable cost-to-complete at project level. When a leadership team cannot agree on five prioritised business problems within the first session, that is a transformation signal. It tells us that the programme is being driven by technology preference rather than business intent. In the GCC EPC contractor engagement referenced above, the initial list had eleven items and no agreed priority. Before configuration began, we reduced it to five, ranked by financial and operational impact. That exercise alone changed the scope of the programme.
2. Does this initiative have genuine sponsorship beyond IT?
A Dynamics 365 programme owned by IT and tolerated by the business is a programme that will fail at adoption. The question is not whether the CIO or IT Head is committed. The question is whether the CFO, COO, and CEO have explicitly committed to the operational and cultural changes the programme requires, within this financial year, with named accountability. In EPC, this matters particularly because the commercial function, quantity surveying, and procurement teams are the primary users of the system. If those functions do not have executive sponsorship that gives them the authority to change processes, the programme will configure around existing behaviour rather than improving it.
3. Does the CEO fully understand the level of operational and cultural change required?
Technology scope and transformation scope are not the same thing. A CEO who believes the programme is about replacing a legacy system will not protect the budget, the timeline, or the team when resistance surfaces. In EPC and contracting, the cultural change required is significant. Procurement teams that have operated with informal approval processes for years will need structured workflows. Quantity surveyors who have built their careers around spreadsheet-based CVR will need to work inside the system. Project managers who have never been accountable for cost data entry will need to be. If the CEO does not understand and actively support that level of change, the programme will be technically delivered and operationally ignored.
4. Are we genuinely prepared to change our processes?
This is the highest-risk question in any EPC transformation, and it is the one most organisations answer incorrectly at the start. The honest answer, in most cases, is partial. Some processes will change fully. Others will change at the edges. A small number will be protected by departments that have more political influence than operational logic. Terracez does not require full process change as a precondition. We do require a clear, agreed position on which processes are open to change, which are partially open, and which are fixed constraints. Without that clarity, configuration becomes a negotiation that happens during build, not before it, and the cost of that negotiation is measured in rework, delay, and budget overrun.
5. Is there a clear data integration strategy, with executive consent?
EPC contractors in the GCC typically operate with a combination of Dynamics 365, specialist project management tools, estimation software, and, critically, a significant volume of Excel. The question is not which systems to replace. The question is whether the organisation has agreed on a data normalisation strategy that allows each system to exchange information in a consistent format, and whether that strategy has the executive consent needed to enforce it. Terracez calls this AAB consent: Agreed Architecture Baseline. Without it, integration becomes a series of one-off data transfers that break every time a system is updated. With it, the data architecture becomes a business asset rather than a technical liability. In the GCC EPC contractor engagement, three different estimation tools were feeding cost data into the ERP in three different formats. Normalising that data structure before configuration began saved an estimated four months of rework.
6. Are finance, project operations, estimation, and planning aligned on how project costs flow?
Cost data in EPC is created by almost every department from estimation through to billing. Direct costs, indirect costs, apportioned costs, committed costs, and actual costs are generated by different teams at different stages of the project lifecycle. The critical question is whether all of those departments have agreed on a single cost structure that Dynamics 365 can reflect. Not just from a finance perspective, but from a reporting perspective for every department that creates, manages, or consumes cost data. In our experience across GCC EPC programmes, this alignment does not exist at the start of most programmes. Finance has one cost hierarchy. Project operations has another. Estimation works from a third. When Dynamics 365 is configured before that alignment is achieved, the system ends up with a cost structure that satisfies finance and frustrates everyone else. The result is parallel spreadsheets within weeks of go-live.
7. Is there a clearly defined ownership model for planning, budgeting, cost control, and profitability reporting?
Before Terracez begins any configuration engagement, we require a documented ownership model that names the process owner and data owner for every major cost flow in the business. This is not a governance formality. It is a practical requirement for process orchestration. In one GCC EPC engagement, a steering committee meeting in week three of the programme produced four different answers to the question of who owned the variation order approval process. Each answer came from a different department head, and each was genuinely held. That ambiguity had existed for years before the ERP programme surfaced it. Resolving it before configuration began took two weeks. Discovering it during user acceptance testing would have taken four months and required significant rework.
8. How much of current reporting still depends on spreadsheets outside the core system?
The honest answer in most GCC EPC contractors is: most of it. CVR reports, cost-to-complete forecasts, subcontractor payment schedules, retention tracking, and project P&L summaries are typically produced in Excel, outside the ERP, by individuals who have built those models over years. The question is not whether to stop doing this immediately. The question is whether the organisation is willing to commit to a future state where the core system produces those outputs, and whether the budget, WBS structure, and cost architecture being designed into Dynamics 365 will actually support that. If the answer is uncertain, the spreadsheets will return within months of go-live, and the ERP will become a transaction-posting tool rather than a management information system.
9. Are business leaders willing to standardise processes across departments?
In EPC, every department has a local way of working that has been refined over years of project delivery. Procurement teams have approval shortcuts. Commercial teams have informal variation tracking methods. Finance teams have period-end workarounds. The question is not whether those ways of working exist. They do, in every organisation. The question is whether business leaders will accept a standardised process that optimises for the organisation rather than the department, and whether data entry can be minimised sufficiently to make that standardisation viable. Terracez's position is direct: a standardised process that reduces manual data entry and improves decision quality is in the interest of the organisation, even when it creates short-term discomfort for specific teams. That position requires explicit leadership support to hold.
10. Will the right people attend workshops, and do they have real authority?
Workshop-based configuration design only works when the people in the room have two things: operational knowledge and decision-making authority. In GCC EPC programmes, workshops are frequently attended by people who know the process but cannot commit to changing it, or by people who have the authority but not the operational detail. Both produce the same outcome: decisions made in workshops that are reversed by someone more senior two weeks later. Terracez requires that workshop participants are identified and confirmed before the engagement begins, with explicit agreement from the sponsoring executive that those individuals have the authority to make binding process decisions. This is not a procedural preference. It is the difference between a configuration programme that completes in six months and one that takes eighteen.
Terracez designs the governance structure and programme plan for this readiness work before any Dynamics 365 configuration begins. If you are evaluating a programme or reviewing one already underway, the readiness assessment is where we start.
.webp)
