Electronic invoicing - Part 1: Semantic data model of the core elements of an electronic invoice
This European Standard establishes a semantic data model of the core elements of an electronic invoice. The semantic model includes only the essential information elements that an electronic invoice needs to ensure legal (including fiscal) compliance and to enable interoperability for cross-border, cross sector and for domestic trade. The semantic model may be used by organizations in the private and the public sector for public procurement invoicing. It may also be used for invoicing between private sector enterprises. It has not been specifically designed for invoicing consumers. This European Standard complies at least with the following criteria: - it is technologically neutral; - it is compatible with relevant international standards on electronic invoicing; - the application of this standard should comply with the requirements for the protection of personal data of Directive 95/46/EC, having due regard to the principles of privacy and data protection by-design, data minimization, purpose limitation, necessity and proportionality; - it is consistent with the relevant prov

Electronic invoicing - Part 1: Semantic data model of the core elements of an electronic invoice
This European Standard establishes a semantic data model of the core elements of an electronic invoice. The semantic model includes only the essential information elements that an electronic invoice needs to ensure legal (including fiscal) compliance and to enable interoperability for cross-border, cross sector and for domestic trade. The semantic model may be used by organizations in the private and the public sector for public procurement invoicing. It may also be used for invoicing between private sector enterprises. It has not been specifically designed for invoicing consumers. This European Standard complies at least with the following criteria: - it is technologically neutral; - it is compatible with relevant international standards on electronic invoicing; - the application of this standard should comply with the requirements for the protection of personal data of Directive 95/46/EC, having due regard to the principles of privacy and data protection by-design, data minimization, purpose limitation, necessity and proportionality; - it is consistent with the relevant prov

Electronic invoicing - Part 2: List of syntaxes that comply with EN 16931-1
This Technical Specification provides in Clause 7 the list of syntaxes that complies with and allows to express syntactically the core invoice model 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 syntaxes were taken into account and assessed according to criteria provided by the Standardization Request [1].

Electronic invoicing - Part 3-1: Methodology for syntax bindings of the core elements of an electronic invoice
This Technical Specification (TS) specifies the methodology of the mapping between the semantic model of an electronic invoice, included in EN 16931-1 and a syntax. For each element in the semantic model (including sub-elements or supplementary components such as Identification scheme identifiers) it should be defined which element in the syntax is to be used to contain its information contents. Any mismatches between semantics, format, cardinality or structure are indicated.

Electronic invoicing - Part 3-2: Syntax binding for ISO/IEC 19845 (UBL 2.1) invoice and credit note
This document specifies the mapping between the semantic model of an electronic invoice, included in EN 16931-1 and the UBL 2.1 syntax (ISO/IEC 19845). For each element in the semantic model (including sub-elements or supplementary components such as Identification scheme identifiers) it is defined which element in the syntax is to be used to contain its information contents. Any mismatches between semantics, format, cardinality or structure are indicated.

Electronic invoicing - Part 3-4: Syntax binding for UN/EDIFACT INVOIC D16B
This documents specifies the mapping between the semantic model of an electronic invoice, included in EN 16931-1 and the ISO 9735 (UN/EDIFACT) syntax. For each element in the semantic model (including sub-elements or supplementary components such as Identification scheme identifiers) it is defined which element in the syntax is to be used to contain its information contents. Any mismatches between semantics, format, cardinality or structure are indicated.

Electronic invoicing - Part 4: Guidelines on interoperability of electronic invoices at the transmission level
This Technical Report recommends a set of Guidelines to ensure interoperability at the transmission level to be used in conjunction with the European Norm (EN) for the semantic data model of the core elements of an electronic invoice and its other associated deliverables. The Guidelines are by nature non-prescriptive and non-binding. These Guidelines take into account the following aspects: 1) recommending best practices for use at the transmission level; 2) supporting interoperability between all the parties and systems that need to interact and within the various operating models in common use; 3) ensuring a level playing field for the various operating models and bi-lateral implementations and for the use of existing and future infrastructures, which support e-Invoicing; 4) promoting a common terminology and non-proprietary standards for transmission and related areas; 5) ensuring the authenticity of origin and integrity of electronic invoice content; 6) providing guidance on data protection, on the enablement of format conversion, and on e-invoice legibility, including the

Electronic invoicing - Part 5: Guidelines on the use of sector or country extensions in conjunction with EN 16931-1, methodology to be applied in the real environment
This Technical Report describes how trading partners may extend the core invoice model and the related business rules and code lists, in order to support business cases that are specific to their trading environment, while at the same time maintaining semantic interoperability with the core invoice model. This Technical Report does not define a methodology for creation of core invoice usage specification, nor does it describe the detailed process of syntax binding.

Electronic invoicing - Part 6: Result of the test of EN 16931-1 with respect to its practical application for an end user
0.1 Introduction Directive 2014/55/EU states the following: "The standard shall be tested as to its practical application for an end user. The Commission shall retain overall responsibility for the testing and shall ensure that, during the performance of the test, special account be taken of the respect for the criteria of practicality, user-friendliness and possible implementation costs in accordance with the second subparagraph of paragraph 1. 0.2 In scope This CEN Technical Report describes the methodology used for testing at a semantic level and at the syntax level, as well as describing the semantic testing, the syntax testing and testing of the validation artefacts that represent EN 16931-1 and the test results. The testing of the validation artefacts will ensure they can be used to automatically check conformance with EN 16931-1. 0.3 Out of scope During meetings with the European Commission they agreed to supplement the testing activities as the need arises. This included the provision of a hosted GITB (Global eBusiness Interoperability Test Beds) environment for synta