The following table is a registry of CIUS and Extension specifications that are planned or published in EU countries. Issuers of specifications, who are members of the eInvoicing User Community, can enter information about their (planned) CIUS and/or Extensions and over time update the status of a specification from Planned → Development → Active. Each update to the registry table is notified to those who are following this page.

During the development process or after publication the issuing party can submit a specification to the CEF eInvoicing Advisory Group that will verify it against a set of criteria. Published specifications that have been verified by the Advisory Group will get the registry status "Verified" while other specifications will have the status "Provisional". Requests for verification may be submitted to the Advisory Group by contacting eInvoicing through the CEF Service Desk.

We invite you to contribute to build on the information available about the CIUS and Extensions on the European standard on eInvoicing by filling the table below:

Evaluation of CIUS and Extensions

CIUS

The compliance of a CIUS is defined in section 4.4.2 in EN 16931, Part 1 as follows:

The core invoice usage specifications that are used in conjunction with the core invoice model shall themselves comply to the methodology and rules described in this guideline and expressed in the following criteria:

—    the specification shall clearly state what business functions and/or legal requirements it is intended to support;

—    the specification shall clearly state its issuer and responsible 'governor';

—    the specification shall clearly state in what way the requirements of the CIUS differ from the core invoice model, either by documenting the difference only or by specifically pointing out what the differences are;

—    the resulting invoice document instance shall be fully compliant to the core invoice model.

—    the specification and, when relevant, its version shall be uniquely identifiable both for referencing and for identification in processing;

—    the specification shall state its underlying specifications (the core invoice model as well as other specifications that it may build upon);

Extensions

The compliance of an Extension is defined in section 5.2 in EN 16931, part 5 as follows:

The extension specifications that are used in conjunction with the core invoice model shall themselves adhere to the methodology and rules described in this guideline and expressed in the following criteria:

— The specification shall clearly state what business functions and/or legal requirements it is intended to support in addition to those covered by the core invoice model.

— The specification shall clearly state its publisher and governor.

— The specification shall clearly state in what way it differs from the core invoice model. The specification and, when relevant, its version shall be uniquely identifiable both for referencing and for identification in processing.

— The specification shall state its underlying specifications and their version.

— The syntax binding of a specification shall follow the syntax binding methodology defined in CEN/TS 16931-3-1.

A resulting semantic data model is defined as being conformant to the core invoice model if its information elements, together with the business rules defined on them, do not form a subset of the core invoice model but add to it.