1. e-Invoicing – e-Ordering 20/11/2008
Angelo TOSETTI Head of Unit DIGIT B4

2. Meeting Agenda
Presenting the Project
Objectives and Main Benefits
Project Status
Architecture of the e-PRIOR platform
Live Demo of the e-PRIOR platform
“What does it mean to participate in the e-Invoicing pilot?”
Pilot (milestones) schedule  Supplier's agenda
Questions and Answers
Introducing the ICD
Brief exchange of ideas on e-Ordering

3. Objectives Main Benefits
Contribute to the i2010 action plan
Contribute to establishing the EEI Framework
Main Benefits
Practical experience
Private sector can leverage from Public sector experience
Transfer and reuse national practises in a cross-border environment
Experience, specifications, tools and components available to MS
Reduce manual interactions and re-work
Reduce payment delays

4. Project Status 1/2

5. Project Status 1/2

6. Project Status 1/2

7. Project Status 1/2

8. Phase 1
Elaboration of the Architecture
Development of Basic Invoice
Invoice
Attachment
Status Request
Development of additional use cases
User Access
Logging
View Business Document
...

9. Phase 2
Phase 2a (Q –> Q2 2009)
Development of Invoice with Dispute (incl. Credit Notes)
Development of additional use cases (Administration Console, Summary Report, Notification...)
Pilot with selected Suppliers
Post-Pilot Workshop
Phase 2b (Q –> Q4 2009)
Development of e-Ordering (incl. User Interface for Suppliers)
Packaging, Dissemination...

10. Architecture
Security
Reception

11. Routing Workflow Validation Archiving Logging
Architecture
Loose-coupling
Loose-coupling
Routing
Workflow
Simulation:
Outbox
Sent folder
Inbox
Javest (SME)
soapUI (Large corporate)
Validation
Archiving
Logging

12. Demo

13. Business requirements
Contributions
EEI Framework
Expert Group e-Invoicing
MARKT/ENTR
IDABC e-Invoicing &
e-Ordering project
DIGIT/MARKT
Business requirements
Data model
Code table
strategy
Profiles
Large-Scale Pilot
INFSO
STANDARDISATION INITIATIVES
The IDABC e-Invoicing and e-Ordering project is providing a number of deliverables: business requirements for e-Invoicing in a public procurement environment and international context; profiles (= standardized business processes); a data model and a code table strategy.
We collaborate with the Expert Group on e-Invoicing, and have given our input with regards to business requirements and the use of standards
We also provide direct input to the PEPPOL consortium, more concretely to WP5 (e-Invoicing), WP4 (e-Ordering) and WP8 (Infrastructure)
We also participate to the CEN/BII workshop, and help them with the use of profiles and give our input towards the formats;
Contribution to & collaboration with other e-Invoicing initiatives

14. Contribution to CEN/BII: Examples
Profile – Procurement Cycle
Business Collaboration
Business Process
Transaction
Ordering
Order
We contributed to the enhancement of the CEN/BII profiles, making them independent from the message standards
The Code Lists (ie. master data) subgroup is chaired by us
Order Exchange
Order Response
Profile – Billing with Dispute
Credit Note
Dispute Resolution
Dispute
Post awarding
Invoice
Profile – Invoice Only
Billing
Invoice Response
Invoice Exchange
Invoice

15. VAT Compliance through EDI (Electronic Data Interchange)
e-Invoicing: authenticity of origin and integrity of content:
Pre-registration of suppliers
Secured network (https with username/password authentication)
Party identifiers (EAN)
Audit log
3 step validation of incoming invoices
Fully automated processes
e-Archiving: authenticity, integrity and readability:
All data related to the transaction is securely archived, including the original invoice, a canonical format, timestamps, …
Human-readability via XSLT.
Interchange agreement between Supplier and Customer.
In order to comply with the VAT requirements, we decided to implement the EDI method. We have implemented a number of procedures to guarantee authenticity of origin, integrity of content and readability, which will be documented in an interchange agreement.

16. Calendar
Suppliers Calendar

17. Q & A

18. Interface Control Document
A Service is a mechanism to enable access to one or more capabilities of e-PRIOR using a prescribed interface;
A service is accessed by means of a service interface (specifics of how to access the underlying capabilities);
A service is opaque in that its implementation is typically hidden from the service consumer;
The Interface Control Document is a specification aimed at defining (in detail) the interface between e-PRIOR and every Supplier System;
In a nutshell, it gathers the business and technical specifications (in terms of services, exchanged messages, data items, technical protocols and Orchestrations).

19. Changes are still possible Please use as a reference
ICD Table of Contents
1. INTRODUCTION
PURPOSE
SCOPE
CORE DEFINITIONS, ACRONYMS AND ABBREVIATIONS
REFERENCES
SYSTEM OVERVIEW
CONTEXT & DOMAIN MODEL
INTERFACE DESIGN PRINCIPLES
FUNCTIONALITIES
e-PRIOR PROFILES
e-PRIOR SERVICES
MESSAGE SPECIFICATION OVERVIEW
COMMUNICATION PATTERNS
ASYNCHRONOUS REQUEST RESPONSE
ASYNCHRONOUS REQUEST RESPONSE LIFECYCLE
SYNCHRONOUS REQUEST RESPONSE
SYNCHRONOUS REQUEST RESPONSE LIFECYCLE
NOTIFICATION
NOTIFICATION LIFECYCLE
TECHNICAL CONNECTION DESCRIPTION
SECURITY CONSIDERATIONS
CONFIDENTIALITY & INTEGRITY
AUTHENTICATION MECHANISM
AUTHORISATION MECHANISM
ERROR MANAGEMENT
HANDLING OF DUPLICATES AND INVERSIONS
WEB-SERVICE DESCRIPTION FILES
INTERFACE VERSIONING
SERVICES VERSIONING
MESSAGES VERSIONING
BUSINESS CONTINUITY STRATEGY
Changes are still possible
Please use as a reference

20. e-Ordering
Do you receive orders from the European Commission?
Are you able to receive them via electronic means? If yes, how (standards, protocols, policies)?
Who can we contact to gather further business requirements?