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.
The provision of this registry of CIUS's and Extensions is due to be continued under the Digital Europe Programme after the closure of the CEF Programme. For further details on the transition from CEF to the Digital Europe Programme, please check our news page regularly or contact our helpdesk.
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:
Country | Sector | Identifier | Registration status | Name | Type | Purpose | Publisher | Governing entity | Underlying specification | Further info | Technical Resources | Status | Contact |
---|---|---|---|---|---|---|---|---|---|---|---|---|---|
Any | Any | P | PEPPOL BIS Billing 3.0 | CIUS | Restricts the business process scope of the EN with reference to BIS2 business processes. | OpenPEPPOL | OpenPEPPOL | EN16931 | http://docs.peppol.eu/poacc/billing/3.0/ | ACTIVE | |||
IS | Any | P | Icelandic national CIUS | CIUS | Applies national regulations and imposes data restrictions to support national business practices when the supplier is Icelandic. | IST | ISgov | PEPPOL BIS Billing 3.0 | TS 236:2018 available at www.stadlar.is | ACTIVE | |||
AT | Any | P | Austrian national CIUS | CIUS | Apply national regulations | BRZ | BRZ | EN16931 | https://www.erechnung.gv.at/files/en16931/CIUS-AT-NAT-XS-1.0.0.pdf | ACTIVE | Philip HELGER | ||
AT | Any | P | Austrian government CIUS | CIUS | Additional regulations only applying to the mandatory government interface. This CIUS builds on top of the Austrian national CIUS! | BRZ | BRZ | AT national CIUS | https://www.erechnung.gv.at/files/en16931/CIUS-AT-GOV-XS-1.1.0.pdf | ACTIVE | Philip HELGER | ||
NL | Energy | P | Energy eInvoice | Extension | Enables the addition of information concerning: 1) Measured energy use, including meter info, meter readings, fuel type etc. 2) VAT specification for more than one party, which is a consequence of the so called supplier-centered model. | NEDU | NEDU | EN16931 (specifically: NLCIUS) | https://energie-efactuur.nl/en/ | ACTIVE | |||
IT | Any | P | Italian national CIUS | CIUS | Applies national regulations and restricts data format in compliance with eInvoice national format (FatturaPA) | AdE | AgID, AdE | EN16931 | https://www.agenziaentrate.gov.it/wps/content/nsilib/nsi/normativa+e+prassi/provvedimenti/2019/aprile+2019+provvedimenti/provvedimento+18042019+-+fatturazione+elettronica+europea | ACTIVE | |||
NL | Any | P | NLCIUS | CIUS | Applies national regulations and conventions. The purpose of the NLCIUS is to prevent the need for any other NL governmental or organizational specific CIUS. | NEN | NEN | EN16931 (specifically: NLCIUS) | STPE is a joint initiative of government, industry and standardization bodies in the Netherlands. https://www.stpe.nl | ACTIVE | |||
NL | Any | P | G-account | Extension | A G-account is a dedicated financial account of the supplier party for VAT taxes and wage taxes (loonheffingen). When the required amount of taxes is paid to this G-account, the customer party cannot be held liable by the tax authority in case the supplier party does not fulfill his tax returns. | NEN | NEN | EN16931 (or NLCIUS) | Links: Wiki G-rekening, MKB servicedesk, Belastingdienst, G-account Specification | ACTIVE | |||
DE | Any | P | XRechnung CIUS | CIUS | German public sector CIUS | KoSIT | KoSIT | EN16931 | http://www.xoev.de/de/xrechnung | https://github.com/itplr-kosit | ACTIVE | xrechnung@finanzen.bremen.de | |
DE | Any | P | XRechnung Extension | Extension | German public sector Extension | KoSIT | KoSIT | EN16931 | http://www.xoev.de/de/xrechnung | https://github.com/itplr-kosit | ACTIVE | xrechnung@finanzen.bremen.de | |
BE | Any | P | UBL.BE | Extension | Applies national regulations and conventions. The purpose is to group BE requirements into one specification. | UBL.BE | UBL.BE | EN16931 | http://www.ubl.be/ | ACTIVE | info@ubl.be | ||
FI | Any | P | CIUS | Finland public sector CIUS. | State Treasury | State Treasury | EN16931 | http://www.treasuryfinland.fi/ | DEVELOPMENT | ||||
SP | Any | P | Spanish national CIUS | CIUS | Spanish public sector CIUS. Applies national regulations and conventions for e-invoicing to the public sector and restricts data formats in compliance with eInvoice national format (Facturae). | Spanish Government | Spanish Government | EN16931 | https://administracionelectronica.gob.es/ctt/face/descargas | ACTIVE | |||
Not Applicable | Any | P | European Commission CIUS | CIUS | European Commission CIUS | European Commission | European Commission | PEPPOL BIS Billing 3.0 | PLANNED | EC-PEPPOL-SUPPORT@ec.europa.eu | |||
Not Applicable | Any | P | European Commission Extension | Extension | European Commission electronic invoicing extension to allow multiple receipt advices per invoice | European Commission | European Commission | PEPPOL BIS Billing 3.0 | PLANNED | EC-PEPPOL-SUPPORT@ec.europa.eu | |||
EI | Local / Regional Government | P | Irish Local Government PO Based CIUS | CIUS | List requirements needed when sending an eInvoice to Local Government in Ireland when a Purchase Order is involved | Irish Local Government eInvoice Project - funded by CEF | Irish Local Government eInvoice Project - funded by CEF | PEPPOL BIS Billing 3.0 | http://localgov.einvoicingireland-project.eu/download/Local_Government_CIUS_Ireland_for_Purchase_Order_based_invoicing_v1.5.pdf | DEVELOPMENT | Edmund Gray | ||
EI | Local / Regional Government | P | Irish Local Government Non PO Based CIUS | CIUS | List requirements needed when sending an eInvoice to Local Government in Ireland when a Purchase Order is not required e.g. a Utility Bill | Irish Local Government eInvoice Project - funded by CEF | Irish Local Government eInvoice Project - funded by CEF | PEPPOL BIS Billing 3.0 | http://localgov.einvoicingireland-project.eu/download/Local_Government_CIUS_Ireland_for_NON_PO_v1.3.pdf | DEVELOPMENT | Edmund Gray | ||
Any DE (Germany) | Any | P | ZUGFeRD 2.0, | CIUS | Applies national regulations and imposes data restrictions to support national business practices in Germany | FeRD - Forum elektronische Rechnung in AWV e.V. | AWV - Arbeitsgemeinschft für wirtschaftliche Verwaltung e.V. | EN16931 https://www.ferd-net.de/standards/zugferd-versionsarchiv/zugferd-2.0.1.html | ferd-net.de | ACTIVE | info@ferd-net.de | ||
Any DE (Germany) | Any | P | ZUGFeRD 2.1, profile EN16931 | CIUS | Applies national regulations and imposes data restrictions to support national business practices in Germany. ZUGFeRD 2.1 is fully compatible and technically identical to french standard Factur-X 1.0 | FeRD - Forum elektronische Rechnung in AWV e.V. | AWV - Arbeitsgemeinschft für wirtschaftliche Verwaltung e.V. | EN16931 | ferd-net.de | ACTIVE | info@ferd-net.de | ||
HR | Any | P | Moj-eRačun extension | Extension | The MeR Extension contains additional business terms required by Croatian legal environment, as well as some business terms required for further automation of invoice processing in B2B environment. Instances of invoices compliant to MeR extension remain conformant to all EN business rules and semantic model - the model is only augmented by several business terms. | Moj-eRačun | Moj-eRačun | EN 16931 | https://www.moj-eracun.hr/en/manual#european-norm | ACTIVE | darko.gulija@moj-eracun.hr |
Country | One or more country codes, which the requirements the specification supports. | ||||
---|---|---|---|---|---|
Sector | The industry sector, which requirements the specification supports. | ||||
Identifier | Unique identifier. | ||||
Registration status | Provisional (P) or Verified (V), default is Provisional (P). | ||||
Name | A short descriptive name for general reference. | ||||
Type | CIUS or Extension. | ||||
Purpose | A brief description of what the CIUS or extention specification is intended for. | ||||
Publisher | The party who formally publishes the specification. | ||||
Governing entity | The party who provides the specification its authority. | ||||
Underlying specification | The specification that is used as base. A valid instance according to a CIUS specification must also be valid according to its underlying specification. If not it is an extension. | ||||
Further info | A hyperlink to more detailed information about the specification. Preferably that should include contact information. | ||||
Technical Resources | Direct link to additional technical ressources like validation artefacts, schematrons test cases. | ||||
Status | The status of the specification (PLANNED, DEVELOPMENT, ACTIVE, REVOKED) |
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.
Please note that the information available does not have an authoritative character.