Tag: EMIR Q&A

  • A tsunami of EMIR Q&As

    A tsunami of EMIR Q&As

    Just when you thought it was safe to go back into the water, ESMA has hit us with a third EMIR Q&A in as many months. The impact on trade reporting can be summarised as follows:

    Funds and counterparties (General Question 1)

    The text now states that the fund manager must (rather than can) report on behalf of the funds and that the ID of the fund manager shall be provided as the report submitting entity. Please take care with this statement – we do not think it should be taken at face value. Whilst the amended EMIR Article 9 makes the fund management companies ‘responsible and legally liable’ for the reporting, we do not believe this is intended to prohibit delegated reporting by the broker (or another third party) on behalf of the fund manager (where the third party would be the ‘submitting entity’). It is another example where ESMA needs to be more precise in its use of language and advice to the industry.

    Reporting of outstanding positions following entry into force of EMIR (backloading)

    TR Question 4 has been completely deleted reflecting the removal of the backloading obligation following Refit.

    Intragroup transactions (TR Question 13)

    Again, synchronising with Refit, the text clarifies that intragroup trades are not reportable if certain conditions are met. These conditions are outlined in TR Question 51.

    Blocks and allocations (TR Question 39)

    Similar to General Question 1, we have further imprecise text from ESMA. ESMA states that the fund manager must report to the trade repository on behalf of the individual fund where the fund is identified as the counterparty to the trade. While the fund manager is responsible and legally liable for making the report, it can still delegate the reporting obligation. This ‘change’ applies from 18 June 2020.

    Notional amount field for credit index derivatives

    Where there is a change in index factor due to credit events, counterparties should not modify the notional (field 2.20); they should only change the index faction (field 2.89).

    Conclusion

    Not a huge amount of change in the latest Q&A, but it does demonstrate some of the pitfalls in interpreting the ESMA text and the importance of keeping in touch with the regulatory changes. If you’d like some help interpreting the changes or would like transparency of the quality of your EMIR trade reporting, please contact us to find out more about how our quality assurance and controls can get your reporting accurate.

  • ESMA publishes new EMIR Q&A

    ESMA publishes new EMIR Q&A

    With ESMA publishing documents faster than it’s possible to read them, we ‘welcome’ another EMIR Q&A today. The good news for reporting is that it mainly impacts clearing and there are only two amendments in the trade reporting section.

    The first of these comes in TR Question 36 – the reporting of OTC derivative notations. This is a simple clarification from ESMA, stating that:

    “For reporting purposes, only instances where a counterparty (being a CCP or another counterparty) steps into the derivative contract and becomes a new counterparty to the derivative contract should be reported with Action Type “New”. For the original report relating to the existing transaction derivative, counterparties should send a termination report marked as ’C= Early termination’, completing the field “Termination date”. The remaining counterparty and the new counterparty should then send a new report with action type “New” relating to the new transaction derivative.”

    So, there’s some new words in TR Question 36, but no change to reporting.

    The second change impacts TR Question 42 – population of ‘Clearing Obligation’ and ‘Cleared’ (fields 2.34 & 2.35) – and this marks a welcome simplification with the new instructions becoming applicable from 17 June 2019. The implementation of EMIR Refit removes obsolete references to frontloading leaving the remaining instructions far more digestible:

    “The field [Clearing Obligation] should be populated in following way: 

    • The field is not applicable to the transactions executed on a regulated market and should be left blank
    • In the case of cleared trades, the field “Clearing obligation” should be populated with “N” and the field “Cleared” – with “Y.”

    Even with the Q&A, understanding how to trade report correctly under EMIR can be a complicated and perplexing task. At Kaizen, we find many of the mistakes firms make with their reporting stem from a basic misunderstanding of the requirements.

    If you want to unravel the mysteries of EMIR trade reporting and avoid the potential pitfalls leading to breaches, why not attend one of our CPD and CISI accredited courses. In our experience, a small investment in training can help avoid costly remediation at a later stage.