Peppol release history

Peppol has three release tracks with separate schedules. This page summarizes releases since 2021, the main changes, and links to the official release notes.

For the post-award track, the date that matters is the mandatory-use date, not the publication date. The gap between the two is the migration window, when both the old and the new validation artifacts are accepted. After the mandatory date only the new ones are, which is why a document that passed one day can be rejected the next without anything in your own system having changed.

The eDelivery specifications work differently. They carry a valid-from date and are mostly your service provider’s responsibility rather than yours. The eDEC code lists have their own version series and are updated several times a year, independently of everything else.

Peppol BIS Billing and the other post-award documents use separate version series within the same release cycle. The current versions are 3.0.21 for Billing and 3.0.17 for ordering, despatch advice, and catalogue documents. See the official release notes for Peppol BIS Billing and for the other BIS documents.

Mandatory from 17 August 2026. Added an optional profile for billing with a response step, with PEPPOL-EN16931-P0100 and P0101 updated to support it. The Danish identifier rules PEPPOL-COMMON-R052 and R053 moved from warning to error, and four new Dutch rules, R054 to R057, arrived as warnings that OpenPeppol has announced will become fatal. The code lists were updated, including the removal of fourteen entries from the EAS list.

Mandatory from 23 February 2026. Introduced PEPPOL-COMMON-R052 and R053 as warnings for Danish company identifiers, both flagged at the time as future errors, and removed PEPPOL-COMMON-R084. On the ordering side, delivery address elements were added to order lines. A hotfix in January 2026 added code 0245 for the Slovak tax identifier to the EAS and ICD lists.

Mandatory from 25 August 2025. PEPPOL-COMMON-R042 was changed so that a Danish CVR number is eight characters without the DK prefix, with a migration period that ran into 2026. PEPPOL-EN16931-R051 was corrected for the currency of BT-117. The ordering documents gained a requested despatch date and product traceability identifiers for medical devices.

German national rules were added, and PEPPOL-EN16931-R002, which requires an invoice note, was excluded when both parties are German. Three Swedish rules, SE-R-003, SE-R-004 and SE-R-013, moved from warning to fatal. If you invoice Swedish buyers and stopped at this release, that is the change most likely to have started rejecting your documents.

SE-R-013 was introduced as a warning that checks the check digit of a Swedish organization number, and PEPPOL-COMMON-R049 was extended with the same check for ICD 0007. Catalogue item identifier requirements were clarified.

PEPPOL-EN16931-R006 was removed as redundant with the syntax rule UBL-SR-04. Order type codes were added to the ordering documents, along with EAS code 0218 for Latvia.

PEPPOL-COMMON-R050, which validates the Australian Business Number, moved from warning to fatal. Several Greek rules were removed and GR-R-011 was added as fatal for the Greek supplier tax identifier.

PEPPOL-COMMON-R049 moved from warning to fatal for Swedish organization numbers under ICD 0007. This release also introduced Peppol BIS Advanced Ordering.

PEPPOL-COMMON-R043 moved from warning to fatal for the Belgian enterprise number under ICD 0208, and PEPPOL-COMMON-R049 was introduced as a warning for Swedish organization numbers.

PEPPOL-COMMON-R043 was introduced as a warning for the Belgian enterprise number, and Italian identifier rules for ICD 0201, 0210 and 0211 were added as warnings. The pattern in this and the following releases is consistent: a national identifier check appears as a warning first and becomes fatal one or two releases later.

eDelivery specifications cover AS4 transport, SMP and SML discovery, the business message envelope, identifier policy, and network policy. They are primarily the responsibility of Peppol Service Providers and determine how messages are routed and which Peppol IDs are valid. The releases below are documented in the eDEC change log.

The Peppol Network Policy 1.0.0 was published as a single set of rules for the network. Message Level Status moved to 1.1.0 with a Service Provider Operational Guideline alongside it, the business envelope to 2.0.2 and the code lists to 9.7. The MLR deprecation and phase-out plan followed on 15 July, setting the end date for the message it replaces.

The first Message Level Status specification, 1.0.0, and the OpenPeppol Service Provider Identification Scheme 1.0.0 were published. This is where the shift from an optional response between end users to a mandatory status between service providers started.

Policy for use of Identifiers 4.4.0, SMP 1.4.0 and SML 1.3.0 were published together, all valid from 1 November 2025. This is the set that governs how a Peppol ID is written and how it is resolved, so it is the one to read if you build addressing logic yourself.

Policy for use of Identifiers 4.3.0, superseded six months later.

AS4 profile 2.0.3, an error correction to the transport profile, and the withdrawal of the legacy business card format schemas.

The reporting specifications were finalized: End User Statistics Reporting 1.1.1, Transaction Statistics Reporting 1.0.2 and the operational guideline that sets out what a service provider reports and when. Reporting became mandatory from 2024.

SMP 1.3.0, published with an impact analysis and a migration path.

The business envelope specification 2.0.0 was published and made mandatory from October 2023. The first reporting specifications were introduced at the same time.

The AS2 transport profile was removed. AS4 has been the only Peppol transport since.

A broad upgrade with three-month migration periods across most of the stack: SMP 1.2.0, SML 1.2.0, Policy for use of Identifiers 4.1.0, transport security policy 1.1.0, AS4 profile 2.0.2, business envelope 1.2.1 and Peppol Directory 1.1.1.

The eDEC code lists are versioned separately and updated several times a year, currently at 9.7. They control which participant identifier schemes, document types, processes and transport profiles exist in the network. A code list update can therefore remove a scheme you rely on without any specification changing, which is what happened to the Finnish LY-tunnus scheme 0037.

PINT is the international invoicing model used where the European billing specification does not apply. Each country builds a specialization on top of it, so a PINT version sets the baseline for the country specifications derived from it. Versions below come from the PINT Billing release notes, and each country specialization has its own notes under the PINT specifications.

If you generate or receive Peppol documents, the post-award track is the one to watch, and the mandatory-use date is the date to plan against. Read the release notes when a release is published in May or November, not when it becomes mandatory three months later. A rule moving from warning to error is the change that breaks a flow that worked, and it is always announced at least one release in advance.

If your service provider handles the connection, the eDelivery track is theirs to keep current. What reaches you from it is occasional: a new identifier scheme you can register, or an old one that is withdrawn.