03.060 - Finances. Banking. Monetary systems. Insurance
ICS 03.060 Details
Finances. Banking. Monetary systems. Insurance
Finanzen. Bankwesen. Wahrungssysteme. Versicherungswesen
Finances. Banque. Systemes monétaires. Assurance
Finance. Bančništvo. Monetarni sistemi. Zavarovanje
General Information
Frequently Asked Questions
ICS 03.060 is a classification code in the International Classification for Standards (ICS) system. It covers "Finances. Banking. Monetary systems. Insurance". 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 230 standards classified under ICS 03.060 (Finances. Banking. Monetary systems. Insurance). 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 03.060 - Finances. Banking. Monetary systems. Insurance
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 defines a method for generating and verifying card security codes (CSCs) using cipher-based message authentication code (CMAC) or keyed-hash message authentication code (HMAC). Key management mechanisms associated with these processes are beyond the scope of this document.
- Standard8 pagesEnglish languagesale 15% off
This document specifies a general framework, including principles, requirements and guidance for assessing, measuring, monitoring and reporting on investments and financing activities in relation to climate change and the transition into a low-carbon economy. The assessment includes the following items:
the alignment (or lack thereof) of investment and financing decisions taken by the financier with low-carbon transition pathways, adaptation pathways, and climate goals;
the impact of actions through the financier’s investment and lending decisions towards the achievement of climate goals in the real economy, i.e. mitigation (greenhouse gas emissions) and adaptation (resilience);
the risks to owners of financial assets (e.g. private equities, listed stocks, bonds, loans) arising from climate change.
To support the financier’s assessment of the impact of investment and lending decisions, this document provides guidance for the financier on how to:
set targets and determine metrics to be used for tracking progress related to the low-carbon transition pathways of investees;
determine low-carbon transition and adaptation trajectories of investees;
document the causality or linkage between its climate action and its outputs, outcomes and impacts.
This document is applicable to financiers, i.e. investors and lenders. It guides their reporting activities to the following third parties: shareholders, clients, policymakers, financial supervisory authorities and non-governmental organizations.
- Standard54 pagesEnglish languagee-Library read for1 day
This document specifies a general framework, including principles, requirements and guidance for assessing, measuring, monitoring and reporting on investments and financing activities in relation to climate change and the transition into a low-carbon economy. The assessment includes the following items:
the alignment (or lack thereof) of investment and financing decisions taken by the financier with low-carbon transition pathways, adaptation pathways, and climate goals;
the impact of actions through the financier’s investment and lending decisions towards the achievement of climate goals in the real economy, i.e. mitigation (greenhouse gas emissions) and adaptation (resilience);
the risks to owners of financial assets (e.g. private equities, listed stocks, bonds, loans) arising from climate change.
To support the financier’s assessment of the impact of investment and lending decisions, this document provides guidance for the financier on how to:
set targets and determine metrics to be used for tracking progress related to the low-carbon transition pathways of investees;
determine low-carbon transition and adaptation trajectories of investees;
document the causality or linkage between its climate action and its outputs, outcomes and impacts.
This document is applicable to financiers, i.e. investors and lenders. It guides their reporting activities to the following third parties: shareholders, clients, policymakers, financial supervisory authorities and non-governmental organizations.
- Standard54 pagesEnglish languagee-Library read for1 day
This document specifies requirements and recommendations for strategic transition planning by financial institutions, designed to protect and enhance value by supporting institutions’ response and contribution to a global net zero and climate-resilient economy. The requirements and recommendations are designed to enable financial institutions to develop and maintain transition planning objectives and targets that advance the temperature and resilience goals of the Paris Agreement[23], and establish robust policies and processes to integrate these into their financial activities. This document is applicable to any financial institution, regardless of size, type and geographic location, with a particular focus on banking, insurance and investment institutions. Its provisions are applied in the context of the institution’s particular business model. NOTE 1 Some considerations specific to particular institution types are included in guidance notes. Additional guidance on product attributes specific to different types of financial institution can be found in Annex A. This document is applicable to all financial activities (including lending, insurance, asset owner investing, asset manager investing and capital market activities) that the institution determines it can either control or influence, using a life cycle perspective (e.g. those described in 7.2.2). It can also be applicable to relevant financial activities within real economy institutions and emerging financial institution types, many of which leverage digital technologies and can be subject to different or bespoke regulatory frameworks (e.g. decentralized finance (DeFi) platforms). NOTE 2 This document is intended for global application, recognizing that some financial institutions, including those in some emerging market and developing economies (EMDEs), can face constraints in the local enabling regulatory environment and data availability. It therefore seeks to ensure flexibility and proportionality in application, as appropriate. NOTE 3 Documents on asset management developed by ISO/TC 251, including ISO 55000[18], ISO 55001[19] and detailed guidance in ISO 55002[20], can be useful for financial institution asset management activity, particularly as it relates to alignment of asset management with business objectives (e.g. those related to transition planning).
- Standard47 pagesEnglish languagesale 15% off
This document specifies the responsibilities of the Registration Authority (RA) and the Submitting Organizations. NOTE Details concerning the involvement of Technical Committee ISO/TC 68, Financial services, Subcommittee SC 9, Information exchange for financial services, in the registration request process can be found on the ISO 20022 website (see www.iso20022.org).
- Standard6 pagesEnglish languagesale 15% off
This document describes the transformation rules to generate ASN.1 abstract syntax from an ISO 20022 compliant MessageDefinition. The generated abstract syntax is for the description and validation of Messages. The transformation rules are a transformation from Level 3 to Level 4. It is a deterministic transformation, meaning that the resulting ASN.1 is completely predictable for a given MessageDefinition. There is neither manual input to the transformation itself nor manual adjustment to the result of the transformation. This document is the ASN.1 equivalent of ISO 20022-4. In ISO 20022-4 the abstract syntax generated is XML Schema; in this document it is ASN.1. In ISO 20022-4 the only encoding supported is UTF-8 XML; in this document there are multiple encodings supported for ASN.1. These include all the standard encodings, but in addition the ability to register custom encodings in Encoding Control Notation (ECN).
- Standard20 pagesEnglish languagesale 15% off
This document complements the ISO 20022 Metamodel, as specified in ISO 20022-1, with generic requirements and guidelines to define specific syntax generation rules for other encodings in order to produce schemas based on each specific syntax generation rules in compliance with this document. Such specific syntaxes include XML, ASN.1 and JSON. (XML and ASN.1 do not imply ISO 20022-4 XML schema generation and ISO 20022-8 ASN.1 generation only. W3C XML Schema, ASN.1 and JSON can be used to express or define a variety of schema types.) Under this metamodel-driven and syntax-agnostic approach of ISO 20022 series, interoperability is ensured at the conceptual level of the metamodel specified in ISO 20022-1, rather than at the physical level of syntaxes specified in ISO 20022-4 and ISO 20022-8. In this document, "schema" refers to the "SyntaxMessageScheme" defined in ISO 20022-1. However, for ease of reading, this document will hereafter refer to it as "schema" which is a general term for design documents that define data structures. The metaclass “MessageDefinition” that is described in ISO 20022-1:2026, Figure 13 is the target of the transformation specified in this document, but the metaclass “MessageChoreography” is not. In other words, this document is only the rules for the syntax of the data representation language. For example, Application Programming Interface (API) specific aspects are outside the scope of this document. Regarding the concept of conformance to this document, see Annex B.
- Standard25 pagesEnglish languagesale 15% off
This document defines a scalable, methodical process to ensure business concept model interoperability and logical model alignment and reverse engineering. This document provides guidance on conceptual interoperability and reverse engineering to explain how to extract relevant information from existing IndustryMessageSet, proprietary MessageSet or business model in order to prepare the submission to the ISO 20022 Registration Authority of equivalent, ISO 20022 conformant BusinessTransactions, BusinessComponents (including BusinessElements and Constraints) and MessageSets. This document describes the activities of ISO 20022 conceptual interoperability and reverse engineering from the point of view of the user who wants to verify that the business functionality, covered by their own IndustryMessageSet, proprietary MessageSets or business model, is covered by ISO 20022 conformant BusinessTransactions, BusinessComponents (including BusinessElements and Constraints) and MessageSets.
- Standard39 pagesEnglish languagesale 15% off
This document describes the modelling workflow, complementing ISO 20022-1 and ISO 20022-2. The modelling workflow describes the required steps a modeller follows in order to develop and maintain standardized BusinessTransactions and InterfaceDefinitions/MessageSets. This document does not describe the permissible artefacts and/or documents to be submitted to the Registration Authority (this information is contained in ISO 20022-7). Examples are provided only to illustrate the modelling methodology and are not normative.
- Standard27 pagesEnglish languagesale 15% off
This document specifies: the overall description of the modelling approach; the overall description of the ISO 20022 Repository (hereby referred to as Repository) contents; a high-level description of the input to be accepted by the Registration Authority to feed/modify the Repository’s DataDictionary and BusinessProcessCatalogue; a high-level description of the Repository output to be made publicly available by the Registration Authority. BusinessTransactions and MessageSets Conforming with ISO 20022 series can be used for electronic data interchange amongst any industry participants (financial and others), independently of any specific communication network. Network-dependent rules, such as message acknowledgement and message protection, are beyond the scope of the ISO 20022 series.
- Standard154 pagesEnglish languagesale 15% off
This document complements the ISO 20022 Metamodel, as specified in ISO 20022-1, with the XML syntax transformation rules to be applied by the ISO 20022 Registration Authority in order to translate an ISO 20022 compliant MessageDefinition into an XML Schema for the description and validation of XML Messages. It specifies the transformation rules from the Logical to the Physical level. It is a deterministic transformation, meaning that the resulting XML Schema is completely predictable for a given MessageDefinition. There is neither manual input to the transformation itself nor manual adjustment to the result of the transformation.
- Standard28 pagesEnglish languagesale 15% off
This document specifies requirements for and gives guidance on the development, embedding, communication, validation and verification of sustainable finance products and services (SFPS). It addresses the product and service areas of lending, asset management, insurance, payment accounts and digital assets. This document is applicable to any organization that intends to provide or is providing SFPS with an integration of defined environmental, social and governance (ESG) aspects and proof of intended impacts. It can be used for aligning existing SFPS or designing new ones. This document enables organizations to define, embed, communicate, attribute and effectively evaluate SFPS. It further enables successful marketing and documenting of SFPS objectives, properties and impacts, as well as validation and verification.
- Technical specification27 pagesEnglish languagesale 15% off
This document provides an overview of regulatory, business and best practice risk mitigation specifications that apply to the implementation, operation and governance of natural person identifier (NPI) policies, procedures and mechanisms necessary to support the lifecycle of all NPIs. The purpose of this document is to provide the basis for the development of one or more international standards related to the safe creation, use and management of NPIs with maximum global interoperability. For the structure of the NPI, see ISO 24366. For reference, ISO 24366 specifies a machine-readable, unambiguous NPI and the relevant reference data to uniquely identify the natural person relevant to any financial transaction rather than the personal identifying information.
- Technical report103 pagesEnglish languagesale 15% off
This document defines the data elements included in the registry record and used to establish the 1:1 relationship between a digital token and the identifier assigned according to the method in ISO 24165-1.
- Standard18 pagesEnglish languagesale 15% off
This document defines the assignment and generation of a random, unique, fixed-length identifier for digital tokens in response to a request for registration that conforms to specified application guidelines (see also ISO 24165-2).
- Standard8 pagesEnglish languagesale 15% off
This document is concerned with the representation of the ISO 20022 e-Repository contents in RDF and OWL by developing a case study around the ISO 20022 auth.016 sample message (hereafter simply referred to as “auth.016”). This includes: a) transformation of the sample message into an RDF instance graph; b) demonstrating a set of SPARQL rules that transform the auth.016 message into a FIX TradeCaptureReport(35=AE) message (hereafter simply referred to as “FIX AE”); c) expressing the metamodel, business components and message components exactly with a custom RDF vocabulary; d) representing those schemas as OWL schemas using OWL vocabulary when possible and annotation properties otherwise; e) creating instance graphs for the auth.016 sample messaging using the vocabulary of the business components and message components. This document also discusses the choices that arise in structuring RDF documents equivalent to documents in XML, and FIX Tag-Value format balancing considerations such as preserving the order of parts of the message versus creating graphs that are suitable for RDFS and OWL inference.
- Technical report45 pagesEnglish languagesale 15% off
This document provides guidelines for a security framework to address the implementation of security mechanisms in technical infrastructures designed for the provision of third-party payment (TPP) services in order to achieve the security objectives defined in ISO 23195. The security framework is intended to protect critical systems and objects within the TPP system environment, either under the direct control of the third-party payment service provider (TPPSP) or by another entity (e.g. a bank). This document is applicable to the provision of any TPP service, including: — the TPP logical structural model; — the definition of the security framework; — the design principles, responsibilities and functional recommendations to support the security mechanism; — guidelines for applying the security framework defined in this document.
- Technical specification24 pagesEnglish languagesale 15% off
This document provides guidelines on privacy for fintech services. It identifies all relevant business models and roles in consumer-to-business relations and business-to-business relations, as well as privacy risks and privacy requirements, which are related to fintech services. It provides specific privacy controls for fintech services to address privacy risks. This document is based on the principles from ISO/IEC 29100, ISO/IEC 27701, and ISO/IEC 29184, the privacy impact assessment framework described in ISO/IEC 29134, and the risk management guideline described in ISO 31000. It also provides guidelines focusing on a set of privacy requirements for each stakeholder. This document can be applicable to all kinds of organizations such as regulators, institutions, service providers and product providers in the fintech service environment.
- Standard30 pagesEnglish languagesale 15% off
This document specifies rules for an international method for building financial instrument short names (FISNs) for any kind of financial or referential instrument within a defined structure. Financial or referential instruments include, but are not limited to, those described by ISO 10962. This document is applicable to any application in the trading and administration of financial or referential instruments in the financial services. The FISN code takes into account the need for human-readability as well as interoperability with existing standards and systems.
- Standard15 pagesEnglish languagesale 15% off
This document specifies the use of the legal entity identifier (LEI) code, represented in ISO 17442-1, in authentic chained data container (ACDC) credentials.
- Standard4 pagesEnglish languagesale 15% off
This document provides an overview, risk assessment, minimum security requirements and extended security guidelines for code-scanning payment in which the payer uses a mobile device to operate the payment transaction. This document is applicable to cases where the payment code is used to initiate a mobile payment and presented by either the payer or the payee. The following is excluded from the scope of this document: — details of payer and payee onboarding; — details of the supporting payment infrastructure, as described in 5.1.
- Standard30 pagesEnglish languagesale 15% off
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 an acceptable security framework for the issuance and management of digital currencies using cryptographic mechanisms standardized by ISO/TC 68/SC 2 and other references. This document proposes a framework approach based on standards for mitigating vulnerabilities for digital currency systems. The objective is that security aspects are integrated by design and not added afterwards as an extra processing layer that needs to accommodate legacy infrastructures.
- Technical specification14 pagesEnglish languagesale 15% off
This document specifies the security framework for using biometrics for authentication of customers in financial services, focusing exclusively on retail payments. It introduces the most common types of biometric technologies and addresses issues concerning their application. This document also describes representative architectures for the implementation of biometric authentication and associated minimum control objectives. The following are within the scope of this document: — use of biometrics for the purpose of: — verification of a claimed identity; — identification of an individual; — biometric authentication threats, vulnerabilities and controls; — validation of credentials presented at enrolment to support authentication; — management of biometric information across its life cycle, comprising enrolment, transmission and storage, verification, identification and termination processes; — security requirements for hardware used in conjunction with biometric capture and biometric data processing; — biometric authentication architectures and associated security requirements. The following are not within the scope of this document: — detailed specifications for data collection, feature extraction and comparison of biometric data and the biometric decision-making process; — use of biometric technology for non-financial transaction applications, such as physical or logical system access control.
- Standard65 pagesEnglish languagesale 15% off
This document specifies a concrete REST webservice API description of the processes and data (see
EN 17419-1:2020 for more information) as an OpenAPI definition specified by the OpenAPI specification.
- Technical report102 pagesEnglish languagee-Library read for1 day
This document defines code values used to enable the classification of merchants into specific categories based on the type of business, trade or services supplied. Values are specified only for those merchant categories that are generally expected to originate retail financial transactions. It is not within the scope of this document to mandate the use of merchant category codes in any given situation.
- Standard2 pagesEnglish languagesale 15% off
SIGNIFICANCE AND USE
5.1 The schedule beta (βs) approach produces informational elements: Overall (or composite) schedule beta (βs), schedule beta upside (βs+), and schedule beta downside (βs–)—representing the quantitative components, and the qualitative insight (“early warning”) into the propensity for directional schedule performance for individual schedule participants.
5.1.1 The quantitative component of schedule beta (βs) (inclusive of the upside and downside subvariants) is an index value that depicts schedule participant’s magnitude and direction of movement as compared to the overall project at an assigned value of 1.0, for example, a βs = +2.5 connotes performance of a schedule participant that moves in the same direction as the collection of completed projects at a rate of 2.5 units (schedule days) for each single unit (schedule day) experienced at the overall project level.
5.1.2 The qualitative component of schedule beta (βs) (inclusive of the upside and downside subvariants) provides insight as a cautionary and predictive signal depicting the ability for an individual schedule participant to perform in-keeping with the initially-established as-planned schedule duration(s).
5.2 Schedule beta (βs) also depicts the overall status or health (performing well or not) of a market sector, location and/or trade. Consistent larger schedule beta (βs) values are indicative of external elements (risks) impacting all participants sharing common attribute(s) (that is, trade, location, market sector, etc.).
5.3 Schedule beta (βs) measures current schedule participant performance. As a rolling value (for example, calculated for projects completed during the two most recently completed full calendar years), it depicts the schedule performance ability of the schedule participant. See Note 1.
Note 1: Schedule Data Source and Usage—Schedule beta (βs) (inclusive of the upside and downside subvariants) utilizes schedule data from any schedule calculation method that depicts individ...
SCOPE
1.1 This guide covers schedule beta (βs), which measures construction project participant schedule performance versus that of the overall completed project and is based on beta (β) from financial portfolio theory for measuring the correlation between individual stock performance and that of the overall stock market.2 By correlating the delta of actual activity performance (“as-built”) minus that originally scheduled (“as-planned”) to the delta of as-built minus as-planned for the overall completed project for a participant’s collection of projects over a specified period of time, a schedule performance index is established in a similar manner as the aforementioned beta (β) of an individual stock.
1.2 Schedule beta (βs) measures, as a unitless index value, schedule participant (“subcontractor’s”) performance—ahead or behind—as-planned duration as correlated to its respective overall project’s schedule performance.
1.3 Schedule beta (βs) is measured with input from at least two (2) independent (mutually exclusive) projects that have reached completion, within the defined period of observation.
1.4 Schedule beta (βs) is measured across a standard predetermined period of time, in similar fashion to that of the insurance industry’s experience modification rate’s (EMR) most recent two (2) complete calendar years within the past thirty-six (36) months.
1.5 Schedule beta (βs) evaluates schedule participant’s (“subcontractor’s”) most recent performance, not its complete history, such that is it indicative of current performance and contemporary influences—market, geographic, industry trade, etc.
1.6 This standard does not purport to address all of the safety concerns, if any, associated with its use. It is the responsibility of the user of this standard to establish appropriate safety, health, and environmental practices and determine the applicability of regulatory limitations prior to use.
1.7 This internation...
- Guide8 pagesEnglish language
This document specifies a concrete REST webservice API description of the processes and data (see
EN 17419-1:2020 for more information) as an OpenAPI definition specified by the OpenAPI specification.
- Technical report102 pagesEnglish languagee-Library read for1 day
This document examines semantic enrichment to support the maintenance of the ISO 20022 conceptual model. It reports on existing and proposed practices to enrich a model: — in a repository, annotating repository concepts with metadata using semantic markup or constraints; — outside a repository, using references to repository concepts, such as the provenance of changes.
- Technical report12 pagesEnglish languagesale 15% off
This document discusses the modes, related mainstream technologies, logical models, physical implementation models, data management (data storage and data security) and service quality control used in the reference data distribution in financial services. This document applies to the reference data distribution and transmission processes in financial services.
- Technical report15 pagesEnglish languagesale 15% off
This document provides guidelines for customer identification in mobile financial services (MFS), including: — a general framework of customer identification for MFS; — the multi-dimensional overall identity assurance level (AL) of an MFS customer and its evaluation criteria; — security and privacy considerations. This document also contains annexes which demonstrate how to apply the ALs in practice, through (e)KYC use cases in different regions, for example. This document is applicable to various kinds of MFS providers, including but not limited to commercial banks and third-party payment service providers. This document is applicable to identifying natural persons. Identifying legal entities, known as (e)KYB, is out of the scope of this document.
- Standard23 pagesEnglish languagesale 15% off
This document provides best practices for writing a banking products or services (BPoS) handbook. It is applicable to any providers of banking products or services (BPoSP) that issue and operate BPoS. NOTE 1 A BPoS handbook is edited by either product managers or personnel in charge of key elements mentioned in this document, based on their role and responsibility within the BPoSP. NOTE 2 Whether ISO 21586 has been formally introduced, this document is useful as existing BPoS contain the key elements listed in ISO 21586.
- Technical report15 pagesEnglish languagesale 15% off
This document gives guidance to organizations on the application of overarching sustainability principles, practices and terminology for financing activities. It addresses what is material from the perspective of the organization and of its stakeholders. This document is applicable to all organizations active in the financial sector, including, but not limited to, direct lenders and investors, asset managers and service providers. Beyond financial institutions and intermediaries, this document can be used by other parties in the financial sector such as providers or recipients of sustainable finance, governmental organizations, public and private sector institutions, business entities, industry associations, financial market regulators, and supervisory and control bodies.
- Standard26 pagesEnglish languagesale 15% off
This document reports on a study to map messages defined using FIX Orchestra into the ISO 20022 model.
- Technical report6 pagesEnglish languagesale 15% off
This document establishes a framework and outlines a process to identify criteria for environmental impacts and performance to take into account when considering projects, assets and activities seeking finance. This document also gives guidance on assessing the risks and opportunities that can arise in applying environmental criteria to projects, assets and activities. It is applicable to parties seeking finance, providing finance or other interested parties.
- Standard39 pagesEnglish languagesale 15% off
- Standard44 pagesFrench languagesale 15% off
This document defines a taxonomy of eligible investment categories for designation as green debt instruments, including bonds and loans. This document categorizes economic sectors and establishes criteria for determining the eligibility of projects, assets and supporting expenditures. It provides guidance on adaptation by sector in Annex A. It provides examples of thresholds and exclusions in Annex B.
- Standard128 pagesEnglish languagesale 15% off
- Standard151 pagesFrench languagesale 15% off
This document provides a set of mandatory and optional conformity tests applicable to all versions of the FIX session layer standard.
- Standard15 pagesEnglish languagesale 15% off
This document specifies the elements and structure of a universal identifier code, the business identifier code (BIC), for financial and non-financial institutions, for which such an international identifier is required to facilitate automated processing of information for financial services. The BIC is used for addressing messages, routing business transactions and identifying business parties. This document applies to organizations and excludes individual persons.
- Standard5 pagesEnglish languagesale 15% off
This document provides the normative specification of the FIX session layer standard and its session profiles.
- Standard79 pagesEnglish languagesale 15% off
This document provides the normative specification of the FIX tagvalue encoding, which is one of the possible syntaxes for FIX messages.
- Standard17 pagesEnglish languagesale 15% off
This document specifies an unambiguous scheme to list official organizational roles by jurisdiction in a standard way. It is not the purpose of this document to compare or align official organizational roles across different countries or jurisdictions, so as not to limit the usage or relevance of this document. To understand the powers associated with each official organizational role, users of this document can consult applicable regulation or legislation, documents of the legal entity in which the official organizational role exists and procedures specific to each organizational entity.
- Standard4 pagesEnglish languagesale 15% off
SIGNIFICANCE AND USE
4.1 This practice establishes expected outcomes associated with an asset management system.
4.2 Understand the difference between performance standards and design standards—these are primarily performance statements versus design statements. What is being measured is achievement, not process.
4.3 This practice encourages an inclusive understanding and communication of the outcomes associated with an asset management system. As additional standards are added, comparisons on this basis to other asset management systems can be further enabled.
4.4 This practice, in combination with Practice E2279, should provide an enhanced basis for making decisions surrounding both assets and asset management systems.
4.5 This practice is intended to foster and enable additional standard practices related to or based on the terms and concepts in the outcomes and outcome components. In particular, this practice may suggest a standard for personal and management skills useful in efforts to achieve these outcomes.
4.6 This practice is to evaluate how robust the asset management system is, and guide future corrections and improvements.
SCOPE
1.1 This practice describes expected outcomes associated with an asset management system. It is a measure of achievement rather than process and is performance oriented rather than design oriented.
1.2 Outcomes are defined as information, events, objects, or states of being produced as a result or consequence of an objective, plan, process, accident, effort, or other similar action or occurrence and can be expressed in a quantitative or qualitative manner.
1.3 An output measure is the tabulation, calculation, or recording of activity or effort and can be expressed in a quantitative or qualitative manner. For example, an output is driving 100 mph; an outcome is arriving safely.
1.4 An outcome measure is an assessment of the results of a program activity compared to its intended purpose. This practice assumes that inputs are correlated to known or declared outputs of the system or system component being assessed.
1.5 Consistent with Practice E2452 (EMPM), these outcomes are grouped into process management outcomes and operational outcomes.
1.5.1 Although they may be directly related, strategies and tactics should not be confused with outcomes. Strategies are long-term plans of action designed to achieve a particular goal. Tactics are maneuvers or actions calculated to achieve some end. For example, increasing exercise is a strategy to attain the goal or outcome of fitness. Running is a supporting tactic to achieve the goal or outcome of fitness. Other tactics or groups of tactics may achieve the same outcome. On the other hand, as the definition of outcome indicates, tactics are not required for attaining outcomes. For example, fitness may be an unplanned result of a job requiring physical exertion.
1.6 This practice describes the outcomes at a high level, with limited discussion of each outcome or components of each outcome. The intent is to provide a framework for current and potential additional standards. A cross reference relating current standards to the outcomes is provided in Section 5.
1.7 The outcomes further described in Section 5 are listed in the following:
1.7.1 Process Management Outcomes:
1.7.1.1 Outcome 1—Mission Support
1.7.1.2 Outcome 2—Accounting and Accountability
1.7.1.3 Outcome 3—Information Management
1.7.1.4 Outcome 4—Planning
1.7.1.5 Outcome 5—Relationships
1.7.2 Operational Outcomes:
1.7.2.1 Outcome 6—Asset Functionality for Intended Purpose
1.7.2.2 Outcome 7—Resource Optimization
1.7.2.3 Outcome 8—Asset Visibility
1.7.2.4 Outcome 9—Safety and Security
1.7.2.5 Outcome 10—Installation, Movement, and Storage
1.8 In Section 5, a rating scale is provided to quantify in a uniform manner achievement of outcomes and outcome components.
1.9 This practice, in combination with Practice E2279,...
- Standard11 pagesEnglish language
- Standard11 pagesEnglish language
This document specifies the elements of an unambiguous scheme to identify over-the-counter (OTC) derivative products that are reportable to trade repositories, in particular: — the structure and format of the unique product identifier (UPI) code; — the minimum data elements of the UPI reference data library, together with their allowable values. At a minimum, the UPI code is applicable to OTC derivative instruments falling under the following categories of the classification of financial instruments (see ISO 10962): — swaps (S); — forwards (J); — non-listed and complex listed options (H); — others (miscellaneous) (M).
- Standard8 pagesEnglish languagesale 15% off
- Standard8 pagesEnglish languagesale 15% off
This document specifies a machine-readable, unambiguous natural person identifier (NPI) and the relevant reference data to uniquely identify the natural person relevant to any financial transaction rather than the personal identifying information.
- Standard13 pagesEnglish languagesale 15% off
- Standard13 pagesEnglish languagesale 15% off
This document specifies requirements for verification bodies performing verification of claims of conformity to ISO 14030-1 or ISO 14030-2 and to ISO 14030-3 or a suitable substitute taxonomy. Conformity to the requirements of this document is mandatory for the verification of statements made by green debt issuers, borrowers and lenders that claim that their products conform to the ISO 14030 series. This document specifies requirements for the validation of claims of eligibility made in conformity to ISO 14030-1:2021, 5.4, ISO 14030-2:2021, 6.3, and ISO 14030-2:2021, 7.3. This document also establishes requirements for the optional use of third-party marks of conformity.
- Standard12 pagesEnglish languagesale 15% off
- Standard12 pagesEnglish languagesale 15% off
- Standard12 pagesFrench languagesale 15% off
- Standard12 pagesFrench languagesale 15% off
This document establishes principles, specifies requirements and gives guidelines: for designating bonds which finance eligible projects, assets and supporting expenditures as “green”; for managing and reporting on the use of proceeds; for defining, monitoring and reporting on their environmental impacts; for reporting to interested parties; for validation and verification. This document is applicable to any issuer of bonds.
- Standard15 pagesEnglish languagesale 15% off
- Standard15 pagesFrench languagesale 15% off
This document establishes principles, specifies requirements and gives guidelines: for designating as “green” loans which finance eligible projects, assets and supporting expenditures; for managing and reporting on the use of proceeds; for defining, monitoring and reporting on the environmental impacts; for reporting to interested parties; for validation and verification. This document is applicable to any borrower seeking financing by way of a green loan for eligible green projects, assets and supporting expenditures. It is also applicable to lenders.
- Standard15 pagesEnglish languagesale 15% off
- Standard15 pagesEnglish languagesale 15% off
- Standard15 pagesFrench languagesale 15% off
- Standard15 pagesFrench languagesale 15% off
This document provides a non-exhaustive list of relevant basic concepts, key initiatives and terms that are in common use in the global community of sustainable finance, and have been identified by ISO/TC 322 as helpful to facilitate a greater understanding of the topics suggested by sustainable finance practitioners, including but not limited to: financial regulators, development and commercial banks, asset managers, investors, international initiatives and researchers. The terms included in this document have been selected because they are: widely accepted and used in financial markets; sourced from supranational organization(s) or initiative(s), or national regulatory authorities; NOTE With priority given to the source with the larger geographic coverage. likely to be used in documents from ISO/TC 322 and other related International Standards; of international prevalence and interest.
- Technical report35 pagesEnglish languagesale 15% off
- Technical report35 pagesEnglish languagesale 15% off
- Technical report33 pagesFrench languagesale 15% off
- Technical report33 pagesFrench languagesale 15% off
This document defines the Data Point Methodology for the creation of Data Point Models in the context of European supervisory reporting. Data Point Models are published by a European supervisory authority. To reflect the defined structures in a machine-readable form, they can be accompanied by an XBRL taxonomy. It is also possible to extend the described methodology to other environments.
- Standard18 pagesEnglish languagesale 15% off
- Standard18 pagesEnglish languagesale 15% off
- 1 (current)
- 2
- 3
- 4
- 5