Tag: MiFID II Post-Trade Transparency Reporting

  • ESMA postpones review of MiFID II RTS 2

    ESMA has written to the European Commission to postpone the review of MiFID II Regulatory Technical Standards (RTS) 2, which was due in July 2019, as outlined in Article 17 of the RTS regulatory text.

    The review is key to understanding bond transparency thresholds and liquidity assessments. Given the uncertainties around Brexit, it was felt that the analysis should be completed after the UK has left the European Union. This will now be due by 30 July 2020 and recent regulatory commentary suggests it will begin around March 2020.

    This is another rescheduling to RTS 2, as data quality already delayed the SI regime for bonds until eight months after MiFID II go-live. The SI regime for derivatives is still not due to go live (for the same reason) until ‘at some point in 2020’. This Brexit-related delay to the review will almost certainly push the derivatives SI regime to the latter end of 2020, which in turn may delay the transparency reporting requirement under RTS 2 which looks at decreasing it from 15 minutes to five minutes in January 2021.

    For regulatory reporting purposes, this brings further complexities to investment firms. Understanding of trading where the primary market liquidity is sitting, and its subsequent size and liquidity thresholds for deferral eligibility, is key. Ensuring you are reporting to the correct APA in Europe or UK brings transparency challenges too. 

    To discuss any of the issues above or to find out how our ReportShield™ services could help with your Post Trade Transparency reporting, please get in touch. 

  • The effects of Brexit on MiFID II post-trade transparency reporting

    The effects of Brexit on MiFID II post-trade transparency reporting

    “There are known knowns. These are things we know that we know. There are known unknowns. That is to say, there are things that we know we don’t know. But there are also unknown unknowns. There are things we don’t know we don’t know.” – Donald Rumsfeld (Feb, 2002).

    Brexit…the ‘known unknown’ of everyone’s lives (at least for those of us in the UK) and not just in financial services but across all sectors of life.

    MiFID II has not escaped Brexit either.  Let’s call it BRiFID!  My colleague David Nowell has covered in detail the effects of Brexit on EMIR trade reporting & MiFIR transaction reporting but in this blog, I want to delve into the effects on post-trade transparency reporting. 

    Kaizen announced at the beginning of December 2018 that we were to offer post-trade transparency reporting testing following on from our established MiFID II transaction reporting testing service. The need and demand for MiFIR completeness and accuracy across regimes has become very relevant, highlighted even further by the recent penalty announcements from the UK regulator, the FCA:

    The FCA’s Final Notice on 19 March for the first of this year’s transaction reporting fines, stated:

    “Firms must take reasonable steps to ensure the accuracy and completeness of the transaction reports that they submit to the Authority. One way that firms can help to achieve this is by having controls in place to reconcile the completeness and accuracy of their transaction reporting process.”

    The most recent fines were admittedly for transaction reporting inaccuracies under MiFID I, and MiFID II sanctions are not yet known or been broadcast. But it is only a matter of time before the next firm is penalised and this could well be for post-trade reporting inaccuracies (known unknowns). Stephen Hanks, Head of Markets Policy at the FCA, mentioned at an conference on 16th April that, “poor data quality is still being sent to APAs and that the FCA will continue to work with investment firms to improve quality as a priority”.

    What Now?

    MiFID II transaction reporting has clearly taken a regulatory priority since go-live but post-trade transparency reporting, its just-as-important sibling, is just as key. The past year’s Level 3 Q&As have brought clarity to previous ambiguous regulatory text so firms should now have a greater understanding of their reporting obligation but do they have the testing and controls in place?

    Stephen Hanks stated; “There are still issues we see in reports and we are particularly disappointed to still be seeing errors in reports which would have been errors under MiFID I, never mind MiFID II.”

    Really! Why? When??

    Yes, in amongst the turmoil of BRiFID, investment firms and regulated markets have a near to real-time responsibility to make sure their RTS 1 equity-like and RTS 2 non-equity trades are reported within one minute and 15 minutes respectively (reducing to five minutes by 2021). The responsibility wording is key. Firms may think they do not have a reporting responsibility or they may have asked their brokers to report on their behalf but have firms put in place the correct control framework to prove this if the regulators come calling?  Could this highlight a firm’s unknown unknowns?

    MiFID II has now been live for almost 15 months. With Brexit there is the very real situation that post-trade transparency reporting will need to be directed to either the EU or UK APA as well as liquidity shifting away from the main markets and the impact of ESMA’s Trading Obligation views.  This is a good time to make sure you’re also compliant with post-trade transparency reporting as well as transaction reporting. 

    What next?

    If you have any doubts about whether your post-trade transparency reporting and controls are up to the required standard, we can help. We have a proven track record in helping firms tackle their regulatory reporting issues and risks head on – and helping them to avoid censure. Our ReportShield™ quality assurance services provide everything you need for reporting assurance including a bespoke control framework, quality assurance testing of all fields on all reports, reference data testing, reconciliation and completeness checks and training. Contact us to find out more. 

  • 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.

  • Deep into the soul of regulatory reporting in 2018

    Deep into the soul of regulatory reporting in 2018

    We look back at the regulatory reporting year that was through the songs of Aretha Franklin (sorry Aretha).

    We saw yet another true legend sing her last note this year as the world stood United Together and said a fond farewell to the awe-inspiring Aretha Franklin. We apologise to any fan and most importantly to the great lady herself as we look back at the key regulatory reporting developments of 2018 through her songs and lyrics. I am afraid we have not learnt from our 2016 Bowie travesty….

    MiFIR transaction reporting go-live

    This time last year many of us were running through go-live lists rather than Santa lists and thinking, “I’m going to Drown in my own Tears“. However all that hard work did pay off and all involved deserve their very own Dr Feelgood feeling for their efforts. On the whole, firms got across the line despite the headwinds that presented themselves in the form of instrument data issues (FIRDs / DSB teething issues, understanding TOTV implications, identifying reportable indices), missing LEIs, rogue validation rules at ARMs and the regulator (to mention just a few).

    Though what January really signaled was the beginning of the journey and not the end. Firms’ efforts in the first months of the year were focused on reporting as much of their business as possible and dealing with the inevitable spike in validation breaks from the ARMs and competent authorities. Now the equally hard part of putting in controls to comply with RTS 22 Article 15, to check that what is reported is accurate and complete, before the regulator does, is the new priority.

    ESMA has been very busy

    We always say that regulatory reporting is the gift that keeps on giving, but ESMA can be a little like your eccentric Aunt Vera in delivering something you didn’t ask for and didn’t really want. Well, Vera has certainly been busy this year.  We had new iterations of the EMIR Q&A from ESMA on 12 July and 26 July. And since MiFIR reporting went live on 3 January, we had updates to the Q&A on 25 May and 26 September and some tweaks to the validation schemes as well.

    To be fair to ESMA, we haven’t had the avalanche of information overload we experienced in 2017 and the Q&A mechanism is an essential tool to help bed-down the new reporting regimes so we are Willing to Forgive. Whilst change can often be painful, you can always rely on Kaizen to ensure our ReportShield™ testing reflects the very latest gift from ESMA to keep you One Step Ahead.

    The FCA and SMCR

    When it comes to the Senior Managers and Certification Regime (SMCR) regime it is plain for all to see that the FCA is expecting firms to demonstrate some Respect. In the coming year, the regime will be extended to the core SMCR firms under which an individual within a firm will be ultimately responsible for ensuring that a firm complies with the conduct rules and expectations. Being able to evidence their firm’s reporting is accurate and complete will be a key demand from those who hold this responsibility.

    SFTR

    Having published its Final Report: Technical Standards under SFTR and certain amendments to EMIR back in March 2017, ESMA and the market anticipated that by December 2018 this would be a live reporting regime for investment firms and credit institutions (banks). All that was needed was European Commission endorsement and the legislative steps that follow….

    The European Commission had a Think and after 15 long months eventually piped up I Knew You Were Waiting in late July 2018, albeit with a long list of proposed amendments; largely semantics. Unfortunately, the Commission also decided that A Change is Gonna Come in reference to the rights that ESMA claimed to govern UTI and branch LEI standards endorsement. They left it with ESMA, Call Me.

    ESMA responded to the proposed amendments in September 2018, but unfortunately, it was not with Amazing Grace but rather a dismissive ‘Non,’ rejecting all the changes. The ball is now firmly in the European Commission’s court and as for the bickering, we’re sure It Hurts like Hell but to date, they have not yet found a Bridge Over Troubled Water and endorsed a final RTS for European Parliamentary and Council scrutiny. May the market sing Oh Happy Day when ESMA and the EC stand United Together and we get some certainty over the timing of SFTR go-live.

    Trade reporting and Jumpin’ Jack Flash

    So quite like Jumpin’ Jack Flash, trade reporting for MiFIR started on 3 January 2018 like a cross-fire hurricane with levels of uncertainty and clarity over different aspects of the regulation and the whole market frowned at the crumbs of a crust of bread at the quality of data.

    Firms howled at the morning driving rain with the barrage of Q&A updates throughout the year but as mentioned previously, this has certainly helped bring clarity to many grey areas within the regulation.  DVC, LEI and SI regime delays helped investment firms that felt drowned, washed up and left for dead by the various regulatory demands placed on them.

    What does 2019 hold for us?  The derivatives systematic internaliser regime. Could we start to see a penalty or sanction regime set out by ESMA and the NCAs which could leave investment firms crowned with a spike right through my head?  Questions still do remain though as to whether transparency and a level playing field has really been achieved…

    A view from across the Atlantic

    The CFTC has also been busy in 2018. Two White Papers published suggest that in these Ever Changing Times it is necessary to refresh the Dodd Frank(Iin) Act.

    The first paper, ‘Swaps Regulation Version 2.0’ sets out new proposals to change reporting to a T+1 model and bring in more detail to collateral data requirements. The second paper, which had us singing Border Song, sees The Weight of regulatory burden somewhat lifted for non-US entities where risk is sufficiently monitored by their home regulations.

    No official new rules or timeline has been given yet but we hope the CFTC will Get It Right when legislation is published. We’ll work with our clients to Jump To It and make the necessary preparations when the time comes.

    Brexit – I say a little prayer

    As we approach the end of the year the shadow of Brexit looms large for everyone.  We will share our thoughts on the impact on reporting early in the New Year but in the meantime, season’s greetings from all of us at Kaizen and we wish you a restful break with your family and friends. We thank you for your continued support and we look forward to helping you feel Rock Steady about your reporting quality in the New Year and beyond.

    If nothing else, we hope you have enjoyed listening to some fantastic and enduring classics…you can listen to our Spotify playlist here.

    With thanks to Kaizen Reporting’s industry leading reporting experts for their contributions. Dario Crispini, David Nowell, James Mooney, Jonathan Lee and Chris Machin.