1. www.peppol.eu PEPPOL is an EU co-funded project CIP-ICT PSP-2007 No 224974 OpenPEPPOL TICC status Net-meeting 28-Nov-2014 OpenPEPPOL AISBL, Belgium Sven Rasmussen Danish Agency for Digitisation Ministry of Finance svrra@digst.dk

2. Agenda TICC part  Roll call - joint  TICC status  AS2 Migration  Transfer of SML Service to DG-DIGIT  Document Identifiers  Support for GS1 and Industry sectors  Simplerinvoicing: new PEPPOL Authority  Update of PEPPOL TIA  EC program Connecting Europe Facility (CEF) Page 2

3. Roll call - Expectations Page 3

4. TICC Status Page 4 Membership status and Highlights 90+ Access Point Service Providers 35 Service Metadata Publisher Service Providers SimplerInvoicing (NL) new PEPPOL Authority Growing Interests in UK for NHS implementation Pilot support for e-SENS Piloting Transactional growth >1 000 000 transactions per month > 30 000 receivers in the PEPPOL Network Software solutions supporting PEPPOL AS2 & SBDH CIPA e-Delivery (Open Source AP & SMP) Oxalis (Open Source AP) Commercial implementations

5. AS2 Migration Page 5 All new / updated specifications available at: http://www.peppol.eu/ressource-library/technical-specifications/transport- infrastructure http://www.peppol.eu/ressource-library/technical-specifications/transport- infrastructure 2014 Mar-01START and AS2 / SBDH Both In-use according to Migration Policy 2014 Sep-01AS2 /SBDH Mandatory protocol Now!Migration concluded START services Phase-out / Not supported

6. SML Migration Page 6 Service Metadata Publisher Since PEPPOL Project hosted by BRZ (AU) Planning to be migrated to EC Services by DG DIGIT Migration of Services Tentatively planned for February 2014 New DNS Domains: OperatorSML domain nameSMK domain name BRZ (old)sml.peppolcentral.orgsmk.peppolcentral.org DG DIGIT (new)edelivery.tech.ec.europa.euacc.edelivery.tech.ec.europa.eu Process Agreements, SLA and test – Ongoing Notification and information (Members News Item, mailing lists, website and PA’s) Software Update (Ex. CIPA ver. 2.2.3) Configuration and deployment

7. Document Identifiers Page 7 PEPPOL Policy for Identifiers split into Policy part and Code lists part: Party ID Document Type ID Process ID Transport Profile ID Guidelines for approval of new Document Type Identifiers: 1) Format should be based on international / industry standard 2) Format maintained as an Open Process 3) Free and open access to specifications 4) Format should be possible to use without bilateral agreements 5) Format must be structured 6) Access to validation tools 7) Assess the relation with PEPPOL BIS profiles

8. OpenPEPPOL and GS1/Industry sectors Use of PEPPOL Network for GS1 messages: EDIfact/EANCOM GS1 XML Master Data synchronisation Support for multiple Industry sectors E-Health (ex. UBL with GS1 Identifiers) Construction (ex. BeAST) Wholesale & retail sector (ex. GS1 eCOM Master data profiles) Use of PEPPOL BIS (UBL) with GS1 Identifiers: Party, Locations, Goods and Items Page 8

9. Introduction of SimplerInvoicing Jaap Jan Nienhuis E-mail: jaapjan@innopay.com Page 9 SimplerInvoicing new PA

10. Revision of PEPPOL TIA Agreed in Bruxelles GA 2014 Objective to resolve issues identified such as: Legal concerns related to liability Specification of penalties Revision and operationalization of “Mandatory BIS requirement” Distinction between e-Delivery (Network) and Payload (Domain) governance Formalization of validation requirement Improved Service Level Requirements Update of Annexes Project established and progressing work Ties into Validation & QA-project Revised TIA for review Q1 2015 Page 10 Update of PEPPOL TIA

11. CEF is an EC Financial instrument anchored with the Europe 2020 strategy supporting the Digital Agenda 970 M € for Digital Service Infrastructures (DSI’s) Improve competitive economic development - especially for SME’s Support the “Single Digital Market” DSI’s particularly relevant for OpenPEPPOL eDelivery DSI eInvoicing DSI Implementations via annual Work Programmes 2014 focus on Core Service Platforms (EU wide infrastructure and capacity) 2015 Includes Generic Services (Member State level) References:http://ec.europa.eu/digital-agenda/en/connecting-europe-facility https://joinup.ec.europa.eu/community/cef/home Page 11 Connecting Europe Facility (CEF)

