1、Electronic invoicingPart 2: List of syntaxes that comply with EN 16931-1PD CEN/TS 16931-2:2017BSI Standards PublicationWB11885_BSI_StandardCovs_2013_AW.indd 1 15/05/2013 15:06TECHNICAL SPECIFICATION SPCIFICATION TECHNIQUE TECHNISCHE SPEZIFIKATION CEN/TS 16931-2 June 2017 ICS 35.240.20; 35.240.63 Eng
2、lish Version Electronic invoicing - Part 2: List of syntaxes that comply with EN 16931-1 Facturation lectronique - Partie 2: Liste de syntaxes conformes avec EN 16931-1 Elektronische Rechnungsstellung - Teil 2: Liste der Syntaxen, die die EN 16931-1 erfllen This Technical Specification (CEN/TS) was
3、approved by CEN on 17 April 2017 for provisional application. The period of validity of this CEN/TS is limited initially to three years. After two years the members of CEN will be requested to submit their comments, particularly on the question whether the CEN/TS can be converted into a European Sta
4、ndard. CEN members are required to announce the existence of this CEN/TS in the same way as for an EN and to make the CEN/TS available promptly at national level in an appropriate form. It is permissible to keep conflicting national standards in force (in parallel to the CEN/TS) until the final deci
5、sion about the possible conversion of the CEN/TS into an EN is reached. CEN members are the national standards bodies of Austria, Belgium, Bulgaria, Croatia, Cyprus, Czech Republic, Denmark, Estonia, Finland, Former Yugoslav Republic of Macedonia, France, Germany, Greece, Hungary, Iceland, Ireland,
6、Italy, Latvia, Lithuania, Luxembourg, Malta, Netherlands, Norway, Poland, Portugal, Romania, Serbia, Slovakia, Slovenia, Spain, Sweden, Switzerland, Turkey and United Kingdom. EUROPEAN COMMITTEE FOR STANDARDIZATION COMIT EUROPEN DE NORMALISATION EUROPISCHES KOMITEE FR NORMUNG CEN-CENELEC Management
7、Centre: Avenue Marnix 17, B-1000 Brussels 2017 CEN All rights of exploitation in any form and by any means reserved worldwide for CEN national Members. Ref. No. CEN/TS 16931-2:2017 ENational forewordThis Published Document is the UK implementation of CEN/TS 16931-2:2017.The UK participation in its p
8、reparation was entrusted to Technical Committee IST/34/-/1.A list of organizations represented on this committee can be obtained on request to its secretary.This publication does not purport to include all the necessary provisions of a contract. Users are responsible for its correct application. The
9、 British Standards Institution 2017 Published by BSI Standards Limited 2017ISBN 978 0 580 96987 4ICS 35.240.63; 35.240.20Compliance with a British Standard cannot confer immunity from legal obligations.This Published Document was published under the authority of the Standards Policy and Strategy Com
10、mittee on 30 September 2017.Amendments/corrigenda issued since publicationDate Text affectedPUBLISHED DOCUMENTPD CEN/TS 169312:2017TECHNICAL SPECIFICATION SPCIFICATION TECHNIQUE TECHNISCHE SPEZIFIKATION CEN/TS 16931-2 June 2017 ICS 35.240.20; 35.240.63 English Version Electronic invoicing - Part 2:
11、List of syntaxes that comply with EN 16931-1 Facturation lectronique - Partie 2: Liste de syntaxes conformes avec EN 16931-1 Elektronische Rechnungsstellung - Teil 2: Liste der Syntaxen, die die EN 16931-1 erfllen This Technical Specification (CEN/TS) was approved by CEN on 17 April 2017 for provisi
12、onal application. The period of validity of this CEN/TS is limited initially to three years. After two years the members of CEN will be requested to submit their comments, particularly on the question whether the CEN/TS can be converted into a European Standard. CEN members are required to announce
13、the existence of this CEN/TS in the same way as for an EN and to make the CEN/TS available promptly at national level in an appropriate form. It is permissible to keep conflicting national standards in force (in parallel to the CEN/TS) until the final decision about the possible conversion of the CE
14、N/TS into an EN is reached. CEN members are the national standards bodies of Austria, Belgium, Bulgaria, Croatia, Cyprus, Czech Republic, Denmark, Estonia, Finland, Former Yugoslav Republic of Macedonia, France, Germany, Greece, Hungary, Iceland, Ireland, Italy, Latvia, Lithuania, Luxembourg, Malta,
15、 Netherlands, Norway, Poland, Portugal, Romania, Serbia, Slovakia, Slovenia, Spain, Sweden, Switzerland, Turkey and United Kingdom. EUROPEAN COMMITTEE FOR STANDARDIZATION COMIT EUROPEN DE NORMALISATION EUROPISCHES KOMITEE FR NORMUNG CEN-CENELEC Management Centre: Avenue Marnix 17, B-1000 Brussels 20
16、17 CEN All rights of exploitation in any form and by any means reserved worldwide for CEN national Members. Ref. No. CEN/TS 16931-2:2017 EPD CEN/TS 169312:2017CEN/TS 16931-2:2017 (E) 2 Contents Page European foreword . 3 Introduction 3 1 Scope 5 2 Normative references 5 3 Terms and definitions . 5 4
17、 Approach 5 5 Assessment criteria 6 6 Assessment Results 7 6.1 UN/CEFACT XML Assessment 7 6.2 UN/EDIFACT Assessment . 7 6.3 OASIS UBL Assessment 8 6.4 Financial Invoice (based on ISO 20022) Assessment . 9 7 List of syntaxes which comply with EN 16931-1:2017 9 Bibliography . 11 PD CEN/TS 169312:2017C
18、EN/TS 16931-2:2017 (E) 3 European foreword This document (CEN/TS 16931-2:2017) has been prepared by Technical Committee CEN/TC 434 “Electronic invoicing”, the secretariat of which is held by NEN. Attention is drawn to the possibility that some of the elements of this document may be the subject of p
19、atent rights. CEN shall not be held responsible for identifying any or all such patent rights. This document has been prepared under a mandate given to CEN by the European Commission and the European Free Trade Association, and supports essential requirements of EU Directive 2014/55/EU 2. This docum
20、ent is part of a set of documents, consisting of: EN 16931-1:2017 Electronic invoicing - Part 1: Semantic data model of the core elements of an electronic invoice CEN/TS 16931-2:2017 Electronic invoicing - Part 2: List of syntaxes that comply with EN 16931-1 CEN/TS 16931-3-1:2017 Electronic invoicin
21、g - Part 3-1: Methodology for syntax bindings of the core elements of an electronic invoice CEN/TS 16931-3-2:2017 Electronic invoicing - Part 3-2: Syntax binding for ISO/IEC 19845 (UBL 2.1) invoice and credit note CEN/TS 16931-3-3:2017 Electronic invoicing - Part 3-3: Syntax binding for UN/CEFACT XM
22、L Industry Invoice D16B CEN/TS 16931-3-4:2017 Electronic invoicing - Part 3-4: Syntax binding for UN/EDIFACT INVOIC D16B CEN/TR 16931-4:2017 Electronic invoicing - Part 4: Guidelines on interoperability of electronic invoices at the transmission level CEN/TR 16931-5:2017 Electronic invoicing - Part
23、5: Guidelines on the use of sector or country extensions in conjunction with EN 16931-1, methodology to be applied in the real environment CEN/TR 16931-61Electronic invoicing - Part 6: Result of the test of the European standard with respect to its practical application for an end user - Testing met
24、hodology According to the CEN-CENELEC Internal Regulations, the national standards organizations of the following countries are bound to announce this European Standard: Austria, Belgium, Bulgaria, Croatia, Cyprus, Czech Republic, Denmark, Estonia, Finland, Former Yugoslav Republic of Macedonia, Fra
25、nce, Germany, Greece, Hungary, Iceland, Ireland, Italy, Latvia, Lithuania, Luxembourg, Malta, Netherlands, Norway, Poland, Portugal, Romania, Serbia, Slovakia, Slovenia, Spain, Sweden, Switzerland, Turkey and the United Kingdom. 1In preparation. PD CEN/TS 169312:2017CEN/TS 16931-2:2017 (E) 4 Introdu
26、ction The European Commission states that “The mass adoption of e-invoicing within the EU would lead to significant economic benefits and it is estimated that moving from paper to e-invoices will generate savings of around EUR 240 billion over a six-year period” 3. Based on this recognition “The Com
27、mission wants to see e-invoicing become the predominant method of invoicing by 2020 in Europe.” As a means to achieve this goal, Directive 2014/55/EU 2 on electronic invoicing in public procurement aims at facilitating the use of electronic invoices by economic operators when supplying goods, works
28、and services to the public administration (B2G) as well as support for the trading between economic operators themselves (B2B). In particular, it sets out the legal framework for the establishment and adoption of a European standard (EN) for the semantic data model of the core elements of an electro
29、nic invoice (EN 16931-1:2017). The core invoice model as described in EN 16931-1:2017 is based on the proposition that a limited, but sufficient set of information elements can be defined that supports generally applicable invoice-related functionalities. In line with Directive 2014/55/EU 2, and aft
30、er publication of the reference to EN 16931-1:2017 in the Official Journal of the European Union, all contracting public authorities and contracting entities in the EU will be obliged to receive and process an e-invoice as long as: it is in conformance with the semantic content as described in EN 16
31、931-1:2017; it is represented in any of the syntaxes identified in CEN/TS 16931-2, in accordance with the request referred to in paragraph 1 of article 3 of the Directive 2014/55/EU; it is in conformance with the appropriate mapping defined in the applicable subpart of CEN/TS 16931-3. This CEN Techn
32、ical Specification provides the conclusions following the assessment of the following four syntaxes: UN/CEFACT Cross Industry Invoice XML message as specified in XML Schemas 16B (SCRDM - CII); UN/EDIFACT INVOIC message as present in the United Nations rules for Electronic Data Interchange for Admini
33、stration, Commerce and Transport (UN/EDIFACT) 8 directory version D.14B 10; UBL invoice and credit note messages as defined in ISO/IEC 19845:2015; Financial Invoice FinancialInvoiceV01 message 9 based on ISO 20022. The assessment was based on the criteria provided by the Standardization Request 1 is
34、sued in accordance with the provisions of Article 3 of Directive 2014/55/EU 2. EN 16931-1:2017 and its ancillary standardization deliverables will enable semantic interoperability of electronic invoices, and help remove market barriers and obstacles to trade deriving from the existence of different
35、national rules and standards and thus contributing to the goals set by the European Commission. PD CEN/TS 169312:2017CEN/TS 16931-2:2017 (E) 5 1 Scope This Technical Specification provides in Clause 7 the list of syntaxes that complies with and allows to express syntactically the core invoice model
36、as specified in EN 16931-1:2017, according to the selection criteria provided by the Standardization Request 1. The selection of the syntaxes also derived from the Standardization Request 1. It states that, to limit costs on public authorities, the list should ideally not exceed five syntaxes. Four
37、syntaxes were taken into account and assessed according to criteria provided by the Standardization Request 1. 2 Normative references The following documents, in whole or in part, are normatively referenced in this document and are indispensable for its application. For dated references, only the ed
38、ition cited applies. For undated references, the latest edition of the referenced document (including any amendments) applies. EN 16931-1:2017, Electronic invoicing - Part 1: Semantic data model of the core elements of an electronic invoice ISO/IEC 19845:20152, Information technology Universal busin
39、ess language version 2.1 (UBL v2.1) UN/CEFACT Cross Industry Invoice in XML Schemas 16B (SCRDM - CII)33 Terms and definitions For the purposes of this document, the terms and definitions given in EN 16931-1:2017 apply. 4 Approach EN 16931-1:2017 defines a semantic model of the core elements of an el
40、ectronic invoice. The purpose of the core semantic invoice model is to facilitate computer applications to generate electronic invoices and then for other applications to receive and process those invoices automatically. These electronic invoices are electronically transmitted and received, without
41、the need for prior bilateral agreement on the content or elements of the invoice. However, in order to exchange electronic invoices, the model elements need to be represented in a “syntax”. A syntax specification allows the computer systems to identify the content (element values) as part of a data
42、stream. CEN/TC 434 identified a short list of syntaxes based on the syntaxes mentioned in the Standardization Request 1: UN/CEFACT XML, UN/EDIFACT 8, OASIS UBL, and Financial Invoice (based on ISO 20022) 9. Table 1 shows the technology stack of the four syntaxes and respective versions by illustrati
43、ng the base syntax, the names and versions of e-Invoicing messaging standards as well as the code-list versions. 2Available also as OASIS UBL v2.1 at http:/docs.oasis-open.org/ubl/os-UBL-2.1/UBL-2.1.pdf 3Available at http:/www.unece.org/cefact/xml_schemas/index PD CEN/TS 169312:2017CEN/TS 16931-2:20
44、17 (E) 6 Table 1 Technology stack for syntaxes and versions Base syntax XML 1.0 ISO 9735 (all parts) 8 (UN/EDIFACT) S4 XML 1.0 XML 1.0 e-Invoicing messaging standard Cross Industry Invoice INVOIC Invoice and Credit Note Financial Invoice e-Invoicing messaging standard version based on directory XML
45、Schemas 16B (SCRDM - CII) based on directory D14B 2.1 v01 Code list versions Codelists based on UN/CEFACT D16B 4 or up Applicable to all syntaxes Codelists based on ISO 2015 or up Applicable to all syntaxes Other (new) codelists 2016 or up Applicable to all syntaxes UN/CEFACT recommendation 20 Revis
46、ion 12 Applicable to all syntaxes UN/CEFACT recommendation 21 Revision 9 Applicable to all syntaxes 5 Assessment criteria The Standardization Request 1 provides a set of criteria (detailed in Table 2) that establishes the basis for the assessment of the syntaxes. Each of the syntaxes has been assess
47、ed according to these criteria. Table 2 The Standardization Request Set of Criteria (Requirements) ID Requirements 1 Comply with the core invoice semantic data model specified in EN 16931-1:2017 2 Be international, open and free to use 3 Have a governance and sustainability model 4 Be part of a cohe
48、rent set of standards and technical specifications to support the broader e-procurement process or the broader e-invoicing supply chain 5 Be widely used in the EU or worldwide 6 Be used in production environments (and not just test) by both the public and the private sector 7 Reflect well-accepted t
49、echnology and aim to incorporate the latest technological developments considered to be state of the art 8 Have guidelines, code lists, validating tools freely available to ease implementation by ICT vendors and suppliers 9 Have a set of official, freely available syntax-dependent artefacts for validation (the XML Schema or Schematron) to support tool independent validation 10 Have an official updating and versioning strategy that takes due account of backward compatibility, as well as appr
