Dynamics 365 Customisation Services in Saudi Arabia

When a standard Dynamics 365 deployment is not enough, the real question is not whether to customise — it is whether your partner has the depth to do it without breaking what already works.

Terracez delivers Dynamics 365 customisation for large enterprises across Saudi Arabia, with on-the-ground teams in Riyadh, Jeddah, and Dammam. Our work spans Project Accounting, Supply Chain, Finance, Production, and Sales — including revenue recognition logic, AI-integrated compliance workflows, procurement automation, and bespoke estimation tools where standard functionality does not reach.

Every customisation we deliver is preceded by a structured impact analysis. In a connected ERP, a change to one module creates ripple effects across three others. This page is for enterprise teams in Saudi Arabia evaluating whether a Dynamics 365 customisation is feasible, safe, and worth the investment. The answer to all three is yes — if the approach is right.

Request a Complimentary Scoping Session

What Dynamics 365 Customisation Actually Means for Saudi Enterprises

Customisation in Dynamics 365 is not the same as configuration. Configuration works within the boundaries Microsoft has set. Customisation extends or replaces those boundaries when the business requirement demands it. For large enterprises in Saudi Arabia, that distinction matters because the business environment creates requirements that out-of-the-box ERP does not address.

Person wearing glasses working on a laptop in an office setting with other people using laptops in the background, displaying a document or webpage on the screen.

Regulatory compliance built into every deployment

ZATCA e-invoicing, VAT reporting, Nitaqat and Saudisation workforce tracking, and Zakat filing requirements.

Man wearing glasses looking at a tablet displaying financial charts and text, with a large screen in the background showing various colorful graphs and data visualizations in a dimly lit room.

Industry, entity and currency complexity

Industry-specific workflows in construction, petrochemical, manufacturing, and trading that do not map to generic module defaults — plus multi-entity and multi-currency complexity across Saudi, GCC, and international operations.

Six men in business attire sit around a conference table, focusing intently on a laptop and a large document with diagrams and sticky notes on the table in a dimly lit room.

Bilingual interfaces and local integrations

Arabic and English bilingual interfaces with right-to-left layout requirements across all user-facing screens, together with integration requirements for local government portals, banking systems, and third-party platforms.

The risk in customisation is not the change itself. It is an undisciplined change made without understanding the downstream consequences. Dynamics 365 is deeply interconnected: Project Accounting connects to Finance, Procurement, and Reporting; Supply Chain connects to Production, Inventory, and Costing. A customisation that is not impact-assessed before development will surface problems in production — often in modules that were never touched.

Our standard: No customisation is scoped without a formal impact analysis. Every change is documented, regression-tested, and validated against the modules it connects to before go-live.

Customisation Delivered: Two Business-Critical Examples

The clearest way to evaluate a customisation partner is not their credentials — it is the complexity of the problems they have already solved.

Two examples from Saudi Arabia show where standard Dynamics 365 functionality was not sufficient and careful engineering was required.

Business-critical customisation delivered by Terracez:

A man in a blue suit sitting at a desk, analyzing data charts displayed on a desktop computer screen, including bar graphs, line charts, and a pie chart.

Revenue Recognition Customisation for Technomak — Project Accounting extension for auditable project profitability reporting, built after mapping Finance, Procurement, Billing and Reporting dependencies.

Open book on a wooden desk with a computer monitor and blurred person working in the background in a softly lit office setting.

Technomak Outcome — Cross-module regression testing and a purpose-built extension delivered financial visibility for investor scrutiny, management reporting and regional expansion.

A focused woman in a blue shirt closely examining a large sheet of paper in an office setting with another person sitting across from her, natural light in the background.

AI-Based KYC Extension — Dedicated KYC portal with AI document verification, Dynamics 365 Sales integration, Azure Blob Storage and automated renewal alerts.

Two business professionals, a woman and a man, engaged in discussion while reviewing documents in a modern office with large windows and plants.

