What's new in E-Documents: Overview (2026 release wave 2)

Overview

The video explains that Business Central already had e-documents but no EDI. EDI here means exchanging orders and related documents between a buyer and a seller company electronically, instead of by email. It is built on the existing e-documents framework and uses the PEPPOL format, which the speaker calls a known technology.

The demo follows one flow. A buyer creates and releases a purchase order, and an XML file goes to the seller. The seller gets a sales order created automatically and accepts or rejects it, which sends an order response back. When the buyer posts the purchase invoice and payment, a remittance advice goes to the seller. The video then covers three new French e-reporting formats and how regulatory lifecycle events are tracked. The speaker says the functionality will be improved later.

Key points

• The EDI document types covered are purchase order, sales order, order response and remittance advice, all handled through the e-documents framework.
• A purchase order sent by the buyer creates a sales order automatically on the seller side. The seller can accept or reject it and send an order response back.
• Posting a purchase invoice lets the buyer send a remittance advice file to the seller, which supports payment reporting.
• Setup needs electronic identifiers on both buyer and seller sides, such as a registration number, so vendors and customers match. Item references are recommended for matching items.
• Document direction can be set to inbound only, outbound only, or both. The video does not demo this, the identifiers or the item references.
• A log shows which files each EDI exchange created and how it progressed. Fact box links connect the purchase order, its e-document and the sales order created from it.
• Three new e-document formats for France are added. French regulatory lifecycle events are stored as messages linked to the original invoice e-document, with statuses collected, submitted, accepted, refused and technical rejected.

Features

A status with a roadmap link comes from the Microsoft 365 roadmap feature this part of the video covers (matched by Haiku; links Opus dropped are not used); other statuses need a status word in the video itself.

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.

• other “purchase order” at 0:59
• other “sales order” at 1:31
• other “payment journal” at 1:44
• other “e-documents” at 2:23

Quotes

• 0:19 “we have e documents functionality in our system but we didn’t have EDI before. What is EDI itself? It is exchange of the order”
• 1:31 “On the seller side, sales order will be created automatically. Then seller can accept or reject the order and send a response back.”
• 2:10 “We have purchase order document, sales order, order confirmation, payment journal. E document type is a purchase order, sales order, order response and remittance”
• 2:23 “we using our people uh format and uh the solution is based on the e documents themselves. So it’s a known technology behind the”
• 3:21 “you will need to use electronic identifiers on both sides. Uh it is JN or VT registration number. Uh for items uh it’s better”
• 8:55 “So uh I’m going to show you we have it introduces uh three new formats for France.”
• 9:48 “All of these things allows um document exchange, payment reporting, but also regulatory status um tracking through e documents.”

Disclaimers in the video

• 10:02 coming-later: we are going to improve the mentioned functionality

Presenters (as heard): Ken, Milita.