What Microsoft says is coming
The roadmap entry (ID 579962) covers Dynamics 365 Finance and Dynamics 365 Supply Chain Management. Its status is In development, and the general availability target is December 2026. It applies to the Worldwide (Standard Multi-Tenant) cloud instance and to the web platform.
Microsoft describes two capabilities:
- An end-to-end, Electronic Invoicing service-based option. Invoices and credit notes from sales orders, free text invoices and project invoices would go out in the UAE extension of PEPPOL International (PINT) XML. They would travel over the PEPPOL Delivery Network. EDICOM would act as the Accredited Service Provider (ASP).
- A generation-only option. XML files would be produced using only the Electronic Reporting (ER) framework, with no service transmission.
December 2026 is a roadmap target, not a shipped fact. Microsoft says roadmap dates are subject to change. Nothing I reviewed confirms that the service-based transmission option or the EDICOM connection is live today.
Correcting the deadlines
The roadmap text frames the mandate as January 1, 2027 for "large and major" companies and July 1, 2027 for small and medium-sized ones. The UAE Ministry of Finance uses revenue thresholds instead. Search coverage of the Ministry's guidance agrees on the following:
| Group | ASP appointment deadline | Mandatory implementation |
|---|---|---|
| Annual revenue of AED 50 million or more | October 31, 2026 (some sources say October 30) | January 1, 2027 |
| Annual revenue below AED 50 million | March 31, 2027 | July 1, 2027 |
| Government entities | March 31, 2027 | October 1, 2027 |
Two points follow from this.
- The first group's appointment deadline has passed. As of November 17, 2026, a business at or above AED 50 million should already have an ASP. The window from October 30 to January 1, 2027 is only 63 days, and it has to cover integration, data mapping and testing. That deadline was originally July 31, 2026. In May 2026, the Ministry extended it to October 30, 2026. The go-live date did not move.
- A late ERP feature does not extend any deadline. The mandate is a legal date, not a software release date. A December GA target leaves very little room between Microsoft's feature and the January go-live.
Some commentary also cites penalties. One source says the penalty regime includes AED 5,000 for each month or part month of failing to implement or appoint an ASP on time. That figure comes from a secondary source. Check the current penalty decision on the Ministry portal before relying on it.
Generating XML is not the same as complying
The UAE uses a Decentralized Continuous Transaction Control and Exchange (DCTCE) model, also called the five-corner model. The Ministry says an e-invoice is structured invoice data exchanged between supplier and buyer and reported electronically to the Federal Tax Authority. It states that PDFs, Word documents, images, scans and emails are not e-invoices.
In outline, the flow works like this:
- The supplier's system (Corner 1) sends PINT AE invoice data to the supplier's ASP (Corner 2).
- The supplier's ASP validates the data, converts it to UAE-standard XML if needed, and passes it to the buyer's ASP (Corner 3). Tax data is reported to the authority (Corner 5).
- The buyer's ASP validates the invoice and delivers it to the buyer (Corner 4). It reports on success and returns status messages.
An ERP that only writes XML covers Corner 1 and nothing else. That is why Microsoft's two roadmap options differ. The ER-only option produces the file. The service-based option is meant to carry the file through a provider and network. Neither replaces your own legal and tax review, and your ASP must be accredited by the Ministry.
What Finance already documents today
Microsoft Learn already has a UAE guide for generating PINT XML from Finance, last updated on November 5, 2026. This is the ER-based path. Treat it as setup guidance for XML generation, not proof that service-based transmission has shipped.
Prerequisite: the primary address of the legal entity must be in the United Arab Emirates.
Configuration steps documented by Microsoft:
- Import four ER formats in the Electronic reporting workspace:
- PINT Sales e-invoice (AE)
- PINT Sales e-credit note (AE)
- PINT Project e-invoice (AE)
- PINT Project e-credit note (AE)
- Reference the formats under Accounts receivable > Setup > Accounts receivable parameters, on the Electronic documents tab. Map sales and free text invoices, their credit notes, project invoices and project credit notes to the matching formats.
- Set up legal registration numbers. Create a UAE registration type and a category of Enterprise ID (COID). The generated files use this category for the seller's commercial registration number.
- Confirm the address structure. At a minimum, configure Country/region, State, City and Street.
- Enter the seller's TRN on the legal entity's Tax registration FastTab. Microsoft notes that the first 10 characters of the TRN are the TIN. They are used in the seller's endpoint identifier for routing.
- Enable customers for e-invoicing by setting the eInvoice option to Yes on the Invoice and delivery FastTab. Enter each customer's TRN in the Tax exempt number field, plus a registration ID where needed.
- Review identification schemas. The default is schema 0235 (UAE Tax Identification Number). Seller and buyer schemas can be overridden with electronic document properties (CompanyEndpointType and CustomerEndpointType).
- Map units of measure and sales tax codes to external codes, using UNECE Recommendation 20 for units and a subset of UNCL5305 for tax categories. If no unit applies, the default is EA. The description on a sales tax exempt code becomes the Tax Exemption Reason in the XML.
The transaction type code
UAE e-invoices must carry a transaction type code in the Invoice\cbc😛rofileExecutionID element. Microsoft's documented implementation is only partial:
- Free Trade Zone: supported through electronic document properties. A property value can be set at the legal entity, customer, customer invoice or project invoice level. Invoice-level values override customer-level values, which override legal-entity-level values. Any non-empty value turns it on.
- Summary invoice: set to 1 when an invoice covers several deliveries with different dates.
- Export transaction: set to 1 when the invoice is issued to a customer outside the UAE.
- Deemed supply, profit margin scheme, continuous supply, disclosed agent billing and supply through e-commerce: out of scope, always 0.
If your business issues invoices in any of the always-zero categories, the documented ER implementation does not mark them. Raise this with your implementation partner and ASP now, not in January.
Generating and viewing files
After posting an invoice, open the invoice journal, select the invoice and choose Send > Original on the Invoice tab. Microsoft says to find the XML under Organization administration > Electronic reporting > Electronic reporting jobs. Select a job, then Show files. If generation fails, Show log > Message details explains why.
ER destinations can send the XML automatically on posting. The Print invoice parameter must be turned on when you post for this to work.
Preparing for the service-based option
Microsoft's general Electronic Invoicing setup page names the prerequisites. You need a Lifecycle Services (LCS) project that includes Finance or Supply Chain Management. The apps must be deployed in a supported Azure geography. The page lists the United Arab Emirates among them. After that, enable the Electronic invoicing integration feature in Feature management. Then set the service endpoint and environment under Organization administration > Setup > Electronic document parameters.
That page is general and not specific to this roadmap item. Don't assume the UAE service will use exactly this path once it arrives.
A readiness checklist
Based on the Ministry's guidance and Microsoft's documentation:
- Work out your phase. Check your revenue against the AED 50 million line. Government entities follow their own schedule.
- Confirm your ASP. The Ministry maintains the official ASP list and notes that accreditation status is updated. If you plan to use EDICOM through Microsoft's service, confirm with both companies that the integration is live and that EDICOM's accreditation is current.
- Check scope and exclusions. The Ministry's 2026 amendment lists exclusions, such as certain sovereign government activity, specified airline transactions, and qualifying exempt or zero-rated financial services. It also covers transactions within a tax group for 24 months from January 1, 2027. Not every invoice is automatically in scope.
- Mind the 14 business days. The amended decision requires covered e-invoices or credit notes to be issued and transmitted within 14 business days of the transaction, subject to its provisions.
- Clean your master data. TRNs, addresses, units and tax codes must be accurate, because the XML is built from them.
- Test exchange, not just files. Test sending, receiving, reporting and status messages with your ASP. Set up error-resolution ownership between finance, IT and the provider.
- Plan for partial adoption. Not every counterparty will be onboarded at the start, so keep buyer and supplier data available.
Analysis
The roadmap item is useful, but it is easy to read too much into it. A December GA target for a roadmap feature does not equal a tested production rollout by January 1. For businesses at or above AED 50 million, the practical question is how a partner-delivered or ASP-delivered interim route will cover them if the Microsoft service slips. Smaller businesses have breathing room. Their appointment deadline is March 31, 2027, and go-live is July 1, 2027.
Independent commentary frames this as a squeeze, with only about nine weeks between the appointment deadline and go-live. That is one view, but the dates support it. A fair counterpoint: the Ministry did extend the first appointment deadline once already. It has kept the go-live date fixed, so no one should plan on further relief.
Microsoft's roadmap is a statement of intent and the Ministry portal is the authority on UAE law. Verify any compliance claim against the Ministry's current guidance and your ASP, and keep an eye on the Finance feature management and release notes for the actual release.
References
- Dynamics 365 Finance: Meet requirements for electronic invoicing in the United Arab Emirates Microsoft 365 Roadmap · 2026-11-17T18:36:41.967573Z
- Customer electronic invoices for United Arab Emirates - Finance | Dynamics 365 | Microsoft Learn learn.microsoft.com
- Activate and set up integration with Electronic invoicing - Finance | Dynamics 365 | Microsoft Learn learn.microsoft.com