The dates are the first thing to flag. Microsoft's roadmap entry (ID 577794) shows the feature as in development, with preview in January 2027 and general availability in March 2027. Other material points to an earlier schedule, so planners should check the dates before relying on them.
What Microsoft says it is building
The framework extends the existing Electronic Invoicing service. The roadmap lists three elements:
- A unified document model. It covers outbound and inbound documents and is based on international standards such as UBL and PEPPOL.
- A standard pipeline and API. It handles submission and response for e-invoicing documents and their statuses.
- An extensibility model. External ASPs, ISVs, Microsoft partners and customers can implement their own integrations without requiring Microsoft to build or maintain provider-specific connectors.
Responsibilities are split. Microsoft defines the data contract, the integration pattern and lifecycle handling. Providers such as PDPs, PAs and PACs implement the endpoints and data transformations on their side.
The stated aim is to decouple ERP from any single e-invoicing provider. In practice that should mean more choice of provider, faster onboarding of new providers and markets, and less vendor lock-in.
What it does not do
The roadmap is blunt about the limits, and these matter most for budgeting:
- It does not make Microsoft an Authorized Service Provider, which means no ASP, PDP, PA, PAC or PEPPOL access point status.
- It does not include built-in connectivity to e-invoicing providers.
- Customers must continue to use third-party e-invoicing providers for last-mile submission to tax authorities or clearance platforms.
- Integrating with a specific ASP is the responsibility of the provider, customer, or ISV.
This is a standard for connecting providers, not a compliance service. You still need a provider contract in every market where e-invoicing is mandated.
Rollout plan
In the initial phase, Microsoft defines the data contract and API specification and supports these in Dynamics 365 ERP and Electronic invoicing service. Microsoft will work with a selected set of ASPs to build and validate integrations for a subset of countries or regions. Customers would then pick from those providers based on where they operate and configure the integration in their ERP environment. The roadmap says later phases will add more countries and more ASPs and ISVs. It names no providers, markets or later dates.
How this differs from today's model
Microsoft Learn documents the current approach as provider-specific. Its ISV last-mile connector page says the connector is for cases where no direct integration with a government platform or recipient exists out of the box. Microsoft uses Edicom, with a Danish scenario, as the worked example. That example requires:
- A separate signed service agreement with the ISV.
- Credentials from the provider: a service ID, a group code and a token.
- The token stored as a secret in the customer's own Azure Key Vault.
- Configuration of pipeline actions to submit documents to Edicom and wait for the response.
- Separate feature setups for status retrieval and for inbound receipt.
In that example, Edicom analyzes the file format and routes OIOUBL files to Denmark's NemHandel and PEPPOL files to the PEPPOL Delivery Network. A shared contract and API could replace some of this per-provider setup. Whether it will is not stated.
Electronic Invoicing is already tied into the ERP. Per Learn, Finance and Supply Chain Management send business data in a unified JSON structure and then request the status of documents being processed. Depending on the scenario, the results can update ERP data such as invoice status or an externally supplied UUID.
Don't confuse "Completed" with "accepted"
Microsoft's submission log documentation carries a warning that matters for any new status API. Submission statuses are Scheduled, Executing, Pending, Completed, Failed and Canceled. They describe whether the Electronic Invoicing feature finished processing. They do not describe the final state of the invoice. A submission can show Completed while the external service has rejected the invoice.
The roadmap says the new API covers "related statuses" but does not say how pipeline completion and provider or regulator acceptance will be represented. Testing that mapping should be a priority in any pilot.
Conflicting timing signals
The roadmap lists January 2027 preview and March 2027 GA. Other sources describe an earlier schedule:
- A Microsoft 365 admin blog that republishes Microsoft's announcement, dated July 14, 2026, says the feature will reach general availability on August 8, 2026.
- An implementer blog from Alletec ties the framework to the 2026 Wave 1 release plan and gives the same August 8, 2026 general availability date.
- A Claydesk guide on UAE e-invoicing refers instead to a December release of the built-in feature.
The roadmap entry here is dated October 22, 2026, so it may reflect a revised schedule. I could not confirm this from the evidence. Microsoft's own caveat is that roadmap dates and descriptions are subject to change. Treat January and March 2027 as the current Microsoft estimate, not a commitment.
Where the UAE comes in
Several partner write-ups connect the framework to the UAE e-invoicing mandate, which is a likely reason for the interest. ClearTax says the native capability does not make Dynamics 365 an ASP. Its description of the division of labor is that the ERP generates and formats the data, and an external ASP validates, transmits and returns statuses. These are vendor sources with a commercial interest in ASP services. Their reading matches Microsoft's stated scope, but they are not primary evidence about the framework itself.
Scope: which products?
The roadmap title and product field name Dynamics 365 Finance. The business-value text names Finance, Supply Chain Management and Project Operations. Microsoft Learn already lists Electronic Invoicing as integrated with all three. It is not confirmed that the new framework will reach all three at the same time.
What admins and ERP owners should do now
- Treat it as planned, not available. Don't build a compliance plan around the framework until Microsoft publishes the contract and API.
- Keep provider contracts in place. Last-mile submission remains a third-party service.
- Ask your provider whether it is among the selected ASPs. Also ask which countries it will cover and whether it supports inbound as well as outbound documents.
- Review prerequisites. Today the service needs customer-owned Azure storage and a key vault, plus the Lifecycle Services add-in, which requires at least a Tier 2 environment. Whether the new framework changes any of that is unknown.
- Define test cases for status handling. Cover rejected, pending and failed invoices, not just the happy path.
Open questions
- No UBL or PEPPOL versions are specified, and no schema has been published.
- Endpoint authentication, error and retry behavior, and provider certification are all unspecified.
- Migration effort for existing provider-specific setups is unknown.
- It is unclear how easy switching providers will really be.
Standardizing the ERP side of provider integration is a sensible move that could cut custom work. Its value will depend on how many providers build to the contract and in which countries.
References
- Dynamics 365 Finance: Globalization Studio - Unified e‑invoicing integration framework Microsoft 365 Roadmap · 2026-10-22T23:45:45.624951Z
- How Do You Integrate Dynamics 365 With UAE E-Invoicing? The 30 October Sequence claydesk.ai
- Microsoft Dynamics 365 UAE E-Invoicing Integration - ClearTax cleartax.com