Compliance Policy 1.0

This Compliance Policy is focused on the contractual responsibilities of the PEPPOL Authorities, the PEPPOL AP and SMP providers with a view to ensure interoperability across the full PEPPOL eDelivery Network and to improve the communication and convergence between all actors. This can only be achieved if the OpenPEPPOL community maintains a common rule set, i.e. principles and compliance criteria, as a baseline for all actors involved.

The aim of the PEPPOL Compliance Policy is to establish a set of guiding principles and rules that can serve to clarify:

The degree of freedom given to PEPPOL Authorities when defining requirements in Annex 5; the operational aspects, such as sending documents without validation, using test certificates in production, mandatory BIS compliance, adherence to SLA terms, etc.; ways of cooperation between PEPPOL Authorities in resolution of problems related to Service Providers with different PEPPOL Authorities as their contractual party.

The Compliance Policy can be found here: Compliance Policy 1.0

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 Directory

The PEPPOL Directory is in use for optional use. All SMP providers are encouraged to push Business Card information of their receivers to the PEPPOL Directory to obtain a higher transparency for all participants in the PEPPOL eDelivery Network.

See official announcement here: https://peppol.eu/peppol-directory-now-live-available-www-peppol-eu/

The PEPPOL Directory is publicly available here: http://directory.peppol.eu

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 OpenPEPPOL@peppol.eu 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

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: https://ec.europa.eu/cefdigital/wiki/display/CEFDIGITAL/eDelivery+Services
Oxalis Source code:
Developer guide: https://github.com/difi/oxalis

Other support documents:

ITC-Transport-BDX Discrepancies-100.pdf
PEPPOL_Certificates_Change_V1.2
ICT-Transport-Trust_Network_Certificate_Policy-2.00.pdf

Post-Award ‘BIS’ Specifications and Guidelines

Peppol BIS Billing 3.0 – Europe

Mandatory from: 15-11-2019 12:00 CEST The Peppol BIS Billing 3.0 is a compliant (CIUS) implementation of the European eInvoicing standard, EN 16931. Consequently, those who receive invoices that comply to this BIS are also compliant to the EU Directive 2014/55 on electronic invoices. It is mandatory that Peppol members who receive invoices through the Peppol network are able to receive invoices based on this BIS. NOTE: Since 2019-04-18 the BIS Billing 3.0 has been the mandatory invoicing specification. The previous BIS2 will be discontinued at the end of this year, 2019-12-31. Study the relevant migration plan from Peppol BIS 4a and 5a to Peppol BIS Billing 3.0 here: PEPPOL Migration Policy BIS Billing

The Peppol BIS Billing 3.0.5 release is now published, together with the migration plan. From 2019-11-15, this is the mandatory release. The documents can be accessed here: http://docs.peppol.eu/poacc/billing/3.0/ Validation artefacts for UBL can be downloaded at the bottom of the link mentioned above. Validation artefacts for CII can be downloaded from a link at the bottom of this page. Further details about the use of CIUS in Peppol can be found at: https://peppol.eu/core-invoice-usage-specification-cius-use-peppol/

Peppol BIS Billing 3.0 – non-Europe

When the Peppol network is used for receiving invoices by members in non-European countries where European Directives are not part of the national legislation and there is a Peppol Authority, then those members are mandated to be able to receive invoices based on the relevant country specific BIS Billing 3.0 specification instead of the Peppol BIS Billing 3.0. Those country specific BIS specification are, in accordance to part 5 of the EN 16931, conformant (extensions) to the EN 16931.

Singapore – SG Peppol BIS Billing 3.0

Singapore has adopted a BIS which follows the PEPPOL BIS Billing 3.0 except that it replaces VAT related rules with Singapore GST (Goods and Service Tax) rules. The name of the specification is ”SG Peppol BIS Billing 3.0”. The Peppol BIS Billing 3.0 specifications apply with the exceptions listed in the SG PEPPOL BIS Billing 3.0 Validations artefacts for SG Peppol BIS Billing 3.0 can be downloaded from here

Other Peppol BIS version 3.0

Mandatory from: 15-11-2019 12:00 CEST Study the relevant migration plan from Peppol BIS 2.0 documents to Peppol BIS 3.0 here: PEPPOL Migration Policy other BIS The following Peppol BIS 3.0.3 documents are published, together with the migration plan.

• Peppol BIS Order only 3.1
• Peppol BIS Ordering 3.1
• Peppol BIS Catalogue only 3.0
• Peppol BIS Despatch Advice 3.0
• Peppol BIS Punch Out 3.0
• Peppol BIS Order Agreement 3.0
• Peppol BIS Message Level Response 3.0
• Peppol BIS Invoice Response 3.0
• Peppol BIS Catalogue Without Response 3.0

The documents can be accessed here: http://docs.peppol.eu/poacc/upgrade-3/ Validation artefacts can be downloaded at the bottom of the link mentioned above

