Tag: EMIR Q&As

  • In the news: David Nowell speaks to Practice Insight

    In the news: David Nowell speaks to Practice Insight

    Our Senior Regulatory Reporting Specialist David Nowell recently spoke to Thomas Helm at Practice Insight for a special report on the accumulative impact of post-crisis reforms. In the report Thomas Helm joins the dots of transparency initiatives to reveal the bigger picture. David commented on data quality for the 124 data fields of EMIR trade reporting and the kind of errors we regularly see here at Kaizen. 

    “David Nowell says he frequently comes across errors, such as notional amounts in the “quintillions” in the Emir space, and that these errors can distort the public data aggregations. When compiling the public data aggregations we’d artificially disregard notionals above a certain level because they were obviously false, he says.

    Read the full report.         

  • ESMA updates Q&A on MiFIR and EMIR reporting

    ESMA seemingly delivered a double whammy on 4 February with the publication of Q&As for both MiFIR and EMIR data reporting. However, there’s nothing to get too excited about, although firms do need to understand the ‘clarification’ and adjust their reporting accordingly.

    Impact on MiFIR data reporting

    Bit of a damp squib. There is only one question that relates to transaction reporting (TVTIC on complex trades); the others all relate to RTS 23/MAR reference data reporting. The clarifications can be summarised as follows (italics indicate direct quote from the Q&A):

    How should the TVTIC (field 3 of RTS 22) be populated in transaction reports of a complex trade?

    Bit of a change here. Previously, firms were required to put the same TVTIC on each leg of the reported trades (if they were traded on a trading venue). New instruction is to use the TVTIC provided by trading venue for each leg of the complex trade (where the trading venue uses multiple TVTICs)

    How should Field 15 (Maturity date) of Table 3 of the Annex to RTS 23 and related MAR RTS and ITS be populated in case of trading in bonds after their originally intended maturity date?

    “For bonds that were not paid out on the originally intended maturity date (and therefore have not expired, because, for example, they defaulted), the maturity date should be set to 9999- 12-31 …until they are finally paid out, in which case the maturity date should be updated with the actual date of redemption”.

    How should field 15 (maturity date) and field 24 (expiry date) of Table 3 of the Annex to RTS 23 and related MAR RTS and ITS be populated, if these dates are non-trading dates, e.g. a weekend or a bank holiday?

    “The maturity date/expiry date defined by the issuer or the prospectus of the financial instrument should be used. No adjustment should be made to the next or previous working day for the purpose of instrument reference data reporting.”

    When should an instrument be terminated in FIRDS?

    “When field 12 (termination date) of Table 3 of the Annex to RTS 23 and related MAR RTS and ITS is initially left empty, the reporting entity is expected to fill it in when the instrument is going to be terminated. This also includes the cases when the given instrument has matured/expired, i.e. where fields 15 (maturity date) or 24 (expiry date) are applicable to the given instrument and are populated in the report.

    The termination date should be earlier than or equal to the maturity/expiry date in the cases where the maturity/expiry date is populated.”

    (RTS 23)What action should be taken by the operator of the trading venue or the systematic internaliser in the cases where the LEI of the issuer cannot be obtained?

    Tell the issuer that they should get an LEI (!!!).


    Impact on EMIR Data Reporting

    There are only three clarifications in the EMIR data reporting Q&A – the first two are amendments to previous trade reporting questions whilst the third is a brand new question:

    Q34 – Reporting of contracts with no maturity date (e.g. CFDs);

    ESMA simply reminds firms that they can also report new trades for instruments with no maturity date with an ‘Action Type’ of ‘P’ (“position component”) if it is to be included in a position level report on the same day. This is in line with previous comments from ESMA.

    Q38 – Trades terminated before the reporting deadline

    All trades must be reported even if they are terminated before the reporting deadline and ESMA is simply clarifying that these reports could also be made with an Action Type of ‘P’ if the trade is to be included in a position level report, on the same day.

    Q50 – Reporting of Confirmation Means

    ESMA states:

    The value ‘N’ (not confirmed) should be used either when:

    • The derivative has to be confirmed by the counterparties but has not been confirmed yet;
    • The derivative does not have to be confirmed by the counterparties because it has been traded on a trading venue and once traded all the terms of the contracts are known and agreed by the parties.

     In other cases, the counterparties should report the ‘E’ or ‘Y’ value for this field depending on the confirmation means used (electronic or non-electronic).

    I think this is the one element in the new Q&As that may surprise some firms as it clearly states that trades on a trading venue should have a value of ‘N’.

    So, not a lot really going on with the new Q&As. It is tempting to think that little news is good news. Personally, I don’t subscribe to this point of view; I think there is still plenty of grey in there that would benefit from further clarification, which is natural given the fundamental changes brought in by MiFIR. I also think there are a few elements in the Guidelines that, with hindsight, could have been better – (equity swaps is my favourite bugbear today).

    If you have a burning MiFIR or EMIR reporting question keeping you awake at night, why not contact us at Kaizen.

  • ESMA updates its EMIR Q&A

    ESMA updates its EMIR Q&A

    ESMA has published another iteration of its EMIR Q&A (12 July 2018). In his first blog for Kaizen, our Senior Reporting Specialist David Nowell summarises the key elements impacting trade reporting:  

    LEI changes due to mergers and acquisitions

    In TR Question 40, ESMA attempts to close some of the gaps in its previous guidance on handling LEI changes due to mergers and acquisitions. The changes bring obligations on reporting counterparties to inform their TR when their “non-EEA counterparty” has a change of LEI and to request the TR to update the LEI in the “other counterparty id” field for all outstanding derivatives. Whilst this change might initially seem attractive from a regulatory perspective, it clearly brings operational challenges for reporting firms and seems to be an imperfect solution as “non-EEA counterparty” is a poor proxy for firms with no EMIR reporting obligation.

    The new TR Question 40 also clarifies the obligations for firms when they have used an incorrect LEI, either to identify themselves as reporting counterparty or to identify their counterparty (“other counterparty id”). On these occasions, the reporting counterparty should “cancel” the incorrect reports with an action type of “E” and re-report them with a correct LEI and the previously agreed UTI. Some may question whether this guidance is consistent with the technical standards which state that an action type of “E” should only be used for the “a cancellation of a wrongly submitted entire report in case the contract never came into existence or was not subject to Regulation (EU) No 648/ 2012 reporting requirements but was reported to a Trade Repository by mistake…” It also may also be inconsistent with the validation which requires: “After a report with action type “E” is submitted, the only allowed action type to be submitted by the other counterparty, if reporting to the same TR, is “E”. No additional reports shall be allowed for that UTI”.

    New but not new

    The new Q&A marks TR Question 47 as being “new” but, in fact, it isn’t – it is the same text as the previous Q&A published on 29 May. However, some participants may have overlooked this addition and may be surprised by the instructions. We are aware that, for cross currency instruments, some participants presumed that “deliverable currency” should be populated with the code for the currency they would be delivering as reporting counterparty and the common data 61 “delivery currency 2” field should be populated with the code of the cross currency they would receive (as suggested by the technical standards). However, Q&A 47 states that “the Delivery currency 2 field should be populated for those derivatives with an FX component for which two currencies are delivered. If both Deliverable currency and Delivery currency 2 are populated, the field Deliverable currency should be populated with the first currency sorted in alphabetical order.” The industry would certainly benefit from some worked examples of derivative reporting much like the ESMA guidelines for MiFIR reporting.

    When a management company can be considered a counterparty

    ESMA also clarified that there are occasions when a fund management company can be considered to be the counterparty to a transaction. Whilst the client is still generally considered to be the counterparty when a management company enters into derivative contracts when providing a portfolio management service, the new Q&A highlights that the management company should be considered the counterparty when it “bears the risk” of the derivative contract. This principle is also borne out in a new trading scenario (“Case 4: Counterparties in the context of portfolio management) where the portfolio manager is shown to have reporting obligations against both a counterparty and a client where it is deemed to ”bear the risk” against the counterparty.

    Here’s the link to ESMA announcement here.

    Our ReportShield™ quality assurance service ensures the accuracy, completeness and quality of EMIR reporting data. If you would like an assessment of the quality of your EMIR reporting, please contact us. 

  • Baskets, ISINs and bank holidays – ESMA publishes new guidance on EMIR

    Baskets, ISINs and bank holidays – ESMA publishes new guidance on EMIR

    ESMA has been busy updating its Q&As. Last week it was MiFID II and this week it’s EMIR. The newly updated Q&A gives guidance on how some specific fields should be populated and which competent authorities should receive certain data. They emphasise once again that simply passing validations is not good enough; the regulator is expecting accurate submissions.  In this blog, we outline some of the key updates. 

    Maturity date

    If maturity date falls on a weekend or bank holiday this is the date that is expected to be reported and not any adjusted date. From a matching perspective this makes logistical sense as different countries have different bank holidays. As well as this, for trades that have expiry dates many years in the future, bank holidays may not be known at the time of execution. I wonder however, if the trade’s adjusted maturity occurs at a later date than the unadjusted date, if we could see any failures to report some post-trade events that happen in between this period. Should ESMA have provided the same clarity for settlement dates?

    Underlying identification

    The guidance states that if an index does not have an ISIN it should be reported with the name that is identical to the names published by the index provider and include special characters. Trading systems tend to dislike special characters so there could be some circumstances where these are difficult to report. Lucky the S&P 500 has an ISIN!

    Access to data by competent authorities

    If the Cambridge Analytica scandal has taught us anything it’s that people care about who has access to their personal data. The same holds true for business data. Until now the guidance for derivatives where the underlying is a basket or an index has been for TRs to allow access to the data for all EU competent authorities. The new guidance is that authorities will only have access to the data if they share the same country as the ISIN or any ISINs that that basket or index is composed of. Other authorities will be allowed access to the data if they need it to carry out their responsibilities. It’s a well-meaning sentiment but it is a difficult change to implement and there are a lot of questions around this which we will follow up separately.

    Deliverable Currencies

    The new Q&A mandates that deliverable currency should be populated in most cases. Our accuracy testing reveals that this is not usually the case within the industry and repositories generally classify the fields as optional. In order to comply with the regulation some changes will need to be made in participants reporting processes.

    Effective Date

    The last new piece of guidance is that if there is no effective date specified in the contract it should be reported as the same date of the execution of the derivative. This is already fairly common practice in the industry but the guidance does not explicitly mention novation events. In the case of a novation where the contract does not contain an effective date, should it be reported as the execution date of the original contract or the date of step in? You decide … just make sure your counterparty agrees!

  • MiFID II Q&A update: New guidance on complex trades and national ID validations

    We are five full months into MiFID II. Competent Authorities are still experiencing teething issues with the instrument data, validations, response messages and providing reporting firms with extracts of their submitted reports. Firms are increasingly moving their focus from addressing validation issues and handling of response files to looking at the accuracy of their reporting. All parties should be working on the most pressing issues following the 80/20 rule.

    “Firms are increasingly moving their focus from addressing validation issues and handling of response files to looking at the accuracy of their reporting.”

    Working on validations to get all the transaction reports accepted by the regulator may not be the most pressing issue.  Firms can still be reporting 100% of their records inaccurately. It is therefore important that attention is turned away from validations to accuracy testing and identifying the valid but wrong population.

    Whilst there are many areas of reporting uncertainty, ESMA has decided to focus its guidance on strategy trades. Strategy trades are relatively rare in the reporting world and affect only a very small proportion of total reportable activity. 

    This post summarises the new guidance from ESMA.

    Complex Trade ID

    A strategy trade is a trade which is composed of more than one financial instrument or legs, where the execution of the trades are contingent on each other and a single price is given for the strategy contract as a whole. 

    When transaction reporting strategy trades, the Complex Trade ID (field 40), must be populated with a code that links each of the legs. This code must be unique to each strategy trade for the reporting firm. ESMA’s latest update to its Transaction Reporting Q&A on Friday (25 May) provides more guidance on how and when the Complex Trade ID should be populated. 

    The aim of the Complex Trade ID is to notify the users of the transaction report that the instrument reported is part of a broader strategy trade and to enable the user to identify any related transactions.  In the guidance they make it clear that:

    • The price reported is the price of the strategy as a whole not the price of the individual leg being reported.
    • The Trading Venue Transaction Identification Code (TVTIC) should be populated for each reported leg of the strategy. Presumably, this would only apply where the strategy itself was executed on a trading venue and the legs execute as part of that strategy. There is more complexity here and more scenarios which the Q&A does not address.  
    • The Complex Trade ID field must be populated even where only one leg of the strategy trade is reportable. It is still a strategy trade and the price must reflect this.
    • Where the strategy itself is allocated an ISIN you still report the individual legs and not the strategy as a whole.
    • In terms of reference data to be reported for strategy trades, the Q&A makes clear that the reference data for the legs must be submitted, not the reference data for a “strategy instrument”.

    National ID validations

    The only other update in the Q&A relates to the validations published for the national identifiers. We have commented in a previous post as to the complexity the approach gives rise to. This is the second update to these validations that have been published.  The latest is:

    • Czech Republic: “It should be noted that the special character “/” is just a separator and should be omitted in transaction reports.”

    Presumably there have been problems with firms including “/” in their identifiers.

    Kaizen’s accuracy testing checks all MiFID II data fields to ensure your reporting is correct. To find out more about how we can help you avoid the ‘valid but wrong’ problem, please get in touch. 

  • ESMA updates EMIR Reporting Q&As for backloading requirement

    ESMA updates EMIR Reporting Q&As for backloading requirement

    ESMA published its latest EMIR Q&As earlier this week to bring it in line with the revised technical standards which come into effect on 1 November this year.  This guidance is supported by the publication of revised validations to be applied by the trade repositories (the so-called L3 validations). Kaizen’s validation service will be available for clients to test their compliance with the validations from 1 May.  We will deal with EMIR RTS re-write in a forthcoming blog that will explore the impact of the EMIR changes. 

    The updated Q&A also deals with the requirements for back-loading of historic trades which is what we address in this article.   

    Back-loading of EMIR reports

    The back-loading obligation applies to firms with trades that were open or entered into after 12 August 2012 (the date from which EMIR took effect) and the commencement of EMIR reporting on 12 February 2014.  This requirement also affects firms that became subject to EMIR after the reporting obligation came into effect due to a relocation or re-categorisation of their business.  Any trades subject to the back-loading requirement must be submitted before the end of 12 February 2019. 

    The back-loading trades can be submitted in their end state and for exchange traded derivatives the concluding position for those cleared contracts.  Where these trades or positions are concluded or terminated after 11 August 2014 (the date when collateral and valuation reporting came into effect), the valuation and collateral fields must also be populated.  

    Reporting firms have been concerned about how to manage the exchange of the Trade ID (UTI) for historic trades.  Such a process would be extremely difficult however ESMA has clarified that where a trade is no longer live at the point of back-loading, the Trade ID or UTI will not have to be exchanged with the counterparty to the trade.

    ESMA has also made clear that following a corporate restructuring, the LEI of the corporate entity that is assuming the obligations for the demised entity’s derivative contracts, must be reported.  If the contracts are not being transferred, the contracts with the liquidated entity would be effectively terminated and should be reported as such.  This makes sense as it will ensure that the risk associated with those contracts is reflected against the entity that holds the risk. 

    A good outcome for firms?

    This is likely the best outcome that could be reached between ESMA and firms in that it allows the EMIR reporting requirement to be met without placing undue burden on reporting firms.  Still, it comes at a time when firms are more than busy with preparations for MiFID II with SFTR closely on its heels.  These changes won’t be the last either, with ongoing guidance via the Q&A process expected for MiFID II reporting both before and after 3 Jan 2018. 

    Dealing with constant change to reporting

    It is clear that firms need to develop speedy and effective processes to implement reporting changes but more than that –  the costs need to be brought under control.  Whilst your reporting solution will be the first area that needs to be addressed, the burden of testing any changes is not insignificant in terms of time, resources and overall cost.  Our testing approach provides early access to validation testing for our clients with full accuracy and completeness testing applied once the reporting solution is completed ahead of go-live.  This testing approach can be used to augment or replace your internal user acceptance testing.  It saves on costs and provides full visibility of your reporting quality, allowing corrections to code or static data to be made before revised reporting requirements take effect.

  • UPDATE: Why populating the clearing obligation field won’t be so easy

    UPDATE: Why populating the clearing obligation field won’t be so easy

    UPDATED 9 September 2016

    Thomson Reuters Accelus has published an opinion piece by our CEO Dario Crispini.

    The article, Why populating the clearing obligation field won’t be so easy, comes off the back of the European Commission’s endorsement of the delegated regulation for mandatory clearing of interest rate swaps denominated in SEK, PLN and NOK currencies in June.

    The regulation extends the clearing obligation from the currency scope of certain EUR, GBP, JPY and USD Interest Rate Swaps and CDSs on the iTraxx main and crossover indices.

    Dario’s article takes a look at what contracts are caught by the clearing obligation and makes the point that completing the field will require great care as there are some hidden complexities.


    The full article is available at Thomson Reuters Accelus, a subscription only service.  If you’re not a subscriber, please download a copy here.

    Article 4 of EMIR introduces the clearing obligation for certain in-scope entities. Earlier this year ESMA published revised EMIR Q&As to give firms more information on how to complete the clearing obligation field which tells ESMA whether or not the contract entered into is subject to mandatory clearing. 

  • Updated EMIR trade reporting rules set stage for fines

    Updated EMIR trade reporting rules set stage for fines

    Kaizen’s CEO Dario Crispini spoke with Thomson Reuters Accelus about the revised EMIR trade reporting regime which aims to bring clarity to the regulatory technical standards first published in 2012.

    “Potentially the EMIR review is more important from an enforcement perspective than it is from an reporting perspective. I do expect to see some fines. The U.S regulators are further ahead and we will see some Dodd Frank fines first. The EMIR review does provide more of a legal platform for taking enforcement action across the various countries. It will be the enforcement processes of the relevant national competent authorities that are applied, which are not EU-wide,” Crispini said.

    The full article is available from Thomson Reuters Accelus, a subscription-only site.

    Extract

    One of the main reasons behind ESMA’s decision to revise the trade reporting RTS was to convert the guidance set out in the many Q&As and the level one and two validation processes into technical standards.

    The EMIR review brings new rules such as the RTS covering product identification and classification, as well as introducing clear obligations regarding unique trade identifier exchange and the timing of UTI exchange.

    “The EMIR review takes many guidelines published by ESMA in the Q&As and makes them regulations or secondary legislation that cannot be contested from an enforcement point of view. For example, if firms have not created a UTI according to the new guidelines, because they are now RTS, they can’t say it was only a guideline. It makes the enforcement process easier for each of the National Competent Authorities,” Crispini said.

    Link to original article

    Read Dario’s recent EMIR opinion piece on mandatory clearing: Why populating the clearing obligation field won’t be so easy