Peppol Code Lists 9.4 – What’s New and Why It Matters for E-Invoicing and Logistics

The Peppol network keeps evolving — and the latest update, Code Lists Version 9.4, marks another important step toward cleaner, more consistent digital document exchange.
While the update may seem minor, it introduces several improvements that will shape how businesses manage logistics, invoices, and EDI communication in the coming year.

A quick reminder — what are Peppol Code Lists?

Peppol Code Lists are the “rules” that keep all participants in the Peppol network speaking the same digital language.
They define how documents are named, how participants are identified, and which formats and processes can be used to send and receive e-invoices or logistics documents.

In short: they make sure that when one system sends an invoice, the other can read it without errors — whether you’re in Poland, Germany, or Singapore.

What’s new in version 9.4

The new release focuses mostly on logistics and process updates, improving clarity and consistency.

Here’s what changed:

• The “Logistics” category in Peppol has been standardized — document names now follow a consistent format (“Peppol … Vx.y”), making version tracking easier.

• New document types have been added for logistics, such as the updated Transport Execution Plan V1.2 and Application Response V1.

• Older versions of these documents — and some legacy Danish OIOUBL documents — have been marked for removal in early 2026.

• A new “Message Level Status” category has been introduced, helping businesses better monitor the status of their messages and data exchanges.

It’s not a huge overhaul — but it makes the Peppol ecosystem cleaner, simpler, and better aligned with how companies actually manage transport and invoicing processes today.

What this means for businesses

For companies using Peppol for e-invoicing or logistics, this update is all about future-proofing.
Here’s why it matters:

1. Smoother communication between systems
   The clearer naming and versioning of logistics documents reduces integration errors and improves traceability.

2. Better control and visibility
   The new message status feature (MLS) helps businesses see exactly where their electronic documents are in the delivery process — fewer black holes, fewer surprises.

3. A gentle reminder to modernize
   If your systems still rely on older OIOUBL formats or first-generation logistics documents, now’s the time to plan an update.
   From January 2026, older types will no longer be supported in Peppol.

Looking ahead

This update may feel technical, but it reflects a broader trend: e-invoicing and logistics are merging into one connected digital ecosystem.
Peppol’s goal is simple — to make cross-border trade as seamless as sending an email.

With more countries (from Slovakia to the UAE) introducing mandatory e-invoicing and Peppol-based frameworks, staying aligned with the latest standards is not just good IT practice — it’s smart business strategy.

Sources:

• Peppol.org – Code Lists v9.4 Publication

• Docs.peppol.eu – eDEC Code Lists