How do you integrate Dynamics 365 with UAE e-invoicing? The sequence that beats 30 October

A Dynamics 365 UAE e-invoicing project has an unusual shape: the regulator's dates are fixed, and the platform vendor's date lands almost on top of them. The mandate — Ministerial Decisions 243 and 244 of 2025, with the first phase re-dated by Ministerial Decision 66 of 2026 — requires businesses at or above AED 50 million in revenue to appoint an Accredited Service Provider by 30 October 2026 and to issue e-invoices from 1 January 2027. Microsoft's release plan, meanwhile, puts general availability of its built-in UAE functionality for Finance & Operations in December 2026. Three weeks of official runway. The question Dynamics shops keep asking us is the right one: what do you build now, what do you wait for, and in what order?

What the calendar says, precisely

The facts, verified against the Ministry of Finance's publications and Microsoft's release plan on the day this was written. The pilot began on 1 July 2026, with voluntary adoption open from the same date. Businesses whose annual revenue is AED 50 million or more appoint an accredited provider by 30 October 2026 and go live on 1 January 2027. Businesses below the threshold appoint by 31 March 2027 and go live on 1 July 2027; government entities appoint by 31 March 2027 and go live on 1 October 2027. A penalty regime exists under Cabinet Decision 106 of 2025 — and it does not apply to voluntary early adopters. The scope is B2B and B2G; B2C stays out until a further decision. The full legal picture is on the UAE compliance page, which we keep current against the Ministry's announcements.

Where Microsoft actually is

Microsoft's release plan for Dynamics 365 Finance lists UAE electronic invoicing under 2026 release wave 1: public preview from July 2026, general availability in December 2026. The feature generates invoices and credit notes from sales orders, free text invoices and project invoices in PINT XML, transmitted over the Peppol network under the five-corner model the UAE has adopted. That is a real commitment, and it is later than a Phase 1 deadline can tolerate. Release plans also carry Microsoft's own caveat that timelines and functionality may change — a caveat worth taking literally, because this one has already moved between waves.

Business Central is a different story: there is no Microsoft-delivered UAE e-invoicing localisation. The base app for the UAE is W1, localisation is left to partners, and the e-document framework expects a country extension that someone — a partner, a provider, or you — has to build and maintain. F&O and Business Central are different projects wearing the same brand. Scope them separately, even inside one group. The platform mechanics — the Globalization Studio add-in, the mandatory Azure Key Vault and whose tenant it sits in, the retired RCS trap — are treated fully on the Dynamics 365 integration page. This note is the sequence.

The two clocks

Microsoft states in its release plan for the unified e-invoicing framework that the feature does not make Microsoft an authorised service provider or Peppol access point, and that customers must continue to use third-party providers for last-mile submission. In UAE terms: whatever Dynamics ships, you still appoint an Accredited Service Provider, because the legal obligation is about who carries your invoice into the five-corner network, not how your ERP renders it. The Ministry's accredited list — published under Ministerial Decision 64 of 2025 and updated periodically — stood at 48 providers, with four more in final assessment, when we checked on 31 August 2026. ZATCA-style capacity crunches reward the early mover: the selection questions are on the ASP selection scorecard, and the lock-in questions are the ones to ask before signing, not after.

So run two clocks. The ASP appointment is due 30 October 2026 — roughly sixty days from this page's publication date. The ERP workstream runs to 1 January 2027. Teams that treat these as one project routinely discover the appointment was the long pole.

The six-stage sequence

1. Scope: which entities, which phase, which Dynamics. List every entity in the group, its revenue against the AED 50 million test, and which system issues its invoices. Note that the obligation applies regardless of VAT registration status, subject to the published exclusions — the revenue test, not the VAT register, decides your phase. A group on F&O for contracting and Business Central for a trading subsidiary is running two integration projects under one programme, with different architectures and different vendor coverage.

2. Audit the data before touching the architecture. The Ministry's field list defines 51 mandatory fields on an electronic Tax Invoice, validated field by field; the e-invoicing participant identifier is not your 15-digit TRN, and the distinction generates rework when discovered late. Seller records that match registrations character for character, structured addresses, buyer identifiers, tax category per line: this is where UAE projects actually slip, and it is measurable today with no provider appointed. We publish both the field-by-field guide and the 25-point self-scoring checklist — run the checklist before any vendor conversation, because remediation is provider-independent and transfers with you.

3. Make the architecture decision deliberately. On F&O the realistic options are three. Wait for Microsoft's GA and configure the built-in feature — cleanest long-term, but it leaves your compliance date resting on a December release and a January enforcement. Generate from the ASP side — most accredited providers extract from Dynamics and construct the PINT AE document in their own platform, which decouples you from Microsoft's calendar at the cost of a second mapping layer to maintain. Or a hybrid: do the data and extraction work now so either path can be switched in, and decide the format layer when the GA lands. On Business Central the decision is starker — a partner extension or the provider's connector, because there is no Microsoft localisation to wait for. In every variant, the work that is never thrown away is the master data layer. Build that first.

4. Appoint the ASP — by 30 October, not alongside the build. The appointment is a legal deadline with a published list; the integration is a project with a plan. Do not sequence the first behind the second. Ask the custody questions before signing: where invoice data is stored (UAE rules require storage within the State), what the exit terms return to you, and what the provider's Dynamics connector actually consumes — a BI Publisher extract, an OData feed, a middleware agent — because that answer sizes your integration work more than any brochure does.

5. UAT with production-shaped data, including the ugly documents. Clean invoices pass first time almost everywhere. Failures concentrate in credit notes referencing originals, foreign-currency invoices with their AED amounts, prepayments, self-billing and inter-company charges. Test the 14-day issuance-and-transmission window against your actual month-end batch behaviour. And resist copying a Saudi design: UAE invoices carry no QR code, and the exchange model differs — a point that catches every team that ran a ZATCA programme first.

6. Cut over, then run it as an operation. Go entity by entity where structure allows. Staff the run state: a named owner for rejections who fixes root causes in master data — the rejection log is a data audit you didn't order — and treat Microsoft's GA, when it arrives, as a planned change window with its own regression cycle, not a rescue that replaces the operation you built.

Where Dynamics projects slip

Three patterns repeat. First, betting the plan on the GA date: a December release against a January mandate leaves no room for the regression cycle a finance system change deserves, and preview functionality is not a production commitment. Second, assuming Business Central is covered because F&O is — the Microsoft coverage that exists is F&O-only, and BC entities discovered late become the project's critical path. Third, reusing the Saudi design: groups that built for ZATCA assume clearance, QR codes and a portal OTP ceremony, none of which describes the UAE's five-corner exchange. The jurisdictions share a region, not an architecture.

How long does this take?

Counting back from 1 January 2027: UAT through November-December, ASP contract signed and onboarding started by late October, data remediation running from September — which makes a Phase 1 Dynamics shop starting now on time, with no slack for a second attempt. The scoping and the data audit are stages one and two of the readiness assessment, and that conversation is free, with a senior practitioner. The remediation itself is the data practice's bread and butter; the connector and extension work sits with the ERP integration practice; and the compliance framing is described plainly on the e-invoicing practice page.

Dates, thresholds and the provider count were verified on 31 August 2026 against the Ministry of Finance's publications (Ministerial Decisions 243 and 244 of 2025, Ministerial Decision 66 of 2026, and the Ministry's accredited-provider list) and Microsoft's Dynamics 365 release plan. All of these are revised without ceremony — check the primary documents before relying on any date here.