OpenPeppol provides a service desk whereby visitors can raise an online request for support using one of the following ticket types:
- PKI Certificates;
- Change requests;
- General support;
- Bug reporting;
- Compliance issue reporting.
A more detailed guidance document covering each of the ticket types can be downloaded by following the ‘Guidance Documents’ link in the box below under ‘Support’. Please read this document before raising a ticket.
OpenPeppol provides a centralised testbed for acceptance of new Access Point Service Providers to the Peppol eDelivery network.
The testbed supports AS2 and AS4 testing and is based on a self-initiated test routine using automated testing procedures. Completion of acceptance testing is validated by the OpenPeppol Operating Office, with a positive result resulting in the issuance of a Peppol PKI production certificate, enabling the service provider to join the network.
A Testbed User guide can be downloaded by following the ‘Centralised Testbed’ link in the box below under ‘Support’. The testbed will be extended to cover SMP Service Providers in the future.
Access to the testbed is provided to new Access Point Service Providers once they become members of OpenPeppol. If you have mislaid your testbed access credentials, please go to the Service Desk and raise a ‘General Support’ ticket.
The Peppol Directory makes it easy for Peppol End Users to find each other in the network and identify each other’s capabilities.
The Peppol Directory is a free-to-browse, open source service. You can search the Directory using one, or a combination, of the following mandatory terms:
- company name
- Peppol endpoint ID
- country
- Peppol document capability
and, where available, by using one of the following optional terms:
- additional identifiers
- contact details
- registration date
- website
- additional free text
If your company is already able to receive Peppol documents, but is not yet listed in the Directory, please contact your Peppol Service Provider and request that they upload your information to the Directory.
You can access the Peppol Directory by following the link in the box below under ‘Support’.
The Compliance Policy is focused on the contractual responsibilities of Peppol Authorities, Access Point providers and SMP providers.
The Compliance Policy ensures interoperability across the Peppol eDelivery network and is achieved through a common rule set that must be adopted by all actors in the OpenPeppol community.
The aim of the Policy is to establish a set of guiding principles that clarify:
- the degree of freedom given to Peppol Authorities when defining local requirements in Annex 5 of their eDelivery Agreement;
- operational aspects, such as: sending documents without validation; using test certificates in production; mandatory BIS compliance, etc.
- methods of cooperation between Peppol Authorities to resolve problems related to Service Providers.
You can access the Peppol Compliance Policy by following the link in the box below under ‘Support’.
OpenPeppol provides members with the following types of technical documentation:
- Guides;
- Specifications;
- Tools;
- Policies
Technical documentation is provided in the following domains:
- eDelivery;
- Post-Award;
- Pre-Award.
Current technical documentation is available by clicking on the relevant item in the summary tables .
In the table below, you will find technical documentation that defines the implementation of the Peppol eDelivery Network.
Compliance with the specifications is mandatory.
These documents provide the necessary resources to enable access to the Peppol eDelivery Network and to implement the following components:
• Access Points, which are gateways that provide a standardised and secure mechanism to exchange different document types within and across geographical domains; • Service Metadata Publishers (SMPs), who provide the exact location and capabilities of Peppol participants; • The Service Metadata Locator (SML), which maintains participants IDs and provides a DNS-based mechanism to discover the SMP where the data for a specific participant can be found.
Please submit any requests for changes to the Service Desk.
| eDelivery | Technical documents |
| Guides | Access Point Implementation Guide |
| Access Point Acceptance Test v1.0 | |
| Introduction to PKI Certification | |
| Peppol eDelivery Agreement | |
| Specifications | SML Service v1.01 |
| SMP Service v1.0 | |
| Peppol Directory v1.1 | |
| Peppol AS2 Profile v1.01 | |
| Peppol AS2 Profile v2.0 | |
| Peppol AS4 Profile v2.0.0 | |
| Peppol AS4 Profile v2.0.1 | |
| Peppol Business Message Envelope v1.2 | |
| Peppol BusDox Definitions v1.01 | |
| Tools | Peppol eDelivery Codelist |
| Peppol eDelivery Codelist Change log | |
| Peppol Certificates Change log v1.2 | |
| Links to Software – Access Points AS2 | |
| Links to Software – Access Points AS4 | |
| Links to Software – Service Metadata Providers | |
| Policies | Transport Security v1.0 |
| Use of Identifiers for BIS2 v3.2 | |
| Use of Identifiers for BIS3 v4.0 | |
| ICT Transport Trust Certificates v2.0 |
In the table below, you will find technical documentation that supports the exchange of numerous business documents used in everyday trading between buying and selling organisations.
Peppol BIS 3.0 is the mandatory specification set, effective from 15th November 2019, replacing the previous Peppol BIS 2.0 which was discontinued on 31st December 2019. Release updates are provided in Spring and Fall of each year.
For eInvoicing in Europe, Peppol BIS Billing 3.0 is a compliant CIUS (Core Invoice Usage Specifications) implementation of the European eInvoicing standard, EN16931. Organisations receiving eInvoices that are compliant to Peppol BIS Billing 3.0 are compliant with EU eInvoicing Directive 2015/55.
For non-European countries with differing eInvoicing legislation and a Peppol Authority, Service Providers using the Peppol network are mandated to receive eInvoices that comply with the country-specific BIS Billing 3.0 specification, which are conformant extensions to EN16931. Country-specific specifications have been released for:
- Singapore
- Australia and New Zealand (A-NZ)
The country-specific specifications for both Singapore and A-NZ follow Peppol BIS Billing 3.0, except for the replacement of VAT rules with Goods and Service Tax (GST) rules. Peppol BIS Billing 3.0 specifications apply with the exceptions listed in the country-specific technical documents. –
| Post-Award | Technical documents |
| Guides | Use of Core Invoice Usage Specification in Peppol |
| Specifications | Peppol BIS 3.0, including: |
| – Peppol BIS Order Only v3.1 | |
| – Peppol BIS Ordering v3.1 | |
| – Peppol BIS Catalogue Only v3.0 | |
| – Peppol BIS Catalogue Without Response v3.0 | |
| – Peppol BIS Despatch Advice v3.0 | |
| – Peppol BIS Punch Out v3.0 | |
| – Peppol BIS Order Agreement v3.0 | |
| – Peppol BIS Message Level Response v3.0 | |
| – Peppol BIS Invoice Response v3.0 | |
| Peppol BIS Billing Europe v3.0.5 | |
| Peppol BIS Billing Singapore v3.0 | |
| Peppol BIS Billing A-NZ v3.0 | |
| Tools | Peppol BIS 3.0: |
| – Syntax, rules, codelists | |
| – Example files, Schematron files | |
| – Validation artefacts | |
| Cross Industry Invoice validation artefacts | |
| Peppol BIS 2.0 validation artefacts | |
| Billing Singapore validation artefacts | |
| Billing A-NZ validation artefacts | |
| Policies | Migration to Peppol BIS 3.0 |
In the table below, you will find technical documentation that supports the exchange of numerous business documents used in the pre-award processes undertaken between buying and selling organisations.
As part of the cooperation between OpenPeppol and the European Association of Public eTendering Platform Providers (EUPLAT), a joint position paper has been published to affirm the value of establishing interoperable solutions for the implementation of the European Single Procurement Document (ESPD) in Europe.
OpenPeppol and EUPLAT share a common concern for the individual national implementations of the European standards for eTendering. The position paper (follow link in the table below) showcases the mature capability of ESPD to represent best practice for the implementation of standardised procurement messages in the Pre-Award domain.
| Pre-Award | Technical documents |
| Guides | eDocuments Guide for Pre-Award |
| eDelivery Guide for Pre-Award | |
| Specifications | Peppol BIS Pre-Award profiles, including: |
| – P001 Procurement Procedure Subscription | |
| – P002 Procurement Document Process | |
| – P003 Tender Submission | |
| Peppol BIS Pre-Award Catalogue | |
| Peppol BIS ESPD, including: | |
| – Peppol BIS ESPD Request | |
| – Peppol BIS ESPD Response | |
| Tools | Peppol BIS Pre-Award profiles: |
| – Syntax, rules, codelists | |
| – Example files, Schematron files | |
| Peppol BIS Pre-Award Catalogue: | |
| – Syntax, rules, codelists | |
| – Example files, Schematron files | |
| Peppol BIS ESPD: | |
| – Syntax, rules, codelists | |
| Example files, Schematron files | |
| Policies | OpenPeppol/EUPLAT ESPD Position Paper |
