Page properties | ||||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
|
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, Additional European Economic Area (EEA) countries or 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:
Table Filter | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|
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 Registered (R), 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. | ||||||||||||||||||||||||||||
Technical Resources | Direct link to the technical information fe.eg. Test message (multiple lines/links are possible). | ||||||||||||||||||||||||||||
Further info | A hyperlink to more detailed information about the specification. Preferably that should include contact information. | ||||||||||||||||||||||||||||
Status | The status of the specification (
|
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.
Note |
---|
Please note that the information available does not have an authoritative character. |
Excerpt | |||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|
| |||||||||||
|