EPC and contracting firms in the UAE and Saudi Arabia are not simply running large projects. They are managing multiple simultaneous environments: different regulatory frameworks, multi-site cost centres, complex subcontractor chains, and procurement cycles that span international suppliers and local content obligations. Most ERP platforms were not built for this. Standard configurations handle finance and procurement in isolation. They do not connect project budgets to procurement commitments in real time, nor do they manage subcontractor retention, back-to-back billing, and ZATCA e-invoicing within the same workflow.
The real challenge is not finding an ERP. It is configuring the right one correctly for how EPC businesses in the GCC actually operate.
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 most cited causes were not technology failures. They were poor capital planning, regulatory compliance gaps, and subcontractor performance issues. Microsoft Dynamics 365, configured correctly for EPC operations, addresses each of these directly. This blog explains how.
Why Standard ERP Falls Short for EPC in the GCC
EPC contracting is operationally distinct from most industries. 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.
The MEED analysis of GCC construction risk identifies three systemic failures that recur across the region. QS 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-10% retention clauses creates significant liquidity strain that unmanaged systems cannot track accurately.
With 2026 GCC construction costs rising approximately 3-4% annually and materials accounting for 55-60% of total project cost in the UAE, the margin for error is shrinking. Commercial teams cannot afford a system that lags behind site reality. Dynamics 365, when configured for EPC operations, addresses each of these directly. But the configuration must be intentional. A generic Dynamics 365 go-live will not deliver EPC-grade project control.
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. First, costs are tracked against specific Work Breakdown Structure elements rather than a project total, which allows budget versus actual analysis at the package level. Second, 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. Third, 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. Fourth, purchase orders and subcontract agreements are recorded as commitments against the project budget before the invoice arrives. That last point 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 (CVR) 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
The procurement workflow in Dynamics 365 is project-aware from the first step. 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.
Dynamics 365 addresses subcontractor management through a combination of contract administration, milestone-based payment control, and retention tracking that operates within the same financial environment as the main project.
Core Subcontractor Capabilities
Dynamics 365 handles subcontractor management through a combination of contract administration, milestone-based payment control, and retention tracking that operates within the same financial environment as the main project. Each subcontractor agreement is registered 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-10% 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 a Successful Dynamics 365 EPC Implementation Requires
Technology does not resolve organisational problems. A well-configured Dynamics 365 instance will expose process gaps, ownership disputes, and governance weaknesses that existed long before the system went live.
In our experience working with EPC and contracting organisations across the GCC, the implementations that deliver genuine commercial control share three characteristics that have nothing to do with the software itself.
Business Process Ownership Before Configuration
Before any Dynamics 365 configuration begins, the organisation must define who owns each commercial process. Who approves a purchase requisition above AED 500,000? Who authorises a subcontractor variation? Who releases retention? When these questions are answered in a workshop, they are straightforward. When they are discovered during user acceptance testing, they become costly delays. This is a business readiness problem, not an implementation problem. Addressing it before configuration begins is the single most effective way to reduce implementation risk.
A Compliance Architecture That Matches the Operating Model
EPC firms operating across UAE and KSA cannot apply a single Dynamics 365 configuration to both entities. The compliance requirements are different, the legal entity structures are different, and the chart of accounts may need to differ as well. This must be designed at the architecture stage, not resolved after go-live. For guidance on choosing the right Dynamics 365 approach for Saudi operations specifically, our Dynamics 365 module selection guide for Saudi businesses provides a practical starting point.
Commercial Team Adoption, Not Just Finance Team Training
The most common failure point in EPC ERP implementations 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 an adoption problem, and it is predictable. The solution is not more training. It is ensuring the system is configured to match how commercial teams actually work, not how the implementation team assumed they work.
The pattern we observe consistently: organisations that invest in business readiness before implementation begin 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 configuration decisions made without sufficient business input.
Is Your Organisation Ready for Dynamics 365 EPC Configuration?
Dynamics 365 is a capable platform for EPC and contracting operations in the UAE and Saudi Arabia. Configured correctly, it provides real-time project costing, procurement control, subcontractor management, and full GCC regulatory compliance within a single integrated environment.
But the platform does not configure itself. The organisations that extract the most value from it are the ones that arrived at implementation with clear process ownership, defined governance, and a commercial team that was prepared to work within a structured system rather than around it.
The question worth asking before selecting a partner or beginning a project is not "can Dynamics 365 handle EPC?" It is "is our organisation ready to implement it in a way that will actually change how we work?"
If you are evaluating Dynamics 365 for your EPC or contracting operations in the UAE or Saudi Arabia, we are happy to discuss what readiness looks like before implementation begins.
How is your organisation currently managing the gap between site procurement and financial reporting? Is it a process problem, a system problem, or both?
.png)
.png)
.png)
.png)
.webp)
