Presentation is loading. Please wait.

Presentation is loading. Please wait.

WHAT IT COULD LOOK LIKE European eInvoicing example 1.

Similar presentations


Presentation on theme: "WHAT IT COULD LOOK LIKE European eInvoicing example 1."— Presentation transcript:

1 WHAT IT COULD LOOK LIKE European eInvoicing example 1

2 eInvoice Governance Communities Implementations UN/CEFACT european eInvoicing example UN/CEFACT Procurement domain Core Interoperable Foundation Library BII Profiles BusinessObjects ISO Universal financial industry message scheme Message definition Focus on this 2

3 Used in ‘core’ 3 a European Profile business process models data models and code lists data structures syntax expression ‘Supplier initiated Invoice’ ‘identifier’ ‘date’ ‘currency’ ‘rate’ ‘party’ ‘location’ ‘item’ ‘document’ ‘period’ ‘address’ ‘common procurement library’ ‘billing process’ ‘invoice syntax mapping’ ‘address type’ ‘invoice transaction requirements’ CORE European INVOICE data model ? using a ‘core’ semantic reference for eInvoicing ‘address details’

4 ‘core’ models ‘supplier initiated Invoice’ ‘identifier’ ‘date’ ‘currency’ ‘rate’ ‘party’ ‘location’ ‘item’ ‘document’ ‘period’ ‘address’ ‘address type’ UN/CEFACT Procurement domain UN/CEFACT Bureau Programme Support UN/CEFACT Bureau Programme Support UN/CEFACT Bureau Programme Support maintained by Used in business process models data models and code lists data structures XML format ‘address details’ Used in EDIFACT format 4

5 The role of CEN/BII specifications 5 BII BII is defining core information requirement models – the set of information elements sufficient to cater for the generally expressed business requirements applicable throughout the European market. BII offers an approach to e- Invoicing interoperability within Europe.

6 the CEN/BII European Profile ‘invoice transaction requirements’ ‘billing process’ ‘invoice format mapping’ CEN/BII UN/CEFACT and OASIS UBL CEN/BII maintained by Used in business process models data models and code lists data structures XML format ‘common procurement library’ CORE European INVOICE data model ? 6

7 HOW IT COULD WORK European eInvoicing example 7

8 using ‘core’ semantics Can we speak in English ? 8

9 English is the business language of the global village but we risk getting lost in translation. – Foundation library is large, complex and ambiguous Globish is a ‘core’ controlled vocabulary for humans – A “lingua franca” or bridging language. – A “core” English. – Provides a semantic reference. Globish allows you to: – Communicate in English, using only 1500 words. – Employ simple, but standard grammatical structure. – Learn enough pronunciation and spelling for 1500 words only. – Lead a conversation in business anywhere in the world. – Agree common semantics. – Continue to speak local languages within each community. a human analogy 9

10 Globish-Italian Dictionary Globish* Dictionary using a ‘core’ semantic reference Globish-Hungarian Dictionary “you owe me $100” du schuldest mir 100 $ tu mi debba 100 $ tartozol nekem 100 $ Globish-German Dictionary what we say to each other (regardless of native language) what we say to each other (regardless of native language) For a German to communicate with an Italian they use agreed phrases based on Globish Dictionary semantically equivalent 10

11 UBL Invoice Cross Industry Invoice Financial Invoice UN/CEFACT Core Interoperable Foundation Library European Invoice Semantics European Common Invoice requirements CORE European INVOICE data model ? semantically equivalent 11

12 Hungarian sentence Italian sentence German sentence Globish Semantic References Globish phrase Globish* Dictionary For a German to communicate with an Italian they use agreed phrases based on Globish Dictionary 12

13 UBL Invoice Cross Industry Invoice Financial Invoice UN/CEFACT Core Interoperable Foundation Library European Invoice Semantics European Common Invoice requirements For a community using Financial Invoice to exchange with a community using UBL Invoice - they use European Invoice phrases based on CIFL 13

