In this section, you will find links to the PEPPOL eDelivery Network and BIS (document) specifications, guidelines, and sample implementations.

The PEPPOL eDelivery Network Specifications

The PEPPOL eDelivery Network Specifications

This section includes specifications and resources to enable access to the PEPPOL eDelivery Network and to implement the following components: Access Points, gateways which ensure a standard and solid transport mechanism to exchange different types of documents across different communities or countries; Service Metadata Publishers (SMPs), which contain the exact location and the capabilities of participants; Service Metadata Locator (SML), used to add/update/delete the IDs of the participants, and which offers a DNS-based mechanism to discover the SMP where the specific participant data is described.


In the table below you will find the set of specifications that define the implementation of the PEPPOL eDElivery Network. Support for these specifications is mandatory.


PEPPOL eDelivery Network specifications:
Document Specifications
Busdox ICT-Transport-BusDox_Definitions-101.pdf
The SML ICT-Transport-SML_Service_Specification-101.pdf
The SMP ICT-Transport-SMP_Service_Specification-101.pdf
The AS2 protocol ICT-Transport-AS2_Service_Specification-2014-01-15.pdf
Policy for using identifiers PEPPOL_Policy for use of identifiers-300.pdf
Envelope specifications ICT-Transport-OpenPEPPOL-Envelope_Specification-100_2014-01-15.pdf


Introduction to AS4 as a new transport protocol

In a Letter of Understanding (LoU) signed between the European Commission and OpenPEPPOL, the parties agree a plan for the transition from AS2 to AS4 as the message exchange protocol in the PEPPOL profile of CEF eDelivery. The transition is planned to follow three main phases, where AS4 will become mandatory in the PEPPOL profile of CEF eDelivery from Q2 2019, provided that each phase is successfully completed. The parties have agreed on a list of conditions that need to be proven and tested to ensure a safe migration and will take steps to stimulate a market take-up of this migration plan.

The agreed transition includes the introduction of the AS4 protocol in the PEPPOL eDelivery Network for optional use from 2017. In the Pre-Award domain, use of the AS4 message exchange protocol is mandatory due to an agreement made with e-SENS. Currently the OpenPEPPOL AS4 Transition Workgroup is preparing a PEPPOL profile of the CEF/e-SENS AS4 implementation to clearly specify how AS4 is to be used in the PEPPOL eDelivery Network. This new profile will be well aligned with the CEF/e-SENS AS4 profile and based on the experience gained during the e-SENS eTendering pilot.


PEPPOL Transport Infrastructure Agreements (TIA):

Transport Infrastructure Agreements (for sample purposes only). You can obtain the appropriate set of agreements from your chosen PEPPOL Authority.

Please see the list of PEPPOL Authorities in the ‘Who is who’ section of our website for further information at a national level and their representatives to contact for obtaining and signing the PEPPOL Transport Infrastructure Agreements (TIA).

You can sign the TIA with any PEPPOL Authority but we recommend you choose an Authority in the country where your business is registered. Alternatively, if there is no PEPPOL Authority in your country, you could sign the TIA with OpenPEPPOL as the Authority and re-contract at a later date when an Authority is established nationally. In this case, please contact to obtain the appropriate agreements.


PEPPOL Transport Infrastructure – implementation support:


CEF e-Delivery
The Directorate-General for Informatics of the European Commission maintains a sample implementation of OpenPEPPOL’s eDelivery Network. This implementation aims at providing a generic solution for public administrations to exchange documents in a secure, reliable and trusted way. The CEF e-Delivery solution provides the following components: Access Points, Service Metadata Publishers (SMPs) and Service Metadata Locator (SML).


Oxalis is a PEPPOL sample implementation for Access Points, which is used extensively in the PEPPOL community.


Software libraries:
Source code libraries Doc. type Source code library / Developer guide
CEF e-Delivery Source code:
Developer guide:
Oxalis Source code:
Developer guide:


Other support documents:

Post-Award ‘BIS’ Specifications and Guidelines

Post-Award ‘BIS’ Specifications and Guidelines

In this page you will find the PEPPOL BIS Specifications in the following sections:


Latest Release

Current Specifications

Validation artefacts

Planned Releases

Previous Versions


Latest release

Name: Spring Release 2017

Published: 13-05-2017

Mandatory from: 15-05-2017 12:00

Status: Mandatory use

Release notes: Release notes for openPEPPOL-VA-V3.4.0.pdf

Full release package as zip: Spring Release 2017 package

NOTE: PEPPOL BIS 4A and 5A version 1.0 have been deprecated

Please implement support as soon as possible.


PEPPOL Migration Policy 


Current PEPPOL Business Interoperability Specifications (BIS)

Below you can find a list of the current PEPPOL Business Interoperability Specifications (BIS) updated with the latest release. The use of the listed PEPPOL BIS is mandatory, and formally approved by the OpenPEPPOL Managing Committee. and

