PEPPOL BIS Billing

www.peppol.eu

PEPPOL BIS Billing 3.0 – understanding the PEPPOL Core Invoice Usage Specifications (CIUS) André Hoddevik Secretary General OpenPEPPOL AISBL Head of eProcurement Unit, Public Procurement Department Agency for public management and eGovernment (Difi)

PEPPOL is owned by OpenPEPPOL AISBL The PEPPOL Vision

To enable businesses to communicate electronically with any European public sector entities in the procurement process, increasing efficiencies and reducing costs

Page 2 PEPPOL is owned by OpenPEPPOL AISBL The PEPPOL Interoperability Framework

Based on the European Interoperability Framework (EIF) To adopt this Framework all a business TIA needs to do is

know the identity of its trading partners PEPPOLBIS agree that the Framework standards cover the required business transaction ensure its software or service provider supports the Framework standards and is connected to a certified Access Point PEPPOL eDelivery Network PEPPOL is owned by OpenPEPPOL AISBL Page 3 The PEPPOL Interoperability Framework components

PEPPOL Business Interoperability Specifications (BIS) utilising the Universal Business Language (UBL – ISO/IEC 19845) Facilitates standards based end-to-end electronic procurement processes Including, but not limited to, e-invoicing – PEPPOL BIS Billing 3.0 PEPPOL eDelivery Network – 4-corner model Technical specifications and sample software (open source) PEPPOL Agreement Framework Legal framework for governance and compliance to facilitate multilateral interoperability Governance set-up through OpenPEPPOL AISBL International non-profit association, life cycle management routines

Page 4 PEPPOL is owned by OpenPEPPOL AISBL PEPPOL BIS Billing 3.0 – why?

PEPPOL Invoice pre-study mandate Perform and document a pre-study of the different approaches for how to use the European standard on Electronic Invoicing (EN) within PEPPOL, including recommendations on the way forward Recommendations from the pre-study The adoption of the EN «as-is» is not feasible EN provides for multiple invoicing processes Incomplete or too open code lists Produce a Core Invoice Usage Specification (CIUS), not extension Using an extension will not result in PEPPOL users being compliant to the EN The mandatory BIS to use UBL 2.1 syntax binding, optional use of CII Minimize implementation costs

Page 5 PEPPOL is owned by OpenPEPPOL AISBL PEPPOL BIS Billing 3.0 – targets

Added functions and processes introduced by the EN should be adopted unless there are good and explicit reasons not to adopt them The new PEPPOL Invoice and credit note shall enable existing PEPPOL users to continue their current invoicing in a EN compliant way as much as possible The migration and the use of the PEPPOL CIUS should be as simple as possible It shall still be possible to use the mandatory invoice BIS without bilateral agreements between sender and receiver’s service providers

Page 6 PEPPOL is owned by OpenPEPPOL AISBL PEPPOL BIS Billing 3.0 – value added

National rulesets within the CIUS – allows for handling of national or domain specific provisions and still maintain cross-border interoperability Documentation in HTML, based on AsciiDoc – improved version control and modular approach that makes it easy to reuse Enhanced quality – additional validation rules to ensure instance compliance Day-to-day use – OpenPEPPOL provides validation services and support Maintenance – life cycle management, release management and quality control is provided by the OpenPEPPOL Post-Award Change Management Board in cooperation with the Development- and test team. Transmission – OpenPEPPOL provides the PEPPOL eDelivery Network, ensuring interoperability at the message exchange level

Page 7 PEPPOL is owned by OpenPEPPOL AISBL National rulesets within the CIUS

OpenPEPPOL offers the only(?) Pan-European implementation of the European Norm

Page 8 PEPPOL is owned by OpenPEPPOL AISBL PEPPOL BIS Billing 3.0 – migration plan (I)

Page 9 PEPPOL is owned by OpenPEPPOL AISBL PEPPOL BIS Billing 3.0 – migration plan (II)

Page 10 PEPPOL is owned by OpenPEPPOL AISBL The PEPPOL Interoperability Framework today

173 Certified Access Points in 21 countries in Europe and North America 12 PEPPOL Authorities Agency for Digital Italy (Italy) Agency for Public Management and eGovernment (Norway) Danish Business Authority (Denmark) Department of Health (UK) Department of Public Expenditure and Reform (Ireland) Federal Public Service Policy and Support (Belgium) Financial Management Authority (Sweden) Free Hanseatic City of Bremen – KoSIT (Germany) Info-communications Media Development Authority (Singapore) Ministry of Economic Development (Poland) SimplerInvoicing (Netherlands) OpenPEPPOL AISBL More than 120.000 public and private sector entities can receive PEPPOL BIS invoices 278 OpenPEPPOL members from 31 countries

