Page tree

CEF DIGITAL home page

eInvoicing Documentation

Registry of supporting artefacts to implement 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 the different technical resources (validation artefacts, code lists, etc.) that are used in eInvoicing implementations when using the eInvoicing standard.



Via this page you also can submit requests for changes - or make your own contributions - depending on the nature of the artefacts. Such change requests are essential to ensure these technical artefacts evolve to suit market needs. You should register on the dedicated page in the eInvoicing User Community to receive email notifications for each update.

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) and approaches for receiving and processing electronic invoices.


CEF eInvoicing code lists technical Advisory Group 

The Advisory Group acts under a mandate to advise and support the European Commission and the CEF eInvoicing team in the maintenance and evolution of the two mentioned code lists. As part of these responsibilities, the group is in charge of validating the “requests for change (RfC)” sent to the CEF eInvoicing team, before updating the code lists on CEF Digital. The group members operate at the request of the European Commission’s Directorate General for Internal Market, Industry, Entrepreneurship and SMEs (hereunder referred to as DG GROW), which organises Advisory Group meetings and acts as chair. The Advisory Group adopts, as far as possible, its opinions and recommendations by consensus.

Scope

The CEF eInvoicing code lists Advisory Group (the Advisory Group) manages the evolution of the two code lists managed by the CEF eInvoicing team, as defined in the European standard for eInvoicing and requested by the European Committee for Standardization’s Technical Committee 434 (CEN/TC434).

Membership and Role

The Advisory Group is composed of representatives from the following groups. Each of these groups can be represented by up to two people, at every meeting of the Advisory Group:

  • European Committee for Standardization Technical Committee 434 (CEN/TC434)
  • Open Pan European Public Procurement On Line Association (OpenPeppol)
  • European E-Invoicing Service Providers Association (EESPA)
  • Publications Office (OP)

Each member joining the meeting accepts to represent their organisation. They have the right to be consulted on the open requests for change and have the power of opinion.

DG GROW may also invite other members on request as relevant to the topics to be addressed.

Frequency of meetings

The Advisory Group holds at minimum a conference meeting before every foreseen publication of a new version of the EAS and/or VATEX code lists.

The release schedule is published on the CEF Digital page Registry of supporting artefacts to implement EN16931.



CEN/TC 434 EN16931

You can get a copy of the European standard itself via the European Standardization Committee, CEN.



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.

CEF is a 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. You can submit a Request for Change (RfC) directly through the CEF Service Desk.



By request from CEN/TC434, CEF has taken on the responsibility to monitor updates to all other code lists that are used in the EN 16931 and, at certain intervals, to provide lists of the code values that are allowed in invoices that comply to the standard as specified in Annex A to the standard.




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, CEF publishes a registry with CIUS and Extensions that have been created fort 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 using the standard to check that an invoice complies with this 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.

CEF has, by request from CEN/TC434, taken on the responsibility of maintaining and publishing these validation artefacts at regular intervals.



Regular release schedule

Code lists

The change requests for the EAS and/or VATEX code lists can be forwarded to the CEF Service desk at all times. They will be bundled as the EAS and VATEX code lists are maintained on a bi-annual schedule, 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 CEF on a bi-annual schedule with fixed dates. Requests for changes are received through the CEF Service desk or via a GitHub Issue.

Processing time is dependent on the complexity and agreement on changes. Simple error corrections may be approved and implemented with short lead time but complex requests may take longer time 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. CEF seeks to resolve every request as quickly as possible and develop them once approved and update the relevant code. CEF applies a code freeze date for each version. Change requests that have been approved and developed before that date are included in the following release.



 Code lists  Validation artefacts  
Process stepsDeadline for change requestsPublication dateEffective date (1)Code freeze date (2)Publication dateEffective date (1)
Spring releaseFriday of 3rd week of February
— next 19/02/2021
Friday of 1st week of March
— next 05/03/2021
15th of May, end of day.
If weekend, then end of following Monday
— next 17/05/2021
Friday of 3rd week of March
— next 19/03/2021
Friday of 1st week of April
— next 09/04/2021
15th May, end of day.
If weekend, then end of following Monday
— next 17/05/2021
Autumn releaseFriday of 3rd week of August
— next 20/08/2021
Friday of 1st week of September
— next 03/09/2021
15th November, end of day.
If weekend, then end of following Monday
— next 15/11/2021

Friday of 3rd week of September
— next 17/09/2021

Friday of 1st week of October
— next 08/10/2021
15th November, end of day.
If weekend, then end of following Monday
— next 15/11/2021

(1) Effective date: the date when compliant implementations of EN 16931 shall have the new version in operation.

(2) Code freeze day: the last day when the code may be modified before it is moved to testing and quality assurance.
Which change requests are included depends on their complexity. Complex changes may require extended decision and development time and correcting simple errors may be done at the last moment.



Looking for help? Need more information?