Provide information on CIUS and Extensions
The table below aims to give the eInvoicing community the opportunity to share the ongoing and planned initiatives across Member States and sectors to create CIUS and Extensions on the European standard on eInvoicing. The content is community-driven and the contributors take the sole responsibility of the information shared. Please note that the information available does not have an authoritative character.
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:
|Name||Type||Country||Sector||Purpose of the CIUS or Extension||Publisher||Governor||Underlying specification||Further info||Status||Contact|
OpenPEPPOL BIS 3.0 5A
|CIUS||Any||Any||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/|
Icelandic national CIUS
|CIUS||IS||Any||Applies national regulations and imposes data format to payment instructions when using national payment clearing services.||IST||ISgov||PEPPOL BIS 3.0 5A||http://www.stadlar.is/stadlastarf/fagstadlarad-i-upplysingataekni.aspx|
|Austrian national CIUS||CIUS||AT||Any||Apply national regulations||BRZ||BRZ||EN16931|
|Austrian government CIUS||CIUS||AT||Any||Additional regulations only applying to the mandatory government interface. This CIUS builds on top of the Austrian national CIUS!||BRZ||BRZ||AT national CIUS|
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.
|Energy eInvoice steering committee||Energy eInvoice steering committee||Simplerinvoicing (SI-UBL)||https://energie-efactuur.nl/en/|
|Wouter van den Berg (TNO)|
|Italian national CIUS||CIUS||IT||Any||Applies national regulations and restricts data format in compliance with eInvoice national format (FatturaPA)||AgID, AdE||AgID, AdE||EN16931||http://www.agid.gov.it/agenda-digitale/pubblica-amministrazione/cef-telecom-einvoicing-eigor|
|NLCIUS||CIUS||NL||Any||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 / SMeF||NEN / SMeF||EN16931|
NLCIUS is a joint initiative of government, industry and standardization bodies in the Netherlands (SMeF body).
expected: dec 2017
|G-account||Extension||NL||Any||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 / SMeF||NEN / SMeF||EN16931 (or NLCIUS)|
|XRechnung 1.1||CIUS||DE||Any||German public sector CIUS.||KOSIT||KOSIT||EN16931||http://www.xoev.de/de/xrechnung|
|UBL.BE||Extension||BE||Any||Applies national regulations and conventions. The purpose is to group BE requirements into one specification||UBL.BE||UBL.BE||EN16931||http://www.ubl.be/|
|CIUS||FI||Any||Finland public sector CIUS.||State Treasury||State Treasury||EN16931||http://www.treasuryfinland.fi/|
|Name||A short descriptive name for general reference|
|Type||CIUS or Extension|
|Country||One or more country codes, which the requirements the specification supports.|
|Sector||The industry sector, which requirements the specification supports.|
|Purpose of the CIUS or Extension||A brief description of what the specification is intended for.|
|Publisher||The party who formally publishes the specification.|
|Governor||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.|
The status of the specification (PLANNED, DEVELOPMENT, ACTIVE, REVOKED)
Please note that the information available does not have an authoritative character.