14 Sample BII (UBL) Invoice Document Salescompany ltd Main street 1 Big city RegionA DK Use of Core Interoperable Foundation Library Extension of cifls:Address NB. not valid syntax  14

15 Sample Financial Invoice Document Finnish Timber Ltd BIZZ Timber street Helsinki

16 PEPPOL Community Banking Community UN/CEFACT Core Interoperable Foundation Library European eInvoice exchange European Common Invoice requirements For a banking community member to exchange invoices with a Spanish organization- they can transform documents using European Invoice semantics (defined by CEN-BII), based on UN/CEFACT CIFL Spanish Community semantically equivalent 16

17 POTENTIAL IMPACT ON UN/CEFACT PROGRAMME OF WORK UN/CEFACT Revised Technical Framework 17

18 potential impact on programme of work UN/CEFACT projects will develop Profiles – ‘Deliverables for Information’ rather then ‘Standards’ – ‘core’ industry rather than ‘cross’ industry – Generic semantics rather than documents, syntax or formats – Similar, but not same as BRS and RSM – Processes, rules and requirements – Formalized business rules – Semantic reference models Other activities… – Develop guidelines Assist in implementation support – Develop UNECE Recommendations Such as Recommendations to use certain specifications or standards As with EDIFACT, Layout Key, Codes, etc.. – Attract more business expertise 18

19 Governance Communities (stakeholders of libraries) Implementations Core Components Library 2.01 Community Core Components Library 3.0 Community UN/EDIFACT Community UNTDED-ISO7372 Community A B what happens to current libraries? D C UN/CEFACT Core Interoperable Foundation Library Note: libraries are developed and approved by communities of use 19

20 UN/CEFACT Projects (approved by Bureau) Agriculture Domain what happens to current BRSs? UN/CEFACT Core Interoperable Foundation Library Sectoral PDA Agriculture Domain eCert Crop Data Sheet E-Lab Supply Chain PDA Procurement Domain CI-* CEFM eTendering BRSs developed as Profiles and approved by projects Registered with self conformance in a UN/CEFACT repository Published as UN/CEFACT Deliverables for Information 20

21 Governance CommunitiesImplementations Agriculture Domain Core Components Library 3.0 community A X what happens to current RSMs? UN/CEFACT Core Interoperable Foundation Library Agriculture Industry Group eCert (RSM) Crop Data Sheet (RSM) Procurement Industry Group CII (RSM) CEFM (RSM) eTendering (RSM) Core Components Library 2.01 Specific technical specifications (such as RSM and Schemas) are developed and approved by governance communities May be registered in a UN/CEFACT repository under a self conformance statement as publications based on UN/CEFACT foundation library (stakeholders of current deliverables) 21

22 summary (proposed) Revised Technical Framework: Standardize on semantics not syntax or formats UN/CEFACT ‘core’ semantics establish foundation for interoperability Communities of use create their own implementations Process, components, structures, documents and syntax Statement of conformance Registry of conformant specifications published by UN/CEFACT UN/CEFACT is a facilitator of interoperability between communities UN/CEFACT impact: UN/CEFACT projects will develop… Profiles for eProcurement processes Business requirements, rules and semantics Published as Deliverables for Information Recommendation for use of standards Communities (e.g. CEN/BII) develops … European core Invoice Data Model European business requirements, rules and semantics 22

23 WHAT NEEDS TO HAPPEN UN/CEFACT Revised Technical Framework 23

24 ISO/PDTR Technical Report Scope Terms and definitions Symbols and abbreviated terms Scope of involved organizations Current work programs Identified issues Analysis The "Open Data Interchange Framework” Recommendations

25 Scope This Technical Report identifies technical specifications and standards that are being maintained, developed or given consideration in work programmes of UN/CEFACT and ISO/TC 154 and strategies that respond to stakeholder requirements for the open interchange of structured data in support of administration, commerce and trade. This may include work from Standards Development Organizations (SDOs) other than ISO and the United Nations Economic Commission for Europe (UNECE).