Planned Releases

Spring release May 2020. Please submit RFC’s to: https://openpeppol.atlassian.net/projects/PEPPOL/queues/custom/1

Earlier releases of BIS Validation Artefacts

Can be found at: OpenPEPPOL Validation Artefacts

Cross Industry Invoice (CII) Validation Artefacts

Can be found here: CII Validation Artefacts

Access Point Implementation guide

Please refer to the following document to obtain the nescessary information for becoming an Access Point Service Provider in OpenPEPPOL: PEPPOL AP Implementation guide

OpenPEPPOL PKI version 3 AP and SMP certificates

For details, further information and downloadable Root CAs, please see: Introduction to the revised PKI Certificate infrastructure and issuing process and the PKI Certificate Migration 2018 pages. Please note that the PKI certificates for AP and SMP providers must be requested from PEPPOL’s Jira Service Desk here: OpenPEPPOL Service Desk

OpenPEPPOL Acceptance Test for AS2 and AS4 Onboarding

All new Access Points must successfully complete the Acceptance Test through the OpenPEPPOL centralized test facility, before obtaining a production certificate. Please follow the link for more information including the detailed test instructions: Acceptance Test user guide

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

Access Point implementations (AS4)

Open Source implementations 

• Oxalis, https://github.com/difi/oxalis
• PH-AP: https://github.com/phax/phase4
• Holodeck: http://holodeck-b2b.org/download/
• Domibus (EC sample implementation): https://ec.europa.eu/cefdigital/wiki/display/CEFDIGITAL/Domibus
• AS4.net: https://ec.europa.eu/cefdigital/code/projects/EDELIVERY/repos/eessi-as4.net/browse

Closed Source or hosted AS4 implementations

• B2BRouter: https://www.b2brouter.net/edelivery/
• Edicom ASx Server: https://www.edicomgroup.com/en_ES/solutions/EDICOMNet/what_is.html
• Babelway: https://www.babelway.com/free-trial/
• IBM: https://www.ibm.com/us-en/marketplace/peppol-services
• Seeburger: https://www.seeburger.com/de/

More CEF conformant AS4  implementations See all CEF tested AS4 implementations here

Service Metadata Publisher (SMP):

CIPA SMP, https://joinup.ec.europa.eu/software/cipaedelivery/home Please note: CIPA SMP (3.x) supports OASIS BDXR but does NOT support OpenPEPPOL DIFI SMP, https://vefa.difi.no/peppol/tools/elma-production/ phoss-SMP, https://github.com/phax/peppol-smp-server

Access Point implementations (AS2)

Open Source

• CIPA AP, https://joinup.ec.europa.eu/software/cipaedelivery/home
• Oxalis, https://github.com/difi/oxalis
• PH-AP, https://github.com/phax/as2-peppol-server, https://github.com/phax/as2-peppol-client

Closed Source

• Unimaze eefacta Server,  http://www.unimaze.com/solutions/enterprise-solutions/eefacta-server

Hosted solutions Galaxy Gateway AP, www.galaxygw.com

In this page you will find the PEPPOL BIS Specifications for the Pre-Award community:

Below you can find a full list of the current PEPPOL Business Interoperability Specifications (BIS) for the Pre-Award area.

The listed PEPPOL BIS are formally approved by the OpenPEPPOL Managing Committee and the pre-award community.

PEPPOL BIS eDocuments guide for pre-award

Describes the cryptographic specifications needed to execute the pre-award processes http://peppol.eu/wp-content/uploads/2018/07/BIS-eDocuments-guide-for-pre-award.docx

PEPPOL BIS eDelivery guide for pre-award

This document describes the common building blocks to able execution of pre-award processes. http://peppol.eu/wp-content/uploads/2018/10/BIS-eDelivery-guide-for-pre-award-v1-1_FINAL.docx

PEPPOL BIS Pre-award metadata profiles

• P001 – Procurement procedure subscription
• P002 – Procurement document access
• P003 – Tender Submission

PEPPOL BIS Pre-Award catalogue

PEPPOL BIS Pre-award catalogue is part Tender Submission process http://docs.peppol.eu/pracc/catalogue/1.0/

PEPPOL BIS ESPD 1.0

• PEPPOL BIS ESPD 1.0 Request is part of Procurement document access process
• PEPPOL BIS ESPD 1.0 Response is part of Tender Submission process

ESPD Joint Position Paper OpenPEPPOL & EUPLAT

As a first initiative following the cooperation between OpenPEPPOL and EUPLAT, a joint position paper on ESPD has been produced to affirm the value of establishing interoperable solutions for ESPD implementations in Europe.

Both parties share a common concern for the individual national implementations of the European standards for e-Tendering, hence the position paper, which aims to showcase and emphasize the mature capability of ESPD to represent a best practice for the implementation of standardized procurement messages in the Pre-Award domain.

Please see the position paper at: OpenPEPPOL and EUPLAT Position paper