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
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.
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 languagesale 10% offe-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 languagesale 10% offe-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 languagesale 10% offe-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
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 languagesale 10% offe-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 the normative specification of the FIX session layer standard and its session profiles.
- Standard79 pagesEnglish 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 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
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
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
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.
- Standard16 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 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 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 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 report33 pagesFrench languagesale 15% off
This document provides guidelines for data point modelling for supervising experts. The main body consists of four sections. The interrogative form helps in choosing which section may best answer your question and lead you to a good understanding of the subject matter. After this first introductory section and the section containing terms and definitions, the main part starts to provide basic knowledge about different types of data models and data modelling approaches. The first and the second sections provide an overview of data models in general, in contrast to the third section that highlights the necessity of data modelling for supervisory data. This third section draws on the objectives and background information of the preceding sections. Furthermore, a paragraph classifies the Data Point Model introduced by the Eurofiling Initiative and elaborated by EIOPA and EBA, where many new terms related to DPM are introduced. Another paragraph explains the areas of application for the DPM. The third section concludes with a paragraph introducing a subset of the technical constrains that need to be considered in the creation process of the DPM. The fourth section gives step-by-step instructions on how to create a DPM. The paper concludes with remarks on the progress achieved so far, and provides an outlook on the software that is being developed at the moment to support you during the creation process.
- Standard36 pagesEnglish 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
This document aims to provide an introduction to the topic of creating a conceptual model for storing multidimensional data which is received as XBRL instances that follow the rules defined by European taxonomies published by the European Banking Authority (EBA) or by the European Insurance and Occupational Pensions Authority (EIOPA).
- Standard52 pagesEnglish languagesale 15% off
This document defines a common terminology to be used in the context of third-party payment (TPP). Next, it establishes two logical structural models in which the assets to be protected are clarified. Finally, it specifies security objectives based on the analysis of the logical structural models and the interaction of the assets affected by threats, organizational security policies and assumptions. These security objectives are set out in order to counter the threats resulting from the intermediary nature of TPPSPs offering payment services compared with simpler payment models where the payer and the payee directly interact with their respective account servicing payment service provider (ASPSP). This document assumes that TPP-centric payments rely on the use of TPPSP credentials and the corresponding certified processes for issuance, distribution and renewal purposes. However, security objectives for such processes are out of the scope of this document. NOTE This document is based on the methodology specified in the ISO/IEC 15408 series. Therefore, the security matters that do not belong to the TOE are dealt with as assumptions, such as the security required by an information system that provides TPP services and the security of communication channels between the entities participating in a TPP business.
- Standard40 pagesEnglish languagesale 15% off
This document defines the process and the structure of the transfer of electronic documents, and facilitates the transfer of electronic documents between stakeholders in the insurance industry.
- Standard65 pagesEnglish languagesale 10% offe-Library read for1 day
This document defines and describes the structure for the codes for an internationally valid system to classify financial instruments. The classification system applies to financial instruments negotiated internationally as well as to domestic instruments. The term “financial instruments” refers not only to classical securities and derivatives but also covers the innovative financial products that have emerged in different markets (a trend that is expected to continue in the future). This document is intended for use in any application in the trading and administration of financial instruments in the international securities business. Insofar as the trading and administration of securities do not affect other countries, the application of this document remains at the discretion of the responsible national bodies, such as stock exchanges, banks, brokers, regulatory bodies and other institutions active in the securities field. In principle, the CFI code reflects characteristics that are defined when a financial instrument is issued and that remain unchanged during its entire lifetime. However, a few events that can lead to a new CFI code for the same instrument are anticipated, such as the changing of voting rights or ownership restrictions by a stockholders' meeting.
- Standard9 pagesEnglish languagesale 15% off
- Standard9 pagesEnglish languagesale 15% off
- Standard9 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.
- Standard43 pagesEnglish languagesale 15% off
- Standard47 pagesFrench languagesale 15% off
This document provides a uniform structure for the identification of financial instruments as well as referential instruments (see Annex A) using a unique identification code and associated minimum descriptive data (see Annex B).
- Standard15 pagesEnglish languagesale 15% off
- Standard15 pagesEnglish languagesale 15% off
This document defines the process and the structure of the transfer of electronic documents, and facilitates the transfer of electronic documents between stakeholders in the insurance industry.
- Standard65 pagesEnglish languagesale 10% offe-Library read for1 day
This document describes the Registration Authority (RA) responsible for the registry of IBAN formats that conform with ISO 13616-1, the procedures for registering IBAN formats that conform with the ISO 13616 series and the structure of the registry.
- Standard3 pagesEnglish languagesale 15% off
This document specifies the elements of an international bank account number (IBAN) used to facilitate the processing of data internationally in data interchange, in financial environments as well as within and between other industries. The IBAN is designed for automated processing but can also be used conveniently in other media interchange when appropriate (e.g. paper document exchange). This document does not specify internal procedures, file organization techniques, storage media or languages to be used in its implementation, nor is it designed to facilitate the routing of messages within a network. It is applicable to the textual data which might be conveyed through a system (network).
- Standard8 pagesEnglish languagesale 15% off
This document specifies how to describe the characteristics of banking products or services (BPoS) from a customer's perspective. Characteristics of a BPoS can be observed from different facets, called key elements, which are divided into three groups: required, optional or voluntary elements. This document elaborates on the purpose, content and description approach for the required and optional key elements. Six levels of conformity are described in this document which are intended to allow a customer to assess the coverage of key elements in a BPoS. The logical and physical formats to express key elements are also defined. This document excludes requirements of a BPoS itself and specific value ranges of any key element are out of the scope. This document guides the provider of BPoS in describing their products or services with the intent to help customers understand or compare specific BPoS. It is not applicable to describing securities or insurance-related products or services. BPoS can be issued by banks and other institutions.
- Standard51 pagesEnglish languagesale 15% off
This document specifies the minimum elements of an unambiguous legal entity identifier (LEI) scheme to identify the legal entities relevant to any financial transaction. It is applicable to "legal entities", which include, but are not limited to, unique parties that are legally or financially responsible for the performance of financial transactions or have the legal right in their jurisdiction to enter independently into legal contracts, regardless of whether they are incorporated or constituted in some other way (e.g. trust, partnership, contractual). It includes governmental organizations, supranationals and individuals when acting in a business capacity[1], but excludes natural persons. It also includes international branches as defined in 3.5. The LEI is designed for automated processing. It can also be conveniently used in other media interchange when appropriate (e.g. paper document exchange). NOTE Examples of eligible legal entities include, without limitation: — all financial intermediaries; — banks and finance companies; — international branches; — all entities that issue equity, debt or other securities for other capital structures; — all entities listed on an exchange; — all entities that trade financial instruments or are otherwise parties to financial transactions, including business entities, pension funds and investment vehicles such as collective investment funds (at umbrella and sub-fund level) and other special purpose vehicles that have a legal form; — all entities under the purview of a financial regulator and their affiliates, subsidiaries and holding companies; — sole traders (as an example of individuals acting in a business capacity); — counterparties to financial transactions. [1] As stated by the LEI Regulatory Oversight Committee on 30 September 2015.
- Standard8 pagesEnglish languagesale 15% off