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 196 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.
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.
- Draft204 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.
- Draft97 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.
- Draft189 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 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 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 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 TC 440 technical committee.
- Technical specification37 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
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
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
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
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
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
This document defines a system for the classification of recycled plastics based on the available data depth (Data Quality Levels, DQL) and provides guidelines for the labelling of the recyclate type and recycled content in compounds.
It is intended to support parties involved in the use and trading of recycled plastics, explicitly including digital trading platforms.
- Standard37 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
This document defines a system for the classification of recycled plastics based on the available data depth (Data Quality Levels, DQL) and provides guidelines for the labelling of the recyclate type and recycled content in compounds.
It is intended to support parties involved in the use and trading of recycled plastics, explicitly including digital trading platforms.
- Standard37 pagesEnglish languagee-Library read for1 day
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
This document: — provides method(s) for identifying, in Open-edi modelling technologies and development of scenarios, the additional 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; — integrates existing normative elements in support of privacy and data protection requirements as are already identified in ISO/IEC 14662 and ISO/IEC 15944-1, ISO/IEC 15944-2, ISO/IEC 15944-4, ISO/IEC 15944-5, ISO/IEC 15944-8, ISO/IEC 15944-9 and ISO/IEC 15944-10; — provides overarching, operational ‘best practice’ statements for associated (and not necessarily automated) processes, procedures, practices and governance requirements that act in support of implementing and enforcing technical mechanisms which support the privacy/data protection requirements necessary for implementation in Open-edi transaction environments; — focuses on the life cycle management of personal information, i.e. the contents of SPIs (and their SRIs) related to the business transaction interchanged via EDI as Information Bundles (IBs) and their associated Semantic Components (SCs) among the parties to a business transaction. NOTE Privacy protection requirements (PPR) on information life cycle management (ILCM) and EDI of personal information as stated in this document primarily via enumerated rules which serve as a minimum set of ILCM policy and operational requirements for all recorded information pertaining to a business transaction in particular, as well as ILCM implementation in any organization in general. This document does not specify the technical mechanisms, i.e. functional support services (FSV) which are required to support BOV-identified requirements. Detailed exclusions to the scope of this document are provided in Annex H.
- Standard120 pagesEnglish languagesale 15% off
This document describes:
- the rationale for building customisation supporting business cases that are specific to their business environment while maintaining organisational and semantic interoperability with the TC 440 specifications;
- the difference between Usage specification and Extension specification;
- a methodology on how to define customisations on:
- BII Transaction specification,
- Business rules,
- Code lists;
- how to claim compliance or conformance to a customisation of a TC 440 specification;
- the connection to the eProcurement Ontology project.
This specification does not describe the detailed process of building an extension.
- Technical specification22 pagesEnglish languagee-Library read for1 day
This document gives guidance on online dispute resolution (ODR) for e-commerce transactions including basic principles of ODR, technical recommendations and operational manuals to e-commerce operators (including e-commerce platform operators) which aim to develop their own ODR service and ODR providers that are outsourced by e-commerce operators. NOTE This document is particularly useful for disputes arising out of cross-border, low-value e-commerce transactions. This document can apply to disputes arising out of both goods and service contracts.
- Standard14 pagesEnglish languagesale 15% off
This document addresses the fundamental requirements of the commercial and legal frameworks and their environments on business transactions. It also integrates the requirements of the information technology and telecommunications environments. In addition to the existing strategic directions of "portability" and "interoperability", the added strategic direction of ISO/IEC JTC 1 of "cultural adaptability" is supported in this document. It also supports requirements arising from the public policy/consumer environment, cross-sectoral requirements and the need to address horizontal issues. It integrates these different sets of requirements. (See Figure 3) This document allows constraints which include legal requirements, commercial and/or international trade and contract terms, public policy (e.g. privacy/data protection, product or service labelling, consumer protection), laws and regulations to be defined and clearly integrated into Open-edi through the BOV. This means that terms and definitions in this document serve as a common bridge between these different sets of business operational requirements, allowing the integration of code sets and rules defining these requirements to be integrated into business processes electronically. This document contains a methodology and tool for specifying common business practices as part of common business transactions in the form of scenarios, scenario attributes, roles, Information Bundles and Semantic Components. It achieves this by: 1) developing standard computer processable specifications of common business rules and practices as scenarios and scenario components; and thus, 2) maximizing the re-use of these components in business transactions.
- Draft212 pagesEnglish languagesale 15% off
- Draft212 pagesEnglish languagesale 15% off
This document provides use cases of sharing economy platforms in the public sector, aiming to support municipalities and administrations to apply suitable models of sharing economy platforms for increasing public values and the efficiency of public services.
- Technical report11 pagesEnglish languagesale 15% off
This document provides the description of relevant factors for evaluating E-commerce transactions, which can help in identifying indicators, evaluation toolkits and an approach for selection of indicators. This document focuses on E-commerce transaction assurance by providing the relevant factors of evaluations including quality of E-commerce transaction platforms and sites, quality of E-commerce transaction services, local external environments for E-commerce transactions and sustainability of E-commerce transactions. This document also explains the way to set up a set of E-commerce transaction evaluation indicators that enables monitoring and improvement of the quality of E-commerce transactions.
- Standard19 pagesEnglish languagesale 15% off
This document establishes a semantic data model of an e-receipt or a simplified electronic invoice.
NOTE In the remainder of this document, when “e-receipt” is mentioned, “simplified invoice” is also meant.
The semantic model includes essential information elements that an electronic receipt needs to ensure legal (including fiscal) compliance and to enable interoperability for cross-border, cross sector and domestic trade. The semantic model can be used by organizations in the private and the public sector for documenting by issuing a receipt for the purchase of services and /or goods. It can also be used for documenting a purchase between private sector enterprises. In addition, it has been designed for the use of consumers.
- Technical specification106 pagesEnglish languagee-Library read for1 day
This document describes:
- the rationale for building customisation supporting business cases that are specific to their business environment while maintaining organisational and semantic interoperability with the TC 440 specifications;
- the difference between Usage specification and Extension specification;
- a methodology on how to define customisations on:
- BII Transaction specification,
- Business rules,
- Code lists;
- how to claim compliance or conformance to a customisation of a TC 440 specification;
- the connection to the eProcurement Ontology project.
This specification does not describe the detailed process of building an extension.
- Technical specification22 pagesEnglish languagee-Library read for1 day
This document provides information on the nature of after-sales services unique to E-commerce transactions. It is a review of current practices across different platforms, an analysis of factors that impact quality of after-sales services in E-commerce transactions and a description of possible means to enhance after-sales services.
- Technical report17 pagesEnglish languagesale 15% off
The scope and limitations of the business processes described in this document have been developed to enable the application of the Buy-Ship-Pay business standard for implementations of national, regional, trade sector or modal specific cross-border scenarios. NOTE Only the high-level process descriptions are referenced in this document in order that the detailed process analysis of the subset scenarios can provide the detailed process requirements in further individual Business Requirements Specifications (BRSs).
- Standard16 pagesEnglish languagesale 15% off
This document establishes a semantic data model of an e-receipt or a simplified electronic invoice.
NOTE In the remainder of this document, when “e-receipt” is mentioned, “simplified invoice” is also meant.
The semantic model includes essential information elements that an electronic receipt needs to ensure legal (including fiscal) compliance and to enable interoperability for cross-border, cross sector and domestic trade. The semantic model can be used by organizations in the private and the public sector for documenting by issuing a receipt for the purchase of services and /or goods. It can also be used for documenting a purchase between private sector enterprises. In addition, it has been designed for the use of consumers.
- Technical specification106 pagesEnglish languagee-Library read for1 day
This document provides guidelines for sharing traceability information related to goods quality assurance in E-commerce. This document illustrates the generic process for establishing traceability for goods quality assurance, addresses critical tracking events (CTEs) and key traceability information in the E-commerce context and provides methods for sharing the collected traceability information. This document is intended to be applied to E-commerce supply chains only.
- Standard23 pagesEnglish languagesale 15% off
The purpose of this deliverable is to specify and describe choreographies for exchanging an electronic product catalogue (“catalogues”) as part of the business processes in the pre-award and post-award area, so that catalogues can serve as a basis for placing orders as well as evaluating tenders. The key aspects covered by this choreography specification are:
- processes for submitting catalogues from the selling to the buying side;
- processes for submitting catalogue-related data as part of a tendering process;
- processes integrating sell-side procurement systems.
This document does not apply to the transactions used in the specified choreographies. These transactions are specified in EN 17015 2. The relationship between the choreographies and the transaction is described in Clause 8.
The identifier of this choreographies document is EN 17015 1:2024.
How to claim compliance to this choreography is specified in 6.2.3.
- Standard39 pagesEnglish languagee-Library read for1 day
This choreographies document specify ordering between Buyer and Seller where the Buyer wants to reach an agreement with the Seller about an order. It specifies a series of activities that govern communication between the parties and refers to the specifications where information and rules that apply are specified.
The various possible behaviours of the Seller and Buyer subsequent to the first order communication are conveyed by variants of this choreography that are specified in 5.2.
Previous activities (e.g. cataloguing) and subsequent activities (e.g. invoicing) are outside the scope of this document. If performed electronically, their implementation is covered by other choreographies.
The identifier of this choreographies document is EN 17016-1:2024.
How to claim compliance to this choreography is specified in 5.2.3.
- Standard81 pagesEnglish languagee-Library read for1 day
This document: a) focuses on PbD aspects of privacy protection requirements as external constraints on any type of Person, (e.g. organization or public administration) involved in any kind of business transaction among such Persons which involves the electronic data interchange (EDI) of any personal information; b) establishes a fundamental set of privacy principles known as Privacy by Design and assumptions based on primary sources; c) integrates existing normative elements in support of PbD as are already identified in ISO/IEC 14662 and ISO/IEC 15944-1, ISO/IEC 15944-5, ISO/IEC 15944-8, ISO 15944-12; d) 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 technical mechanisms that support PbD in Open-edi transaction and collaboration space environments; e) focuses on PbD related aspects of the life cycle management of and accountability for the personal information, i.e. the contents of SPIs (and their SRIs) related to the business transaction interchanged via EDI as information bundles and their associated semantic components among the parties to a business transaction. This document focuses on the BOV aspects of a business transaction and does not concern itself with the technical mechanisms needed to implement the FSV aspects of the business requirements of the FSV including the specification of requirements of an FSV nature which include security techniques and services, communication protocols, etc.). The FSV includes any existing standard (or standards development of an FSV nature), which has been ratified by existing ISO, IEC, UN/ECE and/or ITU standards. This document does not specify the technical mechanisms, i.e. FSV which are required to support BOV-identified requirements. Detailed exclusions to the scope of this document are provided in Annex D.
- Standard63 pagesEnglish languagesale 15% off
The purpose of this deliverable is to specify and describe choreographies for exchanging an electronic product catalogue (“catalogues”) as part of the business processes in the pre-award and post-award area, so that catalogues can serve as a basis for placing orders as well as evaluating tenders. The key aspects covered by this choreography specification are:
- processes for submitting catalogues from the selling to the buying side;
- processes for submitting catalogue-related data as part of a tendering process;
- processes integrating sell-side procurement systems.
This document does not apply to the transactions used in the specified choreographies. These transactions are specified in EN 17015 2. The relationship between the choreographies and the transaction is described in Clause 8.
The identifier of this choreographies document is EN 17015 1:2024.
How to claim compliance to this choreography is specified in 6.2.3.
- Standard39 pagesEnglish languagee-Library read for1 day
This choreographies document specify ordering between Buyer and Seller where the Buyer wants to reach an agreement with the Seller about an order. It specifies a series of activities that govern communication between the parties and refers to the specifications where information and rules that apply are specified.
The various possible behaviours of the Seller and Buyer subsequent to the first order communication are conveyed by variants of this choreography that are specified in 5.2.
Previous activities (e.g. cataloguing) and subsequent activities (e.g. invoicing) are outside the scope of this document. If performed electronically, their implementation is covered by other choreographies.
The identifier of this choreographies document is EN 17016-1:2024.
How to claim compliance to this choreography is specified in 5.2.3.
- Standard81 pagesEnglish languagee-Library read for1 day
This document defines the standardized mapping of the specific requirements of an insurance premium invoice to the generic electronic invoice described in EN 16931-1. This mapping meets the requirements of an electronic premium invoice to ensure legal (including fiscal) compliance as well as business and technical demands of the insurance industry.
Premium invoices can be issued by different organizations of the insurance industry to commercial clients or consumers. This document includes premium invoices issued by insurance companies as well as insurance intermediaries.
This document does not deal with data protection matters in premium invoices.
NOTE General Data Protection Regulation, EU Regulation 2016/679 can include requirements on personal data.
Premium invoices are regularly not subject to VAT but to special taxes. In particular, the requirements resulting from insurance tax regulations are considered. Requirements for other taxes are also incorporated.
The rules defined in EN 16931-1 do not support invoices with amounts not subject to VAT together with additional amounts which are subject to VAT. Therefore, this document also does not support premium invoices which invoice other goods and services which are subject to VAT invoiced together with premium amounts.
Out of the scope of this document are accounting transactions between insurance companies and insurance intermediaries which may contain premium invoice data, but regularly consist of other data (e.g. commissions) which are not part of a regular invoice.
- Technical specification34 pagesEnglish languagee-Library read for1 day
This document defines the standardized mapping of the specific requirements of an insurance premium invoice to the generic electronic invoice described in EN 16931-1. This mapping meets the requirements of an electronic premium invoice to ensure legal (including fiscal) compliance as well as business and technical demands of the insurance industry.
Premium invoices can be issued by different organizations of the insurance industry to commercial clients or consumers. This document includes premium invoices issued by insurance companies as well as insurance intermediaries.
This document does not deal with data protection matters in premium invoices.
NOTE General Data Protection Regulation, EU Regulation 2016/679 can include requirements on personal data.
Premium invoices are regularly not subject to VAT but to special taxes. In particular, the requirements resulting from insurance tax regulations are considered. Requirements for other taxes are also incorporated.
The rules defined in EN 16931-1 do not support invoices with amounts not subject to VAT together with additional amounts which are subject to VAT. Therefore, this document also does not support premium invoices which invoice other goods and services which are subject to VAT invoiced together with premium amounts.
Out of the scope of this document are accounting transactions between insurance companies and insurance intermediaries which may contain premium invoice data, but regularly consist of other data (e.g. commissions) which are not part of a regular invoice.
- Technical specification34 pagesEnglish languagee-Library read for1 day
This document specifies the principles and framework for e-commerce transaction assurance, including participants, activities and assurance elements. It does not describe specific e-commerce transaction assurance requirements or methodologies in detail. It is intended to be used by organizations and individuals engaged in e-commerce transactions.
- Standard22 pagesEnglish languagesale 15% off
This document provides terms and definitions in the field of transaction assurance in e-commerce.
- Standard11 pagesEnglish languagesale 15% off
This document provides: — a review and summary of the adoption of digital methods and technology in the national nuclear sectors; — a summary of the state of the art of some of the standards supporting the digital representation and interoperability of industrial data; — orientation on the use of these standards for model-based systems engineering (MBSE) in order to achieve a nuclear digital ecosystem (NDE); — a high-level roadmap of the stages by which this ecosystem can be achieved, taking into account the maturity of the actors of the ecosystem, their relationships and the added value of using advanced standards. NOTE The complete reports from the participating entities are presented in Annexes A to G. This document includes the following: — the systems composing the nuclear facilities and their input, output, and other products resulting from interactions in the nuclear system or with its environment; — the material accounting and the corresponding requirements; — waste management: all types of nuclear waste produced during processes and activities, and their properties are considered for a seamless management of information in the whole value chain of the nuclear ecosystem.
- Technical report87 pagesEnglish languagesale 15% off
This document provides a consolidated set of rules and associated guidelines as found and defined in the existing parts of the ISO/IEC 15944 series. NOTE Not all parts of the ISO/IEC 15944 series have rules, that is ISO/IEC 15944-6, ISO/IEC 15944-14 and ISO/IEC 15944-20.
- Standard213 pagesEnglish languagesale 15% off
This document: — specifies a group of structured and inter-related concepts pertaining to traceability as a legal or regulatory requirement in the Open-edi context, in addition to concepts that appear in other parts of ISO/IEC 15944 series these concepts having the characteristics of cultural adaptability through the use of multilingual terms and definitions; — provides additional specifications for Open-edi scenarios and scenario components from the perspective of traceability as required by internal or external constraints in business transactions; — provides a more detailed specification for business transactions regarding aspects of traceability, including refined models of Person, Data and Process in support of the ability for Open-edi to incorporate elements or characteristics of traceability in its information bundles (including their semantic components) and business processes; — realizes specifications and descriptions from the traceability requirements as rules and guidelines, to provide recommendations or guidance on Open-edi practices; and, — provides revised primitive Open-edi scenario templates for traceability, integrating the modifications to the template from other existing parts of ISO/IEC 15944 series. This document can be used by Open-edi implementers (including business modellers and system designers) and Open-edi standard developers in specifying Open-edi scenarios, developing Open-edi related standards, and implementing Open-edi rules and guidelines for Open-edi activities. This document does not specify the FSV aspects of traceability, internal behaviour requirements of an organization, or traceability as a metrological concept. Detailed exclusions to the scope of this document are provided in Annex H.
- Standard60 pagesEnglish languagesale 15% off
This document specifies the fundamental principles governing coded domains, identification and description of the coded domains from the BOV view, the rules governing the rule-base of coded domains, the rules for management of ID codes, rules for specifying Human Interface Equivalents (HIEs) to an ID Code, the relations between the coded domain and controlled vocabularies, the rules governing the registration of coded domains as re-usable business objects, and the IT-enablement of coded domains. The document is applicable to the use of standards, specifications, authority files, etc., of a “codes representing X” nature being used in electronic business transactions among parties engaged in Open-edi, which pertains to flows of information using information bundles which cause pre-defined (or pre-definable) changes in the states of the IT systems of the parties to such electronic data interchanges. Detailed exclusions to the scope of this document are provided in Annex I.
- Standard105 pagesEnglish languagesale 15% off
This document specifies the business operational view of an implementation of an Open-edi Distributed Business Transaction Repository (OeDBTR), building on the principles and concepts defined in ISO/IEC 15944-4 of a business transaction. The repository stores the history of the transitions in states of the economic claim and/or other business entities that happen over the course of a business transaction, and does so for a collection of business events. These business events, comprised of transactions and their states, can be identified unambiguously so as to provide the ability to inspect or query the information at some point after the record has been made. The distributed nature of the repository offers users ubiquitous and robust access to the recorded history. A history of business transactions of market exchanges can be useful in auditing or other memoing-based activities, looking back at the immutable record of the interactions between parties. This document does not specify the Functional Services View of a particular implementation of an Open-edi Distributed Business Transaction Repository. For best performance, candidate technologies would likely exhibit properties of long-term permanence, robust immutability, decentralized access, distributed resilience, and fine-grained addressability.
- Standard21 pagesEnglish languagesale 15% off