60 million+ BIS invoices between APs in 2017 PEPPOL is owned by OpenPEPPOL AISBL Page 11 PEPPOL in Germany

In April 2018, the German National IT Planning Council decided to mandate use of the PEPPOL eDelivery Network for transport of e-invoices to public authorities in Germany The Coordination Office for IT Standards (KoSIT), located in the Free Hanseatic City of Bremen, nominated as PEPPOL Authority for Germany The timeline for implementation will be decided by the National IT Planning Council in October In June 2017, the German National IT Planning Council decided to mandated for public authorities to receive and process XRechnung invoices The XRechnung is a Core Invoice User Specification (CIUS) of the European Norm (EN) 16931 on e- invoicing The Xrechnung will be implemented as a national ruleset in PEPPOL BIS Billing 3.0 (EN 16931 CIUS)

Page 12 PEPPOL is owned by OpenPEPPOL AISBL PEPPOL outside Europe

IMDA (Singapore) as the first PEPPOL Authority outside Europe – announced 21 May PEPPOL as national framework and standard for e-invoicing Will serve as a model for setting up other PEPPOL Authorities outside Europe Proves PEPPOL’s relevance and role in enabling the digital economy also outside Europe Strong interest from Singaporean stakeholders – 45 signed on as interested/committed before the public announcement

Page 13 PEPPOL is owned by OpenPEPPOL AISBL Main priorities – the future of the PEPPOL Interoperability Framework

Roll-out of PEPPOL BIS Billing 3.0 throughout Europe supporting implementation of Directive 2014/55/EU Increased use of PEPPOL BIS for catalogue, order/order confirmation and despatch advice Increased use of PEPPOL BIS in Pre-Award processes supporting implementation of Directive 2014/24/EU Revised framework for PEPPOL Transport Infrastructure Agreements Assess and include new domains for use of the PEPPOL eDelivery network On-board more PEPPOL Authorities – also outside Europe Utilisation of Distributed Ledger Technology/Blockchain Page 14 PEPPOL is owned by OpenPEPPOL AISBL The PEPPOL eDelivery Network

Business Agreement Sender Receiver Free to choose ANY Address Registry Access Point in ANY country SML Prepare Process 1 4 SMP Sign ONE Agreement; Capability Connect to ALL look-up

2 Exchange of PEPPOL BIS Open FOUR-corner Documents between Access Points 3 model

NO ROAMING fees Sender Access Point Receiver Access Point between PEPPOL must send valid receives PEPPOL BIS Access Points PEPPOL BIS documents documents

Page 15 PEPPOL is owned by OpenPEPPOL AISBL The PEPPOL eDelivery Network

Business Agreement Sender Receiver Free to choose ANY Address Registry Access Point in ANY country SML Prepare Process 1 4 SMP Sign ONE Agreement; Capability Connect to ALL look-up

2 Exchange of PEPPOL BIS Open FOUR-corner Documents between Access Points 3 model

Message exchange protocol NO ROAMING fees between PEPPOL Current: AS2 mandatory, AS4 optional Access Points Future: AS4 mandatory, AS2 optional Target date: 1 July 2019 if EC and OpenPEPPOL agreed conditions are met by December 2018 Page 16 PEPPOL is owned by OpenPEPPOL AISBL More information E-mail: [email protected] Web address: www.peppol.eu CEF eInvoicing Event eDelivery AS4 network interoperability at message exchange level

29 May 2018

Joao Rodrigues Frade Head of sector CEF Building Blocks, DIGIT PEPPOL migration from AS2 to AS4 CEF eInvoicing User Community

2016 2017 2018 2019

The EC and OpenPEPPOL Task Forces validated that AS4 The EC and OpenPEPPOL As from 1 July 2019, AS4 is signed a Letter of is fit for use in the PEPPOL continue their cooperation. the mandatory message Understanding, outlining the network from both functional exchange protocol in the PEPPOL network. transition from AS2 to AS4 and non-functional (security, • Oxalis has implemented message exchange protocols. load, etc.) perspectives. AS4 support and is currently undergoing The PEPPOL AS4 profile was testing. available and AS4 became an • Oxalis and Domibus will be optional message exchange tested for interoperability. protocol in the PEPPOL • A new onboarding test network. platform for PEPPOL is being created. • INEA grants are available for parties deploying an AS4 solution or upgrading their own solution. • The early adopters in the eInvoicing market already have conformant AS4 solutions. PEPPOL is owned by OpenPEPPOL AISBL Find out more on CEF Digital ec.europa.eu/cefdigital #BIG REUSE