You went live on Dynamics 365 Finance & Operations. The implementation ticked every box on the project plan. And then reality hit: ZATCA rejected an invoice batch, your finance team is printing Arabic documents that look nothing like what the authority expects, and someone in IT is staring at a cryptographic stamping error they've never seen before.
This is not an unusual story. We hear it regularly from CIOs and ERP managers across Saudi Arabia. The problem is not D365 F&O itself — it is a genuinely powerful platform. The problem is that the standard global build was not designed with KSA-specific compliance at its core. Localising it properly requires deliberate, targeted customisation across several areas.
Here is exactly where the gaps are, and what needs to be done about each one.
The core issue: Standard D365 F&O handles global finance well. Saudi Arabia's regulatory environment — ZATCA Phase 2 e-invoicing, 15% VAT with multiple categories, bilingual legal documents — requires customisations that go well beyond switching the country/region field to SAU.
ZATCA Phase 2 Integration: The Biggest Gap in the Standard Build
ZATCA's Phase 2 e-invoicing mandate is where most post-implementation headaches originate. Phase 1 required generating QR codes on invoices — relatively straightforward. Phase 2 is a different matter entirely. It requires real-time integration with ZATCA's FATOORA portal, cryptographic stamping of every invoice, and a clear distinction in how B2B and B2C invoices are handled.
Out of the box, D365 F&O does not handle this. You need to configure the Saudi Arabian ZATCA submission feature within Globalization Studio, and that configuration has several components that must be set up precisely.
What the ZATCA Phase 2 customisation involves
- Cryptographic Stamp Identifiers (CSIDs): Every device or system submitting invoices must be onboarded with ZATCA and obtain a CSID. The Compliance CSID (CCSID) is used during testing; the Production CSID (PCSID) goes live. These must be configured in Azure Key Vault and mapped correctly in D365 F&O's electronic invoicing feature parameters.
- API endpoint configuration: The ZatcaAPIEndPoint parameter must point to either ZATCA's development portal or the production environment. Getting this wrong means invoices appear to submit locally but never reach FATOORA.
- B2B vs B2C invoice handling: Standard tax invoices (B2B) require clearance from ZATCA before they can be issued to the customer. Simplified invoices (B2C retail) must be reported within 24 hours of issuance. These are two distinct processing pipelines in D365 F&O, and both need to be configured separately.
- XML format and electronic reporting: D365 F&O uses Electronic Reporting (ER) to generate the UBL 2.1 XML format that ZATCA requires. The Sales e-invoice (SA) format must be imported, and application-specific parameters must be set up per legal entity.
The most common failure point we see: Teams complete the configuration but skip the internal validation step before pushing invoices to FATOORA. Building a pre-submission validation process that catches formatting or data issues before they reach ZATCA saves significant rework.
VAT Configuration: More Complex Than It Looks
Saudi Arabia's VAT framework sits at a standard 15% rate, but the reality in D365 F&O is more nuanced. Different VAT categories apply across transaction types, and the standard tax configuration does not account for all of them without deliberate setup.
Key VAT customisation areas
Area
What needs configuring
Sales tax codes
Separate codes for standard rate (15%), zero-rated, and exempt transactions
Sales tax groups
Correctly mapped to customer and vendor categories
Item sales tax groups
Assigned at product/service level, not just entity level
Prices include sales tax
Must be enabled specifically for KSA legal entities
VAT reporting
Arabic and English bilingual output for ZATCA audit submissions
Beyond the setup itself, the bigger risk is inconsistency across legal entities. Many Saudi businesses operating multiple entities — or a regional group with a KSA subsidiary — run into scenarios where VAT codes are configured correctly in one entity but inherited incorrectly in another. A VAT configuration audit across all legal entities is worth doing before any compliance review.
One area that catches teams off guard is zero-rated vs exempt transactions. These are treated differently in ZATCA's reporting requirements, and conflating them in D365 F&O's tax setup creates reporting errors that are difficult to unpick after the fact.
Arabic and Bilingual Localisation: Not Just a Language Setting
Switching D365 F&O's interface language to Arabic is straightforward. Producing legally compliant bilingual Arabic/English documents is not.
ZATCA requires that tax invoices include specific fields in Arabic: the supplier's name, address, VAT registration number, and invoice description. For many businesses, this means customising the document output formats in Electronic Reporting to produce parallel Arabic and English content, with right-to-left text rendering correctly on printed and PDF outputs.
What bilingual localisation actually covers
- Legal document templates: Sales invoices, credit notes, and delivery documents all need bilingual output. This is an ER format customisation, not a language pack installation.
- National address format: ZATCA requires a specific national address structure (building number, street name, district, city, postcode, country) that does not map directly to D365 F&O's default address fields. Custom fields or address format configurations are needed.
- Company registration and VAT number display: The Commercial Registration (CR) number and VAT Registration Number must appear on documents in the exact format ZATCA specifies. Default D365 F&O document layouts do not include this by default.
- Right-to-left rendering: Arabic text in PDF outputs needs to render correctly in RTL format. This is a known pain point in standard D365 F&O document generation and often requires custom SSRS or ER report templates.
The practical implication: if your finance team is manually editing invoices after generating them from D365 F&O to add missing Arabic fields or fix formatting, that is a customisation gap, not a user error.
Other KSA-Specific Customisations Worth Addressing
ZATCA and VAT get most of the attention, but there are several other areas where standard D365 F&O falls short for Saudi operations.
Withholding Tax (WHT)
Saudi Arabia applies withholding tax on certain payments to non-resident entities, typically at rates between 5% and 20% depending on the payment type. D365 F&O has a withholding tax module, but it needs to be configured specifically for KSA rates and categories. Many implementations leave this partially configured, which creates reconciliation issues at year-end.
Zakat Reporting
Zakat — the Islamic levy on business profits — is administered by ZATCA alongside VAT. The calculation basis and reporting requirements differ from standard corporate tax. D365 F&O does not have a native Zakat module, so businesses typically handle this through custom financial dimensions and reporting configurations, or via a third-party ISV solution integrated with F&O.
Multi-Currency and SAR Handling
While SAR (Saudi Riyal) is straightforward as a currency in D365 F&O, businesses with cross-border transactions need to ensure exchange rate configurations align with SAMA (Saudi Central Bank) published rates for reporting purposes. Using incorrect exchange rate sources creates discrepancies in statutory reporting.
Chart of Accounts Alignment
Saudi Arabia follows specific accounting standards, and the chart of accounts structure needs to reflect local statutory reporting requirements. A chart of accounts built for a European or US parent company will not map cleanly to what ZATCA and SOCPA (Saudi Organisation for Certified Public Accountants) expect.
How to Prioritise Your Customisation Backlog
If you are looking at this list and recognising multiple gaps in your current implementation, the natural question is: where do you start?
The answer depends on your compliance exposure, but as a general framework:
- ZATCA Phase 2 first — if your business is within the ZATCA rollout wave schedule and not yet fully integrated with FATOORA, this is your highest-risk item. Non-compliance carries financial penalties and can disrupt your ability to issue invoices to customers.
- VAT configuration audit second — even if invoices are going through, misconfigured VAT codes create cumulative errors in your VAT return that become harder to correct over time.
- Bilingual document compliance third — this is operationally disruptive but typically does not carry the same immediate penalty risk as ZATCA integration failures.
- WHT, Zakat, and chart of accounts — important for statutory accuracy but can be addressed in a structured remediation programme rather than an emergency fix.
The other consideration is upgrade risk. D365 F&O releases continuous updates, and customisations built on older versions of the Saudi Arabian ZATCA submission feature may need to be updated when Microsoft releases new versions of the electronic invoicing feature. Staying current on the feature version (currently version 14 or later for ZATCA submission) is part of ongoing maintenance, not a one-time project.
Working With a Partner Who Knows the KSA Landscape
The customisations described in this post are not edge cases or advanced configurations. They are the baseline for running D365 F&O compliantly in Saudi Arabia. The challenge is that many implementations are delivered by partners with strong global D365 expertise but limited depth in KSA-specific regulatory requirements.
At Terracez, we work with businesses across the region who are at exactly this stage: live on D365 F&O, but carrying a customisation backlog that is creating compliance risk or operational friction. Our approach starts with a structured assessment of your current configuration against KSA requirements, identifying exactly what is missing and what needs to be remediated.
If you are managing a D365 F&O environment in Saudi Arabia and recognise any of the gaps described here, get in touch with our team for a no-obligation assessment. We can give you a clear picture of where you stand and what it will take to get fully compliant and operationally optim
.png)
.webp)
