1 / 20

e-Invoicing – e-Ordering 20/11/2008

e-Invoicing – e-Ordering 20/11/2008. Angelo TOSETTI Head of Unit DIGIT B4. Meeting Agenda. Presenting the Project Objectives and Main Benefits Project Status Architecture of the e-PRIOR platform Live Demo of the e-PRIOR platform

nannette
Télécharger la présentation

e-Invoicing – e-Ordering 20/11/2008

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  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 • 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 (Q4 2008 –> 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 (Q3 2009 –> Q4 2009) • Development of e-Ordering (incl. User Interface for Suppliers) • Pilot with selected Suppliers • Post-Pilot Workshop • Packaging, Dissemination...

  10. Architecture Security Reception

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

  12. Demo

  13. MARKT/ENTR DIGIT/MARKT Expert Group e-Invoicing IDABC e-Invoicing & e-Ordering project INFSO Business requirements EEI Framework Profiles Large-Scale Pilot Data model Code table strategy STANDARDISATION INITIATIVES Contributions Contribution to & collaboration with other e-Invoicing initiatives

  14. Ordering Billing Contribution to CEN/BII: Examples Profile – Procurement Cycle Business Collaboration Business Process Transaction 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 Invoice Response Invoice Exchange Invoice

  15. 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 Fullyautomated 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-readabilityvia XSLT. Interchange agreement between Supplier and Customer. VAT Compliance through EDI (Electronic Data Interchange)

  16. Calendar Suppliers Calendar

  17. Q & A

  18. 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). Interface Control Document

  19. 1. INTRODUCTION 1.1. PURPOSE 1.2. SCOPE 1.3. CORE DEFINITIONS, ACRONYMS AND ABBREVIATIONS 1.4. REFERENCES 2. SYSTEM OVERVIEW 2.1. CONTEXT & DOMAIN MODEL 2.2. INTERFACE DESIGN PRINCIPLES 3. FUNCTIONALITIES 3.1. e-PRIOR PROFILES 3.2. e-PRIOR SERVICES 3.3. MESSAGE SPECIFICATION OVERVIEW 4. COMMUNICATION PATTERNS 4.1. ASYNCHRONOUS REQUEST RESPONSE 4.1.1 ASYNCHRONOUS REQUEST RESPONSE LIFECYCLE 4.2. SYNCHRONOUS REQUEST RESPONSE 4.2.1 SYNCHRONOUS REQUEST RESPONSE LIFECYCLE 4.3. NOTIFICATION 4.3.1 NOTIFICATION LIFECYCLE 5. TECHNICAL CONNECTION DESCRIPTION 5.1. SECURITY CONSIDERATIONS 5.1.1. CONFIDENTIALITY & INTEGRITY 5.1.2. AUTHENTICATION MECHANISM 5.1.3 AUTHORISATION MECHANISM 5.2. ERROR MANAGEMENT 5.3. HANDLING OF DUPLICATES AND INVERSIONS 5.4. WEB-SERVICE DESCRIPTION FILES 6. INTERFACE VERSIONING 6.1. SERVICES VERSIONING 6.2. MESSAGES VERSIONING 7. BUSINESS CONTINUITY STRATEGY ICD Table of Contents 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?

More Related