A cooperative e-invoicing infrastructure. Scoping workshop

A cooperative e-invoicing infrastructure Scoping workshop - August 28th 2012

Welcome Jan Julianus

Goal for today Generate input for the project plan Discuss the scope of the cooperative domain 5 key themes to discuss: 1. Functionality 2. Reach & addressing 3. Use of (existing) standards 4. Organisation 5. Business model 3 Workshop 1: Scoping a cooperative e-invoicing infrastructure August 28th 2012. All rights reserved.

Agenda for today 10:00 Welcome & introductions 10.20 Vision: why did we start this project? 10:40 Looking back: session June 28 th 11:00 Scope definition: 1. Functionality 2. Reach & addressing 3. Re-use of initiatives, standards & solutions 12:00 Lunch 12:30 Scope definition: 4. Organisation 5. Business model 13:00 Looking forward: project outline 13.30 Wrap-up 4 Workshop 1: Scoping a cooperative e-invoicing infrastructure August 28th 2012. All rights reserved.

Vision why did we start this project? Douwe Lycklama

Why did we embark on this project? Make e-invoicing a better proposition for senders and receivers: Easier sending Easier receiving and integration in processes Lower overall cost, better services As ubiquitous as telephone, sending a letter, sending an email 10 Workshop 1: Scoping a cooperative e-invoicing infrastructure August 28th 2012. All rights reserved.

Yeah but: we re doing alright? Everybody is busy The market grows Flattening growth? Long tail unaddressed? 11 Workshop 1: Scoping a cooperative e-invoicing infrastructure August 28th 2012. All rights reserved.

Grow the market together Better a small piece of a large market than a large piece of a small market Harvest benefits for: End-customers Service providers Society 12 Workshop 1: Scoping a cooperative e-invoicing infrastructure August 28th 2012. All rights reserved.

We will develop an e-invoicing scheme together Sender Receiver Service Provider SENDING (SPs) Service Provider RECEIVING (SPr) COOPERATIVE 15 Workshop 1: Scoping a cooperative e-invoicing infrastructure August 28th 2012. All rights reserved.

Looking back at the previous session (June 28 th ) Tonnis de Boer

Take-away 1: Need for an infrastructure for secure exchange of e-invoices, with a low entry-barrier Low entry-barrier: Easy to apply, accessible, quick to implement and inclusive Infrastructure: A common structure of systems, roles, solutions and agreements that ensure participants can exchange invoices securely Cooperation among service providers is a solution to achieve this A common infrastructure is necessary to get rid of the current model of islands 17 Workshop 1: Scoping a cooperative e-invoicing infrastructure August 28th 2012. All rights reserved.

Take-away 2: Infrastructure based on a 4-corner model Agreements among participants with distinct roles within the model Distinction between cooperative domain & competitive domain Competition on (additional) functionality, rather than reach Scalable model 18 Workshop 1: Scoping a cooperative e-invoicing infrastructure August 28th 2012. All rights reserved.

Take-away 3: Focus is on the cooperative domain Agreements need to be made on three layers of the cooperative domain The competitive domain enables service providers to develop value propositions for end-customers on top of the cooperative domain 19 Workshop 1: Scoping a cooperative e-invoicing infrastructure August 28th 2012. All rights reserved.

Take-away 4: minimal agreements will create maximum result Collaboration with a focus on reach: Any to any Addressing Re-use of existing (European) e- invoicing initiatives Requirements for joining the project & scheme Business model (if any) Standards 20 Workshop 1: Scoping a cooperative e-invoicing infrastructure August 28th 2012. All rights reserved.

Guiding principles as agreed upon June 28th 1. The current market dynamics and strong focus on the large (corporate) buyer does not result in mass adoption of e-invoicing; 2. The current practice, in which interoperability is governed by bilateral agreements between service providers, is not scalable in the long term nor will it result in an optimal situation for the end-customer; 3. Competition among participating service providers should focus on delivering added value to end-customers rather than the reach of their respective (sender and receiver) networks; 4. The infrastructure should facilitate reach towards any (potential) trading entity; 5. The infrastructure should fit within international developments, and be based on best practices of existing (European) e-invoicing initiatives where possible; 6. Project participants are willing to invest (time & money) in the development of the infrastructure. 21 Workshop 1: Scoping a cooperative e-invoicing infrastructure August 28th 2012. All rights reserved.

Scope of the e-invoicing scheme version 1.0 Topics per theme

Scope: 5 key themes to discuss 1. Functionality What process is supported? 2. Reach & addressing How will users find each other and where are e-invoices send to? 3. Use of (existing) standards What standard(s) to use? 4. Organisation What is needed on an organisation & governance level? 5. Business model What is the business case? 24 Workshop 1: Scoping a cooperative e-invoicing infrastructure August 28th 2012. All rights reserved.

1. Supported functionality

Functionality supported by the scheme Suggested scope: 1. Support of a basic e-invoicing process that can be implemented by the participants within the timeframe of the project 2. Basic process: exchange of XML invoice + PDF attachment 3. Receipt confirmation 26 Workshop 1: Scoping a cooperative e-invoicing infrastructure August 28th 2012. All rights reserved.

Additional messages & functionality after version 1.0 Out of scope: Additional invoice messages (e.g.): Approvals, payment confirmation Support for disputes, validation, other e-business messages Storage and e-archiving of invoices 27 Workshop 1: Scoping a cooperative e-invoicing infrastructure August 28th 2012. All rights reserved.