PEPPOL BIS Common text and introduction

PEPPOL BIS 1A Catalogue Only

PEPPOL BIS 3A Order Only



PEPPOL BIS 18A Punch Out

PEPPOL Punch Out Login & Transmission Specification

PEPPOL BIS 28A Ordering

PEPPOL BIS 30A Despatch Advice

PEPPOL BIS 36A Message Level Response

PEPPOL BIS 42A Order Agreement


OpenPEPPOL Validation Artefacts

The current version of the  Validation artefacts  for all transactions in a single zip file updated with latest release.

Validation artefacts are the tools that help parties and service providers to comply with the PEPPOL Transport Infrastructure Agreements (TIA) as they help to ensure the contents of the exchanged document instances in the PEPPOL network are valid both from a syntactical and a semantic point of view. These business rules check for the correctness of the coded values, co-occurrence constraints or calculations. It is therefore necessary to use them before submitting documents to the network, in order to ensure the overall quality of exchanged electronic documents, and thus the overall performance of the nework.


Planned Releases

Message Level Response BIS 36A – 200 (for review)

Invoice BIS 3.0, aligned to EN 16931

Invoice Message Response BIS


Earlier releases of Validation Artefacts

Can be found at: OpenPEPPOL Validation Artefacts


Testing and Validation support:

Guideline on validation of XML: ICT-PostAward-BIS_Validation_Artifacts-200.pdf

PEPPOL testing for Post-Award implementations: ICT-PostAward-Conformance_Guideline-301.pdf

Access Point (AP) Implementation Guidelines

Access Point (AP) Implementation Guidelines

How to set up a PEPPOL Access Point

How to enroll for OpenPEPPOL PKI certificates

Presentations from face-to-face meetings

Presentations from face-to-face meetings

Status Update Pre-Award

CC meetings in Vienna, May 2017

Pre-Award for newcomers and upcoming members

CC meetings in Vienna, May 2017

PEPPOL Directory

CC meetings in Vienna, May 2017

Input for EN - Group 3

CC meetings in Vienna, May 2017


CC meetings in Vienna, May 2017

TIA Change Management Process

CC meetings in Vienna, May 2017

OpenPEPPOL AS4 migration Update

CC meetings in Vienna, May 2017

Pre-study EN - workshop

CC meetings in Vienna, May 2017

IMR - workshop

CC meetings in Vienna, May 2017

Links to Software for PEPPOL Implementations

Links to Software for PEPPOL Implementations

The following are amongst the available implementations supporting the provision of PEPPOL eDelivery Services for the PEPPOL network.


Service Metadata Publisher:



Galaxy Gateway SMP,



Access Points (AS2)



Galaxy Gateway AP,



Additional tools:




For additional information about AS2 implementations applicable for the PEPPOL eDelivery network when integration with SML/SMP and the PEPPOL PKI Trustmodel is taken into account, we refer to the Drummond Group AS2 website:


Current Drummond Group AS2 certified implementations:

Company Name Product Name Optional Profiles Tested
Axway Axway B2Bi 2.1 / Axway Interchange 5.12 / Axway Activator 5.12 MA, FN, FN-MA, CEM, Chunked Transfer Encoding (CTE), Reliability, Restart, SHA-2
Axway Axway Gateway 6.15 FN
Axway Axway SecureTransport 5.3
Axway TradeSync Integration Manager (TSIM) Version 3.9 MA, FN, FN-MA,FN-MDN
Cleo Cleo Harmony™ v5.2 / Cleo VLTrader® v5.2 / Cleo LexiCom® v5.2 MA, FN, FN-MA, CEM, FN-MDN, Chunked Transfer Encoding (CTE), Reliability, Restart, SHA-2
Dell Boomi AtomSphere April 2015
E2open E2 Cloud Connectivity v6.1 MA, FN, FN‐MA, FN‐MDN, Chunked Transfer Encoding (CTE), Reliability, Restart, SHA‐ 2
EXTOL International, Inc. EXTOL Secure Exchange (ESX) v5.5.3 FN, FN-MDN
Hewlett-Packard Company ELIT AS2 Connector v4.19 with AS2API v1.7 Engine FN, Chunked Transfer Encoding (CTE), SHA-2
IBM IBM DataPower Gateway V7.1 MA, FN, FN-MA, Chunked Transfer Encoding (CTE), SHA-2
IBM IBM® Sterling Information Broker® 5.4
MuleSoft, Inc. MuleSoft Anypoint B2B – AS2 Connector 2.0
/n software RSSBus Connect v4.0 with the /n software EDI Integrator V9 AS2 Engine MA, FN, FN-MA, FN-MDN, CEM, Chunked Transfer Encoding (CTE), Reliability, Restart, SHA-2
OpenText GXS BizManager 3.3 MA, FN, FN-MA, Chunked Transfer Encoding (CTE), Reliability, Restart, SHA-2

AS2 3Q14 Drummond Certified™ Products