Tag: UTC

  • ESMA gets in just before Santa to consult on clocks, data, records and reporting under MIFID II

    ESMA gets in just before Santa to consult on clocks, data, records and reporting under MIFID II

    ESMA’s consultation paper on some MIFIR/MIFID II guidelines were delivered, as promised, before Rudolph had his harness fitted. Well… just about.

    Those still at their desks on 23 December were left scratching the heads on whether they had been naughty or nice as they began to pore over 269 pages of guidelines on transaction reporting, reference data, order keeping and clock synchronization. 

    You may be relieved to hear that we will not be going through all 269 pages in detail in this blog (and there’ll be no more Santa related puns). Instead we look to set this document in context, explore its usefulness, its purpose, and briefly summarise the structure and content.

    Context

    The publication of the consultation paper continues the exercise of adding further granularity to the obligations required under MIFID II/MIFIR and then built upon under ESMA Regulatory Technical Standards (RTS) 22, 23, 24 and 25.  On page 7 of the consultation paper ESMA explains that:

    “…this guidance complements the technical standards and will be essential for the consistent implementation of the new MiFIR rules.”

    Are they useful?

    Considering the already published details under the directive, regulation, and RTS, it is valid to ask whether further granularity and detail is required. It’s worth considering the guidance provided by ESMA to market participants who have to meet EMIR reporting obligations. Under EMIR, guidance was provided in a piecemeal ad-hoc fashion. Guidelines were not drafted and published for consultation, clarifications were instead conveyed via a ‘Question and Answers’ document. For those who have Dodd Frank Reporting (DFA) obligations (under Chapter 17 part 43, 45 and 46) no further guidance other than the regulation was provided. So seen in this light – having well thought out, structured, and consulted upon guidelines should give firms a greater chance of delivering increased quality and consistency of reporting.

    Regulators’ expectations

    The regulators who drafted this consultation document have the experience of reporting under MIFID and as a result, the standards of the RTS and now these guidelines are more informed, detailed, and consistent than compared to EMIR.  Therefore there will be a greater expectation that the quality of MiFIR reporting will be high from the beginning. To increase the likelihood of the guidelines being successful ESMA will consider all comments received by 23 March 2016. Having guidelines that have been written by regulators with previous experience and consulted upon with market participants – combined with a potential year’s delay to MIFID II – gives the best chance of correct reporting than any of the recently introduced reporting obligations such as EMIR and DFA.

    Structure and content

    The guidelines’ length of 269 pages may make it feel impenetrable and inaccessible but on close inspection this is not the case. While there are four issues covered in this document – transaction reporting, reference data, order record keeping and clock synchronization – here we just review the transaction reporting section, which takes up 193 of the 264 pages and is made up of four parts.

    • Part I: General Principles
      Includes guidance on the how, what, when, where to send reports and exclusions.
    • Part II: Blocks (not to be confused with block trades!)
      A block is a collection of fields, which relate to a particular topic and there are 12 blocks in total. For example, block 1 deals with buyer/seller identification, block 4 deals with execution time within the firm and block 10 branches.
    • Part III: Scenarios
      Outlines different trading scenarios that a reporting party may encounter. For example, transmissions of orders, grouped orders, provision of direct electronic access.
    • Part IV: Instruments
      Offers clarity on what instrument data is required to be populated on reports. Focusing primarily on derivatives, this section prescribes when an ISIN is applicable versus when characteristics of the instrument are required.

    In each of the four sections ESMA attempts to provide clear notes on guidance backed up by an example and then an outline of what is expected to be included in the report. It is worth noting that two thirds of the nearly 200 pages on transaction reporting are made up of examples of how the report should be reported.

    Welcome step, but…

    The guidelines and the opportunity for the industry to provide feedback is a very welcome step. Taken together with the MiFID II/R RTS and the now likely year delay, the industry has the materials at its disposal for introducing high quality reporting on go-live. Though I do have a note of caution for firms: ESMA and the competent authorities’ expectations will be high and individuals under the senior managers regime (coming into effect in quarter 1 next year) will be held to account for any failings.

    Over the coming weeks and months we will explore in more detail the effects and implications of guidelines so keep an eye out and feel free to raise questions or comments either to me (dario.crispini@kaizenreporting.com)or via Linkedin or Twitter. Happy New Year from all of us at Kaizen!

  • Just a second…?

    Just a second…?

    MiFID II introduces the requirement to synchronise the business clocks of trading firms and their customers so that timestamps recorded are standardised across the industry. The idea is that regulators will be able to monitor for market abuse more accurately. Trading systems will need to synchronise themselves to a common source of time. But how will they do this? And what are the implications?

    On the back of the FCA’s MiFID II conference this week we were with the National Physical Laboratory (NPL) to find out. Their workshop, “UTC traceability for the global financial sector, realisation of a unified common clock” attempted to answer some of these questions. Taking the front seat was MiFID II’s RTS 25, which outlines the draft regulatory technical standards on clock synchronisation. The direct impact of this piece of regulation was apparent from the range of professionals from all aspects of the industry including financial firms, exchanges, consultants and scientific organisations.  Most notable was the presence of ESMA and the Bureau International des Poids et Mesures (BIPM) as both have a heavy hand to play in RTS 25. We suggest firms take a look at Table 2 in the Annex of RTS 25 which sets out the level of granularity applicable to their trading activities. It is important that firms are clear on what is expected of them and should be in advanced discussions around the technology to be adopted to meet the new regulatory obligations.

    Here are the key points we took away from the conference:

    1. The industry was concerned about deploying GPS as a means to synchronising their business clocks. It was felt that although it meets the regulators’ authorisation of “satellite systems” as a credited tool, it does not provide traceability back to UTC.  This was further supported by BIPM who claimed that due to the irregular leap second lag incurred through GPS signals, the only credible solution was a direct feed from a National Measurement Institute (NMI). ESMA was clear that both options remain and stood firm, stating that they must be realistic in what they ask from firms and not show any bias to any provider.
    2. The industry feels this needs to be part of the Level 3 discussions but it seems very unlikely that GPSs will be scrapped. We advise all firms to gear up based on the Level 2 RTS 25.
    3. The industry also showed concern around implementing the required technology and sought r advice from the regulator. However, ESMA’s view was very clear in stating it is up to the firm to implement what is required.
    4. ESMA highlighted the importance of firms reviewing their transparency systems on an ongoing basis once deployed. The type of review required is not clarified within the RTS, however we would recommend both internal and third party checks to ensure obligations are met.
    5. FIX is planning to update all versions of its protocol (back to FIX 4.2) to capture the accuracy of seconds in timestamps to 6, 9 or 12 decimal places.
    6. BATS Chi-X Europe is considering providing NPL time source feeds to its clients via a PTP feed if there is considerable demand.

    All in all, the industry is aware of the challenge in implementing this step and the effects it will have on their infrastructures. However, having the same “watch” is very much welcomed by all concerned, agreeing it will lead to better data publication and reporting, thus a more transparent industry as a whole.

    What do you think?  We would welcome feedback or comments about the issues raised in this blog and more broadly, about the MiFID II draft technical standards.

    We’ll be releasing further blogs around the finer details of MiFID II so stay tuned!

    In addition to our testing services, we are offering training courses for firms to help them prepare for the reporting elements of MiFID II. Please contact us to find out more. 

    Read our earlier blog on our reaction to the release of the draft RTSs.