FprCEN/TR 16931-10
(Main)Electronic invoicing – Part 10: Additional requirements to extend to B2B
Electronic invoicing – Part 10: Additional requirements to extend to B2B
All parts of EN 16931 with a specific focus on CEN/TR 16931-5 (Electronic invoicing - Part 5: Guidelines on the use of sector or country extensions in conjunction with EN 16931-1, methodology to be applied in the real environment).
Elektronische Rechnungsstellung - Zusätzliche Anforderungen zur Ausweitung auf B2B
Elektronsko izdajanje računov - 10. del: Dodatne zahteve za razširitev na B2B
General Information
Standards Content (Sample)
SLOVENSKI STANDARD
01-april-2025
Elektronsko izdajanje računov - 10. del: Dodatne zahteve za razširitev na B2B
Electronic invoicing – Part 10: Additional requirements to extend to B2B
Elektronische Rechnungsstellung - Zusätzliche Anforderungen zur Ausweitung auf B2B
Ta slovenski standard je istoveten z: FprCEN/TR 16931-10
ICS:
03.100.20 Trgovina. Komercialna Trade. Commercial function.
dejavnost. Trženje Marketing
35.240.63 Uporabniške rešitve IT v IT applications in trade
trgovini
2003-01.Slovenski inštitut za standardizacijo. Razmnoževanje celote ali delov tega standarda ni dovoljeno.
FINAL DRAFT
TECHNICAL REPORT
RAPPORT TECHNIQUE
TECHNISCHER REPORT
February 2025
ICS
English Version
Electronic invoicing - Part 10: Additional requirements to
extend to B2B
Elektronische Rechnungsstellung - Zusätzliche
Anforderungen zur Ausweitung auf B2B
This draft Technical Report is submitted to CEN members for Vote. It has been drawn up by the Technical Committee CEN/TC
434.
CEN members are the national standards bodies of Austria, Belgium, Bulgaria, Croatia, Cyprus, Czech Republic, Denmark, Estonia,
Finland, France, Germany, Greece, Hungary, Iceland, Ireland, Italy, Latvia, Lithuania, Luxembourg, Malta, Netherlands, Norway,
Poland, Portugal, Republic of North Macedonia, Romania, Serbia, Slovakia, Slovenia, Spain, Sweden, Switzerland, Türkiye and
United Kingdom.
Recipients of this draft are invited to submit, with their comments, notification of any relevant patent rights of which they are
aware and to provide supporting documentation.
Warning : This document is not a Technical Report. It is distributed for review and comments. It is subject to change without
notice and shall not be referred to as a Technical Report.
EUROPEAN COMMITTEE FOR STANDARDIZATION
COMITÉ EUROPÉEN DE NORMALISATION
EUROPÄISCHES KOMITEE FÜR NORMUNG
CEN-CENELEC Management Centre: Rue de la Science 23, B-1040 Brussels
© 2025 CEN All rights of exploitation in any form and by any means reserved Ref. No. FprCEN/TR 16931-10:2025 E
worldwide for CEN national Members.
Contents Page
European foreword . 4
Introduction . 5
1 Scope . 7
2 Normative references. 7
3 Terms and definitions . 7
4 Background . 9
4.1 Facilitating business . 9
4.2 An Analogy for the Core Invoice Model . 11
4.2.1 General . 11
4.2.2 Understanding the Core . 12
4.2.3 Understanding Extensions . 14
4.3 Extensions as a visual analogy . 14
4.4 State of Play . 15
5 The need for Extension Components . 16
5.1 Low adoption rates. 16
5.2 Challenges in diverse business sectors . 17
5.3 Extension components improve interoperability of Extensions . 18
5.4 The benefits of Extension Components . 20
5.5 Using Extension Components . 21
5.5.1 General . 21
5.5.2 Sectors creating eInvoice Specifications . 22
5.5.3 Publishing to the Registry . 25
5.6 Maintenance cycle . 27
5.7 Importance for Stakeholders . 29
6 Adaptations to the Extension Methodology . 29
6.1 General . 29
6.2 Updating the Extension Methodology and EN . 29
6.3 Adding the concept of An Extension Component . 29
6.3.1 General . 29
6.3.2 Proposed Updates . 29
6.3.3 Implications of Proposed updates . 29
6.4 Revising text related to Extensions within the EN Part 1 . 30
6.4.1 General . 30
6.4.2 Current text . 30
6.4.3 Proposed Updates . 30
6.4.4 Semantic Definitions and the use of the words contradiction and infringement. 30
6.4.5 Proposed update . 31
6.4.6 Implications of Proposed updates . 31
6.5 Revising the Definitions in the Extension Methodology . 31
6.5.1 Changing Current Definitions . 31
6.5.2 Proposed Updates . 31
6.5.3 Implications of the Proposed Updates . 31
6.6 Adding the concept of Extension Scope . 31
6.6.1 General . 31
6.6.2 Implications of adding an Extension Scope . 32
6.7 Allowed elements in Extension Components . 32
6.7.1 General . 32
6.7.2 Current Instructions . 33
6.7.3 Proposed Updates . 33
6.7.4 Implications of the Proposed Updates . 33
6.8 Cardinality changes in Extensions. 33
6.8.1 Current Instructions . 33
6.8.2 Proposed Updates — Rules and limitations . 33
6.8.3 Implications of Proposed Updates . 34
6.9 Business rules in Extensions: Additions and Removals . 34
6.9.1 Current Instructions . 34
6.9.2 Proposed Updates . 34
6.9.3 Implications of Proposed Updates . 34
6.10 Extending Code Lists in Extensions . 34
6.10.1 Current Instructions . 34
6.10.2 Proposed update to changing Code Lists . 35
6.10.3 Implications of Proposed Updates . 35
6.11 Changing formats in Extensions (Data types, lengths, etc.) . 36
6.11.1 Current Instructions . 36
6.11.2 Proposed Updates . 36
6.11.3 Implications of proposed updates . 36
6.12 Replacing TOGAF Definitions . 37
6.12.1 General . 37
6.12.2 Proposed Updates . 37
6.12.3 Implications of the Proposed Updates . 38
6.13 Development of an Extension Component Library . 38
6.13.1 General . 38
6.13.2 Implications of the proposed implementation . 38
6.14 Governance Framework . 39
6.14.1 General . 39
6.14.2 Implications of Proposed Updates . 39
6.15 Active Governance. 39
6.15.1 General . 39
6.15.2 Selecting the tools . 39
6.15.3 Active Governance Process for Extension Components .
...
Questions, Comments and Discussion
Ask us and Technical Secretary will try to provide an answer. You can facilitate discussion about the standard in here.