Tag: PTT

  • One year to go:  RTS 2 non-equities reporting to reduce to five minutes

    One year to go: RTS 2 non-equities reporting to reduce to five minutes

    The countdown has now started! From this month it is now less than a year to go until investment firms’ RTS 2 non-equities post-trade transparency reporting needs to reduce from 15 minutes to five minutes. This new implementation comes in three years after the original MiFID II go-live.

    RTS 2, Article 7 states: “…for the first three years of application of Regulation No 600/2014, within 15 minutes after the execution of the relevant transaction; thereafter, within 5 minutes after the execution of the relevant transaction.”

    Whereas RTS 1 transparency has been relatively straightforward due to the electronic nature of equities trading (hence the one minute limit), the non-automated nature of voice trading, as an example, still causes problems for firms in terms of meeting the current close-to-real-time 15-minute deadline imposed by the regulation. It is commonly recognised that firms still struggle to meet publication after 15 minutes, whether that’s changing a trader’s habit, automating trading or even introducing FIX messaging protocol which  – believe it or not  – still isn’t used by all firms. So the reduction to five minutes may really impact firms and may alert the national competent authorities to focus more on these transparency deadlines.

    MiFID II’s transparency objective meant that it was bringing the non-equities trading world into the 21st century and electronifying the practice, creating a level playing field and enabling investors to make an informed decision with the knowledge of how the price was formed.

    With under a year to go, firms need to incorporate this change into their book of work technologically, procedurally and in some cases, culturally. At Kaizen, we provide accuracy testing on MiFID II post-trade transparency reporting (PTT) data to check that you are meeting these close-to-real-time requirements and that your data is correct. This includes checking whether you are reporting within the required timescales and alerting firms where they consistently do not meet the deadline after execution. 

    Contact us if you’d like some help in ensuring your PTT reporting is accurate as this will help with your preparation for the change to reporting within five minutes. 

     

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

  • MiFIR offering from Kaizen to include APA trade reporting

    MiFIR offering from Kaizen to include APA trade reporting

    FOR IMMEDIATE RELEASE

    3 December 2018, London: Kaizen Reporting, the specialist regulatory reporting firm, has announced it is extending its award-winning assurance service, ReportShield™, to cover MiFIR trade reporting*.

    Kaizen has hired Chris Machin, who was instrumental in the development of the MiFIR real-time reporting solution TRADEcho, to help develop its new testing service. With a background in global banking (including at UBS and Credit Suisse), operations and client services, Machin brings significant subject-matter expertise on major regulatory regimes including MiFIR, CSDR, SFTR, MAR, EMIR and Dodd-Frank. He was most recently Head of Client Support at Simplitium, where he partnered with the London Stock Exchange to help build the APA TRADEcho.

    Ian Rennie, Managing Director of Kaizen, said: “With both the buy- and sell-side financial firms now turning their attention to the quality of the data published in the real-time reports through APAs, trade reporting is an important focus for our clients and exactly where Kaizen’s strengths of quality, accuracy and transparency will pay dividends.”

    He added: “We are delighted to have Chris leading the development of our testing service for MiFIR trade reporting. Chris previously played a prominent role in the planning, development and go-live at one of the main APAs. His expertise will enable us to quickly meet the increasing demand from clients and regulators for accurate and complete MiFIR trade reports.”

    Machin’s move to Kaizen adds to the company’s growing list of regulatory experts. Earlier this year the regulatory technology firm hired former regulator and EMIR and MiFIR expert David Nowell, and the former head of the ICMA Taskforce on SFTR, Jonathan Lee.  Already providing peace of mind to clients with its market-leading assurance services for EMIR, MIFID II transaction reporting, Dodd Frank and SFTR, the new MiFID II trade reporting testing service will provide additional confidence to clients that they are meeting their reporting obligations.

    Chris Machin commented: “Kaizen are pioneers in their approach to regulatory reporting assurance and I’m delighted to be joining such a forward-thinking company dedicated to giving clients peace of mind in their reporting data quality.  Trade reporting is a key part of MiFID II’s aims to improve price transparency in the financial markets and I am confident that clients will quickly benefit from the new service.”

    Kaizen’s ReportShield assurance service is a set of four controls that test for the accuracy and completeness of regulatory reports, something mandated under MiFIR.  Kaizen’s testing services are unique in their comprehensiveness, delivering full visibility of reporting quality.

    *Under MiFID II, investment firms are required to both trade and transaction report. Trade reporting improves the near to real-time trade transparency information published to potential investors. Financial details of trades are reported to an Approved Publication Arrangement (APA) for dissemination to the market. In transaction reporting trade details must be reported in T+1 to an Approved Reporting Mechanism (ARM) which validates the data before sending the reports to regulators. 

    (ends)

    For media inquiries, please contact Fiona Wilde at communications@kaizenreporting.com or +44 (0) 20 3912 3271.