Tag: FCA

  • Kaizen RegTalk 2026

    Kaizen RegTalk 2026

    Kaizen RegTalk 2026, our flagship conference for the regulatory reporting community, returns on Tuesday 2 June at Drapers’ Hall, London.

    We are pleased to welcome back Tom Soden from the Financial Conduct Authority (FCA) as our keynote speaker, alongside specialists from across the industry, including firms, trade associations and Kaizen’s regulatory experts.

    The regulatory landscape is entering a new period of transition, with significant changes proposed across UK and EU regimes.  As these changes develop, firms will face increased scrutiny on the accuracy and quality of their reported data.

    This year’s event will bring the industry together to share practical insights, examine what the changes mean for firms, and explore what comes next.

    Join us to:

    • Hear directly from the FCA
    • Gain practical insight into UK and EU regulatory developments
    • Prepare for upcoming changes to UK MiFIR Transaction Reporting
    • Explore how firms are strengthening reporting quality and controls
    • Connect with peers across the regulatory reporting community
    • Experience the next evolution of the Kaizen Hub platform, including enhancements available now and a preview of what’s to come.

    View the Kaizen Regtalk 2025 highlights in the video at the top of the page.

    Places are limited to clients and invited guests but if you would like to attend, please email your interest to communications@kaizenreporting.com and we will do our best to accommodate you.

  • What the Industry Learned at our Breakfast Briefing on Market Watch 84 & EMIR Refit Reporting

    What the Industry Learned at our Breakfast Briefing on Market Watch 84 & EMIR Refit Reporting

    Last week, Kaizen brought together more than 300 regulatory reporting professionals – both in person and online – for a deep-dive into Market Watch 84, the recently published UK EMIR Reporting Q&As and the implications for EMIR Refit reporting. With representatives from both the supervisory and policy sides of the UK regulatory landscape joining the discussion, the session offered a direct look at evolving expectations for EMIR reporting.

    While the conversation took place under the Chatham House Rule, several clear themes emerged. Below we summarise the key messages and practical takeaways for firms navigating the next phase of EMIR Refit.

    1. Data quality is a strategic priority, not a technical issue

    A consistent thread throughout the discussion was the critical importance regulators place on data quality. EMIR data is used widely across supervisory, policy and market-monitoring functions. The message was clear:

    • EMIR data feeds directly into senior decision-making
    • Poor reporting undermines supervisory insight
    • Data quality issues are no longer viewed as operational noise – they impact policy outcomes.

    The move to XML and the Refit schema has already improved baseline quality but regulators expect firms to keep raising reporting standards. Data quality is now a leading regulatory risk, not a back-office technical issue.

    2. The Refit implementation was a success and provided essential lessons too

    Both regulators and industry should take confidence from the smooth transition to the new regime under EMIR Refit. Day-one reporting was strong, and the majority of firms completed their six-month uplift window on time.

    However, there were also lessons learned during the implementation phase:

    • Reliance on third-party vendors increased sharply during this time, bringing with it gaps in oversight and testing
    • Some firms struggled to manage competing regulatory projects, especially those with dual EU/UK obligations
    • The uplift to the new regime had removed a small but significant population of “zombie” trades, highlighting weaknesses in historical data hygiene.

    3. Error and omission reporting: more transparency, better governance

    One of the key themes in the discussion concerned error notifications. Error reporting should not be viewed negatively and is increasingly a sign of:

    • Strong controls
    • Clear governance
    • A willingness to be transparent.

    However, what may be viewed negatively is the absence of notifications where errors clearly exist.

    The important points for firms to note are:

    • There is no fixed threshold for materiality – volume alone is not sufficient to determine significance
    • Firms should take a ‘cautious’ approach to submission – if in doubt, submit.  The regulators will communicate with firms if they think their materiality thresholds are not appropriate.
    • Initial submissions can be updated over time, but timeliness is important
    • Quality of narrative can be poor – firms should improve clarity, completeness and consistency.

    Error and omission reporting is now an important part of supervisory dialogue. Firms who avoid it are drawing the wrong conclusion about how it is perceived.

    4. Change management remains a weak spot across the industry

    Despite long preparation windows, many reporting issues stem from weak change-management practices:

    • Insufficient oversight of third-party providers
    • Inadequate testing of mapping and judgements
    • Limited visibility of delegated reporting outputs
    • Dependencies / overlap between EU and UK projects causing resource pressures.

    Firms should now consider the following:

    • Refresh their change-management frameworks
    • Perform structured post-implementation reviews
    • Revisit testing strategies and reconciliation approaches
    • Ensure they have trade repository (TR) access and can independently validate completeness and accuracy.

    5. Q&A updates bring clarity on technical ISINs and FX swaps

    The recent UK EMIR Q&A update addressed two longstanding pain points.

    Technical ISINs

    A new “technical ISIN” is now available for scenarios where underlying instruments lack an issued ISIN. This prevents firms from failing validation rules and, crucially, enables regulators to identify where gaps in global ISIN coverage exist.

    Use is strictly limited to the specified scenarios. This is not a workaround for convenience, and firms should apply it cautiously.

    FX Swaps Clarification

    Perhaps the most welcome update was the long-awaited clarity on FX swaps:

    • If a single instrument is executed, confirmed and settled as a swap, it should be reported as one instrument
    • Where a near-leg and far-leg are executed as separate contracts, only the eligible components should be reported, typically the forward leg, unless both legs fall within the spot window (in which case no reports are required).
    • Package fields should be populated even where the spot leg is not reportable.

    This clarity is expected to significantly improve pairing, matching and overall data quality across the FX landscape.

    5. Pairing and matching are now in the spotlight

    With Phase 2 reconciliation rules coming into effect next year, pairing and matching rates are receiving closer attention.

    Key points:

    • Pairing should approach 100%, even if not fully achievable in practice.
    • Firms should be actively collaborating with peers to resolve UTI, lifecycle and population mismatches.

    Firms that are not already analysing their reconciliation performance, both bilaterally and via vendor tools, should prioritise this now.

    6. Looking ahead: expect more collaboration, not less

    The UK EMIR Reporting Industry Engagement Group, used heavily during the Refit rollout, will continue and will be used to maintain an open channel with industry and to:

    • Shape future Q&A
    • Identify areas of ambiguity
    • Improve pairing and matching
    • Support industry-wide operational alignment
    • Prepare for the 2026 reconciliation phase.

    Conclusion

    EMIR reporting has entered a new phase with the focus having shifted from implementation to ongoing accuracy, demonstrable governance and proactive issue management.

    For firms, this means:

    • strengthening internal controls
    • scrutinising vendor-led reporting
    • investing in reconciliation and data validation
    • engaging early and transparently with supervisors and regulators
    • gearing up for the 2026 reconciliation expansion.

    The industry has made real progress but expectations are rising across the industry.

    For a conversation with one of our subject matter experts or a free health check of your EMIR Reporting please get in touch. 

  • FCA Market Watch 81/82: Overview of FCA Final Notices & Enforcement Actions

    FCA Market Watch 81/82: Overview of FCA Final Notices & Enforcement Actions

    Over the past nine months, the Financial Conduct Authority (FCA) has strengthened its message to the industry on its expectations for firms on MiFID Transaction Reporting.  It has issued Market Watch 81 and Market Watch 82, and two enforcement actions for firms for ‘transaction reporting failures’.  These actions provide a clear message: firms must adopt proactive governance, robust remediation, and strong oversight of transaction reporting frameworks.

    Market Watch 81: Transaction Reporting Vulnerabilities

    Published in November 2024, Market Watch 81 provided a detailed FCA-led assessment of UK MiFIR transaction reporting. Although firms have made progress since 2018, the regulator said that systematic weaknesses remain, including:

    • Change management failures: poor testing, mapping, and documentation resulting in recurring reporting errors
    • Sub-optimal reporting logic: gaps in compliance and business involvement leading to flawed rules
    • Inadequate data governance: absence of clear ownership and data lineage undermining accuracy of transaction reports
    • Weak control frameworks: insufficient reconciliations and validation checks are leaving errors undetected
    • Governance deficiencies: under-resourced compliance teams and limited senior oversight are compounding weaknesses.

    Market Watch 82: Elevated Expectations on Remediation

    Released in July 2025, Market Watch 82 reinforced the FCA’s focus on how firms identify, resolve, and report transaction reporting issues. The FCA reiterated that it expects firms to:

    • Prioritise under-reporting: this means fixing missing transactions before addressing less material errors
    • Remediate root causes: resolving systemic issues prior to back-reporting
    • Ring‑fence resources: treating remediation as a dedicated programme, not an afterthought
    • Embed controls in change processes: ensuring transaction reporting governance is part of every change initiative
    • Proactively engage with the FCA: firms are expected to disclose delays or significant remediation constraints early
    • Sustain continuous monitoring: embedding testing and control frameworks to prevent recurrence.

    Recent enforcement actions

    The two penalties this year demonstrate escalating consequences for reporting failures – from a £99,200 fine for a breach of MiFIR Article 26(1) involving missed CFD transaction reports, to a penalty of more than £1m for a breach of MiFIR Article 26 and Principle 3 of the Authority’s Principles for Businesses where systemic control failures affected nearly a million transaction reports. These cases underscore the importance of proactive monitoring systems and prompt self-disclosure when issues are identified.

    Key take aways for firms resulting from the final notices

    • Prioritise accurate reporting governance: transaction reporting must be elevated as a key regulatory and compliance risk
    • Emphasise remediation and root cause analysis: firms must fix issues promptly and thoroughly, ahead of any back-reporting
    • Maintain oversight over vendors: delegation of reporting functions does not transfer regulatory accountability
    • Act swiftly and transparently: early detection and quick self-reporting can significantly reduce FCA enforcement impact
    • Observe enforcement precedents: the larger penalty involved a firm with prior enforcement history for similar failings in 2022.

    Conclusion

    Market Watch 81 and 82, in concert with these enforcement actions demonstrate a significant shift in tone from the FCA.  It has taken steps to alleviate the reporting burden on firms by reducing the supervisory priority on a number of fields and we expect more clarity to come in terms of future plans in September – but in the meantime the FCA clearly expects firms to be getting their reporting correct.

    Without strong internal control, governance, and remediation practices, firms risk becoming the next FCA enforcement example.

    We help hundreds of firms including some of the world’s largest banks and asset management firms to ensure transaction reporting accuracy and completeness.  Contact us for a conversation or a demo of our regulatory assurance tools to find out how we can keep you on the right side of the regulator.

  • WATCH: Highlights of Kaizen RegTalk 2025

    WATCH: Highlights of Kaizen RegTalk 2025

    We’re thrilled to share the highlights of Kaizen RegTalk, our annual event for our client community, which took place on Tuesday 10 June at Merchant Taylor’s Hall, London. 

    More than 200 clients, partners and industry specialists joined us for an afternoon of networking, insights and best practices on regulatory reporting, with speakers from the FCA, Bank of England, ISDA, Regis-TR, FIA and many client firms. 

    Tom Soden, Manager, Markets Reporting Team at the FCA gave the keynote address.

    Key topics for the afternoon included the MiFIR Review, EMIR Refit lessons learned, delegated reporting best practices, and the growing role of AI.

    Once again, a huge thank you to all our speakers and panellists, and of course to our valued community of clients who make events like this possible.

  • Kaizen and RegGenome Announce Strategic Partnership using AI to expand regulatory content on Single Rulebook

    Kaizen and RegGenome Announce Strategic Partnership using AI to expand regulatory content on Single Rulebook

    London, December 3, 2024 – Kaizen, a leading provider of regulatory compliance solutions for global financial institutions, announced today that it has entered into a strategic partnership with RegGenome, a UK based provider of global financial regulatory data, to use artificial intelligence (AI) to vastly expand the coverage and content of Kaizen’s Single Rulebook platform including new jurisdictions and regulatory domains.

    The collaboration between Kaizen and RegGenome will support the digitisation of regulation where both parties will work together to provide fast and efficient access to a vast array of global regulatory rules, jurisdictions and taxonomies on the Single Rulebook platform. By combining Single Rulebook’s front end user interface with RegGenome’s AI powered regulatory data and information structures, the firms will provide clients with a new standard of regulatory intelligence and change management.

    Many financial institutions operate across multiple locations and global regulatory jurisdictions. Today’s announcement means that firms will be able to navigate and respond quickly to the complex landscape of regulatory change and divergence more easily and efficiently.

    In early 2025, Single Rulebook clients will be able to access regulatory content covering all major global financial markets. This includes coverage of US federal regulators and agencies, European national law and global G20 members.

    In addition to core financial services regulations, Single Rulebook users will also be able to investigate emerging compliance requirements for cryptocurrency, cyber security and digital operational resilience.

    Mark Johnston, CEO, RegGenome commented: “We are delighted to announce our strategic partnership with Kaizen’s Single Rulebook. This collaboration will make RegGenome’s comprehensive structured regulatory data available through Single Rulebook’s innovative platform. By combining our extensive regulatory content with Single Rulebook’s advanced search and analytics capabilities, we’re enabling financial institutions to better navigate the complex regulatory landscape.”

    Chris Dingley, CEO, Single Rulebook said: “We’re excited to announce our partnership with RegGenome today. Working with RegGenome’s AI solution for regulatory data and information means that we will be able to expand the Single Rulebook platform and content rapidly for our clients, continuing and enhancing our efforts to support them with the burden of managing global regulation.”

    RegGenome processes global regulation using artificial intelligence (AI) to transform what is human-readable into machine-readable and machine-consumable data. It is part of the Regulatory Genome Project (RGP), a public-private initiative between the University of Cambridge, Judge Business School, and RegGenome. RGP aims to build and review a set of open-access regulatory information structures, known as the Cambridge Regulatory Genome (CRG), and make available a global repository of aggregated, structured regulatory data.  

    Single Rulebook is Kaizen’s digital solution for searching and navigating global regulation. The platform helps firms manage regulatory change with front end functionality such as rule maps, labels and annotations which can be pinned to regulatory rules and shared across global organisations.

    About RegGenome

    RegGenome is a regulatory data technology company and a leader in computational regulation, changing how the world produces and consumes regulatory information. We process the world’s regulation using AI to transform what is human-readable into machine-readable and machine-consumable data. 

    www.reg-genome.com

    For more information, please contact James Dunseath, Communications Director, on +44 (0) 7557 955795 or media@kaizenreporting.com

  • UK SFTR – Desynchronised Harmony

    UK SFTR – Desynchronised Harmony

    UK announces SFTR validation rule changes

    On 14 October 2021, the FCA published updated validation rules for SFTR in the UK. These amended rules are due to take effect on 11 April 2022*.

    In terms of the validation rules themselves, this move will bring them entirely into line with the new EU SFTR validation rules due to take effect from 31 January 2022. The current rules differ slightly in the treatment of price currency loan and collateral fields.

    We think this is the right approach – UK/EU rules should either be harmonised (as is the case here) or fully diverged (as part of a more aggressive regulatory arbitrage) but not somewhere in no-mans-land in the middle.

    The timing (April rather than January) arguably gives firms a little more time to implement the changes (something the industry has been very vocal about). The fact that these were announced in mid-October rather than the end of July (when ESMA made its announcement) negates this benefit somewhat, particularly for firms that only have a UK reporting obligation. The current two-speed timing (EU implementing in January and UK in April) also complicates things for dual reporting firms as it means two and a half months of validation rule divergence.

    The FCA is dangling a carrot as firms will have until 11 April 2022 to make the changes. We hope ESMA will take the bait and offer a matching extension to its original implementation date!

    *Please note this date was updated from 14 April.

    • If you have concerns about your firm’s SFTR data quality and regulatory compliance, working through the changes to the validation rules or undergoing trade repository migrations, we can help.  Please contact us for a conversation with Jonathan or one of our regulatory specialists to discuss your challenges.  
  • 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.

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

     

  • You better watch out, you better not cry….

    You better watch out, you better not cry….

    The worst Christmas present I ever received was a jar of mustard. To be fair, it was a large jar and it did come from Fortnum and Mason, but it was still a jar of mustard. And I don’t like mustard. What on earth was going through their minds when they thought this dodgy coloured and foul tasting condiment would be a suitable festive gift?

    Secret Santa?

    However, there are worse Christmas presents, especially if your Secret Santa this year was the FCA and you received a letter asking you to explain numerous errors in your MiFID II transaction reports. Many firms fail to appreciate that the FCA Santa really does know if you’ve been naughty or nice with your transaction reporting. It has systems designed to find errors in transaction reports and you will not be alone if you have received a letter from the FCA (as 223 UK investment firms have so far been contacted to explain reporting errors).

    Don’t panic

    Communications from the FCA can often cause alarm within firms, but they shouldn’t necessarily induce panic. The MiFID II transaction reporting requirements are extremely complex and we have discovered errors through the quality assurance testing we have performed for every firm. No NCA can sanction every firm when they find errors in their transaction report and nor do I think they would want to. However, they cannot perform their role of monitoring for market abuse unless they receive complete and accurate transaction reports. The UK FCA has now twice signaled in Market Watch newsletters that firms are making unacceptable errors in their transaction reports and its patience must be wearing thin. It is quite possible that they may be thinking of imposing further sanctions for transaction reporting breaches and, who knows, maybe there’s one going through the enforcement process as we speak.

    Put the right controls in place

    If you receive a less than cheery Christmas missive from the FCA, it is an opportune moment to consider whether you have adequate controls over your transaction reporting processes. We believe the FCA is far more likely to take a collaborative approach with firms if they can see that the firm is trying to do the ‘right thing’ – i.e. implementing the controls detailed in Article 15 of RTS 22. In particular, performing quality assurance testing and regular reconciliations of data within source systems with the reports sent to the FCA. If these controls are not in place, you’re far more likely to find yourself on Santa’s naughty step.

    If you don’t know if your reporting’s bad or good, please speak to us at Kaizen. We have a full suite of quality assurance and reconciliation solutions that can ensure that you are good for goodness sake…

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

  • FCA to increase its scrutiny of EMIR reporting

    FCA to increase its scrutiny of EMIR reporting

    The FCA is likely to increase its focus on EMIR trade reporting quality in response to a recent report from ESMA that criticises the regulator’s approach. In its response to the criticism, the FCA has said it is revising its EMIR data quality strategy which will include the creation of a new central data quality team and the upgrading of its cloud infrastructure to receive EMIR data and check for quality issues.

    What’s the background?

    A recent report from ESMA has concluded that there are number of insufficient supervisory controls over the quality of the FCA’s EMIR data. The FCA was not the only NCA called out – six were assessed. ESMA’s findings will probably not have come as a surprise to many firms. UK firms are used to the FCA being extremely proactive in monitoring the quality of MiFID II transaction reporting however as we’ve pointed out previously, less so with EMIR.

    But isn’t EMIR more important than MiFID II?

    EMIR reporting should be considered as the most important regulatory reporting requirement as it is designed to help regulators monitor for systemic risk – ie. helping to ensure that there is not a collapse of the entire financial system. So it is essential that the regulators have a strong supervisory regime to ensure that the quality of the data reported by firms is sufficient to enable the guardians of financial stability to perform their functions. In a statement contained in ESMA’s Final Report, the FCA rightly points out that it is the Bank of England that is largely responsible for financial stability in the UK, so there are more limited ways in which EMIR data can be integrated into its overall supervisory approach.

    What does the FCA do currently?

    Just over two years ago, the FCA issued a fine of £34.5m to an investment firm for failing to comply with Article 9 of EMIR. This is the only fine it has issued so far for the regime. There is also a requirement on firms to report breaches. However, there is a telling story on the number of error forms submitted to the FCA: earlier this year following an FOI request, the FCA confirmed to us that it received notifications from 384 firms for MiFID II transaction reporting breaches since go-live compared to just 75 for EMIR trade reporting in the period since Q2 2018 when the EMIR breach form became available.  

    When you consider that around 9,000 UK entities have an EMIR reporting obligation and 3,000 UK entities have a MiFID II reporting obligation, this statistic becomes even more concerning.  We can say with confidence that this is most definitely not because UK firms’ EMIR reporting is better than their MiFID II transaction reporting. For example,  in our quality assurance testing we detect a significantly larger amount of errors in the EMIR reports than we do in the MiFID II transaction reports.

    What should firms do?

    Be prepared for a far more intrusive investigation of your EMIR reports. Our advice is to look at your EMIR reporting now.  If you are unsure about the quality of your EMIR reports, or just want to know how good – or bad – your reporting is, then this is why we here at Kaizen exist. Our ReportShield™ testing services have been developed to provide a full assessment the quality of your reporting.  Contact us for a discussion on how we can give you full transparency of your EMIR reporting quality.

    Read the ESMA report on its website.

  • Why communication and cooperation are the key to avoiding regulatory reporting fines

    Why communication and cooperation are the key to avoiding regulatory reporting fines

    Recently we saw a large inter-dealer broker fined by the FCA for ‘improper trading’. The final notice stated that the firm was “failing to conduct its business with due skill, care and diligence, failing to have adequate risk management systems and for failing to be open and cooperative with the FCA”.

    This led me to think that the same message can be used across all regulations and that this was the same communication we heard from the FCA when it handed out the two MiFID I fines earlier this year. Introducing care and diligence with added controls, governance and independent quality assurance testing is one thing; it’s then communication and cooperation with the regulator that are key.

    Be proactive, transparent and open with your NCA

    Being on the front foot with the regulator should not be deemed a negative or onerous task. It is incredibly important that all firms that have found an issue with their reporting, relay this message to their National Competent Authority (NCA) as soon as they can, through the applicable channels. The key message we see and hear from NCAs is that they always encourage firms to be proactive, transparent and open.

    Once an issue has been identified either internally or externally via a quality assurance testing service, analysis has to be completed and the relevant action decided upon.

    Alert your NCA as soon as possible

    Depending on the regulatory regime, the NCA may require a form to be completed. In the UK, for MiFIR transaction reporting an errors and omissions form* needs to be emailed to the Markets Reporting Team.  For EMIR, a breach notification form* needs to be completed.

    The likelihood is that the sooner the issues are identified and then communicated, the happier the relevant NCA will be that you are being proactive and cooperative to improve the quality of your reporting.

    At Kaizen, as well as helping firms check the accuracy of their regulatory reporting, we have former regulators as part of our team of subject matter experts. Not only does their expertise feed into our testing services, our clients also benefit from our advice through the process of communication and cooperation with your NCA.

    We’ve helped a number of firms provide confidence to the regulator through identification of issues in reporting quality but also through putting the right controls in place. Contact us if you’d like to discuss any of the issues raised in this blog.

    *Does not open in new window.

  • FCA warns on further transaction reporting errors in Market Watch 62

    FCA warns on further transaction reporting errors in Market Watch 62

    In its latest Market Watch newsletter, the FCA has highlighted further errors it has detected in firms’ MiFIR transaction reporting. While some of these errors reflect the complexity of reporting requirements, others are very basic and must be testing the patience of the regulator.

    First, the basics…

    Starting with the most basic of errors – some firms are still failing to populate their own LEI in the ‘executing entity’ field where they are executing a transaction. This betrays a fundamental misunderstanding of the transaction reporting requirements and highlights the need for training to be an essential element in firms’ systems and controls framework.

    Another basic mistake is in the incorrect use of national identifiers for buyer/sellers (and their decision makers), ‘investment decision maker within firm’ and ‘person responsible for execution within the firm’. In particular, the FCA has detected use of the second or third priority identifier when the first priority identifier is available. These fields are absolutely essential for market abuse detection and obviously the regulators are going to be particularly unhappy with incorrect population. Failures with these fields could be the result of a misinterpretation of the requirement, or could result from the inadequate collection of data from clients and employees.

    The more complex..

    Moving to some of the more complex requirements, the FCA has highlighted issues with the buyer/seller decision maker, misuse of the aggregate client identifier (INTC) and use of default values in the ‘waiver indicator’, short selling indicator’, OTC post-trading Indicator’, and ‘commodity derivative indicator’.

    There is also an important message for reporting buy-side scenarios – the FCA has detected issues where the buyer/seller decision maker hasn’t been populated with the fund management company where appropriate. Additionally, the FCA has discovered instances of the broker identifying fund in the buyer/seller identifier fields when the fund management company is expected (i.e. where transmission within the definition of RTS 22, Article 4 has not taken place).

    To summarise…

    • The FCA is still very far from happy with the quality of MiFIR transaction reports
    • In highlighting these errors, the FCA removes any defence of ‘ignorance’ for firms
    • The FCA is increasing the sophistication of its data quality procedures and may be implementing cross-entity testing
    • The FCA has again stressed the need for robust methods and arrangements for reporting transactions, including reconciliation of front-office trading records against data provided by the FCA.

    Our advice…

    • Validations do not detect all reporting errors. Only quality assurance testing of the accuracy of your transaction reporting data will help you stay one step ahead of the FCA – get on the front foot and discover any reporting issues before the regulator does
    • To meet the requirements of RTS 22, Article 15 you must reconcile the data in your front office systems to that reported to the regulator 
    • Training on the reporting obligations will help ensure you haven’t misinterpreted any of the MiFIR reporting requirements.

    And of course, we can’t help but point out that detecting transaction reporting errors is why we here at Kaizen exist! Our ReportShield™ assurance services are designed to help you meet all the requirements of MiFIR transaction reporting. Please contact us to learn more about how we can get your reporting accurate and complete. 

    Further reading: Market Watch 62

  • MiFIR transaction reporting goalposts set to shift again

    MiFIR transaction reporting goalposts set to shift again

    Whilst it may be a bit more of a tweak than a wholesale change, firms need to be aware and plan for changes to the ESMA validations that are targeted to come into effect on 23 September this year. 

    The changes were agreed back in July 2018 but delayed by the Brexit postponement and are mainly amendments to cover mistakes in the validation previously introduced. The changes, cut and pasted from the ESMA version history, are as follows:

    • rule id 010: field 3 must not be populated. This also pertains to SIs;
    • rule id 014: add provision for the case when an LEI is in the “Lapsed” status for a certain period;
    • rule id 096: validation of field 28 against the reception timestamp;
    • rule id 117: field 37 not mandatory for SIs;
    • rule id 136: check against additional CFI codes;
    • rule id 154: check against additional CFI codes;
    • rule id 227: correction of a typo in one of the CFI codes.
    • Clarified description of rules 228 and 267.

    For me, the most important of these changes is the change to Rule 117.  From the implementation of this change, firms should no longer populate ‘Country of branch membership’ for trades against systematic internalisers. Of course, this field should never have been populated for trades against systematic internalisers in the first place as this contravenes the Regulatory Technical Standards (“This field shall only be populated for the market side of a transaction executed on a trading venue or on an organised trading platform outside of the Union.”). I think it is important to highlight that this oversight has forced firms to make an error in their transaction reports in order for them to be accepted by the NCAs.

    I don’t wish to criticise the regulators for making errors, as I believe it is inevitable that there will be some initial errors in the implementation of such a complex regulatory reporting regime – for both regulators and firms. However this issue clearly raises the question about whether the NCA would expect every firm to submit a form when they are forced to report incorrectly in order for the NCA to accept the report. There has to be a degree of common sense and this is not reflected in the wording of Market Watch 59.

    It is also fair to say the changes have not been widely publicised. ESMA has made a notification of changes but I’m sure most people, like me, will find this notification extremely difficult to understand. I’m sure people will also be confused by the validation version history that still states that the changes were “applicable from the end of 2018”. Perhaps the FCA is waiting for more confidence in the 23 September implementation date before it makes an announcement. However, whilst these changes aren’t major, firms need time to assess the changes, code and test any required system changes. September 23 already appears very close.

    Kaizen will of course be updating our ReportShield testing to include the latest validation changes in time for September 23. We provide validations as part of our accuracy testing service at no extra charge to clients – saving significant costs in avoiding outsourcing an additional validations service. Please contact us for a discussion with one of our regulatory experts to find out more.

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

  • Kaizen wins ‘Best Reporting Platform or Service’ at Sell-Side Technology Awards

    Kaizen wins ‘Best Reporting Platform or Service’ at Sell-Side Technology Awards

    FOR IMMEDIATE RELEASE

    15 April 2019, London: Leading regulatory reporting firm Kaizen Reporting (Kaizen), developer of the multi-award-winning assurance service, ReportShield™, has won ‘Best Reporting Platform or Service for the Sell-Side’ at the Sell-Side Technology Awards. Hosted and run by WatersTechnology, the awards were set up in order to recognise market-leading technologies and third-party vendors that enable sell-side firms to operate more efficiently and transparently.

    “It’s a real honour to be named as the winner of ‘Best Reporting Platform or Service’, which further shows Kaizen’s commitment to offering our customers the best solutions to their reporting needs.”

    The methodology which applied to nominated companies focused on how they address the sector’s most pressing needs and manage the various risks financial firms frequently face, through innovation and effective collaboration. The winners of the awards were narrowed down from an extremely broad field; entry was open to all technology providers, brokers and sell-side institutions, illustrating the level of quality required to stand out.

    Dario Crispini, CEO of Kaizen, commented:

    “It’s a real honour to be named as the winner of ‘Best Reporting Platform or Service’, which further shows Kaizen’s commitment to offering our customers the best solutions to their reporting needs. The latest transaction reporting fine imposed by the FCA highlights the extent of the challenges firms face in trying to achieve high-quality reporting and the increased risks and costs of reporting failures for both the firms and their senior managers. Our solutions uniquely address these challenges and having that recognised through the Sell–Side Technology Awards is testament to the great work the team at Kaizen is doing”.

    Kaizen’s 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 utilises our multi-dimensional testing methodology to fully assess the quality of the data firms report to the regulator.

    (ends)

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

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

  • FCA MiFID reporting fine – could it have been you?

    FCA MiFID reporting fine – could it have been you?

    Many firms were wondering when the first fine for MiFIR transaction reporting breaches would be levied by the FCA, so it might have come as a surprise to see a fine for a breach under the previous MiFID transaction reporting regime. We have seen strong signals from the FCA that it is disappointed with quality of some of the transaction reports it receives and it has been tireless in explaining that complete and accurate transaction reports are essential to monitor for market abuse effectively.

    Tough line

    Despite these warnings, some might have been thinking that the FCA was too occupied with Brexit to take enforcement action for transaction reporting breaches. The latest fine, at £27.6m after a 30% early settlement discount, is over twice as large as the previous fine for MiFID transaction reporting and should leave firms in no doubt that the FCA will continue to take a hard line with reporting breaches of both the MiFID and EMIR variety.  Many may be left considering what they should be doing to make sure they’re not the next subject of enforcement action.

    What failings did the FCA identify?

    Purely in terms of numbers, between 5 November 2007 and 24 May 2017, the firm:

    1. Failed to report 3,658,423 transactions;
    2. Inaccurately reported 83,074,015 transactions, and
    3. Erroneously reported 49,152,274 transactions.

    These look like very large numbers, but they have to be taken in context: In the period in question approximately 1.8 billion transactions were reported. This implies that the FCA didn’t raise any issues for approximately 1.665 billion transaction reports, or 92.5% of the submitted reports. It would be interesting to know how many senior managers are confident their firm is reporting more than 92.5% of its transactions correctly. Of course, they should be aiming for 100% complete and accurate reporting, but it is possible that many senior managers don’t actually know their accuracy rate.

    Systems and controls

    Of course, it isn’t just a numbers game. The accompanying Final Notice highlights a lack of sufficient systems and controls. In particular, the FCA stated there was a breach of Principle P3 by:

    1. Failing to have adequate systems and controls to ensure that reference or ‘static’ data used for various mandatory fields in the transaction reports submitted to the authority were complete and accurate;
    2. Failing to have in place adequate change management controls to manage changes affecting transaction reporting processes and systems, and
    3. Failing to undertake appropriate testing to ensure the completeness and accuracy of transaction reports.

    It is particularly interesting to note the criticisms in the Final Notice of the control framework calling out that it “did not adequately test and reconcile the completeness and accuracy of all transaction reporting data from its front office systems to the ARM reporting to the Authority.”

    Lessons to be learned

    The obvious lesson is that the FCA is actively enforcing transaction reporting. If your firm does not have adequate systems and controls in place or doesn’t even know how good (or bad) its reporting is; you could be at risk.

    Interestingly, in reference to the weakness of the reconciliation and testing controls, the notice called out the “periodic, sample based” nature of them. The limitations of sample testing and the false confidence that it provides has been one of the root causes of many a fine. At Kaizen, we provide quality assurance testing on all transaction reports and our reconciliation service tests all trades in the front office systems, determines whether they should be reported, and only then reconciles against the reports submitted to the regulator. We can also advise on the control framework, test all reference data (including ISINs, counterparty LEIs and for natural persons) and provide training on the regulatory requirements.

    Firms need to react

    When issues are identified by the FCA the clock is ticking. Firms should take any issue identified by the FCA as a trigger to not only investigate the issue raised but to look across all of its reporting to make sure it is correct. Flushing out issues quickly is critical in maintaining the confidence of the FCA. The industry is littered with examples of firms that have completed reviews and improved procedures only to have issues found many months and sometimes years later.

    Senior Managers liable

    The Senior Managers and Certification Regime (SMCR) has increased the reporting risks by making senior managers personally liable for transaction reporting controls.  The SMCR is soon to extend to all core firms at the end of the year.  Firms and their senior managers need to examine the systems and controls they have over transaction reporting and ask themselves whether they truly understand whether they are meeting the FCA requirements or whether they could be potentially next in line for enforcement action.

    If you have any doubts whether your reporting and controls are up to the required standard, we can help.  We have a proven track record in helping firms tackle their transaction reporting issues and risks head on – and helping them to avoid censure.Our ReportShield™ quality assurance service provides everything you need for reporting assurance including a bespoke control framework, quality assurance testing, reference data testing, reconciliation and training.  

    Please contact us for a discussion with one of our regulatory experts to find out more.

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

     

  • Senior Managers Regime – are you ready?

    Senior Managers Regime – are you ready?

    The Senior Managers & Certification Regime (SMCR) for the remaining financial firms not yet obligated* is going live on 9 December 2019.  Yes, a little scary, given that Brexit is still an unknown, MiFID II is still giving everyone the run around, and SFTR is just around the corner too.

    If you’re one of the firms affected, are you ready for the extra responsibilities of SMCR?  If you’re a senior manager, are you up to speed with your heightened remit, obligation and duties?

    The FCA states its aims are to:

    • encourage a culture of staff at all levels taking personal responsibility for their actions
    • make sure firms and staff clearly understand and can demonstrate where responsibility lies.

    Like many regulations, SMCR was born out of failings in previous regimes and financial market misconduct; in trying to increase personal accountability on approved persons and making sure firms apply the correct framework and governance to the function of senior managers, with the assurance they have ‘fit and proper’ personnel in place. In essence, just to make sure firms are run better.

    Regulatory reporting controls, governance and ultimately, sign-off, will be key to senior managers. Our ReportShield™ services can help compliance and management within firms meet their regulatory reporting requirements with confidence that independent quality assurance, reconciliation and accuracy testing has been implemented across their active regulatory reporting regimes.

    If you have any questions about your SMCR reporting requirements, our regulatory experts can help.  Please contact us to find out more. 

    *These include: investment firms – brokers, securities firms, assets managers, financial advisers).

  • Valid but wrong: FCA warns on MiFIR transaction reporting data quality

    Valid but wrong: FCA warns on MiFIR transaction reporting data quality

    Senior Managers will not need a crystal ball to predict what will happen when the first MiFID II enforcement case is completed…

    In a speech on 7 February, the FCA’s Head of Market Policy, Stephen Hanks, warned about the unsatisfactory quality of some transaction reporting and the potential future consequences. The FCA stated that it was “particularly disappointed” to see fundamental errors in transaction reports that would have been incorrect under the previous MiFID reporting regime, let alone the far more complex MiFIR reporting regime.

    To demonstrate this type of error, the FCA noted that it was seeing zero in the price field in many reports. This is a classic example of what we call the “valid but wrong” problem. A zero price will pass the ESMA validation, but that doesn’t make it correct – we would only expect a zero price to be seen in exceptional cases, such as certain swap contracts where the spread is zero.

    The FCA also warned that just because there has been no enforcement action so far under MiFiD II, it doesn’t mean that it is happy with how firms have met the MiFID II requirements. Of course, formal sanctions are not the only tool at the FCA’s disposal and many firms have discovered how problematic remediating transaction reporting failures can be when issues are discovered. At Kaizen, we recommend four key areas that firms need to focus on to avoid the worst of the FCA’s wrath:

    1. Accuracy Testing
      • Quality assurance testing of all reportable data to identify incorrect transactions, using independent sources of data where possible
    2. Reconciliation
      • Reconcile all trades in your books and records with data received by the regulator
      • Note that the RTS 22, Article 15 reconciliation requirement includes “checking the timeliness of the report, the accuracy and completeness of the individual data fields and their compliance with the standards and formats specified in Table 2 of Annex 1”
    3. Reference data testing
      • Testing of counterparty and instrument static data for accuracy and completeness
    4. Control Framework
      • A risk and accountability framework tailored to your business
      • Process documentation, steering groups, training and remediation process.

    There is no need to have a crystal ball to understand what will happen when the first fine is issued under MiFID II. Senior management teams (which now include the SM&CR Manager responsible for transaction reporting) in organisations large and small will know exactly how well placed their organisation is in terms of judging the data quality of their reports. The call will go out to Compliance, Operations, Business and IT teams to run an immediate and urgent review of controls and data quality. This takes up valuable management and SME time and firms often don’t end up with the full picture. This is the typical response of firms who have not put in place effective controls and emphasises the need to be proactive and get these controls operational.

    At Kaizen Reporting, we have a team of specialist regulatory experts and data analysts delivering excellence on each of these four transaction reporting assurance requirements. Contact us to find out more about how we can give you peace of mind in the quality of your regulatory reporting and keep you on the right side of the regulator.

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

  • Deep into the soul of regulatory reporting in 2018

    Deep into the soul of regulatory reporting in 2018

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

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

    MiFIR transaction reporting go-live

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

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

    ESMA has been very busy

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

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

    The FCA and SMCR

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

    SFTR

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

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

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

    Trade reporting and Jumpin’ Jack Flash

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

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

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

    A view from across the Atlantic

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

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

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

    Brexit – I say a little prayer

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

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

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

  • FCA data extract will now include transaction submission date

    Great news! The FCA has announced that from 15 December its data extract schema will include the transaction submission date.

    At Kaizen, we consider this to be very good news as it will now be possible to identify the latest version of the trade report. Instead of simply reconciling the accuracy and completeness against data from the ARMs, we will now be able to reconcile the data against the records held by the FCA. This makes it far easier for firms to be fully compliant with the obligations detailed in RTS 22 Article 15(3):

    “Investment firms shall have arrangements in place to ensure that their transaction reports are complete and accurate. Those arrangements shall include testing of their reporting process and regular reconciliation of their front-office trading records against data samples provided to them by their competent authorities to that effect.”   

    We look forward to substantially increasing our use of FCA-provided data samples for testing and reconciliation, providing confidence to firms that they are meeting their MiFIR transaction reporting obligations.

    For more information visit the FCA website.

  • 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. 
  • The FCA’s mid-year report on MiFID II transaction reporting

    The FCA’s mid-year report on MiFID II transaction reporting

    School’s out for summer and financial firms are being handed their report card by the FCA. Is it an A for effort and a D for quality?

    The FCA’s MRT has hosted a transaction reporting forum where they focused on data quality and completeness for MiFID II. The forum slides have been published and they contain some fascinating data on the extent and quality of data submitted in the first six months of the new reporting regime. During this period, the FCA ingested nearly 3.5 billion transaction reports, but also had to reject a large number of reports. The FCA produced the following list of its top ten rejections:

    1. Instrument is not valid in reference data on transaction date (CON-412)
    2. Underlying instrument is not valid in reference data on transaction date (CON-472)
    3. Country of branch membership is missing (CON-370)
    4. Commodity derivative indicator is missing (CON-640)
    5. Instrument classification identifier is incorrect (CON-430)
    6. No underlying reported for swap transaction (with direction indication CON-473)
    7. Net amount is missing (CON-351)
    8. Transaction report with the same transaction reference number has already been sent for the firm and not cancelled (CON-023)
    9. Transaction for cancellation cannot be found (CON-024)
    10. Transaction has already been cancelled (CON-025)

    The top two rejection reasons both concern instrument validation and I don’t think these will be a surprise to anybody. It’s difficult to know who is responsible for these rejections as the reference data the FCA uses (the ESMA ‘FIRDS’) is not perfect and should not be considered a “golden source” – in Market Watch 54, the FCA reported that “ESMA states that it cannot take any responsibility for this information [FIRDS] being complete, accurate or up to date”. Firms need to report instruments that are reportable (!) but sadly FIRDS may still not be a perfect source to test against this obligation and instrument reference data remains a key concern for reporting firms.

    Whilst firms are at fault for the majority of these rejections, it’s perhaps unfair to blame them exclusively for all the rejections caused by points three through to seven. We know firms have received rejections for missing ‘country of branch membership’ when the ‘venue’ field has been populated with a systematic internaliser (which would appear to be inconsistent with the ESMA validation rule). Some of the other rejections are dependent upon the CFI (instrument classification) being correct in FIRDS and FIRDS hasn’t always been up to the task. Some participants have also questioned whether some of the ESMA validations have been designed correctly. For example, ‘Net amount’ is required for all cash bond transactions, but this validation is determined by CFI code starting with the characters ‘DB’ which unfortunately captures instruments such as ETCs (exchange traded commodities like iShares Physical Gold ETC) which have a debt structure but aren’t the type of instruments that logically have an associated ‘net amount’ value. Similarly, some participants have questioned the relevance of the underlying direction indictor for CDSs and whether the validation is consistent with the example detailed in ESMA’s Guidelines document.

    The FCA continues to provide excellent feedback on reporting issues and the importance of providing complete and accurate transaction reports. However, it would be a mistake for firms to assume that their reports are adequate just because they pass validation and are accepted by the FCA. Validations do not check whether the actual data contained within the reports is correct, something that our quality assurance testing is able to do. The accepted reports are just the tip of the iceberg and it is the issues that lie undetected underneath the water that we are able to identify with our testing.

    Read: Mark Steward, the FCA’s Director of Enforcement and Market Oversight’s speech on MiFID II and the fight against financial crime.

    Further reading: Ian Rennie on the issues we’ve seen so far in our MiFID II testing. 

  • MiFID II reporting: what we’re seeing six months in

    MiFID II reporting: what we’re seeing six months in

    Six months in, MiFID II is still leaving practitioners and regulators alike scratching their heads with a number of seemingly intractable problems. The reporting of derivatives in particular is causing difficulty as firms continue to struggle with reporting eligibility concerns, the misreporting of certain fields and validation issues. Firms have sometimes been unable to get a copy of what they reported to their regulator or approved reporting mechanism (ARM). Taken together, this reduces the efficacy of transaction reporting, says our managing director Ian Rennie.

    Reporting eligibility

    The trials of applying the concept of “traded on a trading venue” (TOTV) are well documented. Although ESMA’s opinion (issued on 17 May 2017) sought to establish a clear meaning of TOTV, concerns persist. There are still teething problems with the infant Derivatives Service Bureau (DSB) service particularly with the interaction of the DSB’s instrument normalisation and the reporting requirements.

    Aside from TOTV there are problems with applying the reportability criteria to transactions involving indices. Identifying accurately which indices contain MiFID instruments is problematic. One obvious example is Boeing which is dual listed as LON: BOE and NYSE: BA. There is, however, no regulatory requirement on index providers to make public the constituents of any index, which are dynamic in nature; moving in and out on a regular basis.  As a result, smaller firms may find it prohibitive to source the appropriate and relevant data to identify reportable index derivatives.

    Incorrect fields being reported and risk of detection

    There have also been instances of inaccurate or superfluous fields being reported. The commodity indicator flag is being populated on non-commodity instruments. Similarly, instrument fields are being populated unnecessarily when the transaction in question is reported with a valid Financial Instruments Reference Data System (FIRDs) International Securities Identification Number (ISIN). Volatile attributes were a late addition to the reporting obligations and overall the industry is still looking to implement this change.

    The UK Financial Conduct Authority (FCA)’s investment in its Market Data Processor (MDP) platform has been significant and gives the regulator a greater capacity to detect circumstances where two parties to a transaction have reported divergent values for the same transaction. This is particularly the case in instances where transactions are traded on a venue and now, as mandated, firms must persist the trading venue ID for the transaction. The FCA can use that ID to pair transactions and then match fields to highlight any discrepancies, which it can then automatically fire out to both firms.

    Obtaining data from competent authorities and ARMs

    Regulatory Technical Standard 22, Article 15, obliges firms to reconcile and test between their internal systems and data provided by competent authorities. Failing the provision of the data by the relevant national competent authority (NCA), firms should use data from their ARM or, as a last resort, use the transaction reports submitted by the firm to their NCA.

    The FCA appears to be a frontrunner, through its MDP system, in providing data back to the firms it regulates. Commitment by other NCAs to provide back to firms their data is not clear and should be closely monitored. That said, the current FCA extract service is not fit-for-purpose; even where firms obtain FCA data through the MDP portal they are unable to reconcile back safely to their own source systems.

    As mentioned above, RTS 22, article 15 points firms to obtain data extracts from their ARMs if not available from the competent authorities. Approved reporting mechanisms have had teething problems as well in their ability to provide data back to firms. In some instances, firms have been limited by the number of transactions they can obtain and there have been problems with the methods available for the data transfer. All ARMs have made significant progress in the area, which is most welcome.

    Efficacy of reporting and communication from the NCAs

    The primary objective of MiFID II reporting is to aid NCAs in the detection of market abuse. Any issues that prevent the correct application of the reporting criteria, reporting inaccuracies or unneeded fields or roadblocks facing firms’ efforts to conduct assurance activities, therefore, will reduce the efficacy of the reporting regime, as will inappropriate requirements.

    One simple example that illustrates this is the reporting of pricing of equity swaps when compared with contracts for difference (CFDs). For equity swaps ESMA’s guidelines require the financing charge to be reported — a piece of information that appears wholly irrelevant to market abuse — while for CFDs, which are economically the same instrument, the price of the underlying is reported.

    In summary, both firms and the regulator still need to do plenty of work to get MiFID II reporting into shape. This is likely to be a long and difficult road.

    Our ReportShield™ quality assurance service gives financial firms peace of mind in the accuracy, completeness and overall quality of MiFID II reporting data. If you would like an assessment of the quality of your MiFID reporting six months in, please contact us.

    A variation of this article was published by Thomson Reuters Accelus, a subscription-only site, on 12 July 2018.

  • Measure for measure: ESMA’s assessment of EU-wide supervisory measures for EMIR

    Measure for measure: ESMA’s assessment of EU-wide supervisory measures for EMIR

    Measure for Measure is classed as a comedy yet it is also considered one of Shakespeare’s problem plays as it has aspects of a tragedy. Dealing with the concepts of justice and virtue, the play sprang to mind when reading ESMA’s recently published report on EMIR supervisory measures.

    This is because the report, which runs to some 40 pages, highlights some significant differences in approach by the national competent authorities (NCAs) on supervision and enforcement of EMIR requirements, as well as the fines and other supervisory actions that have been undertaken to date. The report has both good and bad news for financial firms.

    Let’s start with the good: There have only been three fines raised for EMIR breaches to date across Europe. Two of these fines were levied by COVIP (Italy), one for €105k and the other for €60k both in relation to article 9 reporting breaches and article 11 breaches in respect of clearing activities. Within each jurisdiction, the maximum fines that can be levied are almost consistently low.

    And the bad news: the third fine in our list is the eye-watering £35m fine raised by the FCA for the non-reporting of 68 million exchange-traded derivative contracts.  The per-record penalty applied by the FCA was increased because of prior breaches under the MiFID I transaction reporting regime. That points to the FCA treating reporting failures as a single type of breach irrespective of the reporting obligation concerned. In its final notice, the FCA also took the time to highlight that insufficient testing was carried out to ensure the accuracy and completeness of reports as well as weaknesses in oversight arrangements. And in another piece of bad news, the largest potential fine for those countries that have a cap is France’s €100m. 

    Few investigations across Europe

    Perhaps it’s unsurprising, but not all authorities have been active in conducting investigations since the inception of EMIR.  What is surprising is how few investigations have been carried out across Europe when the number of entities, both financial and non-financial, falling within the scope of EMIR is so vast.  We can’t tell the true number of investigations conducted as the “more than 20” category (as shown below) could hold a great many but we would expect ESMA to have stopped there because it was closer to 20 than 40. 

    In terms of investigations carried out, Belgium is the standout performer with more than 20 investigations being run across reporting, clearing obligation, reporting, risk mitigation techniques and Article 11 in respect of Non-Financial counterparties. On the other end of the scale, we have a number of countries that haven’t undertaken any investigations at all including Ireland, Finland, Norway and the Netherlands.

    Number of investigations carried out on the reporting obligation by country in 2017:

    None

    BU

    CZ

    FI

    HR

    IE

    LV

    MT

    NL

    NO

    SI

    1 to 5

    FR

    EL

    SK

    UK

     

     

     

     

     

     

    6 to10

    AT

    DK

    PL

    SE

     

     

     

     

     

     

    11 to 20

    CY

    ES

    PT

     

     

     

     

     

     

     

    >20

    BE

    DE

    LU

    IT

     

     

     

     

     

     

     

    Another piece of bad news (at least for firms) is that we can expect ESMA to push for more harmonisation and more investigative activity.  ESMA and other competent authorities have been concerned with the quality of reporting under EMIR and MiFID. This, combined with the EMIR regime being in its 4th  year and matching rates across repositories remaining challenging, pressure to improve reporting will continue.  Pressure to ensure compliance with the clearing obligation and risk mitigation techniques can also be expected in the coming year.  

    The report also drew attention to the fact that no work seems to have been carried out in terms of the anti-evasion provisions of EMIR.  This would be a complex area to assess but firms should be prepared for questions on this which means having a handle on what guarantees are in place between EU group entities and non-EU entities.

    Penalties across the EU

    The report highlights the approach to penalties as an area where there is a low level of harmonisation. We’ve created the table below which shows the divergence in percentage terms of the maximum caps (France at €100m) and minimum penalties (Bulgaria €40k) across the EU. 

    In the UK and Spain, there is no stated penalty cap. In the case of the UK, a per record penalty is applied which means that the penalty regime scales to the level of reportable activity and degree of non-compliance for the firm concerned. 

    Country

    Percentage of maximum

    Max € (000)

    Notes

    Spain

    n/a

    –

    Variable no stated maximum

    France

    100.00%

    100,000

    Capped at less than 10x gain made or loss avoided

    United Kingdom

    n/a

    –

    Variable no stated maximum

    Finland (articles 4 & 10)

    10.00%

    10,000

    Capped at less than 10% turnover

    Sweden

    5.00%

    5,000

    Now capped at 10% of turnover but figures relate to a decision when the old rules applied.

    Belgium (National Bank)

    5.00%

    5,000

    Capped at less than 10% turnover

    Italy

    5.00%

    5,000

    Capped at less than 10% turnover

    Greece

    3.00%

    3,000

     

    Ireland

    2.50%

    2,500

     

    Poland

    2.50%

    2,500

    < 10% of turnover

    Belgium (FSMA)

    2.50%

    2,500

    Capped at 3x gain made or loss avoided

    Luxembourg

    1.50%

    1,500

    Capped at 5x gain made or loss avoided

    Netherlands

    1.00%

    1,000

     

    Cyprus

    0.70%

    700

    Capped at 2x gain made or loss avoided

    Germany

    0.50%

    500

     

    Czech Republic

    0.40%

    400

     

    Austria

    0.15%

    150

     

    Malta

    0.15%

    150

     

    Latvia (legal persons)

    0.14%

    142

     

    Finland (articles 9 & 11)

    0.10%

    100

     

    Slovenia

    0.10%

    100

     

    Croatia

    0.07%

    67

     

    Latvia (natural persons)

    0.06%

    57

     

    Bulgaria

    0.04%

    40

     

     

    NCA powers across the EU

    NCA powers are relatively consistent allowing them to: summon and interview personnel, conduct on-site investigations and inspect documents. They also all have the power to issue fines, issue binding and non-binding letters whilst some NCAs have the power to issue criminal sanctions against individuals. 

    Actions firms should be taking for EMIR reporting

    Firms should be reviewing their EMIR control environment. This means assessing the more difficult activities of regular accuracy testing, reference data testing and front to back reconciliations as well as ensuring the governance process is robust and up-to-date. 

    Governance arrangements need to be looking at the operation of the reporting process itself, the assurance process around accuracy and completeness of reporting but also the remediation process, ensuring that known issues are being appropriately escalated, prioritised and remediated which includes replaying records to correct historic errors. 

    While we are known for providing accuracy testing and reconciliation services, we also help our clients mature their broader reporting controls with our Control Framework – all are key components of our ReportShield™ quality assurance service. We also, in conjunction with our consultancy partner Elixirr, run remediation programmes to bring firms’ trade repository records into line.  If you would like to discuss your reporting controls please contact us.

    A variation of this article was published by Thomson Reuters Accelus (subscription only) on 20 July 2018. 

  • FCA makes data integrity a clear focus for 2018/19

    FCA makes data integrity a clear focus for 2018/19

    The FCA recently published its business plan for 2018/19.  In this blog, we highlight the areas impacting regulatory reporting and other areas of interest to us and our clients.

    MiFID II

    As we are now six months into MiFID II, the FCA has signalled its intention to focus on market cleanliness, leveraging the more granular transaction reports that MiFID II requires. Another priority is to look closely at the operation of the primary and secondary markets where transaction reporting data, if it is of high quality, will be useful in its analysis.

    In the business plan’s introduction, FCA Chief Executive Andrew Bailey explains how the major changes resulting from MiFID II requirements will improve “market integrity in wholesale markets”. One consequence, he says, is the “strengthening of the transaction reporting…regimes” and that the FCA “will closely monitor how well firms are complying with these new requirements”.

    Market integrity

    MiFID II’s expanded scope will provide the FCA with more information on transactions. The plan says the FCA will “monitor, detect and investigate potential abuse in these markets and enforce against unlawful behaviour where appropriate.” It will focus “supervision monitoring on the fixed income, commodity and non-standard derivative markets,” and will use “indicators such as market cleanliness data and the number of suspicious transaction and order reports to assess the potential harm from market abuse which damages confidence and participation in the market.”

    The FCA goes on to state that:

    “MiFID II provides us with better tools to deal with potential harms from algorithmic High-Frequency Trading (HFT) by introducing new obligations and systems and controls for both traders and venues. We will focus supervisory efforts on monitoring compliance with these new rules and increasing our understanding of the use of trading algorithms and other innovations across the wholesale financial markets. We will use existing diagnostic work on HFTs, circuit breakers and mini-flash crashes to inform this work. This will enable us to anticipate and deal with potential harms this kind of technological advancement may create.”

    We expect much of the analysis is conducted by using transaction reports as well as using the granular order data from trading venues.

    The FCA plans to publish a report in Q4 of 2018/19 detailing its approach to market integrity. However, the business plan points to the active use of transaction reports by the FCA in the coming year.  It would be reasonable to assume that preceding use of the data, the FCA will undertake some assessment of reporting quality and completeness: the types of business rules alluded to by Ana Fernandes in last year’s Transaction Reporting Forum run by the BBA (now UK Finance). Any errors or incomplete reporting will become more visible to the regulators so we should expect activity in this area probably more likely in 2019 once firms have had an adequate amount of time to iron out wrinkles in their reporting systems. 

    RegTech developments

    The FCA is continuing with its TechSprints and work on the use of advanced analytics. As a RegTech firm, Kaizen is participating in these. An area of obvious interest is its proposals to utilise artificial intelligence/advanced analytics as part of the supervisory process to detection areas of non-compliance. Transaction and EMIR reporting would be obvious candidates for this type of activity as well as:

    • automated detection of unauthorised business activity on the internet through a variety of new technologies
    • testing advanced Natural Language Processing (NLP) technologies and semantic language models in an effort to automate what would otherwise be manual supervisory tasks
    • automated evaluation and detection of misleading advertising.

    The FCA will also be following up on its Call for input on Machine Executable Regulatory Reporting.

    Monitoring firms’ use of data

    The use of data by financial services firms is of obvious interest to the FCA and a potential source of new benefits as well as risks. To address this they will be monitoring the use of machine learning the use of big data pools, algo trading developments and the wider use of artificial intelligence within the regulated community.

    Cryptocurrencies

    Some of our clients execute transactions in cryptocurrencies.  This has been an area of difficulty as there is no clear or consistent treatment of cryptocurrencies across jurisdictions. The FCA sees cryptocurrencies themselves (i.e. those designed primarily as a means of payment/exchange) as being outside their regulatory perimeter. As a regulator, the FCA is concerned about protecting consumers: Initial Coin Offerings (ICOs) and cryptocurrency derivatives represent risks that potentially fall within its remit so the FCA will participate in a forthcoming Treasury Committee inquiry.

    You can read the FCA’s 2018/19 business plan in full on its website. 

  • In the news:  Dario Crispini on post-2008 world and how MiFID has altered the landscape

    In the news: Dario Crispini on post-2008 world and how MiFID has altered the landscape

    Kaizen’s CEO Dario Crispini spoke to Best Execution’s Lynn Strongin-Dodds about MiFID a decade on.

    At the time MiFID was introduced Dario was the head of the then FSA’s Transaction Monitoring Unit and managed the regulator’s transition to MiFID reporting including introducing the approach to fines for incorrect transaction reporting. 

    Here’s an exert from the article:

    Long before the financial crisis wreaked havoc on stock markets and investment banks, MiFID I was being hatched in the hallowed halls of the European Commission. It was officially launched in 2007 with the aim to shake up the status quo in the equities landscape. However, as events the following year proved, much more work was needed to be done to corral the worst of the excesses and improve transparency.

    The dispersion of liquidity has been another major challenge. “The removal of the concentration rules under MiFID I was a good thing, in terms of competition, but one of the unintended consequences was the fragmentation of the liquidity,” says Dario Crispini, founder and CEO at Kaizen Reporting and former manager of the transaction monitoring unit of the Financial Service Authority between 2001 and 2010. “As the market evolved, this led to more complex trading strategies and high frequency traders and algorithmic trading which caused distortions.”

    You can read the full article here. 

     

     

  • In the news: Dario Crispini on transaction reporting data quality with Thomson Reuters

    In the news: Dario Crispini on transaction reporting data quality with Thomson Reuters

    Now MiFID II go-live has taken place, the FCA’s focus is starting to turn to the quality of the transaction reporting data being received by its Market Data Processor (MDP).

    Kaizen’s CEO Dario Crispini spoke with Rachel Wolcott at Thomson Reuters Accelus about the enhanced new tools the FCA has in place for monitoring transaction reporting data quality under MiFID II.

    “Fixing data quality problems early will help firms manage regulatory risk as well as the overall cost of reporting, perhaps even bringing it down,” Dario told Thompson Reuters. 

    “The sooner they (firms) do the data quality assessments they’ll be in a better place to get fixes done without having to reallocate resources to new IT projects. When we look at EMIR and Dodd-Frank Act reporting there’s still issues known about for a long time but there’s just not enough resources to put in those fixes,” he said.

    The FCA’s Market Data Processor (MDP) has far superior analytical tools and exception alerts which will make the FCA’s surveillance more proactive and timely.

    Read the full article: UK regulator to check MiFID II reporting data quality shortly, despite systems glitches (a subscription-only site).

    Trade repositories need constant supervisory hand holding to manage data quality-ESMA

    Dario also spoke to Thomson Reuters about the challenges trade repositories in Europe are facing when it comes to managing data quality issues.

    Read the full article Trade repositories need constant supervisory hand holding to manage data quality-ESMA (subscription-only site).

  • ESMA’s LEI solution is a Grandma-like gift

    ESMA’s LEI solution is a Grandma-like gift

    Thank you Santa, you have delivered the first wish on our Christmas list –  a solution for firms with clients without LEIs!

    Well…kind of.  ESMA has blinked first but late in its long standing game of Chicken with the industry and today announced it has relaxed its approach on the LEI requirements for reporting entities and issuer of financial instruments.  There was very little wriggle room for ESMA as it has no powers to amend the regulation and instead has had to relax one of the validations and pass on significant operational difficulties to firms and trading venues.

    ESMA recognises industry concerns

    In its statement, ESMA recognises three key concerns of the industry. First, that firms will not succeed in getting LEIs for all of their clients prior to 3 January 2018. At the same time, it acknowledges that these clients will still approach firms to trade with them post 3 January regardless of not having an LEI.  Finally, trading venues will face similar problems with non-EU issuers who will not have obtained LEI.  There is a fourth issue of handling corporate actions for clients without LEIs.  These are issues that Kaizen reflected previously in our blogs and publications and ESMA has now been persuaded by the consequences of the LEI obligations. In short, the LEI mandate would result in a scenario where clients without an LEI have no option but to trade with a US located bank or venue resulting in a material outflow of business from the EU financial system.

    A Christmas gift but not for life…

    ESMA’s proposal is a temporary but messy solution so as not to breach the regulations. For a period of six  months from 3 January, investment firms and trading venues can continue to provide trading services to clients without an LEI that would trigger a transaction reporting obligation. But only if two obligations are met:

    • The investment firm obtains the necessary documentation from the client to apply for an LEI on the client’s behalf
    • The trading venue reports its own LEI instead of the  LEI code of non-EU issuers whilst reaching out to them to get one

    Investment firms will have to apply immediately for the issuance of an LEI on behalf of the client and then submit all required reports for that client once the LEI has been issued.  ESMA and the NCAs accept that this solution will cause a delay in reports being made and they will actively monitor the timeliness of late reports.  At the same time, they will amend their validation rules to allow the acceptance of transaction reports where LEI issuance date is after the transaction reporting execution date.  But the FCA have already communicated that they will not be able to make this change for the 3rd January!

    ESMA and your Grandma

    Like Christmas presents from your Grandma, ESMA’s LEI ‘present’ is well meaning but does not quite hit the spot.  Worse of all, it doesn’t come with a receipt that will allow you to exchange for a better gift. The effect upon firms is a messy one:

    • Outreach: Firms will have to, at short notice, reach out to clients to obtain the required data to register them for an LEI and what happens if the client doesn’t want to play?
    • Register and pay for LEIs: Put in place a process at short notice to process LEI requests
    • First Mover Disadvantage: Those firms who respond first will end up paying for LEIs that then also benefit their competitors
    • LEI Duplication: Although the GLIEF system is meant to prevent duplication of LEI issuance, it will likely face its greatest test as multiple firms apply on behalf of clients
    • Excluding Reports: Firms will have to put in place processes to identify and exclude transactions without LEIs and then report once the LEIs issued
    • NCAs not ready: The FCA have already said they will not be able to make the validation changes in time, meaning that they will reject reports even if they follow process outlined by ESMA
    • ARMs and firms not ready: ARM validations and for some firms their own internal validation processes will have to be altered to allow the historic reports to be submitted with newly minted LEIs.

    So –  not quite the present we all wished for and we may well be left scratching our heads in January wondering how to put it together and make it work.  Fingers crossed we have better luck on our other nine items on our Christmas wish list…

  • Dear Santa…a MiFID II Christmas wish list

    Dear Santa…a MiFID II Christmas wish list

    Dear Santa

    I have been very good this year. I planned my MiFID II transaction reporting project early. I read Levels 1, 2 & 3 (well maybe not all of level 3…). I put enough money in the budget, identified my risks and spoke to my peers.  In short I think I have done everything possible but I still think I might be in a little bit of trouble. So this year for Christmas I have one or two wishes that I hope you can grant so I can start the new year with a cheery grin as big as yours.

    Could you and Ruldolph please drop into my stocking this year:

    1. An LEI for all my clients who are refusing to get one even though I have offered to help many times in doing so.  I do want to keep talking to them next year!
    2. Help trading venues send the fields they need to for me to make my report.
    3. May my ARM be able to onward report to the FCA without any issues.
    4. A bright and sparkling new reconciliation that reconciles all my trades and not just the ones I sent
    5. Change ESMA’s mind and let them agree that the FIRDs list is a golden source of data
    6. Please just make ‘shortselling’ either go away or send me a new magical toy that will calculate it every day and correct it even  after I need to include a trade that was not captured the previous day
    7. Some really clever testing that identifies any of my mistakes so I can tell my Senior Manager Regime (SMR) manager all is well and he/she won’t lose their house
    8. Make all corporate actions involuntary even though they aren’t (our secret, Santa)
    9. Now I have lots of friends from different countries and I would like just one way of identifying them not several.
    10. An Xbox with the latest version of Overwatch

    Now Santa I hope you don’t think me too greedy, but compared to my friends in America and Hong Kong I think I might be in more need for Christmas presents than them.

    I’ll leave a mince pie for you and some carrots for Rudolph . Even if you can send me a few of the items I have asked for, I will be happy and I promise I’ll ask a lot less for next year.

    Love from…
    Little Johnny

    P.S If you can’t do 4 and 7 then please drop this letter over to those lovely people at Kaizen Reporting, I am sure they will be able to help!

  • FCA to focus on reporting data quality in 2018

    FCA to focus on reporting data quality in 2018

    The Kaizen team’s previous visit to The Royal Garden Hotel in Kensington was just a few weeks ago when we picked up the Best Compliance & Regulatory Solution award at the Fund Services Awards.  We found ourselves at the hotel again at City & Financial’s one-day conference last week to get a flavour of how ready the industry is for the go-live of MiFID II in the new year. Kaizen’s Ian Rennie is pictured and spoke about how Senior Managers can ensure they’re compliant with MiFID II under the Senior Manager’s Regime. 

    All eyes on reporting data

    The keynote address came from the Financial Conduct Authority’s (FCA) Ana Fernandes and she made one thing very clear: The FCA expects firms to be ready come January 3rd 2018.  Excuses about the complexity of the new regime will be no use to anybody, especially given the amount of time firms have had to prepare for it, she said.  Ana also made the point that a firm’s reporting requirement does not simply end after successful data submission. Constant monitoring is expected post-reporting and any corrections that need to be made should be done quickly. There is going to be a lot of eyes on this data and firms will be called out on anything that looks suspicious.

    LEIs are a key focus for regulator

    Ana went on to explain that one third of the fields in MiFID II are related to counterparty information and that this is a key area that the FCA is focusing on. They want to know exactly whose investments will have a negative knock-on effect in the market.  Of course with this, the mandate of the LEI is justified in the eyes of the regulator.  If firms are still disputing this decision at this stage and have not looked into the deeper complexities of the regulation, they have a lot to be worried about.

    Data quality must be good at source

    The comments on the importance of LEIs were echoed by the next speaker, Francis Gross, Senior Advisor at the Directorate of General Statistics at the European Central Bank. His main focus was on increased harmonisation and standardisation of data and believes that in order to identify market abuse before it is too late, data quality must be good at the source.  He compared financial services data unfavourably to that of retail, saying, “if shops had same data quality as financial services then shop shelves would be bare and there would be queues in the street’.  The reality is that there is no time to cleanse it at the regulators’ end given the quantity of data they receive every day.  

    It’s all about data accuracy

    My take home point of the whole conference was that gone are the days where firms only need to worry about under or over reporting of data.  2018 will bring a shift of focus to the accuracy and completeness of data reported.  Both EMIR RTS 2.0 and MiFID II bring more rigid definitions of data that needs to be reported and firms need to have controls in place to prove they are reporting correctly and completely, something Kaizen is helping its clients with as they prepare for MiFID II.  

    Please contact us if you would like to discuss any points raised in this blog or discuss your preparations for MiFID II transaction reporting.  

  • Transaction reporting tops concerns at MiFID II conference

    Transaction reporting was chief amongst concerns at today’s UK Finance MiFID II implementation conference, where Stephen Hanks from the FCA was keynote speaker.

    At one of the first conferences since the BBA merged with other financial trade associations, Stephen Hanks spoke widely on the expected MiFID II implementation issues, focusing on four main areas of interest:

    • The publication and content of the FCA policy document published 3 July
    • Recent European Commission and ESMA activity
    • Transaction reporting issues
    • Some shared thoughts on how the FCA intends to act over next six months.

    Policy document is technical not guidance

    The publication of the 1000-page policy document had been accompanied by a loud sigh of relief within the FCA but left financial journalists scratching their heads on where to start! Stephen explained that documentation’s primary purpose should be seen as a technical exercise of translating EU legislation, of both the MiFID and non-MiFID variety, into the FCA handbook. There is no significant inclusion of guidance in the document as the FCA wishes to deliver this through their participation in ESMA’s efforts.

    That said, Chapter 2 of the handbook outlines where the FCA is adding additional requirements over and above the EU legislation. The four main areas outlined by Stephen were:

    • Policy and taping of corporate financials and discretionary managers
    • Divergence with ESMA over the appropriate test
    • Research
    • Client classification.

    FCA to provide clarity on issues before 3 January 2018

    On the topic of the appropriate test, Stephen explained that the FCA has decided to ignore ESMA; a decision not taken lightly. Rather it is a decision taken based on the specific prevalence of UCITs and Investment trusts in the UK compared to the rest of Europe  and as such, the FCA will continue to follow to advice previously provided by ESMA’s predecessor, CESR in 2010.

    Over the coming months the FCA, with the European Commission (EC) and ESMA will be focusing on a number of issues to try and provide required clarity before go live on 3rd January 2018. On both share and derivative equivalence, expect further consultation between NCAs, ESMA, EC and the industry and subsequent publications of Q&As. . The topic of commodity limits is taking up considerable time and effort at the FCA with a focus on arriving at the appropriate level of limits. The FCA is placing reliance of ESMA guidelines on how entities should determine trading venue status but are taking  wide and varied soundings from UK firms on whether they should be treated as a trading venue  or a brokerage model.

    FCA has significantly enhanced ability to detect data issues

    Stephen made special reference to transaction reporting highlighting that Zen’s replacement Market Data Processor (MDP) went live with industry testing on the 3rd July with ARMs, to be followed swiftly with APAs and trading venues. He described transaction reporting as a “particular challenge” and recognised that there will “be serious challenges” but made it clear that the “FCA wanted to work with the industry”. That said he explained that MDP will have in-built business testing, similar to that run by Kaizen, to detect data quality issues. In short the FCA ability and capacity to identify data quality issues will be significantly enhanced with the introduction of functionality provided by MDP.

    During the 200 days left to go for MiFID II go-live the message from the FCA was to take all reasonable steps to comply with the obligations, that the FCA recognised the material increase in complexity that MiFID II brings and that these two points will shape the supervisory environment in 2018. If firms do have significant or expect to have significant issues they should be flagged to the regulator as soon as possible and before go-live.

  • Top ten takeaways from the BBA’s transaction reporting forum

    Top ten takeaways from the BBA’s transaction reporting forum

    The head of the FCA’s Transaction Monitoring Unit, Ana Fernandes, gave a clear indication of the FCA’s position on MiFID II reporting at the BBA’s Transaction Reporting Forum this morning. 

    Here are our top ten takeaways from the event:

    1.  “The devil is in the detail” – Ana acknowledged the tension between being prescriptive with detailed rules vs providing general principles for firms to adhere to. 
    2. “MiFID II is an enhanced regime,” not a new regime.  The FCA and the industry are leveraging 20 years or more of transaction reporting experience. Our take on that is expectations for good quality data will be higher than for a new reporting regime.
    3. MDP applications need to be submitted as soon as possible.  The FCA isn’t seeing “as much traction as expected”.  If you delay too much, don’t expect the FCA to turn it around and they won’t differentiate between the types of entities onboarding whether it is ARMs, trading venues or directly submitting firms.
    4. The FCA is ready to commence industry testing on 3rd July but not all reference data will be available due to dependencies on FIRDS.  Any test cases firms are planning will therefore need to take this into consideration.
    5. The FCA is still not seeing many queries from firms and they would expect more.
    6. Traded on a Trading Venue (TOTV) didn’t get much attention other than to say that the FCA expects the scope will apply to a small proportion of instruments once the trading obligation for derivatives is in force.  We will be publishing a blog shortly with our views on TOTV.
    7. New Q&As are being finalised by ESMA covering amongst other things:
      • Increases and decreases in notional
      • Reference data
      • Corporate actions
      • ISINs.
    8. The FCA will be conducting business validations as well as technical validations.  The technical validations have been published but she did give some indication that the business validations will cover quality tests including matching between reports across firms and other data such as order book data and trade reports.  The FCA expects firms to do the same as part of their data quality efforts.
    9. Where issues are identified, notifications to the FCA should take place in the same manner as today. 
    10. Leniency – on prompting from the floor regarding leniency in the early days post go-live, Ana stated that the FCA will consider each case on its merits. 

    It is clear the importance of effective data quality tools especially reconciliations is paramount in the mind of the regulator.  Ana was clear the FCA expects firms to have reconciliations in place at go-live.  Kaizen will be offering cross-entity reconciliations where there’s agreement between parties to help firms meet this requirement.  Do get in touch if you’d like to discuss this or any of your MiFID II reporting requirements further. 

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

  • FCA provides timeline for MiFID II testing services

    FCA provides timeline for MiFID II testing services

    The FCA has published details of how interested parties can register to connect to their MiFID II data submission service and has also announced that they will provide testing facilities six months ahead of MiFID II go-live.

    The Market Data Processor (MDP) service replaces the current transaction reporting system Zen and will be operated and supported by a third party, Sopra Steria. The MDP also provides the mechanism for other Data Reporting Service Providers (ARMs, APAs and CTPs), trading venues and systematic internalisers to submit the instrument reference data required under RTS 23 and trade data required by ESMA to calculate the double volume cap as per RTS 3.

    Some parties such as our partner UnaVista are developing services to support MiFID II including an instrument static submission service so parties won’t have to register and pay the connection and annual fees to use the MDP service directly. In addition to a substantial cost saving, it has the benefit of validating the data before submitting it to the FCA.

    The MDP service specifications will be available to registering parties from the end of September and from Q4 for commodity position reports. A test environment will be available from 1 July 2017 allowing connecting entities and those further down the chain a good deal of time to undertake comprehensive testing prior to the MiFID II go-live date of 3 January 2018.

    Sopra Steria will also be managing the data extract service. This is the mechanism by which samples of submitted transaction reports can obtained for testing the veracity and completeness of the submissions. This process is expected to be conducted by all reporting firms as part the controls required to comply with RTS 22 Article 15 paragraph 3.

    Useful link: MiFID II Regulatory Technical Standards.

  • FCA publishes second MiFID II consultation paper

    FCA publishes second MiFID II consultation paper

    The FCA has published its second consultation paper (CP 16/19) on the implementation of MiFID II.

    This consultation paper covers a range of issues including position limits and reporting for commodity derivatives, systems and controls requirements for firms providing MiFID investment services and client asset protections.

    The FCA’s CEO Andrew Bailey, reiterated the importance of firms continuing on with their MiFID II preparations despite the outcome of the EU referendum.

    “MiFID II contains important measures to enhance investor protection and bolster financial stability. It reflects recent themes of UK conduct regulation, such as improved controls on the manufacturing and distribution of financial products, and it implements the international commitments the UK entered into to reform derivatives markets following the financial crisis. As we said in our statement following the EU referendum, firms must continue to abide by their obligations under UK law, including those derived from EU law and continue with implementation plans for legislation that is still to come into effect,” he said in a statement.

    The FCA published its first consultation paper on MiFID II on 15 December 2015 (CP15/43) and there will be a further consultation paper later this year.

    The closing date for responses to consultation paper CP16/19 is 28 October 2016.

    MiFID II comes into effect on 3 January 2018.

  • Why data quality is key to regulatory reporting compliance

    Why data quality is key to regulatory reporting compliance

    The FCA has used its latest MarketWatch newsletter to remind firms of their transaction reporting obligations, the persistent poor quality of their reporting, and that the FCA have mechanisms in place to detect errors which may result in stringent actions such as fines.

    While this message isn’t new, the FCA has also published a table showing approximately 650,000 data quality breaches across the industry over a one-week period where the FCA’s Transaction Monitoring Unit (TMU) tested only four of the transaction reportable fields. It will be a disappointment to the FCA that in each instance the errors are ones previously made by firms sanctioned for incorrect transaction reporting as well as errors highlighted in previous Market Watch newsletters. These include things such as late reporting of transactions, incorrect MIC codes, wrong execution times, wrong quantity or missing unit price.

    Just the tip of the iceberg

    The one-week snapshot by the FCA does not reveal the true size of the problem.  We took a closer look and analysed in detail the findings of the publicly available fines issued to firms for incorrect transaction reporting since 2009.  Our findings are displayed in the graphic above.

    1. Tip of the iceberg: Maybe not the perfect analogy, but for those firms fined and where information is publicly available, we found only 35% of the firm’s reportable transactions were reported accurately and completely. That is to say, passed ARM validation and the data was correct.
    2. Base of the iceberg: That leaves 65% of the firms’ reportable transactions being reported incorrectly or not at all. In all cases, firms did not have appropriate controls in place to identify and test the correctness of their reports. In short, they were unaware that the majority of their reports were incorrect.

    Only 7% of the transactions were not attempted to be reported or were duplicates.  All of the remainder were breaches where the report passed validation but the data was incorrect. In other words, they were ‘valid but wrong’.

    Transaction reports must be tested at source

    What this tells us is that firms need testing at source not just ARM validation. Even after eight years of MiFID transaction reporting, numerous warnings and increasing fines from the FCA, significant numbers of transactions are being reported incorrectly with firms unaware of their inaccuracies. In addition, firms are deriving false confidence from passing the validations provided by ARMs and the FCA.

    Importance of getting reporting right

    In Market Watch 50, the FCA TMU makes it clear that they see failure to produce current MiFID reports of good quality as an indication on how well a firm can meet its future and more complex obligations under MiFID II/R and in part, compliance with the recently introduced Senior Managers Regime.

    It says: “The ability of firms to submit accurate and complete transaction reports is essential if they are to be in a strong position to meet the more complex requirements of MiFIDII/R.” It also reminds firms: “If we continue to find firms that fail to identify or mitigate risks associated with market abuse then we will take stringent action against those firms. These actions could include penalties such as fines.”

    This echoes the warnings raised by the FCA in all of the public fines for transaction reporting. The obligation to make complete and accurate reporting is also unambiguously clear through the FCA Handbook (SUP 17) and the Transaction Reporting User Pack (TRUP 3.1).

    Detecting market abuse

    In Market Watch 50, the FCA also reminds the industry of how important a tool transaction reporting is to allow them to detect market abuse.  Poor quality data directly affects the ability of the FCA, European competent authorities and other regulatory bodies such as the Bank of England to detect market abuse or carry out their supervisory responsibilities.

    Where to from here?

    The picture illustrated by the fines for transaction reporting is one where a large majority of reported transactions have passed high levels of validation but the data is still inaccurate. Failure by firms to report correctly is a major industry problem. Firms need to change their approach to protect themselves under the current MiFID regime and the upcoming MiFID II/R in 2018.


    Kaizen’s ReportShield™ accuracy testing checks transaction reporting data at source and identifies transactions successfully submitted to ARMs and the FCA but still wrong.  An independent, managed service, ReportShield is already being used by a number of firms to provide reporting assurance and deliver confidence to management and the regulator. The service significantly reduces risk to firms, offers protection to managers who have SMR responsibilities, and is delivered at a significantly lower cost than testing in-house.

  • Updates From The Deutsche Boerse Buy-Side Working Group

    Updates From The Deutsche Boerse Buy-Side Working Group

    Stephen Hanks from the FCA provided some interesting feedback about MIFID II progress at the Deutsche Boerse Buy-Side Working Group (April 21) which we were speaking at and attending. We wanted to share some of the key points we learned at the event.

    Broad points of interest:

    • The finalised delegated acts for MiFID II should be published next week (week commencing 25 April) closely followed the week after with MIFIR delegated acts.
    • The FCA advised that with regards to the waiver volume caps, the debate continues around the appropriate calculation approach. This highlights the ongoing industry concerns regarding these caps being exceeded and all activity in a security being fully lit. As discussed at the working group, it is too early to assess the impact this could potentially have.
    • Questions also remain about principle trading by an institution operating an MTF and what the firm operating the MTF could put through the platform.
    • The FCA also suggested that EU level discussions implied that systematic internalisers would not be able to use matched principal activity as their primary trading model on the SI platform as such activity is considered to fall outside the purpose of the SI regime. The FCA advised that questions also around price improvement under the SI regime should also be dealt with in the delegated acts to be published in the next couple of weeks.

    From a transparency perspective the FCA provided the following comments:

    • Regarding the establishment of a CTP for equity securities, no indications of interest have been received by authorities from potential service providers.
    • For non-equity securities there will now be a phased approach for SSTI.
    • The FCA confirmed that size thresholds for bonds and the present 100k euro threshold was also being looked at by ESMA.
    • As per recent statements, ESMA will also be producing new advice for non-equity transparency.

    From a transaction reporting perspective:

    • ESMA is also reviewing the definition of an ARM and what activities would trigger the requirement to register as an ARM. Debate has been raised as a result of there being unregulated intermediaries conducting key activities between the regulated firm and its ARM. This would mean that regulators would only have locus over a portion of the process and not all of it.
    • The FCA advised that although there are questions around the benefits of including ‘short selling’ flags in the transaction report, this will remain a requirement.

    The main take away here is clearly the timing around the publication of the finalised acts. This will firm up requirements being created under the legislation. Those managing the MiFID II projects have been waiting for the acts to be finalised to progress the work required which is significant for all financial firms. The acts are also bound to raise further discussion points and once published, will provide the platform for progressing with the Level 3 work.

  • Continued uncertainty around future transparency under MiFID II

    Continued uncertainty around future transparency under MiFID II

    The European Commission’s late pushback on MiFID II will cause the industry further headaches and has not surprisingly frustrated ESMA.

    Last week, the Commission rejected three of the 28 MiFID II technical standards asking ESMA to take another look at them.

    ESMA has responded in three open letters, saying it will get to work straight away but has made it clear that the Commission has not followed procedure and should’ve got back to it by the end of December, not nearly three months later.

    One of the issues the Commission has asked for a rethink on are ESMA’s proposals for bringing more transparency to the bond markets – something we here at Kaizen are particularly interested in.

    Damage to liquidity

    The Commission’s concerns around bond market transparency are consistent with the views of the industry. The minutes of the FCA’s recent trade association roundtable highlighted not just worries from a bond market perspective but whether appropriate and equal consideration is being applied to the other asset classes coming into scope for transparency under MiFID II such as derivatives. The new regulation is clearly attempting to remove the opaque nature of these sectors. However arguments continue that the MiFID II RTS as currently drafted would potentially damage liquidity and would in fact be harmful to liquidity providers. The Commission has clearly acknowledged these concerns and ESMA is now revising its approach.

    Further challenges for implementation

    Although a rethink on MiFID II transparency may initially appear positive, for the industry as a whole it creates further problems. Without clarity on these standards, firms will have to make broad assumptions around the current guidance as they progress with MiFID II implementation. It is unclear how long it will take ESMA to review, but the European Parliament has been clear that further delays beyond 3rd Jan 2018 are not an option and the deadline must be met.

    Considerable challenges

    ESMA’s response not surprisingly has highlighted the ongoing frustrations that exist in this extremely delicate and challenging area.

    ESMA’s letter reveals that the Commission views the current transparency proposals on calculating liquidity inappropriate and that more frequent, timely calculations are required. It is understandable given that within the new market sectors liquidity fluctuates dramatically over short periods and a liquid security can rapidly move to being illiquid. ESMA has already faces considerable challenges sourcing the data to calibrate the regime as the MiFID only gives them the power to obtain transparency data post MiFID go-live.  In recognition of this conundrum the draft text proposes all FX derivatives be classified as illiquid for the transparency reporting obligations until such time as ESMA is able to source and assess more meaningful data.

    Developments here will need to be closely monitored as small changes in the regulations have the ability to create a major impact on MiFID II projects.

  • 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.
  • MiFID II fee proposals – how will they impact you?

    MiFID II fee proposals – how will they impact you?

    Feedback on the FCA’s fee proposals to recover the costs of submitting data under MiFID II is expected to be released shortly.

    The consultation began in November and finished early last month.  The proposals may have slipped notice however the fees will need to be included in the budgeting process going forward and may significantly impact smaller commodity derivative trading firms and firms that are (or are considering) becoming operators of a trading venue.  The proposals are summarised below and will be of interest for firms that will operate an MTF, OTF or a regulated market under MiFID II as well as firms executing commodity derivatives or acting as a systematic internaliser.

    More transactions, higher fees

    Whilst the costs are not excessive, if firms submit reports directly to the FCA the costs are likely to be prohibitive for smaller firms pointing to the need for intermediaries such as Approved Reporting Mechanisms (ARMs) to aggregate submissions, particularly for commodity position reporting.  The consultation paper doesn’t provide any hint as to the ongoing maintenance and administration costs to run the service but this is likely to be substantial.  The consultation proposes that these costs are raised from the ‘relevant firms that benefit from effective market reporting’.  It is not clear what they mean by this but I suspect they are referring to a per report fee that will be levied on the firms for which the report has been made.  So that means the more transactions, the higher the fees.

    Data Reporting Service Providers

    MiFID II creates a new type of entity called the Data Reporting Service Provider (DRSP).  This category encompasses ARMS, Approved Publication Arrangements (APAs) and Consolidated Tape Providers (CTPs).  Each of these entities require authorisation by a competent authority under the DRSP regulations but in addition, as they have to submit data to the competent authorities, they need to connect to the competent authority’s systems.

    To capture this data the FCA is looking to appoint a Market Data Processor (MDP) who will manage the connectivity and processing of the above data.  The costs of the MDP, authorisations and ongoing supervisory activities have to be recovered.  The FCA’s fee consultation paper sets out their proposals in this regard.

    FCA application fees

    There is a separate fee structure proposed for DRSPs (ARMs, APAs and CTPs) as they are regulated outside of FSMA (The Financial Services and Markets Act).  The DRSP fees will not apply to entities that are “incoming” DRSPs.  Incoming DRSPs are ARMs, APAs and CTPs that are authorised in another EU jurisdiction.  Incoming DRSPs will have to contribute to the costs of connecting to the FCA’s systems but will not face application fees.

    Investment firms providing DRSP services will incur the DRSP fees in addition to their FSMA fees.  Such applications will not be treated as variation of their existing permissions but as full applications as it is under a separate regime.

    FCA periodic fees

    Periodic fees have been proposed as a new G25 fee block for DRSPs.  Rates will be confirmed once the FCA’s costs are better known.  The periodic fees apply for the first quarter pre MiFID go-live as a flat rate fee of £20-30k for each authorised DRSP.  Where the DRSP is authorised for more than one category, e.g. as an ARM and an APA, the proposal is an additional 50% of the periodic fee for each additional DRSP category.

    The tables below set out the proposed fee structure.  If the fees collected fall below the costs incurred overall by the FCA then the difference will be collected via periodic fees.

    FCA DRSP fees

    [supsystic-tables id=’2′]

    FCA data submitter on-boarding fees.

    Only one connectivity/on-boarding fee would be applicable for the MDP.  So if a firm is connected for transaction report submissions they would not have any additional on-boarding fee for other data types.

    [supsystic-tables id=’3′]

    FCA ongoing transactional fees

    It is not clear how the regulator’s ongoing costs of operating the reporting system will be recovered but we anticipate that there will be a fee per transaction report made.  This could be levied directly on the parties submitting to the FCA, principally the ARMs and trading venues and if so, these parties are likely to pass through these costs to their clients, the reporting firms.

    *subject to change

  • MiFID II implementation roundtable

    MiFID II implementation roundtable

    For those tracking MiFID implementation activities, the FCA have posted their minutes from the October MiFID II Implementation Roundtable with trade associations.

    The minutes largely cover communication plans including the provision of webinars and other supporting materials to help with the implementation and interpretive challenges that exist.  A couple of areas they covered of interest is the use of endorsed industry guidance which the FCA wants to move away from. However they did say they would be happy to review material produced by the trade associations which is encouraging.  They also cover feedback on its recent MiFID II conference.  See our earlier blog.

  • 10 things we learned at the FCA’s MiFID II conference

    10 things we learned at the FCA’s MiFID II conference

    Like many of our clients MiFID II is uppermost of our minds at the moment. And on Monday we were discussing all things MiFID II at the FCA’s MiFID II Wholesale Firms Conference in London. Likely to be the first of many conferences about the new regulation, this was probably the earliest event possible given the regulatory technical standards (RTSs) were only released on 28 September.

    Our advice to firms?  Don’t delay: Get your heads around the new rules and get into the detail quickly.

    Here are our key take aways from the conference:

    Regulatory Process

    1. The UK is now working towards transposing the MiFID text into UK law and this must be completed by 3 July 2016 while the European Commission now has three months to consider the published regulatory and technical standards. The FCA’s view is that it is unlikely that the Commission will impose any changes and this position will be affirmed by Q1 2016.  The FCA will publish further consultation papers and these are likely to be split with a consultation paper in December 2015 and an additional one in early 2016.

    2. Regarding the timeline, the FCA acknowledged this is challenging for the industry and regulators alike. However delays to MiFID II are only possible if the Commission considers this is appropriate and it is not within the college of regulators’ powers to impose.  That said, we do think there will be a request for either a partial or full delay given the truncated timetable for what will be a lengthy legislative process.

    3. Organisations not currently within the scope of MiFID I may potentially fall into MiFID II particularly around the commodities space.  These firms will need to quickly plan how they will manage this authorisation process and should submit applications to the FCA by 3 July 2016.   Applications submitted post 3 July will be processed by the FCA on a best efforts basis but there will be no guarantee that applications will be completed before MiFID II goes live in January 2017.  Something that could be very detrimental to business.  A similar story applies to firms that will have to apply for trading venue status OTF or MTF, high frequency trading firms, or as a systematic internaliser.  All activity within firms will need to be assessed to confirm whether authorisation will be required and many platforms are expected to be captured such as broker crossing mechanisms which will come under the new OTF regime.

    Transparency

    4. Following a review by ESMA, the FCA confirmed that agreement had been reached on the approach to be adopted towards the calculation of liquidity and the transparency obligations that would therefore be imposed in respect of non-equity securities.

    5. ESMA, following extensive consultation with industry participants and having reviewed considerable datasets, proposes the liquidity calculation will be applied on an Instrument by Instrument Approach (IBIA).  The FCA believes this will mean real-time transparency reporting obligations for 4% of bonds with a significant portion of these being from sovereign debt.

    6. With regards to deferred publication regime, delays will be possible between two days and up to four weeks from the point of execution.  Venues will also be able to apply for pre-trade transparency ‘waivers’ where the execution is above standard market size. The FCA asked that venues apply for such waivers as soon as possible given that approval is required ahead of trading activity if reliance is to be placed upon any such waivers.

    Commodities

    7. Position limits will be imposed in the commodities sector. The limits will have a cap of between 5-35% of the deliverable supply. Such limits also extend to firms’ open interest positions which imply a potential delivery at such a level. Similarly, the FCA also confirmed that thresholds will be applied to speculative trading in such instruments, and firms exceeding the threshold would require authorisation under MiFID II.

    8. Position limits represent significant challenges for groups with multiple entities trading commodities as the limits are applied both across the group and to each entity so one entity in the group could be within the limits, while across the group the combined total exceeds the position limits. This type of calculation is also to be applied when evaluating whether a firm’s commodity trading activity is ancillary to its main activities or not.  Such calculations look at both the individual entity’s positions and the net positions across a consolidated group.

    9. Position reporting by venues is also a requirement under the new regulations.  The FCA is fully aware of the challenges that the requirements place, not least the need to identify clients down to the ‘end client’.

    10. In transaction reporting, the RTSs are pretty clear but one area we sought clarity on was the new complex trade ID field.  This field seeks to link trades that are part of a wider trading strategy.  Ana Fernandes from the Transaction Monitoring Unit gave a very clear exposition of the aims and drivers behind RTS 22 and confirmed that the aim was to capture true strategies and the intention was not to cover hedging activity or even matched principal activity (riskless principal). However Article 12 wording still points to these transactions being captured.  It is also worth noting that in the RTS ISINs are the only identifier for trading venue instruments.  We expect that was a shock for the likes of Eurex and ICE as the consultation proposal was for Aii codes as well as ISINs.

    What we liked:  In the last session, a panel of regulators including ESMA, BaFin and AMF were quizzed by Nick Bailey of the FCA.  We saw this as very positive in that it shows the regulators are talking to each other; indeed they said that such collusion would be in breach of the competition laws were they operating as firms.

    Once the regulators have had more time to digest the detail of the 900+ pages of RTSs we hope to see more of these events with greater detail and elaboration of the implications for firms and their trading activities.

    In addition to our testing services, we are offering training courses for firms on the reporting elements of MiFID II. If you are interested please contact us. 

     

  • ESMA writes the control section of your transaction reporting BRD…

    ESMA writes the control section of your transaction reporting BRD…

    ESMA has published its eagerly awaited regulatory technical standards (RTS) for MiFID II for consideration by the European Commission.

    Chapter 7, Market Data Reporting (RTS 22) outlines the obligations for transaction reporting. And for those responsible for drafting their firm’s control section of the Business Requirements Document (BRD) Article 15 of RTS 22 makes their job very easy! Recent regulation, whether it be the Dodd Frank Act (DFA) in the US or EMIR in Europe, has become increasingly prescriptive of the controls expected of participating firms. Article 15 takes this prescriptive nature into a different league, placing testing and reconciliations front and centre.

    MiFIR (Article 26(7)) requires firms to verify the completeness, accuracy and timeliness of the transaction reports they submit. RTS 22 expands on this and explains that complete and accurate reporting data is essential to market surveillance and outlines how that is to be achieved.

    Under the first section of Article 15 there are the usual requirements relating to the security and functionality of data and measures to enable timely resumption of reporting when reporting systems go down and measures to identify errors and omissions.  More specifically there is requirement on firms to have mechanisms to avoid duplicate reporting and under reporting.

    Whereas over-reporting is tolerated under current obligations, reporting transactions where there is no obligation is not permitted and Article 15 says firms will need to have mechanisms in place to identify over-reporting.  Over-reporting is the submission of a transaction report where it is not required under the reporting rules.  This can be reporting a trade on an instrument that is not reportable or reporting a transaction on a non-reportable event such as dividend reinvestment.

    When firms become aware of any of these types of errors or omissions they need to be reported to the relevant competent authority. To that end ESMA mandates not only reconciliations but specifies the data sources and fields to be included; reconciliations should be between front office trading records and information contained in transaction reports and checks should be in place to prove the timeliness of reports and the accuracy and completeness of all the individual data fields.

    In tandem with regular reconciliations, Article 15 states that firms are required to put in place a testing methodology and approach for their reporting processes. The multimillion pound fines issued by the Financial Conduct Authority for transaction reporting breaches over the last five years have often been on transactions which have been reported as valid and been through some form of reconciliation process but ultimately have still breached Chapter 17 requirements of the supervisory manual.  It is these breaches that your testing approach must be able to identify.  The often piecemeal, sample-based testing that is common in firms today will not be satisfactory.

    Kaizen Reporting’s testing approaches are setting the industry standard and will enable you to meet your MiFID II requirements efficiently and cost effectively. We combine unrivalled regulatory knowledge with the latest data analytics to provide the highest level of confidence in transaction reporting. 

  • EMIR level 2 validations – are you ready?

    EMIR level 2 validations – are you ready?

    At the end of October ESMA is introducing new validations to be applied by Trade Repositories (TRs) which I think will be a good thing for reporting quality.  In this article I provide some context to the changes, but contend that validation on its own is not enough to deliver quality reporting.  Validations cannot identify records that are valid but wrong.  For that we need a much smarter approach.

    ESMA and national competent authorities have expressed concerns around the quality of reporting today and they expect firms to address this.  But to promote quality ESMA has taken its first step towards improvement with the introduction of additional validations.

    Some background

    ESMA originally required the TRs to apply very limited validations to EMIR reports. The idea was that the TRs would not reject records because of problems in data quality and submissions would not be delayed by problems with one or more data fields within the report.  Therefore ESMA and other regulators would have access to the data that was available irrespective of quality.

    This approach makes more sense the more data that is submitted with each record.  The reason is that with strict validation, a single error in one field would prevent the remaining data from being received by the TR.  However, this approach requires the reporting entity to have a strong control framework in place to ensure that errors are self-identified and rectified.

    The limited validation approach initially adopted by ESMA differs markedly from that taken for Transaction Reporting.  On launch of the Approved Reporting Mechanisms (ARMs) regime in November 2007 a detailed set of strict validations was specified by the FSA (now the FCA) to be in place before an ARM would receive authorisation. These validations are applied by the ARMs to all records submitted by reporting firms and if the record failed a validation it would be rejected by the ARM and the firm notified.  I am calling this approach strict validation.  Many firms apply their own validations prior to submitting their records to an ARM and the FCA also applies strict validation at the point of receipt creating multiple layers of strict validation the vast majority of which is duplicative.  So we see very low industry rejection rates for reports sent by ARMs to the FCA.

    Benefits of strict validation

    The primary benefit of strict validation is that the submitting firm keeps ‘holding the baby’, i.e. they know when their submission has failed and will be in breach of the timeliness obligations.  They are in effect forced to act to remedy the problem.  The reporting entity does not need to have a good control framework in place to know that they have a problem that needs fixing.

    ESMA has now undertaken a volte face and now requires the TRs to apply strict validations.  Nearly every field is subject to some sort of validation requirement per the L2 validations.

    The change in validation approach clearly introduces new challenges and costs for firms as well as the TRs.  These validations would have been better implemented before EMIR go-live, but it has taken the experience of poor quality data to crystalise this decision.

    So what should firms be doing to prepare?

    There is the immediate problem of ensuring that you will be able to continue to report post October.  That means assessing the impact of the new validations on existing positions and correcting in advance any errors that would result in updates to those positions being rejected.  Similarly, firms should consider whether their process for dealing with rejections can handle an increase in volumes particularly in the early period.

    More than that, firms should be looking at how to identify records that are valid but wrong.  This requires testing of the EMIR reports at the Trade Repository and reviewing the adequacy of their control framework over EMIR reporting more generally.  Errors can be introduced into the reporting process or are a result of an incorrect interpretation of the reporting requirements so care must be taken to ensure that the testing that is conducted doesn’t build in the same interpretation errors.

    More can be said on testing but I will leave that for another post. If you have any views on the above I would be keen to hear them.