What's New: E-Documents (2026 release wave 1)

Overview

The video covers what is new for E-Documents in 2026 release wave 1. The PEPPOL format was redesigned and moved into a first-party app, which gives more control and scalability and makes customization and localization easier. The old electronic document formats in the base app are to be obsoleted and removed so the code lives only in the first-party app.

It also shows linking an inbound e-document to a purchase invoice that already exists, a case that arises in intercompany scenarios. Further sections cover localization updates (Spain, Denmark, France), the PEPPOL app’s interfaces and enum for developers, the PEPPOL 3.0 setup page, and the migration path.

Key points

• PEPPOL is now a first-party app instead of part of the base app. The plan is to obsolete the PEPPOL code in the base app and remove it, and the electronic document formats are being phased out in favor of e-documents.
• Inbound e-documents can be linked to an existing purchase invoice. This is currently allowed only for intercompany vendors. Only invoices for that vendor whose amount matches the total of the received invoice can be linked.
• The PEPPOL app exposes 10 interfaces, split by part of the PEPPOL 3.0 format, so developers can extend one part without changing the whole format. A PEPPOL validation interface allows custom validation before the format is created.
• A new PEPPOL 3.0 setup page lets users select enum values and configure the PEPPOL implementation.
• Vendor templates can set a default e-document type (purchase invoice or purchase order). Service participant can now be linked to company information.
• The e-documents verify tool for Spain is in public preview because its use is not yet enforced.
• Denmark OIOUBL e-invoicing now works with carbon footprint data, which is filled into purchase invoices automatically. French electronic invoicing is work in progress, and payment with e-documents is enabled in the framework.

Features

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 37202 “PEPPOL 3.0 Setup” at 7:17
• page “inbound e-document” at 9:08
• enum 37200 “PEPPOL 3.0 Format” at 5:02
• interface “PEPPOL validation interface” at 6:18

Not found in BC28-30: page “inbound e-document”, interface “PEPPOL validation interface”.

Quotes

• 0:34 “PEPPOL is now first party app. This is much easier for more control, more scalability, easier for localizations”
• 0:47 “One new functionality really important link inbound e-documents to purchase invoice and this is extremely important”
• 1:01 “in a background system will create intercompany purchase invoice in the company B. So now we have created invoice in company B but we”
• 3:01 “We enabled verify tool in Spain. Now this is a public preview but this is completed. This is a public preview only because this”
• 5:02 “PEPPOL app app exposes 10 interfaces which is quite some but they’re divided into the different parts of the format”
• 8:03 “we’re going to the plan is to obsolete the code and remove it from base app so it only lives in the first party”
• 9:19 “the specific thing about this feature is that it it’s currently only allowed for intercompany vendors”
• 10:18 “the amount corresponds to the total on the invoice. So, let me actually just show you that”

Disclaimers in the video

• 3:01 preview: this is a public preview but this is completed. This is a public preview only because this is not enforced to be used yet
• 3:39 coming-later: work in progress French electronic invoicing. This is something what we are working on
• 8:03 subject-to-change: we’re going to the plan is to obsolete the code and remove it from base app so it only lives in the first party app and at some point later on

Presenters (as heard): Alexander Totovic, Magnus.