12. www.peppol.eu PEPPOL is an EU co-funded project CIP-ICT PSP-2007 No 224974 OpenPEPPOL PoACC status Net meeting November 28 th 2014 OpenPEPPOL AISBL, Belgium Anders Kingstedt The Swedish Financial Management Authority (ESV) anders.kingstedt@esv.se

13. Agenda Validation and Quality Assurance project Message Level Response (MLR) EN on e-Invoicing Yellow pages Project AOB Page 13

14. Validation – Quality Assurance Page 14

15. Scope – validation / verification and quality assurance AP Content Quality Handling reference information * Ensuring Well formedness (XML) Valid XML Scheme (UBL XSD) Business rules (Schematron / XSLT – PEPPOL BIS) Validation & Notification Notification & receipts -Technical -Message -Business * Message Level Response (MLR) Rules for handling / rejecting / accepting messages * - currently out of scope for OpenPEPPOL / PEPPOL General considerations Relation to TIA Policies and general rules Publication & management Tool support Responsibilities -End to end -AP to AP Ensuring technical / infrastructure stability Storing / logging / audit trail …

16. Prague WS outcome

17. Decision points, recommendations and takeaways from the OpenPEPPOL Prague F2F meeting (TICC / PoACC) The Sender is responsible for validation MLR is suggested to be used for negative response only An escalation ladder for policy breaches should be established The /correct/ use of profile & customization id is important Release cycle; Major version 16 months, Minor version every 6 months, hot fixes when needed. Performance issues in large volumes scenarios must be considered Rounding issues – to be addressed? “test of test” – potential new project? Business level validation (such as checking for reference information) – controversial subject but for now out-of-scope

18. Relationships & Dependencies Validation & Quality Assurance TIA revision Versioning Policy (general) Release Mgmt. Migration Policy MLR PEPPOL policy on the use of identifiers impacts defines clarifies ??? uses

19. Validation & QA Policy - Current status Introduction Mission Statement Scope/applicability Goals and non-goals Terminology Layout of the document Roles and Responsibilities Legal requirements Enforcement Quality Assurance Artefact Lifecycle management Change management Release management Release schedule Release versioning Structure of artefacts Validation process Validation business processes overview Sender side validation process Receiver side validation process Validation process error codes Use of the MLR How to validate a document Identify validation artefact Inform sender of validation result Annex 1: List of Validation Artefacts Annex 2: Concepts and definitions Annex 3: Further tasks

20. Handling acknowledgements (draft) The above flow is illustrative; the actual flow of events might not be executed in the order presented. In scope Out of scope

21. MLR Issues presented in Prague The role and value of the MLR inthe current form is challenged MLR requires mandatory use in order to be useful A focused meeting to address the above issues will be held in Stockholm December 15 th (at ESV)

22. Yellow Pages project Page 22

23. List of participants Page 23

24. Yellow Pages project status First kick off meeting conducted: Ger Clancy (IBM, Ireland) is assuming the PM role Sven and Anders are project owners In excess of 20 participants Functionality : A common register used to locate PEPPOL users, i.e. those who can receive e-documents in the PEPPOL network Global lookup Should be in sync with and based on SMP content Should support retrieval of he following information: - name of company/organization, - global id's, - endpointid, - supported doc type Outstanding issues, Challenges, Risks and mitigation EU level participation not secured Actions and next steps First core and review team meeting scheduled for 8 th of December Page 24

25. EN – e-Invoicing Page 25

26. Overview – CEN PC 434 -Objective: To develop European standard (EN) for the semantic data model of the core elements of an electronic invoice based on the Directive 2014/55/EU on electronic invoicing. OpenPEPPOL role in PC 434: to liaise with PC 434, to secure OpenPEPPOL’s interest and to provide input to the development of a semantic data model based on the PEPPOL BIS and its underlying specifications (the CEN BII and UBL). Formal OpenPEPPOL Representation: Anders Kingstedt, PoACC leader Sven Rasmussen, WS 3 leader Time table: First draft ready by, final publication by December 2016. Page 26

27. Overview – CEN PC 434 Organization: WS 1 – Clarify Core, Semantic Model WS 2 – Evaluate BII & MUG, consider at other standards input WS 3 – Take EU project input into consideration, evaluate specific requirements Page 27

28. Planning ahead -Next TCON in the PoACC – TBA -General Assembly; March - Brussels -F2F 2015 - TBA - Venues TBD (suggestions: Amsterdam? Vienna? London? Warzaw?) - Dates: May, October Page 28

29. Last but not least… A BIG thank you For your efforts in making PEPPOL a success this past year. Page 29

30. www.peppol.eu PEPPOL is owned by OpenPEPPOL AISBL Join the OpenPEPPOL community! For more information: E-mailinfo@peppol.euinfo@peppol.eu Web addresswww.peppol.euwww.peppol.eu