ZATCA and e-invoicing in Dynamics 365 F&O

Station seven said the electronic reporting layer is the compliance engine. This station is its most important application in this region.

Start with the difference that decides the product in the Gulf: Microsoft ships ZATCA phase two here, and does not ship it in its smaller sibling. The comparison in figures is in the Dynamics 365 Finance & Operations guide.

What the vendor ships, by name

Microsoft’s documentation does not settle for saying the product “supports ZATCA”. It names the components, which is what makes the claim checkable.

Component	Its name in the documentation
The service	The Electronic Invoicing service, inside the Globalization Studio workspace
Sales format configuration	Sales e-invoice (SA)
Project format configuration	Project e-invoice (SA)
Submission feature	Saudi Arabian Zatca submission (SA)
Compliance check feature	Saudi Arabian ZATCA compliance check (SA)

The practical moment that separates a consultant from everyone else: when a customer asks “is the system ZATCA-ready?”, the answer is not yes but the names of these components and their versions. The documentation states minimum versions per feature, and the configurations are imported from a repository and revised over time.

Which means “ready” is a version rather than a permanent state. Anybody who imported a configuration two years ago and never updated it may be submitting in a format no longer accepted.

What stays with the implementer

The service transmits; the correctness of what it transmits comes from your data.

What has to be set	Where
Tax registration number and entity details	The legal entity
A complete, correctly formed address	Address data
Tax groups, rates and statuses	Tax setup
Payment methods mapped to a standard code list	The configuration’s application-specific parameters
Units of measure in their standard coding	Master data

The second-to-last row deserves a pause: the ZATCA configuration in this product asks you to map every payment method you have defined to a standard international code list. Skip it and you submit an invoice rejected for a reason that has nothing to do with accounting.

The rule that compresses this station: a rejected invoice is fixed in master data, not on the invoice. Get station three right and you never see most of these errors.

The UAE — the limit today

Here it has to be said as it is rather than as one might hope.

Microsoft placed UAE e-invoicing in the 2026 release wave one plan: public preview July 2026, general availability December 2026.

And even after general availability an accredited service provider remains mandatory for transmission — not because the product lacks something, but because the UAE model itself requires an accredited intermediary. The product produces the document in the required format; the provider transmits it and reports to the authority.

So the question to ask at any demo: which version of the feature, with which named accredited provider, and who owns the integration between them? The mandate itself is covered in UAE e-invoicing, the Saudi requirement in ZATCA phase two, and the systems compared in the readiness table.

What to do when the requirement changes

E-invoicing configuration here is not a setting applied once. It is a version that gets updated.

The update cycle is three steps, repeating.

Step	What you do	Who owns it
1. Watch	Monitor feature releases in the repository	Finance with the partner
2. Import and test	Import the new version into the test environment and issue a document	IT
3. Publish	After the test document is accepted	Finance approves

Step one is the one that gets neglected, because nobody owns it explicitly. The result is a recurring pattern: the system works for a year, then a whole batch is rejected in one day, and it emerges that the authority changed the format and the configuration was never updated.

This meets the quarterly update policy at station nine: an item reading “verify the e-invoicing configuration version” is added to every update’s test checklist, so one process covers both files instead of two.

Arabic on screen

Arabic is a first-class language in this product, unlike its smaller sibling. Microsoft publishes a dedicated documentation page on financial dimensions and main accounts in right-to-left languages — and its existence says something useful: the account structure specifically is where the direction problem lives, rather than the surface. Which is what you built at station three.

The difference between a language appearing in a list and a screen working in it is what decides user acceptance.

Ask for three screens in Arabic at the live demo: supplier invoice entry, a trial balance, and a printed sales invoice. The third matters most, because it reaches the customer and the authority.

And recall station one: MB-310 is offered in English and Japanese only, so Arabic is on the screen and of no help in the exam.

What you actually do in this station

• Read Microsoft’s Saudi e-invoicing page in full, and list the components and their versions.
• List the fields the document requires, and mark where each is populated in master data.
• Set up tax groups for four cases: a domestic sale, an export, a reverse charge, and an invoice-level discount.
• Write the three-part UAE demo question and try it on a real partner.
• Ask for screenshots of the three screens in Arabic.

The three commonest mistakes

One: saying “the system supports ZATCA” with no version. Support is a version rather than a state, and a stale configuration submits in a superseded format.

Two: fixing rejected invoices on the invoice. The fix is in master data, or the rejection repeats daily.

Three: assuming the UAE works like Saudi Arabia. The models differ, and an accredited intermediary is mandatory there however mature the product.

The acceptance test for this station

1. Name the Saudi e-invoicing components as Microsoft documents them.
2. Explain why “ZATCA-ready” is a version rather than a state.
3. Name five master data fields the electronic document depends on.
4. Explain the UAE position today with its dates, and the provider’s role.
5. Name the three screens asked for in Arabic, and why the third matters most.

What comes next

You know the product’s limit in front of the state. The next station is its limit in front of you: extensions and updates — extension without overlayering, four updates a year of which two cannot be refused, and a free testing tool that decides whether updates are routine or a crisis.