Tag: EMIR rewrite

  • New rules = new tools: DTCC simplifies technology ahead of EMIR rewrite

    New rules = new tools: DTCC simplifies technology ahead of EMIR rewrite

    This week we attended the DTCC’s Partners Forum in London to get a taste of what the future holds for firms reporting data to the global trade repository (GTR).  As reporting rules become more complex across all global jurisdictions, the DTCC is aiming to simplify the functionality of the GTR.  Of course anything that makes reporting more straightforward is something we welcome here at Kaizen but there is a lot of work to do to prepare and resource appropriately to make sure you comply with the both changes in obligations and at DTCC. 

    The next phase of the GTR Re-architecture is going to be aligned with the go-live weekend for EMIR RTS on October 28th and is scheduled to be rolled out globally in 2018.

    If you have access to DTCC’s learning center you can see all of the latest updates here.

    Straightforward ingestion

    The new harmonized template is a ‘one size fits all’ solution to understanding how to format and upload data to the repository.  It acts as a one-stop-shop for finding the required information across all five asset classes and also enables filtering on specific products within asset classes, giving greater clarity on what fields are required to be reported.

    Practical processing

    DTCC have also adopted a new ‘latest is greatest’ approach in trade state calculation.  This removes the complexities of multiple submissions being interdependent on each other. UTI locks will also become a thing of the past which will make successful submission to the GTR easier.  However, this puts more responsibility on data submitters to ensure that counterparties are correct and to remove any incorrect submissions.  Delegated submissions will also be split into two parts and allow for separate processing per counterparty.

    Error messages are also being redesigned and will give greater insight into exactly where the error lies and what needs to be corrected.

    Upgraded reports and portal

    What we view as the greatest benefit of the Re-Architecture is the new way in which counterparties and third parties will have access and visibility to data.  Participants will have absolute transparency on what has been reported to the regulator and who it has been reported for.  Historic data will also be retrievable with the new search tool.  Eventually recurring queries can be scheduled to allow bespoke reports to be generated for every user on a timeline that will suit them.

    Changes in context

    The DTCC Re-Architecture is a big step in the right direction in terms of simplifying the way data is submitted and viewed but there is a lot of work to do to get to a place where you can truly take advantage of its benefits – and the clock is ticking.

    We are helping a number of firms understand and get the correct controls in place for the new EMIR RTS obligations due to come into force on I November, please get in contact if you would like to have a conversation about this or any other upcoming changes to reporting obligations. 

  • Big EMIR changes in MiFIR’s shadow and deadline fast approaching

    Big EMIR changes in MiFIR’s shadow and deadline fast approaching

    With so much focus on delivering reporting functionality for the upcoming MiFIR obligations, we shouldn’t forget the substantial changes required from EMIR’s Revised Technical Standards (RTS 2.0).

    The revised RTS was published in January in the Official Journal of the European Union and updated Q&As were published in April.  

    When will obligations come into effect?

    The new legislation will come into effect on 1 November 2017 with the exception of one rule, which came into effect immediately…the extension of the back-loading deadline (which we covered in this blog).  This came as a sigh of relief to those who had not yet started this task yet and a nasty kick in the teeth to those who had spent many painful hours digging through their archives searching for ancient data.  The justification for extending the deadline is that terminated trades do not increase systemic risk.  Given that one of the key objectives of the regulator is to identify systemic risk, the question ‘why does the regulator need this data?’ needs to be asked.  What will happen in 2019 when the new deadline approaches?

    Standardisation is welcome

    Many of the other new rules provide standardisation on how to populate existing fields. This is certainly a step in the right direction.  Counterparties no longer need to quibble over who is the buyer and who is the seller of their contract.  RTS 2.0 provides 10 lengthy rules to determine what is eventually reported out as a single letter – ‘B’ or ‘S’.  Disputes on which party should generate the UTI can be put to rest and altercations on counterparty identification will end as UTI generation responsibilities are created and LEIs are mandated.

    Standardisation is also desired for the ‘classification and precise identification of derivatives’. This is of course more easily said than done in a world where the industry always moves faster than regulation. Spreadbets and swaptions have become newly added contract types as they rise in popularity but ESMA has admitted that not every derivative can be put into a box by allowing the use of ‘other’ contract types.  Does this make the most complicated contracts the easiest to report?

    We also see clarifications and extensions to the allowed values for action type, which was a field that was introduced as part of the Level 2 validations.  ‘C’ is now confirmed to mean an early termination of a contract rather than a more general cancellation. ‘P’ has been introduced to identify the position component of the contract.  The need to report a transaction as ‘new’ followed by ‘compressed’ is replaced by this which should put a smile on some people’s faces as it means substantially less data to submit.  Some things never change though and action type ‘E’ should still be regarded as the kiss of death in terms of EMIR reporting.  Once action type ‘E’ has been reported by either counterparty, you can say goodbye to that UTI. Not even the new action type of ‘R’ for correction will be able to allow the re-reporting of that UTI.

    New fields?

    Lastly, no new legislation would be complete without the introduction of some completely new required fields.  ESMA will require a much more comprehensive view on what collateral details need to be reported. In addition, the party receiving the collateral will also need to report as well as the party posting.  The ‘level’ field has also been introduced so that submissions on a position level can be separated from a trade level.  However, definitions on exactly what is the difference between trade and position level are more difficult to come across.  One notable difference is that positions can have 0 notional whereas trades cannot.

    How we can help

    With such a focus on MiFIR there is a risk that firms may underestimate the material changes introduced by RTS 2.0.  Take the time to check whether you are on track to deliver on the required changes now and contact us if you would like help to understand the new obligations and/or get your testing and controls in place.