35.240.63 - IT applications in trade
ICS 35.240.63 Details
IT applications in trade
Applications des TI dans le commerce
Uporabniške rešitve IT v trgovini
General Information
Frequently Asked Questions
ICS 35.240.63 is a classification code in the International Classification for Standards (ICS) system. It covers "IT applications in trade". The ICS is a hierarchical classification system used to organize international, regional, and national standards, facilitating the search and identification of standards across different fields.
There are 212 standards classified under ICS 35.240.63 (IT applications in trade). These standards are published by international and regional standardization bodies including ISO, IEC, CEN, CENELEC, and ETSI.
The International Classification for Standards (ICS) is a hierarchical classification system maintained by ISO to organize standards and related documents. It uses a three-level structure with field (2 digits), group (3 digits), and sub-group (2 digits) codes. The ICS helps users find standards by subject area and enables statistical analysis of standards development activities.
e-Library Subscription
Create subscription and get permanent access to documents within 35.240.63 - IT applications in trade
Currently subscription includes documents marked with .We are working on making all documents available within the subscription.
- 1 (current)
- 2
- 3
- 4
- 5
This document specifies the requirements for digital product passport (DPP) access rights management, including IT security, data protection, and responsibility transfer between economic operators. It defines the framework for managing confidential information access, while acknowledging that public DPP data requires no access restrictions to be read.
- Draft18 pagesEnglish languagee-Library read for1 day
This document applies to:
Organisations:
- public sector procurement authorities at local, regional, national, and European levels;
- private sector organizations engaging in innovation partnerships with public entities;
- research and development institutions participating in cross-sector innovation;
- SMEs and large enterprises involved in public-private innovation ecosystems;
- international organizations seeking to implement European innovation procurement approaches.
Innovation Dimensions:
- dimension A: Business Model Innovation (Strategic and Tactical) - 13 innovations across circular economy, product-as-service, and collaborative models;
- dimension B: Innovative Operational Procurement - 12 innovations including enhanced PCP/PPI integration and seven-procedure frameworks;
- dimension C: Innovation Sourcing Infrastructure - 5 high-impact innovations encompassing digital portfolios, AI-driven analytics, and federated intelligence;
- dimension D: Technological Innovation - 20 innovations covering IoT, blockchain, AI, quantum computing, and emerging technologies.
Legal Framework Coverage:
- cross-sector innovation authorization beyond traditional PCP/PPI scope;
- innovation sandbox and safe harbor mechanisms for experimental approaches;
- cross-border legal harmonization for international standards development;
- system-of-Systems legal orchestration for complex multi-organizational coordination;
- liability limitation and risk protection frameworks for good faith innovation.
Scope Exclusions
This document does not cover:
- traditional procurement of standard goods and services without innovation components;
- sector-specific legal frameworks that do not involve cross-sector collaboration;
- emergency procurement procedures where innovation is not the primary objective;
- military and defense procurement subject to specific security classifications;
- legal frameworks for routine administrative procurement below innovation thresholds.
- Draft32 pagesEnglish languagee-Library read for1 day
This document defines the requirements and frameworks for secure information processing and communication to safeguard integrity, authenticity and reliability in the digital product passport (DPP) data exchange, minimizing product fraud and counterfeiting through data verification and integrity enforcement mechanisms.
This document provides a framework for establishing trust, interoperability, and interoperation via secure electronically signed data construct (ESDC) for multi-actor applications, applicable across various sectors and in multilingual environments. Existing hardware and software systems for unique product identification and storage of this identification are to be considered.
The following is out of scope of the document: system architecture for DPP, DPP use cases, secure elements related to data carriers and cryptographic security features for unique product identifiers.
NOTE 1 While not disrupting existing traceability and authentication systems, this document facilitates interoperability by introducing an ESDC scheme to be combined with existing data constructs to cover and preserve existing data models.
NOTE 2 Annex B includes illustrative examples and references to supporting implementations, intended to demonstrate approaches that promote interoperability across diverse environments. These references are provided to assist stakeholders in selecting appropriate solutions that comply with applicable legal obligations and technical standards, while preserving existing systems.
- Draft19 pagesEnglish languagee-Library read for1 day
This document establishes comprehensive frameworks and models for innovative developments in procurement across all sectors, providing systematic methodologies and organizational frameworks enabling transformation of procurement practices through structured governance and innovation management.
This document applies to:
— Organizations
• public sector procurement authorities at local, regional, national, and European levels;
• private sector organizations engaging in innovation partnerships with public entities;
• research and development institutions participating in cross-sector innovation;
• SMEs and large enterprises involved in public-private innovation ecosystems;
• international organizations seeking to implement European innovation procurement approaches.
— Innovation Coverage
• cross-sector innovation frameworks applicable to both public and private organizations;
• enhanced Pre-Commercial Procurement (PCP) and Public Procurement of Innovation (PPI) frameworks;
• system-of-Systems (SoS) orchestration for complex multi-organizational coordination;
• four-dimensional innovation architecture covering business models, operations, sourcing, and technology.
— Framework Applications
• strategic innovation planning and implementation across organizational boundaries;
• digital transformation and technology integration for all sectors;
• circular economy and sustainable procurement models;
• cross-border collaboration and harmonization mechanisms.
- Draft26 pagesEnglish languagee-Library read for1 day
This document establishes the technical pillar of the Strategic Trilogy, converting the 50 INNOV innovations from CEN/TR 17011-2-1 [1] into 87 comprehensive standards while operating within the legal facilitation framework provided by CEN/TR 17011-2-3 [2].
- Draft33 pagesEnglish languagee-Library read for1 day
This document provides information on how to address product quality data interchange based on risk assessment for consumer product safety in e-commerce. This document: analyses e-commerce supply chain context; analyses product risk assessment in e-commerce; gives use cases on risk-based product quality data for interchange; presents the general process for product quality data interchange among e-commerce stakeholders.
- Technical report28 pagesEnglish languagesale 15% off
This document specifies the mapping between the semantic model of an electronic invoice, included in EN 16931-1 and the ISO/IEC 9735 (UN/EDIFACT) syntax. For each element in the semantic model (including sub-elements or supplementary components such as Identification scheme identifiers) it is defined which element in the syntax is to be used to contain its information contents.
- Technical specification211 pagesEnglish languagee-Library read for1 day
This document specifies the mapping between the semantic model of an electronic invoice, included in EN 16931-1 and the UBL syntax. For each element in the semantic model (including sub-elements or supplementary components such as Identification scheme identifiers) it is defined which element in the syntax is to be used to contain its information contents. Any mismatches between semantics, format, cardinality or structure are indicated.
- Technical specification269 pagesEnglish languagee-Library read for1 day
This document specifies the mapping between the semantic model of an electronic invoice, included in EN 16931-1 and the Cross Industry Invoice in the UN/CEFACT XML syntax. For each element in the semantic model (including sub-elements or supplementary components such as Identification scheme identifiers) it is defined which element in the syntax is to be used to contain its information contents. Any mismatches between semantics, format, cardinality or structure are indicated.
- Technical specification152 pagesEnglish languagee-Library read for1 day
This CEN Technical Specification (TS) contains the mapping between the semantic data model of an electronic invoice (EN 16931-1) and the UN/CEFACT XML Industry Invoice syntax. For each element in the semantic model (including sub-elements or supplementary components such as Code List identifiers) it is defined which element in the syntax is to be used to contain its information contents. Any mismatches between semantics, format, cardinality or structure are indicated. Any rules to be followed when using the specific syntax are stated informally in this TS. If later versions of the UN/CEFACT XML Industry Invoice support the semantics more accurately, this is indicated. For earlier versions (from D16B onwards) also a solution is presented.
- Technical specification152 pagesEnglish languagee-Library read for1 day
This CEN Technical Specification (TS) contains the mapping between the semantic data model of an electronic invoice (EN 16931-1) and the UBL syntax. For each element in the semantic model (including sub-elements or supplementary components such as Code List identifiers) it is defined which element in the syntax is to be used to contain its information contents. Any mismatches between semantics, format, cardinality or structure are indicated. Any rules to be followed when using the specific syntax are stated informally
in this TS. If later versions of UBL support the semantics more accurately, this is indicated. For earlier versions (from UBL 2.1 onwards) also a solution is presented.
- Technical specification269 pagesEnglish languagee-Library read for1 day
This CEN Technical Specification (TS) contains the mapping between the semantic data model of an electronic invoice (EN 16931-1) and the UN/EDIFACT INVOIC syntax. For each element in the semantic model (including sub-elements or supplementary components such as Code List identifiers) it is defined which element in the syntax is to be used to contain its information contents. Any mismatches between semantics, format, cardinality or structure are indicated. Any rules to be followed when using the specific syntax are stated informally in this TS. If later versions of the UN/EDIFACT INVOIC support the semantics more accurately, this is indicated.
- Technical specification211 pagesEnglish languagee-Library read for1 day
This document defines the concepts, characteristics and models associated with shared manufacturing. It identifies models associated with shared manufacturing practices and provides principles of intellectual property (IP) management in shared manufacturing. This document is applicable to stakeholders engaged in shared manufacturing.
- Technical report16 pagesEnglish languagesale 15% off
The scope of this document includes:
- the semantic description of a product, including its properties where relevant and the semantic aspects to represent the product lifecycle;
- a common information model allowing for the implementation of data dictionary systems;
- metadata models and formats to be used in exchange and representation, allowing for the integration of dictionaries;
- rules on how to systematically use such metadata models when developing product group specific data models and dictionaries;
- technical and organizational interoperability.
This document follows the approach of standard interoperability layers and proposes the following aspects in this regard.
- Standard25 pagesEnglish languagee-Library read for1 day
This document specifies requirements for data carriers used in a digital product passport system. This covers: symbology characteristics, format, error correction codes, encoding methods, printing and production quality, and durability.
This document also specifies requirements on graphical or other indicators for easy recognition of DPP data carriers and the indication on the data carrier placement, machine readability, quality checking, links between physical product and digital representation.
The following aspects are out of scope: architecture and use cases, secure elements and any other cryptographic security features.
- Standard38 pagesEnglish languagee-Library read for1 day
This document aims to standardize the specifications for the API of the digital product passport (DPP) as mandated by the ESPR of the European Commission. The purpose of this API is to facilitate the searchability of DPPs, as well as to provide the necessary means for interactions throughout the lifecycle of a product's DPP.
- Standard19 pagesEnglish languagee-Library read for1 day
This document defines a standard for secure and efficient data exchange protocols and data formats to be used for the digital product passport. Data exchange protocols establish the rules and procedures that systems follow when communicating and exchanging information. Data formats define the structure and presentation of that information so it can be understood and processed correctly by the involved systems. Together, protocols and formats ensure that data can be exchanged in a manner that is secure, interoperable, reliable, and compatible across various platforms and sectors.
This will guarantee that data are human and machine-readable, structured, searchable, and transferable through an open, interoperable network without vendor lock-in.
a) Secure communication:
This document defines protocols that ensure secure and authenticated data exchange between systems, ensuring that data are protected against unauthorised access and, when necessary, only authorized entities can access the information.
b) Interoperability for data exchange:
The protocols and data formats defined in this document support easy integration with existing data exchange systems, ensure compatibility of protocols and formats across various sectors and supporting a wide range of applications and use cases.
c) Ease of use and integration:
Ensure that the identified protocols and formats can be implemented easily, especially for mobile devices, and are user-friendly in order to facilitate widespread adoption.
d) Data integrity:
The protocols and data formats defined in this document ensure the integrity of information linked to physical objects and electronic data throughout the entire value chain, extending to the product's or asset's end-of-life.
e) Documentation and discoverability:
The protocols and formats are available to individuals without specialized knowledge, enabling broader adoption across sectors.
In order to promote interoperability, reduce costs for businesses, and align with existing European regulations and initiatives, this document considers the data exchange protocols and data formats already in use in other legislations. Relevant existing standards are integrated into the development process to ensure consistency and coherence with industry practices and regulatory frameworks.
- Standard17 pagesEnglish languagee-Library read for1 day
This document specifies requirements for data storage, archiving, and data persistence of digital product passports, all based on a decentralized approach. The archiving functionality securely stores historical passport data, preserving a comprehensive record of past information. Persistence ensures that data included in the digital product passport remains available even when the economic operator creating the digital product passport is no longer active.
This document also specifies requirements for the replication between economic operators and back-up operators as well as rules for data lifetime definition.
- Standard10 pagesEnglish languagee-Library read for1 day
This document defines the principles and specifies the requirements and guidelines for unique product identifiers, unique economic operator identifiers, and unique facility identifiers used in digital product passports. It covers the following areas:
a) global uniqueness;
b) persistence;
c) syntax;
d) granularity;
e) interoperability;
f) openness.
This document accommodates unique product identifiers at three granularity levels of specificity: model, batch, or individual item, to support various operational needs.
This document describes identification (ID) schemes that use issuing agencies, self-issuing systems, or a combination of both.
- Standard58 pagesEnglish languagee-Library read for1 day
This document defines the purpose, governance and functional requirements of the eInvoicing Registry for CIUS and Extension Specifications. This document is not to be confused with other business / project focused Technical Specifications. It follows CEN rules and will be published as a CEN document with normative statements.
A key part of this document is to provide a functional specification, which will describe the various functions of eInvoice Registry Services.
The Registry is intended to serve as a structured, transparent and publicly accessible repository that facilitates the discovery, registration and management of eInvoicing Specifications that either restrict the conditional elements of the Core Invoice Model and/or extend it in conformance with Part 5 Extension Methodology.
The scope of this document includes:
- Definition of Registry Services - the structure and capabilities of the Registry including the types of artefacts it stores or references, e.g. CIUS, Extension Specifications, Validation Artefacts and Services, and Code Lists;
- Governance Model - the roles and responsibilities of entities involved in managing and maintaining the Registry;
- Submission and Verification Processes - how Specifications are submitted, reviewed and verified for inclusion in the Registry;
- Functional Specification - the required functionality, processes and procedures that enable the Registry to operate efficiently.
- Technical specification51 pagesEnglish languagee-Library read for1 day
This document describes the transaction information requirements of the transactions used in the basic
collaborations described in EN 17015-1 Electronic Public Procurement – Catalogue – Choreographies.
For each transaction there is an overview, the transaction business requirements and the transaction information requirements model containing definitions of terms, usage descriptions and cardinality of the information elements.
The document describes the following transactions:
1) Catalogue;
2) Catalogue Response
3) Pre-award Catalogue Request
4) Pre-award Catalogue
5) Shopping Cart
How to claim compliance to a transaction is described in paragraph 6.
How to claim conformance to a transaction is described in paragraph 6.
- Standard144 pagesEnglish languagee-Library read for1 day
This document establishes a framework for the implementation of a sharing economy. It specifies requirements for and gives guidance on the operational economic, social, environmental, legal and other considerations and factors associated with implementation of sharing economy applications and approaches in sharing economy contexts. This document is applicable to all actors participating in the sharing economy ecosystem, including platform operators, providers, users and other stakeholders. This document is applicable to all types and sizes of organization (e.g. commercial enterprises, government agencies, not-for-profit organizations).
- Standard12 pagesEnglish languagesale 15% off
This document describes the transaction information requirements of the transactions used in the collaborations described in EN 17016-1:2024. For each transaction are specified the transaction business requirements, the transaction information data model containing definitions of terms, usage descriptions and cardinality of the information elements and the transaction business rules.
This document describes the following transactions:
1) Order;
2) Order Change;
3) Order Cancellation;
4) Order Response Simple
5) Order Confirmation;
6) Order Rejection;
7) Order Response;
8) Order Change Confirmation;
9) Order Change Rejection;
10) Order Cancellation Confirmation;
11) Order Cancellation Rejection;
12) Order Agreement.
How to claim compliance to a transaction is specified in Clause 6.
How to claim conformance to a transaction is also specified in Clause 6.
- Standard392 pagesEnglish languagee-Library read for1 day
This document aims to standardize the specifications for the API of the digital product passport (DPP) as mandated by the ESPR of the European Commission. The purpose of this API is to facilitate the searchability of DPPs, as well as to provide the necessary means for interactions throughout the lifecycle of a product's DPP.
- Standard19 pagesEnglish languagee-Library read for1 day
The scope of this document includes:
- the semantic description of a product, including its properties where relevant and the semantic aspects to represent the product lifecycle;
- a common information model allowing for the implementation of data dictionary systems;
- metadata models and formats to be used in exchange and representation, allowing for the integration of dictionaries;
- rules on how to systematically use such metadata models when developing product group specific data models and dictionaries;
- technical and organizational interoperability.
This document follows the approach of standard interoperability layers and proposes the following aspects in this regard.
- Standard25 pagesEnglish languagee-Library read for1 day
This document specifies requirements for data storage, archiving, and data persistence of digital product passports, all based on a decentralized approach. The archiving functionality securely stores historical passport data, preserving a comprehensive record of past information. Persistence ensures that data included in the digital product passport remains available even when the economic operator creating the digital product passport is no longer active.
This document also specifies requirements for the replication between economic operators and back-up operators as well as rules for data lifetime definition.
- Standard10 pagesEnglish languagee-Library read for1 day
This document defines a standard for secure and efficient data exchange protocols and data formats to be used for the digital product passport. Data exchange protocols establish the rules and procedures that systems follow when communicating and exchanging information. Data formats define the structure and presentation of that information so it can be understood and processed correctly by the involved systems. Together, protocols and formats ensure that data can be exchanged in a manner that is secure, interoperable, reliable, and compatible across various platforms and sectors.
This will guarantee that data are human and machine-readable, structured, searchable, and transferable through an open, interoperable network without vendor lock-in.
a) Secure communication:
This document defines protocols that ensure secure and authenticated data exchange between systems, ensuring that data are protected against unauthorised access and, when necessary, only authorized entities can access the information.
b) Interoperability for data exchange:
The protocols and data formats defined in this document support easy integration with existing data exchange systems, ensure compatibility of protocols and formats across various sectors and supporting a wide range of applications and use cases.
c) Ease of use and integration:
Ensure that the identified protocols and formats can be implemented easily, especially for mobile devices, and are user-friendly in order to facilitate widespread adoption.
d) Data integrity:
The protocols and data formats defined in this document ensure the integrity of information linked to physical objects and electronic data throughout the entire value chain, extending to the product's or asset's end-of-life.
e) Documentation and discoverability:
The protocols and formats are available to individuals without specialized knowledge, enabling broader adoption across sectors.
In order to promote interoperability, reduce costs for businesses, and align with existing European regulations and initiatives, this document considers the data exchange protocols and data formats already in use in other legislations. Relevant existing standards are integrated into the development process to ensure consistency and coherence with industry practices and regulatory frameworks.
- Standard17 pagesEnglish languagee-Library read for1 day
This document defines the principles and specifies the requirements and guidelines for unique product identifiers, unique economic operator identifiers, and unique facility identifiers used in digital product passports. It covers the following areas:
a) global uniqueness;
b) persistence;
c) syntax;
d) granularity;
e) interoperability;
f) openness.
This document accommodates unique product identifiers at three granularity levels of specificity: model, batch, or individual item, to support various operational needs.
This document describes identification (ID) schemes that use issuing agencies, self-issuing systems, or a combination of both.
- Standard58 pagesEnglish languagee-Library read for1 day
This document specifies requirements for data carriers used in a digital product passport system. This covers: symbology characteristics, format, error correction codes, encoding methods, printing and production quality, and durability.
This document also specifies requirements on graphical or other indicators for easy recognition of DPP data carriers and the indication on the data carrier placement, machine readability, quality checking, links between physical product and digital representation.
The following aspects are out of scope: architecture and use cases, secure elements and any other cryptographic security features.
- Standard38 pagesEnglish languagee-Library read for1 day
This document specifies a semantic data model of the core elements of an Electronic invoice. The semantic data model includes only the essential information elements that an Electronic invoice needs to ensure legal (including fiscal) compliance and to enable interoperability for cross-border, cross sector and domestic trade. The semantic data model can be applied by organizations in the private and the public sector for public procurement invoicing. It can also be used for invoicing between private sector enterprises. It has not been specifically designed for invoicing consumers.
This document complies at least with the following criteria:
— it is technologically neutral;
— it is compatible with relevant international standards on electronic invoicing;
— the application of this standard should comply with the requirements for the protection of personal data of Directive 95/46/EC, having due regard to the principles of privacy and data protection bydesign, data minimization, purpose limitation, necessity and proportionality;
— it is consistent with the relevant provisions of Directive 2006/112/EC [2];
— it allows for the establishment of practical, user-friendly, flexible and cost-efficient electronic invoicing systems;
— it takes into account the special needs of small and medium-sized enterprises as well as of subcentral contracting authorities and contracting entities;
— it is suitable for use in commercial transactions between enterprises.
- Standard163 pagesEnglish languagee-Library read for1 day
This document defines the purpose, governance and functional requirements of the eInvoicing Registry for CIUS and Extension Specifications. This document is not to be confused with other business / project focused Technical Specifications. It follows CEN rules and will be published as a CEN document with normative statements.
A key part of this document is to provide a functional specification, which will describe the various functions of eInvoice Registry Services.
The Registry is intended to serve as a structured, transparent and publicly accessible repository that facilitates the discovery, registration and management of eInvoicing Specifications that either restrict the conditional elements of the Core Invoice Model and/or extend it in conformance with Part 5 Extension Methodology.
The scope of this document includes:
- Definition of Registry Services - the structure and capabilities of the Registry including the types of artefacts it stores or references, e.g. CIUS, Extension Specifications, Validation Artefacts and Services, and Code Lists;
- Governance Model - the roles and responsibilities of entities involved in managing and maintaining the Registry;
- Submission and Verification Processes - how Specifications are submitted, reviewed and verified for inclusion in the Registry;
- Functional Specification - the required functionality, processes and procedures that enable the Registry to operate efficiently.
- Technical specification51 pagesEnglish languagee-Library read for1 day
This document provides a reference model intended to support the analysis and design of B2B electronic transactions utilizing smart contracts. The model identifies and defines five core components that constitute the foundational elements for such transactions, as follows: authentication and responsibility of transaction parties; transaction procedure and execution; transaction consensus mechanism; transaction verification mechanism; security controls.
- Technical report17 pagesEnglish languagesale 15% off
This document describes the transaction information requirements of the transactions used in the basic
collaborations described in EN 17015-1 Electronic Public Procurement – Catalogue – Choreographies.
For each transaction there is an overview, the transaction business requirements and the transaction information requirements model containing definitions of terms, usage descriptions and cardinality of the information elements.
The document describes the following transactions:
1) Catalogue;
2) Catalogue Response
3) Pre-award Catalogue Request
4) Pre-award Catalogue
5) Shopping Cart
How to claim compliance to a transaction is described in paragraph 6.
How to claim conformance to a transaction is described in paragraph 6.
- Standard144 pagesEnglish languagee-Library read for1 day
This document describes the transaction information requirements of the transactions used in the collaborations described in EN 17016-1:2024. For each transaction are specified the transaction business requirements, the transaction information data model containing definitions of terms, usage descriptions and cardinality of the information elements and the transaction business rules.
This document describes the following transactions:
1) Order;
2) Order Change;
3) Order Cancellation;
4) Order Response Simple
5) Order Confirmation;
6) Order Rejection;
7) Order Response;
8) Order Change Confirmation;
9) Order Change Rejection;
10) Order Cancellation Confirmation;
11) Order Cancellation Rejection;
12) Order Agreement.
How to claim compliance to a transaction is specified in Clause 6.
How to claim conformance to a transaction is also specified in Clause 6.
- Standard392 pagesEnglish languagee-Library read for1 day
This European Standard establishes a semantic data model of the core elements of an electronic invoice. The semantic model includes only the essential information elements that an electronic invoice needs to ensure legal (including fiscal) compliance and to enable interoperability for cross-border, cross sector and for domestic trade. The semantic model may be used by organizations in the private and the public sector for public procurement invoicing. It may also be used for invoicing between private sector enterprises. It has not been specifically designed for invoicing consumers.
This European Standard complies at least with the following criteria:
- it is technologically neutral;
- it is compatible with relevant international standards on electronic invoicing;
- the application of this standard should comply with the requirements for the protection of personal data of Directive 95/46/EC, having due regard to the principles of privacy and data protection by-design, data minimization, purpose limitation, necessity and proportionality;
- it is consistent with the relevant provisions of Directive 2006/112/EC [2];
- it allows for the establishment of practical, user-friendly, flexible and cost-efficient electronic invoicing systems;
- it takes into account the special needs of small and medium-sized enterprises as well as of sub-central contracting authorities and contracting entities;
- it is suitable for use in commercial transactions between enterprises.
- Standard163 pagesEnglish languagee-Library read for1 day
This document describes:
- business processes and the technical environments in which simplified invoices and e-receipts are exchanged; and
- the needed syntax bindings of electronic simplified invoices and e-receipts.
- Technical report21 pagesEnglish languagee-Library read for1 day
The European Commission will in its project "VAT in the digital age" (ViDA) mandate that VAT reporting on intra-EU transactions is performed in near real-time and based on EN 16931-1. This Technical Report defines the impact of this legislation on the various deliverables of CEN/TC 434, with a focus on the subset to be sent to tax authorities and how EN 16931-1 needs to be changed. The ViDA package applies to all EU member states and specific territories where the VAT legislation applies (e.g. Northern Ireland in respect to goods).
This document does not define the content of the common electronic message based on the electronic invoice to be sent to the authorities. The definition of that common electronic message (DRR message) is a task of the European Commission, possibly with help of CEN. As the DRR message is not an invoice, but a VAT report, it is not to be regarded as a Core Invoice Usage Specification (CIUS). The DRR message therefore needs not to obey the rules for developing a CIUS. For example, not all mandatory elements in the invoice need to be part of the DRR message.
- Technical report31 pagesEnglish languagee-Library read for1 day
This document: provides method(s) for identifying, in Open-edi modelling technologies and development of scenarios, the extra requirements in Business Operational View (BOV) specifications for identifying the additional external constraints to be applied to recorded information in business transactions relating to personal information of an individual, as required by legal and regulatory requirements of applicable jurisdictional domains having governance over the personal information exchanged among parties to a business transaction; integrates existing normative elements in support of privacy protection requirements as are already identified in ISO/IEC 14662 and ISO/IEC 15944-1, ISO/IEC 15944-2, ISO/IEC 15944-4 and ISO/IEC 15944-5, which apply to information concerning identifiable living individuals as buyers in a business transaction or whose personal information is used in the business transaction; provides overarching operational "best practice" statements for associated (and not necessarily automated) processes, procedures, practices and governance requirements that need to act in support of implementing and enforcing mechanisms needed to support privacy/data protection requirements necessary for the implementation in Open-edi transaction environments; identifies and provides a sample scenario and implementation (use case) for one or more use cases of privacy/data protection in business transactions; provides guidelines on the need for procedural mechanisms in the event that mandatory disclosure rules of transactional information that needs to be implemented. This document does not specify the technical mechanisms needed to implement the Functional Services View. Detailed exclusions to the scope of this document are provided in Annex H.
- Standard133 pagesEnglish languagesale 15% off
This document describes:
- business processes and the technical environments in which simplified invoices and e-receipts are exchanged; and
- the needed syntax bindings of electronic simplified invoices and e-receipts.
- Technical report21 pagesEnglish languagee-Library read for1 day
This document provides practices for developing terms of use for business-to-consumer (B2C) E-commerce platforms, including specific principles, key elements and developing processes. This document is applicable to all parties involved in B2C E-commerce transactions and the development process of terms of use.
- Technical report23 pagesEnglish languagesale 15% off
This document outlines the business processes and data requirements for the implementation of electronic bill of lading (eBL). Its primary focus is the secure digital transfer of title documents via a trusted platform. Additionally, it specifies optional data elements that are essential for leveraging distributed ledger technology (DLT) to support the eBL workflow.
- Standard53 pagesEnglish languagesale 15% off
The purpose of this deliverable is to specify and describe the reference architecture applied as the basis for the development of Business Interoperability Interface specifications in the eProcurement domain by the CEN/TC 440 Technical Committee.
- Technical specification52 pagesEnglish languagee-Library read for1 day
The purpose of this deliverable is to specify and describe the reference architecture applied as the basis for the development of Business Interoperability Interface specifications in the eProcurement domain by the TC 440 technical committee.
- Technical specification37 pagesEnglish languagee-Library read for1 day
The European Commission will in its project "VAT in the digital age" (ViDA) mandate that VAT reporting on intra-EU transactions is performed in near real-time and based on EN 16931-1. This Technical Report defines the impact of this legislation on the various deliverables of CEN/TC 434, with a focus on the subset to be sent to tax authorities and how EN 16931-1 needs to be changed. The ViDA package applies to all EU member states and specific territories where the VAT legislation applies (e.g. Northern Ireland in respect to goods).
This document does not define the content of the common electronic message based on the electronic invoice to be sent to the authorities. The definition of that common electronic message (DRR message) is a task of the European Commission, possibly with help of CEN. As the DRR message is not an invoice, but a VAT report, it is not to be regarded as a Core Invoice Usage Specification (CIUS). The DRR message therefore needs not to obey the rules for developing a CIUS. For example, not all mandatory elements in the invoice need to be part of the DRR message.
- Technical report31 pagesEnglish languagee-Library read for1 day
The purpose of this deliverable is to specify and describe the reference architecture applied as the basis for the development of Business Interoperability Interface specifications in the eProcurement domain by the TC 440 technical committee.
- Technical specification37 pagesEnglish languagee-Library read for1 day
This document describes how trading partners may extend the Core Invoice Model and the related business rules and code lists, to support business cases that are specific to their trading environment, while at the same time maintaining semantic interoperability with the Core Invoice Model.
This document does not define a methodology for creation of a Core Invoice Usage Specification, nor does it describe the detailed process of syntax binding.
- Technical specification38 pagesEnglish languagee-Library read for1 day
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).
- Technical report49 pagesEnglish languagee-Library read for1 day
The purpose of this deliverable is to specify and describe the reference architecture applied as the basis for the development of Business Interoperability Interface specifications in the eProcurement domain by the CEN/TC 440 Technical Committee.
- Technical specification52 pagesEnglish languagee-Library read for1 day
This document specifies the elements, among those defined in PDF digital signatures (PAdES), that enable verification of a digital signature over a long period of time. It does not give new technical specifications about the digital signature itself, nor new restrictions of usage of the technical specifications about the digital signatures which already exist.
- Standard26 pagesEnglish languagesale 15% off
This choreographies document describes the exchange of information in the Fulfilment phase between seller and buyer where the seller wants to announce delivery of the ordered goods or services. The purpose of the fulfilment it is to monitor the executions of the contract. This process is the process between the ordering process and the billing process. The billing process can start when fulfilment has been initiated. The business value for this is:
— To prepare the buyers organization for the physical delivery;
— To enabling an automatic check of delivery for the buying organization before paying the received invoice;
— To match the ordered products with the physical deliveries, such as serial numbers, lot identifiers and other information that might not be present at the time the goods were ordered;
— The assist in getting an accurate calculation of the environmental footprint of the goods by including the emission during the transport;
— To feed data into the logistic process, so no retyping is needed during the transport of the goods.
The identifier of this set of choreographies is EN 17017-1:2025
How to claim conformance to a choreography variant defined in this document is described in 4.2.3.
- Standard28 pagesEnglish languagee-Library read for1 day
- 1 (current)
- 2
- 3
- 4
- 5