eInvoicing Documentation
Registry of supporting artefacts to implement the European standard on eInvoicing
Directive 2014/55/EU led to the definition of the European standard on eInvoicing (EN 16931). The Directive promotes the uptake of eInvoicing in public procurement.
This registry provides you with direct access to different technical resources (validation artefacts, code lists, etc.) that are used in eInvoicing implementations when using the eInvoicing standard.
Request for change
Via this page, eInvoicing stakeholders are invited to submit requests for change or make their own contributions - depending on the nature of the artefacts.
Such change requests can be submitted by anybody interested and/or working with eInvoicing and having eInvoicing basic knowledge. These contributions are essential to ensure these technical artefacts evolve to suit market needs.
As an eInvoicing stakeholder, you can register on the dedicated page of the eInvoicing User Community to receive email notifications for each update. And to see the status of eInvoicing in each EU Member State, you can browse the eInvoicing Country Factsheets to see national policy frameworks, eInvoicing platforms (if existing), approaches for receiving and processing electronic invoices, digital reporting requirements, etc.
CEN/TC 434 EN16931
You can get a copy of the European standard itself via the European Standardization Committee, CEN.
- See the guide to obtaining a copy of the European standard on eInvoicing including derivative use
- The European standard on eInvoicing technical specifications and reports in 6 parts
- Technical Body CEN/TC 434 - Electronic Invoicing
Code lists
The European standard on eInvoicing defines which code lists may be used for each business term that has the data type "code", such as electronic address, VAT number, currency, etc.
The Digital Europe Programme (DIGITAL) is the managing authority for two code lists that are used in the EN 16931, the EAS code list and the VATEX code list. For details, please refer to the page about code lists. You can download the code lists in Excel format or in machine readable genericode format. You can submit a Request for Change (RfC) directly through the Service Desk.
EAS code list
- 15/11/24 | Published: 01/10/24 | EAS code list – version 13.0 (latest version)
- 15/11/23 | Published: 06/10/23 | EAS code list – version 12.0
- 15/05/23 | Published: 24/03/23 | EAS code list – version 11.0
- 15/11/22 | Published: 21/09/22 | EAS code list – version 10.0
16/05/22 | Published: 04/03/22 | EAS code list – version 9.0
17/05/21 | Published: 05/03/21 | EAS code list – version 8.0
16/11/20 | Published: 04/09/20 | EAS code list - version 7.0
30/06/20 | Published: 26/05/20 | EAS code list - version 6.0
15/05/20 | Published: 17/02/20 | EAS code list - version 5.0
15/11/19 | Published: 07/10/19 | EAS code list - version 4.0
17/06/19 | EAS code list - version 3.0
15/03/19 | EAS code list - version 2.0
14/11/18 | EAS code list - version 1.0
VATEX code list
15/11/24 | Published: 01/10/24 | VATEX code list - version 6.0 (latest version)
- 15/05/24 | Published: 12/04/24 | VATEX code list - version 5.0
- 16/11/20 | Published: 15/09/20 | VATEX code list - version 4.0
- 15/05/20 | Published: 17/02/20 | VATEX code list - version 3.0
15/11/19 | Published: 07/10/19 | VATEX code list - version 2.0
15/03/19 | VATEX code list - version 1.0
By request of CEN/TC434, DIGITAL has taken on the responsibility of monitoring updates to all other code lists that are used in EN 16931 and, at certain intervals, to provide lists of the code values that are allowed in invoices that comply with the standard as specified in Annex A to the standard.
As of version 7 of the codes are distributed in a computer-readable genericode format, in addition to the normative Excel file.
- 15/11/24| Published: 01/10/24| (latest version)
– Full listing of the code lists as used in EN16931 - version 14.0 | Genericode files - 15/05/24| Published: 12/04/24
– Full listing of the code lists as used in EN16931 - version 13.0 | Genericode files - 15/11/23 | Published: 06/10/23
– Full listing of the code lists as used in EN16931 - version 12.0 - 15/05/23 | Published: 24/03/23
– Full listing of the code lists as used in EN16931 - version 11.0 | Genericode files - 15/11/22 | Published: 21/09/22
– Full listing of the code lists as used in EN16931 - version 10.0 | Genericode files - 16/05/22 | Published: 04/03/22
– Full listing of the code lists as used in EN16931 - version 9.0 | Genericode files 15/11/21 | Published: 10/09/21
– Full listing of the code lists as used in EN16931 - version 8.0 | Genericode files17/05/21 | Published: 05/03/21
– Full listing of the code lists as used in EN16931 - version 7.0 | Genericode files16/11/20 | Published: 15/09/20
– Full listing of the code lists as used in EN16931 - version 6.0 Updated16/11/20 | Published: 04/09/20
– Full listing of the code lists as used in EN16931 - version 6.030/06/20 | Published: 26/05/20
– Full listing of the code lists as used in EN16931 - version 5.015/05/20 | Published: 17/02/20
– Full listing of the code lists as used in EN16931 - version 4.015/11/19 | Published: 07/10/19
– Full listing of the code lists as used in EN16931 - version 3.017/06/19
– Full listing of the code lists as used in EN16931 - version 2.015/03/19
– Full listing of the code lists as used in EN16931 - version 1.0
Technical Guidance document on Tax Codes for eInvoicing
The Technical Guidance document on Tax Codes for Electronic Invoicing describes how codes that are defined in the European electronic invoicing standard (EN 16931) should be used in specific use cases concerning tax. The purpose is to support aligned use of the standard. The first version has been published in July 2024, and it undergoes revisions as required. This document is the result of the discussions among stakeholders within the Technical Advisory Group on Electronic Invoicing led by Georg Birgisson, an external expert on eInvoicing working for the European Commission. Users of the document can propose additional use cases through the DIGITAL Service Desk.CIUS (Core invoice Usage Specifications) and Extensions
The European standard takes into consideration that buyers who must support specific processes or legal requirements may need to restrict, or extend the European standard's core data model. The European standard provides for this by defining Core Invoice Usage Specification (CIUS) and Extensions.
In order to foster sharing of implementation specifications, The Digital Europe Programme has published a registry with CIUS and Extensions that have been created based on the EN 16931. Listing of such specifications is open to all parties and is encouraged.
Validation artefacts
The European standard on eInvoicing defines rules that allow people that are using the standard to check that an invoice complies with the standard. These rules are expressed in technical validation artefacts. These technical artefacts make it possible to automatically validate whether an invoice complies with those rules.
Validation artefacts are implemented by software developers and network specialists as components in eInvoicing services to validate if electronic invoices comply with EN 16931. By using the same validation artefacts, these different eInvoicing services will be aligned across Europe.
DIGITAL has by request from CEN/TC434, taken on the responsibility of maintaining and publishing these validation artefacts at regular intervals. The maintenance of the eInvoicing Registry to support artefacts to implement the European standard on eInvoicing continues under the Digital Europe Programme (DIGITAL) after the closure of the CEF Programme. For further details on the transition from CEF to the Digital Europe Programme, feel free to contact our Service Desk.
- 15/11/24| Published: 08/10/24| (latest versions)
– EN16931 Validation artefacts for UBL 2.1 - version 1.3.13
– EN16931 Validation artefacts for CII 16b - version 1.3.13
– Release notes - version 1.3.13 - 15/05/24| Published: 12/04/24
– EN16931 Validation artefacts for UBL 2.1 - version 1.3.12
– EN16931 Validation artefacts for CII 16b - version 1.3.12
– Release notes - version 1.3.12 - 15/11/23 | Published: 06/10/23
– EN16931 Validation artefacts for UBL 2.1 - version 1.3.11
– EN16931 Validation artefacts for CII 16b - version 1.3.11 15/05/23 | Published: 11/04/23
– EN16931 Validation artefacts for UBL 2.1 - version 1.3.10
– EN16931 Validation artefacts for CII 16b - version 1.3.1015/11/22 | Published: 17/10/22
– EN16931 Validation artefacts for UBL 2.1 - version 1.3.9
– EN16931 Validation artefacts for CII 16b - version 1.3.915/05/22 | Published: 08/04/22
– EN16931 Validation artefacts for UBL 2.1 - version 1.3.8
– EN16931 Validation artefacts for CII 16b - version 1.3.8- 15/11/21 | Published: 04/10/21
– EN16931 Validation artefacts for UBL 2.1 - version 1.3.7
– EN16931 Validation artefacts for CII 16b - version 1.3.7 15/06/21 | Published: 14/06/21
– EN16931 Validation artefacts for UBL 2.1 - version 1.3.6
– EN16931 Validation artefacts for CII 16b - version 1.3.617/05/21 | Published: 13/04/21
– EN16931 Validation artefacts for UBL 2.1 - version 1.3.5
– EN16931 Validation artefacts for CII 16b - version 1.3.501/02/21 | Published: 01/02/21
– EN16931 Validation artefacts for UBL 2.1 - version 1.3.4
– EN16931 Validation artefacts for CII 16b - version 1.3.415/11/20 | Published: 02/10/20
– EN16931 Validation artefacts for UBL 2.1 - version 1.3.3
– EN16931 Validation artefacts for CII 16b - version 1.3.330/06/20 | Published: 26/05/20
– EN16931 Validation artefacts for UBL 2.1 - version 1.3.2
– EN16931 Validation artefacts for CII 16b - version 1.3.215/05/20 | Published: 28/02/20
– EN16931 Validation artefacts for UBL 2.1 - version 1.3.1
– EN16931 Validation artefacts for CII 16b - version 1.3.115/11/19 | Published: 05/10/19
– EN16931 Validation artefacts for UBL 2.1 - version 1.3.0
– EN16931 Validation artefacts for CII 16b - version 1.3.005/07/19
– EN16931 Validation artefacts for UBL 2.1 - version 1.2.3
– EN16931 validation artefacts for CII 16b - version 1.2.314/05/19
– EN16931 Validation artefacts for UBL 2.1 - version 1.2.1
– EN16931 validation artefacts for CII 16b - version 1.2.1
Regular release schedule
Code lists
The change requests for the EAS and/or VATEX code lists can be submitted to the DIGITAL Service desk at all times. They will be processed and released according to the bi-annual maintenance schedule of EAS and VATEX code lists (i.e., in spring and in autumn, with set dates as the deadline for change requests and publication dates).
Validation artefacts
The validation artefacts are maintained by DIGITAL. Requests for changes are received through the DIGITAL Service desk or via a GitHub Issue.
Processing time is dependent on complexity and agreement on changes. Simple error corrections may be approved and implemented within a short lead time, but complex requests may take longer and include consultation with CEN TC434 Working Group 1. Consequently, there is not a specific deadline for each release, in the way that change requests submitted before a certain date will be adopted in that release. DIGITAL seeks to resolve all requests as quickly as possible and develop them once approved and update the relevant artefacts. DIGITAL applies a code freeze date for each version. Change requests that have been approved and developed before that date are included in this version.
Code lists | Validation artefacts | ||||||
---|---|---|---|---|---|---|---|
Process steps | Deadline for change requests | Publication date | Effective date (1) | Code freeze date (2) | Publication date | Effective date (1) | |
Spring 2025 | Friday of 3rd week of February | Friday of 1st week of March | 15th of May, end of day. | Friday of 3rd week of March | Friday of 1st week of April | 15th of May, end of day. | |
Autumn 2025 | Friday of 3rd week of August | Friday of 1st week of September | 15th November, end of day. | Friday of 3rd week of September | Friday of 1st week of October | 15th November, end of day. |
(1) Effective date: the date when compliant implementations of EN 16931 shall have the new version in operation.
(2) Code freeze date: the last day when the code may be modified before it is moved to testing and quality assurance.
What change requests are included depends on their complexity. Complex changes may require extended decision and development time and correcting simple errors that may be made at the last moment.
Looking for help? Need more information?