Tag: MiFIR

  • Key themes from our webinar: The Regulatory Reporting Landscape in 2026

    Key themes from our webinar: The Regulatory Reporting Landscape in 2026

    Regulatory reporting is entering a new phase as the era of large-scale refits and rewrites across G20 regimes comes to an end but the pressure on firms has not let up.

    In our recent webinar, The Regulatory Reporting Landscape in 2026, our regulatory specialists explored what this shift means in practice and where firms should be focusing their attention now.

    Below are some of the key themes discussed during the session.

    From regulatory change to regulatory scrutiny

    Following several years of extensive refits and rewrites across G20 reporting regimes, regulators are now entering a period of reassessment. While proposals for change are on the table including the Financial Conduct Authority’s (FCA) MiFID transaction reporting consultation and ESMA’s Call for Evidence on reporting simplification, firms are operating in a landscape where scrutiny is increasing.

    Across jurisdictions, regulators are placing increased emphasis on the quality, consistency and usability of reported data. But firms should be aware that ‘simplification does not mean deregulation’. Regulatory data remains key to market abuse detection, financial stability monitoring and risk-based supervision and has an increasing number of other uses, making the quality of reported data even more important. Regulators are actively using today’s data to assess risk and exposure, so firms cannot take their eyes off the ball.

    Diverging timelines but shared direction of travel

    One of the central themes of the webinar discussion was the differing pace of change between the UK and the EU.

    In the EU, the European Markets and Markets Authority (ESMA) is currently in a period of reflection following its Call for Evidence on transaction reporting, with no immediate changes to reporting expected in the short term. By contrast, the UK’s FCA is already moving forward with proposals to simplify MiFID transaction reporting, including descoping certain instruments, removing reporting fields and revisiting existing guidelines.

    Despite these different timelines, the underlying direction of travel is the same: simpler frameworks, fewer data points and reduced costs of reporting, but higher expectations around data quality and controls.

    Data quality is the focus for all regulators and firms

    Live polling during the webinar revealed that improving reporting accuracy is the top priority for firms heading into 2026, ahead of preparing for future regulatory change or investing in new reporting platforms.

    Common reporting errors highlighted in the webinar included:

    • Inconsistent counterparty data

    • Collateral and valuation reporting

    • Reference data quality

    • Repeated or overlapping data fields that do not reconcile cleanly.

    These issues can occur even in mature reporting environments and often only come to light through deeper data quality analysis.

    EMIR and other G20 regimes – expanded requirements

    Although EMIR and other OTC derivative reporting regimes are no longer in rewrite mode, the webinar highlighted that 2026 will still bring operational challenges. There are expanded reconciliation requirements for EMIR, evolving guidance and increased supervisory focus. This means that firms cannot afford to treat these regimes as ‘business as usual’.

    Regulators in North America and APAC are also shifting attention towards data governance, control frameworks, UTI and UPI usage, and delegated reporting oversight.  A recent report from ASIC that reviewed the CFD sector, shows how reporting quality is increasingly being used as a proxy for governance.

    What does this mean for firms? 

    A consistent message throughout the webinar was the importance of knowing your current state. Firms that have a clear understanding of their reporting processes, data lineage and controls will be far better placed to respond to both supervisory scrutiny and future regulatory change.

    Rather than waiting for what comes next, firms should use this period to stabilise business-as-usual reporting, remediate known data issues and strengthen governance foundations.

    Watch the on-demand webinar to hear the full discussion, including regulator-focused insights, live polling results, and audience Q&A with our regulatory reporting specialists.

  • INTC or not INTC? FCA expectations for aggregate client accounts under MiFIR Transaction Reporting

    INTC or not INTC? FCA expectations for aggregate client accounts under MiFIR Transaction Reporting

    One MiFIR transaction reporting convention that continues to trip firms up is the aggregate client account: INTC. In this blog, we take a deep dive into how INTC is supposed to work and why regulators keep coming back to it.

    INTC isn’t obscure. It’s everywhere:

    • 108 references in ESMA reporting examples
    • a clear legal basis in RTS 22
    • detailed direction in the ESMA Guidelines
    • repeated warnings in FCA Market Watch 62 and 70, and 
    • extensive coverage again in the FCA’s discussion and consultation papers.

    So why does it still go wrong so often?

    The legal foundation for INTC: RTS 22

    RTS 22, Article 11 is clear about the objective of INTC: to enable effective market monitoring, transaction reports must include exact information on any change in position of the investment firm or its client at the time the transaction took place. Firms must therefore report related fields consistently, and report different legs of a transaction such that their reports, collectively, provide a clear overall picture that accurately reflects changes in position.

    INTC is one of the conventions that allows firms to meet this objective, but only when used exactly as intended. ESMA fills in the “how” in the Guidelines.

    What INTC actually is (and isn’t) under MiFIR

    The ESMA guidelines define INTC clearly: the aggregate client account (INTC) is a reporting convention used to provide a link between the market side and client side of transactions.

    It therefore:

    • is not “real”
    • does not represent ownership
    • does not indicate internal position-taking
    • must never introduce a net position.

    When a firm aggregates multiple client orders and executes them in the market, INTC provides the bridge that allows a regulator to connect the market execution and the allocations to the underlying clients.

    That bridge must be temporary. Any movement through INTC must net to zero within the same business day.

    When INTC may be used in transaction reporting

    When reporting with INTC, there must always be:

    • a market-side transaction(s) into or out of INTC, and
    • corresponding client-side transactions out of or into INTC

    The ESMA guidelines are unambiguous: INTC should only be used in the circumstances set out in the guidelines. It shouldn’t be used for:

    • an order for one client executed in a single execution, or
    • an order for one client executed in multiple executions.

    And where there is a transfer into INTC, there must be a corresponding transfer out within the same business day, so the aggregate client account is flat.

    FCA Market Watch: repeated warnings

    The FCA has been flagging misuse for years. In Market Watch 62, the FCA highlighted firms:

    • using INTC for single-client orders, and
    • reporting flows that did not net off on the same business day.

    In Market Watch 70, three years later, the same issues remained:

    • one client, multiple fills reported via INTC
    • INTC used to signal an internal trading account, and
    • missing the market-side or client-side leg altogether.

    The underlying message is consistent: INTC is not a convenience field. It is a controlled linking convention.

    The scale of the problem: FCA policy papers

    The recent FCA discussion and consultation papers add numbers to what had previously been more of a supervisory narrative.

    The regulator’s analysis shows

    • one in five firms had INTC imbalances
    • seven per cent of all INTC reports contributed directly to those imbalances.

    Across the most recent full year of FCA analysis (2023):

    • 342 million reports used INTC
    • 447 firms used INTC.

    The FCA considered whether to introduce more precise linkage mechanisms between market and client side. The direction of travel in the consultation is to rule that out because implementation costs would outweigh benefits and increasing complexity could worsen data quality.

    In other words: the regulator is not planning to redesign INTC for firms but it does expect firms to use it properly.

    Why the FCA cares so much about INTC

    INTC errors are not cosmetic. When INTC does not net to zero – or is used incorrectly – the consequences are material:

    • regulators see phantom positions
    • ownership appears to pass through firms incorrectly
    • market abuse surveillance becomes distorted
    • aggregation logic breaks down.

    In short: market reconstruction fails.

    What firms should be doing now

    For MiFIR firms, the message is clear. The regulator has acknowledged that structural change may not be beneficial which means it will expect higher accuracy within the existing framework.

    1. Re-validate your INTC logic:
    • is INTC used only for genuine aggregation across multiple clients?
    • does it net to zero by instrument, per day?
    • do your reporting scenarios adhere to the guidelines?

    2. Expect supervisory scrutiny:

    • the FCA is clearly focusing on INTC
    • guidance will be reviewed, but the existing expectations already apply
    • less complexity in the regime means the regulator will expect greater precision, not less.

    Four simple letters – ‘INTC’ – have an outsized impact. Getting it right is one of the simplest ways to materially improve transaction reporting quality – and one of the easiest ways to stand out for the wrong reasons if you don’t. 

    While you are driving home for Christmas or taking your chance on the trains, worrying that you’ll be getting a FCA letter about INTC, please get in touch. Our award-winning ReportShield quality assurance highlights any issues you may have with INTC and once you know you have a problem, you can put it right before the FCA gets 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.

  • FCA’s Market Watch 82: Key actions for firms on remediation

    FCA’s Market Watch 82: Key actions for firms on remediation

    Following on from Market Watch 81 where the FCA assessed the root causes of transaction reporting quality issues, Market Watch 82 focuses on the process firms are expected to engage with once errors are identified.

    All reporting firms should have robust procedures in place to identify, address and disclose regulatory reporting issues. Many will be actively engaged in the process. The findings detailed within Market Watch 82 stem from the FCA’s recent observations supervising the UK MiFID transaction reporting regime and focus on observed inefficiencies within the processes firms have in place.

    The Market Watch is in two halves – the first looks at remediation processes, and the second reviews remediation notifications. 

    We’ve distilled the newsletter into key actionable items that all firms must/might/should consider now if they haven’t already. 

    Remediation process

    • Document and agree a prioritisation methodology against which all “issues” are assessed
    • Remediate accordingly to the agreed prioritisation (the FCA makes it clear that under-reporting takes priority over misreporting a field where the supervisory priority has been downgraded)
    • Remediate the root cause first, then back report
    • Accurately identify all impacted records
    • Due care and diligence ensures repetition, missed records and unnecessary deadline extension requests are avoided
    • Determine and action a remediation plan to fix all impacted records within a realistic timeline
    • Ringfence resources to remediation – remediation is never done well “off the side of the desk”. A focused effort by regulatory subject matter experts will likely get the job done more efficiently than relying on individuals with other priorities
    • Make regulatory reporting and data migration a key sign off for all change projects be it new business, infrastructure or regulatory reporting driven change
    • Regular data quality testing will confirm that issues are no longer occurring once fixed and it is equally important to make sure that new issues aren’t introduced or worse, previous ones reoccur.

    Remediation notifications

    • Clearly state whether the issue is misreporting, under-reporting, or late reporting. Make sure you describe it in plain language, avoid internal jargon and keep it to the point 
    • Align your root cause analysis with the common causes from Market Watch 81. If citing human error, you should assess whether better processes, controls, or oversight could have prevented it
    • If exact impact details aren’t available, submit the notification without delay. Make this clear and provide estimated figures if needed. Indicate when the full assessment will be completed and specify whether volumes are exact or approximate
    • Give details about the planned remediation – if this is work in progress then detail the activity required to determine back-reporting timelines rather than give no details. Even the best teachers can’t mark blanks  
    • Clearly link the issue to its specific root cause, focusing on the actual weakness in systems or controls. Avoid generic statements about overall improvements. If including a third party, assess whether better vendor controls or oversight could have prevented the problem.

    As we were all reminded during the football over the weekend, a draw after two halves leads to penalties, and the FCA reminds us that “some firms must improve their operational frameworks”. A look back to the Final Notice issued by the FCA earlier this year reminds us that the firm in question was chastised for not only for accuracy errors but also for delayed regulatory notification and weaknesses in controls. 

    Our ReportShield services are used by hundreds of firms to address the issues raised by the FCA in Market Watch 81 and 82. For help with your remediation programme, a review of your controls or a comprehensive assessment of your data quality using our market-leading tools, please get in touch. 

  • Kaizen wins Best Transaction Reporting Solution at the RegTech Insight Awards USA 2024

    Kaizen wins Best Transaction Reporting Solution at the RegTech Insight Awards USA 2024

    New York, London, 22 November 2024 – Leading regulatory technology firm, Kaizen, has won ‘Best Transaction Reporting Solution’ at the RegTech Insight Awards USA 2024 for its ReportShield™ Accuracy Testing service. This is the fourth year in a row that Kaizen has won a RegTech Insight USA award.

    Kaizen’s ReportShield™ Accuracy Testing is an automated, managed solution that tests the quality of trade and swap transaction data reported to the regulator. What makes the solution unique is the comprehensive deep testing of all records, which provides financial firms with full visibility of their reporting quality. Accuracy Testing is available via the Kaizen Hub, Kaizen’s easy to use web-based portal. It is the only assurance service that is tailored to all global reporting regimes including the CFTC and SEC swap data reporting rules as well as MAS, HKMA, ASIC, MiFIR, EMIR, and SFTR.

    Angela Wilbraham, CEO at A-Team Group and host of the 4th annual RegTech Insight Awards USA 2024, commented “Congratulations to Kaizen for winning the Best Transaction Reporting Solution award in this year’s A-Team Group RegTech Insight Awards USA 2024. These awards celebrate providers of leading RegTech solutions, services and consultancy and are uniquely designed to recognise both start-up and established providers who are creatively finding solutions to help with regulatory challenges and span a wide range of regulatory requirements. Our congratulations to Kaizen for their achievement in winning this award in a highly competitive contest.”

    Ian Rennie, Managing Director and Co-founder of Kaizen, commented: “I would like to thank everyone who selected Kaizen as the Best Transaction Reporting Solution at this year’s RegTech Insight USA Awards. As part of our recent £42 million minority investment, the US will be a key focus for us as we look to help firms with the challenges in adhering to the CTFC and SEC rules and other regulations. This year we have seen an unprecedented amount of change not only in the USA but globally and we are as committed as ever to providing the very best in solutions that help firms meet their regulatory requirements of accurate, complete and timely reporting.”

    The CFTC has been one of the most active of the global regulators over the past few years, fining six registered swap dealers US$60m in the past year, for reporting violations, making it clear that failure to comply with supplying accurate and complete data comes at a cost.

    (ends)

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

  • WATCH: Regulatory Reporting and RegTech in 2022

    WATCH: Regulatory Reporting and RegTech in 2022

    From the expectations of regulators to upcoming regime changes, Kaizen’s CEO Dario Crispini shares his views on Regulatory Reporting and RegTech in 2022 in our latest video interview.

    To discuss any of the topics raised in this inteview or for a conversation about the quality of your reporting, please contact us.

    (The videos below are individual snippets of each interview question, if you’d prefer to watch shorter clips). 

  • Recent FCA fine shows importance of MiFIR Transaction Reporting

    Recent FCA fine shows importance of MiFIR Transaction Reporting

    A recent FCA fine of a boutique UK investment bank is a good example of how the UK regulator is using transaction reporting data to detect market abuse and financial crime. 

    In the final notice released last week, the FCA referenced that their investigation was (in part) based on their analysis of transaction reporting data and material received from the firm, which was fined £178,000 for “failings which led to the risk of facilitating fraudulent trading and money laundering.”

    At Kaizen we are often asked “what does the regulator do with all of this transaction reporting data?”. It is often a criticism levelled at regulators – do they actually do anything with the data?

    The answer is – yes they do. By having an audit trail of trading activity reported under the MiFIR Transaction Reporting regime the authorities were able to piece together trading patterns that highlighted “sophisticated and organised criminal activity”.

    Being a former regulator myself, I know first-hand that regulators are looking at the data and continually assessing, monitoring and considering a long list of offences, many of them not related to market abuse.

    ESMA’s recent review in relation to MiFID transaction and reference data reporting shows that they intend to use transaction reports to monitor other parts of the rulebook, including suitability and compliance with the buy-back programme safe harbour under the Market Abuse Regulation.

    Long gone are the days when regulators monitored firms by relying on visits and the review of prudential related returns. Given the sheer scale of trading activity and the fast pace in which markets evolve, having a database of transactions showing data elements that include traders, decision makers and who is buying and selling when and where, is extremely powerful.

    What’s crucial is that the reporting regime keeps up with market developments. Although the key proposals following ESMA’s recent review look sensible, there are a number of missed opportunities with a key one being in relation to cryptocurrencies where the level 1 text needs updating.

    The final notice also highlighted the need for firms to have effective systems and controls to monitor their own trading and payment activity. Having accurate and complete transaction reporting not only allows the regulator to meet its own objectives but should allow firms to detect unscrupulous activity as a first line of defence.

    Having confidence in UK and global markets is of paramount importance and given that the competition created by MiFID has led to a fragmented marketplace and trading environment, the need for regulators to have a holistic cross-market view through accurate and complete transaction reporting has never been greater.

    • To read the final notice visit the FCA’s website.
    • For a completely independent assessment of the accuracy and completeness of your Transaction Reporting or for a conversation with Simon about your transaction reporting challenges, please contact us.
  • Do not adjust your (transaction reporting) clock

    Do not adjust your (transaction reporting) clock

    This weekend, the UK clocks spring forward to British Summer Time. While you may need to adjust the clocks and watches at home, please remember that the time fields for MiFIR trade and transaction reporting and EMIR trade reporting should be populated in Coordinated Universal Time (UTC). Firms were required to report in UK local time under MiFID I but this is no longer the case for MiFIR transaction reporting.

    The regulators are not likely to have any sympathy if you make errors following these time transitions as they have warned firms of such mistakes in Market Watch 59:

    “The time when the transaction was executed should be reported in Coordinated Universal Time (UTC). We continue to see errors in transaction reports when UK clocks transition to and from British Summer Time, as well as errors driven by inaccurate clock synchronisation. Firms should have arrangements in place to ensure consistent and accurate reporting of trading date and time.”

    How Kaizen can help

    As part of our ReportShield™ quality assurance services, we can run a number of tests to detect instances where the wrong time has been populated. Our accuracy testing service can test all fields in all reports submitted over a given period to give you confidence that your reporting is complete and accurate. For more details or a discussion with one of our regulatory experts, please contact us. 

    Pub quiz trivia

    It may appear strange that the official abbreviation for Coordinated Universal Time is ‘UTC’ rather than ‘CUT’. This abbreviation arose from a desire to use the same abbreviation in all languages. Whilst the abbreviation ‘CUT’ makes sense for English speakers, French speakers advocated ‘TUC’ for ‘temps universel coordineé’. In the end, they agreed to compromise on ‘UTC’, which doesn’t make sense in either language…

    Why not join in the conversation in our Kaizen community on LinkedIn?

  • 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: Dario Crispini’s regulatory reporting predictions for 2020

    Video: Dario Crispini’s regulatory reporting predictions for 2020

    • Will data quality continue to be the theme for regulatory reporting in 2020? 
    • What are the big regulatory reporting regimes coming up?
    • What issues should firms be looking out for?
    • Will we see penalties for MiFID or EMIR reporting?
    • What are the key challenges for the RegTech industry in 2020?
    • And what on earth is ‘BRiFID’?

    The answers to these questions and more in this and more in the above video from our CEO Dario Crispini.

    With thanks to the Wealth Mosaic for collaborating with us on this video. 

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

     

  • MiFID II 2nd anniversary – ready for the terrible twos?

    MiFID II 2nd anniversary – ready for the terrible twos?

    It’s two years since the introduction of MiFIR transaction reporting. What will regulators be expecting at this stage?

    Quite simply, complete and accurate transaction reporting. Whilst the MiFIR transaction reporting regime is very complex, I think regulators’ patience is starting to wear thin. The UK FCA has twice signalled in Market Watch that it is seeing unacceptable errors in transaction reports and firms have to heed that message. All the NCAs have a job to do – MiFIR Article 24 obliges the competent authorities to monitor the activities of investment firms and if the quality of data submitted by firms prevents them from meeting this obligation, then the authorities will take action.

    What action have we seen from the FCA so far?

    Just because we haven’t seen any formal enforcement cases for MiFIR transaction reporting does not mean that the FCA is happy with the quality of the data it has received. Far from it – judging by its remarks last year in Market Watch 59 and 62. It is entirely possible that the FCA is working on cases already – there is often quite a long lead time in such cases.

    What we have seen from the FCA is plenty of letters warning firms that they have discovered issues with their data. This demonstrates that the FCA is investigating the quality of reports and that firms will get found out if they haven’t got sufficient controls over their reporting processes. Often firms believe that because the FCA hasn’t contacted them, their reporting must be ok. This could prove to be a very risky assumption. The FCA has limited resources to monitor the 3,000-plus firms that have a transaction reporting requirement. However, the sophistication of their monitoring systems is increasing and they will be able to work their way through the number of firms that report. It is very important to note that when the FCA does find issues, it usually requires firms to back date all the impacted reports since go-live. The longer it takes issues to be discovered, the more complex and expensive this back-reporting exercise becomes.

    How can firms be sure they’re reporting accurately?

    Again, there is a very simple answer to this – they need to implement the controls detailed in Article 15 of the regulatory technical standards. In particular, they need to perform quality assurance testing of their submitted transactions and they need to do regular reconciliations from the data in their source systems to the reports received by the FCA.

    Unfortunately, I think there are many firms that are afraid of what they will find once they start implementing the correct controls. Too often, transaction reporting is filed in the ‘too difficult drawer’. Many firms fear their transaction reporting has become an Augean Stables and they don’t want to discover how difficult a task they have on their hands. If this is the situation you are in, perhaps it’s time for a new year’s resolution –  call in Kaizen to perform the quality assurance checks and reconciliations from front office systems to data reported to the FCA. We can also help design a quality assurance control framework and train your staff on reporting. So what are you waiting for? 

    Happy Anniversary MiFID II.

  • Kaizen Reporting in the news 2019

    Kaizen Reporting in the news 2019

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

  • Video series: Dario Crispini on Kaizen’s key regulatory reporting services

    Video series: Dario Crispini on Kaizen’s key regulatory reporting services

    Kaizen Reporting’s CEO Dario Crispini talks about the regtech company’s multi-award winning regulatory reporting assurance services and the unique testing methodology behind them. 

    This is a four part introduction to Kaizen Reporting video series from CEO Dario Crispini.

    Watch the first video in the series – Why was Kaizen founded?

    Watch the third video in the series – Issues and risks of poor data quality in regulatory reporting.

    If you’re concerned about the data quality of your regulatory reporting, get in touch. 

    Huge thanks to the Wealth Mosaic whom we collaborated with on this project. 

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

  • Video series: Dario Crispini on why he set up Kaizen Reporting

    Video series: Dario Crispini on why he set up Kaizen Reporting

    Kaizen Reporting’s CEO Dario Crispini talks about the factors that led him to start the company, our services, and the benefits we bring to our clients, in the first video of a series introducing who we are and what we do.

     

    This is a four part introduction to Kaizen Reporting video series from CEO Dario Crispini.

    Watch the second video in the series – Kaizen’s key regulatory reporting services.

    Watch the third video in the series – Issues and risks of poor data quality in regulatory reporting.

    If you’re concerned about the data quality of your regulatory reporting, get in touch. 

    Huge thanks to the Wealth Mosaic whom we collaborated with on this project. 

  • The scariest regulatory reporting changes facing you this Halloween

    The scariest regulatory reporting changes facing you this Halloween

    It’s Halloween! And what better time to cover off some of the scariest regulatory reporting changes that you need to keep very very close to, following the full-moon…

    Quoting Macbeth’s three witches, “By the pricking of my thumbs, something wicked this way comes”, here are three key regulations affecting everyone in the coming months:

    In Thunder comes Brexit

    31 October was always going to be a horror Halloween show but the EU have prolonged the agony for another three months to 31 January. The good news is that most firms have prepared for the October exit but do keep an eye on any unknown regulatory changes in the coming months – or read our Brexit White Paper to help with your preparations.  

    In Lightning comes SMCR

    Ghosting quietly in, don’t forget if you’re an Core or Enhanced Firm, as categorised by the FCA, your CF Approved Persons change to SMFs under the Senior Managers and Certification Regime (SMCR) on 9 December. Encouraging a culture of taking responsibility for actions and demonstrating a clear understanding of where that responsibility lies, are the key messages. You can’t use a magic wand to sign-off on the accuracy of your regulatory reporting, a key task for your SMFs.

    In Rain comes SFTR

    As we speak on the day of the devil, SFTR is only 166 days away.  This is frighteningly close.  Are you prepared and testing in UAT for this new reporting regime coming into effect on 14 April 2020? Contacting our very own SFTR expert Jonathan Lee is much less scary than a letter from the regulator.

    When the hurly-burly’s done, when the battle’s lost and won, Kaizen is here to help with the most scary of regulatory reporting challenges. Please contact us if you’re worried about any of the above and we can turn your regulatory reporting obligations from a trick to a treat!

    Author: Chris Machinbeth

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

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

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

    Register

     

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

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

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

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

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

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

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

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

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

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

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

    Read the full article. 

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

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

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

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

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

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

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

  • Ten steps to MiFIR transaction reporting nirvana

    Ten steps to MiFIR transaction reporting nirvana

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

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

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

    2. Do not under-estimate the costs of remediation

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

    3. Training.

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

    4. Valid does not necessarily mean correct

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

    5. Quality assurance checks are essential

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

    6. Firms must not mark their own homework

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

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

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

    8. Heed the words of the regulator

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

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

    9. Get market identifier codes right

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

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

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

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

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

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

  • FCA publish Market Watch 59

    FCA publish Market Watch 59

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

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

    Valid but incorrect reports

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

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

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

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

    Instrument Reference Data

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

    Errors and omissions notifications forms

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

    How Kaizen can help

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

  • Lack of training results in transaction reporting breaches

    Lack of training results in transaction reporting breaches

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

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

    Help is at hand

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

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

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


    ¹ FCA Final Notice to Goldman Sachs

  • Alpha FMC and Kaizen to provide transaction reporting compliance assurance service

    Alpha FMC and Kaizen to provide transaction reporting compliance assurance service

    Combined proposition will assess governance and control frameworks and identify any gaps in MiFID II transaction reporting obligations.

     

    FOR IMMEDIATE RELEASE

    5 February 2019, London: Alpha FMC the global leader in asset and wealth management consultancy, has teamed up with multi-award-winning Kaizen Reporting, the specialist regulatory reporting firm. The collaboration will comprise a “health check” for specialist wealth managers and smaller asset managers by providing independent transaction reporting assessments. 

    The new proposition will see Kaizen’s proprietary testing technology combine with Alpha’s wide-ranging global asset and wealth management expertise to provide independent and expert assurance to wealth and asset managers that their transaction reporting arrangements meet the standards required by MiFID II.

    The combined proposition will check the accuracy of all of an institution’s reported data, assess the effectiveness of firms’ governance and control frameworks, and identify any gaps they might have in meeting the regulator’s transaction reporting obligations.

    “The proposition is an ideal solution for asset and wealth managers with lower trading volumes who require peace of mind that they are reporting accurately and correctly.” 

    The key benefits of the proposition include:

    • Full visibility of the quality of data reported to the regulator, including accuracy testing of all instruments, scenarios and data fields
    • Review of existing transaction reporting governance and oversight framework
    • Independent assessment and recommendations for regulatory compliance
    • Fast execution and outcomes

    The proposition comprises a discovery phase, using a detailed questionnaire to cover transaction reporting compliance and the process involved. This is followed by an evaluation phase involving a thorough assessment of the regulatory reporting control and governance framework.

    Reporting quality will be checked by Kaizen’s accuracy testing service which assesses all data fields on all reported transactions to provide a complete picture of reporting integrity. Recommendations will then made on whether transaction reporting controls are robust and whether the required level of testing is in place.

    Andrew Glessing, Head of Regulation, Compliance and Risk at Alpha FMC said:

    “We are delighted to work alongside Kaizen, who are the standard-setters when it comes to reporting assurance. With MiFID II requirements now a year old, this is the perfect time for specialist wealth and asset managers to take stock of their reporting quality and processes. We think this proposition fills a gap in the market by providing firms with market leading assurance tools and expert advice on their transaction reporting arrangements.”

    Dario Crispini, CEO of Kaizen, said:

    “This is an important milestone in Kaizen’s timeline. By joining forces with Alpha, we are able to offer the wealth and asset management sector a vital snapshot of the quality of its transaction reporting through an all-important health check. I am delighted we are working together.”

    “The proposition is an ideal solution for asset and wealth managers with lower trading volumes who require peace of mind that they are reporting accurately and correctly.  We recommend health checks take place periodically for ongoing visibility of reporting quality or in some circumstances, more regular testing may be required

    (ends)

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

  • ESMA updates Q&A on MiFIR and EMIR reporting

    ESMA seemingly delivered a double whammy on 4 February with the publication of Q&As for both MiFIR and EMIR data reporting. However, there’s nothing to get too excited about, although firms do need to understand the ‘clarification’ and adjust their reporting accordingly.

    Impact on MiFIR data reporting

    Bit of a damp squib. There is only one question that relates to transaction reporting (TVTIC on complex trades); the others all relate to RTS 23/MAR reference data reporting. The clarifications can be summarised as follows (italics indicate direct quote from the Q&A):

    How should the TVTIC (field 3 of RTS 22) be populated in transaction reports of a complex trade?

    Bit of a change here. Previously, firms were required to put the same TVTIC on each leg of the reported trades (if they were traded on a trading venue). New instruction is to use the TVTIC provided by trading venue for each leg of the complex trade (where the trading venue uses multiple TVTICs)

    How should Field 15 (Maturity date) of Table 3 of the Annex to RTS 23 and related MAR RTS and ITS be populated in case of trading in bonds after their originally intended maturity date?

    “For bonds that were not paid out on the originally intended maturity date (and therefore have not expired, because, for example, they defaulted), the maturity date should be set to 9999- 12-31 …until they are finally paid out, in which case the maturity date should be updated with the actual date of redemption”.

    How should field 15 (maturity date) and field 24 (expiry date) of Table 3 of the Annex to RTS 23 and related MAR RTS and ITS be populated, if these dates are non-trading dates, e.g. a weekend or a bank holiday?

    “The maturity date/expiry date defined by the issuer or the prospectus of the financial instrument should be used. No adjustment should be made to the next or previous working day for the purpose of instrument reference data reporting.”

    When should an instrument be terminated in FIRDS?

    “When field 12 (termination date) of Table 3 of the Annex to RTS 23 and related MAR RTS and ITS is initially left empty, the reporting entity is expected to fill it in when the instrument is going to be terminated. This also includes the cases when the given instrument has matured/expired, i.e. where fields 15 (maturity date) or 24 (expiry date) are applicable to the given instrument and are populated in the report.

    The termination date should be earlier than or equal to the maturity/expiry date in the cases where the maturity/expiry date is populated.”

    (RTS 23)What action should be taken by the operator of the trading venue or the systematic internaliser in the cases where the LEI of the issuer cannot be obtained?

    Tell the issuer that they should get an LEI (!!!).


    Impact on EMIR Data Reporting

    There are only three clarifications in the EMIR data reporting Q&A – the first two are amendments to previous trade reporting questions whilst the third is a brand new question:

    Q34 – Reporting of contracts with no maturity date (e.g. CFDs);

    ESMA simply reminds firms that they can also report new trades for instruments with no maturity date with an ‘Action Type’ of ‘P’ (“position component”) if it is to be included in a position level report on the same day. This is in line with previous comments from ESMA.

    Q38 – Trades terminated before the reporting deadline

    All trades must be reported even if they are terminated before the reporting deadline and ESMA is simply clarifying that these reports could also be made with an Action Type of ‘P’ if the trade is to be included in a position level report, on the same day.

    Q50 – Reporting of Confirmation Means

    ESMA states:

    The value ‘N’ (not confirmed) should be used either when:

    • The derivative has to be confirmed by the counterparties but has not been confirmed yet;
    • The derivative does not have to be confirmed by the counterparties because it has been traded on a trading venue and once traded all the terms of the contracts are known and agreed by the parties.

     In other cases, the counterparties should report the ‘E’ or ‘Y’ value for this field depending on the confirmation means used (electronic or non-electronic).

    I think this is the one element in the new Q&As that may surprise some firms as it clearly states that trades on a trading venue should have a value of ‘N’.

    So, not a lot really going on with the new Q&As. It is tempting to think that little news is good news. Personally, I don’t subscribe to this point of view; I think there is still plenty of grey in there that would benefit from further clarification, which is natural given the fundamental changes brought in by MiFIR. I also think there are a few elements in the Guidelines that, with hindsight, could have been better – (equity swaps is my favourite bugbear today).

    If you have a burning MiFIR or EMIR reporting question keeping you awake at night, why not contact us at Kaizen.

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

  • MiFIR offering from Kaizen to include APA trade reporting

    MiFIR offering from Kaizen to include APA trade reporting

    FOR IMMEDIATE RELEASE

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

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

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

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

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

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

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

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

    (ends)

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

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

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

    Share your views 

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

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

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

     

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

    Stockholm conference: New regulatory insights on EMIR and MiFIR reporting

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

    European Commission’s Fitness Check

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

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

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

    MiFIR data quality issues in Europe

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

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

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

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

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

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

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

    Join us in Stockholm for the Trade and Transaction Reporting Conference

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

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

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

    Event details:

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

  • ESMA updates its validation rules (again)

    ESMA updates its validation rules (again)

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

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

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

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

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

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

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

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

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

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

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

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

  • MiFID II Q&A updates – an early Christmas present from ESMA

    MiFID II Q&A updates – an early Christmas present from ESMA

    ESMA has, this week, published updates to three of their Q&As on MiFID II which you need to be aware of for your MiFID II programmes as we approach go-live. 

    For transaction reporting, the latest update reiterates how you determine reportability for some specific instruments.  We believe that key amongst these is ESMA’s confirmation that units in collective undertakings and ETFs need only be assessed on the instrument itself and not on their underlying holdings. This point has been outstanding since the original data reporting consultation paper. 

    There are also other updates to Q&As including transparency topics and Market structure topics.

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

  • Listen now: Webinar – Senior Managers Regime responsibilities under MiFID II

    Listen now: Webinar – Senior Managers Regime responsibilities under MiFID II

    UPDATED Monday 18 December

    The Senior Managers Regime (SMR) requires a named person in each financial firm to demonstrate that they are complying with their regulatory obligations.  Listen here for our webinar which looked at the SMR in the context of the upcoming MiFID II reporting obligations which go live on 3 January 2018. 

    Kaizen’s Dario Crispini and Ian Rennie joined UK Finance Capital Markets Director Robert Driver to outline what firms should be doing to inform and protect senior managers to demonstrate effective controls under MiFID II.

    Key topics in the webinar included: 

    1. What are some of the key questions that could be asked of you by your senior executive who is responsible for transaction reporting under the SMR
    2. Where MiFIR fits into the regulatory landscape and what it is attempting to achieve
    3. The consequences of poor data quality and what controls you need to put in place to be compliant with Article 15 of RTS 22.
    4. Current industry reporting issues regarding MiFIR
    5. Steps you can take now to ensure compliance with MiFID II and the SMR.

    Date: Wednesday 13 December 2017
    Time: 3pm (GMT) for one hour

    Listen here

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

  • Q – Who should read the latest MiFIR Q&A?

    Q – Who should read the latest MiFIR Q&A?

    A – Those involved in: portfolio management outsourcing, IPOs, corporate actions and trading of swaps which contain an index.

    ESMA has published its latest version of its Questions and Answers on MiFIR with updates exclusively on the topic of firms’ transaction reporting obligations under MiFIR article 26 and ESMA RTS 22. There are four questions raised, each marked with the update date of 14 November 2017.  Here we briefly explore the key points of each question and answer.

    Q7: How should transactions be transaction reported where portfolio management has been outsourced? (page 33)

    ESMA provides a new detailed scenario and answer to the question in the form of diagrams, example reports and narrative explanation. In this scenario, where firm (B) is outsourcing the portfolio management to another firm (Z), who is making the investment decisions on behalf of firm (B), ESMA confirms that firm B needs to report the algo or person who is primarily responsible for the decision to delegate.

    Q8: What are the reporting obligations for a primary issuance?

    ESMA has confirmed that all members of a syndicate need to report all execution legs by the ‘coordinating bank’ (CB) and the ‘billing and delivery bank(s) (B&D).  A CB is defined as a bank that will buy from the issuer/seller and sell to another bank or banks in the syndicate. A B&D bank will then sell to the clients, noting that a CB can also act as a BD. In relation to the time that needs to be reported, this should be the date time at which the pricing and the allocations are finalised between issuer and the syndicate, normally the first listing. ESMA has provided worked out examples for other fields.

    Q9: When are corporate events reportable?

    The industry is going to have to pick through the answers to question 9. ESMA reiterates that corporate actions are reportable where the investor has an opportunity to make an investment decision. It then goes on to recognise in practice that many corporate actions are as a result of mandatory events that bring them within the exclusions under 2(5)(i) of Article 26. This still leaves an element of interpretation on behalf of firms to identify these exclusions.  There is clear guidance on corporate events resulting from a default option and where an investor has given standing instruction.  For both categories a report is required.

    ESMA also confirms that it is the transaction resulting from the event that should be reported and provides a worked example. There are other points to review but in short and at first glance, this guidance reiterates that firms will need to put in place measures to identify reportable corporate actions.

    Q10: Are both legs of a swap reportable, when one leg contains an index such as LIBOR or EURIBOR?

    I think the answer simply says ‘look at example 106 in section 5:35.7.1’ but uses many more words than that to say this!

    The main purpose of this blog was to draw your attention to the latest Q&A and to highlight some of the key points. In terms of readiness for 3 January, I think the most significant impact will be the reporting of corporate actions and firms’ ability and capacity to separate those that are reportable from those that are not.

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

  • Transparency is still an issue 10 years post financial crisis

    Transparency is still an issue 10 years post financial crisis

    “If these things were so large, how come everyone missed them?”
    The Queen – 5 November 2008

    It’s ten years this month since the financial crisis began and we’re reminded that it was Her Majesty The Queen who spoke for the nation when she asked why it had taken so many financial experts by surprise.

    Her Majesty asked the question at a visit to the London School of Economics a few months after the collapse of Lehman Brothers.  The reply?  “At every stage, someone was relying on somebody else and everyone thought they were doing the right thing.”

    Could it happen again?

    August 9 2007 is largely known for being ‘the day the world changed’ when BNP Paribas froze three of their funds, indicating they had no way of valuing the assets inside them.  The run on British bank Northern Rock began a month later.  One year later in September 2008, Lehman Brothers filed for bankruptcy, prompting worldwide panic.

    Now, ten years on, could it happen again?  Have efforts to prevent another financial crash been successful?  The Governor of the Bank of England Mark Carney thinks so.  Last month he said that the things that caused the last financial crisis had been fixed.  Carney believes that the reforms agreed by the G20 have created a safer, simpler and fairer financial system.  

    Part of this reform agenda was a substantial increase in reporting requirements which are meant to bring greater transparency and allow regulators to be able to spot the build-up of systemic risk.  But persistent data quality issues continue to thwart making good on this objective.

    Data quality is the big issue

    Why?  The regulations that have arisen out of the ashes of the financial crisis including EMIR, Dodd Frank Act and the soon to be live MiFID II are meant to put in place reporting regimes that give regulators all the information they need to identify the build-up of systemic risk and detect market abuse.  The idea being that if there is to be a next time, regulators can’t stand behind the reason that they had limited visibility.  However, the increase in breadth and depth of information required has led to a corresponding and manifest increase in complexity which has led in turn to a decrease in data quality – which, if left undetected, can have serious and dire consequences for firms and regulators alike.

    We’ve highlighted before the problems that banks are having with their regulatory reporting quality – the very reason Kaizen is kept in business!  Last year the FCA found 65,000 data quality breaches in a week when testing only four of the MiFID transaction reportable fields.  Our own analysis has found at least 65% of transactions are being reported incorrectly with firms completely unaware of the inaccuracies of their data.  And this is in a mature regime which is comparatively simple compared to MiFID II, EMIR and DFA. 

    Stuck between a rock and a hard place

    If regulators, having asked for a substantial increase in reported data, are then unable to identify the build up of systemic risk, this will ring hollow in the corridors of power of the G20 governments.  Under this pressure regulators will have increasingly low tolerance with firms who persist with reports that have significant data quality issues.  

    For the industry to be able to add ‘improved transparency’ to Carney’s list of positive changes since the financial crash, there needs to be a sustained and comprehensive improvement in the quality of the data that firms report to regulators.

    Regulators cannot afford to allow data quality issues to persist.  They will take the necessary actions and we can expect increased censure and fines to follow as required.

    What next?

    In this context and environment it is critical for firms to be able to identify and quantify data quality issues in their reporting, which is exactly what Kaizen does for our clients and how we explained what we do to the Queen in our recent conversation with her at Buckingham Palace!  

    In all seriousness, please contact us if you have concerns about the quality of your regulatory reporting or would like confirmation of its accuracy and completeness.  We are here to help. 

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

  • MiFID II: Industry pushes back on ‘no LEI: no trade, no admission’

    MiFID II: Industry pushes back on ‘no LEI: no trade, no admission’

    Kaizen’s CEO Dario Crispini and Managing Director Ian Rennie spoke with Thomson Reuters Accelus about efforts by the financial services industry to persuade ESMA to soften its approach on the use of LEIs under MiFID II. 

    Firms are disputing two issues – the ‘no LEI, no trade’ rule spelled out in RTS 22 (which mandates the use of LEIs for corporate and other counterparties) and ‘no LEI, no admission’ rule in RTS 23. Firms are looking for leeway from ESMA to allow the use of other identifiers, at least initially. 

    On the ‘no LEI, no trade’ rule, without an LEI, the transaction report will fail the validation test and be rejected by the ARM or national competent authority. 

    “The validation means that if there is a corporate entity as counterparty or a decision maker on a trade, if they don’t have a LEI, then the firm can’t report the trade. There will be circumstances where someone does a trade and then they find out they don’t have a LEI. What do they then do? It’s not possible to get the report to the regulator with the wrong identifier. It makes sense to try to move away from that strict validation. That will require quite a bit of movement from ESMA,” Dario told Regulatory Intelligence. 

    “My understanding is all firms are trying to meet the requirement and deal with the rump of their counterparties and issuers as they go live. Everyone is geared up for ‘no LEI, no trade’ but are, at the same time, explaining the potential unintended consequences to their competent authorities,” said Ian.

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

     

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

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

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

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

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

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

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

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

    Register here

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

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

  • Workshop: MiFID II Guidelines and Common Scenarios

    Workshop: MiFID II Guidelines and Common Scenarios

    FULLY BOOKED.

    We’ve joined forces with the BBA again to deliver a new training workshop, this time focused on MiFiD II training scenarios.

    This workshop will explore the challenges that the final transaction reporting guidance and its corresponding scenarios present. Building upon the learning from the Understanding your Obligations workshop, this one-day training session will delve into the detail of the reporting guidance and how this applies in various scenarios to ensure the highest level of compliance with MiFID II obligations.

    There will be an opportunity for delegates to submit their own reporting scenarios beforehand to work through on the day, as well as covering off some of the most common scenarios.

    ESMA has made it clear that it expects the quality of MiFID II/MIFIR reporting to be high from go-live in January 2018.  It is essential that investment firms understand the guidelines and factor their direction into the design, build and control of their transaction reporting solution.

    This workshop is open only to financial regulated firms.

    Date: 2nd February 2017
    Venue: London Institute of Banking & Finance, 8th Floor, Peninsular House, 36 Monument Street, London, EC3R8LI

    Book and find out more.

     

     

  • Camels are horses: the problem of identifiers under MiFID II

    Camels are horses: the problem of identifiers under MiFID II

    This article was first published by Thomson Reuters Accelus (a subscription only service) on 21 November 2016. 

    We seem to be surrounded by questions of identity these days; a problem that was recognised and typified by the story of Theseus’s ship by the early Greeks. When Theseus and his young crew returned to Athens from Crete they did so in a ship with 30 oars. The ship was preserved by the Athenians down the ages by renewing the timbers as they decayed. Is this renewed ship, where none of the original timbers actually made the journey from Crete, still Theseus’s ship or has it become something different?

    Today we face this question of identity in a slightly different form in terms of nationality. Whether we are European or British, British or Scottish, and what determines nationality in any case. The topic “Mistaken identities” is the title of this year’s Reith Lectures by Professor Kwame Anthony Appiah. In his lectures, he looks at what gives people their national identity, a question firms will be faced with when trying to categorise their clients.

    In the regulatory sphere as well, questions of identity appear in several forms.  The Know Your Client (KYC) and Politically Exposed Persons (PEP) mean firms need to know that the person they are looking to deal with is who they say they are.  In reporting, firms need to identify who we are trading with; both individuals and companies. We also have to identify the traders within the firms themselves, and we need a way to identify the products being traded.

    This piece will focus on the question of nationality and the use of identifiers for individuals and companies under MiFID II and some of the challenges that this will bring. We will deal with identifiers for instruments at another time.

    MiFID II transaction reporting requirements seek to provide regulators with greater visibility of who is trading and who is making the investment decisions. This contrasts with MiFID where financial firms can often be identified with a global identifier (BIC or FRN codes) whilst other companies, partnerships and individuals are identified at a firm level using each firm’s internal identifiers. The lack of global identifiers makes it much more difficult for regulators to see what is going on across the market.

    Identifying individuals under MiFID II

    Under MiFID II ESMA has opted to use a suite of identifiers for individuals where the identifier to be used is to be based on the individual’s nationality. To my mind, it is unfortunate that they took a fragmented approach because it introduces an additional problem of what type of identifier to use, making reporting much harder. I presume this was a 28-country committee decision. As they say, a camel is a horse designed by committee!

    The requirements for identifying individuals are specified in the Regulatory Technical Standards (RTS) 22 and a table of the required identifiers by nationality is illustrated in annex II of the RTS. The annex tells you which identifier should be used for each nationality. The table in annex II tells you what to use once you know the nationality of your client or trader.

    Six of the countries opted to use the CONCAT approach as their only identifier. Other countries have elected to use national identifiers, passport numbers or tax numbers.

    What is CONCAT?

    As the name suggests CONCAT is a method to generate an identifier for individuals based on the compression or concatenation of four data elements:

    1. Country code (2 characters: ISO 3166-1)
    2. First name (first 5 characters padded with # where required)
    3. Surname (first 5 characters padded with # where required)
    4. Date of birth (YYYY-MM-DD)

    The CONCAT is comprised of these elements in the order shown.

    There is an argument that the four elements lack an important feature of an identifier, that of uniqueness. The cost of clashes, where two individuals are allocated the same CONCAT code, will be dependent on the frequency with which clashes occur.

    The process doesn’t end there. Before creating the CONCAT, the names need to be subject to a transliteration process to convert them into a common Latin alphabet by removing punctuation marks: apostrophes, hyphens, accents, and umlauts. Titles should also be removed as well as prefixes such as “Van” or “De” or “De la”. I am sure there will be questions where individuals treat the prefixes as part of a single surname: or example, where Delarue is used by the individual rather than De La Rue.

    What is the client’s nationality?

    “Firms must ask both new and existing clients whether they have multiple nationalities and to notify their firm if they acquire or lose a nationality.”

    Returning to the philosophical and social question of identity and nationhood: what is your client’s nationality? Rather than getting everyone embroiled in conjectures, ESMA has happily provided a waterfall approach to be used where individuals have multiple nationalities:

    1. For EEA countries use the first country ISO country code when it is sorted alphabetically
    2. Where there are EEA and non-EEA countries, the EEA countries take precedence.
    3. Non-EEA countries use the first country ISO country code when it is sorted alphabetically

    That means firms must ask both new and existing clients whether they have multiple nationalities and to notify their firm if they acquire or lose a nationality.

    Even then, we need to know each client’s list of nationalities which might not be so easy to determine. In my case, which I am sure is not unusual, I was born in Guernsey but have Italian and Irish parents which may complicate things. I am living in the UK but I have never been through any citizenship process. So in all honesty, I’m not sure what my nationality is.

    If I am a UK national, I would be identified using my national insurance number according to the table in RTS 22. But is it so simple?  I think I may have been registered as an Italian citizen and allocated a codice fiscal or Italian tax code.  So perhaps I would be classified as Italian, but I also used to have an Irish passport and I now travel on a Guernsey passport. So what nationalities do I have? I  have been told that anyone who has Irish parentage is eligible for an Irish passport. The problem is I am not actually sure what nationalities I have. As a client completing a form where I am requested to state all my nationalities I would have to do a significant amount of research just to determine how to fill in the form.

    To help address this, it might be an idea to provide industry guidance for the public on how to determine your nationality. ESMA has not, however, provided any guidance regarding what constitutes nationality for transaction reporting purposes. Does citizenship, tax residence, domicile, place of birth, a passport, all qualify? We need to know the answer to be able to arrive at the appropriate identifier to put in the transaction report.

    So taking my example, and assuming I am a national of the respective countries, you would get a table along the lines of something like this:

    Nationality

    Country code (ISO 3166)

    Identifier to use per annex II RTS 22

    Priority

    Basis

    British

    GB

    National Insurance number

    1

    First EU country alphabetically based on country code

    Guernsey

    GY

    Passport

    4

    Not an EU state.  EU states take precedence.

    Irish

    IE

    CONCAT

    2

    Second EU country alphabetically based on country code

    Italian

    IT

    Codice fiscale

    3

    Third EU country alphabetically based on country code


    In a post-Brexit world, the identifier to be used would change because the UK would switch from being an EU state to a non-EU state. Whilst my nationalities haven’t changed, the status of the UK has.  Reapplying the logic to compute the appropriate identifier to use would produce the following:

    Post-Brexit implications
    If there are any EU nationalities, they take precedence over non-EU nationalities. The first EU nationality of the country code when sorted alphabetically is used in that scenario. In this case it would be GB.  Looking at the table in RTS 22 annex II then shows that the UK requires a national insurance number, as its primary identifier.

    Nationality

    Country code (ISO 3166)

    Identifier to use per annex II RTS 22

    Priority

    (post Brexit)

    Basis

    British

    GB

    National Insurance number

    3

    Not an EU state.  EU states take precedence.

    Guernsey

    GY

    Passport

    4

    Not an EU state.  EU states take precedence.

    Irish

    IE

    CONCAT

    1

    First EU country alphabetically based on country code

    Italian

    IT

    Codice fiscale

    2

    Second EU country alphabetically based on country code

     

    The table above shows that this is not going to be a simple process. It however, will go beyond just clients.

    Beyond clients

    Within the MiFID II transaction report there are a number of fields which may require an individual to be identified. Not all of these will be clients.

    Field no.

    Field name

    Type of individual

    7

    Buyer identification code

    Client

    12

    Buyer decision maker code

    Client or representative

    16

    Seller identification code

    Client

    21

    Seller decision maker code

    Client or representative

    57

    Investment decision within firm

    Trader

    59

    Execution within firm

    Trader

     

    Where there is some sort of power of representation in place, that party will also need to be allocated an identifier using the same process if they are to place trades on behalf of the account. Traders within the firm are also caught.

    Identifying businesses under MiFID II

    A much simpler identifier is in place for businesses. MiFID II requires all parties operating a business to be identified with a Legal Entity Identifier (“LEI” code). I say “operating a business” and not “companies” because any party eligible for an LEI under the LEI allocation rules must be identified with an LEI. Under these rules an individual operating a business as a sole trade or as a local is eligible for an LEI.

    “The regulations require firms to have an LEI in their possession before entering into a trade with a client or counterparty or on behalf of their client.”

    No LEI no trade

    This gives rise to the ‘no LEI, no trade’ rule. At present, the regulations require firms to have an LEI in their possession before entering into a trade with a client or counterparty or on behalf of their client. This can be extended to the decision maker fields for representatives under a mandate or power of attorney.

    A legal firm operating for an account will need to register for an LEI. Registration can be made on behalf of a third party or client where they give authority and the information needed to do so. Costs are currently around £100 per LEI and £55 for renewals – required after two years depending on the number of LEIs being registered.

    LEI status

    There are several statuses that an LEI can have. Reporting firms must use an “active” LEI in the executing entity field which are: “Issued”, “Pending transfer” or “Pending archival”. For clients and representatives, they must have registered for an LEI which can be one of the following statuses: “Issued”, “Lapsed”, “Pending transfer” or “Pending archival”.

    Branches

    Branches should be identified with the LEI of their head office, certainly until such time that the proposed branch level LEIs are issued.

    What should firms be doing now?

    Firstly, firms need to test their existing client and counterparty static data (including representatives) to check they have correctly captured LEIs that are already in issue. Then they need to conduct a reach-out exercise encouraging them to obtain an LEI. If you have a lot of clients, you may not want to shoulder the cost of registering an LEI for them. This however could be deemed to be an inducement and may be considered contrary to the inducement rules set out in MiFID II so firms should tread carefully.

    For individuals, a reach-out exercise is needed to collate nationalities and associated identifiers, then the appropriate identifier needs to be determined.

    Mapping client and counterparty accounts to the LEI dataset is a complex activity. At Kaizen, we have been working on LEIs for more than two years, developing solutions that address the challenges associated with mapping identifiers for both individuals and businesses. The LEI dataset itself is not without its problems as it uses multiple alphabets and contains duplicate records and entities with common legal names within its dataset. Building this assessment capability in-house will be an expensive and time-consuming exercise. In addition, this will need to be carried out on a recurring basis as new LEIs are being registered daily.

    As with all regulations, the philosophical and the practical collide, leaving firms with the challenge of accommodating the two.

     
  • The good, the bad and the new: Final MiFID II transaction reporting guidelines

    The good, the bad and the new: Final MiFID II transaction reporting guidelines

    It was a big day in the world of regulatory reporting on Monday (10 October) with the publication of what is expected to be the final version of ESMA Guidelines for MiFID II transaction reporting.

    These guidelines are very important because they establish an obligation on financial market participants who “shall make every effort to comply with those guidelines and recommendations.”[ref]Article 16(3)of Regulation (EU) no 1095/2010 of the European Parliament and of the Council[/ref] Failure to comply with the guidelines will be considered a breach of the transaction reporting requirements.

    The guidelines are extensive so we’ve carried out an initial review of the 280-odd pages and a quick comparison to the previous version focusing on the transaction reporting requirements.

    Our take? Well, the good news is that ESMA has answered a lot of questions. The not-so-good news is that many questions still remain unanswered.  The bad news is that the guidelines have thrown up some new questions.

    Here are our immediate observations (there will be more to come once we’ve had more time to plough through and analyse all the changes).

    Identifying natural persons

    There have been some changes to identifiers for individuals which we think will be welcomed by the industry:

    1. Person identifiers: no longer requires firms to monitor for the expiry of identification documents such as passports.
    2. Clarification of how to determine nationality of individuals with multiple non EEA nationalities is by the first country code when sorted alphabetically.
    3. Introduction of an exhaustive list of name prefixes where these are to be removed when constructing the CONCAT identifier.
    4. Name and surname fields are now to allow the original country spelling so transliteration is not required for these fields.

    Who is the decision maker?

    This is the key question that competent authorities need to answer when undertaking surveillance for market abuse. As such, this is key information in the transaction report and ESMA has provided further clarifications and examples in the scenarios for the various decision maker fields including reporting chains which will prove very useful when mapping out the reporting logic.

    Reporting trades against fund managers has been clarified

    ESMA clarifies that they are looking for the decision maker. Therefore, where there is a transaction on the instruction of the fund manager, the fund manager will be the buyer and the decision maker field is left blank as it is one and the same party.

    Where execution is determined outside of the reporting firm then the “execution within firm” field should be populated with “CLIENT”. Similarly, where executions are filled by an order management system then this should be identified with an Algo identifier.

    Venue identifier

    The original guidance and RTS 22 indicated that all trading that was not directly on venue activity would be reported as XOFF. Unfortunately, the latest guidance suggests a move back to the MiFID I approach where the venue MIC code must be used when a trade is executed under the rules of a venue.

    “The buying and selling interest of two parties is not brought together by the Trading Venue either on a discretionary or non-discretionary basis, but the transaction is nonetheless subject to the rules of that Trading Venue and is executed in compliance with those rules.”

    ESMA confusingly goes on to say,

    “Where an Investment Firm is not the direct market facing entity the Investment Firm is not regarded as executing on the Trading Venue for the purposes of transaction reporting.”

    This seems to contradict the prior statement. The examples provided, however, do make clear that where the parties to a transaction agree that it is executed under the rules of an exchange or trading venue then the venue field should be populated with the MIC code of that exchange or trading venue.

    Short-selling flag

    Only real change here is that aggregated client orders do not require a short-selling flag to be populated as it relates to multiple clients. Transaction reports that show individual client-side activity will need to be populated based on the each client’s overall position in the traded security.

    ESMA has also clarified in the examples that the short-selling flag is only required for uncovered short sales of shares and sovereign debt instruments per articles 12, 13 and 17 of the short selling regulations.

    Cancellation of transaction reports

    ESMA has clarified that only the “key” fields 1, 2, 4 and 6 are to be submitted in the cancellation report. Inclusion of additional field information will result in a rejection of the cancellation report.

    Identification of the underlying instrument

    Surprisingly, ESMA has asked that where there is a derivative on a derivative (an option on a future on an equity, for example) the direct underlying should be identified i.e. the future rather than the equity.

    This raises the question of reportability. Are they suggesting that underlying refers to only one level down and when assessing reportability, there is no longer a look through to the ultimate underlying? For example, an option on an ADR on BT shares would not be reportable because the look through only goes down one level to the ADR? While when assessing the ADR you would look through one level to find BT shares and conclude the ADR itself is reportable? In the case where the immediate underlying is a future on a third country exchange that doesn’t use ISIN to identify its products means that the underlier field cannot be populated again – does this suggest that ESMA now considers such instruments as not reportable?

    Equity swaps and instruments reported with two separate transactions reports

    There has been an amendment to the approach ESMA wants to see for instruments which have multiple legs such as equity swaps. ESMA has compressed the two legs of an equity swap into a single transaction report using + and – to flag the buyer and seller of the legs. Previously in the consultation paper ESMA expected two transaction reports which were to be linked using the complex trade ID field.

    Similarly, for equity swaps the ISIN code for each equity leg is included in underlying instrument field with a + for the buyer (receives the performance) and – for the seller (on the equity leg that where they pay the performance).

    Similarly, where a benchmark is exchanged for equity performance the benchmark is identified in the “Underlying index name” field with a + or -.

    Other things of note:

    • Transfers are further defined in the text.
    • Changes in ownership structure are reportable.
    • Units of funds are not financial instruments and therefore not reportable.
    • Transactions for the creation and redemption of funds are only excluded where they are directly with the fund administrator. This was in the prior version of the guidance but it is now much clearer.
    • Identifying buyer or seller for trusts has been amended to be consistent with the approach taken for firms.

    What’s not addressed
    Outsourcing – do you need to be an ARM?

    There is an open question being debated by lots of different interested parties. The suggestion by ESMA had been that where a firm uses a central reporting hub to generate the transaction reports for all the reporting entities in its group that firm would have to register as an Approved Reporting Mechanism or ARM. Similarly, parties that stood between the reporting firm and the ARM providing reporting services would also be required to become an ARM.

    The guidelines clarify that

    “No requirement for a receiving firm to become an ARM. There was request for confirmation that a receiving firm reporting details transmitted by a transmitting firm did not need to become an ARM. ESMA confirms that that is not an outsourcing arrangement as the receiving firm is making its own report and it is not required to become an ARM. A statement on this has been included in the relevant section of the Guidelines.”

    From this it does imply that any form of outsourcing type arrangement involving your transaction reporting activity may require the supplier of the service seeks ARM status. This is not black and white and my suspicion is that this issue is still under discussion behind the closed doors at ESMA. What they have been able to do is rule out a scenario for receiving firms in the reporting chain to be ARMs.

    My view is that extension of the ARM regime beyond entities seeking to submit transaction reports directly to a competent authority on behalf of third parties will be unworkable.

    To conclude

    The above is by no means an exhaustive list – as always, the devil will be in the detail. Firms should be looking to see if their request for additional scenarios (as requested in the consultation paper) has been appropriately addressed.

    Do share with us here at Kaizen your initial reaction to the guidelines and anything further you’ve discovered so far. As mentioned, we will post a more thorough analysis once we’ve had more time to digest.

    Happy reading!

  • 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.
  • Looking for some practical guidance on MiFID II reporting?

    Looking for some practical guidance on MiFID II reporting?

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

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

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

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

    Where
    Clifford Chance, London

    Cost
    Delegate Fee: £395 + VAT

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

    www.cityandfinancialconferences.com/MIFIDIITTR

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

  • MiFID II delay confirmed but there’s no time to waste

    MiFID II delay confirmed but there’s no time to waste

    The European Commission has confirmed the MiFID II implementation deadline has been extended by a year to 3 January 2018.

    While this isn’t in any way surprising, the clarity is welcome news for the industry after ESMA initially proposed a delay in November. The Commission says the delay is to ‘take into account of theexceptional technical implementation challenges faced by regulators and market participants.’

    Twenty-two months is still a very short time for firms to complete all the changes required for MiFID II.  Given the significant size and scope of the new reporting requirements – affecting a much larger group of market participants – those affected should take action now if they haven’t already done so to get themselves ready. 

    A year’s delay may seem like a long time but firms should not take their foot off the pedal.  The reprieve to 2018 means it is likely that regulators will have less tolerance for those who do not meet the new reporting requirements from the get-go.  In addition, those who leave it to the last minute may find themselves with much higher implementation costs.

    We can help firms prepare for the new transaction reporting requirements required under MiFID II from getting your transaction reporting in order through to bespoke training on the new requirements.

    Contact us to find out how we can give you MiFID II peace of mind.

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

    It’s crystal ball time – regulatory reporting in 2016

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

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

    Past

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

    Present

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

    Future

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

    Common theme – increased scrutiny

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

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

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

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

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

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

    Context

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

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

    Are they useful?

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

    Regulators’ expectations

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

    Structure and content

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

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

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

    Welcome step, but…

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

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

  • Is indirect clearing any clearer?

    Is indirect clearing any clearer?

    ESMA has published its latest consultation on Indirect Clearing Arrangements under both EMIR and MIFIR. The consultation paper covers both ETD and OTC derivatives and is designed to ensure consistency between the two regimes.

    The paper looks at “longer chains” and states that:

    “The requirements applicable to a direct client would need to be extended to all the intermediaries between the clearing member and the counterparty at the end of the chain. This means in particular that the provisions related to default management apply throughout the chain, including the requirement to protect through contractual arrangements, to the extent possible, what is owed to the indirect client in relation to the indirect clearing services from the insolvency of any of the intermediary clients providing clearing services.”

    For more information please refer to the Consultation Paper.