26 Areas of Activity Classification Matrix

27 Areas of Standardization matrix

28 Tools: Techniques and Methodologies

29 Tools: Naming and Design Rules

30 Tools: Interoperability

31 Information: Data Dictionaries and Models

32 Information: Document Definitions

33 Information: Message Protocols/Syntax

34 Activities: Business Process Models

35 Activities: Profiles

36 Guidance: Business Requirements

37 Guidance: Usage Guidelines

38 Guidance: Interoperability Requirements

39 Identified Issues 1.ISO TS Parts 1-4 are out of date with OASIS standards 2.Gap in maintenance, harmonization and validation procedures for dependent work items 3.Need to improve public communication to user communities 4.Perceived lack of collaboration between ECE/IEC/ISO/ITU 5.Limited awareness and/or acceptance of UN/CEFACT and ISO/TC 154 deliverables 6.Need to improve collaboration on digital signature interoperability 7.Restricted availability of Postal Addressing Specifications for use in eBusiness 8.Need to improve the timing of UN/EDIFACT directory and code list releases 9.Confusion on multiple versions of Core Component Technical Specification 10.Lack of full alignment of TDED, EDED, CCL 2.01 and CCL Need to clarify JTC 1/SC 32/WG 1 Scope and Work Program 12.Overlap of ISO/TC 8 deliverables with UN/CEFACT deliverables 13.Lack of published semantic reference models for Trade Facilitation 14.Ambiguous status of the UNeDocs project

40

41 Methodology & Technology Requirements How to design ‘core’ – Development methodology – ‘tools’ What to build – Content of ‘core’ libraries – ‘information’ How to use ‘core’ – Guidelines for customization ‘activities’ – Guidelines for implementation ‘guidelines’ Different skills Different audience Different governance 41

42 Areas of Standardization Responsibilities Communities of Use

43 Open Data Interchange Framework

44 Applying ODIF to the CIFL

45 Additional Work Items for ISO

46 Additional Work Items for UN/CEFACT

47 Specifications used UN/CEFACT Publications Communities produce Testing conformance to specifications ProcessBusiness processISO ? (UMM) Int. Business Processes Reference Models* Self conformance SemanticsCore ComponentsISO ? (CCTS, UCM) ISO 9735 (EDIFACT) Core Component Library** EDIFACT DED ISO TC 154, UN/CEFACT Business Information Entities*** ISO ? (CCTS, UCM) ISO 9735 (EDIFACT) EDIFACT DEDCustomized Library(s), MIGs ISO TC 154, UN/CEFACT Content constraintsISO ? (DTTS, UCM) ISO 9735 (EDIFACT) UNECE Code lists other Code lists Qualified data types, business rules ISO TC 154, UN/CEFACT StructureDocument StructuresISO ? (CDTS, UCM) ISO 9735 (EDIFACT) EDIFACT UNSMs ‘core’ document structures Message Library(s) ISO TC 154, UN/CEFACT SyntaxFormatsISO 9735 (EDIFACT) OASIS UBL NDR OASIS genericode EDIFACT DED, Code lists and UNSMs XML libraries genericodes Schemas, XML artifacts, MIGs Self conformance Filling out the technical framework

48 NEXT STEPS

49 Schedule

50 Summary Technical Framework: – Focus on ‘core’ standards – Collaborate with SDOs to provide supporting methodologies and technologies – Strengthen maintenance for EDIFACT Organizational: – More business than technology – More maintenance than development – Focus on meeting real market requirements Strategic: – Interoperability foundation for communities of use (Single Windows, Public Procurement, Finance, regional, industry, etc…) – Not doing everything, but ensuring everything is done. – Not what we were, but what we can be. simple, pragmatic and facilitative… and achievable


Download ppt "WHAT IT COULD LOOK LIKE European eInvoicing example 1."

Similar presentations


Ads by Google