Ga verder naar contentGa verder naar content en skip ook inhoudsopgave
In- en Uitvoer
Home

Commission Implementing Regulation (EU) No 1247/2012 of 19 December 2012 laying down implementing technical standards with regard to the format and frequency of trade reports to trade repositories according to Regulation (EU) No 648/2012 of the European Parliament and of the Council on OTC derivatives, central counterparties and trade repositories Text with EEA relevance

Commission Implementing Regulation (EU) No 1247/2012 of 19 December 2012 laying down implementing technical standards with regard to the format and frequency of trade reports to trade repositories according to Regulation (EU) No 648/2012 of the European Parliament and of the Council on OTC derivatives, central counterparties and trade repositories Text with EEA relevance

THE EUROPEAN COMMISSION,

Having regard to the Treaty on the Functioning of the European Union,

Having regard to the opinion of the European Central Bank(1),

Having regard to Regulation (EU) No 648/2012 of the European Parliament and of the Council of 4 July 2012 on OTC derivatives, central counterparties and trade repositories(2) and in particular Article 9(6) thereof,

Whereas:

  1. To avoid inconsistencies, all data sent to trade repositories under Article 9 of Regulation (EU) No 648/2012 should follow the same rules, standards and formats for all trade repositories, all counterparties and all types of derivatives. A unique data set should therefore be used for describing a derivatives trade.

  2. Since OTC derivatives are typically neither uniquely identifiable by existing codes which are widely used in financial markets, such as the International Securities Identification Numbers (ISIN), nor describable by using the ISO Classification of Financial Instruments (CFI) code, a new and universal method of identification has to be developed. If a unique product identifier is available and follows the principles of uniqueness, neutrality, reliability, open source, scalability, accessibility, has a reasonable cost basis, is offered under an appropriate governance framework and is adopted for use in the Union, it should be used. If a unique product identifier meeting these requirements is not available, an interim taxonomy should be used.

  3. The underlying should be identified by using a single identifier, however there is currently no market wide standardised code to identify the underlying within a basket. Counterparties should therefore be required to indicate at least that the underlying is a basket and use ISINs for standardised indices where possible.

  4. To ensure consistency, all parties to a derivatives contract should be identified by a unique code. A global legal entity identifier or an interim entity identifier, to be defined under a governance framework which is compatible with the FSB recommendations on data requirements and is adopted for use in the Union, should be used to identify all financial and non-financial counterparties, brokers, central counterparties, and beneficiaries once available, in particular to ensure consistency with the Committee on Payment and Settlement Systems (CPSS) and International Organisation of Securities Commissions (IOSCO) report on OTC Derivatives Data Reporting and Aggregation Requirements that describes legal entity identifiers as a tool for data aggregation. In the case of agency trades, the beneficiaries should be identified as the individual or entity on whose behalf the contract was concluded.

  5. The approach used in third countries and also taken by trade repositories themselves as they start their businesses should be taken into account. Therefore, to ensure a cost-effective solution for counterparties and to mitigate operational risk for trade repositories, the reporting start date should include phase-in dates for different derivative classes, beginning with the most standardised classes and subsequently extending to the other classes. The derivative contracts which were entered into before, on or after the date of entry into force of Regulation (EU) No 648/2012, that are not outstanding on or after the reporting start date, are not of major relevance for regulatory purposes. They must however be reported under Article 9(1)(a) of Regulation (EU) No 648/2012. To ensure an efficient and proportionate reporting regime in those cases and taking into account the difficulties in reconstructing data of terminated contracts, a longer deadline should be provided for such reporting.

  6. This Regulation is based on draft implementing technical standards submitted by the European Securities and Markets Authority (hereinafter ESMA) to the Commission.

  7. In accordance with Article 15 of Regulation (EU) No 1095/2010 of the European Parliament and of the Council of 24 November 2010 establishing a European Supervisory Authority (European Securities and Markets Authority)(3) ESMA has conducted open public consultations on such draft implementing technical standards, analysed the potential related costs and benefits and requested the opinion of the ESMA Securities and Markets Stakeholder Group established in accordance with Article 37 of that Regulation,

HAS ADOPTED THIS REGULATION:

Article 1 Format of derivative contract reports

The information contained in a report under Article 9 of Regulation (EU) No 648/2012 shall be provided in the format specified in the Annex to this Regulation.

Article 2 Frequency of derivative contract reports

Where provided for in Article 11(2) of Regulation (EU) No 648/2012, mark to market or mark to model valuations of contracts reported to a trade repository shall be done on a daily basis. Any other reporting elements as provided for in the Annex to this Regulation and the Annex to the delegated act with regard to regulatory technical standards specifying the minimum details of the data to be reported to trade repositories pursuant to Article 9(5) of Regulation (EU) No 648/2012 shall be reported as they occur and taking into account the time limit foreseen under Article 9 of Regulation (EU) No 648/2012, notably as regards the conclusion, modification or termination of a contract.

Article 3 Identification of counterparties and other entities

1.

A report shall use a legal entity identifier to identify:

  1. a beneficiary which is a legal person;

  2. a broking entity;

  3. a CCP;

  4. a clearing member which is a legal person;

  5. a counterparty which is a legal entity;

  6. a submitting entity.

2.

Where a legal entity identifier is not available, the report shall include an interim entity identifier as defined at the Union level which is:

  1. unique;

  2. neutral;

  3. reliable;

  4. open source;

  5. scalable;

  6. accessible;

  7. available at a reasonable cost basis;

  8. subject to an appropriate governance framework.

3.

Where neither a legal entity identifier nor an interim entity identifier is available, a report shall use a Business Identifier Code in accordance with ISO 9362 where available.

Article 4 Identification of Derivatives

1.

A report shall identify a derivative contract using a unique product identifier which is:

  1. unique;

  2. neutral;

  3. reliable

  4. open source;

  5. scalable;

  6. accessible;

  7. available at a reasonable cost basis;

  8. subject to an appropriate governance framework.

2.

Where a unique product identifier does not exist, a report shall identify a derivative contract by using the combination of the assigned ISO 6166 ISIN code or Alternative Instrument Identifier code with the corresponding ISO 10962 CFI code.

3.

Where the combination referred to in paragraph 2 is not available, the type of derivative shall be identified on the following basis:

  1. the derivative class shall be identified as one of the following:

    1. commodities;

    2. credit;

    3. foreign exchange;

    4. equity;

    5. interest rate;

    6. other.

  2. the derivative type shall be identified as one of the following:

    1. contracts for difference;

    2. forward rate agreements

    3. forwards;

    4. futures;

    5. options;

    6. swaps;

    7. other.

  3. in the case of derivatives not falling into a specific derivative class or derivative type, the report shall be made on the basis of the derivative class or derivative type that the counterparties agree the derivative contract most closely resembles.

Article 5 Reporting start date

Article 6 Entry into force

ANNEX