Upgrade-Safe Architecture — The solution extended Dynamics 365 without modifying the ERP core, preserving the Microsoft upgrade path.

Person wearing glasses sitting at a wooden desk reviewing printed charts and graphs, with a desktop computer displaying data visualizations in the background and potted plants on the desk.

KYC Outcome — Processing moved from a two-to-three-day manual cycle to a near-automated exception-handling workflow.

Customisation Capabilities Across the Dynamics 365 Platform

Terracez has delivered customisations across the full Dynamics 365 platform for enterprises in Saudi Arabia.

The examples below reflect actual work delivered, not theoretical capability.

Finance and Project Accounting

Revenue recognition logic, project profitability reporting, multi-entity consolidation, Zakat and VAT-compliant financial structures.

A diverse group of five professionals, including men and women wearing traditional Middle Eastern attire and business clothing, gathered around a laptop engaged in discussion or collaboration.

Supply Chain Management

Automated item generation, purchase requisition consolidation, supplier onboarding workflows, multi-warehouse inventory rules.

Four diverse business professionals engaged in a meeting around a table with laptops and charts, one man in a suit presenting a paper with graphs and data to the others.

Production and Manufacturing

Custom item rejection and approval workflows, production order modifications, quality control integration.

A diverse business meeting with five people, including a man in traditional Middle Eastern attire showing a document, a woman in a hijab taking notes, a man in a suit listening, and another woman drinking coffee, all seated around a table in a modern office with a white brick wall.

Sales and CRM

AI-based KYC portals integrated with Dynamics 365 Sales, customer onboarding automation, pipeline and deal governance workflows.

Man sitting at a desk gesturing toward a computer screen displaying a digital interface with ERP (Enterprise Resource Planning) written in the center surrounded by various icons representing business functions.

Construction and Project Industries

Bespoke estimation tools for construction and marine projects, contract management extensions, project controls dashboards.

Person in a dark suit sitting at a desk using a smartphone, with illustrated chat bubbles containing the text 'AI' above the phone, next to an open laptop and documents on the desk.

Compliance and Regulatory

ZATCA Phase 1 and Phase 2 e-invoicing integration, Nitaqat and Saudisation workforce reporting, Arabic-English bilingual interfaces.

Platform Extensions

Azure Blob Storage integration, Power Platform automation, custom portals connected to core ERP data.

Have a specific customisation requirement? Tell us what you need and we will confirm feasibility within one business day.

Tell us what you need

When We Customise vs. When We Extend

Not every business requirement should be solved by modifying core Dynamics 365 code. Part of our value is helping clients make the right architectural decision before development begins.

Customisation

The business requirement is central to a core financial or operational process.
The standard module produces incorrect results for a specific business rule.
The change is bounded, impact-assessed, and upgrade-safe.
Core behaviour genuinely needs to be extended to meet the requirement.
Connected-module dependencies can be fully understood and regression-tested before deployment.

Extension

The requirement involves significant data volumes, document management, or AI processing.
Modifying core code would create upgrade risk or performance degradation.
The functionality is best served by a dedicated portal or external system connected via API.

The Engineering Decision

The petrochemical KYC solution is a clear example of the extension approach.
The Technomak revenue recognition work is a clear example of core module customisation.

Both required the same discipline: understand the system, assess the impact, and build the right solution for the requirement — not the easiest one.

Speak With a Transformation Advisor

Saudi Arabia Regulatory Requirements: Built Into Every Deployment

Saudi Arabia has a specific and evolving regulatory environment that affects every Dynamics 365 deployment. These are not optional additions — they are baseline requirements for any enterprise operating in the Kingdom. Terracez treats them as standard components of every engagement, not billable extras.

Customisation decisions must account for tax, workforce, localisation and reporting requirements from the start. The controls below are part of the Saudi delivery context Terracez builds into Dynamics 365 programmes.

