Microsoft ERP Integration · United Arab Emirates

Dynamics on PINT AE.

The awkward fact first: Microsoft has not shipped UAE e-invoicing for Dynamics 365. Finance & Operations is listed as planned for a later 2026 wave, and Business Central has no Microsoft UAE localisation at all — while your first deadline is 30 October 2026. This page is about closing that gap without betting on a release date.

Not shipped UAE e-invoicing is "planned" for F&O and absent from Business Central, per Microsoft's own coverage page
30 Oct 2026 Deadline to appoint an Accredited Service Provider if revenue is AED 50m or more
Key Vault A mandatory component of F&O electronic invoicing — and it lives in your tenant
Not an ASP Microsoft states its framework does not make it a service provider or access point
The timing problem

Your mandate date is not Microsoft's release date.

Microsoft's published electronic-invoicing coverage lists the United Arab Emirates as planned for 2026 release wave 2 in Finance & Operations. The UAE localisation page for F&O currently documents VAT reporting, the FTA audit file and an invoice layout — no e-invoicing. Business Central is further back still: the UAE has no Microsoft-delivered e-document localisation, and the base app is W1 with localisation left to partners.

Meanwhile the dates are fixed by decision, not by roadmap. Businesses at or above AED 50 million in revenue appoint an Accredited Service Provider by 30 October 2026 and go live on 1 January 2027. Below that threshold it is 31 March 2027 and 1 July 2027; government entities appoint by 31 March 2027 and go live 1 October 2027.

So the planning question is not "when will Microsoft ship it". It is "what do we build, and what do we deliberately not build, given that something has to be working before the platform vendor arrives". Answering that badly in either direction is expensive: build too much and you throw it away when the localisation lands; build too little and you miss a date that carries a monthly penalty.

Product status as at 28 July 2026, from Microsoft's own documentation. Microsoft is actively reshaping this area — treat any release-date claim, including ours, as perishable and re-check before you commit a plan to it.

The UAE dates, and where they come from
  • Pilot: commenced 1 July 2026; voluntary adoption open from the same date
  • Phase 1: revenue ≥ AED 50m — ASP by 30 October 2026, live 1 January 2027
  • Phase 2: revenue < AED 50m — ASP by 31 March 2027, live 1 July 2027
  • Government entities: ASP by 31 March 2027, live 1 October 2027
  • Legal basis: Ministerial Decisions 243 and 244 of 2025, with the first-phase dates set by Ministerial Decision 66 of 2026 — which amended only the first phase
  • Penalties: Cabinet Decision 106 of 2025 — but they do not apply to voluntary early adopters
The first decision

F&O and Business Central are not one product.

F&O

Finance & Operations

Microsoft's Electronic invoicing is a hyper-scalable multitenant service that runs processing logic outside Finance itself. It is enabled as an add-in through Lifecycle Services and configured in the Globalization Studio workspace.

  • Cloud only — Microsoft states electronic invoicing does not support on-premises deployments
  • Installing the add-in requires at least a Tier 2 environment
  • Deployment must sit in one of Microsoft's listed Azure geographies — the UAE is on that list
  • Customisation is by X++ extension; overlayering has been sealed since release 8.0
BC

Business Central

A different architecture entirely: the E-Document Core app plus AL extensions, with no Microsoft-hosted processing service behind it. Capable, but considerably more of the work is yours or a partner's.

  • Native Peppol support is BIS 3.0 only; other formats live in specific localisations and are not part of W1
  • Clearance-model support is a framework only — Microsoft states you must write an extension for your country's requirements
  • Built-in connectors exist for several providers, but you need a contract with them and Microsoft notes it may incur extra cost
  • The stock Peppol data-exchange definitions are illustrative — Microsoft says you likely cannot use them as is
Saudi

The contrast worth knowing

If your group also files in Saudi Arabia, the two platforms diverge sharply — which matters when one programme has to cover both jurisdictions.

  • ZATCA Phase 2 is shipped for F&O, with named configurations and minimum versions published by Microsoft
  • Business Central has no Microsoft ZATCA localisation — Saudi is Partner/W1 there too
  • Even on F&O, ZATCA onboarding and obtaining your CSIDs remain your obligation, not Microsoft's
  • See our ZATCA implementation notes for how the Saudi side behaves in practice
Stale advice

RCS is gone

A live trap. The Regulatory Configuration Service was merged into Globalization Studio from version 10.0.39, new provisioning stopped, and Microsoft planned full shutdown in August 2024.

  • Guidance that tells you to configure e-invoicing "in RCS" is describing a service that no longer exists
  • The Electronic invoicing add-in is a different component and remains current — do not conflate the two
  • Some Microsoft pages still reference RCS despite recent updates; that is a documentation defect, not a live path
  • The Global repository was likewise deprecated, with lifecycle management moving to Dataverse solutions
Key custody

Azure Key Vault is not optional, and that is good news.

Microsoft documents a key vault as a mandatory component of Electronic invoicing, alongside a storage account. It holds the storage account's shared access signature token, the secrets used across scenarios, and the certificates used for digital signing and for establishing trusted connections to external services. For cloud deployments it is the only supported option in production.

