European Union: New ESMA Guidance On EMIR Transaction Reporting

ESMA published a revised set of Q&As on EMIR on 11 February, the eve of the EMIR transaction reporting go-live date. They include updates and new guidance in several areas, including transaction reporting.

This Client Alert pulls together the relevant new/modified sections from the latest Q&As (available at: applicable to the 12 February EMIR reporting start date. We have reproduced those sections below with added commentary. The aim is to assist those who will need to ensure that their reporting set-up incorporates this new guidance to focus on the main points of relevance to them.

Our commentary is in dark red for ease of reference. Pages 69 to 71 of the Q&As also include transaction reporting scenarios applicable to OTC trades. We have not reproduced them here.

There is a statement on ESMA's website mentioning the new Q&As saying that "ESMA appreciates that it will require a certain amount of time for both reporting firms and TRs to properly incorporate this further guidance." See

  • TR Question 4(b): Reporting of outstanding positions following the entry into force of EMIR (Backloading)

Commentary: This is a modification as opposed to a new question and reflects a clarification of previous guidance. It is reflective of what we and many others in the market had understood to be the position in any event. Nevertheless, it provides an additional degree of comfort that this common understanding was correct. The underlined language reflects the modification.

Q: Should information on valuation and collateral be reported for contracts entered into from 16 August 2012?

A: OTC derivatives transactions that are still outstanding on the date when the reporting obligation for this information comes into force (i.e. 180 days after the reporting start date) will need to include the information on valuation and collateral as from the date of the reporting obligation and not for all the days from 16 August 2012 to the date of the application of the reporting obligation pursuant to Article 5 of 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. Similarly, contracts that were terminated before the reporting obligation starts applying should not include the information on collateral and valuation.

  • TR Question 10(d) Codes: LEI (Legal Entity Identifier)

Commentary: This may make it difficult for European entities to enter into reportable EMIR trades with counterparties in jurisdictions where local law or regulation prevents information about that counterparty from being reported.

Q: If a counterparty is established in a third country whose legal framework prevents the disclosure of its identity by the European counterparty subject to the reporting obligation, how should the European counterparty fill the counterparty field?

A: Article 9(5) EMIR provides that at least the identities of the parties to the derivative contracts should be reported to trade repositories. This requirement cannot be waived. Therefore, a European counterparty dealing with counterparties that cannot be identified because of legal, regulatory or contractual impediments, would not be deemed compliant with Article 9(5) of EMIR.

  • TR Question 18 Article 9 of EMIR Reporting to TRs: UTI construction

Commentary: As a matter of practicality it seems likely that most market participants would use either method 1 or method 2 to generate a UTI (Unique Trade Identifier), but ESMA prescribes certain alphanumerical characters as pre-defined prefixes dependent upon which method is used. You may have already had similar information if, and to the extent that, you have been told this by your TR (Trade Repository), but it is worthwhile highlighting this where you will be responsible for generating UTIs as this is the first time these methods have been set out by ESMA in its guidance on trade reporting.

The use of "should be allowed to be used" in the first paragraph below suggests that it is not mandatory to use the same trade identifier where the same trade is subject to two reporting obligations in different jurisdictions. Similarly, the use of "could" in the second last sentence suggests that Unique Swap Identifiers under Dodd-Frank can be, but are not required to be, used where a trade is reportable under both regimes.

The requirement to agree which form of a Unique Trade ID they will use (i.e. which generation method) before reporting a derivative contract may lead to some consternation and last minute emails between counterparties. Taking a pragmatic approach, if parties have already entered into reporting delegation agreements or have agreed which of them will be responsible for generating the UTI, then the policy aim behind this (i.e to avoid competing methods being used) should be achieved. If an agreement gives the generating party or the delegate a wide discretion then this may suffice as agreement to abide by the decision of that generating party as to which generation method is used. As a matter of good housekeeping, parties who generate UTIs on this basis may want to inform their counterparties which method they are using and that they have decided to use it in exercise of their agreed discretion.

Q: How to construct a Unique Trade ID?

A: Commission Delegated Regulation (EU) No 148/2013 specifies that in the absence of a Trade ID agreed at the European Level, a unique code should be generated and agreed with the other counterparty (Table 2, field 8). This means that only one Trade ID should be applicable to any one derivative contract that is reported to a trade repository under EMIR and that the same Trade ID is not used for any other derivative contract. It is also acknowledged that contracts reported under EMIR rules might also be reported under the rules of other jurisdictions. Hence, the same Trade ID should be allowed to be used in both those jurisdictions for reporting the given contract in order to facilitate the reconciliation among all the data sets.

Commission Implementing Regulation (EU) No 1247/2012 specifies that the Trade ID can have up to 52 characters. Therefore a Trade ID that is less than 52 characters in length is permissible provided that it meets the other criteria laid out here. There is no requirement to pad out Trade ID values to make them 52 characters long.

As an illustration, ESMA considers that any of the methods provided in the following list of Trade ID construction would be deemed to meet the requirements for reporting under EMIR. ESMA reserves the initial three character sequences 'E00' to 'E99' inclusive for these purposes. The Trade ID should be formed by the concatenation (without separators) of the three elements in each case.

Method 1:

a. The characters 'E01'. The characters '000' will also be permitted but only for derivative contracts executed before 12 February 2015.

b. The MIC code (ISO 10383) of the applicable trading venue.

c. A unique code generated by that trading venue or by a CCP used by that trading venue to clear the derivative contract. If the CCP generates the code and if derivative contracts executed on that trading venue could be cleared by more than one CCP, then measures should be put in place to avoid different CCPs generating the same value.

Method 2:

a. The characters 'E02'.

b. The (20 character) Legal Entity Identifier of the generating entity (normally one of the parties to the trade).

c. A unique code generated by the Unique Trade ID generating entity.

Method 3:

a. The characters 'E03'.

b. A unique code generated independently by both counterparties based on the pre-agreed set of information about the trade in such a way that both counterparties will arrive at the same code and that it would be unique with respect to any other report. The two counter-parties are responsible for providing the same code. The information used should include Common Data from Table 2 of the Commission Delegated Regulation (EU) No 148/2013 and the Legal Entity Identifiers of the two counterparties.

Method 4:

Note that ESMA considers this approach as sub-optimal and therefore intends to maintain it as a possibility only for derivative contracts that have been or will be entered into before 12 February 2015:

a. The characters 'E04' or '000'.

b. An identifier of the generating entity other than the full Legal Entity Identifier (normally one of the parties to the trade).

c. A unique code generated by the Unique Trade ID generating entity.

For derivative contracts that are also reportable under the provisions of the Dodd-Frank Act, the same value as would be reported under the Dodd-Frank Act, i.e. the Unique Swap Identifier, could be used.

Counterparties should agree which form of a Unique Trade ID they will use before reporting the derivative contract. This therefore includes determining the approach that they will use to define which entity generates the Unique Trade ID.

  • TR Question 19 Article 9 of EMIR Reporting to TRs: UTI generation

Q: What criteria should be applied by the two counterparties to determine the one that would generate the Unique Trade ID?

A: ESMA would like to stress the importance of the general obligation according to which the counterparties need to agree the report's contents before submitting it to TRs. This obligation stems from the requirement of Article 9(1) of EMIR, 'counterparties and CCPs shall ensure that the details of their derivative contracts are reported without duplication' and is specified in the European Commission's Frequently Asked Questions document Section II Question 5:

At the same time, ESMA believes that there might be merits to suggest a non-binding approach that could be followed by counterparties in case of disagreement on the responsibility to generate a Unique Trade ID. This approach is suggested without prejudice to other arrangements on the generation of a Unique Trade ID that counterparties might agree on.

The generation and communication of the Unique Trade ID should occur at the earliest possible stage in the trade flow.

The following order of preference could be suggested for generation and communication of the Unique Trade ID:

  • For centrally executed and cleared trades the code could be generated either:
    • by execution venue for its member or
    • at the point of clearing by the CCP for the clearing member. Subsequently, the Unique Trade ID could be generated by the clearing member for its counterparty (e.g. MiFID investment firm).
  • For centrally confirmed and cleared trades at the point of clearing by the CCP for the clearing member.
  • For centrally confirmed but not cleared trades at the point of confirmation (by the confirmation platform).
  • For other trades, the following hierarchy could be followed:
    • Financial counterparty generating the Unique Trade ID for their non-financial counterparty;
    • Non-financial counterparty above the clearing threshold generating the Unique Trade ID for their non-financial counterparty below the clearing threshold;
    • Within the same group of entities in case of disagreement the seller generates the Unique Trade ID.

TR Question 20 Article 9 of EMIR Reporting to TRs:

Empty fields


ESMA has said it appreciates time will be required for parties to fully comply with this updated guidance. Nevertheless, if parties are able to incorporate this part of the guidance into their transaction reports at an early stage, it may save them having to go back and complete these fields in reports they have already submitted if ESMA requires all submitted reports to follow this format.

Q: Are all fields specified in the Annex of the Commission Delegated Regulation (EU) No 148/2013 mandatory?

A: In general, all fields specified in the RTS are mandatory. Nevertheless, two different instances need to be acknowledged, namely:

1. The field is not relevant for a specific type of contract/trade, for example:

  • settlement date field where the underlying is an index,
  • commodity underlying field in case of equity derivatives,
  • Domicile of the Counterparty in case of coverage by LEI.

2. The field is relevant for a given type of contract/trade, however:

a. there is a legitimate reason why the actual value of this field is not being provided at the time the report is being submitted, or

b. none of the possible values provided for in the Annex of the Commission Implementing Regulation (EU) 1247/2012 for a given field apply to the specific trade (e.g. in the case of report submitted by the CCP, field No 7 in the Table 1 Counterparty Data).

In order to enable the TRs distinguishing between the two instances above and allow them to comply with requirements of Article 19 of the Commission Delegated Regulation (EU) 150/2013 (in particular to verify the compliance of the reporting counterparty or submitting entity with the reporting requirements), a different approach should be envisaged when it comes to population of the not-relevant and relevant fields.

In the first case, since the field is not relevant for a given trade, it should be left blank.

In the second case, the mandatory relevant field should not be left blank and should include the NA value instead.

  • TR Question 21 Article 9 of EMIR Reporting to TRs: UPI taxonomy

Commentary: Although most of this is unlikely to be news to most reporting parties, it is worth bearing in mind the clarification in point 4 that proprietary classification identifiers provided by TRs should not be used to complete data fields 2 and 3 of the Common Data section of a transaction report.

Q: In the absence of a Unique Product Identifier taxonomy endorsed in Europe, what identifiers should be used for derivative contracts for which neither ISIN nor AII codes are available?

A: According to Article 4(3) of the Commission Implementing Regulation (EU) No 1247/2012 in cases where a unique product identifier does not exist and a derivative contract cannot be identified by using the combination of ISIN or AII with the corresponding CFI code, the type of derivative contract shall be identified through the Interim taxonomy on the following basis:

1. The derivative class (field No 2 in the Table 2 Common data) shall be identified as one of the following:

a. commodities;

b. credit;

c. foreign exchange;

d. equity;

e. interest rate;

f. other.

2. The derivative type (field No 3 in the Table 2 Common data) shall be identified as one of the following:

a. contract for difference;

b. forward rate agreement;

c. forwards;

d. futures

e. options;

f. swaps;

g. other.

3. In case of derivative contracts not falling into a specific derivative class or 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.

4. In the absence of UPI taxonomy endorsed in Europe, no other taxonomy, classification or code should be used to populate these fields (i.e. Fields No 2 and 3 in the Table 2 Common data). If the Trade Repository offers a proprietary classification or taxonomy it could be used to populate other additional fields provided for by the given Trade Repository, but it should not be used for population of Fields No 2 and 3 referred to above.

  • TR Question 22 Article 9 of EMIR Reporting to TRs: Venues with AII codes

Q: How to determine whether a particular contract has to be identified by the ISIN code or by the AII codes?

A: Derivative contracts traded on trading venues in the European Union and classified as the AII venues should be identified by the combination of the AII and CFI codes. The full list of such regulated markets (flagged as the AII venues in the 'Instrument Identifier' column) can be found in the MiFID Data Base (in the 'Regulated Markets' section) published on the ESMA website: Note that only the AII and CFI codes should be used for AII venues to ensure consistent reporting. For options and futures traded on MTFs the involved MTF should be consulted.

Derivative contracts traded on any other venues should be identified either by the ISIN code if available or, where ISIN code is not available, the Interim taxonomy as specified in Article 4(3) of the Commission Implementing Regulation (EU) No 1247/2012.

  • TR Question 23 Article 9 of EMIR Reporting to TRs: AII code

Q: How to populate field No 2 (Product ID 1) in the Table 2 Common Data for the AII derivative contracts?

A: Field No 2 should be populated with the Exchange Product Code assigned by the Regulated Market. At the same time field No 10 (Venue of execution) in the Table 2 Common Data should be populated with the MIC code of the venue of execution and not with 'XOFF' or 'XXXX'.

  • TR Question 24 Article 9 of EMIR Reporting to TRs: Buy/Sell indicator for swaps

Q: How should the field No 13 (Counterparty side) in the Table 1 Counterparty data be populated for the Equity, Debt and Dividend swaps?

A: As a general principal, the buyer of the Equity Swap should be the Fixed Rate Payer (the buyer is the one who receives the equity performance).
In case of Equity Swap the buyer of the Equity Swap is the one who gets the risk of the price movement of the underlying (the Fixed Rate Payer and Equity Amount Receiver). So the seller is the Equity Amount Payer and Fixed Rate Receiver.

In case of the Equity Swap with two equity legs the buyer of the Equity Swap is the one who gets the risk of the price movement of the underlying.

In case of Debt Swap the buyer of the Debt Swap is the one who gets the risk of the price movement of the bond. So the seller is the Bond Performance Amount Payer and Fixed Rate Receiver.

In case of Dividend Swap the buyer of the Dividend Swap is the one who receives the equivalent actual dividend payments, so the seller is the Dividend Payer and Fixed Rate Receiver.

  • TR Question 25 Article 9 of EMIR Reporting to TRs: Decimal values in fields No 15 and 16

Q: Are decimal values allowed in the fields No 15 (Price multiplier) and 16 (Quantity) in the Table 2 Common data?

A: Yes, the specified format of up to 10 numerical digits should be understood as also allowing for the decimal values.

  • TR Question 26 Article 9 of EMIR Reporting to TRs: Complex Contracts

Q: How the following cases should be reported:

a. A contract stemming from another contract (e.g. option on a future)

b. Trading strategies (e.g. Straddle or butterfly trades)

c. A transaction with 2 legs


a. If the first contract ceases to exist before giving rise to the second one which is materially different from the first one, the two contracts should be reported separately. Therefore, even though the two contracts are connected in the way they come into existence, they should be reported in two separate reports.

b. The two (or more) derivative contracts related to the same trading strategies should be reported separately.

c. Both legs of the contract should be reported in one report, where the combination of fields in the Annex of the Commission Delegated Regulation (EU) No 148/2013 provides for this. Otherwise, a report per leg should be submitted.

  • TR Question 27 Article 9 of EMIR 'Leg 1' and 'Leg 2' fields

Q: Which leg of the transaction should be assigned to the 'Leg 1' field and which one to the "Leg 2"?

A: As these fields are included in the Table 2 as Common data, counterparties are expected to agree a consistent approach to assigning each leg to the respective field in the report. Lack of agreement would lead to reconciliation problems at the TR level.
The obligation to agree the reports content stems from the requirement of Article 9(1) of EMIR, 'counterparties and CCPs shall ensure that the details of their derivative contracts are reported without duplication' and is specified in the European Commission's Frequently Asked Questions document Section II Question 5:

Client Alert 14-048

The content of this article is intended to provide a general guide to the subject matter. Specialist advice should be sought about your specific circumstances.

To print this article, all you need is to be registered on

Click to Login as an existing user or Register so you can print this article.

In association with
Related Topics
Related Articles
Related Video
Up-coming Events Search
Font Size:
Mondaq on Twitter
Mondaq Free Registration
Gain access to Mondaq global archive of over 375,000 articles covering 200 countries with a personalised News Alert and automatic login on this device.
Mondaq News Alert (some suggested topics and region)
Select Topics
Registration (please scroll down to set your data preferences)

Mondaq Ltd requires you to register and provide information that personally identifies you, including your content preferences, for three primary purposes (full details of Mondaqs use of your personal data can be found in our Privacy and Cookies Notice):

  • To allow you to personalize the Mondaq websites you are visiting to show content ("Content") relevant to your interests.
  • To enable features such as password reminder, news alerts, email a colleague, and linking from Mondaq (and its affiliate sites) to your website.
  • To produce demographic feedback for our content providers ("Contributors") who contribute Content for free for your use.

Mondaq hopes that our registered users will support us in maintaining our free to view business model by consenting to our use of your personal data as described below.

Mondaq has a "free to view" business model. Our services are paid for by Contributors in exchange for Mondaq providing them with access to information about who accesses their content. Once personal data is transferred to our Contributors they become a data controller of this personal data. They use it to measure the response that their articles are receiving, as a form of market research. They may also use it to provide Mondaq users with information about their products and services.

Details of each Contributor to which your personal data will be transferred is clearly stated within the Content that you access. For full details of how this Contributor will use your personal data, you should review the Contributors own Privacy Notice.

Please indicate your preference below:

Yes, I am happy to support Mondaq in maintaining its free to view business model by agreeing to allow Mondaq to share my personal data with Contributors whose Content I access
No, I do not want Mondaq to share my personal data with Contributors

Also please let us know whether you are happy to receive communications promoting products and services offered by Mondaq:

Yes, I am happy to received promotional communications from Mondaq
No, please do not send me promotional communications from Mondaq
Terms & Conditions (the Website) is owned and managed by Mondaq Ltd (Mondaq). Mondaq grants you a non-exclusive, revocable licence to access the Website and associated services, such as the Mondaq News Alerts (Services), subject to and in consideration of your compliance with the following terms and conditions of use (Terms). Your use of the Website and/or Services constitutes your agreement to the Terms. Mondaq may terminate your use of the Website and Services if you are in breach of these Terms or if Mondaq decides to terminate the licence granted hereunder for any reason whatsoever.

Use of

To Use you must be: eighteen (18) years old or over; legally capable of entering into binding contracts; and not in any way prohibited by the applicable law to enter into these Terms in the jurisdiction which you are currently located.

You may use the Website as an unregistered user, however, you are required to register as a user if you wish to read the full text of the Content or to receive the Services.

You may not modify, publish, transmit, transfer or sell, reproduce, create derivative works from, distribute, perform, link, display, or in any way exploit any of the Content, in whole or in part, except as expressly permitted in these Terms or with the prior written consent of Mondaq. You may not use electronic or other means to extract details or information from the Content. Nor shall you extract information about users or Contributors in order to offer them any services or products.

In your use of the Website and/or Services you shall: comply with all applicable laws, regulations, directives and legislations which apply to your Use of the Website and/or Services in whatever country you are physically located including without limitation any and all consumer law, export control laws and regulations; provide to us true, correct and accurate information and promptly inform us in the event that any information that you have provided to us changes or becomes inaccurate; notify Mondaq immediately of any circumstances where you have reason to believe that any Intellectual Property Rights or any other rights of any third party may have been infringed; co-operate with reasonable security or other checks or requests for information made by Mondaq from time to time; and at all times be fully liable for the breach of any of these Terms by a third party using your login details to access the Website and/or Services

however, you shall not: do anything likely to impair, interfere with or damage or cause harm or distress to any persons, or the network; do anything that will infringe any Intellectual Property Rights or other rights of Mondaq or any third party; or use the Website, Services and/or Content otherwise than in accordance with these Terms; use any trade marks or service marks of Mondaq or the Contributors, or do anything which may be seen to take unfair advantage of the reputation and goodwill of Mondaq or the Contributors, or the Website, Services and/or Content.

Mondaq reserves the right, in its sole discretion, to take any action that it deems necessary and appropriate in the event it considers that there is a breach or threatened breach of the Terms.

Mondaqs Rights and Obligations

Unless otherwise expressly set out to the contrary, nothing in these Terms shall serve to transfer from Mondaq to you, any Intellectual Property Rights owned by and/or licensed to Mondaq and all rights, title and interest in and to such Intellectual Property Rights will remain exclusively with Mondaq and/or its licensors.

Mondaq shall use its reasonable endeavours to make the Website and Services available to you at all times, but we cannot guarantee an uninterrupted and fault free service.

Mondaq reserves the right to make changes to the services and/or the Website or part thereof, from time to time, and we may add, remove, modify and/or vary any elements of features and functionalities of the Website or the services.

Mondaq also reserves the right from time to time to monitor your Use of the Website and/or services.


The Content is general information only. It is not intended to constitute legal advice or seek to be the complete and comprehensive statement of the law, nor is it intended to address your specific requirements or provide advice on which reliance should be placed. Mondaq and/or its Contributors and other suppliers make no representations about the suitability of the information contained in the Content for any purpose. All Content provided "as is" without warranty of any kind. Mondaq and/or its Contributors and other suppliers hereby exclude and disclaim all representations, warranties or guarantees with regard to the Content, including all implied warranties and conditions of merchantability, fitness for a particular purpose, title and non-infringement. To the maximum extent permitted by law, Mondaq expressly excludes all representations, warranties, obligations, and liabilities arising out of or in connection with all Content. In no event shall Mondaq and/or its respective suppliers be liable for any special, indirect or consequential damages or any damages whatsoever resulting from loss of use, data or profits, whether in an action of contract, negligence or other tortious action, arising out of or in connection with the use of the Content or performance of Mondaqs Services.


Mondaq may alter or amend these Terms by amending them on the Website. By continuing to Use the Services and/or the Website after such amendment, you will be deemed to have accepted any amendment to these Terms.

These Terms shall be governed by and construed in accordance with the laws of England and Wales and you irrevocably submit to the exclusive jurisdiction of the courts of England and Wales to settle any dispute which may arise out of or in connection with these Terms. If you live outside the United Kingdom, English law shall apply only to the extent that English law shall not deprive you of any legal protection accorded in accordance with the law of the place where you are habitually resident ("Local Law"). In the event English law deprives you of any legal protection which is accorded to you under Local Law, then these terms shall be governed by Local Law and any dispute or claim arising out of or in connection with these Terms shall be subject to the non-exclusive jurisdiction of the courts where you are habitually resident.

You may print and keep a copy of these Terms, which form the entire agreement between you and Mondaq and supersede any other communications or advertising in respect of the Service and/or the Website.

No delay in exercising or non-exercise by you and/or Mondaq of any of its rights under or in connection with these Terms shall operate as a waiver or release of each of your or Mondaqs right. Rather, any such waiver or release must be specifically granted in writing signed by the party granting it.

If any part of these Terms is held unenforceable, that part shall be enforced to the maximum extent permissible so as to give effect to the intent of the parties, and the Terms shall continue in full force and effect.

Mondaq shall not incur any liability to you on account of any loss or damage resulting from any delay or failure to perform all or any part of these Terms if such delay or failure is caused, in whole or in part, by events, occurrences, or causes beyond the control of Mondaq. Such events, occurrences or causes will include, without limitation, acts of God, strikes, lockouts, server and network failure, riots, acts of war, earthquakes, fire and explosions.

By clicking Register you state you have read and agree to our Terms and Conditions