Tag: David Nowell

  • FIRDS: Are trading venues contributing to poor quality transaction reporting?

    FIRDS: Are trading venues contributing to poor quality transaction reporting?

    Perhaps the biggest irony about MiFIR transaction reporting is that reports submitted by investment firms need to be complete and accurate, but ESMA states it cannot provide any guarantee that one of the key tools firms need to do this, the ESMA FIRDS reference database, is “complete, accurate or up-to-date”. This is particularly harsh on firms as they can report with the correct ISIN to identify the financial instrument, but if that ISIN (or underlying ISIN) is not on the FIRDS database within seven calendar days, then the report will be rejected by the competent authority. The onus is then on the firm to investigate whether they should re-submit the report.

    This is unfair on firms as most of them are trying to do the right thing by only reporting transactions in instruments that are reportable, but they are frustrated with limitations of ESMA’s FIRDS database. It would be easy to blame ESMA for this, but I believe that also is unfair. The quality of FIRDS can only ever be as good as the information submitted to it and it is the EEA trading venues that are obliged to submit this data through the requirements detailed in RTS 23. The quality of FIRDS data has improved dramatically since go-live, as you would expect over the course of two years, and many trading venues may be reporting perfectly. However, other trading venues are not, and deficiencies in this reference data was highlighted in Germany’s Ministry of Finance’s position paper on MiFID and MiFIR.

    Germany’s Ministry of Finance concludes that “ further analysis is needed on the question of how to ensure the provision of accurate, reliable and timely reference data. The analysis should also explore ways to make FIRDS the golden source for reference data.” Well I’m sure we all know the obvious answer to this one – there is nothing quite like a sanction, perhaps in the form of a fine and public censure, to ensure data quality is taken more seriously. We have seen sanctions used for firms’ poor transaction reporting and how this can focus attention, so maybe trading venues need to be wary of the possibility of sanctions if they don’t improve the quality of their reference data. If you are a trading venue that has doubts about the quality of its reference data, now might be a good time to look at quality assurance solutions.

    The quality of FIRDS data also impacts the thorny issue of the ESMA opinion paper on OTC derivatives traded on a trading venue. In this paper, ESMA expands the reportable instrument set to include “OTC derivatives sharing the same reference data details as the derivatives traded on a trading venue”. This paper has caused much consternation in the industry. Whilst some firms have paid as much attention to the opinion paper as a London cyclist does to a red light, many other firms are desperately trying to do the right thing in trying to match the reference data attributes of their OTC derivatives against the attributes of derivatives on the FIRDS database to see if they are reportable. The quality of the FIRDS data, and the flexibility of FIRDS itself, often makes this a frustrating and imprecise task. This appears particularly true for FX and interest rate derivatives and prompts the question (also asked by Germany’s Ministry of Finance) of whether the concept of ‘traded on a trading venue’ should be applied to OTC derivatives. Anybody who thinks it should, needs to try assessing whether some OTC FX swaps are reportable or not. They would probably find that they first need to match attributes against the ANNA Derivatives Service Bureau to find potential ISINs and then compare the attributes associated with these ISINs against FIRDS to see if the instruments are reportable (not forgetting to check if the underlying forwards have reportable ISINs). They may well struggle with the flexibility of FIRDS in this task and may possibly be perplexed by the quality of much of the data – for example, the lack of consistency between the financial instrument long name and the attributes, particularly the expiry date. 

    Whilst the MiFIR definition of reportable instruments appears easy on paper (MiFIR Article 26(2)), there is plenty of devil in the detail and many firms struggle to fully understand them. These firms are unlikely to understand the implications of the ESMA ToTV opinion paper and it does appear to be too complex a requirement for the associated regulatory benefit. The current data quality and flexibility of FIRDS does not seem fully adequate to support this requirement. More importantly, it appears that the quality of FIRDS reference data may be causing issues with the overall quality of transaction reporting. Whilst many trading venues are on top of the task of their RTS 23 reporting, it appears that some trading venues need to up their game to avoid regulatory attention.

    If you’re worried about the quality of your reported data, this is why we here at Kaizen exist. Our accuracy testing and reference data testing services check all data fields in every trade or transaction report submitted to the regulator so you have a full picture of the quality of your reporting.  Contact us for a discussion on how we can help. Join in the conversation over on our LinkedIn.

  • Video: David Nowell on what is happening with EMIR Trade Reporting

    Video: David Nowell on what is happening with EMIR Trade Reporting

    In this video, David Nowell answers the below questions:

    • Why is EMIR important?
    • Following recent comments from ESMA about the FCA and other NCAs, what changes are we likely to see?
    • What do the changes mean for financial firms?
    • What are the key changes from the recent EMIR re-fit?

    If you need help with your EMIR Trade Reporting data quality, get in touch.

  • Video: David Nowell on MiFID II reporting

    Video: David Nowell on MiFID II reporting

    Kaizen’s Senior Regulatory Reporting Specialist David Nowell provides us with his view on:

    • What the regulators will be expecting now on MiFID II reporting
    • How investment firms can ensure reporting accuracy

    Read David’s blog MiFID II 2nd anniversary – ready for the terrible twos?

    Thank you to the Wealth Mosaic. 

  • Kaizen Reporting in the news 2019

    Kaizen Reporting in the news 2019

    20 December 2019: Dario Crispini spoke to Drew Nicol at Securities Lending Times – UK’s FCA predicted to ramp-up non-compliance fines in 2020

    18 December 2019: Dario Crispini spoke to Luke Jeffs at FOW – FCA to “dramatically increase” scrutiny in 2020 – expert

    28 November 2019: David Nowell spoke to Alice Tchernookova at Practice Insight (IFLR) – MiFID II’s review path ahead.

    28 November 2019: David Nowell spoke to Hugo Bromley at Practice Insight (IFLR) – Away from equities: MiFID II, Priips struggle in fixed income, derivatives

    23 October 2019: Ian Rennie spoke to Alice Tchernookova at Practice Insight (IFLR) – FCA: Buyside ‘miles behind’ on SMCR journey.

    22 October 2019: Jonathan Lee spoke to Lynn Strongin Dodds at Best Execution – The long and winding road of SFTR.

    12 September 2019: David Nowell spoke to Thomas Helm at Practice Insight (IFLR) – Special report: Transparency makes markets safer but more complex.

    4 September 2019: David Nowell spoke to James Thursfield at FOW – German consultation positions FIRDS as potential golden source.

    25 July 2019: David Nowell spoke to Alice Tchernookova at Practice Insight (IFLR) – Industry bemoans ‘excessive’ rules.

    11 July 2019: David Nowell spoke to Alice Tchernookova at Practice insight (IFLR) – Emir refit: frustration hits the industry as new rules come in.

    11 July 2019: David Nowell spoke to Gill Wadsworth at Best Execution – The Long Goodbye.

    5 July 2019: David Nowell spoke to Rachel Wolcott at Thomson Reuters – ESMA says 40% of EMIR trade reports match; sceptical reporting specialists say rate likely much lower.

    1 July 2019: David Nowell spoke to Fraser Tennant at Financier Worldwide – Transaction reporting: the importance of getting it right.

    12 June 2019: Chris Machin spoke to Louisa Chender at FOW – Consolidated tape post-Brexit could create competition, costs.

    5 June 2019: David Nowell spoke to Justin Pugsley at Global Risk Regulator – Consequences of MiFID still unfolding ahead of pending review.

    30 May 2019: David Nowell spoke to Louisa Chender at FOW – Essential Mifid II tool not yet accurate.

    14 May 2019: David Nowell spoke to David Braid at Practice Insight – Goldman/UBS fines sharpen Mifid reporting compliance.

    7 May 2019: David Nowell spoke to Thomas Helm at Practice Insight – Buyside at risk of Emir reporting fines.

    5 May 2019: Dario Crispini spoke to Nickolas Pratt at Funds Europe – Asset servicing: Avoid a transaction reporting fine.

    28 March 2019: Dario Crispini spoke to Louisa Chender at FOW – Goldman Sachs fined £34.3 million for reporting failures.

    19 March 2019: David Nowell spoke to Hayley MCdowell at The Trade – UBS fined £27.6 million for MiFID reporting failures.

    19 March 2019: Ian Rennie spoke to Louisa Chender at FOW – UBS slapped with £27.6 million fine for reporting flaws.

    14 March 2019: David Nowell spoke to Thomas Helm at Practice Insight – Mifid II: UK firms start receiving FCA letters.

    8 February 2019: Jonathan Lee spoke to Rebekah Tunstead at Bob’s Guide – Banks pressurize trading venues for SFTR filing clarity.

    1 February 2019: Dario Crispini spoke to Rachel Wolcott at Thomson Reuters – Workload to prepare transaction reporting for Brexit is equivalent to MiFID II go live.

    29 January 2019: Jonathan Lee spoke to Sharon Kimathi at Practice Insight – SFTR: banks anxious about delegated reporting.

    14 January 2019: David Nowell contributed an article for Global Risk Regulatory – Issues remain one year on from MiFIR transaction reporting going live.

    11 January 2019: Jonathan Lee spoke to Olly Jackson at International Financial Law Review – SFTR: market sill needs critical data.

    3 January 2019: David Nowell spoke to Louisa Chender at FOW – Mifid II reporting issues linger one year on.

  • No market abuse sanctions by FCA in 2018

    No market abuse sanctions by FCA in 2018

    ESMA has published its peer review on how national competent authorities handle suspicious transactions and orders reports (STORs) under the Market Abuse Regulation. It is fully compliant in four of the ESMA metrics and broadly compliant in the other two.  So congratulations FCA – pretty much top of the league in this review.

    However, what is interesting is that despite this near-perfect report card, the FCA has not imposed any measures and sanctions on firms.  Surely the true measurement has to be the number of successful market abuse cases the regulator has brought? The ESMA report has a handy table showing the number of measures and sanctions imposed for market abuse infringements and the UK figures for 2018 show no sanctions.

    Without wanting to appear like the Christmas Grinch, in our view this is a very disappointing figure. Bearing in mind that 2018 marked the introduction of a dramatically more complex transaction reporting regime which offers regulators a far richer data set to monitor market abuse more effectively, this failure to sanction would indicate to us that something isn’t right.

    Whilst many firms are making great efforts to report STORs and to submit transaction reports, the FCA can only do its job effectively if those transaction reports are complete and accurate. If you are not completely confident that your transaction reports meet this requirement, talk to us about our ReportShield™ data quality, reconciliation and training services.

    What do you think about this peer review from ESMA? Join in the conversation over on our LinkedIn.

  • Join us at Infoline’s Trade and Transaction Reporting Conference in Stockholm

    Join us at Infoline’s Trade and Transaction Reporting Conference in Stockholm

    We are delighted to be able to offer 30% off tickets. Use code FKM63769KAIZEN.

    Register

     

    Calling all investment firms, securities firms, banks and trading venues impacted by the reporting and disclosure obligations of SFTR, MiFIR and EMIR! Please join us at this one day conference in Stockholm. Don’t miss our Senior Regulatory Reporting Specialist, Jonathan Lee, discussing SFTR Reporting best practice and how to prepare for the April 2020 go-live at 10:30am. Followed by Senior Regulatory Reporting Specialist, David Nowell, on a panel to discuss the ongoing challenges with MiFID II Transaction Reporting and EMIR Trade Reporting. 

  • ESMA clarifies FX forwards transaction reporting in new MiFIR Q&A

    ESMA clarifies FX forwards transaction reporting in new MiFIR Q&A

    ESMA has provided a very useful example of how to report FX forwards in its latest Q&A on MiFIR data reporting. In particular, we would urge firms to take note on the practice of populating the ‘quantity’ and ‘price’ fields:

    • The ‘quantity’ (and ‘quantity currency’) should reflect the amount of the FX forwards in the base currency
    • The ‘price’ (and ‘price currency) should show the forward rate expressed as a price of base currency in the quoted The monetary value XML tag should be used (if reporting to an ARM in flat file, ‘price type’ is monetary value.

    The only additional changes appear to be in the table of national identifier formats. This details a change in the format of Portuguese passports issued after April 2018 and corrections to the Romanian National Identification Number and national passport formats.

    Whilst the new MiFIR Q&A signals only relatively minor changes, it clearly demonstrates the need for firms to remain on top of regulatory developments. Our regulatory reporting training courses help firms stay abreast of the reporting requirements and help identify any interpretational errors. For further details, please see our training courses.

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

  • In the news: David Nowell and Chris Machin speak to FOW

    In the news: David Nowell and Chris Machin speak to FOW

    Our Senior Regulatory Reporting Specialists David Nowell and Chris Machin recently sat down with James Thursfield from FOW to discuss the results of the German Ministry of Finance industry consultation. The article highlights the need for a golden source for reference data and the role of the FIRDS database.

    “The regulators are well aware of deficiencies with the FIRDS reference data and already state that it cannot be relied to be complete, accurate and up-to-date,” Nowell told FOW. 

    “Esma has always, even before go-live, stated that they would not be the Golden Source (even if de-facto they actually are) and no solution has been suggested,” Machin said.

    Read the full interview.

  • In the news: David Nowell speaks to Practice Insight on regulatory change

    In the news: David Nowell speaks to Practice Insight on regulatory change

    Senior Regulatory Reporting Specialist David Nowell spoke to Alice Tchernookova from International Financial Law Review’s publication Practice Insight about the future of regulation now that MiFID II has bedded down within the industry. 

    “We have almost reached a stage where we must ask ourselves whether being fully compliant is actually possible,” said David Nowell.

    Read the full article. 

  • ESMA fines trade repository for data delivery breaches

    ESMA has announced it has fined a trade repository for failing to provide regulators direct and immediate access to details of derivative contracts. The failures relate to trade terminations and valuations and collateral updates for the period from the start of EMIR trade reporting go live in February 2016 through to October of the same year. According to the public notice, ESMA remained unaware of the error until it was informed by the Dutch national competent authority (NCA) in July 2016.

    The fine should be a reminder to all industry participants that ESMA takes EMIR trade reporting very seriously. ESMA and the NCAs also have a ‘Data Quality Action Plan’ to address quality issues in EMIR trade reports submitted by firms.

    If you are in any doubt whether your reports meet the standards required by the regulators, please get in contact with us to discuss your EMIR data quality. The FCA has already issued a £34.5m fine for EMIR reporting breaches – we can help you put the right controls in place to make sure that you are not at risk too.

  • MiFIR versus EMIR – which is the most important reporting regime?

    MiFIR versus EMIR – which is the most important reporting regime?

    There are many similarities between the MiFIR transaction reporting and EMIR trade reporting requirements. Both are T+1 reporting regimes and there is a large overlap in the instrument set that they cover. However, there are distinct regulatory drivers behind each regime: MiFIR transaction reporting is primarily used to detect market abuse whilst EMIR trade reporting is used primarily to monitor for systemic risk.

    There is no doubt that combating market abuse is a very important regulatory service; everybody benefits from clean markets. Complete and accurate transaction reports are vital to help the regulators perform this task effectively. However, systemic risk is even more important as it represents the risk of collapse of the entire financial system -there is no point monitoring for market abuse if the financial system has collapsed around you.

    It is very interesting therefore to compare the number of errors and omissions forms for MiFIR breaches against the number of equivalent forms for EMIR trade reporting breaches. Statistics from the UK Financial Conduct Authority (FCA) obtained through a Freedom of Information Act request show that it received notifications from 384 firms MiFIR transaction reporting breaches since go-live compared to a paltry 75 for EMIR trade reporting in the period since Q2 2018 when the EMIR breach form became available. So, it is tempting to believe that firms recognise the relative importance of EMIR trade reporting and are making greater efforts to ensure the accuracy of data they report. Sadly, this is not the case. At Kaizen, we perform data quality checks on firms’ transaction reports and trade reports. For EMIR we initially find that a much lower number of EMIR trade reports are accurate than compared with the MiFIR reports we test. This reflects the complexity of the reporting regime, but we find firms’ reporting quality rapidly improves once we have highlighted and explained the errors to them.

    So this presents an apparent anomaly. The evidence suggests the quality of EMIR trade reports is at a lower level than the quality of MiFIR transaction reports, yet over five times as many firms have notified the FCA of MiFIR transaction reporting errors than they have for EMIR trade reporting. It is not difficult to understand why this is the case; the FCA is constantly reminding the industry on the need to notify them of MiFIR transaction reporting breaches, and to correct those errors, but it appears to be comparatively silent on the need to notify them of EMIR reporting breaches. What is more difficult to understand is why the FCA appears to be less active in meeting its G20 commitments in ensuring the same level of high quality in EMIR trade reporting data.

    If you’re concerned about the quality of your MiFIR transaction reporting data or EMIR trade reporting data or would simply like confirmation that it is accurate and complete, please get in touch for a complementary consultation with one of our regulatory experts.

  • Ten steps to MiFIR transaction reporting nirvana

    Ten steps to MiFIR transaction reporting nirvana

    Firms face a daunting array of complex regulatory requirements, but one of the most fiendishly difficult to comply with appears to be transaction reporting. The recent substantial fines levied by the UK Financial Conduct Authority (FCA) showed that even tier-one firms have difficulty meeting the transaction reporting requirements. Considering that these breaches relate to the previous Markets in Financial Instruments Directive (MiFID) reporting regime, firms are becoming increasingly perplexed about how to meet the far more complex Markets in Financial Instruments Regulation (MIFIR) transaction reporting regime. While regulators continue to stress the importance of complete and accurate transaction reporting, the following 10-point path can lead firms closer to transaction reporting nirvana:

    1. Do not be in denial about the costs of doing business

    Budgets are tight everywhere, but investment firms need adequate resources to meet the regulatory requirements, and transaction reporting is one of the most important of these.

    2. Do not under-estimate the costs of remediation

    Being fined by the FCA is never pleasant, but despite recent evidence, fines are likely to remain an exceptional outcome. The regulator is, however, likely to make firms correct and back-report everything they have got wrong. The cost of this remediation will probably far outweigh that of establishing systems and controls to help avoid mistakes and in some cases may even cost more that the fine itself. In addition, if the FCA feels a firm has insufficient controls in place then it can impose a costly skilled persons review under s166 of the Financial Services and Markets Act 2000.

    3. Training.

    This is probably the quickest and cheapest win. In our experience, many of the mistakes firms make with their reporting stem from a basic misunderstanding of the requirements. They are not simple and one mistake resulting from inadequate training can lead to millions of incorrect transaction reports.

    4. Valid does not necessarily mean correct

    This is why we here at Kaizen exist. The regulators apply an extensive validation check on all the reports they receive. There is, therefore, a natural inclination for firms to believe that if a report passes the validation then it must be correct. This is not the case. Our accuracy testing finds that around 70% of reports which passed the validation checks contain at least one error.

    5. Quality assurance checks are essential

    Not least because it is the law: one of the requirements of the “methods and arrangements” for reporting set out in Article 15 of the Regulatory Technical Standards (RTS) 22. It is also one of the main requirements necessary for firms to be confident that their reports are accurate and ensure they do not perpetuate errors.

    6. Firms must not mark their own homework

    Using an independent quality assurance service to test every submitted transaction report will provide a thorough, impartial analysis giving absolute certainty about the state of the firm’s reporting.

    7. Reconcile trades from front-office systems to records received by the regulator

    This is a hard and fast requirement clearly stated in RTS 22. Some firms mistakenly believe this simply involves checking that the number of trades concluded matches the number of reports received by the regulator. This is simply not good enough. The reconciliation must include checking “the accuracy and completeness of the individual data fields and their compliance with the standards and formats specified in Table 2 of Annex I.”  The FCA actively monitors whether firms have requested data from it to complete this check, and so any firm failing to perform this end-to-end reconciliation will be on the regulator’s radar.

    8. Heed the words of the regulator

    The FCA does not really want to sanction firms; it would much prefer that firms’ reports were complete and accurate so that it could do its job of monitoring for market abuse. The regulator sends a consistent and strong message to firms about what they need to do to achieve this goal, which firms must heed. The core message is that firms need adequate systems and controls for transaction reporting. This starts with a solid governance framework, supported by reconciliation and a data accuracy checking. The FCA also publishes information about many of the significant failings it sees, and its latest Market Watch 59 identifies the following errors:

    • Incorrect time (especially after the transition to British Summer Time).
    • Price not reported in the major currency.
    • Re-use of identifiers for multiple clients.
    • Incorrect client type code.
    • Inconsistency between trading capacity and buyer/seller IDs
    • Transposition of the “buyer” and “seller” identifiers.

    9. Get market identifier codes right

    It might sound innocuous, but the correct venue field is very important due to the associated validation and data accuracy checks. One of the most common mistakes is using an “operating level” market identifier code (MIC) rather than the correct segment-level MIC. This can result in the firm’s report eventually being rejected by the regulator because the instrument identifier is associated with the segment MIC rather than operational-level MIC. It can also affect how the firm populates other fields such as “country of branch membership”.

    10. Do not be afraid to submit an “errors and omissions” form

    The regulatory sky will not fall in if a firm submits an errors and omissions form. The FCA has reported that it has so far received around 1,300 errors and omissions forms from more than 390 firms, so those firms which do decide to report will not be alone. Failure to submit this form at the right time can, however, land firms in a lot more trouble: the FCA noted in Market Watch 59 that it is unhappy about firms making corrections without first submitting the form.

    MiFIR transaction reporting is a very complex requirement which firms almost universally find difficult to meet (whisper it quietly, but some competent authorities have had their own difficulties too). Failure to make complete and accurate reports will result in costly remediation issues and can prove risky for the senior manager in charge of transaction reporting. Taking due note of the 10 points above will help firms reach their transaction reporting nirvana.

    For more information on any of the points above, please get in touch for a conversation with one of our regulatory experts. 

    This article was first published by Thomson Reuters Regulatory Intelligence on 7 June 2019.

  • EMIR Refit – white elephant regulation

    EMIR Refit – white elephant regulation

    Many firms are waking up to the fact that ‘EMIR Refit’ is being implemented on 17 June 2019 and they may be having a coronary over how it might impact EMIR trade reporting. For once, firms can relax as the only big(ish) change for trade reporting takes effect from June 2020.

    Before diving into the detail, let’s take a step back and remind ourselves what EMIR Refit is all about.

    The aim of EMIR Refit is to make its compliance burden more proportionate, particularly for the non-financial counterparties (NFCs). Now that is an absolutely splendid aim, so how has it worked out with trade reporting? After the colossal amount of time spent on the debate, I have to conclude that it’s a massive disappointment for reporting, resulting in the following meagre pickings:

    1. Mandatory delegated reporting on behalf of NFC- firms from 18 June 2020. This is the only meaningful change from Refit. From 18 June 2020 (repeat 2020, not 2019) ‘financial counterparties’ will become responsible and legally liable for reporting the details of derivative contracts they have concluded with an NFC-  on behalf of both. The NFC- can still choose to report on its own behalf if it wants to, but it must give its counterparty notice of its intentions to avoid duplicative reporting.
    2. Removal of the back-loading obligation. There is no longer an obligation for counterparties to report historic data on derivatives that were outstanding on or after 16 August 2012 and which terminated before the EMIR reporting start date of 12 February 2014. This might sound like a welcome dispensation for the industry, but it wasn’t a very practical requirement in the first place – what possible value could the regulators extract from trades terminated five years in the past? The revised reporting technical standards also virtually forced this change as it is highly unlikely that any counterparty will have the required information to report these ancient trades in the post-2017 standards.
    3. Intra-Group Exemption – There may be too many conditions to be met for this to be of much use, but an exemption from the reporting obligation is available for intra-group transactions where all the following criteria are met:
      • at least one counterparty is an NFC;
      • both counterparties are fully consolidated;
      • both counterparties are subject to appropriate centralised risk evaluation, measurement and control procedures;
      • the parent undertaking is not a financial counterparty.

    Additionally, counterparties must notify their NCA of their intention to apply this exemption

    1. Fund management company reporting obligations. Fund management companies and Alternative Investment Fund Managers will become solely responsible and liable for reporting derivative trades made by their UCITS, AIFs and institutions for occupational retirement provision.

    Delegated reporting

    So the only substantial change to trade reporting introduced by EMIR Refit is the mandatory delegated reporting by financial counterparties on behalf of their NFC minuses. Although many financial counterparties provide delegated reporting already, they will be concerned by the addition of legal responsibility for the accuracy of the delegated reporting they provide. This concern may highlight one of the loopholes of EMIR trade reporting – although delegated reporting may boost the pairing rates, it might not actually be very good. There is a great temptation to simply ‘flip’ elements of a trade report and present this as delegated reporting on behalf of the counterparty. The true requirements of delegated reporting could be far more onerous, particularly with the increased complexity of many elements introduced in the 2017 revised reporting technical standards. This is evidenced by Refit stressing the obligation on the NFC- firms to supply all the required information to their financial counterparties in order for them to report accurately on their behalf.

    It is also questionable whether the mandatory delegated reporting will help the NFC- firms that much. It will only work as planned if all their counterparties are EU firms. Many of their current counterparties may already be non-EU counterparties, so they will have to maintain their trade reporting infrastructure. Of course, a hard Brexit would seriously negate the value of this new measure as ESMA would not have any power to force a UK financial counterparty to provide delegated reporting for a non-EU NFC- (but maybe it could force the NFC- to only deal with EU firms).

    A lost opportunity

    Many firms had hoped that the Commission’s review of EMIR during 2015 and 2016 could lead to fundamental changes in the trade reporting requirements. Expectations included the removal of ETDs from the reporting obligation and the removal of the dual-sided reporting obligation. At the very least, many financial counterparties hoped that the review would lead to the removal of the obligation to report individual ETD trades and to rely on the end-of-day position reports. Since the main purpose of EMIR trade reporting is to monitor for systemic risk, there appears to be little value in collecting reports of ETD trades when they are immediately netted into an end of day position report. Additionally, key elements of EMIR trade reporting like lifecycle events and collateral reporting can only really be sensibly applied to the end of day positions for ETDs. Perhaps the only value of ETD trade reports is for the detection of market abuse – but this is the driver behind MiFIR transaction reporting and their inclusion in EMIR is expensive duplication.

    If the purpose of EMIR Refit is to address disproportionate compliance costs and to streamline reporting, then it can only be described as a lost opportunity. The existing EMIR trade reporting regime might be considered white elephant regulation – expensive and onerous to comply with, yet difficult to understand how it meets its objectives. Even the November 2017 revisions failed to disguise the fact that ETDs have been shoe-horned into reporting regime primarily designed around OTC derivatives.

    If you have concerns about whether you are meeting your EMIR trade reporting requirements or would like confirmation your reporting is accurate and complete, please get in touch with us for a conversation with one of regulatory experts.

  • ESMA publishes new EMIR Q&A

    ESMA publishes new EMIR Q&A

    With ESMA publishing documents faster than it’s possible to read them, we ‘welcome’ another EMIR Q&A today. The good news for reporting is that it mainly impacts clearing and there are only two amendments in the trade reporting section.

    The first of these comes in TR Question 36 – the reporting of OTC derivative notations. This is a simple clarification from ESMA, stating that:

    “For reporting purposes, only instances where a counterparty (being a CCP or another counterparty) steps into the derivative contract and becomes a new counterparty to the derivative contract should be reported with Action Type “New”. For the original report relating to the existing transaction derivative, counterparties should send a termination report marked as ’C= Early termination’, completing the field “Termination date”. The remaining counterparty and the new counterparty should then send a new report with action type “New” relating to the new transaction derivative.”

    So, there’s some new words in TR Question 36, but no change to reporting.

    The second change impacts TR Question 42 – population of ‘Clearing Obligation’ and ‘Cleared’ (fields 2.34 & 2.35) – and this marks a welcome simplification with the new instructions becoming applicable from 17 June 2019. The implementation of EMIR Refit removes obsolete references to frontloading leaving the remaining instructions far more digestible:

    “The field [Clearing Obligation] should be populated in following way: 

    • The field is not applicable to the transactions executed on a regulated market and should be left blank
    • In the case of cleared trades, the field “Clearing obligation” should be populated with “N” and the field “Cleared” – with “Y.”

    Even with the Q&A, understanding how to trade report correctly under EMIR can be a complicated and perplexing task. At Kaizen, we find many of the mistakes firms make with their reporting stem from a basic misunderstanding of the requirements.

    If you want to unravel the mysteries of EMIR trade reporting and avoid the potential pitfalls leading to breaches, why not attend one of our CPD and CISI accredited courses. In our experience, a small investment in training can help avoid costly remediation at a later stage.

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

  • Lack of training results in transaction reporting breaches

    Lack of training results in transaction reporting breaches

    One of the most interesting statements from the FCA Final Notices following the recent fines for MiFID transaction reporting breaches concerned the general lack of expertise around transaction reporting in the industry. The firm impacted was clearly trying to do the right thing, but was hampered by “…a scarcity across the Firm and the industry of personnel with the expertise and systems knowledge required both to implement the enhanced controls and remediate the issues identified during the course of the project”¹ 

    It is difficult to understand why this lack of expertise should still afflict such an important area of compliance. Whilst it may not appear to be the most glamourous area of regulation, the FCA has shown a continued willingness to take action against firms for breaches. Many of the errors highlighted by the FCA appear to have been simple mistakes in the interpretation of the reporting requirements and might have been avoided through a more effective training programme. It should also be remembered that these fines relate to the old MiFID transaction reporting which is relatively simple compared to the greatly increased scope and complexity of the current MiFIR transaction reporting regime.

    Help is at hand

    At Kaizen, we believe effective training is an essential element in ensuring complete and accurate transaction reporting. We offer a half day CPD-accredited training course, endorsed by the Chartered Institute for Securities and Investment (CISI), which gives candidates a core understanding of the transaction reporting requirements and the fields that comprise a transaction report. The course can be taken at Kaizen HQ or at your own offices and is accompanied by an exam which enables you to demonstrate your understanding of the reporting requirements. Similar courses are available for EMIR trade reporting and SFTR. Visit our training page for further details and to book your place on one of our upcoming scheduled dates. 

    Are you a Transaction Reporting guru? Why not take part in #TransactionReportingTuesday over on LinkedIn.

    Every Tuesday, on the Kaizen LinkedIn we will be publishing a MiFIR Transaction Reporting question from our training exam. The answer will be posted a week later along with a new question. 


    ¹ FCA Final Notice to Goldman Sachs

  • Second fine for transaction reporting breaches in two weeks is a record £34.3m

    Second fine for transaction reporting breaches in two weeks is a record £34.3m

    The FCA has issued a record fine of £34.3m for incorrect transaction reporting, hot on the heels of a fine two weeks ago for similar breaches. 

    According to the FCA, the firm in question failed to provide accurate and timely reporting relating to 220.2 million transaction reports between November 2007 and March 2017.

    If any firm doubts the FCA’s resolve in its pursuit of complete and accurate transaction reporting, they need to take note of these fines and the accompanying warning from Mark Steward, the FCA’s Director of Enforcement:

    ‘The failings in this case demonstrate a failure over an extended period to manage and test controls that are vitally important to the integrity of our markets. These were serious and prolonged failures. We expect all firms will take this opportunity to ensure they can fully detail their activity and are regularly checking their systems so any problems are detected and remedied promptly, unlike in this case.’

    The two recent fines are almost double the amount of the previous 12 fines for MiFID reporting combined.

    What went wrong?

    The FCA’s Final Notice tells a very familiar tale of what happens when a complex organisation, acting in good faith, attempts to deliver upon these very complex regulatory obligations; a significant, material, and widespread set of issues left undetected for many years.

    The key message is that these errors result from inadequate systems and controls over transaction reporting. In particular, the FCA found issues with:

    1. Change management
    2. Accuracy and completeness controls – again signalling issues with an approach that only tests data samples
    3. Reference Data – identification of counterparties

    The FCA is evidently tired of sounding like a broken record as these three control issues continually result in transaction reporting failings. The message should be familiar to firms and their SMCR managers responsible for reporting.  It’s not a secret that if firms don’t test the accuracy of their reporting, don’t test their reference data and change management processes, and don’t have adequate reconciliation from front office systems to the reports received by the FCA, then they cannot have confidence their reporting is correct.

    Lessons for MiFIR transaction reporting

    It is important to note that both fines are for failures under the previous MiFID transaction reporting regime. It is possible that this now marks the end of sanctions for the MiFID reporting regime and that the FCA’s focus will turn to the MiFIR reporting regime which is considerably more complex than the MiFID reporting regime. The FCA has already warned about the unsatisfactory quality of some transaction reporting under the new regime and the potential future consequences. There are many more things that can go wrong under the new regime and it is essential that firms are confident that they have adequate controls over their transaction reporting. Firms need to take note that the reference period for this fine’s transaction reporting breaches started on 5 November 2007 – the very first day of the MiFID transaction reporting; no grace period. 

    Get peace of mind in your reporting quality

    Our blog about the fine two weeks ago asks ‘could it have been you?’ and if you have any doubt, it is important to act now.  These two fines should be a wake up call for senior managers to get their reporting controls up to standard – and fast. 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 MiFIR, EMIR, Dodd-Frank or another G20 regulation.

    Our ReportShield™ quality assurance service marries our regulatory expertise with data science, and uniquely tests every single record at source avoiding the pitfalls of testing only a sample of data.  The service includes everything you need for reporting assurance including a bespoke control framework, quality assurance testing, reference data testing, advanced reconciliation and training. Please contact us for a discussion with one of our regulatory experts to find out how we can give you peace of mind in your reporting quality. 

  • Kaizen’s reaction to the £27.6 million fine issued by the FCA for incorrect reporting

    Kaizen’s reaction to the £27.6 million fine issued by the FCA for incorrect reporting

    Our Senior Regulatory Reporting Specialist, David Nowell, commented on the £27.6 million fine issued by the FCA today for breaches under the MiFID reporting regime:

    “Many may be surprised that the FCA should levy such a large fine for breaches under the previous MiFID reporting regime. However, it is a clear sign of the FCA’s tenacity and determination to strive for complete and accurate transaction reporting. It is also a message that could strike fear in the hearts of many senior managers as the new MiFIR transaction regime is far more complex than the previous MiFID regime. The requirement for adequate systems and controls over transaction reporting are clearly set out in Article 15 of RTS. Having a strong governance framework, regular reconciliations, quality assurance testing, and reference data testing are key elements in meeting these requirements. The FCA has been clear and consistent in its demands for complete and accurate transaction reporting; this latest fine is a strong and timely reinforcement of this message.”

    For accurate and complete reporting please contact us.
    For media inquiries, please contact Fiona Wilde on media@kaizenreporting.com or +44 (0) 20 3912 3271.

     

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

  • Santa’s SFTR gift extends to EMIR

    Santa’s SFTR gift extends to EMIR

    Santa delivered the long-awaited SFTR technical standards just in time for Christmas to delight SFTR specialists everywhere. But there also appeared to be something at the bottom of Santa’s sack for EMIR trade reporting specialists because the SFTR implementing technical standards also amended the EMIR trade reporting ITS. However, now we’ve taken the wrapping paper off this present, there doesn’t seem to be anything of value inside…

    No real change

    The reference to “Implementing Regulation (EU) No 1247/2012” seems curious as this is the old ITS that has already been amended by the shiny new Implementing Regulation (EU) 2017/105. Putting that aside, the changes appear meaningless. In a nutshell, the only taxonomy that can be used to classify an instrument is the CFI (as the ‘UPI’ alternative doesn’t exist and wouldn’t be a classification taxonomy if it did exist). This is not a real change as ESMA’s validation scheme already ensured only the CFI could be used – NB: the validation scheme is a really (under)handy mechanism to tweak the technical standards without having to bother with tiresome process.

    Annoyingly, Annex II of the SFTR ITS replaces Annex to the EMIR trade reporting ITS (Regulation (EU) 2017/105 rather than the stated (EU) 1247/2012). This is a tricky case of spot the difference – even the amusing typos in the formats of the ‘Collateral portfolio code’ and the ‘Trade ID’ have been persisted. The only changes I could find were on ‘Product classification type’ (only ‘C’ for CFI allowed), ‘Product classification’ (has to be a CFI) and the UPI is no longer referenced as a possible ‘Underlying identification type’ or ‘underlying identification’.

    SONIA

    At a micro detail level, I was disappointed that SONIA wasn’t allowed to join the floating rate index club, despite being set to become a key benchmark. The publication of the ‘new’ ITS annex might have been an ideal time to add it to the list of permitted codes for floating rate indices alongside other key benchmarks such as JIBAR and BUBOR. As a paranoid Briton, I like to think of it as a slight against UK standards, but maybe we were nebulous in just not asking for it. Still, it might be a good one for firms to remember if they ever get lectured by the regulators on the importance of putting “EONA” in their floating rate fields instead of “EONIA”.

    We will be providing EMIR trade reporting half-day training courses from early next year.  Please contact us to register your interest and for further details. 

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

  • How was it for you? Take our survey on the EMIR RTS changes

    How was it for you? Take our survey on the EMIR RTS changes

    Share your views 

    It’s a year since the revision to the EMIR Reporting Technical Standards (RTS) went live*. The resulting changes were fundamental including a significant increase in the number of reportable fields (from 85 to 129), significant changes to taxonomies, and additional asset class specific fields. Many participants struggled with implementation, particularly as there were competing compliance projects, including preparation for MiFID II transaction reporting, on-going at the same time.

    We’re a nosy bunch at Kaizen and we would love to hear your views on last year’s EMIR RTS changes and how valuable you feel the data is to the regulators.  Please head over to our short survey to have your say.  All responses are anonymous.

    *OK, the trade repositories implemented the changes on the Monday, but technically they were intended for implementation on 1 November 2017.

     

  • Stockholm conference: New regulatory insights on EMIR and MiFIR reporting

    Stockholm conference: New regulatory insights on EMIR and MiFIR reporting

    It was great to be a part of last week’s Trade and Transaction Reporting Northern Europe Conference in Stockholm and in particular, hear insights from the European Commission and the Dutch and Finnish National Competent Authorities (NCAs) on EMIR and MiFIR, as well as the latest on SFTR reporting timelines. 

    European Commission’s Fitness Check

    Gerd Heinen, Policy Officer at the European Commission, spoke about the Commission’s ‘Fitness Check’ on supervisory reporting. The objective of the Commission’s project is to “identify areas where the cost and burden of supervisory reporting can be reduced without compromising the objectives of financial stability, market integrity, and consumer protection”. I’m sure both the reporting firms and the recipient regulatory bodies would agree this is a worthy and valuable project. However, the two sides certainly didn’t agree in their responses to the Commission’s public consultation, particularly on whether the reporting requirements were fit for purpose.

    The Commission published a summary report following its consultation, which contains some fascinating statistics and cost estimates. My particular favourite is that only four per cent of respondents thought that all the existing supervisory reporting requirements were relevant for maintaining financial stability and upholding market integrity and investor protection. I also enjoyed the Commission’s observation that “out of 391 responses received, 258 came from industry stakeholders (all of which were in the same sector and from the same member state), who provided very similar responses to sections 1 and 3”.

    The Commission expects to publish its conclusions of its Fitness Check in the first half of 2019 and ‘if necessary’ follow publication with recommendations to streamline and simplify supervisory reporting.

    MiFIR data quality issues in Europe

    I equally enjoyed a joint presentation from the Dutch and Finnish National Competent Authorities (NCAs) on their observations on MiFIR transaction reporting implementation. From a Brexit perspective, it was interesting to note that just over 50% of all transaction reports received by the Dutch NCA were from UK firms routed via the UK’s FCA. The corresponding figure for the Finnish NCA was even higher at roughly 80%.

    When it came to reporting quality issues, the Dutch and Finnish regulators presented the following areas of concern:

    • Gaps in reporting
    • Rejected transactions not corrected
    • Use of CONCAT instead of higher priority identifier
    • Incorrect national identifier format
    • Wrong trading venue identifier (On market vs XOFF) – Operator MIC instead of Segment MIC
    • LEI codes
    • Timestamp granularity
    • Default trading times
    • Trading place identifier
    • Price
    • Reporting of transaction chains
    • Non-flat ‘INTC’ end of day.

    There are some similarities here with the UK FCA findings presented in their summer forum. However, it is noticeable that this work extends beyond the relatively simple ESMA defined validations and firms need to be aware that the NCAs are now extending their quality assessment to ‘business validations’ such as ‘flat INTC accounts’ as well.

    At Kaizen, we believe you need to be a few steps ahead of the NCA in discovering errors in your transaction reports.  Even if reports pass through the ARM and NCA validation checks, it doesn’t mean that the data contained within them is correct. Our accuracy testing service carries out over 1000 tests on every transaction report to detect errors and give full transparency of the quality of your reporting so you don’t fall foul of the regulator. 

    For more information on Kaizen’s accuracy testing and how we can help solve your MiFIR (and EMIR) reporting challenges, please contact us.

  • Book now! Kaizen launches regulatory reporting training service led by industry expert David Nowell

    Book now! Kaizen launches regulatory reporting training service led by industry expert David Nowell

    FOR IMMEDIATE RELEASE

    23  October 2018, London: Leading regulatory technology firm Kaizen Reporting today announced that it is launching a training service led by the company’s new Senior Regulatory Reporting Specialist, David Nowell. The training will initially focus on MiFIR transaction reporting before expanding to include EMIR trade reporting and the upcoming Securities Financing Transaction Regulation (SFTR).

    A former regulator, Nowell has 30 years’ financial services experience. Having previously worked as a transaction reporting technical specialist at the UK FSA, as head of transaction reporting for a tier-1 investment firm and head of compliance for an Approved Reporting Mechanism and Trade Repository, David has a thorough understanding of both the importance and the challenges in meeting the regulatory reporting requirements. He also has extensive experience of client training on both MiFIR transaction reporting and EMIR trade reporting.

    Dario Crispini, CEO of Kaizen, commented: “David is widely seen as a leading authority in the industry. The FCA frequently warns about the risk to institutions of inadequately trained regulatory reporting teams and in many of its warning notices cites a lack of training as a factor in its decision to censure a firm for incorrect reporting.  Expanding our services to include training makes sense for us, and we are looking forward to helping our clients improve their knowledge in this space.”

    David Nowell, Senior Regulatory Reporting Specialist at Kaizen, commented: “Training is an integral part of the systems and controls that firms need in place to be reporting accurately. It’s impossible to get your regulatory reporting correct unless you understand the legislation from the Level 1 text down to the regulatory technical standards, guidelines, Q&A and validations. Our new courses are designed to help get our clients up to speed quickly, allowing them to understand what needs to be done to report correctly as soon as possible.”

    David adds, “Ensuring your staff are properly trained on the reporting regulations can save costs in the long run as it will increase a firm’s chances of avoiding regulatory sanctions for incomplete or inaccurate reports and the additional expense of costly back reporting exercises.”

    The training service includes four-hour classroom-style workshops as well as in-house sessions for financial institutions. 

    (Ends) 

    For more information please visit our training page or for inquiries about the service please email training@kaizenreporting.com

    For media inquiries, please contact Fiona Wilde at media@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.

  • In the news: David Nowell on the FCA’s ‘first warning’ to industry on transaction reporting improvement

    In the news: David Nowell on the FCA’s ‘first warning’ to industry on transaction reporting improvement

    Kaizen’s senior regulatory reporting specialist David Nowell spoke with Thomson Reuters Accelus about the recent forums where the FCA’s markets reporting team set out the common mistakes that firms had made on reports and urged them to focus on accuracy and completeness. 

    David’s recent blog covered the mistakes in detail, and when speaking to Thomson Reuters he said, “The temptation with MiFID II transaction reporting is to get across the line. With EMIR some firms took the fire and forget approach to reporting. With MiFIR, the recent transaction reporting forums should have woken up firms to the fact that improving their reporting is an ongoing job.” 

    If firms fail to correct the mistakes, eventually there will be fines. 

    David said, “Firms should be in no doubt of what needs to be done to achieve complete and accurate reporting. A firm may get away with a private warning, but it will be asked to back report and engage in remediation. Even then, the firm might not find everything that’s wrong with its reporting and will incur the cost of re-reporting again.”

    Read the full article: First warning: UK FCA sets out expectations for MiFID II transaction reporting improvement (a subscription-only site). 

    • Kaizen’s award-winning ReportShield™ quality assurance service checks transaction reporting data for accuracy, completeness and timeliness. What sets ReportShield™ apart is that it tests every single data field so you get a complete picture of what’s wrong and right with your reporting. 
    • ReportShield™ includes accuracy testing, advanced reconciliation, reference data testing and a control framework – everything you need to be compliant with your regulatory reporting obligations. 
  • Media release: Leading regulatory expert David Nowell joins rapidly-growing Kaizen team

    Media release: Leading regulatory expert David Nowell joins rapidly-growing Kaizen team

    We’re delighted to announce another senior new hire in the space of a week! David Nowell, the former head of regulatory compliance at London Stock Exchange’s UnaVista, will be joining us next week. Nowell will be a Senior Regulatory Reporting Specialist, bringing with him extensive experience including over ten years at the Financial Services Authority (FSA). The news about David comes at an exciting time for us, with several new hires from tier 1 banks and the recent recruitment of Jonathan Lee, former SFTR taskforce leader at ICMA, and the addition of Elixirr (announced in March) to existing partnerships, with companies including UnaVista.

    David’s impressive knowledge of and involvement in regulatory compliance is evident in his responsibilities at UnaVista, the largest Approved Reporting Mechanism, where he was tasked with ensuring continued compliance with EMIR and MiFID reporting requirements as well as liaising with various regulatory authorities. These duties and his advice to and training for firms helped to consolidate his reputation as a leading voice in regulation and an important factor in Kaizen’s decision to enlist his services.

    Dario Crispini, CEO of Kaizen, commented: “I’m delighted for David to be joining the team to further enhance the service we provide to our client base of tier 1 and 2 banks, fund managers and brokers. Our formula of combining market-leading data scientists with industry experts is what sets us apart from competitors, and with David fitting perfectly into the latter category I’m confident he’ll be a crucial part of our operations in the months and years ahead.”

    Ian Rennie, Managing Director of Kaizen, added: “Many years of direct involvement with regulatory authorities as well as product and solution development makes for a perfect background for the service we provide to our clients. Our effective and proven quality assurance service gives financial institutions the confidence they need to focus resources elsewhere in the knowledge that they are fully compliant with ever-more stringent reporting requirements.”

    David Nowell said: “Kaizen has built a reputation of being at the forefront of its field, so this step in my career was the natural choice. I very much look forward to working together with Kaizen’s talented team and being part of the innovation and expertise that the firm consistently produces.”

    Editorial contacts

    Fiona Wilde
    Email: media@kaizenreporting.com
    Tel: +44 (0) 20 3912 3271