2. Reach / addressing

How will users easily find each other? Suggested scope: 1. Infrastructure facilitates reach 2. Any sender of e-invoices is able to reach any receiver 3. Any receiver of e-invoices is reachable for any sender 4. End-customers are able to exchange invoicing details as easy as telephone numbers 5. End-customers can switch service provider without having to switch address 29 Workshop 1: Scoping a cooperative e-invoicing infrastructure August 28th 2012. All rights reserved.

Example: How does PEPPOL addressing work? PEPPOLs registry locator (DNS) Resolving a REST-URL for the participant. Is automatically directed by the DNS to the relevant registry Service registry (SMP) A message to trading partner ID:731923449 Service metadata (where to send to, what to send) Sending messge according to the service metadata ID:731923449 30 Workshop 1: Scoping a cooperative e-invoicing infrastructure August 28th 2012. All rights reserved.

3. (Re-)use of initiatives, standards & solutions

Re-use of initiatives, standards and solutions Suggested scope: 1. Initiatives: Re-use EESPA-material for agreements on internal control, disputes, SLA Re-use PEPPOL material for addressing 2. Message standards: One primary standard for exchange of invoices within the scheme Outside the scheme, service providers are able to communicate with their customers in any desired format Support of at least 2 versions of the standard chosen Investigate whether UBL2.0 can be used as the single messaging standard An implementation manual of the standard 3. Solutions: Digipoort should be integrated to make the government part of the solution FiNBOX should be accounted for to make bank customers reachable 32 Workshop 1: Scoping a cooperative e-invoicing infrastructure August 28th 2012. All rights reserved.

4. Organisation

Organisation & Governance of the scheme Suggested scope: Legal entity for scheme governance Entry criteria for becoming a participant SLA Internal controls Compliance / adherence Suggested solutions: Development of Foundation E-business Infrastructuur NL or other legal entity (existing organisation) 34 Workshop 1: Scoping a cooperative e-invoicing infrastructure August 28th 2012. All rights reserved.

Scope of organisation & governance Agreements to be made: Conditions and requirements of Foundation e-business infrastructuur NL Becoming a project and scheme participant Being a project and scheme participant Exit of a project and scheme participant Out of scope for version 1.0 : ISO 27001 certification for the governing body and the scheme as a whole 35 Workshop 1: Scoping a cooperative e-invoicing infrastructure August 28th 2012. All rights reserved.

5. Business model

Business model Suggested solution: Each participant has a commercial proposition towards its own endcustomers Every provider has to connect with every provider in the opposite role The scheme allows to make additional bi-lateral agreements on finances, op top of the multi-lateral cooperative agreements of the scheme 37 Workshop 1: Scoping a cooperative e-invoicing infrastructure August 28th 2012. All rights reserved.

Looking forward: project outline Goal, approach and planning

The following activities are foreseen The coming months participants will be working towards the common goal to implement version 1.0 of the scheme by Q2 2013 Key activities: Development of scheme documents by participants on the following subjects: 1. Functionality 2. Reach & addressing 3. Use of (existing) standards 4. Organisation 5. Business model Implementation of scheme version 1.0 Pilot of scheme version 1.0 Live 39 Workshop 1: Scoping a cooperative e-invoicing infrastructure August 28th 2012. All rights reserved.

Scheme development: project outline Stakeholder involvement Direct stakeholders Indirect stakeholders Facilitate integral optimisation of interests on different levels Content, implementation and infrastructure Pragmatic decision-making approach, which should fit the (future) governance structure Working groups: solution / option generation per layer of the scheme Project board: safeguard consistency of scheme documents / working groups Iteration and timeboxing Pivotal to find optimal solutions and to discover bottlenecks 40 Workshop 1: Scoping a cooperative e-invoicing infrastructure August 28th 2012. All rights reserved.

Organisation & Governance of the project Direct stakeholders Participate Project Board Provide input Process Content Indirect stakeholders Participate Working groups Functionality / Solution Information exchange / Technical Organisation / Governance 41 Workshop 1: Scoping a cooperative e-invoicing infrastructure August 28th 2012. All rights reserved.

Required effort by participants Project participation in: 3 working groups 1 project board Estimated 0.5-1 FTE during 4-6 months, depending strongly on scope of solution Implementation in own market offering (own estimates) Contribution to maintenance of the scheme (to be decided) 43 Workshop 1: Scoping a cooperative e-invoicing infrastructure August 28th 2012. All rights reserved.

First milestone: Letter-of-Intent by Oct 15 2012 This phase of the project will be concluded by signing a letter-of-intent, as a sign of formal commitment All participants willing to contribute to the development of the e- invoicing infrastructure are required to sign this letter-of-intent Commitments on scope, approach and required effort for realisation First informal commitment requested before October 1st 44 Workshop 1: Scoping a cooperative e-invoicing infrastructure August 28th 2012. All rights reserved.

Next steps Draft project plan: send for review (7 Sept. 2012) Review round of project plan by participants (10-20 Sept. 2012) Next session: September 27 th 2012 Presentation of final project plan Q&A Intention for participation: in or out? Signing Letter of intent: October 15 th 2012 Start of the project: October 16 th 2012 45 Workshop 1: Scoping a cooperative e-invoicing infrastructure August 28th 2012. All rights reserved.

Wrap-up

Thank you For your cooperation Questions? tonnis@innopay.com

A cooperative e-invoicing infrastructure. Scoping workshop - August 28th 2012