Saudi localisation is treated as a delivery baseline: tax, workforce, Zakat and Arabic-language requirements are considered before customisation design is approved.

The following regulatory and localisation controls are considered as part of Dynamics 365 solution design and deployment in Saudi Arabia.

Saudi Regulatory and Localisation Controls

Requirement

Dynamics 365 delivery context

1. ZATCA E-Invoicing (Fatoorah)

ZATCA's e-invoicing mandate applies in two phases. Phase 1 required electronic invoice generation and storage. Phase 2 requires real-time integration with ZATCA's Fatoorah platform for invoice clearance and reporting. Terracez has delivered both phases, including Dynamics 365 Finance integration with the ZATCA API, QR code generation, and XML invoice formatting to ZATCA specifications.

2. VAT Compliance

Saudi VAT at 15% applies across most transactions. Dynamics 365 Finance handles VAT natively, but Saudi-specific scenarios — partial exemptions, reverse charge mechanisms, cross-border transactions, and multi-entity VAT groups — require careful configuration and, in some cases, customisation. Our deployments include full VAT return reporting aligned to GAZT requirements.

3. Nitaqat and Saudisation Reporting

The Nitaqat programme sets mandatory Saudisation quotas by industry and company size. Tracking workforce composition, calculating Saudisation percentages, and producing compliant reports requires data from HR, Payroll, and Finance to be connected and reported correctly. Terracez configures and, where needed, extends Dynamics 365 Human Resources to meet these obligations.

4. Zakat Reporting

Zakat calculation for Saudi entities follows rules that differ from standard corporate tax logic. Our Finance deployments include Zakat-compliant chart of accounts structures and reporting templates aligned to ZATCA's Zakat assessment requirements.

Arabic Language and Localisation

All user-facing screens, reports, and printed documents are delivered in both Arabic and English with full right-to-left interface support. This is a non-negotiable baseline for user adoption in Saudi Arabia.

How Our Saudi Arabia Customisation Engagements Work

A Dynamics 365 customisation engagement with Terracez follows a structured process designed to eliminate the most common failure modes: scope creep, undiscovered module dependencies, and post-go-live defects in connected functions.

The engagement begins with the business rule and its impact surface — not with development.

Five connected stages take the requirement from validation and impact analysis through architecture, development, testing, deployment and hypercare.

The Five-Step Customisation Engagement

Requirement Validation

We begin by understanding the business requirement in precise terms — not the feature request, but the underlying business rule, the data it touches, and the outcome it needs to produce. This is where most customisation projects go wrong: the requirement is not specific enough to build correctly.

Impact Analysis

Before any development begins, we map every module, function, and integration that the proposed change could affect. For complex modules like Project Accounting or Supply Chain, this analysis typically surfaces two to three dependency risks that were not visible in the initial requirement. These are resolved at the design stage, not after deployment.

Architecture Decision

Based on the requirement and impact analysis, we determine whether the right approach is a core customisation, a platform extension, or a configuration change. This decision is documented and agreed with the client before development starts.

Development and Testing

Development follows Microsoft's extensibility best practices, preserving upgrade paths wherever possible. Testing covers the customised function, all connected modules, and regression scenarios for existing workflows that share the same data or logic.

Deployment and Hypercare

Go-live is supported by our on-the-ground teams in Riyadh, Jeddah, and Dammam. A hypercare period follows every deployment, with defined SLAs for issue resolution and direct access to the consultants who built the solution.

Terracez consultants planning a Dynamics 365 customisation engagement in Saudi Arabia.

For a deeper look at how governance decisions shape customisation outcomes, read our guide: If you are an IT Manager or Operations Director preparing for a go-live, this is essential reading:

Read the Customisation Governance Guide

Read the Go-Live Guide

On-ground presence: Terracez has delivery teams physically based in Riyadh, Jeddah, and Dammam. For business-critical customisations, this matters. Time zone alignment, Arabic language capability, and the ability to be on-site when it counts are not small details.