The reason this matters commercially is that it settles the argument most ERP e-invoicing projects have late and badly. The vault is in your Azure tenant. Your signing certificates stay under your control, referenced by the platform rather than handed to it — Microsoft's own configuration format points at a vault path and a secret name rather than embedding the material.

Two operational details that catch people out. If you reference a secret without pinning its version, the system resolves to the active certificate with the latest expiration date — convenient, and a silent way to pick up the wrong certificate during a renewal overlap. And because the vault is yours, so is the renewal calendar: nobody else is watching those expiry dates for you.

What to settle before build
  • Vault ownership: your subscription, your access policies, your audit trail
  • Access model: who and what can read the signing secret, and how that is reviewed
  • Version pinning: whether you pin certificate versions or accept latest-expiry resolution
  • Renewal calendar: owned by a named person, with alerting well before expiry
  • Data residency: UAE rules require invoice data to be stored within the State — decide where the vault, the storage account and the archive sit
  • Exit: what a provider hands back, in writing, at the start
Read this before you scope

Microsoft says, in writing, that it is not your service provider.

This is the single most useful sentence in Microsoft's e-invoicing documentation, and the one most often missed in ERP-led compliance plans. Its release plan for the unified e-invoicing integration framework states that the feature does not make Microsoft an authorised service provider, PDP, PAC or Peppol access point; that it does not include built-in connectivity to e-invoicing providers; and that customers must continue to use third-party providers for last-mile submission. Integrating with a specific provider is described as the responsibility of the provider, the customer or an ISV.

In UAE terms that is decisive. The mandate requires you to appoint an Accredited Service Provider — the Ministry currently publishes a pre-approved list, with final accreditation to follow. No amount of Dynamics configuration satisfies that obligation, because the obligation is about who carries your invoice into the five-corner network, not about how your ERP renders it.

The practical consequence: an ERP workstream and an ASP appointment are two separate decisions on two separate clocks, and the ASP clock runs out first — 30 October 2026, two months before go-live. Teams that treat this as one project routinely discover the appointment is the long pole.

The UAE mandate in detail →
UAE specifics that change the design
  • No QR code. UAE invoices are XML and do not carry a QR code — unlike Saudi. Do not copy a ZATCA design
  • B2B and B2G only. B2C is out of scope until a further decision
  • Not just VAT registrants. The system applies regardless of VAT registration status, subject to the published exclusions
  • 14 days. Invoices must be issued and transmitted through the system within 14 days of the business transaction
  • Outage reporting. System failures must be notified to the Authority within the prescribed window — this is what the daily penalty attaches to
  • Data stays in the State. Invoices and associated data must be stored within the UAE
Prerequisites

What has to be true before anyone writes code.

As with every mandate, the integration is rarely what delays you. The delay is master data and identifiers discovered mid-build.

The UAE requires a specific participant identifier: the Tax Identification Number, being the first ten digits of the Corporate Tax registration number — and for members of a tax group it is the member's own number, not the group representative's. That single rule has re-opened more customer and legal-entity master-data programmes than any technical requirement on this page.

Field coverage is published by the Ministry as a versioned document rather than buried in a spec: 51 mandatory fields for an electronic Tax Invoice, and 49 for a commercial electronic invoice. Because it is versioned, treat it as a moving target and check the current release rather than a consultant's summary of it.

Readiness checklist
  • Participant identifiers correct per entity, including each tax-group member separately
  • Customer and supplier master carrying counterparty identifiers for every trading partner
  • Tax determination mapped to the treatments the format expects
  • Entity and branch structure resolved — which legal entity issues, and from which Dynamics instance
  • Environment tier sufficient for add-in installation, with parity to production
  • ASP appointed — the long pole, and a contractual process, not a technical one
  • Archive and residency decided, given the in-country storage requirement
Sequencing

How we would run it, given the release uncertainty.

01

Decide the bet

Agree explicitly whether you are waiting for Microsoft's localisation or building ahead of it, and write down what changes if the release slips. Most groups at or above the AED 50m threshold cannot responsibly wait.

02

Appoint the provider

Start the ASP appointment first, because it has the earliest hard date and is a commercial process with its own lead time. Choose on exit terms and interoperability, not on a demo.

03

Data, then plumbing

Fix identifiers and master data in Dynamics before generating documents. Stand up the vault and storage account early — they are prerequisites, not build tasks, and access approvals take longer than the configuration.

04

Pilot deliberately

Voluntary adoption has been open since 1 July 2026 and penalties do not apply to voluntary participants — which makes the pilot window the cheapest place in the whole programme to be wrong. Use it.

What drives cost: whether you are on F&O or Business Central (Business Central carries materially more custom build for the UAE), the number of legal entities and issuing instances, master-data condition, whether Saudi is in the same programme, and how much you choose to build ahead of Microsoft's localisation. We do not publish a rate card, because those factors move the number more than a list price would. What we commit to is directional pricing on the first call and a written fixed-fee quote within 24 hours.

