Tag: Trade Reporting

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

     

  • In the news: David Nowell speaks to Practice Insight

    In the news: David Nowell speaks to Practice Insight

    Our Senior Regulatory Reporting Specialist David Nowell recently spoke to Thomas Helm at Practice Insight for a special report on the accumulative impact of post-crisis reforms. In the report Thomas Helm joins the dots of transparency initiatives to reveal the bigger picture. David commented on data quality for the 124 data fields of EMIR trade reporting and the kind of errors we regularly see here at Kaizen. 

    “David Nowell says he frequently comes across errors, such as notional amounts in the “quintillions” in the Emir space, and that these errors can distort the public data aggregations. When compiling the public data aggregations we’d artificially disregard notionals above a certain level because they were obviously false, he says.

    Read the full report.         

  • FCA publish Market Watch 59

    FCA publish Market Watch 59

    Market Watch 59 is ‘almost totally dominated by Transaction Reporting Observations’ and marks yet another strongly worded message from the Financial Conduct Authority on the importance of complete and accurate transaction reporting and how it is critical to the FCA’s work to ensure that markets function well.

    As ever, the FCA stress the importance of adequate systems and controls over transaction reporting and highlights how these requirements are clearly defined in Article 15 of RTS22. In particular, the FCA stresses the importance of reconciliation of front office trading records against data samples from the NCA. It also notes that some market participants don’t appear to be aware of the FCA’s facility to provide this data and the need for regular and thorough reconciliation.

    Valid but incorrect reports

    One of the more important messages from the FCA’s Market Watch is that:

    “Firms should not assume that a report was accurate because it was accepted by the Market Data Processor, as business validation rules are not intended to identify all errors and omissions”

    As we already know at Kaizen, there are too many ‘valid but incorrect’ transaction reports. In amongst the errors highlighted by the FCA are a number of old favourites, including the transposing of the buyer and sell:

    • Incorrect time (especially after the transition to British Summer Time!!!)
    • Price not reported in the major currency
    • Venue populated with the operating MIC where a segment level MIC is available
    • Misreporting the buyer as the seller and vice versa (oh come on!)
    • Re-use of identifiers for multiple clients
    • Incorrect client type code
    • Inconsistency between trading capacity and buyer/seller IDs

    Instrument Reference Data

    There is slightly conciliatory tone on the rejections where the instrument ID, or underlying instrument ID, is not present on FIRDS. Whilst the FCA is still keen to point out this is sometimes the firms’ fault, using the wrong Venue code for example, quite often it results from incorrect reference data submitted by the trading venues. The FCA is clearly sending a message to the trading venues and systematic internaliser that greater control is required over their RTS23 reference data submissions.

    Errors and omissions notifications forms

     The FCA’s observations end on a particularly worrying note for many firms. It reminds firms that where errors or omissions are identified in transaction reports, participants must submit a corrected report to the NCA. Alas, the FCA has noted that some firms are submitting an errors and omissions form, but not subsequently correcting the errors or correcting errors without submitting an errors and omissions form. The FCA does not appear to be happy about this!

    How Kaizen can help

    This is exactly what we here at Kaizen exist to do.  We have a proven track record in helping firms tackle their trade and transaction reporting issues and risks head on – and helping them to avoid censure whether it is for RTS23, MiFIR, EMIR, Dodd-Frank or another G20 regulation. Please contact us for a discussion with one of our regulatory experts 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.

  • Another year of significant growth, success and development for Kaizen

    Another year of significant growth, success and development for Kaizen

    FOR IMMEDIATE RELEASE

    17 December 2018, London: Leading regulatory reporting firm Kaizen Reporting, developer of the multi-award-winning assurance service, ReportShield™, has rounded off a successful year of exciting expansion, both of its specialist team and its services, consolidating its market-leading reputation. With several influential senior hires, the launch of a tailored, expert-led regulatory reporting training service and numerous prestigious award wins, Kaizen has continued to set itself apart at the forefront of the industry.

    Kaizen began the year with a significant partnership with challenger consultancy Elixirr to deliver a complete end-to-end regulatory reporting remediation service for financial institutions, a much-needed partnership for responding to increasing levels of complexity in market regulations.

    This was followed with the hiring of two senior staff: the former chair of the ICMA taskforce on SFTR, Jonathan Lee, and the former regulator and EMIR and MiFIR expert, David Nowell. The addition of two highly-respected regulatory veterans further consolidated Kaizen’s position as market leader, bringing clients even greater assurance services for EMIR, MIFID II transaction reporting, Dodd-Frank and SFTR.

    Kaizen continued to win awards, and in December ReportShield was named ‘Best New Regulatory Reporting Product’ by the FOW International Awards. It was also one of a select group of companies chosen to exhibit at the fourth annual FIA Innovators Pavilion in Chicago, launched to showcase forward-thinking solutions for the global derivatives market. In addition, Kaizen was listed in the RegTech 100, a global directory of companies providing the most innovative solutions in regulation.

    Earlier this month Kaizen announced an expansion of its MiFIR offering, adding APA trade reporting. At the same time Chris Machin, a MiFIR trade reporting specialist, joined Kaizen to head the development of its new service.

    Dario Crispini, CEO of Kaizen, commented: “Our successes in 2018 are down to the commitment and innovation of our fantastic team here at Kaizen. We have doubled our client base and increased the staff numbers supporting our clients by a third. We have made even greater strides towards solidifying our position as the leading regulatory assurance provider. It’s not only a testament to our hard work, but also to the value of the service we are delivering to our clients.”

    “Our successes in 2018 are down to the commitment and innovation of our fantastic team here at Kaizen”

    Ian Rennie, Managing Director of Kaizen, added: “What I think has particularly differentiated this year from previous years is the expertise we have brought on board in the form of Jonathan, David and Chris. We now not only offer an unrivalled service across more regimes but also the specialist expertise from well-known players in this space, bringing even more peace of mind to our clients.”

    Dario continued, “Looking ahead to 2019, we will see regulators increasingly focus on the quality of data being reported for MiFID II, EMIR, Dodd-Frank and other G20 regulations. For MiFID II in particular, the UK regulator, the FCA, is already writing to firms to warn them about improving their data quality. We will also see the extension of the SMCR regime which will put further pressure on senior individuals within financial institutions to ensure their reporting is accurate and complete. And now that the regulatory technical standards have been approved, preparation for SFTR reporting will also increasingly demand time and focus from financial institutions. Putting the right controls in place at an early stage will result in compliant and efficient reporting from go-live”

    ReportShield is a set of services that help financial firms meet their reporting control obligations and effectively manage their reporting risks.  The service includes Kaizen’s award-winning accuracy testing which is unique in its ability to test all reported data, providing firms with full visibility of the quality of their reporting.

    (ends)

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

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

  • SFTR RTS endorsement is still wait and see

    SFTR RTS endorsement is still wait and see

    Wednesday’s Trade & Transaction Reporting Northern Europe conference delivered updates from the European Commission (EC) and ESMA on the state of play for SFTR. It was a useful refresher course but did not deliver anything more tangible on reporting go-live timescales.

    European Commission Policy Officer Gerd Heinen said the delay in the EC’s adoption of the SFTR Regulatory Technical Standards (RTS) is the result of relatively minor technical legal concerns. He said they were highly motivated to endorse the RTS before year end but the EC did not agree with ESMA’s assertion that it was sufficient for them to endorse common standards for UTIs and branch LEIs for these fields to come into force, rather than amending the RTS itself. Once the RTS is endorsed by the EC, there is a three-month period for the European Parliament and the Council to adopt, followed by publication into the Official Journal. A further 20 days later, the RTS will come into force, consistent with a late Q1 2020 reporting go live for banks and investment firms. Market infrastructures (including CCPs), funds and large non-financial counterparties will follow at subsequent three-month intervals.

    ESMA Senior Policy Officer Nikolay Arnaudov reiterated that there were seven technical standards under SFTR (*). He highlighted that this was an EU transparency regime aimed at enhancing financial stability and contributing to the global securities financing transactions data collection exercise. He revisited the EMIR foundations of the report and the four data tables as building blocks (counterparty, loans & collateral, margin, and re-use). However, he would not be drawn any further on go-live dates beyond saying that the RTS amendments by the EC and the subsequent rejection of those amendments by ESMA, were in line with standard procedures.

    We continue to believe that an RTS (likely to be little different in substance from the March 2017 ESMA RTS) will be endorsed by the EC during November or December 2018. This would mean the reporting requirement goes live for banks and investment firms during the latter stages of Q1 2020, with an outside chance that it falls into April 2020.

    (*) The seven technical standards are:

    • RTS and ITS on SFT reporting
    • RTS and ITS on registration and extension of registration of trade repositories
    • RTS on data collection
    • RTS on data availability and access levels
    • ITS on exchange of data between authorities
  • EMIR trade reporting: lifting the lid on pairing and matching

    EMIR trade reporting: lifting the lid on pairing and matching

    EMIR trade reporting is part of the regulatory response to the financial crisis of 2007/2008.  It requires complete and accurate reporting of derivatives to trade repositories (TRs) to enable regulators to monitor for any build-up of systemic risk. Unlike Dodd Frank, EMIR is a dual reporting regime – both counterparties have a reporting obligation (if they are captured by EMIR). This has caused consternation among some parts of the industry as they believe the inherent duplication is wasteful and just increases costs for the industry. The other side of the argument is that dual-sided reporting reinforces the quality of the data by highlighting errors if the two sides of the report don’t “pair” or “match”. The TRs inform the reporting firms where the trade reports have not matched or even paired with the versions supplied by their counterparty.

    How do the TRs pair and match the trade reports?

    The first stage is to find out if both counterparties to the trade have a reporting obligation. This is done by examining the values in the ‘ID of the other counterparty’ field (1.4) and the ‘Country of the other Counterparty’ field (1.5). If these indicate that the ‘other counterparty’ has a reporting obligation, then the TR will set out to find the other side of the trade report – ie. to ‘pair’ it with the report submitted by the ‘other counterparty’.

    This ‘pairing’ is achieved by using the ‘Unique Trade Identifier’ (UTI) in each report and the LEIs in the ‘Reporting Counterparty ID’ field (1.2) and ‘ID of the Other Counterparty’ field (1.4). If the receiving TR does not have both sides of the report, it will request the data from the other TRs. If the two reporting counterparties have failed to use the same UTI, or if they have entered the wrong LEI in either counterparty field, then the TRs will not be able to ‘pair’ the trade.

    If the TRs are able to pair both ‘sides’ of the trade report, they will then check a subset of the fields to ensure that they ‘match’ (as each counterparty is reporting the same trade, the trade details should match). The current set of fields subject to this matching process are as follows:

    • Counterparty side
      (aka buy/sell indicator)
      if one counterparty
      has said ‘B’ the other
      must be ‘S’ and vice versa.
    • Contract Type
    • Asset Class
    • Product Classification Type
    • Product Classification
    • Product Identification Type
    • Product Identification
    • Underlying ID Type
    • Underlying ID
    • Notional Currency 1
    • Notional Currency 2
    • Trade ID
    • Venue of Execution
    • Compression
    • Price/Rate
    • Price Notation
    • Currency of Price
    • Notional
    • Price Multiplier
    • Quantity
    • Delivery Type
    • Execution Timestamp
    • Effective Date
    • Maturity Date
    • Termination Date
    • Confirmation Timestamp
    • Confirmation Means
    • Clearing Obligation
    • Cleared
    • Clearing Timestamp
    • CCP
    • Intragroup
    • Fixed Rate Leg 1
    • Fixed Rate Leg 2
    • Exchange Rate 1
    • Forward Exchange Rate
    • Exchange Rate Basis
    • Commodity Base
    • Commodity Details
    • Option Type
    • Option Exercise Style
    • Strike Price
    • Strike Price Notation
    • Maturity Date of the Underlying
    • Seniority
    • Reference Entity
    • Frequency of Payment
    • Series
    • Version
    • Index Factor
    • Tranche
    • Attachment Point
    • Detachment Point

    Many of these fields must match exactly, whilst others have to match within a tolerance. The matching on a few of these fields is conditional – for example, the Underlying ID must match where the Underlying ID Type is ‘I’ (for ISIN), but does not need to match where the Underlying ID Type is ‘X’ (for index) and free text has been used.

    What happens if the report fails to pair or all the fields do not match?

    The TRs will still accept the report, but they will inform the reporting counterparty if the report does not pair and it will also identify all the fields that have not matched if a pair has been found. The reporting counterparties are then expected to resolve the issues with their counterparty.

    How good are the pairing and matching rates?

    The pairing rates are a little disappointing and the matching rates are extremely low. Whilst the pairing rates have increased since the implementation of the revised reporting technical standards last year (probably due to the guidance on the UTI generating party being formally added to the regulation), the matching rates have not.

    Does this matter?

    Yes. Remember, one of the drivers behind dual-sided reporting is to reinforce the quality of the data and the disappointing rates indicate that there are issues with data quality. While firms may not have seen much action from the NCAs on EMIR data quality aspects (although the £35m fine levied by the UK FCA may have come as a shock), ESMA clearly flagged that it will focus on data quality in its annual report and work plan:

    “ESMA continued to closely engage with NCAs and exchange data to identify counterparties where reporting causes large amounts of breaks in the reconciliation process. ESMA plans to further intensify its engagement with the NCAs as part of the NCA cooperation process related to data quality.”

    Firms most definitely need to be aware that NCAs are monitoring the pairing and matching rates and could target those firms seen as outliers. Whilst the reason for unpaired or unmatched reports could lay with the ‘other counterparty’, those firms with comparatively low pairing and matching rates overall will be in the sights of the NCAs.

    What can firms do to improve matching rates?

    Low matching rates are a very good indication of poor quality EMIR trade reports. Sadly, there’s no short cut on this one; to improve the matching rates, firms need to improve the quality of the data they submit. This is where Kaizen can help. We can offer a reconciliation from the front office trading data to the data submitted in your name to the trade repository. We can also run an accuracy test on all your trade and position reports, including a check that your outstanding positions are an accurate reflection of your trade reports. We also offer training on the EMIR reporting standards. For further information please contact us.

  • Join us in Stockholm for the Trade and Transaction Reporting Conference

    Join us in Stockholm for the Trade and Transaction Reporting Conference

    We are very pleased to be taking part in the Infoline Trade and Transaction Reporting Northern Europe Conference on 17 October in Stockholm. The conference is aimed at investment and securities firms, banks and trading venues impacted by the reporting and disclosure obligations of EMIR, MiFID II,and SFTR.   

    On the agenda are our very own Senior Regulatory Reporting Specialists David Nowell and Jonathan Lee who will give practical insight on EMIR and MiFIR reporting data quality (David) and taking the pain away from SFTR transaction reporting implementation (Jonathan).

    We’d be delighted to see you there and would love to pass on a 30% saving on your conference pass (please quote FKM63655KR). 

    Event details:

    For more information, please don’t hesitate to contact us.

  • Tales from the crypt – the great cryptocurrency derivatives EMIR reportability debate

    Tales from the crypt – the great cryptocurrency derivatives EMIR reportability debate

    Cryptocurrencies are often seen as a great way to get rich quick, or poor quicker. To be honest, if I wanted to lose a shed load of money, I’d much rather nip down the bookies and put it all on Tripod Lad to win the 3:30 at Kempton Park. Whilst it might fall at the first fence, at least I would have some idea about the mechanics preventing it reaching the winning post. However, my approach to losing money is looking increasingly old school. It appears that there’s nobody left on the planet who doesn’t know somebody holding a fraction of a bitcoin in the hope that it will miraculously increase in value enough to put their grandkids through university.

    So, how worrying is the rise of the derivatives on cryptocurrencies? Well, we’ve certainly seen extreme volatility in this asset class, commonly attributed to investor behaviours of herding and regret-aversion. Does this create systemic risk? Well, it’s tempting to believe this asset class isn’t mature enough yet to represent a risk to the entire financial system. However, the launch of exchange traded derivatives on cryptocurrencies has led to involvement of increasing numbers of systemically important financial institutions in this asset class. The CFTC Chairman J. Christopher Giancarlo has warned whilst cryptocurrency derivatives are a relatively small market in terms of systemic risk, it is one that the CFTC needs to watch carefully.

    So, we hope this is a development the EEA regulators are also watching carefully. Surely this is one of the good things about EMIR trade reporting – ESMA and other EEA regulators will have had 6 years of analysing cryptocurrency derivatives to assess whether they could have the potential to grow and become a new threat to financial stability. Or have they? Possibly not, as there is a great deal of confusion in the industry as to whether cryptocurrency derivative instruments are actually reportable at all under EMIR. Whilst some firms have decided to trade report them to trade repositories, others have not. The confusion stems from the definition of reportable derivatives. EMIR takes this definition from MiFID and the FCA has explained that whilst cryptocurrency derivatives are “capable” of being financial instruments under MiFID II, it does not consider cryptocurrencies to be currencies or commodities under MiFID II. This is unfortunate as it leaves firms with the added dilemma that if these derivatives are EMIR trade reportable, exactly how should they be reported. Those firms that have chosen to report have taken the decision to report as commodity derivatives; mainly because the ESMA validation for currency derivatives requires an official ISO currency code and cryptocurrencies do not have one.  However, it is debatable whether reporting cryptocurrencies as commodities will deliver much value to the regulators as they will not be recognisable as cryptocurrencies from the report. Maybe the perfect opportunity to address this issue would have been through the fundamental changes to the reporting technical standards implemented in October 2017.

    The reporting of cryptocurrency derivatives may be one of the “known unknowns” in EMIR reporting. However, there are many known reporting errors in EMIR trade reporting that make it through the ESMA validation scheme. Just because a trade repository has accepted a report doesn’t mean it is error free. Some firms consider EMIR trade reporting to be a “fire and forget” reporting regime apparently forgetting the obligation for “complete and accurate” reporting so long as “T+1” is achieved. However, ESMA’s 2017 Annual Report and 2018 Work Programme makes it abundantly clear that the quality of data reported to TRs is not good enough and needs to be improved.

    How good is your EMIR trade reporting? Our ReportShield™ quality assurance service delivers an independent and comprehensive analysis of the accuracy and completeness of your EMIR trade reports. For a consultation with one of our experts, please contact us.

  • ESMA updates its validation rules (again)

    ESMA updates its validation rules (again)

    Just when you thought it was safe to set out on holiday with no more reporting changes to worry about, ESMA announced some changes to its EMIR trade reporting validation rules on 9 August.

    On first glance, the changes appear fairly innocuous with only five fields impacted:

    • Reporting Timestamp; 
    • Reporting Counterparty ID;
    • ID of the Other Counterparty; 
    • Underlying Identification; and  
    • Confirmation means.

    However, no change to reporting is ever easy for firms or trade repositories (TRs). Although an implementation date of 5 November 2018 gives the industry some time to prepare, it is surprising that the changes come without any warning or consultation. They also come without any explanation of their value to the regulator. This is frustrating as good regulation should result from a robust cost benefit analysis and the industry is going to struggle to understand the benefit of some of these changes.

    Let’s take the first change – the ‘Reporting Timestamp’: “The reporting timestamp should be equal or earlier than the timestamp of the receipt of the report by the TR. The date part of the timestamp cannot be earlier than the day preceding the date of the receipt of the report by the TR. The receipt of the report should be understood as the moment the report enters a TR’s system.”

    This is probably the biggest change to the industry as many trade repositories don’t ask for firms to populate this field, as the time the firm reports should be exactly the same time the TR receives it. If the TR doesn’t auto-populate this field, it appears to introduce the possibility of error by asking the reporting firm to populate the field itself. If the TRs were to incorrectly populate the reporting timestamp, it would be challenged by the reporting firms, so the regulators would appear to be trying to fix something that isn’t broken.                 

    The validation changes to the ‘Reporting Counterparty ID’ and ‘ID of the other Counterparty’ shouldn’t present too many issues as they are both relaxations of the validations. In each case the LEI can have a status of ‘lapsed’ or ‘retired’ where the ‘Action Type’ is ‘C’ (for ‘early termination’), and the LEI no longer has any check on the ‘registration status’ where the Action Type is ‘E’.

    The validation changes to the ‘Underlying identification’ appear to be both pointless and risible. The first element allows the special characters of hyphen and full stop where the ‘Underlying identification type’ is ‘A’ for Aii. It is pointless because the Aii code can no longer be used in the ‘underlying identification’ field post MiFIR implementation and it is laughable as the hyphen has always been an integral part of the Aii (i.e. the ESMA validation would have prevented the underlying Aii being reported correctly). The additional characters are also allowed where the underlying identification type is ‘B’ (for ‘basket’) – this would cause issues as the hyphen is also used as the separator for the individual components of a basket.

    The final change impacts the ‘Confirmation means’ field which now stipulates that: If field 2.15 [Venue] is populated with a MIC code other than “XXXX” or “XOFF” and field 2.35 [‘Cleared’]is populated with “N”[Not cleared], this field shall be populated with “N”[non-confirmed]. This is sensible and is one of the tests that Kaizen already includes in our EMIR trade reporting quality assurance testing.  We apply more than 450 tests to EMIR reports to check if the data contained within them is accurate.  Our clients can also take advantage of a new Kaizen service which offer clients the opportunity to pre-test their compliance with the new validations through a tool that replicates the ESMA validation scheme.

    For further details on our pre-testing validations service and other Kaizen quality assurance services please contact us.

  • ESMA updates its EMIR Q&A

    ESMA updates its EMIR Q&A

    ESMA has published another iteration of its EMIR Q&A (12 July 2018). In his first blog for Kaizen, our Senior Reporting Specialist David Nowell summarises the key elements impacting trade reporting:  

    LEI changes due to mergers and acquisitions

    In TR Question 40, ESMA attempts to close some of the gaps in its previous guidance on handling LEI changes due to mergers and acquisitions. The changes bring obligations on reporting counterparties to inform their TR when their “non-EEA counterparty” has a change of LEI and to request the TR to update the LEI in the “other counterparty id” field for all outstanding derivatives. Whilst this change might initially seem attractive from a regulatory perspective, it clearly brings operational challenges for reporting firms and seems to be an imperfect solution as “non-EEA counterparty” is a poor proxy for firms with no EMIR reporting obligation.

    The new TR Question 40 also clarifies the obligations for firms when they have used an incorrect LEI, either to identify themselves as reporting counterparty or to identify their counterparty (“other counterparty id”). On these occasions, the reporting counterparty should “cancel” the incorrect reports with an action type of “E” and re-report them with a correct LEI and the previously agreed UTI. Some may question whether this guidance is consistent with the technical standards which state that an action type of “E” should only be used for the “a cancellation of a wrongly submitted entire report in case the contract never came into existence or was not subject to Regulation (EU) No 648/ 2012 reporting requirements but was reported to a Trade Repository by mistake…” It also may also be inconsistent with the validation which requires: “After a report with action type “E” is submitted, the only allowed action type to be submitted by the other counterparty, if reporting to the same TR, is “E”. No additional reports shall be allowed for that UTI”.

    New but not new

    The new Q&A marks TR Question 47 as being “new” but, in fact, it isn’t – it is the same text as the previous Q&A published on 29 May. However, some participants may have overlooked this addition and may be surprised by the instructions. We are aware that, for cross currency instruments, some participants presumed that “deliverable currency” should be populated with the code for the currency they would be delivering as reporting counterparty and the common data 61 “delivery currency 2” field should be populated with the code of the cross currency they would receive (as suggested by the technical standards). However, Q&A 47 states that “the Delivery currency 2 field should be populated for those derivatives with an FX component for which two currencies are delivered. If both Deliverable currency and Delivery currency 2 are populated, the field Deliverable currency should be populated with the first currency sorted in alphabetical order.” The industry would certainly benefit from some worked examples of derivative reporting much like the ESMA guidelines for MiFIR reporting.

    When a management company can be considered a counterparty

    ESMA also clarified that there are occasions when a fund management company can be considered to be the counterparty to a transaction. Whilst the client is still generally considered to be the counterparty when a management company enters into derivative contracts when providing a portfolio management service, the new Q&A highlights that the management company should be considered the counterparty when it “bears the risk” of the derivative contract. This principle is also borne out in a new trading scenario (“Case 4: Counterparties in the context of portfolio management) where the portfolio manager is shown to have reporting obligations against both a counterparty and a client where it is deemed to ”bear the risk” against the counterparty.

    Here’s the link to ESMA announcement here.

    Our ReportShield™ quality assurance service ensures the accuracy, completeness and quality of EMIR reporting data. If you would like an assessment of the quality of your EMIR reporting, please contact us. 

  • Media release: Kaizen and Elixirr partner to bring new level of transaction reporting compliance

    Media release: Kaizen and Elixirr partner to bring new level of transaction reporting compliance

    Kaizen and Elixirr, the challenger consultancy, have announced a new partnership, which will deliver a complete end-to-end regulatory reporting remediation service for financial institutions. We will collaboratively offer clients greatly-improved assurance testing, governance and support on their trade and transaction reporting remediation projects.

    This is a significant milestone in responding to the increasing levels and complexity of regulation faced by the industry. Kaizen is unique in its approach to compliance assurance, checking every single item of transaction data for accuracy and completeness, while Elixirr provides practical and hands on support to resolve the reporting issues highlighted by the Kaizen assurance assessment.

    Data quality has been a continual problem under the original MiFID reporting regime[1] but the increased complexity of EMIR and MiFID II reporting obligations means that this will be even harder to achieve. At the same time, regulators’ capacity to identify issues has widened, and the UK’s Senior Managers’ Regime puts additional pressure on individual managers within firms to ensure they are reporting correctly.

    Firms which do not fully address reporting issues are at risk of multi-million pound fines, reputational damage, and the cost of internally remediating the problem, which is often significant. In an industry first, Kaizen’s technology solution, combined with Elixirr’s remediation skills, will identify reporting issues quickly and ensure they are resolved and replayed, in a cost-effective, seamless way. 

    Barry Lewis, Partner at Elixirr who led the formation of the partnership, says “Kaizen have developed a service that is invaluable to the financial services industry, so we’re delighted to partner with them in such a value-added offering. This partnership means we can combine robust data quality assurance tools with the analysis and remediation expertise of our team, and help our joint clients respond even more effectively to the increasing needs for reporting compliance.”

    Dario Crispini, Kaizen CEO , says, “I see the partnership as an important step forward in compliance evolution. By combining the skillset and expertise of the two companies we are able to provide clients with greatly enhanced confidence and accuracy when reporting to regulators. Elixirr has a strong reputation, attention to detail and unwavering passion to really help firms succeed and we trust them to provide the best remediation solutions for the companies we work with. The market is already responding well, and I have full confidence that this partnership will quickly benefit our clients and go from strength to strength in the months and years to come.”

    Recently awarded the Queen’s Award for Enterprise in innovation, one of the UK’s highest business accolades, Kaizen has combined data science with leading regulatory expertise to develop ReportShieldTM, a quality assurance service that provides firms with a complete set of controls to ensure the accuracy, timeliness and completeness of their reporting data.  ReportShield tests all of a firm’s records, avoiding the shortcomings of other approaches which test only small data samples.

    Elixirr has a proven track record of working with financial services firms internationally to help them identify issues and achieve full and sustainable reporting compliance.

    -ENDS-

    For media inquiries, please contact Fiona Wilde, Head of Communications and Marketing on 07834 731 602 or media@kaizenreporting.com.

    [1] Kaizen’s analysis of transaction reporting fines issued by the FCA found that 65% of transactions were incorrect, and that firms were unaware of these inaccuracies. See our infographic here. 

  • Kaizen hires ex-trade repository specialist to support growth

    Kaizen hires ex-trade repository specialist to support growth

    Leading regulatory reporting assurance company Kaizen Reporting is pleased to announce that James Mooney has joined its team in London as a regulatory consultant. James is a derivatives regulatory expert whose most recent role was at global financial services corporation Depository Trust and Clearing Corporation (DTCC). Prior to that he was with Fidelity Investments.

    Kaizen Founder and CEO Dario Crispini, said, “I’m delighted that James has joined Kaizen to support our growing client base of tier 1 and 2 banks, fund managers and brokers. He brings a deep understanding of trade repository requirements across multiple jurisdictions including DFA, EMIR, Canada, ASIC, MAS and HKMA. Alongside his technical knowledge, his practical knowledge of the regulations and experience of serving large global clients are invaluable.”

    The new role reflects the growth Kaizen is experiencing as it responds to increased demand for its quality assurance services that address the increasing complexities of regulations such as MiFID II and EMIR. Its client base has significantly expanded in the past two quarters to include an additional three tier 1 banks, several of the largest global asset management firms and one of the world’s largest brokers.

    Dario, formerly head of the FCA’s Transaction Monitoring Unit, continues, “Firms have struggled to get their reporting correct under the much less complicated MiFID regime for nearly ten years – and it’s about to get a lot more challenging. Testing and reconciliations are mandatory under MiFID II and it’s important that firms put the right controls in place now so that they hit the ground running with their reporting on 3 January 2018.”

    James Mooney, said, “It’s great to be joining Kaizen at such an exciting time as it takes on more clients and expands the jurisdictions it covers. Kaizen are the industry experts in regulatory reporting and pioneers in their approach to testing, which is fast becoming the industry standard. Its mission to give its clients confidence in their reporting quality really resonated with me and I’m proud to be part of a team that wants to improve data quality standards in the industry.”

    Kaizen’s pioneering ReportShield™ quality assurance services provide firms with an automated set of testing and controls that give full transparency of reported data, ensuring that clients meet their regulatory obligations. The service recently won a Queen’s Award for Enterprise for innovation in recognition of its impact on the industry.

    For media inquiries, please contact Fiona Wilde at media@kaizenreporting.com.

  • Kaizen attends Queen’s Award royal reception

    Kaizen attends Queen’s Award royal reception

    We’re delighted to share some official – and unofficial – photos from last week’s Buckingham Palace reception for winners of the 2017 Queen’s Award for Enterprise. 

    Our Senior Data Scientist Tamer Onder and CEO and Founder Dario Crispini had the honour of meeting Her Majesty the Queen at the event, held on Tuesday 11 July. 

    In April, we were awarded a Queen’s Award for innovation for our ReportShield accuracy testing service which checks all regulatory reporting data at source to give financial firms complete transparency of their regulatory reporting quality. 

    Awards for innovation are given to businesses that can demonstrate their innovative products or services are commercially successful, stable and sustainable.  Winners also have to prove they are a good corporate citizen. 

    The Queen’s Awards for Enterprise are for outstanding achievement by UK businesses in the categories of innovation, international trade and sustainable development and were established in 1965.

    They are one of the most prestigious business awards in the country, with winning businesses able to use the esteemed Queen’s Awards emblem for the next five years. 

    Read our press release from earlier in the year when we first found out we’d won the award. 

     

     

  • Webinar: Do you have the right systems and controls in place?

    Webinar: Do you have the right systems and controls in place?

    Join us and our partner UnaVista for a webinar: MiFIR – the right systems and controls

    Date: Wednesday 28 June 2017
    Time: 10am (EDT) 3pm (GMT) 4pm (CEST)

    Kaizen’s Founder Dario Crispini was the head of the FCA’s Transaction Monitoring Unit when MiFID I was introduced.  

    On this webinar, Dario will discuss lessons learned from control failings under MiFID I, the consequences of not getting the control environment right, and the new requirements for systems and controls under MiFIR.  

    Dario will also outline the latest comments by the regulator on MiFiR, a taste of which can be found in our latest blog. 

    The webinar is part of a series on MiFIR run by our partner UnaVista, who will outline key tools and capabilities such as accuracy testing, reference data, reconciliations, validations, management information, workflow and exception management etc that firms need to consider ahead of MiFIR.

    Register here

    Kaizen’s award-winning quality assurance service ReportShield™ gives you everything you need to be compliant with transaction reporting requirements under MiFIR.  Find out more about our testing and controls. 

  • Kaizen Reporting’s ReportShield™ testing wins Queen’s Award for innovation!

    Kaizen Reporting’s ReportShield™ testing wins Queen’s Award for innovation!

    Regulatory technology firm, Kaizen Reporting is delighted to announce that it has won a Queen’s Award for Enterprise, the highest accolade in UK business.

    Kaizen’s award comes in the innovation category for the prestigious business awards which are announced today by the Business Secretary Greg Clark.

    Kaizen won the award for its ReportShield quality assurance service which tests 100% of regulatory reports. This is in contrast to traditional methods which only test small data samples.  The in-depth testing gives Kaizen’s clients full sight of any errors within their reporting data so they can be corrected.

    Changing the way reporting is done

    Kaizen CEO and Founder, Dario Crispini, said, “Winning a Queen’s Award for innovation is a huge honour and recognition of the way Kaizen’s ReportShield testing is changing the way reporting is delivered throughout the industry.”

    Regulatory trade and transaction reporting has become absolutely vital since the financial crisis in 2007. Regulators rely on regulatory reporting to detect insider dealing, rogue trading and the build-up of systemic risk (one of the primary causes of the crisis).

    However regulatory reporting is becoming increasingly complex and financial firms have struggled to get it right.  This has resulted, in some cases, in regulatory fines running into millions of pounds and costly bills to retrospectively fix the errors.

    Improving the quality of regulatory reporting

    In response to this, Dario, a former regulator, and Ian Rennie, industry expert, set up Kaizen Reporting in 2013 to help improve the quality of firms’ regulatory reporting.   

    By combining their regulatory knowledge with data science, Kaizen developed ReportShield, an automated testing service that fully assesses the quality of regulatory reporting data.

    Dario continues, “Incorrect regulatory reporting is a major industry problem that Kaizen wants to help solve. ReportShield is helping both sides of the industry – firms can be confident of their reporting integrity and avoid fines, and the regulator receives good quality transaction reports, ensuring market transparency.”

    Dario added, “I’d like to personally thank the Kaizen team for their dedication and expertise in developing ReportShield, and also our clients and partners for their support over the past three years.” 

    Winners of the Queen’s Award are invited to attend a reception at Buckingham Palace later in the year.

    ends

    About the Queen’s Awards

    Established in 1965, the Queen’s Awards for Enterprise are for outstanding achievement by UK businesses in the categories of innovation, international trade and sustainable development. Awards for innovation are given to businesses that can demonstrate that their innovative products or services are commercially successful.

    For media inquiries, please contact Fiona Wilde, Head of Communications and Marketing on 07834 731 602 or fiona.wilde@kaizenreporting.com.

  • Q: Which ‘reporting crocodile’ will be nearest the canoe in 2017?

    Q: Which ‘reporting crocodile’ will be nearest the canoe in 2017?

    A: MiFID II, and it’s only 358 days away…

    In our last blog we looked back on the reporting events and challenges that shaped 2016 through the hits of Bowie; but as we begin 2017 we find ourselves asking, ‘where are we now?’ (last Bowie reference…promise!). In short, there are many reporting regimes that are contenders to win the accolade of the ‘reporting crocodile’ nearest the canoe for UK firms in 2017. However, the characteristics and specific demands that MiFID II requires of firms, establishes it as the most demanding and challenging regulatory reporting ask of 2017. The clock is ticking and as at the time of writing, we have 358 days until go-live!

    The other crocodiles circling the canoe

    For those of you who came back into the office to deal with the aftermath of your firm’s Bank of Israel Reporting go live, 3 January 2018 may seem a long way off. Equally if you are responding to the CFTC review of your DFA reporting through the NFA and their 4s letters or an official examination by them, again MiFID II seems a distant problem to contend with. Worse still, your firm may be facing regulatory censure on longstanding commitments such as MiFID I or, as we are seeing increasingly, fines from the CFTC in relation to accuracy of reports under the DFA regime. Then there is pressure from ESMA and competent authorities to improve the quality of EMIR reports. In addition to the EMIR Review and MiFID II, European firms need to contend with consultations on SFTR.  For those who have US and HK obligations there are the new SEC and HKMA obligations due throughout the first three quarters of the year.

    These ‘crocodiles’ are not just circling but hitting the canoe at the same time and of course, you cannot pick and choose which ones to deal with; all need to be grappled with. But what makes MiFID II stand out as the crocodile you need to deal with most?

    What are the characteristics of MiFID II that require special attention?

    In a nutshell – in many respects, MiFID II confers materially different obligations on firms and runs a much greater risk of regulatory censure following go-live compared to other G20 reporting obligations. There are three characteristics which mark out MiFID II for special attention:

    First, the sheer number of fields, many different from what has been asked of before. E.g. Trader ID, algo ID, short-selling field, pre-trade waivers, and precise execution time to the millisecond and beyond!

    Second, MiFID II builds upon an existing regime where competent authorities, most notably the FCA, have developed expertise in detecting data quality issues and have a regime in place to issue sanctions. Ana Fernandes of the FCA made it clear at the recent FCA TMU Transaction Reporting Forum, that expectations will remain high and the ability of the TMU to detect errors will be improved come 3 January 2018.

    Third, the sheer complexity of the MiFIR requirements dwarfs that of competing regimes. Whether it is determining what transactions need to be reported, what business events need to be excluded, notwithstanding ‘no LEI no trade’, the short-selling calculation, or how to put in place the mandated regulatory controls, the level of complexity is materially different than what has been expected before.

    Next, we explore some of these complexities and discuss what firms need to be doing now to ensure successful delivery this time next year.

    Your MiFID II to do list

    It’s the New Year and what better time to draft your ‘MiFID II Transaction Reporting to do list’?  Better still, we’ve done it for you…

    1. Reporting Solution – Build or Buy?

    Key to meeting the complex obligations of MiFID II is putting in place the appropriate reporting solution.  There is no fixed answer on whether to buy or build as it depends completely on your firm’s size, previous investment in meeting reporting obligations, and expected reporting volumes.

    At one end of the spectrum there are the large tier 1 banks who have been investing heavily in their reporting solutions over the last six years. In this case, it is most likely that there will be an extension of recent builds to cater for MiFID II requirements. A word of warning, IT architects and IT leads that expect a similar build to EMIR should think again, see below for examples of why.

    At the other end of the spectrum, are firms who have previously had little or no reporting obligations who are only now looking to make the decision on whether to build or buy. On balance, due to the complexity involved and time remaining, buying a solution and adapting it to your needs is probably the least risky option and you should choose a provider with a track record of providing reporting solutions that are ready to roll off the production line.

    2. Determine what trades are reportable, based upon instrument being traded

    At first glance it appears straightforward how to determine what instruments needs to be reported. Firms will be able to rely, to a certain degree, on the list that ESMA is mandated to provide under RTS 23. But even here there are significant implementation and operational issues with this list. For example, if it is not produced or there are issues with it then firms still have the obligation to report correctly, irrespective of the provision of the list.

    It become more complicated when you have to identify instruments which reference those traded or admitted to trading on trading venues.  How will firms identify and report the below examples?

    • Third country futures that reference instruments admitted or requested for trading on trading venue (RM, MTF or OTF)
    • OTC derivatives and 3rd country ETDs that reference instruments admitted or requested for trading on trading venue (RM, MTF or OTF)
    • How to identify, at the time of trade, the index constituents.

    Due to these inherent problems; determining which instruments are reportable becomes a materially more complex proposition compared to MiFID I, EMIR and DFA. Firms need to be working now with their counterparts, vendors and participate in discussions with their Trade Associations to put in place workable solutions.

    3. Establish what activity requires reporting

    Having figured out what instruments need reporting firms need to turn their attention to determining what activity is reportable. In short, take a look at RTS 22, Article 2 and the 14 different sets of activities that need to be excluded. The fact that many of these business activity exclusions have not been seen in EMIR, demonstrates again the material difference in the type of reporting solution required for MiFID II compared to previous reporting regimes. Firms will have to look at their trade data and ensure their reporting solutions are able to identify activity that should be excluded, as MiFIR does not allow for over-reporting.

    4. No LEI – No Trade

    Both the FCA and ESMA in recent public meetings have reiterated the point that firms must not trade with entities that do not have a LEI. This has been reiterated in the first MiFID II Q&A published by ESMA. There is considerable work for client onboarding teams and relationship managers to reach out to clients without LEIs and ensure compliance by 3 January 2018. Good luck!

    5. Short-sell calculation

    We will not discuss here the merits or otherwise of the short-selling requirement for transaction reporting (ok well, a little passing reference…suffice to say the value of this field is a best questionable.) Transactions in cash equities and government securities will require a calculation to identify transactions that take the firm short at any given point. Making an accurate calculation that takes into account late trade bookings and busts will be problematic and firms should not underestimate the time and cost that will be needed to ensure compliance.

    6. Under RTS 22, Article 15, ESMA high priests did say upon to firms, ‘thou shall test and reconcile one’s transaction reports….’

    Ok, maybe not as dramatically as that but ESMA now makes the obligation to test and reconcile mandatory under MiFIR. The important point to note is that controls are often the first casualty of delivery, as go-live approaches. For MiFID II this is not an option; firms need to ensure effective testing and reconciliations are in place at go-live. Failure to do so will be a breach. Looking to third party providers who have mutualised the costs of testing and reconciliations may make sense to ensure comprehensive and effective controls are in place prior to go live in 358 days time.

    There are many more items to add to the MiFID II Transaction Reporting to-do list.  Of course in the current environment there is no choice between which regimes you implement. That said, the complexity and the introduction of new demands on firms by MiFID II means it should be treated as the largest crocodile nearest the canoe when firms are planning their 2017 regulatory reporting delivery.

  • 2016: The reporting (Jean) Genie is well and truly out of the bottle

    2016: The reporting (Jean) Genie is well and truly out of the bottle

    David Bowie was many things to many people but a transaction reporting aficionado he was not. That said, in the year that saw the great man leave on his own “Space Oddity“, we use some of his most loved hits and lyrics to help us look back at reporting in 2016 …. and only hope he is not looking down to see us take such a liberty! David, we’re truly sorry…

    The reporting “Labyrinth” – new obligations

    Every year since the 2009 G20 Pittsburgh summit, which gave birth to the G20 reporting commitments, the industry has had to plan for and comply with new regulatory reporting obligations across the globe and 2016 has not been any different. Added to the “Labyrinth” of existing regulatory obligations, we have seen Canadian G20 reporting go live in July, the introduction of branch reporting in Hong Kong, and closer to home we have seen changes to EMIR reporting brought about by the introduction of clearing obligations. To cap the year off, firms will need their own “Heroes” working during the holiday season to make sure they can go live with Bank of Israel reporting on 1 January 2017!

    “Ch-ch-ch-ch changes”

    In regulatory reporting that has only recently gone live, 2016 has seen “Changes” or consultations on changes to their obligations. In accordance with Article 85(1) EMIR, the European Commission launched a review of the legislation on 21 May 2015 and published its final report on 23 November 2016.  As a result, the Commission has committed to a legislative review of EMIR in 2017 which will include an attempt to streamline trade reporting requirements.  In the US, we have seen no action relief expirations for CFTC DFA (Dodd Frank Act) reporting and the advent of SEC reporting drawing closer. The election of Donald Trump aligned with a Republican majority in the US Congress could mean substantial changes with the repeal of certain sections of the DFA in 2017 a distinct possibility.

    “Ashes to Ashes” for MiFID I transaction reporting

    As transaction reporting under MiFID I enters its final year, throughout 2016 firms have found themselves “Under Pressure”, trying to prepare for the much more demanding and complex ask of MiFID II.  Both buy side and sell side firms have been grappling with their understanding of the obligations imposed by MiFIR Article 26, the supporting RTS 22 and final guidelines.  The final guidelines document published in October represents a substantial investment by ESMA and the competent authorities.  Ana Fernandes of the FCA’s Transaction Monitoring Unit stood in public and compared the physical size of TRUP to the MiFIR guidelines. Her conclusion –  they have invested significant time and effort in the drafting of the regulations and supporting guidelines and their expectations of the standard of reporting is higher than that of  regimes that have recently gone live.  Throughout 2016 firms have been busy digesting what is required of them to comply with MiFIR transaction reporting obligations, realising it is significantly more complex than either EMIR or DFA.  In short, the significant increase in complexity of MiFIR reporting combined with the greater scrutiny of regulators means MiFIR could prove all-consuming for firms in 2017.

    Data Quality? Everything is not “Hunky Dory”

    As the year ended, the industry received messages both from the FCA and ESMA about the quality of the data that is being reported to them. Ana Fernandes and Olga Petrenko both struck the same chord at last month’s Transaction Reporting Conference at the BBA when they called out the poor quality of data still being reported.  Ana outlined that reporting under MiFID I, now live for nine years, still has significant errors – something that we highlighted when we analysed transaction reporting fines earlier this year.  Olga explained that ESMA is still receiving complaints from other bodies such as central banks about the quality of the data they are receiving from the reports made under EMIR.  Consequently, ESMA will have the improvement of data quality as its primary objective of 2017.  Both bodies are investing heavily to develop the capacity to identify data quality issues where they will increasingly compare reports, use independent sources of data, and introducing ‘business’ validations to identify errors and hold firms accountable in meeting their obligations.

    If these years are to be the “Golden Years” of reporting and less a “labyrinth” of competing demands, then the industry needs to invest heavily in accurate advice and appropriate solutions throughout 2017 so the quality of the data they report meets the increasing expectations of the regulators.

    There’s a lot to do as we head into 2017 but to soften the blow perhaps have a listen to Bowie over the festive season.

    Thank you for your support in 2016 and we wish you a restful break with your friends and family.

    Seasons greetings from us all at Kaizen.

  • Updated EMIR trade reporting rules set stage for fines

    Updated EMIR trade reporting rules set stage for fines

    Kaizen’s CEO Dario Crispini spoke with Thomson Reuters Accelus about the revised EMIR trade reporting regime which aims to bring clarity to the regulatory technical standards first published in 2012.

    “Potentially the EMIR review is more important from an enforcement perspective than it is from an reporting perspective. I do expect to see some fines. The U.S regulators are further ahead and we will see some Dodd Frank fines first. The EMIR review does provide more of a legal platform for taking enforcement action across the various countries. It will be the enforcement processes of the relevant national competent authorities that are applied, which are not EU-wide,” Crispini said.

    The full article is available from Thomson Reuters Accelus, a subscription-only site.

    Extract

    One of the main reasons behind ESMA’s decision to revise the trade reporting RTS was to convert the guidance set out in the many Q&As and the level one and two validation processes into technical standards.

    The EMIR review brings new rules such as the RTS covering product identification and classification, as well as introducing clear obligations regarding unique trade identifier exchange and the timing of UTI exchange.

    “The EMIR review takes many guidelines published by ESMA in the Q&As and makes them regulations or secondary legislation that cannot be contested from an enforcement point of view. For example, if firms have not created a UTI according to the new guidelines, because they are now RTS, they can’t say it was only a guideline. It makes the enforcement process easier for each of the National Competent Authorities,” Crispini said.

    Link to original article

    Read Dario’s recent EMIR opinion piece on mandatory clearing: Why populating the clearing obligation field won’t be so easy

  • Five things we learned from the FCA’s MiFID II venue roundtable

    Five things we learned from the FCA’s MiFID II venue roundtable

    FCA’s MiFID II trading roundtable have been published. What did we learn?

    • ESMA Level 3 Q&As will not be published until the implementing measures are finalised. Given what now appears to be an inevitable delay of 12 months, the guidance could be significantly delayed as questions remain outstanding in several key areas such as transparency for non-equity securities.
    • The FCA advised that their own second MIFID II consultation paper was likely to be published in the middle of 2016. Again the exact timing of this depends upon the progress with the implementation measures.
    • Venues continue to stress concerns about the new obligations.  For example, where the entity utilising their services is not obliged to report and therefore creates an obligation upon the venue to report the activity executed to meet reporting obligations.  Further clarification is still required here however clearly this creates a significant onus upon the venues that does not exist today. The FCA did confirm as per their guidance that a venue would be expected to report such activity to their home member state.
    • The effective processing of transparency waivers is also a significant concern to venues. The FCA confirmed that interfaces are in place between it and ESMA which allow for batch processing to assist with the timely processing of waiver applications. Waivers will need to be in place for each venue for market participants to utilise the appropriate exemptions and deferrals from publication requirements.
    • Under AOB the FCA was questioned on the approach towards direct market access (DEA) by 3rd country clients (non-EEA). The FCA advised there are a couple of key considerations here. It confirmed questions have been raised with the European Commission about exemptions in Article 2.1 (d)  for those dealing on own account with DEA access based outside EU. With regards to firms based outside the EEA providing DEA access, the FCA confirmed that the consultation paper followed the Treasury implementation legislation which did not permit firms based outside the EEA from providing access to EEA trading venues.
  • Looking for some practical guidance on MiFID II reporting?

    Looking for some practical guidance on MiFID II reporting?

    Despite the year’s delay,  firms mustn’t take their foot off the accelerator when it comes to their MiFID II preparation.  The timing therefore couldn’t be better for the upcoming event: derstanding Transaction and Trade Reporting Under MiFID II: A Practical Guide to Implementation of the New Requirements on Wednesday 9 March.

    Our CEO Dario Crispini will join the expert speaker panel at the event along with Kaizen’s Senior Consultant Adrian Gill.

    The event, which is part of a two-year programme of MiFID II events run by City and Financial, will cover the following points:

    • Progress report on transaction reporting
    • Transaction reporting obligation on firms
    • Data readiness
    • Role of transmission and delegation
    • Products identifiers and product classification
    • Trading with non EEA firms
    • Establishing a control framework for MiFID II transaction reporting
    • ESMA guidance in the RTS
    • Identifying errors and omissions
    • Authenticating the source of transaction report
    • Avoiding over-reporting and under-reporting
    • Testing and reconciliations
    • Record-keeping obligation on firms
    • Transaction reporting obligation and Approved Reporting Mechanisms of trading venues
    • Obligation to provide financial investment data
    • Trade reporting – balancing the competing demands of transparency and liquidity under MiFID II
    • Implementation: timelines and problems.

    Where
    Clifford Chance, London

    Cost
    Delegate Fee: £395 + VAT

    Website and booking
    (Includes event programme, speaker list, registration fees etc)

    www.cityandfinancialconferences.com/MIFIDIITTR

    Alternative booking options:
    email bookings@cityandfinancial.com or call 01932 340115

  • It’s crystal ball time – regulatory reporting in 2016

    It’s crystal ball time – regulatory reporting in 2016

    As the memories of performances of A Christmas Carol fade, the ghosts of Christmas past, present and future are a useful analogy to convey the challenges firms will encounter in meeting their regulatory reporting obligations in 2016.

    From the past, MiFID reporting of the 2007 vintage still provides a real and present risk to firms. The present, in the form of EMIR and DFA reporting, will undergo changes to requirements. Looking to the future there are a number new obligations that are due (REMIT, Money Markets) and significantly, the highly likely delay of MiFIR/MIFID II to 2018. A common theme running through all obligations is the increasing levels of scrutiny from regulators and therefore of firms’ senior management.

    Past

    Despite all the focus and costs expended upon the new reporting obligations globally, still the most material risk to firms in getting their reporting wrong is UK transaction reporting required under MiFID since 2007. Last year we saw fines break new records, reaching GBP£13m and it is not inconceivable that in 2016 firms may receive higher fines. It is crucial that firms do not take their eyes off the ball so that they continue to adhere to legacy reporting requirements.

    Present

    The introduction of EMIR and DFA obligations over last few years is still fresh in the minds of regulators, trade repositories and firms. In 2015 EMIR reporting has seen significant change with ESMA mandating trade repositories to introduce much higher levels of validation on firms’ submissions. In the year ahead we expect to learn of further significant changes to EMIR reporting obligations as a result of both the consultation of 2015 and knock-on effects of EMIR clearing. For those firms who have a DFA reporting obligation, the later part of 2016 will see changes to CFTC Part 45 rules as part of the rewrite. Firms will need to plan for changes to obligations that have only very recently been introduced.

    Future

    Wherever you look, there are new reporting obligations with compliance dates in 2016. In the energy markets, REMIT OTC obligations are due in the second quarter. In the third quarter Switzerland is set to introduce its version of EMIR. Despite the advent of trade repositories, the central banks are requiring their own reports. In the second and third quarters of this year, the Bank of England and the European Central Bank are requiring money market reports. MiFIR/MIFID II is the one omission from the list, due to the highly likely scenario that it will be delayed from January 2017 to January 2018. Despite this delay preparation for the MiFIR requirements for transaction, trade reporting and instrument data reporting will dominate the change agenda for 2016/17.

    Common theme – increased scrutiny

    Regardless of whether the reporting obligation is a legacy requirement, recently introduced, or with a compliance date in 2016/17, the expectations and scrutiny of regulators is only on an increased trajectory. As such, expect increased fines for those more mature reporting regimes (MiFID). For more recent regimes, fines (DFA) have already been issued or greater scrutiny from regulatory bodies is becoming evident (EMIR). Future reporting regimes will be expected to hit the ground running with high quality reports expected from the get-go. The importance of ensuring correct reporting has never been as important to firms and the financial system as a whole.

  • Finally it’s out, proposed 12 month delay to MiFID II

    Finally it’s out, proposed 12 month delay to MiFID II

    The industry has been mooting a delay to MiFID II for some time now and there were elliptical comments by the FCA and ESMA representatives at the recent FCA conference hinting at an appetite for a delay.  Now, a one year delay was proposed at a hearing of the European Commission’s Committee on Economic and Monetary Affairs yesterday.

    In a statement, MEP Markus Ferber, Rapporteur for MiFID II, blamed ESMA and the European Commission for “dawdling time and again…………responsible for the delays are solely ESMA and the Commission.”

    In a speech by Steve Maijoor to EU institutions published today he raises the need for legislative measures to delay MiFID II principally due to the amount of preparatory work required for building both the rules and IT required for its implementation.

    For a delay, an amendment to the level 1 text will have to be agreed. With today’s announcements that looks extremely likely however it has to be stressed that the European Commission has said only that they are thinking about a delay.

    An additional 12 months would be a boon to firms struggling with implementation.  A delay will mean that there is more time for middleware and service providers to develop their offerings allowing firms to have more clarity on their implementation options.

    A delay may very well result in higher project costs for firms as the projects are extended out but overall they will be better placed to make their preparations.  That said, there will be little appetite for late or poor implementation by firms particularly when it comes to transaction reporting quality.  An extra year would mean that firms now have everything they wanted for the implementation so regulators will expect them to get it right.

  • Latest EMIR Q&A update looks like a major headache for Trade Repositories…

    Latest EMIR Q&A update looks like a major headache for Trade Repositories…

    ESMA’s latest update of its EMIR Q&A document requires reporting entities (or the party to which they have delegated reporting) to notify their trade repository when there is a change in their identifier.

    This means either:

    • A change in their Legal Entity Identifier (LEI) due to a merger or acquisition, or
    • Where the entity obtains an LEI when they previously reported another code (BIC or internal code).

    Once notified of the change, the Trade Repository is to notify the other repositories and update all open trades with the new value by replacing the old value in all the identifier fields where it had previously been used.  The Trade Repository is then to notify all the counterparties to the modified trades, as well as regulators.

    Why is this being introduced now?

    Level 2 validations take effect from November. The validations will affect updates to any open trades in the repositories where a BIC or internal code has been used to identify the reporting entity. Furthermore, there will always be corporate activity resulting in a need to change identifiers.

    The guidance provided is not as clear as it should be. On my reading, the Trade Repositories are to update all the open trades where the party changing the LEI is the ‘counterparty’ or ‘other counterparty’. I could be wrong on this but if so, the guidance needs to be updated.

    Major headache

    I am not sure how the Trade Repositories will like this change as they are required to amend client records quite substantially which introduces processing risk. Further, it is highly likely that client records will get out of synch with those at the Trade Repositories. I can’t see it as being anything other than a major headache for them particularly if they are to contact all the counterparties to trades where the reporting entity’s identifier has changed.

  • Obligation to use LEIs picks up pace

    Obligation to use LEIs picks up pace

    LEIs are already required when reporting under EMIR but their use is to be mandatory from 2015 under COREREP and FINREP.

    The EBA published its recommendations on use of LEIs in regulatory reporting and the FCA has adopted the recommended approach. This means that UK firms must have registered both themselves and group companies for an LEI by the end of the year. They are required for COREREP and FINREP submissions for both the reporting firm and any relevant group entities when submitting on a consolidated basis. LEIs are also to be used to identify counterparties when reporting where an LEI has been issued for the counterparty.

    Firms are advised to obtain an LEI from a local operating unit and the FCA expect firms to register their LEIs immediately upon receipt using the FCA survey tool.

    They have become regulators’ entity identifier of choice so we can expect to see it as mandatory for a range of reporting obligations not least under MiFID II and Security Finance Transaction Reporting.