Start With a Scoping Conversation

If you have a Dynamics 365 customisation requirement in Saudi Arabia, the right first step is a scoping conversation — not a proposal. We need to understand the business rule, the module it lives in, and what it connects to before we can tell you what is feasible, how long it will take, and what it will cost.

Terracez offers a complimentary scoping session for enterprise organisations in Saudi Arabia. In that session, we will assess your requirement, identify the likely impact surface, and give you an honest view of the approach before any commitment is made.

Our teams are based in Riyadh, Jeddah, and Dammam and are available for on-site meetings across the Kingdom.

Terracez Saudi Arabia Dynamics 365 customisation consultation.

Thank you. A senior Terracez advisor will be in touch within one business day to confirm your session.

Oops! Something went wrong while submitting the form.

Dynamics 365 Customisation in Saudi Arabia — Frequently Asked Questions

Direct answers to the questions Saudi enterprises most often ask before starting a Dynamics 365 customisation engagement.

Have a customisation requirement?

Request a scoping conversation below

Request a Scoping Session

Can Dynamics 365 be customised for Saudi Arabian businesses?

Yes. Dynamics 365 is designed to support customisation through Microsoft's extensibility framework, allowing partners to extend module behaviour, build integrations, and create purpose-built solutions without replacing the core platform. For Saudi businesses, this includes both regulatory requirements (ZATCA, VAT, Nitaqat) and industry-specific workflows in construction, petrochemical, manufacturing, and trading.

What is the difference between Dynamics 365 customisation and configuration?

Configuration adjusts Dynamics 365 within the boundaries Microsoft has defined — setting up workflows, approval rules, chart of accounts, and reporting templates. Customisation extends or modifies the platform beyond those boundaries, typically through custom code, API integrations, or purpose-built extensions. Both are valid approaches; the right choice depends on the specific business requirement and the risk profile of the change.

How long does a Dynamics 365 customisation project take in Saudi Arabia?

Scope determines timeline. A bounded customisation — such as a custom approval workflow or a reporting extension — can be delivered in four to eight weeks. A complex customisation involving core financial logic, such as revenue recognition in Project Accounting, or a new integrated system, such as an AI-based compliance portal, typically requires three to six months, including impact analysis, development, testing, and hypercare. Terracez provides fixed timelines after the impact analysis is complete.

Is it safe to customise modules like Project Accounting or Supply Chain?

It is safe when the approach is disciplined. Project Accounting and Supply Chain are among the most interconnected modules in Dynamics 365, which means a customisation in either area has the potential to affect Finance, Procurement, Reporting, and Production simultaneously. Terracez conducts a formal impact analysis before any development begins in these modules, mapping every dependency and resolving risks at the design stage rather than after deployment.

Can Dynamics 365 integrate with ZATCA's Fatoorah platform?

Yes. Terracez has delivered ZATCA Phase 1 and Phase 2 integrations for Saudi clients, including real-time invoice clearance with the Fatoorah API, QR code generation, and XML invoice formatting to ZATCA specifications. This integration is a standard component of every Finance and Operations deployment in Saudi Arabia.

Do you provide post-customisation support in Saudi Arabia?

Yes. Terracez provides managed support with defined SLAs following every customisation engagement. Our support teams are based in Saudi Arabia, covering Riyadh, Jeddah, and Dammam, with direct access to the consultants who designed and built the solution.

What industries have you delivered Dynamics 365 customisations for in Saudi Arabia?

Our Saudi Arabia customisation work spans construction and EPC, petrochemical and energy, manufacturing, trading and logistics, and real estate development. Specific examples include revenue recognition customisation for an engineering firm, an AI-based KYC compliance extension for a petrochemical trading company, bespoke estimation tools for construction and marine projects, and supply chain automation across multiple manufacturing clients.