Vendor neutrality

When we would tell you to build less.

We operate a Peppol-certified Access Point, so we have an obvious interest in recommending work. Here is where we would argue against it.

You are in Phase 2 on Finance & Operations. If your revenue is below AED 50 million, your appointment date is 31 March 2027 and go-live is 1 July 2027. Microsoft's localisation may well land inside that window. Building a full custom format layer now, on F&O specifically, risks paying for something you will later replace — do the master-data work, appoint the provider, and keep the build thin.

Business Central at low volume. The e-document connector route with an established provider will usually beat a bespoke AL build, and Microsoft has already wired the framework for several providers. The bespoke case is real only at genuine complexity — multi-entity, unusual document types, or an existing integration estate.

A platform move already scheduled. If you are mid-migration between Business Central and F&O, or consolidating instances, build the compliance layer against the destination and bridge the deadline on the source with the lightest option that is compliant.

What does not change is the ASP appointment. That is required by decision regardless of platform, vendor or architecture — including if you appoint someone other than us.

Sources for the claims on this page
  • Product status: Microsoft's published electronic-invoicing country coverage, UAE localisation page, and Business Central e-documents documentation
  • Key Vault: Microsoft's electronic-invoicing components and Key Vault client configuration documentation
  • "Not an ASP": Microsoft's release plan for the unified e-invoicing integration framework
  • UAE dates and obligations: Ministerial Decisions 243, 244 of 2025 and 66 of 2026; Cabinet Decision 106 of 2025
  • Field counts and identifiers: the Ministry's published mandatory-fields document, V1.0
  • Format: PINT AE, published by OpenPeppol

Verified against those primary sources on 28 July 2026. Microsoft's e-invoicing architecture is mid-transition; re-check product status before relying on it.

Questions we actually get

Asked on most Dynamics discovery calls.

Can we just wait for Microsoft to ship UAE e-invoicing?

If you are in Phase 1 — revenue at or above AED 50 million — we would not. Your ASP appointment is due 30 October 2026 and go-live is 1 January 2027, while Microsoft's UAE support for Finance & Operations is listed as planned for a later 2026 wave and Business Central has no Microsoft UAE localisation at all. Waiting means betting a penalty-bearing deadline on a release date you do not control. Phase 2 is a genuinely different calculation, and there we might well advise waiting on the format layer while doing the data and provider work now.

Is Microsoft an Accredited Service Provider?

No, and it says so directly: the feature does not make Microsoft an authorised service provider or Peppol access point, it does not include built-in connectivity to providers, and customers must continue to use third-party providers for last-mile submission. The UAE obligation to appoint an Accredited Service Provider is separate from anything you configure in Dynamics.

Where do our signing certificates live?

In an Azure Key Vault in your own tenant. Microsoft documents the vault as a mandatory component and, for cloud deployments, the only supported production option. The platform references a secret by vault path and name rather than holding the material itself. One caution: if you do not pin the secret version, the system resolves to the active certificate with the latest expiry — which can quietly select the wrong certificate during a renewal overlap.

We were told to configure this in RCS. Is that right?

Not any more. The Regulatory Configuration Service was merged into the Globalization Studio workspace from version 10.0.39, new provisioning was stopped, and Microsoft planned full shutdown in August 2024. If a proposal still centres on RCS, it is working from stale material — though in fairness a few of Microsoft's own pages still mention it. The Electronic invoicing add-in is a separate component and is current.

Does the UAE invoice need a QR code like Saudi?

No. UAE invoices are XML and do not carry a QR code. This is one of several places where copying a ZATCA design produces the wrong answer — the UAE model is a five-corner exchange through Accredited Service Providers with reporting to the Authority, not a clearance-and-stamp model. Groups running both jurisdictions should expect two designs sharing master data, not one design applied twice.

We run both Dynamics and another ERP. Does that change anything?

It changes the shape of the programme rather than the obligation. Each system that issues invoices needs its own path to your provider, and each legal entity needs its own correct identifier — including separate identifiers for tax-group members. What you should not do is run two independent compliance projects: the master data, the provider relationship and the archive are common, and only the ERP-side extraction differs.

Other ERPs

We integrate on your ERP — we don't replace it.

Each mandate lands differently on each platform. These are the ones we implement most often in the GCC.

SAP Oracle Zoho Tally Odoo

Mandate Monitor

Deadlines move. We will tell you when.

Short, source-checked notes when a GCC mandate actually changes — a wave announced, a specification revised, a date moved. Written by the people doing the implementations. No sequence, and you can leave in one click.

We use it to send mandate updates and nothing else. See our privacy policy.

Start with thirty minutes.

Tell us whether you are on Finance & Operations or Business Central, your revenue band, and how many entities issue invoices. We will tell you what to build now, what to leave for Microsoft, and where your ASP deadline really sits — with a written fixed-fee quote within 24 hours.

Book a consultation → Read the UAE mandate briefing Free · Senior practitioner · Quote in 24 hours