What's New: E-Documents and Clearance Model (2025 release wave 2)
Business Central's clearance model for e-documents (2025 release wave 2): a framework for invoices that tax authorities or third-party partners must pre-approve before they go to customers. It is not localized by default, the clearance service must be built per country, and receiver validation is announced for later.
- Introduction and session overview
- Business value of clearance model and e-documents
- Multiorder vs clearance model architecture
- Clearance model process and future features
- Setup requirements and workflow configuration
- E-document service and workflow demo setup
- End-to-end clearance workflow demonstration
- Framework approach and localization strategy
- Summary and resources
Overview
The session explains why many countries require invoices to be pre-approved by a tax authority or partner, and how the e-documents framework now covers this with a clearance model. It contrasts the multiorder architecture with the clearance model, which needs a different foundational process, and supports three, four or five corner models.
The demo covers setting up two e-document services (one for clearance, one for sending to the customer) and a workflow with five steps, from document creation to emailing the customer. It shows a clearance response with a QR code carried into the invoice and email attachment. The video ends on localization strategy: Microsoft provides the framework, partners build country implementations, and Microsoft plans to migrate its India and Mexico e-invoicing and to deliver VeriFacTur 2 for Spain.
Key points
- The clearance model is a framework for invoices that tax authorities or third-party partners must pre-approve before they are sent to customers. It needs a different architecture from the earlier multiorder model, which supported three-, four- and five-corner setups.
- It is not localized by default. Each country localization must be built separately on top of the framework.
- Two e-document services are needed: one for clearance submission to the authority and one for sending to the customer. The clearance service does not exist in Business Central and must be built per country.
- The workflow template guides setup through five steps, from document creation to customer email delivery. Workflow setup and service endpoints are configured manually for each localization.
- Clearance responses can include a QR code, which is embedded in the invoice and in the customer email attachment, depending on localization requirements.
- Receiver-side validation is not supported yet. It is announced for future delivery with no timeline given.
- Microsoft is planning to migrate India and Mexico e-invoicing to the new e-documents format, and to deliver VeriFacTur 2 for Spain. No timeline was given.
Features
| Feature | Status | At | Evidence |
|---|---|---|---|
| Clearance model for e-documents | status not stated, demoed | 0:31 | |
| E-document workflow orchestration | status not stated, demoed | 4:03 | |
| Clearance service and provider service setup | status not stated, demoed | 4:03 | |
| Access point support (sender and receiver) | status not stated | 3:35 | |
| QR code support in e-documents | status not stated, demoed | 2:25 | |
| Receiver validation (future) | announced | 3:23 | “Currently this is not supported. This is something what we will deliver in the future to fully support clearance model is validation as a” (3:23) |
| Migration of existing e-invoicing formats | announced | 9:16 | “now we will start planning how to migrate Indian and Mexican e voicing to new e documents format and verifact 2 in Spain as” (9:36) |
AL objects mentioned
As heard in the captions. A name that matches one object page by exact type and name links to it; the others stay as named.
- page “e document service page” at 4:57
- page “e document page” at 6:52
- page 43 “Sales Invoice” at 6:34
- page 132 “Posted Sales Invoice” at 7:47
Not found in BC28-30: page “e document service page”, page “e document page”.
Quotes
- 0:31 “Clearance model was something we missed when we deliver this functionality. This is new framework and we had some time to stabilize to create”
- 0:41 “many countries require that when you need to have pre-approved by tax authorities or some other third party partners your invoice”
- 1:16 “this is now in a framework very similar as we had for other e document features this is framework this is not by default”
- 2:00 “It require different architecture. So process is process foundational process this is different.”
- 3:23 “Currently this is not supported. This is something what we will deliver in the future to fully support clearance model is validation as a”
- 8:37 “if you’re building your localization you need to build this by yourself because it depends from localization to localization”
- 10:17 “many countries require this model. This is something what really important for uh starting using e documents as a framework globally.”
Disclaimers in the video
- 1:16 not-in-this-release: framework not by default localized, localizations must be built separately
- 3:23 coming-later: receiver validation not yet supported, planned for future delivery
- 8:37 other: clearance service does not exist in business central and must be built by partners
- 9:16 coming-later: will continue to build localization on top of e documents framework with clearance model for missing countries
- 9:36 coming-later: planning how to migrate Indian and Mexican e-invoicing to new e documents format and verifact 2 in Spain
Presenters (as heard): Alexander, Benji.