Category: Blogs

  • ESMA Call for Evidence: Interim Report Signals Direction of Travel for Transaction Reporting Reform

    ESMA Call for Evidence: Interim Report Signals Direction of Travel for Transaction Reporting Reform

    • ESMA signals major changes ahead for EU transaction reporting rules
    • Scenario 1a is the leading near-term option for reform
    • Change will depend on EU legislative updates

    ESMA has set a course towards a more streamlined and efficient trade and transaction reporting regime across European markets with the publication today of its Interim Report on the Call for Evidence on a comprehensive approach for the simplification of financial transaction reporting.

    It has now been ten months since the Call for Evidence (CfE) was launched and five months since ESMA’s Data Day. The interim report summarises feedback from 108 written responses to the CfE, alongside separate insights gathered from 14 meetings involving 25 stakeholders.

    This is not the end of the consultation process nor even the beginning of the end. Rather, it marks the end of the beginning. There is now clear acknowledgement that the current framework is not where the industry or regulators want it to be and that significant change is inevitable. However, that change will neither be quick nor straightforward.

    Cost-benefit analysis

    Much of the report consolidates existing themes; a restatement of the current challenges, a reframing of the objectives and detailed analysis of stakeholder views on the options originally presented in June 2025.

    Given the need for a thorough cost-benefit analysis (CBA), the report does not yet contain policy recommendations. As a next step, ESMA will continue to engage with market participants, including through an open hearing on 28 May before moving towards final recommendations expected by the middle of the year.

    An independent entity is currently conducting an extensive CBA involving 30 participants across four sectors; buy-side firms, sell-side firms, market infrastructure providers and non-financial corporates. In parallel, ESMA is assessing the impact on the public sector through input from National Competent Authorities (NCAs) and other stakeholders. The results of both CBAs will feed into the Final Report, expected in July 2026.

    Key developments

    Despite its interim nature, several clear markers provide greater certainty regarding the direction of travel, if not the final destination:

    • Of the four scenarios originally presented, Scenario 1b (event-based delineation) and Scenario 2b (expanded “report once”) have been ruled out due to limited support.
    • Scenario 1a is emerging as a viable near-term option; offering limited structural change, lower implementation costs and shorter timelines. It may also serve as a phased pathway towards Scenario 2a, which is increasingly viewed as the longer-term target.

    By way of reminder:

    • Scenario 1a – delineation by instrument: separation of ETDs and OTC derivatives across EMIR and MiFIR, alongside revisions to dual-sided reporting
    • Scenario 2a – “report once”: a unified MiFIR framework incorporating EMIR and SFTR within a single reporting template.

    Stakeholders consistently emphasised the need to reduce the burden associated with dual-sided reporting under both EMIR and SFTR while preserving the principle of maintaining the full scope of information.

    Focus on Scenario 1a “sub-variants”:

    Looking ahead to the Final Report, ESMA is expected to select one of the following of Scenario 1a:

    • Option 1ai (with schema changes):
      Retains the CfE approach with targeted schema modifications to preserve supervisory capabilities (e.g. market abuse monitoring and systemic risk oversight). Includes expansion of mandatory delegated reporting and removal of reconciliation processes linked to dual-sided reporting.
    • Option 1aii (without schema changes, no delineation):
      Focuses on reducing costs associated with dual-sided reporting through expanded delegated reporting, without introducing ETD/OTC delineation.
    • Option 1aiii (without schema changes, with delineation):
      Introduces partial separation between ETDs and OTC derivatives (e.g. excluding EU ETDs from EMIR), while maintaining current MiFIR scope. Also includes expanded delegated reporting and associated reconciliation processes.

    Direction of travel

    Across all variants, there is a consistent trajectory:

    • Expansion of delegated reporting obligations
    • Removal of reconciliation requirements linked to dual-sided reporting
    • Continued emphasis on data quality through mechanisms ensuring alignment between counterparties.

    Importantly, these sub-variants are not alternatives to Scenario 2a, but potential intermediate steps designed to deliver earlier relief while preserving a path towards a more comprehensive “report once” framework.

    While the longer-term end-state of Scenario 2a remains even less precisely defined, ESMA has been clear that intermediate steps will not be reversed as the framework evolves.

    Critical dependency: Level 1 change

    A key takeaway from the report is ESMA’s explicit acknowledgement that meaningful reform will require Level 1 legislative change, “provided that the relevant changes to the Level 1 framework are made to enable ESMA to progress this simplification exercise”.

    This means that while the Final Report will set out policy recommendations, implementation will depend on action by the European Commission, Parliament, and Council. As such, timelines are for now uncertain and will be measured in years. 

    Final thoughts

    We have deliberately avoided speculation at this stage as the Final Report is on the horizon and this is when ESMA will provide more concrete proposals. We need to bear in mind that these will be policy recommendations not legal change. We are also deliberately avoiding specific analysis vis-a-vis the FCA’s agenda in the UK although it is clear that both regulatory bodies have a very similar objective in mind.

    A key difference in the EU is that political will and space in the legislative timetable is also required, whereas the FCA can, for the most part, act without recourse to Parliament.  

    Momentum is building but this will play out over years not months.

    • Read the report in full on ESMA’s website
    • For a conversation with Matthew or one of our regulatory specialists to discuss your regulatory change challenges, please get in touch.
  • EMIR Inter-TR reconciliations in the EU and UK: what firms need to know ahead of April and September deadlines

    EMIR Inter-TR reconciliations in the EU and UK: what firms need to know ahead of April and September deadlines

    Two years on from the go-live of EMIR Refit, additional Inter-TR (trade repository) reconciliation requirements are coming into force for firms operating under EU EMIR and UK EMIR. The upcoming EU deadline at the end of April is followed by the UK in September.

    EMIR Refit’s reconciliation requirements were introduced in a phased approach:

    • Phase 1 fields – went live at the start of EMIR Refit (approx. 80 fields)
    • Phase 2 fields – two years on from go-live, a further 61 fields, bringing the total number of reconcilable fields to 148.

    What are Inter-TR reconciliations?

    Inter-TR reconciliations require trade repositories to compare derivatives reports submitted across different TRs to ensure consistency between counterparties for the same trade. Where both sides of a trade are reported to different repositories, regulators expect certain data fields to match.

    Many of these additional ‘phase 2’ fields, particularly valuation and lifecycle-related data, bring stricter matching requirements, with many requiring exact alignment between counterparties.

    In practice, this means more data to get right, less tolerance for differences, and a much higher likelihood of reconciliation breaks if firms are not fully aligned.

    Why this matters now

    Regulators have been clear that data quality remains a significant issue, and that they are using EMIR data (and that of other regulatory reporting regimes) not just to detect systemic risk but for a much wider set of supervisory measures and policies. Pairing rates, field consistency, and lifecycle reporting often fall short of regulatory expectations which is consistent with the outcomes seen in our own testing of hundreds of firms’ data.

    Inter-TR reconciliation is designed to address this by:

    • Identifying mismatches between counterparties
    • Highlighting systemic data quality issues
    • Increasing transparency across the reporting ecosystem.

    For firms, this introduces a new level of visibility. Errors that may previously have gone unnoticed internally will now be surfaced externally.

    Key challenges firms will face

    • Data alignment across counterparties

    With a significantly expanded data set under EMIR Refit, aligning reporting interpretations across counterparties becomes more complex. Even small differences, such as formatting, timing, or field population, can result in reconciliation breaks.

    • Lifecycle event consistency

    Lifecycle events remain a key challenge. Amendments, compressions, and terminations must now be reported consistently across both sides of the trade and across repositories.

    As more lifecycle-related fields are brought into scope for reconciliation, firms without strong controls in this area are likely to see a growing volume of breaks.

    • UTI and pairing accuracy

    Accurate UTI generation and sharing is critical. Failures here will directly impact pairing rates, which underpin successful reconciliation. Firms should not assume that existing UTI processes will hold up under increased scrutiny.

    • Operational readiness

    Inter-TR reconciliation introduces new workflows, including exception management and remediation. With a larger volume of reconciled fields, firms should expect a corresponding increase in breaks particularly in the early stages. Clear ownership, prioritisation frameworks, and scalable processes will be essential.

    What does good look like?

    Firms that approach inter-TR reconciliation effectively will focus on three key areas:

    • Proactive testing of data to catch issues before submission
    • Counterparty engagement to align on reporting approaches
    • Structured exception management to investigate and resolve breaks efficiently.

    Final thoughts

    Inter-TR reconciliation is a clear signal that regulators are moving towards a more data-driven, holistic view of reporting compliance. For firms, the challenge is no longer just to report but to report consistently, accurately, and in alignment with counterparties. With deadlines fast approaching, now is the time to ensure that reconciliation processes are robust enough to stand up to this new level of scrutiny.

    Kaizen’s Completeness Controls provide a comprehensive, independent reconciliation from source system data to reports made to end points, covering eligibility, reportability, pairing and matching, and timeliness. Contact us for a demo of our platform or for a conversation with Tim or one of our regulatory experts.

  • CFTC Swap Data Reporting in Uncertain Times: 5 Reasons Why It Matters More

    CFTC Swap Data Reporting in Uncertain Times: 5 Reasons Why It Matters More

    Given the backdrop in Washington, clients and industry contacts are asking me if the CFTC remains as focused on reporting and whether firms could consider scaling back their efforts. I understand the logic: a shifting regulatory environment in the US, recent No-Action Reliefs on error correction and notification, and signals of a regulatory pivot towards crypto and fraud.

    Factor in an industry exhausted after years of gruelling rewrites and the case for easing off feels almost compelling. Almost.

    My answer is a categorical nope – and here’s why.

    1. Regulators increasingly use the data for far more than systemic risk monitoring

    The Dodd-Frank Act reporting framework may have originated from the 2008/9 financial crisis with systemic risk the objective, but regulators across the G20 countries are using this data for an expanding range of purposes, including:

    • Market surveillance
    • Position monitoring
    • Market abuse and insider trading detection
    • Policy calibration.

    ASIC’s recent review of the Australian CFD market is a case in point. They used the reported data for consumer protection purposes and the resulting enforcement action secured nearly A$40m in refunds to retail investors. A different use case entirely from the original mandate but made possible by the quality of the underlying data.

    And consider the Archegos collapse. The SEC took significant criticism for what it didn’t see coming. The idea that either the CFTC or SEC would voluntarily walk away from data they’ve spent years working to obtain and improve just doesn’t hold up.

    It’s also worth remembering that the original systemic risk mandate is looking as mission critical as it has been since The Big Short. If anything the environment we’re operating in has made it more relevant:

    • War in the Middle East driving oil prices sky high and damaging the global economy
    • Growing concerns about structural vulnerabilities in the private credit space
    • Questions about whether the current AI boom might be a bubble
    • Significant uncertainty about the risks, opacity and sustainability of cryptocurrency markets (and yes, the irony of arguing for data quality while regulators are being nudged to go easier on crypto is not lost on me)
    • All of the above sitting alongside risks like stretched asset valuations, elevated sovereign debt levels, and a geopolitical risk environment that feels anything but settled.

    2. No-Action Relief letters are not a free pass on data quality

    It would be easy to assume the two recent CFTC No-Action Relief letters (easing the so-called ‘Part 49’ burdens around Error Correction and Error Notification) are a signal that the commission is easing off. It’s actually the opposite.

    Let’s recap:

    • NOAR Letter 25-25 (July 2025) means firms only having to submit a ‘failure to timely correct’ notification where the issue impacts over 5% of the open trades within that asset class.
    • NOAR Letter 25-43 (December 2025) reduces the correction requirements in three main ways:
      • Reduced requirements to correct dead (matured/terminated) trades
      • Corrections focused on the most important fields (LEIs, UTIs, UPIs and Appendix A fields)
      • Only the latest version of any trade needs corrected.

    Collectively, that’s a significant reduction in administrative burden. And credit to ISDA for the advocacy that got the CFTC to this more pragmatic place.

    But the intent is telling. The Commission isn’t saying reporting quality matters less. It’s saying: we’ve cleared away the noise, so now crack on with what really matters. In other words, there are no excuses left. 

    Regardless of where the CFTC sits on enforcement priorities, NFA examinations of swap dealers continue with data accuracy and reporting controls firmly in scope. The same goes for FINRA’s examinations on the SEC side. Reporting quality is not an optional extra.

    And here’s the sting in the tail: those two No-Action Relief letters cut both ways.The NFA will likely expect firms to demonstrate exactly what they’re doing with the correction requirements that remain. Relief from the burdensome stuff is not a pass on the important stuff.

    3. Cross-jurisdiction reporting means issues don’t stay isolated to CFTC

    If your firm is big and important enough to be invited into the Swap Dealers Ballroom, there’s a strong chance you’ve qualified for other equally prestigious obligations. The Security-Based Swap Dealers convention is only two blocks down Fifth Avenue. Toronto and the glamour of the CSA Gala are just a short flight from JFK. And further afield, your international colleagues are getting dressed up for EMIR, ASIC, HKMA and more.

    Even if the CFTC were to signal a reduced focus in data quality – which it won’t – the underlying data, systems and teams that support them tend to have multi-jurisdictional duties. Let your CFTC data grow stale or polluted and there will be a knock-on effect across every other regime you report into.

    As I commented here, the CFTC and SEC recently announced a Memorandum of Understanding that has implications for swap and security-based swap data. The MOU commits the two agencies to sharing access to reported data, combining analytical and monitoring capabilities, and coordinating on examinations and enforcement.

    Given that these two agencies have historically been more territorial than collaborative, that part about sharing analytical capabilities and analysis is game-changing. Likewise, collaboration on monitoring capabilities and examinations is an interesting and sensible development. And none of it points towards a reduced emphasis on data quality, quite the opposite. Factor in the rapid pace of AI tooling and the two commissions will soon be able to pore over your swap data like never before.

    4. The current ‘quiet period’ is the best time to improve your reporting

    The last three or four years of reporting rewrites have been a major slog. Factor in the SEC’s Security-Based Swap Reporting implementation in late 2021 and early 2022, the CFTC ReWrite in 2022, Phase 2 in 2024, and Canada’s CSA Rewrite in 2025 and even firms with purely North American obligations have been living on a near-permanent regulatory deadline treadmill. And regulatory deadlines, as everyone in this industry knows, are not renowned for their flexibility.

    Whilst we wait for the next round of regulatory timelines, it’s entirely understandable to want to take a bit of a breather. But it’s also a missed opportunity.

    With the rewrites bedded in and the next major deadline not imminent, this is precisely the window to tackle the things that always get deprioritised: cleaning up source data, enhancing systems, tightening controls, and investing in the teams that run them. Firms that use this period will be in a fundamentally stronger position than those that don’t.

    Because before long, the CFTC will have fired the starting gun on the remaining phases of the rewrite, or the CSA will have announced timelines for the next iteration of their Derivatives Data Technical Manual. Or both. And we’ll all be back in deadline mode, and those “day two” initiatives will get quietly shelved again. The window is open now – it won’t stay that way.

    5. High quality data is a business asset, not a compliance tax

    Several years of regulatory stress, my once youthful team is now looking like The Battered Bastards of Baseball, and all for what? So that regulators can ensure we’re not the next Bear Stearns?

    Well, not quite. Because it’s not just the regulators who can use this data. You can too. And you should.

    The good news is that within all that regulatory effort your firm has achieved most of the following:

    • Sourced and cleaned up massive amounts of data
    • Associated LEIs to internal client and counterparty codes
    • Collated and normalised data from multiple upstream systems
    • Linked collateral data from a collateral management system with actual trade data
    • Enriched and verified financial product codes and taxonomies with UPI data
    • Implemented multiple data controls that surface anomalies and issues like never before.

    It’s not just the regulators who now have better oversight of your derivatives business. You do too. This data and the infrastructure around it, is an asset. It isn’t siloed like many trading or upstream systems. It spans your entire derivatives business, with potential value extending across risk, finance, operations, legal and commercial functions simultaneously.

    Looking at the reporting data and controls as solely a regulatory burden is not only shortsighted. It’s also a strategic error. There is value within that data if you choose to unlock it.

    So is CFTC Swap Data Reporting still worth the effort?

    The regulatory pressure hasn’t gone away – it’s evolved. The CFTC and SEC have better tools, broader mandates, and now a formal framework for sharing data and analysis with each other. Examination programmes continue. Cross-jurisdictional obligations don’t disappear because Washington feels uncertain. And the quiet period won’t last.

    But beyond the compliance case, the firms that will come out ahead aren’t just the ones that report accurately. They’re the ones that recognise what they’ve built and put it to work.

    The data is there. The infrastructure is there. The only question is whether you choose to treat it as a burden or an asset.

     

     

  • ASIC and MAS shift to data scrutiny: what it means for regulatory reporting

    ASIC and MAS shift to data scrutiny: what it means for regulatory reporting

    Through recent discussions in Sydney and Singapore and ongoing work with firms in the region, I’ve seen a clear shift in APAC regulatory reporting: from implementation to data scrutiny and supervision.

    It’s clear that attention has moved beyond how firms implemented the 2024 rewrites, and onto the quality of the data being reported. ASIC’s recent review of the contracts for difference (CFD) sector reinforces this position. 

    Where discussions previously centred on readiness and interpretation, they are now focused on identifying data issues, understanding inconsistencies, and addressing the root causes of poor data quality. 

    This follows a familiar pattern. In the UK and EU under EMIR Refit, regulators have moved from implementation to identifying outliers, challenging firms and ultimately enforcing remediation and fines. ASIC is already well into this process, with MAS moving in the same direction. 

    Gaps in data quality are increasingly visible

    As supervision increases, weaknesses in reported data are becoming more apparent. 

    UPI is emerging as a key issue. The current framework allows for inconsistencies between the UPI and other reported fields, with limited validation to catch errors. In some cases, this creates structurally correct but fundamentally inconsistent reporting (what we call the ‘valid but wrong‘ scenario), with the added risk of distorting how trades are interpreted from a risk perspective.

    At the same time, longstanding challenges remain. Collateral and valuation reporting, despite being calculated daily by firms, are still not consistently reflected in regulatory submissions. This creates a disconnect between internal systems and reported data, making it difficult for regulators to assess true exposure.

    Complexity is increasing but clarity isn’t

    Firms are navigating growing complexity across reporting regimes, but without a corresponding increase in regulatory clarity. A consistent theme from firms was the lack of detailed, scenario-based guidance. In its absence, interpretation varies and over time, those inconsistencies become the outliers regulators focus on.

    At the same time, global firms are managing ongoing regulatory change. ESMA’s simplification agenda across MiFIR, EMIR and SFTR is being closely watched, but simplification does not reduce the cost of compliance. Each change introduces implementation effort, resource constraints, and trade-offs with other priorities.

    Beyond the headline regimes, firms are also contending with requirements across KRX, JFSA, HKMA and others, all of which demand the same level of control and oversight, often with less guidance available. This is something we are seeing consistently across firms we work with in the region.

    What this means for firms

    The key question from regulators now is can your data be trusted? 

    Firms that continue to treat data quality as a technical or operational issue will struggle to keep pace with this shift. Across our work with firms in APAC, those that are ahead are treating data quality as a control framework, supported by independent testing, and clear ownership.

    As supervision increases, so does the cost of getting it wrong. As we all know, remediation programmes are expensive, time-consuming, and highly visible.

    Ensuring data quality upfront is no longer just about compliance. It’s about reducing risk, controlling costs, and maintaining confidence in reported data.

    Kaizen supports firms globally with independent regulatory reporting quality assurance, helping them identify gaps in controls, strengthen governance and evidence reporting quality before issues surface with regulators. Contact us for a conversation about how we can help you.

  • EU regulators haven’t paused on reporting quality

    EU regulators haven’t paused on reporting quality

    As we’ve been discussing for almost 12 months now, the EU regulatory reporting change agenda has, for the first time in several years, largely paused while the European Securities and Markets Authority (ESMA) considers the feedback received from its Call for Evidence (June 2025) on simplifying financial reporting. Until that process concludes, the legislative schedule for MiFID II transaction reporting and related frameworks has stalled.

    Some reporting firms may have drawn the wrong conclusion from this pause by thinking that if ESMA has slowed down, regulators across Europe might focus their attention elsewhere and ease their demands for high-quality reporting data. Recent publications from two mainland European regulators suggest otherwise.

    AMF and CSSF both signal continued focus on reporting data quality

    The Autorité des marchés financiers (AMF) in France and the Commission de Surveillance du Secteur Financier (CSSF) in Luxembourg have each released detailed papers outlining how they monitor MiFID II transaction reporting, the common reporting issues they continue to find and what they expect from supervised firms.

    The timing is notable and reinforces that national competent authorities (NCAs) are not standing down while the legislative picture clears. 

    CSSF: systematic testing and quarterly remediation feedback

    The CSSF’s January 2026 press release outlines its ongoing transaction reporting quality testing. As of 1 January 2026, 105 Luxembourg firms are in scope, submitting nearly 24 million reports in 2025. The CSSF applies standardised tests aligned with NCAs and ESMA, alongside its own quarterly analytical summaries (running since 2022), which highlight data inconsistencies firms are expected to investigate and fix.

    Key focus areas include instrument price anomalies, branch field errors affecting NCA routing, inconsistent INTC account MIC usage, cross-checks with Suspicious Transaction and Order Reports (STORs), and reconciliation with Luxembourg Stock Exchange order book data. The CSSF also emphasises that transaction data is increasingly used beyond market abuse monitoring, including for single volume cap calculations, raising the importance of accuracy across all fields.

    AMF: reporting controls named as a 2026 supervisory priority

    France’s AMF has explicitly identified data-quality frameworks and reporting controls as a 2026 supervisory priority. While regulators often highlight data quality issues, it is less common to see formal focus on the underlying processes that produce the data. This suggests that AMF scrutiny may extend beyond outputs to firms’ internal controls.

    Meanwhile some firms with dual reporting obligations in both the UK and EU may have been distracted by the reporting “revolution” (simplification rather than deregulation) currently being contemplated by the UK’s Financial Conduct Authority.

    What this means for reporting firms

    The message from continental Europe is clear: while the legislative process may be sitting in the sidings, regulators are still actively using, monitoring and challenging firms on the quality of their reported data.

    • Regulatory reporting data quality remains a supervisory priority. Regulators continue to emphasise the accuracy, completeness and reliability across MiFID II transaction reporting submissions.
    • Transaction reports are actively monitored.  Validation checks and analytical reviews are running on submitted data on a recurring basis, not just when something has gone wrong.
    • Supervisors conduct systematic data-quality testing, analysing key reporting fields such as instrument identifiers, prices, client identifiers and trading-venue information to detect anomalies.
    • Firms receive regulatory feedback on potential issues. The CSSF distributes quarterly analytical summaries highlighting potential reporting errors that firms are expected to investigate and remediate.
    • Regulators cross-check datasets. Transaction reports are compared with other supervisory data sources such as STORs and trading-venue data to identify inconsistencies.
    • Proactive remediation is expected. Firms are expected to identify and correct reporting issues themselves rather than waiting for regulators to highlight them.
    • Regulatory reporting controls are under scrutiny. The AMF has specifically identified data-quality frameworks and reporting controls as an area of supervisory focus for market intermediaries.
    • High-quality reporting underpins market supervision. Accurate data is essential for market abuse detection, trading-volume monitoring and broader market oversight.
    • The current MiFIR reporting framework remains in force. Despite reform being paused, firms must continue to comply fully with existing reporting obligations without interruption.

    The window to act

    It’s clear that even though the regulatory reform agenda has slowed temporarily, supervisory expectations around reporting quality have not.

    For firms subject to transaction reporting, the time allowed by the pause in the change agenda should be used wisely: this is a practical opportunity to ensure that assurance and controls, monitoring and remediation processes are working as intended.

    The rules, they are going to be “a-changin”, and it’s always easier to navigate change from solid ground than from shifting sand. 

    For a conversation about your transaction reporting data quality or a demo of our assurance platform, please get in touch.

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

  • ASIC’s CFD review sends a clear warning on regulatory reporting quality

    ASIC’s CFD review sends a clear warning on regulatory reporting quality

    Regulatory reporting lessons from ASIC’s CFD report

    ASIC’s review of the contracts for difference (CFD) sector makes one thing very clear: transaction reporting data is now a frontline supervisory and enforcement tool.

    Risky business: Driving change in CFD issuers’ distribution practices (Report 828) focuses on CFDs in Australia but it contains crucial insights for the global derivatives market: regulators are reviewing reported data to assess conduct, governance and control frameworks, not just compliance with the reporting rules.

    70 million errors: what ASIC’s findings tell us

    The report details ASIC’s findings of a sector-wide review of CFD issuers’ distribution practices and compliance measures conducted between October 2024 and December 2025. Among the compliance issues identified, substandard OTC derivatives transaction reporting stood out, with over 70 million erroneous reports. While the review focused on CFDs, the reporting deficiencies identified can affect all derivative products.

    ASIC categorised the failures into two categories:

    1. Poor data quality and missing reportable information
    • Missing Data: Unwind payments, under-reported derivatives and collateral info
    • Inaccurate data: Incorrect Action and Event type combinations, erroneous timestamps, prices, valuations and collateral
    • Abnormal values: Notional amounts exceeding hundreds of millions of dollars

    These are all errors that we here at Kaizen find in our quality assurance testing.  At scale they undermine the regulators’ ability to understanding market activity and identify emerging risks within the market.

    1. Inadequate oversight and governance
    • Minimal or no oversight of delegated reporting arrangements: No systematic way of knowing when third parties faced system issues or anomalies that may cause misreporting
    • Data scrutiny: No processes in place to review data quality before and after submission to trade repository

    The positive outlier

    Amid the widespread failures, one reporting entity stood out by consistently reporting high-quality data with no identifiable errors. This was achieved through regular collaboration with peers, close adherence to oversight guidance for delegated reporting arrangements, and systematic reconciliations between trade repository and source systems.

    ASIC’s spotlight on these practices signals that reporting entities can achieve exemplary reporting quality by implementing effective controls and governance for both in-house and delegated reporting arrangements, including:

    • Data quality checks: Detect abnormalities such as unusually large notionals, valuations, and inaccurate or missing collateral data
    • Trade and position reconciliations: Identify discrepancies between source systems and trade repository records, including over or under-reporting
    • Exceptions monitoring and resolution: Tracking, prioritising and resolving issues identified through data quality checks and reconciliations

    These practices reflect an organisational culture where data quality is prioritised, controls are embedded, and issues are identified and resolved proactively, pointing to a mature governance framework.

    The wider implications

    The October 2024 ASIC rules rewrite represented a fundamental change in how transaction data supports regulatory oversight. Control over data quality and reconciliations aren’t extraordinary measures; they’re baseline practices for entities that take reporting seriously.

    The message from ASIC’s report extends far beyond CFDs and Australian markets. As regulators globally gain experience with years of accumulated reporting data, they will be using that data for conduct reviews, enforcement actions, and assessments of firms’ control environments. The report’s title says it all: treating reporting quality as an afterthought is risky business. The question isn’t whether your regulator will scrutinise your reported data – it’s when.

    How Kaizen can help

    ASIC’s findings highlight a clear expectation that firms must be able to demonstrate effective assurance, controls and oversight over their regulatory reporting, including delegated arrangements.

    Kaizen supports firms globally with independent regulatory reporting quality assurance, helping them identify gaps in controls, strengthen governance and evidence reporting quality before issues surface with regulators. Contact us for a conversation about how we can help you.

  • FCA Transaction Reporting Update: Proposed Key Changes in CP25/32

    FCA Transaction Reporting Update: Proposed Key Changes in CP25/32

    The Financial Conduct Authority’s (FCA’s) Discussion Paper and more recent Consultation Paper on Improving the UK Transaction Reporting Regime signal more than a revision of the reporting rules. They point to a much broader shift in the FCA’s view of data: both what it collects and how it uses it.

    As the FCA consults on its proposals to reduce cost and complexity, it is clear about its objectives:

    “We want to clarify and streamline transaction reporting requirements so firms can improve the quality of data they submit. We expect the proportion of complete, accurate and timely transaction reports to increase as a result.”

    This statement reflects the core message emerging from both DP24/2 and CP25/32. On one level, the reforms aim to modernise the UK transaction reporting regime, remove redundant requirements and align it more closely with the FCA’s statutory objectives. But beneath this sits a second theme: regulators are increasingly relying on regulatory data for surveillance, risk assessment and policy decisions, and that increasing reliance inevitably brings greater scrutiny.

    From supporting a statutory objective to a strategic data asset

    A decade ago, transaction reporting was seen as helping the FCA identify potential instances of market abuse and to combat financial crime. Today, the FCA describes a much broader remit. Transaction reports have evolved into a strategic regulatory data asset which underpins multiple functions – supervision, enforcement, market monitoring and policy design.

    Across the two papers, the FCA sets out an expanding set of uses:

    1. Market abuse – firstly, detecting, investigating and preventing market abuse remains the regulatory reporting’s central purpose, and the FCA is clear that incomplete or inconsistent data undermines its ability to act quickly and confidently.
    2. Financial crime –  the FCA also links transaction reporting to preventing and disrupting financial crime, reflecting the growing convergence between market oversight, conduct supervision and financial crime monitoring – where transaction-level reporting provides traceability and evidence.
    3. Functioning of markets – beyond misconduct, reporting data also supports the FCA’s understanding of how markets function in practice: assessing liquidity, tracking trading behaviour, identifying disruptions and monitoring resilience.
    4. Direct supervision – increasingly, it is also used to supervise firms more directly. For example identifying risk signals, weaknesses in controls and compliance issues. Reporting quality is no longer an operational footnote; it influences supervisory priorities and drives engagement.
    5. Evaluation of rules – the FCA emphasises that its decisions must be grounded in data and an evidence-based understanding of markets. Transaction reports help all regulators, including the Bank of England and Prudential Regulation Authority, assess how rules influence behaviour and where emerging risks are building. The data is used not only to implement policy, but also to evaluate whether rules are working as intended, and whether reforms are needed.
    6. Measuring market stress – the FCA also explicitly references the use of transaction reporting during periods of stress, where timeliness and completeness become critical in assessing liquidity and volatility pressures, concentration risks and disorderly market conditions.
    7. Data sharing – reporting is increasingly part of cross-authority coordination. Transaction data is shared with other bodies, such as the Bank of England, to support risk monitoring in sovereign debt and bond markets.  This underlines that reporting quality is not simply an FCA issue, but also feeds into wider financial stability intelligence.

    CP25/32: a material reduction in what firms must report

    Against this backdrop of a growing reliance on data, the consultation paper proposes a reduction in requirements. The headline changes include:

    • reducing the number of transaction reporting fields from 65 to 52, removing 13 fields from the current dataset; albeit with five fields that are effectively already removed using a reduction in their supervisory priority
    • removing the reporting obligation for around six million EU-only instruments, i.e. instruments only traded on EU venues
    • removing FX derivatives from scope
    • shortening the default back-reporting period from five years to three; and
    • providing clearer guidance on complex areas such as swaps to improve reporting consistency between firms
    • removing the obligation to report a limited set of corporate actions. 

    Taken together, these proposed changes represent a move toward a more targeted and proportionate dataset aligned with what the FCA genuinely needs, and specifically designed to reduce unnecessary complexity.

    Reduced burden should increase data quality

    A theme running through CP25/32 is that simpler reporting should enable better reporting. The FCA’s logic is straightforward: if requirements are clearer and more proportionate, firms will spend less time wrestling with complexity and remediation and more time ensuring that the remaining fields are complete, accurate and timely.

    The FCA is explicit that it expects quality improvements, and it reinforces that expectation in several ways:

    1. Streamlining and clarity should reduce misinterpretation and inconsistency, lowering the rate of rejected or inaccurate reports.
    2. Removing low-value fields and obligations refocuses resources on the data the FCA actually relies on.
    3. Reduced scope lowers operational complexity, removing failure points in mapping, controls and remediation.
    4. Stronger baseline reporting should reduce the frequency of ad hoc follow-up data requests, improving efficiency for both firms and the regulator.
    5. Finally, the FCA makes clear it will measure improvement through observable indicators such as acceptance rates, error alert ratios and corrective reporting ratios, alongside supervisory trends. This is a clear signal that quality will be monitored and improvement expected. 

    Improving competitiveness is not deregulation

    These reforms will likely require implementation by early 2028 and may not be the “white heat” of technological change UK Prime Minister Harold Wilson envisaged in the 1960s.  But they do reflect the same modernisation theme: regulation must adapt, be simpler and be more proportionate to today’s environment.

    This is where the FCA’s international competitiveness and growth objective matters. Not as a licence to weaken standards, but as a mandate to make regulation more effective and less burdensome while remaining anchored in allowing the regulator to achieve its consumer protection and market integrity objectives.  Done well, reform becomes a strategy: simpler rules, better supervision, less friction and a regulatory regime that protects trust in UK markets while promoting investment and innovation. 

    What happens next?

    The consultation closes on 20 February and impacted firms should respond either individually or collectively via a trade association. Kaizen is working with several trade associations to support their members in understanding the proposed changes and their impact. A policy statement will follow from the FCA with the expected changes, work will commence on revised reporting guidelines, and firms will have until early 2028 to implement the required changes.    

    The direction of travel is clear. The FCA is moving towards a streamlined reporting framework designed to support an expanding set of uses. But firms must be aware that with increased reliance on data comes increased scrutiny. Firms should read CP25/32 as simplification, not deregulation. It is a proposed reduction in burden coupled with a sharper focus on quality. With this comes a stronger expectation that firms deliver data that regulators and other agencies can rely on.

    There are undoubtedly benefits for industry. But the regulator’s new agenda includes strong data quality expectations – and firms should not lose sight of them.

    For a conversation with Matthew or one of our regulatory experts about the FCA’s proposals or for a free health check of your MiFIR transaction reporting data quality, please get in touch. 

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

  • Three long years of G20 regulatory rewrite pain – and what comes next

    Three long years of G20 regulatory rewrite pain – and what comes next

    September’s Hong Kong Monetary Authority (HKMA) Rewrite go-live felt like the final milestone in three or four years of regulatory reporting rewrites pain. HKMA’s changes were the last big jigsaw piece in a series of G20 rule revisions that started with the CFTC Rewrite way back in December 2022.

    For firms active across multiple jurisdictions, this hasn’t been “a bit of change”- it’s been a rolling transformation of how OTC derivatives are reported, validated, reconciled and governed.

    In many ways, the last four years of change have mirrored my own journey here at Kaizen. Joining in June 2021 with a remit to lead and expand Kaizen’s North American services we began with the SEC’s Security-Based Swap Reporting (SBSR) implementation. We then pivoted to the first phase of the CFTC’s Rewrite and the changes have been coming thick and fast since then.

    The rewrites in fast forward

    After years of relative stability, the pace since late 2022 has been relentless and has included:

    • December 2022 – CFTC Rewrite
      A complete overhaul of the US derivatives regime: new data standards, more fields, tougher validations and a much sharper view of what “good” reporting looks like.
    • December 2022 – SEC SBSR and Canadian CSA alignment 
      SEC Security-Based Swap Reporting went live in two stages, then was reshaped when the CFTC Rewrite arrived. DTCC was allowed to apply much of the CFTC Rewrite model to Canadian CSA reporting, pulling Canada into roughly the same orbit.
    • January 2024 – CFTC Phase 2
      UPI adoption for everything except commodities, driving more standardisation but more complexity for front-to-back systems and controls.
    • April 2024 – JFSA Rewrite and EU EMIR Refit 
      Japan joined the party with its own rewrite, while the EU’s EMIR REFIT changed fields, formats and lifecycle reporting fundamentally.
    • September 2024- UK EMIR Refit
      A separate but related regime for the UK post-Brexit, with its own implementation and quirks.
    • October 2024 – ASIC and MAS Rewrites
      Australia and Singapore implemented their G20-aligned rewrites, each with local flavour.
    • July 2025 – CSA Rewrite (Round Two) 
      Canada’s second swing, absorbing lessons from earlier reforms and the CFTC-style approach.
    • September 2025 – HKMA Rewrite
      The “grand finale” of this wave, as Hong Kong landed its own version of the global agenda.

    Battered, bruised…and still standing

    Most banks and reporting firms are emerging from this period a bit battered, but undeniably wiser.

    From Kaizen’s vantage point, we’ve seen clients:

    • Rebuild reporting architectures to support ISO standards, UPIs and new lifecycle models
    • Re-map hundreds of fields across multiple regimes under intense time pressure
    • Strengthen control frameworks – especially reconciliations and completeness/accuracy checks – to cope with far more granular data

    It hasn’t always been elegant, but the resilience, dedication and problem-solving across the market has been impressive. If I may be so bold, the industry as a whole should take a moment to give themselves a pat on the shoulder for what has been collectively tackled and accomplished.

    The regulatory change calendar over the last few years was nothing short of ridiculous, but we didn’t flinch, and here we are emerging on the other side.

    Spoiler alert…this isn’t the end

    Tempting as it is to declare victory, the regulatory carousel never really stops. On the G20 reporting side alone, the next wave already includes:

    • January 2026 – UK EMIR validations
      Revised validation rules will tighten expectations on data quality and consistency.
    • April and September 2026 – EMIR Inter-TR Reconciliation uplift 
      The Inter-TR Reconciliation scope is due to increase to around 150 fields in April 2026 for the EU and September 2026 for the UK – a significant jump in matching expectations and breaks management.
    • CFTC: Phase 3 (and maybe 4)
      The CFTC still has UPI adoption for Commodities, 49 proposed fields and a delayed move to ISO 20022 XML waiting in the wings. Whether it lands as one or two further phases, we’re not done.
    • CSA: Derivatives Data Technical Manual v2.0
      Somewhat hilariously, Canada managed to issue a 2.0 version of its Derivatives Data Technical Manual two weeks before the 1.0 version went live on 25 July. Most changes are minor, but it points toward another implementation date once consultation feedback is digested.

    So no, this is not “the end”. It’s more like the end of one particularly brutal season, with the next one already in rehearsal.

    ESMA’s Call for Evidence: Slow and Dangerous

    Alongside all of this, ESMA has launched a Call For Evidence (CFE) on reducing reporting burdens across EMIR, MiFIR and SFTR. The goal is to cut duplication and conflicting standards, something most firms would happily see.

    Trade associations such as ISDA and ICMA have suggested, among other things:

    • Limiting ETDs to MiFIR and OTCs to EMIR
      ETDs would align with market abuse detection under MiFIR, while OTCs sit with systemic risk monitoring under EMIR – which is where they arguably always belonged.

    • Single-sided reporting with a clear hierarchy
      EMIR is still an outlier with dual-sided reporting and mandatory reconciliation of both sides. A move to single-sided reporting and a clear responsibility hierarchy would remove a lot of operational friction.

    Ordinarily, you’d expect ESMA’s CFE to take years to turn into anything concrete. But with US priorities and timelines uncertain – including when the CFTC will tackle its remaining Rewrite elements – ESMA’s slow-and-steady approach may yet deliver the next major structural shift in G20 reporting.

    So where are we now?

    • The first wave of rewrites – CFTC, EMIR, JFSA, ASIC, MAS, CSA, HKMA – is largely through initial implementation
    • A second wave is forming around enhanced validations, expanded reconciliations and “day 2” fixes
    • And in the background, structural debates – like ESMA’s CFE – could reshape the landscape again, hopefully with simplification in mind.

    The bulk of the reporting rewrites have been delivered. But the regulators will continue to assess the data they are receiving and look at what their counterparts have done. Along with the future changes we currently know about, it’s a safe bet that we can expect some more changes to be announced going forward. The carousel continues to spin.

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

    The important points for firms to note are:

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

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

    4. Change management remains a weak spot across the industry

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

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

    Firms should now consider the following:

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

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

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

    Technical ISINs

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

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

    FX Swaps Clarification

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

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

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

    5. Pairing and matching are now in the spotlight

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

    Key points:

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

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

    6. Looking ahead: expect more collaboration, not less

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

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

    Conclusion

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

    For firms, this means:

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

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

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

  • Key changes proposed by FCA on MiFIR Transaction Reporting

    Key changes proposed by FCA on MiFIR Transaction Reporting

    The FCA’s CP 25/32 has landed and at nearly 200 pages, its full impact will take some time to digest. We were all expecting proposals to tune the obligation to suit the UK market, as well as steps to improve data quality and a reduction in the reporting burden on firms. And that is what it has delivered.

    But I think it is fair to say that the consultation proposes a more sweeping modernisation of the UK’s transaction reporting framework than was expected. A full read confirms that the proposed reform marks the most significant overhaul since transaction reporting was introduced.

    Here is a short summary and we’ll be taking a deeper dive over the coming weeks to fully grasp the finer details:

    1. Fewer reporting fields, leaner data requirements

    One of the headline changes is the reduction of transaction reporting data fields from 65 down to 52. This streamlining is designed to remove low-value data while maintaining the information needed to detect market abuse. The FCA is also proposing a reduction of instrument reference data fields from 48 to 37, alongside the removal of the obligation for systematic internalisers (SIs) to submit instrument reference data.

    2. Smaller instrument universe

    Another major shift is the removal of circa six million financial instruments – those only tradeable on EU venues – from the UK’s reporting scope. This re-scoping is expected to significantly shrink the volume of daily reports while aligning the UK regime more closely with the structure of domestic markets.

    3. FX derivatives out, shorter back-reporting period

    The consultation also proposes to eliminate FX derivatives from transaction reporting entirely, removing a category that currently generates high reporting volumes but low regulatory value. In addition, the FCA plans to shorten the back-reporting window from five years to three years, reducing the long-tail workload of historical corrections.

    4. Smarter reporting through conditional single-sided logic

    The true impact of the above proposal is unclear at this stage but the expansion of conditional single-sided reporting will be welcomed by some. It is not as extensive as the much loved portfolio manager’s exemption but it should have a beneficial impact on some firms.

    We are looking forward to participating in the debate with our clients and trade associations over the coming months. Please look out for a more detailed summary shortly!  

    For a conversation with Matthew or one of our regulatory experts about the FCA’s proposals, please get in touch.

  • When the clocks go back – don’t (or maybe do) let your timestamps fall behind!

    When the clocks go back – don’t (or maybe do) let your timestamps fall behind!

    In the early hours of Sunday 26 October, clocks across the UK and much of mainland Europe will go back one hour. For most of us, that means an extra hour in bed. For those working in trade and transaction reporting, it can also mean an extra opportunity for time-related errors to impact reported data accuracy.

    Under UK and EU MiFIR and EMIR, all reportable time fields must be expressed in Coordinated Universal Time (UTC). This consistency makes it easier for regulators to monitor trading activity across jurisdictions and identify potential instances of market abuse. As we have noted before, the FCA clearly used the transaction data to analyse two successful market abuse cases this year. 

    With the clock change approaching, now is a good time to double-check your reporting systems, times received on execution messages and the many hidden locations where +/- offsets may still be applied.

    Despite how long this requirement has been in place, we continue to see firms struggle with daylight saving. We have onboarded several clients this year, who – after receiving regulatory inquiries about incorrect trade times – have commissioned us to review their wider reporting accuracy. 

    At Kaizen, our ReportShield quality assurance helps firms detect and correct time-based inconsistencies. Because whether you spring forward or fall back, as well all know accurate timing is essential to accurate reporting. 

    Get in touch for a demo or a conversation on how we can get your reporting into better shape.

  • HKMA Rewrite: A Major Transformation Complete

    HKMA Rewrite: A Major Transformation Complete

    This week marks the completion of nearly three years of G20 regulatory reporting updates, starting with the CFTC Rewrite, followed by the EMIR Refit (EU and UK), JFSA, ASIC and MAS Rewrites, culminating in the most significant change yet: the HKMA Rewrite.

    Why is it the most significant? Despite it having a fairly low profile compared to the other updates, the HKMA Rewrite goes well beyond the incremental changes we’ve seen with previous G20 refits/rewrites. The Hong Kong regulator has undertaken a comprehensive restructuring of its derivatives reporting framework, bringing it into line with other G20 jurisdictions.

    What’s changed?

    The rewrite delivers some genuinely welcome improvements.  

    • Fewer reportable fields. HKMA has streamlined the reporting burden significantly, reducing reportable fields from more than 300 down to 183 for trade reporting and just 34 for margin and collateral. This should make life considerably easier for operations teams managing daily submissions.
    • Technical alignment. HKMA has moved from one of the most challenging message specifications to ISO20022 XML format. Firms that have already invested in this infrastructure for other G20 jurisdictions can leverage their existing systems rather than building from scratch. This alignment should help reduce both implementation costs and ongoing operational complexity.
    • Requirements: New margin and collateral reporting requirements provide regulators with better visibility into the collateralisation aspects of systemic risk, while the adoption of Unique Product Identifiers (UPI) and making the Unique Transaction Identifiers (UTI) the primary trade ID, improves pairing and matching processes across the different G20 regimes.

    What makes it different?

    HKMA has retained some jurisdiction-specific requirements that set it apart. Unlike EMIR, they still require both legs of FX swaps to be reported (linked via ‘Swap Link ID’), and they’ve maintained broader CDS field requirements compared to JFSA and MAS.

    On the positive side, there’s no need to navigate the clearing obligation and threshold determinations that were introduced in the EMIR Refit.

    Worth the effort 

    While any major regulatory overhaul brings implementation challenges, this transformation represents a strategic win for the industry. The alignment with global standards means firms can build on existing regulatory reporting infrastructure rather than starting from scratch. The streamlined field requirements should reduce ongoing errors and operational friction, while positioning Hong Kong’s derivatives market infrastructure for continued growth.

    For firms already reporting across multiple G20 jurisdictions, this harmonisation effort should ultimately simplify rather than complicate things, making the huge implementation effort worthwhile.

    For a conversation with one of our subject matter experts of a free health check of your HKMA reporting please get in touch. 

  • One Year to Go! US Securities Lending SLATE Reporting 2026

    One Year to Go! US Securities Lending SLATE Reporting 2026

    One year from now, on 28 September 2026, the US securities lending market faces its biggest shake-up in history. After years of largely paying lip service to the 2015 Financial Stability Board mandate for global regulatory authorities to collect and aggregate data on securities financing markets, the US securities lending market is taking action.

    What is SLATE Reporting? 

    SLATE introduces a single-sided reporting requirement for lenders of US securities eligible under CAT, TRACE or MSRB rules. Where the loan is effected, accepted or facilitated  – in whole or in part – in the USA, lenders must report details of those loans to FINRA’s Securities Lending and Transparency Engine (SLATE). This implies significant extraterritoriality where at least one party to the loan is in the USA, especially where the borrower is based in the USA but the lender is in a third country.

    It is the “covered” person’s responsibility to determine whether a securities loan is reportable, based on CAT NMS, TRACE and/or MSRB listing of the underlying security. If the security has not yet been loaded into SLATE, then the covered person will be responsible for providing FINRA with necessary information in order to have it added.

    (The covered person is a FINRA member direct security lender, a securities loan executing agent or the entity with the direct contractual relationship in the lending agreement.)

    Delays

    Earlier this year, following a request from FINRA, the Securities Exchange Commission (SEC) granted a delay, which pushed back the reporting launch date from 2 January 2026 to 28 September 2026. However, attempts to kybosh the regulation as a whole have been thwarted. The SEC accepted FINRA’s request to allow more time to build and test SLATE infrastructure and to ensure high quality, accurate and consistent reporting.

    Recent revisions

    The participant specification also changed significantly on 26 June 2025, with extensive revisions and the removal of certain fields. Reporting is required not only for new loans but also for a complex array of lifecycle events. The removal of the settlement date field and modification effective date fields may make reporting of these events more challenging and potentially introduces confusion about contractual vs. actual/effective reporting.  

    Initial covered loan reports not previously reported to SLATE will be required to be reported same-day by 23:59:59 Eastern Time (ET) to the FINRA SLATE platform. This applies to loans effected on a business day between 0:00:00 and 19:00:00 ET. The same requirement covers loan allocations, modifications, full and partial terminations, corrections and cancellations.

    This same day reporting from the point at which the loan is first contractually agreed and binding, not when it has settled, is likely to prove extremely challenging. Care will also be necessary to ensure that block loan trades are terminated when allocations are reported and that the value of the new allocation trades equals that of the original block.

    Delegated reporting?

    Firms may intend to delegate SLATE reporting in full. However under many trading scenarios they may find themselves unable to pass on the title of “covered person” – and therefore can only delegate the physical act of reporting, not the legal obligation to ensure that reporting is complete, accurate and timely.

    Firms engaged in the US securities lending and borrowing markets globally should independently assess their scope or potential scope. Once scope is established, firms need to decide on their approach.  Options include:

    1. Reporting directly as covered person
    2. Using a reporting agent (such as an agent lender, likely to take legal responsibility as a covered person), or
    3. Utilising a service bureau (third party vendor) but still remaining covered person

    Firms could also use a combination of these approaches.

    Cost implications

    Each of these options will come with different cost implications. Once captured by the regulation, whichever route you choose the cost of doing business is likely to incorporate FINRA platform costs, reporting fees and charges where late reporting occurs. Indeed, late reports will each incur a penalty charge on the same day.  Additional costs will relate to operational overheads including appropriate control frameworks to ensure compliance and data retention requirements.    

    There is also potential to be captured by system generated and intra-day securities loans such as those executed on a firm’s behalf but ICSDs, such as auto-borrowing, fails curing and auto-collateralisation trades that are not expressly excluded from the SLATE obligation. These may pose issues to report just as they do under SFTR.

    What should firms do to prepare? 

    In readiness, securities lenders should be asking themselves:

    • Are there trading scenarios in which the firm comes into scope for a FINRA SLATE reporting obligation?
    • What approach/s does the firm intend to take in order to be compliant? (Build/Buy or Hybrid)
    • Has this business and its securities loan lifecycle events been mapped out?
    • Has a data discovery exercise been performed to identify sources of all of the data elements necessary?
    • How will self-reporting or use of a service bureau be monitored and controlled?

    For a conversation with Jonathan about preparing for US SLATE Reporting, please get in touch.

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

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

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

    Market Watch 81: Transaction Reporting Vulnerabilities

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

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

    Market Watch 82: Elevated Expectations on Remediation

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

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

    Recent enforcement actions

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

    Key take aways for firms resulting from the final notices

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

    Conclusion

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

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

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

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

  • Delegated Reporting: The Danger of ‘Out Of Sight, Out of Mind’ reporting

    Delegated Reporting: The Danger of ‘Out Of Sight, Out of Mind’ reporting

    At Kaizen, we see firsthand how widespread delegated reporting has become across the UK and EU financial services industry. It was one of the main panel topics at our recent Kaizen RegTalk conference where I was joined by Alpha FMC’s Bernardo Castel-Branco, Regis TR’s Nick Bruce and Fredrik Karlsson from SEB. The conversation was facilitated by ISDA’s Andrew Bayley.

    Delegated reporting is effective in enabling firms, especially the buy-side, to simplify their reporting operations. However while you can delegate the physical act of reporting, you cannot delegate the legal liability. As we frequently discuss with our clients and at the events we hold, the belief that ‘out of sight is out of mind’ is a dangerous misconception.

    The central challenge: oversight without duplication

    Under EMIR and SFTR, there are specific scenarios where delegated reporting is mandatory. But voluntary delegated reporting is also common in whole or in part for certain market segments. During the panel, we shared an example from agency securities lending, where asset management firms often completely outsource security settlement, custody, collateral management, lending, and reporting. In some cases, their first awareness of any reporting issue comes from a regulator inquiry, not their own internal checks.

    This is the key problem with delegated reporting: it can reduce operational burden, but it doesn’t reduce liability. The challenge is to ensure you have oversight and the right controls in place without rebuilding the whole reporting function that you were trying to outsource in the first place. 

    Common mistakes we see in delegated reporting

    Our panel shared four mistakes that they see frequently across the industry:

    • Treating it as free: The “zero cost add-on” model – where reporting is offered free alongside other services like custody is common but often causes problems. Limited resources go to delegated reporting because it is viewed as non-commercial, so service quality suffers and controls can be found lacking.
    • Managing issues at the wrong level: Errors and omissions are often managed at the omnibus account level across all clients rather than tackled on a firm-by-firm basis. This prevents firms receiving firm-level regulatory oversight from the delegated reporter and being able to communicate issues and remediation plans with the regulator. When problems arise, firms often can’t establish the materiality or set realistic timelines for resolution.
    • Weak agreements: Standard agreements are typically written to limit delegate liability rather than ensure service quality, which doesn’t help the delegating firm to enforce standards with the delegate or meet their regulatory obligations.
    • Missing the required data: Firms often lack access to underlying data from books and records, trade repositories and approved reporting mechanisms (ARMs) needed for proper oversight. If you can’t independently verify what’s being reported on your behalf, you’re taking an unnecessary risk.

    Best practices for effective oversight

    At Kaizen RegTalk we asked our audience of more than 200 clients what was the most important aspect of successful delegated reporting. 

    1. Shared understanding (38% of poll respondents said this was crucial): This requires ongoing dialogue between delegating firm and delegate. You can’t assume your delegate understands your business requirements, you need to actively manage this relationship. In practice, this means building your control framework with systems that let you monitor delegate performance without recreating the entire reporting function.
    2. Strong, independent controls (36%): The delegating firm must maintain the ability to independently verify the quality of their reporting. This includes reconciliation and access to trade repository data for basic checks. You also need ways to assess what’s important, and documentation showing queries raised and responses received.
    3. Clear communication (17%): Regular updates and processes to resolve disputes are critical. When issues arise, you need defined escalation paths and service level agreements for resolution. The panel emphasised keeping delegated reporters “under pressure” through regular challenging to show that you’re actively engaged and expect high standards.
    4. Well-defined roles (9%): Both parties need to understand exactly what’s expected and when. You also need the ability to terminate the relationship and report directly if the service quality deteriorates. The FCA’s approach allows flexibility in materiality judgments. Firms must exercise best judgment about what’s material for regulatory purposes versus what’s material for their business.

    Looking Ahead

    The panel highlighted several challenges they are seeing more often, including:

    • Resource conflicts between commercial priorities and delegated reporting quality
    • Cross-border complexity creating operational headaches for teams
    • Fragmented technology and incomplete datasets mean reconciliation tools are struggling to piece together trade flows and reporting requirements to validate reports.

    Most importantly, the panel was concerned that knowledge retention* is becoming an issue as teams move between projects or are outsourced or offshored.

    What was the panel’s conclusion?

    Delegated reporting can work, but only with active oversight. The “out of sight, out of mind” approach simply doesn’t work.

    You can delegate the reporting, but you can’t delegate the liability. If done right, it reduces operational burden while maintaining standards but done wrong, it creates dangerous blind spots that regulators will likely find.

    • For help in establishing effective control and oversight of your delegated reporting, please get in touch. 
    • Find out more about how our SFTR Daily Controls can support your delegated reporting.
    • *Our Single Rulebook tool helps teams collaborate on regulation to create a single company view and trace decision-making across your organisation.
  • CSA Rewrite: Will the real Alan McIntyre please stand up (Part 2)

    CSA Rewrite: Will the real Alan McIntyre please stand up (Part 2)

    I asked AI tool Claude to write a blog in my voice discussing the Canada Rewrite. The blog that the AI tool wrote is published in Part 1 here.

    After reviewing what AI wrote as me, I thought it might be interesting to review Claude’s findings and provide my own commentary on where it got things right – and where it missed some crucial nuances.

    Claude’s Goldilocks Perfect Blend Observation

    Alan’s AI blog started with:

    “The Great Canadian Compromise: How the CSA Rewrite Became the Goldilocks of Derivatives Reporting

    After nearly three years of watching the Canadian Securities Administrators (CSA) craft their derivatives reporting rewrite, I’m convinced they’ve pulled off something remarkable: creating a regulatory framework that’s somehow both everything and nothing like its global cousins. It’s like watching someone order poutine with a side of fish and chips while sipping a margarita – technically it shouldn’t work, but here we are.”

    I’m impressed that AI referenced and improved on my ‘poutine’ joke from a previous article. I’m even more impressed that the main finding is spot-on: by taking their time, the CSA has arguably benefited by adopting the best of the CFTC Rewrite with a smattering of ESMA’s EMIR elements.

    The Canadian timeline was partly practical—they wanted reporting firms to have completed their CFTC Rewrite and EMIR Refit projects first. This was partly Canadian politeness (they didn’t want to overburden firms with too many overlapping projects) and also the real-world difficulties of writing clear, descriptive new rules.

    I concur with AI-me that the result is a nice blend of the best of the CFTC Rewrite and EMIR Refit.

    The Field Count Nuance Missed by AI

    “The Numbers Game: More Fields Than You Can Shake a Stick At

    Let’s start with the obvious: field counts. The CFTC managed to slim down to a svelte 128 fields for their 2022 rewrite, clearly believing that less is more. ESMA, meanwhile, went full maximalist with 203 fields in EMIR REFIT, apparently subscribing to the philosophy that if you’re going to ask for data, you might as well ask for everything including the kitchen sink and the recipe for the sandwich the trader ate during execution.

    Enter Canada with 148 fields (up from their initially proposed 140), sitting comfortably in the middle like a regulatory Switzerland. It’s neither the American “keep it simple, stupid” approach nor the European “let’s document everything down to the thread count of the counterparty’s suit” methodology. It’s distinctly Canadian – polite, thorough, but not unreasonably so.”

    AI-me is correct that the 148 CSA Rewrite fields sits between the CFTC’s 128 fields and EMIR Refit’s 203. However, it’s missing the important nuance that in reality, the CSA fields are far more closely aligned to the CFTC’s fields. While it’s true that the CSA adopted a handful of EMIR Refit fields, the far higher EMIR Refit field count is explained by multiple factors including:

    • ESMA publishing the margin fields in a separate table to the transaction fields
    • Unfortunate ESMA-isms like dual product identification fields
    • A higher prevalence of asset class specific fields (commodities fields in particular).

    AI-me also missed the contextual nuance that the CFTC has proposed a further 48 fields to accommodate them rolling out UPI for commodities.

    UPI: Where AI got it wrong (phew – my job might be safe for now!)

    “The UPI Situation: Taking Sides in the Global Divorce

    Here’s where things get interesting. The CSA has decided to require Unique Product Identifiers (UPIs) for ALL asset classes, putting them firmly in the ESMA camp and leaving the CFTC looking like the odd one out at the derivatives reporting dinner party. The Americans are still dragging their feet on commodity UPIs like a teenager being asked to clean their room.

    This creates a delicious regulatory arbitrage situation. Canadian firms reporting to multiple jurisdictions now get to experience the joy of generating UPIs for their commodity trades when reporting to Toronto, but not when reporting to Chicago. It’s like being asked to wear both a tie and a Hawaiian shirt to the same party – technically possible, but aesthetically questionable.”

    This is where having a human in the loop – someone who’s attended the meetings and followed the progress of certain topics – becomes essential.

    AI-me got this one wrong when it concluded:

    The CSA has decided to require Unique Product Identifiers (UPIs) for ALL asset classes, putting them firmly in the ESMA camp and leaving the CFTC looking like the odd one out.

    I’m being harsh on my AI counterpart here as it is not wrong that Canadian reporting rules require UPI for all five asset classes including commodities. In terms of comparing the CSA requirements with the CFTC’s, this is spot on.

    But it’s missing the all-important detail of the prolonged bun-fight that this caused ie. the industry and trade associations lobbying the Canadian regulators to align the commodities UPI compliance date with the CFTC’s (yet to be published) commodities UPI compliance date. The CSA then obliged with a blanket order providing the requested relief to implement UPI for commodities in Canada when the CFTC does likewise in the USA.

    I Concur With The Crypto and Timeline Tango Findings

    Nothing to add or challenge for these two sections.

    ISO 20022 – The Gift That Keeps on Giving

    “The ISO 20022 Tease: The Gift That Keeps on Giving

    Perhaps the most telling aspect of the CSA Rewrite is what it doesn’t include: ISO 20022. Like the CFTC, they’ve decided to save this particular joy for a future implementation, presumably sometime in 2026. This means we get to look forward to yet another round of system changes, testing, and the inevitable discovery that the ISO 20022 standard is both incredibly comprehensive and utterly bewildering.

    It’s like promising to renovate your kitchen but deciding to do it in phases – first the cabinets, then the plumbing, then the electrical, ensuring maximum disruption over the longest possible timeframe.”

    I absolutely love that AI-Me has adopted the “Gift that keeps giving” tagline that I first used to describe transaction reporting way back in 2015.

    As for the CFTC and the Canadian regulators kicking the ISO 20022 standards can down the road, I agree with me again (starting to become a theme). The current effort avoided in tackling this is merely delaying the pain and baking in yet another implementation further down the road.

    To Summarise

    The AI analysis was genuinely insightful – it captured the essence of the CSA’s “Goldilocks” approach and identified the key strategic decisions that make the rewrite distinctive. Where it fell short was in the crucial regulatory nuances that only come from following the detailed implementation process.

    The question now is whether the Canadians’ careful balance of compromise and pragmatism will prove as effective in practice as it appears on paper.

    I already had a very particular issue with AI. The way it’s typically written down in capital letters is often indistinguishable from Al (as in A lowercase L, or Al, as I’m often known). As a result I often read “ask AI” and wonder what has this got to do with me!

    Now it seems the situation is even worse than I suspected because AI does a better AL than I do!

    It replicated my writing style and replicated my humour (that alone should be a cause for concern, never mind AI driven killer robots, doubling down on McIntyre’s woeful humour should be an urgent concern for the UN!). And worst of all it did a decent analysis. Not perfect but at the same time truly terrifying for someone that earns their crust in the knowledge economy.

    And if AI learns how to chat to clients and how to drink pints after work, then I’m well and truly toast!

    PS. My partner added that if AI learns how to do housework then I’m getting replaced at home too!!

    • For a conversation with Alan about the CSA Rewrite or a free health check of the quality of your reported data, please get in touch.

     

  • CSA Rewrite: Will the real Alan McIntyre please stand up (Part 1)

    CSA Rewrite: Will the real Alan McIntyre please stand up (Part 1)

    I asked AI tool Claude, to write a witty blog about the Canada Rewrite in the voice of Alan McIntyre, regulatory reporting expert at Kaizen. What it generated nailed my writing style and my humour. It also referenced previous jokes that I’ve used and it wrote something much better than I thought it could have written!

    Part 1 is included below. In Part 2, I’ll assess Claude’s findings and provide my own commentary, but in the meantime read on to find out what my, er, colleague? assistant? replacement? wrote as me:

    The Great Canadian Compromise: How the CSA Rewrite Became the Goldilocks of Derivatives Reporting

    By Alan McIntyre, Regulatory Reporting Expert, Kaizen

    After nearly three years of watching the Canadian Securities Administrators (CSA) craft their derivatives reporting rewrite, I’m convinced they’ve pulled off something remarkable: creating a regulatory framework that’s somehow both everything and nothing like its global cousins. It’s like watching someone order poutine with a side of fish and chips while sipping a margarita – technically it shouldn’t work, but here we are.

    The Numbers Game: More Fields Than You Can Shake a Stick At

    Let’s start with the obvious: field counts. The CFTC managed to slim down to a svelte 128 fields for their 2022 rewrite, clearly believing that less is more. ESMA, meanwhile, went full maximalist with 203 fields in EMIR Refit, apparently subscribing to the philosophy that if you’re going to ask for data, you might as well ask for everything including the kitchen sink and the recipe for the sandwich the trader ate during execution.

    Enter Canada with 148 fields (up from their initially proposed 140), sitting comfortably in the middle like a regulatory Switzerland. It’s neither the American “keep it simple, stupid” approach nor the European “let’s document everything down to the thread count of the counterparty’s suit” methodology. It’s distinctly Canadian – polite, thorough, but not unreasonably so.

    The UPI Situation: Taking Sides in the Global Divorce

    Here’s where things get interesting. The CSA has decided to require Unique Product Identifiers (UPIs) for ALL asset classes, putting them firmly in the ESMA camp and leaving the CFTC looking like the odd one out at the derivatives reporting dinner party. The Americans are still dragging their feet on commodity UPIs like a teenager being asked to clean their room.

    This creates a delicious regulatory arbitrage situation. Canadian firms reporting to multiple jurisdictions now get to experience the joy of generating UPIs for their commodity trades when reporting to Toronto, but not when reporting to Chicago. It’s like being asked to wear both a tie and a Hawaiian shirt to the same party – technically possible, but aesthetically questionable.

    The Crypto Conundrum: Modern Problems, Modern Solutions

    One area where the CSA has clearly been taking notes from ESMA’s homework is cryptocurrency derivatives. The inclusion of the “Derivative Based on Crypto-assets” field shows they’re thinking ahead – unlike the CFTC, which is still figuring out how to classify Bitcoin derivatives without causing an existential crisis in their taxonomy department.

    This is smart regulatory future-proofing. Cryptocurrency derivatives aren’t going anywhere, and having a dedicated field for them prevents the current comedy of errors where firms report Bitcoin derivatives under the commodity asset class while secretly wondering if they should be filing them under “miscellaneous modern monetary confusion.”

    The Timeline Tango: July 25, 2025

    The CSA’s implementation date of July 25, 2025, is fascinating from a strategic perspective. It’s almost exactly 2.5 years after the CFTC’s December 2022 implementation, which means Canadian firms have had plenty of time to watch their American colleagues struggle through the transition, learn from their mistakes, and presumably stock up on coffee and antacids.

    This timing also means the CSA Rewrite lands right in the middle of what I like to call the “global regulatory reporting fatigue zone” – that sweet spot where everyone’s tired of implementing new rules but not quite tired enough to stop making them.

    The ISO 20022 Tease: The Gift That Keeps on Giving

    Perhaps the most telling aspect of the CSA Rewrite is what it doesn’t include: ISO 20022. Like the CFTC, they’ve decided to save this particular joy for a future implementation, presumably sometime in 2026. This means we get to look forward to yet another round of system changes, testing, and the inevitable discovery that the ISO 20022 standard is both incredibly comprehensive and utterly bewildering.

    It’s like promising to renovate your kitchen but deciding to do it in phases – first the cabinets, then the plumbing, then the electrical, ensuring maximum disruption over the longest possible timeframe.

    The Goldilocks Effect: Just Right?

    The CSA Rewrite represents something genuinely unique in the regulatory reporting landscape: a conscious attempt to cherry-pick the best elements from multiple jurisdictions while avoiding their worst excesses. It’s more comprehensive than the CFTC Rewrite but less overwhelming than EMIR Refit. It’s forward-looking on crypto assets but pragmatic about implementation timelines.

    Whether this Goldilocks approach – not too hot, not too cold, but just right – actually works remains to be seen. What’s certain is that it creates a fascinating test case for whether regulatory compromise can produce better outcomes than regulatory extremes.

    As we near July 25, 2025, one thing is clear: the Canadian approach to derivatives reporting reform is as distinctly Canadian as maple syrup on bacon – it shouldn’t work, but somehow it might just be brilliant.

    Now, if you’ll excuse me, I need to go update my regulatory reporting calendar. Again.

    • Stay tuned for Part 2 where human Alan fights back!
    • For a conversation with Alan about the CSA Rewrite or a free health check of the quality of your reported data following the rewrite, please get in touch.

     

  • EMIR Refit: Five Key Takeaways from Kaizen RegTalk

    EMIR Refit: Five Key Takeaways from Kaizen RegTalk

    EMIR Refit is one of the most significant pieces of regulatory change in financial services in recent years. At our recent Kaizen RegTalk conference, we hosted a panel discussion: “EMIR Refit – One Year On” bringing together speakers from the Financial Conduct Authority (FCA), Bank of England, HSBC as well as Kaizen’s subject matter expert Tim Hartley, to share their experiences of the implementation. The panel was hosted by John Graham from the Futures Industry Association (FIA). 

    To set the scene, the EMIR panel commenced with a live audience poll asking how firms felt about their EMIR Refit experience one year on. The results painted an interesting picture: 

    • 47% said it went “about as expected,” 
    • 20% found it “smoother than expected.” 
    • 20% are “still working through issues,” and 
    • 13% found it “more challenging than expected.” 

    These results confirm the broad industry view that firms made good progress in ensuring compliance at go live, and were able to submit successfully, but that momentum has slowed down as firms focus on their ‘day two’ book of work. 

    Here are five key takeaways from our panel discussion:

    1. Learning from the challenges of EU go-live 

    Firms with dual reporting obligations in the UK and EU had the advantage of going live first with EU EMIR Refit and then five months later with UK EMIR Refit. The staggered go-live dates meant that firms had the chance to see what worked and what didn’t in the EU regime, providing them with the opportunity to rectify errors and improve processes in time for UK implementation. 

    The majority of UK firms reported successfully on day one with high acceptance rates and minimal disruptions, which is reflected above in the total 67% of firms who highlighted a positive experience of go-live (i.e. “about as expected” and “smoother than expected”).

    2. Now is the time to focus on data quality

    While the initial focus was on acceptance rates, the panel participants made it clear that getting technically connected and having reports accepted was only the beginning. Many firms are meeting the validation rules, and trade repository rejection rates are thankfully low. However, firms can be compliant with the validation rules BUT still have inaccuracies in their data – the focus for firms now must be to identify and locate issues and remediate them.   

    Many firms are now spending significant time and resources on fixing errors that are still ongoing, and the industry is grappling with the much more difficult task of ongoing data quality management. 

    Key issues that firms continue to face include: 

    • Matching Problems: while pairing rates are getting better, reconciliation breaks still create significant work. Different interpretations between counterparties on certain fields are causing ongoing headaches. 
    • Counterparty Data Issues: this is especially problematic when firms use delegated reporting, where maintaining oversight while relying on third parties creates practical challenges with reporting for the same legal entity. 
    • More Changes Coming: additional reconciliation fields will be rolled out in phases, indicating that firms need to stay prepared. 

    3. Resilience during periods of increased volatility 

    One area discussed by the panel participants was how well systems are coping under pressure for example, during the recent ‘Liberation Day’ market stress and volatility, reporting volumes jumped from 30 million to 76 million reports per day – more than double average volumes. But firms’ systems and teams across the industry managed the increased reporting volumes smoothly.

    4. ‘Regulatory decay’ 

    The panel highlighted something that is often underestimated: the ongoing effort required to continue to align with regulatory requirements after implementation and go-live. Budget pressures and limited team resources means firms need to prioritise which problems to fix first. 

    A major concern raised was “regulatory decay” – losing knowledge as team members move onto new projects. Firms realise they need strong processes in place to maintain standards and grow the expertise they’ve built in-house. 

    5. Regulators ARE using the data

    Regulators from the Bank of England and FCA gave insights into how they are actually using EMIR data, which reinforces why it’s so important to get reported data correct: 

    • Policy Decisions: the data goes directly to the Financial Policy Committee and Monetary Policy Committee 
    • Watching Markets: real-time monitoring of risks and market concentration 
    • Crisis Response: quick analysis when firms fail (like Silicon Valley Bank) — results in minutes, not days 
    • Stress Testing: using detailed derivatives data for policy planning 
    • Market Abuse: every FCA investigation in the past decade has started with data from transaction reports. 

    Looking Ahead 

    Panel participants made it clear that the key lesson from the EMIR Refit implementation is that it wasn’t a one-time project. Meeting the regulatory obligation is an ongoing process that requires constant attention to data quality and systems management, especially given how important this data is to regulators and what it’s being used for. 

    Concerned about the quality of your EMIR Reporting data? More than 200 firms from tier 1 banks to small fund managers rely on Kaizen’s quality assurance to meet – and exceed – their regulatory obligations. Contact us to request a demo or for a conversation with one of our regulatory experts. 

  • ESMA’s 2024 Annual Report: Data Quality Progress and Recent MiFIR Review Developments

    ESMA’s 2024 Annual Report: Data Quality Progress and Recent MiFIR Review Developments

    ESMA’s 2024 Annual Report, released in June, provides a wide ranging overview of the European regulator’s activities across its broad mandate. While the 84-page document touches on numerous regulatory initiatives, the updates on transaction and trade reporting frameworks provide useful insights for reporting firms.  

    Data Quality Indicator Dashboards  

    The report highlights ESMA’s implementation of data quality indicator (DQI) dashboards, now accessible to National Competent Authorities (NCAs) via ESMA’s data platform, for both MiFIR transaction reporting and EMIR trade reporting.  

    The new framework establishes clear accountability: reporting entity issues go to relevant NCAs, while Data Reporting Service Provider (DRSP) problems are handled directly by ESMA. While in theory the DQIs sound like an improvement in supervisory tools, as we know, the real test will be whether they translate into meaningful improvements in data quality. 

    MiFIR Developments Overshadowed by Strategic Pause 

    ESMA’s data strategy implementation focused on “optimising financial market data while reducing regulatory burden” through reusing transaction data to eliminate duplications. The migration to ESMA’s new data platform allowed wider use of MiFIR transaction data for applications like monitoring European carbon market integrity.  

    The most significant development came after the Annual Report’s publication when ESMA announced that the MiFIR Review is being put on hold while it conducts a Call for Evidence “to gather feedback on opportunities to simplify, better integrate and streamline supervisory reporting.” This pause affects existing requirements under transaction reporting (RTS 22), order data (RTS 24), and reference data (RTS 23). 

    The Call for Evidence deadline is September 19, with ESMA’s final report due by early 2026.  

    EMIR: Modest Improvements Amid Complexity 

    The report also highlights improvements in EMIR reporting data quality, supported by ESMA’s peer review follow-up. However, these improvements should be seen in perspective, coming after many years of well-known data quality problems that have made effective supervision difficult. 

    ESMA’s Trade Repository supervision during the EMIR Refit implementation was more successful, which the regulator attributes to intensive pre-implementation engagement.  

    Broader Regulatory Pressures 

    Beyond reporting frameworks, the Annual Report reveals an organisation struggling with an expanded mandate and limited resources. ESMA admits it has had to move staff and resources to different areas due to new responsibilities without the additional funding. 

    The report also illustrates ESMA’s increasingly broad mandate. This shows regulatory ambition, but it also highlights how difficult it is to maintain focus and expertise when covering so many complex areas. 

    Evolution, Not Revolution 

    The developments in MiFIR and EMIR reporting represent gradual improvements rather than fundamental reforms to regulatory reporting. Better data quality tools and clearer operational guidance are welcome, but they address symptoms rather than the underlying framework and complexity of rules. 

    The pause of the MiFIR Review, while giving breathing space for firms, acknowledges that the current approach may be overly burdensome. For firms, this provides an opportunity to influence the direction of the reporting framework but obviously extends the uncertainty about long-term requirements. ESMA’s growing focus on data and enhanced supervisory powers suggests more intensive oversight could be just around the corner. 

  • ESMA’s SFTR Data Quality Indicators: Progress with Limitations

    ESMA’s SFTR Data Quality Indicators: Progress with Limitations

    The New Framework 

    ESMA finalised its 23 SFTR Data Quality Indicators (DQIs) during 2024 and published them last month together with a “Framework for provision of data and follow-up on SFTR data quality issues“. The framework laid out how results of the DQIs are identified and expressed at the EU level, discussed at the Repositories Task Force (RTF) and shared with National Competent Authorities (NCAs) at the entity level.

    NCAs are now expected to follow up with the entities and provide feedback to ESMA. ESMA then reviews the feedback and performs a rerun to confirm the issue has been resolved, this is then shared with the RTF with any follow-ups deemed necessary. Given how variable and sporadic SFTR supervision has been across Europe, these are very positive developments. 

    Understanding the 23 DQIs: Not All Created Equal 

    Ask an ESMA official and all 155 SFTR reporting fields were created equal, however, I suspect that there is a very different view on the ground in the regulatory reporting oversight offices of the 30 NCAs and two European Supervisory Authorities (ESAs). Under SFTR, predominantly but not exclusively a systemic risk monitoring regulation, trade economics are king.  

    In summary, while the DQIs will provide the less sophisticated NCAs with a means of challenge their regulated entities in at least a minimal way, for others unfortunately at this stage, they may be little more than a distraction in performing their valuable work in keeping their domestic economies from harm. ie. time spent reviewing ESMA findings and coordinating responses may actually be better placed analysing genuinely systemic issues in that jurisdiction. 

    Two-Sided Reconciliation Tests (8 DQIs): Eight of the 22 DQIs rely on a fundamental assumption: that SFTR reports are genuinely two-sided. This means both parties have reporting obligations, are in the same jurisdiction, haven’t delegated their reporting, and their data comes from independent sources rather than shared systems. In theory, this creates a true representation of each firm’s books and records. However the reality is very different. These DQIs are flawed because so few reports are genuinely, independently two-sided. Most data ultimately comes from a single source – whether through shared systems, data vendors, or reporting delegation. In our experience, time and time again, two wrongs really do make a wrong when you’re trying to reconcile reports that originated from the same place.

    Reporting Discipline Issues (10 DQIs): A further 10 of the DQIs cover essentially SFTR reporting discipline issues rather than material economics. These include the number of rejected reports (NACKs), late reporting, missing variation margin reports on CCP cleared trades, client codes used in place of LEIs, missing issuer LEIs, incorrect reporting counterparty classification x 3, duplicate reports and not updated event dates. 

    The One with Potential: DQI 11A Anomalies 

    There is just one SFTR DQI that appears to have the potential to be truly powerful. Unfortunately like many things SFTR, it is rather loosely defined. DQI 11A Anomalies uses statistical approaches to identify abnormal/anomalous values in listed fields but encouragingly, in ratios between relevant fields too. This DQI spans 20 SFTR fields covering repo, securities lending and margin lending across loan values, collateral values, market values, lending fees, haircuts, CCP margins, collateral reuse and cash reinvestment (for securities lending). Arguably this should really be broken down into hundreds of sub and specific DQIs per type of SFT and nature of the test, such that there is a thorough understanding of the parameters and expectations. It would also enable firms to implement these indicators in their own controls frameworks. Unfortunately there are no further details or definition, such that both NCAs and reporting counterparties are left to guess the precise nature of the tests. 

    The Bigger Picture Problems 

    Aside from the limited instances of true independent two-sided reporting and an over-emphasis on reporting discipline, many of the tests also focus on the number of reports or instances, not their economic value. Also considering that in terms of market size and risk exposure, in excess of 75% of the SFT market in the EU is repo and the closely related buy-sellback market, it is something of a concern that the lion’s share of DQIs are focused on the securities lending. As primarily macro-systemic regulation, this is disappointing. 

    Looking Forward 

    It’s easy to pick holes in the new SFTR DQIs but for the forgotten stepchild of EMIR, they are certainly a move in the right direction. While at this stage it appears to be something of an opportunity squandered, firms should be painfully aware that they are on notice to up their game in terms of SFTR data quality. Those NCAs that have kept quiet and have been lurking in the shadows are highly likely to let their presence be felt once they start receiving DQI queries from ESMA that require their attention. 

    Kaizen’s quality assurance testing includes checking for all issues included in ESMA’s DQIs and many more. For a conversation with Jonathan or one of our regulatory experts about your SFTR data quality, please get in touch.

  • ESMA’s Data Quality Report 2024: MiFiR transaction reporting remains a key focus

    ESMA’s Data Quality Report 2024: MiFiR transaction reporting remains a key focus

    ESMA’s fifth report on data quality (published 30th April) – like last year’s – seemed light on a first read for MiFIR. But a second read alongside another ESMA document, the “Data Quality Engagement Framework (DQEF) for MiFIR’ published a week after the report, reminds us that MiFIR transaction reports and their data quality remain a key focus for ESMA and EU National Competent Authorities (NCAs).

    The purpose of MiFIR transaction reporting

    In the data quality report (DQR) ESMA reinforces, should we have forgotten, that data supports the day-to-day activities of financial regulators and remains essential for them to achieve their primary mandates of financial stability, orderly markets and market integrity.

    “Reduce the reporting obligations on firms”

    The DQR provides a number of use cases, introduces the DQEF and gives a significant mention to the role of transaction reports in the transparency and volume cap calculations that will reduce the reporting obligations on firms.  In case you missed it – “reduce the reporting obligations on firms”. The proof of concept (PoC) to prove the role of reports in these calculations determined that data quality is good but the DQEF being introduced is designed to address the critical data quality issues that became apparent during the exercise. 

    Improved tooling for increased scrutiny

    Furthermore, the DQR mentions that ESMA and NCAs now have improved tooling for monitoring markets. This includes details on the ESMA Data Platform (EDP) where regulators can share reported data and access predefined analytics to support them in their work.  As we highlighted last year – firms contributing reports to these calculations that are lacking data quality can expect their NCA to give them an opportunity to discuss the issues found.

    Delving into the details

    At a macro level, reported data under MiFIR is used to monitor overall trends and key market-level developments.  NCAs use the data in national financial stability reporting and sectoral updates whilst some have established systems to monitor trading venue activity or to rank firms based on their risk profiles.

    For the detection of market abuse, NCAs have developed a variety of automated alerting tools to highlight behaviours that could threaten market integrity for follow up by surveillance staff.  Data from different regimes is combined to identify cases of potential market abuse. 

    New tests to enhance data quality

    The PoC to test the potential for using MiFIR data for transparency and volume cap calculations achieved > 95% accuracy and hence will replace the existing systems (FITRS and DVCAP) and reduce the reporting burden for firms.  The discrepancies found will be addressed via the newly established DQEF based on ESMA’s existing transaction data validation rules and the TREM (Transaction Reporting Exchange Mechanism) DQEF tests, with new completeness, accuracy and consistency tests introduced to enhance data quality.

    The aim is to launch the DQEF in the first half of 2025 to allow NCAs and firms to address the quality issues found – ahead of the go live of the new transparency and volume cap system.   

    Conclusion

    We are often asked, ‘do regulators actually use the data?’ and the DQR provides clear evidence that they do. ESMA’s reuse of MiFIR transaction data for transparency and volume cap calculations demonstrates its commitment to reducing duplicative reporting – something the industry has long requested. However, increased data usage means increased scrutiny. Firms submitting poor quality data can expect to be contacted, remediation expected, warnings given and potential enforcement action.

    Firms often approach us for quality assessments after the regulator has challenged their data. This puts them in damage control mode.  The better approach is proactive quality assurance that identifies problems before regulators do. Please don’t hesitate to reach out to us at Kaizen to see how we can help.

  • The FCA’s Approach to Financial Crime: Market Integrity is Non-Negotiable

    The FCA’s Approach to Financial Crime: Market Integrity is Non-Negotiable

    In an important powerful address at the Market Abuse and Market Manipulation Summit on April 28, 2025, Therese Chambers, joint executive director of enforcement and market oversight at the Financial Conduct Authority (FCA), laid out the regulator’s comprehensive strategy to maintain market integrity and combat financial crime, including market abuse, through what she terms the “three Ps” approach – being predictable, proportionate, and purposeful.

    Crackdown on Organised Crime: No Mercy for Market Abusers

    Financial crime is at the forefront of the FCA’s agenda and strategy. In her speech in April, Chambers identified Organised Crime Groups (OCGs) as “the most serious threat to our markets,” revealing they account for approximately 25% of all Suspicious Transaction & Order Reports (STORs). The scale of the problem threatening market integrity is staggering – the FCA has identified over half a billion pounds in OCG profits from suspicious trading since 2022 alone.

    As a result, the regulator is taking aggressive action to disrupt these criminal operations, including executing arrests and coordinating with multiple agencies on financial crime both domestically and internationally. This zero-tolerance approach extends beyond OCGs to all forms of market abuse and market manipulation.

    Where firms persistently fail in their responsibilities, the FCA won’t hesitate to intervene with decisive action. A recent example is the restrictions imposed on an investment firm, preventing it from onboarding any new customers to its Contracts for Difference (CFD) business without FCA permission due to inadequate systems and controls for identifying and reporting market abuse.

    Raising the Bar: Sophisticated Threats Demand Sophisticated Controls

    As market abuse techniques evolve in complexity, the FCA is raising expectations for firms’ detection and prevention capabilities. Chambers acknowledged that “those who seek to abuse our markets are becoming more sophisticated. But so are our detection and enforcement capabilities.”

    Firms are expected to implement increasingly advanced surveillance systems that can keep pace with emerging threats. The FCA was explicit that adequate systems and controls to identify and report market abuse are “not just a nice-to-have – it’s a fundamental responsibility.”

    MiFID transaction reports remain vital to the FCA’s work in identifying and acting against market abuse, providing “a rich and unique view of our markets.” This is particularly important during periods of volatility – Chambers noted that on April 7 alone, 76 million transaction reports were received across asset classes, more than double the daily average of 30 million.

    Culture Is Key: Building Market Integrity From Within

    A strong anti-market abuse culture within firms forms the bedrock of the FCA’s strategy. The regulator sees firms as “the first line of defence against market abuse,” and recognises that “most firms work very hard to get it right.”

    Chambers emphasised that firms should not hesitate to offboard entire corporate relationships if they don’t fit their risk profile. “In fact, this is often the right response when risks are identified,” she stated. This highlights the expectation that maintaining market integrity should be prioritised over commercial interests when necessary.

    The value of data combined with collaboration is evident in the FCA’s reliance on Suspicious Transaction & Order Reports (STORs). These reports are described as “invaluable” to the FCA’s work, with over 70% of current market abuse investigations originating from a STOR. Last year alone, the FCA received 4,528 STORs, showing an increasing trend over previous years.

    Market Integrity: The Foundation of Economic Growth

    One of the most compelling aspects of Chambers’ speech was the direct connection drawn between market integrity and economic prosperity. She emphasised that “cleaner markets instil confidence, which encourages investment into our markets, which encourages growth and innovation. It’s a virtuous cycle.”

    The FCA’s 5-year strategy to 2030 includes a dedicated pillar to fighting financial crime, alongside supporting sustained economic growth. Chambers was emphatic that “our work on market abuse is a critical part of all areas of that strategy” and that “market cleanliness and economic growth go hand in hand.”

    Innovation Meets Integrity: The PISCES Initiative

    In a significant move to balance regulation with growth, the FCA has announced plans for a ‘Private Intermittent Securities and Capital Exchange System’, or PISCES – a new type of stock market for private companies that will allow firms to trade shares on a periodic basis, outside the Market Abuse Regulation (MAR) regime.

    This innovative approach is described as a ‘private plus’ mechanism where “transaction reporting will not apply” and “companies will retain more control over aspects of their trading events, such as timing, frequency and participation.” While this represents a lighter regulatory touch to support growth, it’s important to note that the UK’s Criminal Market Manipulation regime will still apply to this market. In addition, MAR would also apply if PISCES shares were admitted to trading to a Multilateral Trading Facility (MTF).

    This initiative demonstrates the FCA’s “calculated increase in our risk appetite to support growth” and willingness to “innovate and take more risks.”

    Recent Enforcement Success: Day Traders Face Consequences

    The FCA’s commitment to enforcement is producing results. As recently highlighted in a LinkedIn post by our Subject Matter Expert for Market Abuse & Surveillance, Simon Appleton, “Wall crossed ‘day traders’ plead guilty to insider dealing,” the regulator is successfully pursuing convictions and confiscating proceeds from illegal activities.

    The case raises important questions about how and why ‘professional day traders’ were routinely provided with non-public, price-sensitive information through ‘wall crossings’ – which are typically used to gauge interest from potential investors rather than traders seeking quick profits.

    Another recent enforcement action demonstrates the critical importance of industry vigilance. Chambers referenced charges against five individuals for insider dealing offences, including a former analyst at an asset management firm, who allegedly used inside information to enable trading that yielded profits of approximately £1.5 million. This case originated from a STOR that prompted further investigation of trading data.

    Looking Ahead: Global Challenges Require Global Solutions

    As suspicious behaviour easily crosses borders, Chambers stressed that “close and cooperative relationships with domestic and international regulators and law enforcement agencies are more important than ever.” The FCA is strengthening its international engagement and strategy to address this reality.

    The regulator is also expanding its focus across asset classes, having “significantly ramped up our effort and coverage across Fixed Income, Currencies & Commodities (FICC) markets.” A recent example includes an investigation into three bond traders regarding alleged manipulation of Italian government bond futures, resulting in bans and fines.

    The message from the FCA is clear: market integrity is non-negotiable. Through their three-pronged approach of being predictable, proportionate, and purposeful, they are determined to create markets that remain hostile to abuse while fostering innovation and growth. As Chambers concluded, “Together, let’s keep building a market that remains hostile to abuse and welcoming to honest participation.” 

  • ESMA’s 2024 Data Quality Report: EMIR Refit under the Microscope

    ESMA’s 2024 Data Quality Report: EMIR Refit under the Microscope

    ESMA released the fifth iteration of its Report on Quality and Use of Data (DQR) late last month, which highlights the use of reported data across multiple regimes, critiques submission quality, and references some of the enforcement actions carried out in 2024. This analysis focuses on the DQR’s EMIR data quality findings and their implications for firms. We have also published our SFTR analysis of the report.

    Focus on EMIR Refit

    Last year’s DQR placed a heavy emphasis on the potential for the EMIR Refit reporting changes to improve data quality. 12 months later, ESMA provides a mixed assessment:

    • ‘Positive assessment of go live’ in April 2024
    • Concerns regarding preparedness of Trade Repositories and reporting entities
    • Ongoing ‘need for further engagement for corrective actions’.

    EMIR Reporting was described by ESMA in last year’s DQR webinar as being ‘much more complicated’ under EMIR Refit. From Kaizen’s view of post-Refit reporting, many firms still have significant work to do to uncover hidden reporting issues and apply successful remediation procedures. This report may still be too early to provide a true reflection of data quality under the EMIR Refit regime.

    Limited Data Quality Indicators (DQIs)

    The EMIR metrics provided in the report give a limited and somewhat lacklustre view on where EMIR data quality currently rests.  Of the seven DQI metrics displayed:

    • Six show a mild improvement in data quality metrics (such as the Number of Outstanding Trades in Chart 3)
    • One indicates declining quality – percentage of missing valuations (Chart 7).

    A more comprehensive analysis of all the EMIR DQIs would be extremely useful for the industry and help us to gain a more accurate evaluation of data quality. ESMA’s Data Quality Dashboard for EMIR Refit document details (approximately) an additional 18 DQIs (c.25 in total) that are being actively monitored and discussed between supervisory authorities. The DQIs are a key tool within their regulatory arsenal and it is disappointing only a small number appear in the public report.

    Key DQI findings

    Rejection rates

    ESMA highlights the rejection rate of derivatives, which sits at approximately 1-2.5% across EU submitters. The rejection rate is described as ‘critical for authorities’ to ensure data is complete and accurate. ESMA’s expectation is for a ‘close to zero’ rejection rate.

    For me, the late report statistic is far more important, as firms are required to report trades in a timely and accurate fashion. Late submissions by some counterparties can lead to the view of unpaired submissions that distort the visibility of derivative exposure. Firms are required to report by end of day T+1, and are not in breach of any regulatory requirements if they resubmit a rejected derivative within that timeframe. In the absence of any material increases in this statistic, I question the value of emphasising it.

    Legacy format upgrades

    The DQR states that ‘36 million’ submissions needed upgrading to the new EMIR Refit format within 180 days from April 2024. At the end of February 2025, 2% of those submissions had not been converted. Firms with a UK EMIR reporting obligation should take note of the focus on updating old submissions and enforcing the strict schemas under EMIR. ESMA states firms should ensure ‘swift upgrading’ of any old format derivatives.

    Maturity date issues

    Abnormal or blank maturity dates continue to cause confusion (as shown in Chart 6), despite a small reduction to approximately 10% of submissions. Due to products such as CFDs, the maturity date fields have not been mandatory under EMIR Reporting’s validation rules, long prior to EMIR Refit. Regulators fully expect these ‘optional’ fields to be populated where applicable to the derivative. It is worth repeating:

    Optional fields do not mean the entity has a choice as to whether they are populated or not.

    Abnormal or blank maturity dates is a relatively high figure at 10% and ESMA explicitly expects a ‘lower percentage going forward’. Firms must ensure that this data point, and all further ‘optional’ fields are fully reviewed and are being reported for all submissions in a timely and consistent manner.

    Missing valuations

    Chart 7 shows that missing valuations are increasing (currently at 12.36%), even though daily valuations are required for a large majority of EMIR reporters and have been since August 2014. 

    Entity Responsible for Reporting (ERR)

    The DQR also places emphasis on a new field from EMIR Refit, the Entity Responsible for Reporting (ERR). This OTC field is described as a ‘crucial addition under EMIR Refit’ and ESMA appears dissatisfied with the volume of misreporting of this field (as shown in Chart 6).

    Trade Repositories’ (TRs) challenges

    ESMA gives mention to the reporting difficulties of TRs as well as entities, including issues such as:

    • Difficulty with reporting portability
    • LEI updates from M&A activity
    • Inter-TR reconciliation delays
    • Challenges providing complete reports to the NCAs.

    In my opinion, this highlights the complexity of EMIR Refit for firms and TRs alike, notably given the vast range of reportable products and lifecycle events, under a complicated reporting regime.

    The simplification paradox

    ESMA makes efforts to explain its desire to simplify reports and reduce the regulatory burden for firms. Very few firms will agree that this objective has been achieved in practice or in the spirit of the regulation. While many aspects of reporting have received welcome clarification, additional reporting requirements have been introduced and made the overall regulatory regime much more complex.

    What does this mean for firms?

    Based on the DQR findings, firms should focus on:

    1. Ensuring proper population (where applicable) of maturity data fields
    2. Valuation reporting – review processes to stop the increasing trend of missing valuations
    3. ERR field accuracy – verify the correct implementation of this ‘crucial’ addition
    4. Legacy migrations – complete any remaining pre-Refit format submission upgrades
    5. Rejection rates vs late reporting – while ESMA focuses on rejection rates, firms should also prioritise timeliness.

    Assessment

    Overall, I welcome the DQR’s attention to data quality critique and its motivation to help firms achieve regulatory compliance through complete, accurate and timely reporting. The justification of how data is used is particularly valuable, as this large operational burden is often questioned by firms.

    Going forward, the DQR would benefit from further transparency and metrics across the full suite of DQIs. This would help firms understand how their reporting is being reviewed by supervisory authorities and allow them to focus their limited remediation resources on improving the most material parts of EMIR Reporting.

    Better guidance and clarity would also ensure firms are better equipped to ensure reporting is complete and accurate at point of submission, negating the need for costly remedial action for firms and regulators alike.

    Concerned about the quality of your EMIR Reporting data? More than 200 firms from tier 1 banks to small fund managers rely on Kaizen’s quality assurance to meet – and exceed – their regulatory obligations. Contact us to request a demo or for a conversation with one of our regulatory experts. 

  • ESMA’s 2024 Data Quality Report: Increased Focus on SFTR Data Quality

    ESMA’s 2024 Data Quality Report: Increased Focus on SFTR Data Quality

    ESMA’s Report on Quality and Use of Data for 2024 (published 30 April 2025), delivers a clear message: “ESMA expects that reporting entities increase the quality of their reported data significantly” and “the quality of the SFTR data still has large margins of improvements.”

    A particularly encouraging development is the “enhanced cooperation with BaFin,” where ESMA and BaFin established “an enhanced periodic engagement” with BaFin stepping up their approach and increasing targeted efforts. This marks positive progress in what had previously appeared to be somewhat polarised regulatory scrutiny across the EU.

    SFTR Data Quality Indicators Now Fully Implemented

    ESMA finalised its Data Quality Indicators (DQI) approach for SFTR in 2024, following their successful introduction for EMIR in 2022. Prior reports highlighted concerns, most notably the overstatement of open term securities loans values during 2021-2023, but there was relatively little structured analysis before the DQIs. ESMA notes that “a TR issue due to which inflated market values were observed has been resolved with the pending correction of historical data being monitored,” likely referring to reporters’ failure to send terminations or add maturity/end dates to open term securities loans.

    Key SFTR Data Quality Indicators Revealed

    Missing Valuations (DQI 5a)

    This metric shows significant improvement, falling from 26.3% in March 2023 to 8.5% by December 2024, though still above ESMA’s 5% threshold. The “dramatic” improvement was due to “amelioration of reporting by a few of the major reporting entities.”

    Outdated Valuations (DQI 5b)

    Of all DQIs, this remains “the worst among depicted DQIs,” despite falling from 41.4% in March 2023 to 26% by December 2024. ESMA emphasises: “Having updated information in times of adverse market movements and crises is crucial for authorities” and it is “imperative for counterparties to swiftly follow on the identified issues with outdated valuation.”

    Trade Reporting Discrepancies (DQI 1a)

    This indicator shows an average of 35% mismatch in outstanding SFTs between counterparty pairs – far above the 5% threshold and higher than EMIR’s 20.5%. This is remarkable considering that many SFTR reports are single-sided, and many dual-sided reports are generated by a single party with pre-matching and third-party data enrichment.

    Position-Level Discrepancies (DQI 1b)

    This indicator measures differences in position-level reporting between counterparties. While ESMA highlights this metric, position-level reporting is relatively uncommon in SFTR, making its prominence in the report somewhat curious.

    Entity Responsible for Reporting (DQI 9a)

    This field identifies who is responsible for reporting (UCIT managers for funds, AIFMs for AIFs, etc.). Though important for attributing data quality errors to the correct entity, this metric showed modest issues at 1.9% by end of 2024.

    Regulatory Expectations Rising

    ESMA’s commitment to data quality is clear: “ESMA always encourages the amelioration of reporting even in cases where the error rate is below the DQEFs which govern actions taken to tackle data quality.”

    Our Perspective

    At Kaizen, we welcome the increased focus on SFTR data quality five years after implementation. The publication of the Data Quality Engagement Framework and DQIs provide important steps toward greater regulatory certainty.

    However, we are cautious about equating matched reports with high-quality data. We would also challenge the focus on securities lending data elements and the relative absence of repo data given its greater systemic risk significance.

    Is your SFTR reporting in good shape? Can you evidence this? Kaizen provides comprehensive quality assurance for accurate, complete and timely SFTR reporting.  We also provide Daily Controls for SFTR delegated reporting arrangements.

    Contact us to request a demo or for a conversation with Jonathan or one of our regulatory experts.

  • FCA tells buy-side CEOs that market abuse is a supervisory priority for 2025

    FCA tells buy-side CEOs that market abuse is a supervisory priority for 2025

    Hot on the tail of the Dear CEO letter to wholesale brokers, the latest FCA letter to asset managers and alternatives cites the reduction of financial crime and market abuse within their broader supervisory strategy.

    This Dear CEO letter, from Camille Blackburn the FCA’s Director of Wholesale Buy-Side reveals that the UK regulator will be conducting targeted work in the area of financial crime and market abuse.

    The FCA prompts asset managers that they should be alert to the risk that they could facilitate financial crime and the importance of having robust systems and controls to mitigate this risk. Where the FCA identifies weaknesses in controls they will conduct reviews in the areas such as anti-money laundering controls in private market funds.

    In addition, the FCA repeats that market abuse undermines market confidence and integrity, and that having robust systems and controls are crucial in mitigating this risk.

    The regulator closes with a reminder that they expect firms to:

    • discuss this letter with their Board, Executive Committee, and accountable Senior Managers; and
    • ensure that their market abuse controls enable them to discharge obligations under the Market Abuse Regulation.

    If you would like support with your Market Abuse Risk Assessment framework to help prevent issues like insider trading and market manipulation before they occur, please get in touch. 

     

  • FCA confiscation order demonstrates that insider dealing doesn’t pay

    FCA confiscation order demonstrates that insider dealing doesn’t pay

    Last year the Financial Conduct Authority (FCA) secured a successful conviction against Mr Mohammed Zina for six insider dealing offences that took place between 2014 and 2017. Although the profit from the insider dealing totalled just over £140,000, the confiscation order is for nearly £600,000, thus confiscating the entirety of Mr Zina’s assets.

    The order must be paid within three months, or Mr Zina will face an additional five years in prison on top of the original 22 month sentence. The reason the confiscation order is significantly larger than the trading profits is because the court found Mr Zina ultimately benefited across a number of offences, including fraud.

    Although examples of compelling restitution from firms, issuers and individuals were first heard of in Hong Kong, the FCA has increasingly been keen to use these powers.

    In 2017, Tesco agreed to pay redress to 10,000 investors after giving a false and misleading trading update, which was the first redress order under s384 of FSMA 2000. In addition, in 2020 Redcentric Plc agreed to provide compensation to all net purchasers of shares between Nov 2015 and Nov 2016, having misstated accounting balances.

    Long gone are the days when insider dealing was seen as a ‘victimless crime.’ The focus now is not only on securing convictions, but also on ensuring that those benefitting from insider dealing are forced to compensate innocent investors that were on the other side of the orderbook.

    These are very healthy developments in the ongoing drive to uphold market integrity, maintain confidence in the markets and send a clear message that insider trading or fraud in financial markets won’t be tolerated by the UK regulator.

    Additional Resources:

    If you would like support with your Market Abuse Risk Assessment framework to help prevent issues like insider trading before they occur, please get in touch. 

  • FCA issues its first transaction reporting fine under MiFID II

    FCA issues its first transaction reporting fine under MiFID II

    The FCA has issued its first enforcement notice for a breach of transaction reporting requirements since MiFID II went live in 2018. A UK-based broker was fined just under £100,000 by the FCA for failing to submit more than 46,000 single-stock contracts for difference (CFD) transaction reports between October 2022 and March 2023.

    Why was the firm fined? 

    Firms take note – what is interesting about this fine is that even though the broker had identified its failure to submit the transaction reports following a third-party review, it did not proactively report the breach to the FCA. It was the regulator that independently identified the discrepancy in transaction data.

    The expectation from the FCA is that as soon as firms identify issues with their reporting, they need to let the FCA know via an error and omissions notification. This then demonstrates to the regulator that they have the right systems and controls in place. 

    The value of the fine

    The high-risk nature of single-stock CFDs with regards to potential market abuse, and the firm’s failure to quickly bring the breach to the FCA’s attention, meant that it was initially fined more than £141,000. The broker received a 30% discount on the penalty for early resolution. The FCA initially allocated a value of £2.00 for each of the broker’s missing transaction reports (a step up from the £1.50 amount in the previous final notice from 2019). However because the FCA deemed that the broker had not acted deliberately or recklessly and there was no or little loss or risk of loss to consumers, investors or other market users this was further reduced as per the existing framework.

    Subsequently under step 4 of their determination the FCA concluded that the “absolute value of the penalty is too small in relation to the breach to meet the Authority’s objective of credible deterrence” and hence multiplied the amount by seven, to avoid “firms being tempted to see any fines imposed because of transaction reporting breaches as a cost of doing business.” This is clearly an area of FCA focus. Firms should review their current processes and governance and take note of the regulator’s less conciliatory stance.  

    What is the background to the fine?

    The general temperature of regulatory scrutiny around transaction reporting has been rising recently, and via Market Watch 81 the FCA was clear in its expectations of firms that they needed to improve their transaction reporting controls and review weaknesses in their processes.

    What did the final notice say?

    The FCA highlighted weaknesses in the firm’s change management processes and potentially a lack of subject matter expertise within the brokerage when it established and operated a new line of business in single-stock CFDs. The FCA notes, “it was the responsibility of a single individual…to manually identify which financial instruments were reportable when new business was commenced”.  It also noted that the firm “did not put in place any steps to scrutinise this process or any checks to ensure that the correct trades had been identified as reportable”. This points to a lack of effective reconciliation, which is expected under Article 15, RTS 22 of MiFIR.

    And while a third party review identified that the broker had not reported the transaction data, as mentioned earlier in this blog, the broker did not proactively contact the FCA regarding the breach. The final notice reiterated that the regulator expects to be notified quickly and not just once prompted.

    What does the fine mean for firms?

    This fine should stand as a warning for firms and a stark reminder to act now and review current processes and governance around transaction reporting. It is important to note the change in temperature from the regulator. The FCA is paying close attention to the transaction reports firms are submitting (and not submitting) and expects firms’ systems and controls to be robust where they do identify breaches.

    Our ReportShield™ quality assurance solutions are designed to give firms peace of mind in meeting regulatory expectations on MiFID II transaction reporting. Available on our easy-to-use dashboard, our solutions are unique in testing every single record at source so that all errors including under and over reporting are detected. Through our experienced team of regulatory experts, we can also advise firms on communication with the FCA and other regulators, and provide training on the reporting requirements. Please contact us for a discussion about your reporting challenges. 

  • FCA highlights linkages between market abuse and money laundering, with another Dear CEO letter

    FCA highlights linkages between market abuse and money laundering, with another Dear CEO letter

    The FCA has written to the chief executives of wholesale brokers setting out their new strategy for supervising the sector. In the letter, the FCA cites the inherent risk that wholesale brokers may be used to execute trades that facilitate financial crime.

    The FCA will be conducting targeted work to assess how firms manage their broker employees and control various inherent risks, including insider trading, market abuse and non-financial misconduct, such as bullying and harassment.

    The letter to wholesale brokers specifically references the link between anti-money laundering controls and market abuse, as well as four Market Watch newsletters, including Market Watch 69 which outlines the benefits of having effective surveillance systems in place and a comprehensive, accurate and up-to-date market abuse risk assessment.

    The UK regulator explains the importance of having a good culture to complement a robust control framework and detective and monitoring controls, including “trade and communication surveillance.”  The expectation is that firms receiving the letter should agree actions and next steps by the end of March 2025.

    Also in relation to financial crime and market abuse, the FCA published a paper last week entitled ‘Assessing and reducing the risk of Money Laundering Through the Markets (MLTM)’, which the FCA expects firms to read in full.

    The MLTM paper, which applies to investment firms more broadly, highlights: the advantages of an integrated approach to market abuse and money laundering surveillance; the benefits of trading surveillance alerts being considered alongside KYC and other information; and that Suspicious Activity Reports (SARs) often originate from Trade Surveillance alerts and Suspicious Transaction and Order Reports (STORs).

    Additional Resources:

    To learn more about how Kaizen could help your firm with its Market Abuse Risk Assessment framework, please get in touch. 

  • FCA’s Discussion Paper starts to shape the UK’s Market Abuse Regime for Crypto Assets

    FCA’s Discussion Paper starts to shape the UK’s Market Abuse Regime for Crypto Assets

    Following confirmation from the government last month that it will introduce legislation to bring crypto assets into the FCA’s regulatory perimeter, the UK regulator has published a Discussion Paper (DP) that includes market abuse related considerations.

    The roadmap indicates that a Consultation Paper covering Market Abuse, Admissions and Disclosures will be published in Q3 2025 with the FCA’s Crypto regime scheduled to go live in 2026.

    It’s clear from the DP that the FCA will carefully consider the competitiveness of the UK crypto assets market but it’s also apparent that the proposed Market Abuse Regime for Crypto assets (MARC) intends to reduce the incidence of market abuse, lessen information asymmetries and reduce harm to consumers, thus increasing confidence and market growth.

    The MARC framework approach intends to prevent, detect, and disrupt crypto asset market abuse and help prevent regulatory arbitrage by aligning with global standards, including the IOSCO CDA Recommendations covering Market Abuse, Surveillance and Material Non-Public Information.

    New legislation is expected to require the disclosure of inside information in relation to crypto assets traded on a regulated Crypto Asset Trading Platform (CATP) as well as prohibit insider dealing, the unlawful disclosure of inside information and market manipulation.

    Challenges

    The existing market abuse regime cannot simply be transferred to crypto asset markets, given the highly fragmented and cross-border nature of these markets, issuers being less identifiable, the decentralised price formation processes and greater participation from retail consumers making the surveillance process more difficult.

    However, the fact that the FCA acknowledges these key challenges, coupled with the questions being raised in the DP being so considered and broad, appears to be a positive development for the crypto assets sector and the proposed UK MARC regime.

    Comments on the FCA’s DP must be submitted to the regulator by 14 March 2025.

    Additional Resources:

    To learn more about how Kaizen’s surveillance solution could help your firm comply with global market abuse regulation or for assistance with your market abuse risk assessment, please get in touch. 

  • What’s on the horizon for Securities Financing Transaction (SFT) Reporting in 2025?

    What’s on the horizon for Securities Financing Transaction (SFT) Reporting in 2025?

    Approaching the final act of 2024, the world remains in a perilous place, economic growth is faltering, interest rates have been slow to ease but inflation also remains sticky and prone to energy price shocks. In this environment, money market and securities finance transaction (SFT) reporting moves closer to the top of the Treasury’s and Central Bank’s toolkit as they seek to establish the effectiveness and transmission of monetary policy together with any signs of external factors impacting the order and robustness of broader capital markets.

    New US regimes and SFTR Review

    2024 will draw to a close in the money markets and SFT reporting space with the introduction of daily US Non-Centrally Cleared Bilateral Repo Market reporting to the Office of Financial Research (OFR) for major securities/government bond brokers and dealers, on 2 December. OFR Phase 2 on 1 April 2025 will see reporting expanded to cover ‘Category 2’ major ‘Buyside’ Non-Centrally Cleared Bilateral Repo market participants.

    Elsewhere though, 2025 looks potentially like a year of delays. US securities lending reporting under SEC 10c-1a and administered by FINRA as Rule 6500 SLATE reporting is politically a very hot potato, facing a number of amendments and potential delays with the SEC postponing their approval of the FINRA rule until January, corresponding with Gary Gensler’s departure. Additionally, US trade associations are potentially launching other legal challenges. It might still go ahead on 2 January 2026 though!

    The SFTR Review also appears to be subject to further delay, with no sign of it appearing on the ESMA 2025 schedule of work.

    Where to focus for 2025

    However, while many eyes may be pointing at the shiny new regulations, in practical reality, it’s the seasoned, mature regulatory reporting regimes that compliance officers want to worry about.

    Regulators make allowances for new regulations, they let them bed in and teething troubles are tolerated – not so once a regime has been live for five years.    

    Unfortunately, almost five years in, data quality in the SFTR space continues to let it down. It has perhaps not helped that (new UK validation rules – live on 25 November 2024 aside – which are largely a replay of ESMA’s March 2023 rules), SFTR has been somewhat untouched for an extended period now. The last SFTR Q&A was published in June 2023.

    Of late, we’ve heard anecdotes of new NCAs entering into the fray with challenging questions and investigations following concerted pressure from ESMA and potential signs of a delegated reporting timebomb too. While the SFTR Review may be subject to further delay, regulators such as the UK FCA have been keen to draw our attention to SFTR.

    FCA Market Watch 81 – what does it mean for SFTR?

    Earlier this month, the FCA released Market Watch 81 which primarily focused on MiFID transaction reporting requirements however it made it clear that it would also be of interest to firms subject to UK EMIR and SFTR. 

    The newsletter contains a rich seam of statements that in our anecdotal experience apply equally to SFTR. To let Market Watch do the talking…

    “We continue to identify incomplete and inaccurate transaction reports,” with complaints about issues re-occurring post remediation, poor change management, data governance, control frameworks and oversight.

    Perhaps most poignant of all from an SFTR perspective was the statement:

    “Data quality issues can also emerge where change processes are outsourced to third parties, and there is inadequate oversight over the scope of deliverables. This can be worsened by the absence of transaction reporting subject matter expertise within the firm.”

    Furthermore: “We have identified firms who have excluded services and data provided by third parties from their control and reconciliation framework. This can create gaps in monitoring and prevent firms from identifying issues originating outside the firm.”

    The FCA also stated:

    “Limited compliance oversight over transaction reporting can hinder firms from improving their reporting processes through independent advice and challenge.”

    Of course, a layer of independent quality assurance through regulatory testing (such as our ReportShield Accuracy Testing) would ensure that regulatory reports are subject to a fully independent challenge.

    “Staff turnover and absences can also affect data quality. We have identified data quality issues including failure to report transactions where key staff dependencies exist, and there are not clear policies and procedures to manage reporting in their absence.”

    Again, outsourcing elements of your controls environment and oversight not only helps counteract key person dependencies but also mitigates against any inadequacies in policies, procedures and change management.  

    Don’t rest on your laurels

    Governments and regulators are currently on edge for understandable reasons. Excuses for incomplete or inaccurate reporting of the very regulations (SFTR, EMIR, CFTC etc) implemented in mitigation of the global financial crisis have been exhausted. The onus is now on firms to ensure complete, accurate and timely reporting or start to face the wrath of emboldened regulators across Europe, North America and globally. This is no time for resting on your laurels.  

    Our ReportShield solutions are designed to directly address the controls issued raised in Market Watch 81 – to request a demo or for a conversation with one of our regulatory experts, please get in touch.

  • ASIC and MAS Rewrites go live – what’s changed?

    ASIC and MAS Rewrites go live – what’s changed?

    From today, firms with ASIC and MAS reporting obligations are operating under a new landscape.

    Just like the recent EMIR Refit and CFTC ReWrite before that, both rewrites introduce many changes to align with global harmonisation of G20 derivatives reporting. Congratulations to all industry participants involved in the implementation, which is no mean feat so soon after last month’s UK EMIR Refit go live.

    Let’s recap: what are some of the main changes to both regimes?

    • Mandatory usage of ISO 20022 XML format – the cessation of CSV and FPML formats means firms have had to either build internally or procure the ability to send and receive messages in ISO 20022 XML format from a third party.
    •  A significantly increased data set, due to the addition of new fields – firms have had to interpret these new fields by analysing technical specs and guideline documents to ensure that they are sourcing the right values and where not available, create customised logic to synthetically manufacture the correct values.
    • Adoption of the Unique Product Identifier  – firms have had to incorporate the correct UPI data against reportable transactions for subsequent reporting.

    ACKs and NACKs

    Ideally, the completion of all of this work culminates into reports being successfully accepted by the respective Trade Repository (TR), commonly referred to as an ‘ACK’ message. A high ‘ACK’ rate indicates that the report messages submitted by the reporting firm, successfully conforms to the required standards and schemas and also meets the business validation requirements that prevents non-sensible data (for example, omitting option type details when the derivative is an option).

    Achieving a high ‘ACK’ rate or conversely, low ‘NACKs’ (rejections) is definitely a positive first step towards a successful go-live.

    Is your reporting valid but wrong?

    Unfortunately, the work doesn’t end there because the risk of ‘valid but wrong’ reporting can still exist on a report messages that have been ‘ACK’ed’. The valid but wrong scenario occurs when reports pass the validation rules, but the data within the reports is inaccurate. Validations are often syntax rules that require firms to report their data in the right format. For example, if the value reported in a counterparty field does not contain a valid LEI ie a 20 digit alphanumeric that exists in the GLEIF database. ​

    To stay on the right side of the regulators in Australia and Singapore, firms would be remiss to ignore the need to have adequate controls in place to ensure that submitted reports are an accurate, complete and timely representation of reportable derivatives. Kaizen’s ReportShield solutions provide a completely independent assessment of the quality of your reporting by testing all data fields on all reports, with results available on our easy to use dashboard. 

    To gain confidence in the quality of your reported data (and avoid the valid but wrong scenario), please get in touch for a free healthcheck of your reported ASIC or MAS data.

  • FCA pushing firms to be more intrusive when trading for ‘obfuscated overseas aggregated accounts’

    FCA pushing firms to be more intrusive when trading for ‘obfuscated overseas aggregated accounts’

    Market Watch 80 highlights the potential risks associated with trading for overseas clients who operate aggregated accounts with unknown ultimate beneficial owners (UBOs). While these accounts offer administrative advantages, they can be used to conceal suspicious trading activity and facilitate market abuse.

    The Financial Conduct Authority (FCA) has observed an increase in such activity, particularly in leveraged equity products, and particularly in firms overseas where the regulatory approach to market abuse may not be equivalent to that of the FCA. They have identified instances where FCA authorised firms unknowingly executed trades for individual UBOs who had previously had their own trading accounts terminated due to suspected market abuse.

    To mitigate these risks, the FCA recommends firms take extra precautions when onboarding and dealing with ‘obfuscated overseas aggregated accounts’ (OOAAs). This includes modifying risk frameworks, requiring additional information from OOAAs, and applying robust measures to terminate relationships if necessary.

    Whilst the FCA acknowledges it is harder to detect market abuse when the identity of the underlying client is not known, the regulator recommends and encourages firms to be more intrusive with their clients in these situations.

    Simon Appleton commented:

    “Regulated Investment Exchanges and operators of trading venues have historically questioned the market abuse related controls of member firms. Although the commercial nature of the relationship between firms and their clients is different to that between operators and members of trading venues, the suggestion here is that firms need to be more on the front foot with their clients and be more intrusive in a similar manner to the approach taken by exchanges and their members.”

    Given that it is the responsibility of all investment firms in the execution chain to have effective market abuse related systems and controls in place, these steps are a way of protecting the firm from being used to facilitate insider dealing or market manipulation.

    Additional Resources:

    Read Market Watch 80 in full on the FCA’s website..

    To learn more about how Kaizen’s surveillance solution could help your firm comply with global market abuse regulation or for assistance with your market abuse risk assessment, please get in touch. 

  • ESMA MiFIR Review: Key changes proposed to MiFIR Transaction Reporting (RTS 22)

    ESMA MiFIR Review: Key changes proposed to MiFIR Transaction Reporting (RTS 22)

    ESMA has launched a consultation on Level 2 measures under the MiFIR Review, seeking feedback on transaction data reporting (amended RTS 22) and order book data (amended RTS 24).

    What’s the background to the consultation?

    ESMA published a report in March 2021 on the functioning of the transaction reporting regime under Article 26 of the Markets in Financial Instruments Regulation (MiFIR). This led to a set of legislative proposals included in the review of MiFIR. The final legislative amending text of the ‘MiFIR Review’ was published in the Official Journal of the European Union and entered into force on 28 March this year. This included an updated version of the provisions for transaction reporting (Article 26).

    In this latest regulatory milestone, ESMA is asking for input on its amendments to the regulatory technical standards (RTS) 22, the section of MiFIR which sets out the transaction reporting obligations and reportable fields. The deadline to submit comments is 3 January 2025. We are certain that clients will want to engage with their trade associations and also respond themselves.

    Some of these proposals are far reaching and will be complex to implement. This now feels almost as significant a package of change as the shift from MiFID to MiFID II in 2018.

    From first sight of the initial report through to the publication in the Official Journal, we said that the devil will be in the detail. 

    What are the key changes proposed to RTS 22?

    1. Instrument Scope

    Not a major change but for OTC Derivatives where the underlying is not ToTV or an index made up of instruments that are ToTV then these will only have to be reported if Traded on a Trading Venue unless they are specifically included in Article 8a(2) of the revised MiFIR Text. The consultation includes two diagrams that makes this scope easy to visualise. For firms understanding exactly what is in and out of Article 8a(2) will be the challenge.

    2. Additional Field – Effective Date

    Further details will become clear after consultation but so far for debt instruments, the effective date should be the date when the transaction will be settled and for derivatives it should be the date when the obligation under the contract becomes effective, which may be in the future (forward starting date).

    3. Additional Field – Entity subject to the reporting obligation

    The field will provide added value in the limited instances where the executing and submitting entity differs from the firm with the obligation to report.

    4. TIC or TVTIC, that is the question

    Here is where we start to see significant implementation challenges – the existing challenges of TVTIC will remain i.e. what format and where is the venues “TVTIC” to be found and there is to be more legislation for the extension of “TVTIC” to “negotiated” trades, a new “TIC” for trades executed on Non EEA trading venues. ESMA is also consulting on a proposal for the generation and dissemination of a “TIC” across the entities involved in OTC/XOFF transactions.

    5. Improvements to INTC

    There are proposals to introduce a new identifier to link market side executions to the ultimate fills to multiple clients where a firm aggregates client orders. Fortunately this requirement begins and ends with the executing firm – there is no mention of sharing this code with the clients themselves. So far so good, but ESMA doesn’t stop there.

    6. A new code to link to the same sequence of report chains resulting in the execution of a transaction

    A catchy title with a less than catchy implementation challenge. ESMA proposes to include a new and unique code (Chain Identifier) that is transmitted across all counterparties involved in a chain. All involved parties must make sure to transmit the code to its direct counterparty until the ultimate reporting entity. The introduction of such new identifier would also imply the identification of the primary entity responsible for the creation of the code and responsible for disseminating it. We assume though only to its immediate counterparty.

    The code should be transmitted across the counterparties along with the sequence of confirmations chains. The firm executing the transaction would have the obligation to pass the code down the chain. The firm executing the order should provide a unique code to the client that pertains to the executed transaction that allows the client to produce its own transaction report. Again, more detail will come in the Level 3 (L3) so firms won’t really know what they don’t know until it is completed.

    7. Less complex new asks but more data will be required:

    • Date transactions should be reported – fortunately this is to be a “fixed” date which will be equal to the date of application of the revised RTS 22.  Here ESMA adds further detail “The application date should also ensure sufficient time for implementation, which… should be ideally 12 months from when the technical documentation is available”. Our question is does the “technical documentation” include all Level 3 – as a lot of Level 3 will be required to clarify some of the additional requirements specifically relating to the TIC/Chain and INTC requirements.
    • Additional data to identify indexes, aligns to the benchmark regulation and splits the field into two components.
    • Alignment of Buyer /Seller /Price /Complex trades and packages to EMIR. There is a lot of detail as to the changes required for Buyer/Seller identification for derivative transactions which at least if aligned to EMIR, firms will be able to cross reference interpretation already recently undertaken for EMIR Refit.
    • Inclusion of a DLT identifier in transaction reports for financial instruments that are natively issued on a blockchain and for financial instruments that are re-issued in a tokenised form.
    • Client categorisation.

    There are a number of other changes as to Order Transmission/exclusion of some additional transaction types and some adjustments to field definitions and names, but I leave you with this one hidden in the revised text of the RTS:

    8. No 1st Priority Identifier – No Trade

    “The highest priority identifier shall be obtained by the investment firm from the client/relevant party prior to trading”. This is the MiFIR Review equivalent of ‘No LEI No Trade‘ of 2018. We know firms do and have made significant efforts to capture Level 1 identifiers but have relied on the fall back if they don’t have it. ESMA is proposing to remove that fall back altogether.

    What happens next?

    Following the consultation period, ESMA will publish a final report and submit the draft RTS to the European Commission for adoption in Q1 2025. 

    For Kaizen clients, our ReportShield quality assurance testing will continue on the basis of the current regulations, rules and guidance. We will be following the consultation process closely with our clients and partners and will provide further updates as the changes crystalise in early 2025. 

     

  • High stakes mean compliance monitoring of unauthorised communications required

    High stakes mean compliance monitoring of unauthorised communications required

    A US bank received heavily reduced fines from the US SEC and CFTC for proactively admitting unauthorised channels were used for business-related communications which were neither recorded nor monitored.

    According to the CFTC the bank is the only firm to self-report their recordkeeping and supervisory failures.

    It is not enough to have policies and attestations

    What these fines show is that it is not enough for firms to have a list of approved communication channels that are monitored, subject to review and when appropriate archived.

    It was also not enough that the bank required regular attestations from dealers that they were not using personal text messages and social interactions to engage in business-related communications.

    Compliance monitoring, disciplinary action and enforcement are all key

    It was the failure of the bank to ensure that employees complied with their communications policies and procedures. It was also the failure of the bank to maintain those business-related communications and failing to supervise its business effectively.

    Although approaching employees about the usage of personal devices is a sensitive area, the stakes are so high because their unauthorised usage can undermine the effectiveness of the market abuse regime.

    Given the importance of market integrity and confidence in the financial services sector, the proactive compliance monitoring for breaches of the firm’s communication policy and procedures is key.

    Being clear about the firm’s business-related communications policy, as well as informing employees about the firm’s disciplinary and escalation processes is also essential.

    These controls should already be in place for firms that have conducted and acted upon a comprehensive market abuse risk assessment (MARA). The potential for regulatory enforcement action is high for firms with gaps in their controls.

    Additional Resources:

    CFTC Orders Truist Bank to Pay $3 Million Penalty and Remediate Recordkeeping and Supervision Failures Relating to Widespread Use of Unapproved Communications Methods

    Twenty-Six Firms to Pay More Than $390 Million Combined to Settle SEC’s Charges for Widespread Recordkeeping Failures

    • To learn more about how Kaizen’s communications platform could help your firm comply with global market abuse regulation or for assistance with your market abuse risk assessment, please get in touch. 
  • FCA Market Abuse Surveillance TechSprint – What We Learned

    FCA Market Abuse Surveillance TechSprint – What We Learned

    Last month we were excited to take part in the FCA’s Market Abuse Surveillance TechSprint which brought together industry participants to explore AI-powered solutions to help detect forms of market abuse.

    We asked our Head of Operations for Surveillance Charles Dickson, Data Scientist Josian Quintana-Arroyo, and our subject matter expert Simon Appleton about their experiences taking part in the event and what they learned from it.

    First things first, what was your role in the TechSprint?

    Charles: I was the project manager, coordinating within our team and with the FCA. I ensured our project remained true to the TechSprint objectives whilst providing tangible benefits to our clients. This was done by constantly linking our research back to (i) the presentation and knowledge we would be able to share on the demo day at the FCA, and (ii) the enhancements we could roll out to our clients upon project completion.

    Jos:  My role was technical: data science and machine learning. I investigated the data, engineered variables and applied AI methods to detect market abuse.

    Simon: I provided subject matter expertise covering market abuse, surveillance, MiFIR transaction reporting data and order book data.

    What was the problem we were given to explore? Were we successful with our approach?

    Charles:  We chose to explore how to ‘transform market abuse surveillance by incorporating anomaly detection’. This is because we had an existing research project in this area which would allow us to immediately start applying these ideas to the vast datasets which the FCA helpfully gave TechSprint participants access to. In our case, given Kaizen’s rich history and deep knowledge in transaction reporting, it was that dataset we were most interested in.

    Jos: There was success showing our approach was correct although further work is being carried out. This is because detecting market abuse is a complex process that requires a lot of analysis and consensus. There were some false positives. The variables we engineered were relevant and our approach showed results consistent with other datasets which is how we knew we were on the right track.  However, many of the potential anomalies flagged required further investigation. This ‘further investigation’ aspect of product development is a critical part of developing a meaningful algorithm.

    Simon: It was clear that our data scientists, programmers and product development staff benefitted from having access to an extensive and broad dataset covering transaction reports, orders and prices. We also further advanced our understanding and usage of AI in the anomaly detection process.

    What was your biggest learning from taking part in the TechSprint? Do you have any advice for individuals and firms taking part in future events?

    Charles: Thanks to AI, we have a rapidly improving toolset available to us. It is our responsibility to apply these with careful thought and discretion so that the resulting output is explainable and defensible, both for clients and regulators. With the vast options available, it is best to have a targeted approach to return specific answers rather than generating an exponentially growing set of questions. To get these answers implemented with clients, you need to prove additive value to existing rules-based monitoring – reduced false positives with better true positive detection, allowing compliance officers to concentrate more of their time investigating breaches and near-misses.

    Jos: We learned a lot from engineering a model with so much data. We also had the chance to refine our current algorithms as all the fresh data allowed us to shed light on our own work: for example, we reconsidered the importance of two variables that we currently use. Having to explain our findings to an audience also made me think of the problem from a different point of view and I am now testing the same models with a simpler approach which will make them more easily interpretable.

    My advice to others would be to move fast and come up with end-to-end solutions and improve them later, time feels a lot shorter when having to handle so much data. Also to be honest with yourself about the results if they are not as good as expected, there is a lot to learn from what doesn’t work as intended.

    Simon: Although obvious, the importance of having data scientists, programmers, product and market abuse surveillance experts working well together and learning from each other made it exciting and resulted in a positive atmosphere and outcome. Selecting people with the relevant, complementary skills, knowledge and a collaborative approach would be my main suggestion.

    Along with our TechSprint participation, we recently announced we are introducing a new AI powered voice transcription functionality on our communications surveillance platform. What is your advice for firms when assessing AI powered tools?

    Charles: Firms should run AI powered tools in parallel with conventional processes to ensure they are achieving at least the same effectiveness before migrating fully to AI. This would involve a multi-month period with in-depth comparison and human feedback. Categories for assessment would include transparency, defensibility, effectiveness, efficiency, and synergies to other monitoring processes.

    Jos: Some tools are very easy but expensive to implement especially when scaling up. Some more rudimentary approaches are effective albeit more difficult to implement, and they will be worth the saving in costs. Be realistic and well informed about what the latest technology can and cannot do. Some tools can improve performance even if they don’t do the work for you; they could still be valuable.

    Simon: Given that this is a fast-moving environment, keeping your options open, opting for shorter contract periods and selecting a provider that has hedged their bets, rather than opting for a single solution.

  • Insider dealing related STORs back into pole position in Europe

    Insider dealing related STORs back into pole position in Europe

    ESMA’s recent report relating to Suspicious Transaction and Order Reports (STORs) provides the market with an overview of their use in different EU countries.

    STORs are an important tool for NCAs to detect, monitor and investigate practices relating to market abuse. MAR requires firms or individuals to report orders and transactions that could constitute insider dealing, market manipulation or attempted insider dealing or market manipulation to the NCA of the trading venue.

    In earlier ESMA reports it was evident that Brexit had a significant impact on the STOR related statistics. This report focusses on STORs received during 2023 and although the conclusion is that the figures are consistent compared with the previous years, there are several interesting observations, including:  

    • the total number of STORs submitted rose by 12% to 6,530, compared to 5,833 in 2022
    • Germany again submitted the most by raising 33% of the total but this was down from 42% last time with German investment firms submitting 3% fewer STORs than in 2022
    • Sweden, a country that prides itself on the quality of its market abuse surveillance, submitted the third highest number of STORs, with 9% of the total and significantly more than many other countries. The number of STORs solely from investment firms in Sweden was up 3% on 2022
    • the ratio of notifications by trading venues (10%) and investment firms (77%)
    • the percentage of STORs by instrument type remained stable with shares accounting for 85%, bonds 7% and derivatives 5%.

    Insider dealing vs market manipulation

    One of the interesting aspects of the report is seeing that more STORs now relate to insider dealing than market manipulation. Although this was always historically the case, the opposite has been true during recent years.

    Insider dealing related STORs accounted for 51% in 2023, up from 45% of the total in 2021 and 44% in 2022. Whereas alleged market manipulation accounted for 47% in 2023, down from 52% of the total for the previous four years.

    Although this annual report from ESMA excludes STORs received by the UK’s FCA, it still highlights some interesting trends. It is too early to say whether the increase in STORs relating to insider dealing is a sign that firms are becoming more sophisticated in their approach towards surveillance, including electronic communications surveillance.

    • For a conversation with Simon about your market surveillance challenges or a demo of our integrated trade and communications surveillance system, please get in touch. 

     

  • Market abuse risks for the buy-side not limited to insider dealing

    Market abuse risks for the buy-side not limited to insider dealing

    At a recent market abuse event it became obvious that the general feeling in the room was that market manipulation risks are not the primary concern for many asset managers. Although insider dealing was seen as the main market abuse risk for buy-side firms, the risk of market manipulation should be treated just as seriously.

    Ability to manipulate prices

    Buy-side firms have historically been seen as users of markets but over the last few years they have increasingly been able to directly impact the price formation process and, with it, the potential to create a false and misleading impression of trading interest.

    A significant percentage of asset managers are now direct market participants on trading venues, mainly multi-lateral trading facilities but some regulated markets too. In addition, with the advent of direct electronic access, asset managers can directly route orders to a wide variety of markets, including via the use of algorithmic trading.

    The ability to manipulate prices can also come through the usage of non-binding Indications of Interest (IOI) messages, misuse of Request for Quote functionality, conditional orders and “off-venue crosses” and so, it becomes clear that the risk of market manipulation exists quite broadly at inherent level. Lastly, the ability to release false and misleading news is there for any market user.

    Motivation

    Where clients and funds sit on large positions (long or short) there can be a heightened focus on whether the positions are showing a paper profit or loss, and this focus can intensify on key dates and at year end.

    Market manipulation at year end

    An interesting market abuse case involved Stefan Chaligné, a fund manager, and Patrick Sejean, a trader, who bought shares minutes before Chaligné’s lviron Fund was to be valued. The value of the fund was artificially inflated and Chaligné’s performance fee boosted by more than £260,000.

    Sejean emailed the following to an unnamed colleague shortly after speaking to Chaligné: “Please buy in the last hour of trading …The goal is to put each stock price as high as possible at the close, so if you want you can buy most of the volume at the close.”

    The purchase of shares on New Year’s Eve resulted in a 2.9% uplift in the value of the £70m fund at year end. The UK’s regulator fined Mr Chaligné (the fund manager) £900,000 plus €362,950 disgorgement of benefit (profits gained from the manipulation). Lastly, the fund manager was deemed not a fit and proper person and was banned from performing any regulated activity.

    Although this case, from 2013, highlights the importance of trade and communications surveillance, importantly, the fund manager could now independently use direct electronic access to transmit orders directly to the market.

    Market abuse risk assessments

    While it’s impossible to eliminate all risks, some market manipulation risks can be reduced through using centralised dealing desks and having a robust market abuse control framework in place.

    Conducting up-to-date and periodic market abuse risk assessments will help a firm identify the risks and ultimately help mitigate them where possible.  It also demonstrates to internal audit and risk management teams, as well as regulators that a firm has the correct risk assessment policies and procedures in place and is doing all it can to reduce the risk of the firm committing or facilitating market abuse.

  • Money Market Statistical Reporting (MMSR) regime expansion goes live

    Money Market Statistical Reporting (MMSR) regime expansion goes live

    As of July 1, 2024, the European Central Bank (ECB) has implemented revised guidelines for Money Markets Statistical Reporting (MMSR). Twenty-four new firms, including some of the world’s largest and global systemically important banks (G-SIBs), are joining the 46 that are already navigating MMSR, bringing the total to 70 entities. Post-Brexit, these institutions have become key players in the EU money markets, making their inclusion essential.

    Why MMSR matters

    MMSR is crucial in providing data on daily money market transactions. This isn’t just about ticking regulatory boxes – this is about giving the ECB the insights it needs to steer the Eurozone economy through monetary policy. Secured and unsecured transactions, foreign exchange swaps, overnight index swaps (OIS) – the ECB relies on this granular data to make decisions that impact us all.

    What are the consequence of getting it wrong?

    The ECB expects accuracy, promptness, and transparency. If firms don’t comply, the consequences can be severe – hefty fines can be imposed (as much as 10% of a bank’s total annual turnover) and there can be reputational damage too. Inaccurate reporting can ripple out, leading to flawed policy decisions that affect the entire economy. The ECB’s data quality checks ensure that firms maintain high standards, but the responsibility ultimately lies with the reporting firms.

    What errors do we find?

    At Kaizen, our testing of the accuracy of MMSR data has uncovered common issues such as incorrect rates, misinterpretation between collateral nominal and transaction nominal, inaccurate haircuts, misreported execution times, and variations in FX forward points and OIS rates. These errors can stem from manual mistakes, system glitches, or misinterpretations of the guidelines. Identifying and correcting these issues is essential for maintaining the integrity of MMSR data.

    Are you ready?

    The inclusion of 24 new firms into the MMSR fold is a significant development. The enhanced dataset arising from the additional firms’ reporting will offer a richer, more diverse view of the market but also ramps up the pressure on firms to deliver good quality reports. For new reporting agents, this means upgrading systems, implementing new validation processes, and ensuring staff are up to speed.

    At Kaizen, our ReportShield™ quality assurance services are designed to help you navigate these changes. Combining the deep expertise of our regulatory experts with advanced technology, our solutions provide robust controls, continuous independent testing, and validation of submitted data. We leave no stone unturned, meticulously testing every data field on every report.

    Final thoughts

    Today marks a new era in MMSR reporting. The revised guidelines present challenges and opportunities for firms.  The expanded scope necessitates a renewed focus on data quality and firms’ control frameworks to ensure they are meeting the new requirements.

    Additional insights 

  • Three top tips for implementing regulatory reporting rewrites

    Three top tips for implementing regulatory reporting rewrites

    Implementing regulatory change projects is never a straightforward journey and although the list of tasks may seem never ending, it can sometimes benefit a firm to pause and assess how their implementation is going. A key area of focus can be how the current project integrates new information. We have seen numerous examples of this in the past few months. In March, ASIC scoped in seven additional data elements from CP361. In May, MAS finalised its OTC derivatives reporting regulations which contained differences from its original consultation and more recently published its FAQ and Guidelines.  

    If this process is left unchecked, this can often derail project delivery and risk regulatory breach. 

    Here are our top three tips to thrive in this environment.

    1. Monitor ongoing changes

    Although regulators have provided the core requirements on rewrites, firms still need to remain attentive to any late changes. This can be achieved by connecting with industry working groups, trade associations and signing up for notifications at respective NCA websites. However, attending the meetings and analysing all of the variable outcomes from industry discussions can be time consuming. Committing adequate resources to this task will enable a firm to gather and evaluate new information prior to translating them into new requirements where necessary.

    1. A consistent approach

    Whenever new requirements do surface, firms are forced to decide whether to include or exclude for go live. Choosing to delay means firms go live with a reporting process that contravenes the rules. Conversely, adding new requirements midway can also jeopardise the final delivery. When any decision could lead to potentially undesirable outcomes, it’s the criteria rather than the decision that increases in importance. There can be many ways of doing this, ie. trading volumes, field materiality, IT effort, source system dependencies or anything else a firm feels appropriate. Whatever that may be, applying this framework consistently will help with prioritising work in line with a firm’s risk appetite within the context of regulatory reporting.

    1. Spotlight the issues

    Design a project status dashboard that provides transparency on how new requirements impact project deliverables. When issues do arise, make them stand out within the project status summaries so that project stakeholders automatically give their attention to the most pressing issues. This allows them to quickly identify situations that may require intervention or escalation to senior management. The key here is that the issues are effectively disseminated to the people that are empowered to make key decisions in relation to resourcing or even approving a risk accepted strategy.

    The bottom line is that firms have a clear go live date and there is always new information that needs to be evaluated. Firms that have a strategy to evaluate changes consistently will allow new issues to quickly come to light and remedied in time for go live. This can only increase their chances of success in achieving regulatory compliance at go live.  

    To find out more about how we can help you prepare for the upcoming UK EMIR Refit, MAS or ASIC ReWrites, please get in touch.

  • US OFR bilateral uncleared repo reporting – playing catch-up or saving the greatest till last?

    US OFR bilateral uncleared repo reporting – playing catch-up or saving the greatest till last?

    The market has been taken by surprise by the 2 December 2024 go live date for the new OFR Bilateral Uncleared Repo Reporting regime. Earlier this month, the OFR (Office of Financial Research) of the US Treasury adopted the non-centrally cleared bilateral repo (NCCBR) final rule.

    Largest segment of the US repo market comes under scrutiny

    In the headline of this blog, I say ‘the greatest’ because at $US2 trillion outstanding commitments per day, this is the largest of the four segments of the US repo market and by extension, the US SFT market overall as well. It is also the second biggest single SFT market in the world (after the EU bilateral uncleared repo market). Despite its size, this market remains rather opaque, something that the OFR is finally looking to address.  

    While the activities in the US cleared repo and triparty repo markets are already captured by US regulators, the securities lending market (where reporting commences in 2026) and non-centrally cleared bilateral repo (NCCBR) markets remain under-scrutinised. This became a particular concern following the spike in repo rates that occurred in September 2019 and also in relation to the sharp drop in US Treasury prices and further spike in repo rates in March 2020. US regulators continue to harbour major concerns about collateral risks given the prevalence of lower quality non-Fedwire eligible collateral. They are also concerned about the amount of cash borrowing the uncleared bilateral markets offer to highly leveraged entities such as hedge funds.        

    Background to the final rule

    The OFR is wasting no time in closing out this gap, albeit more than nine years after the seminal Financial Stability Board (FSB) paper ‘Standards and Processes for Global Securities Financing Data Collection and Aggregation‘, and four and a half years after SFTR go-live in Europe.

    We had a pilot reporting exercise from the OFR in June 2022, followed by the publication of proposed rulemaking for the collection of NCCBR data in January 2023 and a 60 day consultation ending in March 2023 – then radio-silence!  Then on 6 May 2024, the OFR published the final rule along with reporting instructions, technical guidance and a fact sheet on reporting. 

    Shock announcement 

    Taking the market by surprise, they have sprung a 2 December 2024 reporting go-live date upon us (150 days after the effective date of 5 July 2024) for ‘Category 1’ covered reporters. These include securities brokers, securities dealers, government securities brokers and government securities dealers with outstanding commitments to borrow cash and extend guarantees in NCCBR transactions with counterparties every business day during the prior quarter of $US10 billion. This captures approximately 40 firms.

    Category 2 reporters are required to comply 120 days later from 1 April 2025. Category 2 reporters comprise of any financial companies that are not securities or government securities brokers or dealers with over $US1 billion in assets or under management whose average daily commitments in NCCBR transactions are over $US10 billion in each of the business days in the prior calendar quarter. Category 2 will routinely capture relatively few firms but nevertheless, those potentially coming into scope will be expected to re-test themselves for eligibility each quarter.

    Reporting requirements 

    The very aggressive deadline aside, surveying the reporting itself, it looks eminently sensible.  It is essentially daily repo position reporting of all new transactions, existing transactions that remain open and any transactions opened and closed on the same business day.       

    What’s in scope?

    The scope will include bilateral uncleared repos under (but not limited to) Master Repurchase Agreements (MRA), Global Master Repurchase Agreements (GMRA) or transactions subject to the provisions of 11 U.S.C. 559. Following the consultation regarding the proposed rule, sell/buy-back transactions have also been brought into scope. However, transactions under Securities Lending Agreements (SLA), Master Securities Lending Agreements (MSLA) or Global Master Securities lending Agreements (GMSLA) not considered as repurchase agreements, are expressly out of scope, acknowledging that these will be captured imminently under the FINRA SLATE regime under the SEC 10c-1a regulation. Repos associated with the execution of commercial mortgage loans or the initial securitisation of a residential mortgage loan are also out of scope.    

    Reports comprise 32 fields

    Reporting comprises of 32 data fields by 11am on Trade Date +1 (T+1) Eastern time, following a trading day that runs from 6pm on T-1 to 6pm on T. Reporting shuns the needless complexity of ISO 20022 XML for more human-readable TXT or CSV, to be submitted to the OFR’s Data Collection Utility (DCU). The only lifecycle / action type required is the need to requirement to resubmit a day’s complete submission should OFR enquiries result in the identification of an error.

    Maybe all SFT reporting should be like this! The ability for regulators to survey the latest activities and current SFT position of firms on a daily basis without the need for a complex set of reportable actions, data tables and in excess of 100 fields seems admirable. The only notable limitation may be the lack of availability of collateral reuse data.      

    If you are concerned about your reporting obligations under the OFR’s Uncleared Bilateral Repo Reporting requirements, FINRA ‘SLATE’ SEC 10c-1 for securities lending, or other global money market reporting obligations generally, please get in touch.

     

  • FCA expects robust and increasingly sophisticated market abuse surveillance controls

    FCA expects robust and increasingly sophisticated market abuse surveillance controls

    In Market Watch 79, the UK’s Financial Conduct Authority (FCA) has shared its observations concerning failures of market abuse surveillance at authorised firms, and observations stemming from their peer review of firms’ testing of front-running surveillance.

    Failures of market abuse surveillance were frequently caused by the faulty implementation of surveillance systems, poor change management controls that introduced errors, and missing necessary information feeds, such as trade or order data for certain business flows.

    The impact of these failures meant that certain business flows were not monitored and that alerts were either partially or wholly ineffective due to inadequate testing. The length of time it took firms to identify and fix these failings ranged between a few weeks or less to two years or more. Coincidentally, a firm in the US was recently fined $350 million as a sub-set of trading and order data had not been feeding into their surveillance platforms, as outlined here.

    The FCA observed that one firm had not activated a news feed to facilitate the identification of insider dealing, a failure found only after contact from FCA. Separately, the poor design and setting of a firm’s insider dealing alert parameters, led to potentially suspicious activity going undetected for several years.

    In a separate review, the FCA looked at the frequency and methods used by several large investment firms to test the effectiveness of their client order front running models. Some firms had no formal process covering this, whereas some focused their reviews too heavily on parameter calibration. The FCA cites factors to consider, including the type of financial instrument, the market participants involved, trading methods and trading venues accessed.

    Finally, the FCA helpfully lists the steps firms should take to help prevent surveillance failures, including:

    • Ensuring all relevant trade and order data is accurate and captured
    • Having comprehensive governance arrangements as well as documentation covering testing
    • Appropriate tailoring of alert models and testing by second line and internal audit
    • Having processes to proactively guard against surveillance failures

    It’s clear that the FCA is increasingly stressing the importance of having effective market abuse surveillance by conducting deep dive, thematic and peer reviews and identifying weaknesses in the controls at firms.

    The UK regulator is pushing the boundaries further than before by highlighting that their expectations, and what they see as best practice, are becoming more advanced and sophisticated.

    Given the profound consequences for firms getting this wrong, the FCA is encouraging firms to review the observations in their latest MarketWatch newsletter and consider the adequacy of their arrangements.

    At Kaizen, our proprietary surveillance solutions provide trade and communications monitoring on one system to help middle office and compliance teams comply with market abuse regulations and detect spoofing, layering and other forms of market manipulation.

    • For a free demo of our surveillance solutions, please contact us.
    • Read the MarketWatch newsletter in full on the FCA’s website.
  • SEC Rule10c-1 and FINRA’s Securities Lending Transparency Engine (SLATE)

    SEC Rule10c-1 and FINRA’s Securities Lending Transparency Engine (SLATE)

    Securities Loan? Put it on the SLATE

    The Financial Industry Regulatory Authority (FINRA) published a proposed rule change to adopt the FINRA Rule 6500 Series (Securities Lending and Transparency Engine) ‘SLATE’ on 1 May 2024.

    US Securities Lending Reporting Takes Shape

    SLATE proposals take the SEC’s Final Rule 10c-1a of 13 October 2023 and start to map out what the securities lending transparency regime will look like in the USA once it goes live on 2 January 2026 (assuming no delay by the SEC). This in turn will lead to the publication of individual loan and aggregated securities lending data by FINRA from 2 April 2026. The FINRA rule is subject to a consultation, albeit scheduled to end on 28 May – a mere 21 days after its appearance in the Federal Register. At this stage, we have quite a detailed text outline but no schemas, validation rules or exacting field specifications.

    Requirements for Trade Reporting ++

    The industry has been somewhat surprised by the proposed rule. What first appeared ahead of the FINRA announcement to be simple trade reporting of approximately 12 data elements is shaping up to be a great deal more complex and expensive to implement and report under. This is end of day transaction and lifecycle reporting (on T) by the lender or their agent and subsequent significant loan transparency on T+1. 

    Elements of the scope remain TBC

    The exact scope, potential extra-territoriality and potential dual reporting (to FINRA and the OFR) remain somewhat uncertain. FINRA have identified 609 ‘Covered persons’ who will need to register and report to SLATE, broken down as 434 persons effecting a loan as lender without intermediary, 34 broker dealers borrowing excess margin securities, 4 broker dealer intermediaries, 31 non-broker intermediaries, 97 broker dealers acting as reporting agents and 9 clearing agencies acting as reporting agents. There is no further detail as to who they are or how they came to this estimate.

    Devil will be in the detail regarding reporting taxonomy

    The reporting requirements break down into around 15 public data fields, together with confidential fields relating to identifiers for parties to the loan, indications where securities are sourced from broker/dealer inventory and whether the loan is being used to close out a fail. Depending upon how you count them, we can see effectively up to 45 reportable fields.

    It is the conditional fields (referred to as modifiers and identifiers), full disclosure of all lifecycle events with sequencing, the need to report all modifications (changes and terminations) and the requirement to ingest FINRA generated unique trade identifiers (UTI) and reuse them for all subsequent lifecycle reporting that ramp up the complexity.

    Same day reporting

    Unfortunately for “covered person” reporters, FINRA requires not only the end of day snapshot of any modification but individual reports for each and every change to the terms of the transaction. All by 8pm ET on trade date (if ‘effected’ by 7:45pm ET).

    The modifiers and identifiers required are: Exclusive Arrangements (the lender has with a borrower or intermediary), Loan to Affiliate, Unsettled Loan, Terminated Loan and Rate or Fee Adjustment. To an SFTR veteran, these have the look and feel of counterparty fields in the case of the first two, an error action type (where the loan ultimately wasn’t good), a termination report and a modification of the rebate rate field or lending fee field. It may make the reporting more intuitive to frame these as optional fields (where applicable) and action types (new, modify, error or terminate) or similar, rather than “modifiers and identifiers.”

    Security Lending Data Published T+1

    The public data will be shared by FINRA during the morning of T+1 (excluding the loan amount) at both the individual loan level and in the form of daily loan statistics (e.g. aggregate loan activity and the distribution of loan rates). This data will incorporate both new loans and loan modifications. On T+20, loan amounts will also be shared. This data will be on the FINRA website free of charge for personal, non-commercial use only. For other uses, FINRA will require fees to obtain SLATE data.   

    Reporting requirements exceed remit and could jeopardize effective transparency

    The Financial Stability Board’s (FSB) 2015 proposals around securities financing data collection globally generally were to focus on periodic, settled, position level reporting. The primary objective here (and the substance behind the majority of the c.2000 consultation responses received by the SEC) was to provide greater retail level transparency around the securities lending market and how this market in turn facilitates short sellers in the US equity market. By insisting on pre-settlement trade level data, every modification, incorporating loans that never actually conclude and the modifiers and identifiers (rather than simply excluding biased data from the daily tape) runs the risk of blinding the public with science rather than in providing an invaluable level playing field of transparency with enhanced competition.

    If you are concerned about your reporting obligations under SEC 10c-1, the OFR’s Uncleared Bilateral Repo Reporting requirements or other global money market reporting obligations generally, please get in touch.

  • EMIR Refit implications for the SFTR Review

    EMIR Refit implications for the SFTR Review

    With the go live of EMIR Refit this week, ESMA’s attentions will surely turn next to what to do about SFTR. Next year, SFTR will be five years post-implementation and it will be time for the delayed SFTR Review to commence.

    Having studied the EMIR Refit, it’s apparent that quite a few of the changes were piloted by the SFTR introduction in 2020. Lessons learned by ESMA from the original EMIR regulation and implementation subsequently fed through to SFTR. And it seems likely that many of the developments rolled out in the EMIR Refit will find their way into the SFTR Review.

    Opposite directions

    As a bit of an EMIR outsider, it’s somewhat alarming the extent to which EU regulation and the industry dynamic are moving in opposite directions. The industry is focused on adopting standards, the Regulatory Oversight Committee’s (ROC) common data elements, common booking models, common domain models (CDM), simplification and far greater automation through machine reading and blockchain. CDMs focus on non-proprietary, non-licensed fundamental transaction, position and lifecycle data, an approach that is about achieving fully matched, perfectly replicable trade data with relatively few fields and no complications. CDMs should in theory dramatically reduce the number of manual touchpoints on any trade, significantly reducing operational costs.

    However EU regulators are looking for more data, extensive embellishment and enrichment, to not only achieve a truly forensic analysis of a firm’s balance sheet, processes and operations, but also to negate the need for them to hold any reference or static data at all. Indeed, thinking that 155 fields for SFTR was a lot, we now face up to 203 fields under EMIR Refit (a 65% increase on the original). There are ‘just’ 110 common data elements listed by the ROC…

    Which EMIR Refit elements are likely to be incorporated into the SFTR Review?

    • Bilateral variation margin reporting. Back in 2016 at the Paris hearings on SFTR technical standards, I suggested that there be a separate table to report bilateral variation margins for repo transactions, as ESMA insisted that Table 3, the Margin Table, was exclusively for CCP margins. This motion wasn’t carried and consequently, it is evident that SFTR bilateral variation margin reporting is currently flawed and frequently underreported. The approach required under SFTR v1 of providing trade level collateral updates with UTIs and bilateral variation margin collateral updates without UTIs does not appear to ever have been fully understood. Therefore, the EMIR Refit change that incorporates both CCP margins together with bilateral variation margining in the same margin table would be a welcome step forward, removing confusion and enhancing regulatory certainty.
    • Executing Agent field. The introduction of an executing agent field (as per EMIR Refit) would also significantly enhance the trade repository reconciliation process, particularly when reporting or facing funds as one of the counterparties. This should mitigate current misreporting, where the agent lender or broker fields are often misused to represent fund managers.
    • Intra-group trade identifier. Another party to the transaction field that may carry from EMIR is an Intra-group trade identifier. This omission was something highlighted in the recent ESMA Market Report on EU Securities Financing Transactions Markets 2024. While not strictly necessary (intra-group entities can be identified by their LEI), it would further reduce the burden on regulators to establish this relationship themselves. 
    • Waterfall guidance on UTI. EMIR Refit was written post-Brexit and consequently, they have taken account of the fact that many transactions in Europe today are single sided, being cross-jurisdictional. Therefore, there is a new waterfall providing guidance about responsibility to generate and share unique transaction identifiers (UTIs) when trading across borders. This measure should reduce late reporting (where there is uncertainty about UTI generation and sharing and consequently late reporting) and again provide clearer direction and certainty for reporting counterparties.   
    • Effective dates are another EMIR Refit feature that are likely to benefit SFTR.  At present the need to delay reports until agreed contractual modifications take effect certainly presents a timing challenge to complete and accurate reporting. The revive action type (allowing the reopening of matured or terminated/cancelled by mistake trades) may also be broadly welcomed, aiding in dealing with trades failing over their maturity date/end date for example.
    • Additional EMIR Refit changes that are likely to be mooted include event types complementing certain action types, package identifiers (useful for identifying products such as collateral swaps) and the requirement to report the nature and corporate sector of the other counterparty in addition to the reporting counterparty.

    There is no better way to prepare for SFTR 2 than to get your house in order for SFTR 1. For help addressing your SFTR data quality concerns, please get in touch.

  • ESMA Data Quality Report 2023: What does it say about EMIR?

    ESMA Data Quality Report 2023: What does it say about EMIR?

    As well as seeing the much discussed EMIR Refit, 2024 also marks 10 years of EMIR reporting. That’s 10 years of submissions, rejections, errors, omissions, reconciliations, assurance checks, process improvements, revised rules, webinars, seminars, conferences etc. 

    As a general trend, Kaizen has seen (and helped facilitate) the improvement of reporting data quality, via assurance controls, improving industry understanding, checks and balances implemented, explanatory guidance and improvements to the validation rules. Yet this year’s 2023 Report on the Quality and Use of Data (DQR) focuses on the most basic of data quality concepts that firms should easily adhere to by now, accompanied with equally lacklustre expectations for meeting those reporting requirements. Whilst Kaizen are supportive of the DQR findings, we feel ESMA could have gone further.

    Data quality indicators 

    Many EMIR reporting firms will find this year’s DQR useful, as ESMA includes a reasonable range of data quality issues under scrutiny such as large notional amounts, incorrect maturity dates, mismatch of trades and positions between counterparties, and even late or missing valuations. Helpfully ESMA has also included a description of its implemented 19 Data Quality Indicators (DQIs) in Appendix 6.1.1, although reporting counterparties would greatly benefit from a little more granularity to quantify the empirical checks used, but for now, this is a good start.

    The DQR provides useful descriptions and examples of how EMIR reporting is used in practice by national competent authorities (NCAs) as shown in Section 3. ESMA describes how the data influences a wide range of policy decisions, interestingly many of which differ from its original intended use of monitoring risk and derivative exposure. Critics that still question the benefits of EMIR reporting may take comfort in the non-exhaustive list of documents in Appendix 6.3 which show ways in which the derivative data is used.

    Reconciliation issues

    Firms should however not take comfort in the differing volume of outstanding transactions between counterparties. This notion of the number of open transactions between the two counterparties to the trade, is very basic, and after 10 years, firms should be getting this right. Reporting firms should have suitable reconciliations in place to monitor and remediate both the execution of derivatives vs those reported and to monitor the Inter-TR reconciliation reports, which highlights such discrepancies. The same can be said for position level submissions reported differences between counterparties. The submission of derivatives and agreement of how many trades or positions are to be reported is arguably the most basic part at the very origin of a firm’s reporting journey. Market participants, reporting vendors and ESMA (with regulatory oversight) should expect more, namely that firms are far more able to report matched reports to a trade repository.

    Valuations and collateral

    Valuations and collateral continue to be a data quality theme, as seen in all previous DQR iterations. ESMA notes a positive reduction in late and missing valuations, but again, such an improvement on a very basic aspect of EMIR reporting should not be applauded, but expected to be held at a higher standard to ensure the completeness, accuracy and usability of reported data. ESMA and NCAs should be asking why, after 10 years, can the simple notion of “daily valuation updates” not be easily achieved?  In previous years, ESMA used a 15-day calculation as an indication of late valuations in order to judge the change in data quality, rather than calculate using true daily updates required, and it would be useful to have a little more calculation transparency here too.

    Maturity dates

    ESMA comments on the issue of abnormal maturity dates, which admittedly is a little more advanced than some of the other data quality issues described. For maturity dates, the findings are not quite so favourable, as the abnormal maturities are not falling at a rapid rate, indicating data quality is not correspondingly rising for this statistic. ESMA does however miss a useful opportunity to mention EMIR reporting’s confusing notion of ‘optional fields’, of which ‘maturity date’ is one such example. Optional fields do not mean the reporter has a choice to complete that field, but that the field should be populated where relevant to the derivative executed. Optional fields are often (incorrectly) chosen not to be reported, and cause confusion over the true requirements of an already complicated reporting regime. Notably, ESMA also apportions blame for the notional values differences and number of trades outstanding between clearing members and CCPs on to this maturity date field on page 17.

    Great expectations

    The DQR describes overall NCA activity and targets of data quality discrepancies over the last 12 months. Unfortunately, expected standards are not necessarily shown to be any more rigorous.  For example, ESMA explains that when NCAs addressed with firms, only 34 of 163 identified issues were resolved. Then, to add insult to injury, of 116 issues not resolved, ESMA describes ‘substantial improvement’ in 15% of issues. Both statistics seem pretty mediocre, notably when, these are issues being actively chased by the regulators.

    Such statistics erode confidence and motivation of market participants to pursue a high standard of data quality. However with the introduction of the EMIR Refit, firms can expect this to change and will see a much higher level of scrutiny for their EMIR reporting going forward.  

    Over and under reporting

    And finally, another reoccurring theme is the issue of over and under reporting when trade repositories relay reported data to ESMA. Whilst ESMA acknowledges this is a key issue, such occurrences must be stamped out. Market participants spend a huge amount of time, money and other resources to report these required derivatives, and as a minimum should have confidence that the reports will be routed correctly, according to agreed reporting mandates.

    What’s next?

    Overall, the detail included in the latest DQR is most welcome, and shows whilst there are some data quality improvements, such improvements have only been seen on the most basic of reporting requirements. As we head into year 11 of EMIR reporting and get to grips with the wholesale change under EMIR Refit, market participants should expect a high level of data quality scrutiny to be analysed, commented on and enforced by those with regulatory oversight.

    • Read our analysis of the MiFIR aspect of the report from Matthew Vincent or the SFTR angle from Jonathan Lee.
    • EU EMIR Refit is now live.  But is your reporting accurate? For an independent, forensic review of your firm’s new EMIR reporting, please get in touch.
  • ESMA Data Quality Report 2023: What does it say about SFTR?

    ESMA Data Quality Report 2023: What does it say about SFTR?

    ESMA published its 2023 Report on the Quality and Use of Data earlier this month. In this blog, we focus on the SFTR elements of the report and we also look at another ESMA report published the same week, the ESMA Market Report: EU Securities Financing Transactions Markets 2024.

    The week of 8 April 2024 was an embarrassment of riches in the world of SFTR with not one but two reports relating to securities financing transactions regulation reporting, each highlighting serious issues with reporting data quality. 

    SFTR ‘severe misreporting’ – fine?

    Not once, not twice, but on three consecutive occasions, ESMA has raised the botheration of “severe misreporting” through a failure to close out outstanding securities loans through either modification of the open term field to false and addition of a maturity date/end date or booking of an early termination. This overreporting significantly distorts the regulator’s view of the SFT market and its ability to monitor and tackle genuine systemically significant issues or clear cases of market manipulation and abuse.

    In the 2021 Data Quality Report, it was noted that the value of open SFTs was constantly increasing until November 2021 when an NCA took action against one counterparty that saw them book backloaded early terminations. The outstanding number of open SFT reports more than halved from c.7.5 million to <3 million by December 2021. This also resulted in a notable drop in the proportion of open SFTs made up by SLEBs from as much as c.85% down to c.65% between October 2020 and October 2021.

    In the 2022 Data Quality Report, there were up to three entities in a single jurisdiction reporting ‘implausibly high values in the field 2.56 ‘loan value’ reported for the securities lending transactions’. This issue, while not fully resolved by the end of 2022 nevertheless saw total SLEB loan value fall from c.€250 trillion !!! to c.€10 trillion.

    Three strikes and you’re out?

    No fines, public disclosures and an apparent lack of regulatory jeopardy and sadly lessons do not appear to be learnt. Perhaps lightning does strike three times! This year’s (2023) data quality report highlighted that one entity was still overreporting during the first half of 2023. Their SLEB loan value represented 55% of the total market value until ESMA contacted the relevant NCA and oversaw the resolution plan and corrective actions. This saw their SLEB loan value market share drop to a relatively immaterial amount (based on ESMA’s chart).

    Furthermore, ESMA noted that one counterparty was reporting repo principal amounts that accounted for c.15% of the overall market, reaching its peak in November 2022 at around €3 trillion. This entity was also populating the triparty agent field in error with the same LEI as the reporting counterparty. As remediation takes place, the market share of this reporting counterparty has dropped completely off the chart…

    ESMA Market Report – data quality observations

    In the meantime, the inaugural report on EU SFT markets (primarily focused on the repo market) was a welcome addition to ESMA’s market reports series.  

    However, it’s important to highlight that issues with outliers, stale reports, missing maturity dates and implausible collateral to loan ratios meant that ESMA had to exclude up to 36% of overall collateral market value from their analysis. Neither the scale of the data exclusion, nor the implications for data quality appear to have been fully acknowledged by this report.  

    The measure taken by ESMA to set thresholds for outliers based on “relevant monetary variable(s)” four standard deviations outside the median value indicate quite severe data quality issues. Setting the threshold so wide, I wonder how many values in the sample fell even two standard deviations outside the median. This measure resulted in a 4k reduction of the number of records in the sample, (0.6% of records) but a 19% or €2 trillion reduction in notional amount.

    The removal of stale reports, including mismatched but paired double-sided trades and records with an event date older than one year resulted in another 97k records (7% of records) being excluded, resulting in a cumulative 25% reduction in collateral market value. The need to exclude 97k records does not bode well either for the desirability of two-sided reporting, nor having overly stringent reconciliation requirements encompassing so many fields with such limited (or non-existent) tolerances. In fact if you were to exclude two-sided records from a single source (delegated reporting and a single vendor enrichment), then the negative effects would be even more evident.

    Finally, removal of term repos without maturity date and the exclusion of records with implausible collateral-to-loan ratios resulted in the loss of a further 5k records (1% of the total records) and a total of 36% reduction in overall collateral market value.

    When data quality issues appear to have such an adverse effect on data analysis, measures of stability, regulatory oversight and transparency, maybe it’s time to revisit the rulebook and terms of engagement with reporting counterparties?

    • Read our analysis of the MiFIR and EMIR angles of the 2023 Report on the Quality and Use of Data.
    • For an independent, forensic review of your firm’s reporting data quality, please get in touch.
  • ESMA Data Quality Report 2023: What does it say about MiFIR?

    ESMA Data Quality Report 2023: What does it say about MiFIR?

    ESMA published its 2023 Report on the Quality and Use of Data earlier this month. In this blog, we focus on the MiFIR elements of the report. 

    In June 2023, ESMA updated its data strategy defining how data will be used to support its objectives and reiterated that data plays a critical role in the day-to-day processes of NCAs, central banks (such as the European Central Bank (ECB)) and ESMA. Data is used extensively allowing financial regulators to fulfil their obligations under their key mandates to maintain financial stability, orderly markets, and market integrity.

    How ESMA is using ARM and APA data

    In the context of supervision of data reporting service providers (DRSPs), ESMA notes in the report that it uses metrics relating to the timeliness, completeness, availability and integrity of data received by approved reporting mechanisms (ARMs) and approved publication arrangements (APAs). It draws attention to the fact that the number of files rejected by ARMs has fallen significantly, suggesting better quality of data. ESMA conducted a comparison of transactions reported to ARMs with those published by APAs, evidencing issues around APA data access and aggregation, which triggered follow-up actions from a supervisory and policy perspective. ARM transaction data was also used to detect and investigate one case of significant overreporting relevant for the MiFIR transparency calculations. 

    ESMA notes that the observations drawn from its analysis lead to new validation rules, enhancements of test methodologies and guidance in the definition of reporting fields. In the report, it publishes a list of publicly available reports detailing how regulatory reporting data has been used to support the analysis. It uses examples such as the evolution of EEA share market structure since MiFID II published in October 2023, and a study by the AMF in France that used MiFIR data to analyse the profiles of individuals conducting retail investor activity.

    Comparison between transaction and transparency data

    The report also details that ESMA assessed the consistency between transaction data reported by ARMs and transparency data published by APAs. It found that reports common to both datasets exhibit a reasonable level of price consistency, whilst the use of machine learning (clustering) allowed the identification of misreporting patterns which have been notified to reporting entities. One result of the comparison between transparency and transaction data allowed ESMA to identify an incorrect reporting practice used by multiple organised trading facilities, leading to duplication in the transparency system.

    As per last years’ report, it is clear that data remains a priority for ESMA and with that, data accuracy. Regulators are clearly using the data to support their statutory objectives and outliers in the data will be identified, action taken and importantly for firms, data quality issues will be raised with the reporting firms themselves.

    • Read the ‘2023 Report on the Quality and Use of Data’ in full on ESMA’s website.
    • Read our blogs on the 2023 Data Quality Report on EMIR and SFTR.
    • For a free heathcheck of your MiFIR reporting (transaction, post-trade transparency or RTS 23 instrument) please get in touch.
  • How Surveillance Platforms can help Prevent Data Leaks

    How Surveillance Platforms can help Prevent Data Leaks

    Data is the lifeblood of the modern world, but its increasing vulnerability to leaks and breaches poses a significant challenge. In the age of digital communication, sensitive information can be just a click away from falling into the wrong hands. Fortunately, communications surveillance tools are emerging as a critical defence against data leaks. In this article, we explore how these tools can be deployed to prevent data leaks and safeguard valuable information.

    The Data Leak Dilemma

    Data leaks can have devastating consequences for organisations, including the exposure of private data and confidential information, financial losses, damage to reputation, legal liabilities, and the erosion of customer trust. Common types of data leaks include:

    • Unauthorised Access: When individuals gain unauthorised access to confidential data, either internally or externally.
    • Insider Threats: Employees or contractors intentionally or unintentionally disclosing sensitive information.
    • Phishing and Social Engineering: Cybercriminals manipulate individuals into revealing confidential data or login credentials.
    • Third-Party Compromise: Data leaks can occur through third-party vendors or service providers with access to an organisation’s systems.

    The Role of Communications Surveillance Tools

    Communications surveillance tools have traditionally been associated with compliance and risk management. However, they are increasingly recognised for their vital role in proactively preventing data leaks. Here’s how they can be deployed for this purpose:

    • Emails: Surveillance tools can scan emails for sensitive data, attachments, or suspicious patterns indicative of data leaks, such as the use of personal email addresses.
    • Chat and Messaging Apps: These tools can monitor internal and external communications for signs of data sharing or compromise.
    • Voice Calls: Surveillance software can analyse voice calls to identify keywords or phrases related to data leaks.
    • Alerts: Surveillance software can send timely alerts when it detects unusual communication patterns, large data transfers, or unauthorized access attempts.
    • Algorithms: the platform can flag irregular behaviour, such as accessing confidential data outside of normal working hours.
    • Behaviour Analysis: Surveillance software can analyse user behaviour to identify potential insider threats or suspicious activities that may lead to data leaks.
    • Data Loss Prevention (DLP) solutions: often integrated with surveillance tools, they can classify and tag sensitive data, ensuring it is not shared inappropriately.

    Challenges and Considerations

    While communications surveillance tools are valuable in preventing data leaks, there are important considerations to bear in mind:

    • Privacy Concerns: Balancing the need for security with employee privacy is crucial. Clear policies and transparency are essential to address these concerns.
    • Data Encryption: Implementing end-to-end encryption can make surveillance more challenging. Organisations need to strike a balance between security and surveillance capabilities.
    • False Positives: Overly aggressive surveillance can lead to false positives, impacting productivity and potentially causing employee morale issues.
    • Compliance: Organisations must ensure that their surveillance practices comply with relevant data protection and privacy regulations.

    Why it’s important

    In a world where data is both an asset and a liability, data security has become a paramount concern for organisations of all sizes. Communications surveillance tools, when implemented thoughtfully and responsibly, play a pivotal role in safeguarding sensitive information and mitigating the risks associated with data leaks. By proactively monitoring communication channels, detecting anomalies, and responding swiftly to potential threats, organisations can fortify their defences and protect their most valuable data assets from falling into the wrong hands.

    Where companies already have these tools in place for workflows like market abuse monitoring, not additionally leveraging them for other use cases could be a missed trick. 

     

    • Please get in touch to see how our communications surveillance platform could help you improve data security and prevent leaks.
  • FCA releases Market Watch 78 focusing on instrument reference data under RTS 23

    FCA releases Market Watch 78 focusing on instrument reference data under RTS 23

    The FCA has released Market Watch 78, which focuses on improving data quality for instrument reference data. At face value the audience for this newsletter appears to be trading venues or systematic internalisers (SIs). However all MiFIR investment firms should take a keen interest in its contents because the standards expected for the submission of IRD apply equally to other reporting obligations.

    The FCA highlights that:

    • Issues with IRD impact its ability to monitor markets effectively
    • IRD is key to its ability to conduct effective market oversight
    • IRD enables it to understand the nature and characteristics of products traded by market participants.

    Interestingly the regulator notes that UK EMIR trade reports are enriched with IRD to monitor for systemic risk. This is a step beyond just validating and supplementing of transaction reporting submissions (RTS 22) and transparency data (RTS 1,2,3).

    Data quality processes

    The FCA highlights its concerns with firms’ data quality processes, including where firms are repeatedly submitting identical records after receiving a rejection message. This should be a lesson for all firms submitting reference data as the FCA says that this could indicate weakness in firms’ exception management processes. The FCA is also concerned about, and presumably monitoring, the late submission of IRD as this can prevent investment firms from submitting transaction reports.

    In addition, the FCA draws attention to the fact that IRD submitting entities should include a review of warnings generated by the Market Data Processor (MDP). It can be inferred that the regulator does not believe this review is robustly taking place. In particular, the FCA focuses on Warning Message INS-128. Firms should be developing a check for inconsistencies with their submissions and including a process to resend the corrected record, or discuss the record with the relevant trading venue.

    The FCA provides a table with top 10 rejection codes by count and drills into best practice for firms to deal with a couple of the topics – Invalid issuer LEI and Invalid instrument classification.  A particular pattern on the table is validation errors related to the relationship between the first trade date and other key date fields. 

    Across all regimes the expectation is that firms have arrangements in place to identify incomplete or inaccurate data, and report data in a timely manner, beyond reviewing rejections. The FCA further notes that there is prevalent use of dummy or default values in IRD submissions, highlighting specifically:

    • instrument classification
    • name of the index/benchmark of a floating rate bond
    • identifier of the index/benchmark of a floating rate bond.

    Breach notifications

    In the final section of the newsletter, the regulator says it has received 135 breach notifications since 2018 and is “concerned that some IRD submitting entities may not be notifying us when they identify issues”.  When submitting IRD, firms should therefore make sure they have the same robust breach notification process in place for notifying the Markets Reporting Team across both RTS 22 and RTS 23.

    Cancelled instrument reference data

    The newsletter also highlights that only 23 entities have cancelled records in its FIRDS system over the past two years.  This means that most IRD submitting entities haven’t used this functionality.  The FCA says it expects “all entities to have processes to cancel records when required”.

    What does Market Watch 78 mean for firms?

    This Market Watch clearly highlights the importance the FCA attaches to ensuring high IRD quality as it underpins the integrity of the data for conducting effective market oversight.

    “Firms must have processes to ensure that their IRD submissions are accurate” – Market Watch 78

    It may also prompt firms without a RTS 23 reporting obligation to investigate whether their transaction reporting submissions match the static characteristics of the instrument’s reference data, and question whether they are highlighting potential data quality issues as a result.

    At Kaizen, our RTS 23 Accuracy Testing managed service provides firms with full visibility of instrument reference data reporting issues across the topics mentioned in Market Watch 78 and beyond, ensuring trading venues and SIs meet their reporting obligations and effectively manage their reporting risks.

    • For a free healthcheck of your RTS 23 instrument reference data, please contact us.
    • Read the newsletter in full on the FCA’s website.
  • FCA to help develop market abuse regimes for Crypto Assets and Private Intermittent Securities

    FCA to help develop market abuse regimes for Crypto Assets and Private Intermittent Securities

    The FCA recently published its 2024/25 business plan where it outlined a number of priorities, including that it will continue to deliver on its public commitment to “take assertive action on market abuse”. During the next financial year this commitment will involve the FCA:

    • Increasing their ability to detect and pursue cross-asset class market abuse, including fixed income and commodities;
    • Issuing a discussion paper on transferring MiFID data reporting regimes for transactions (RTS22) and reference data (RTS23) as part of the Smarter Regulatory Framework (SRF) process;
    • Assisting in delivering a proportional market abuse regime for Crypto Assets and the Private Intermittent Securities and Capital Exchange System (PISCES) facility;
    • Extending their data reporting supervision approach to EMIR, SFTR and Orderbook regimes;
    • Publishing the results of their peer review of market abuse systems and controls in providers of Direct Market Access (DMA); and
    • Publishing updated Market Cleanliness Data in Q3 2024

    Market abuse regime for Crypto assets

    It’s too early to tell but it is expected that the market abuse regime would apply to all persons committing market abuse on a crypto asset that is admitted to trading on a UK trading venue, regardless of where the person is based or where the trading takes place. 

    In addition, UK based crypto asset trading venues will be required to have controls to detect and disrupt market abuse and report suspicious activity to the UK regulator.

    Private Intermittent Securities and Capital Exchange System (PISCES) facility

    As anticipated, PISCES will allow privately held companies to open ‘intermittent trading windows’ in which shareholders can sell existing shares through its platform. Buyers in the trial period are likely to be limited to institutional and professional investors, although this could be expanded to include sophisticated and high-net worth investors.

    From the UK Treasury’s Consultation Paper relating to PISCES, the proposed market abuse regime will draw on existing definitions and concepts from MAR where appropriate. The proposed regime will also focus on the greatest market abuse risks in the context of PISCES (to avoid being disproportionate) and the scope will be limited to on-PISCES trading. The three market abuse offences under MAR, which the government intends to apply to PISCES are unlawful disclosure of inside information, market manipulation and insider dealing.

    In relation to the monitoring and enforcement against market abuse on the PISCES facility:

    • market participants, such as the PISCES operator and intermediaries, will need to establish and maintain effective arrangements, systems and procedures to prevent, detect and report suspected market abuse to the FCA
    • the PISCES operator would also be subject to requirements to ensure fair and orderly markets
    • the FCA will be the statutory authority for investigating and taking any enforcement action
    • participant companies will not be able to delay disclosure of inside information
    • the offences would apply to both firms and individuals

    UK authorities helping markets by fostering innovation

    It is always interesting to see where the FCA intends to increase its focus of attention in the short-term. Investing £11.3m in the SRF to repeal assimilated law and replace these with FCA rules, including MiFIR transaction and reference data reporting was to be expected. 

    Tailored market abuse regimes for crypto assets and for the trading of shares in private companies shows how the UK Treasury and the FCA are both helping to foster innovation and are embracing the FCA’s secondary objective for international competitiveness and growth.   

     

    • Please get in touch to see how we can help your firm improve its monitoring controls and achieve peace of mind with regards to detecting any suspicious activity or market abuse.
  • EU EMIR Refit – one month to go!

    EU EMIR Refit – one month to go!

    With just over one month to go until EU EMIR Refit, it will be all hands on deck for regulatory reporting teams to ensure a smooth go live.

    What are some of the last-minute things that firms should be considering? Here’s our top three:

    1. XML Files

    Make sure that you have the ability to read and review XML files or convert XML into something you can read because it’s not just submissions impacted, the results files will also be in XML. 

    2. Trade State Report

    From 29 April, under EU EMIR, the trades successfully submitted on T or T+1 will be shown on the T+2 ‘trade state report’, rather than being reported on the next day’s trade state report, as seen under current EMIR reporting. 

    This differs from how the trade state report will be generated under UK EMIR Refit, which will not alter from today’s process.

    3. Timing – 26/29 April

    Many of the trade repositories are planning to close their doors over the weekend of 27/28 April to update all systems to only accept new trades via the new reporting format.

    Why does this matter? Many cleared trades executed on Friday, get reported on the Saturday. But on this occasion, the trades will need to be reported on Monday when the TR re-opens, and can only be reported in the new EMIR format. 

    How we can help 

    Here at Kaizen, our award-winning assurance solutions are ready to support firms to assess their reporting quality. Firms are already utilising our on demand Accuracy Testing in the lead up to go live, to check the quality of the data that will be submitted from Monday 29 April. 

    After go live, regulators will expect accurate, complete and timely data to be reported by firms. Our ReportShield™ assurance includes Accuracy Testing which provides comprehensive, independent checking of all 203 data fields in the new regime, as well as Advanced Regulatory Reconciliations to check for completeness.  We can also help with a review of your control framework too. 

    We wish everyone preparing for EMIR Refit all the best for the next month! 

    • For a conversation with Tim or one of our regulatory specialists about any aspect of EMIR Refit, or for an independent assessment of the quality of your reporting under the new requirements, please contact us. 
  • What does daylight saving mean for regulatory reporting?

    What does daylight saving mean for regulatory reporting?

    On 31 March, in the early hours of the morning, clocks across the UK and the majority of mainland Europe will go forward an hour. Since Europe spans several time zones, the switch will occur at different local times. 

    Whilst you may need to adjust the clocks at home or spend another six months with different times on the microwave and oven, please remember that the time fields for UK & EU MiFIR trade and transaction reporting and UK & EU EMIR trade reporting should continue to be populated in Coordinated Universal Time (UTC).

    Trade time is of significant importance to regulators. As we have highlighted before, UK and EU NCAs are unlikely to be sympathetic if you make errors following these time transitions.  The UK’s FCA has warned firms of such mistakes for many years:

    “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.”  Market Watch 59.

    The CSSF in Luxembourg has also commented as to the importance of this field:

    “In the context of data quality tests performed on transaction reports, the CSSF identified that in several transaction reports the time indicated in field 28 “Trading date time” was the local time instead of UTC. Investment Firms have been informed that, within the framework of the transaction reporting obligation, dates and times shall always be reported in UTC.”

    • For more details or a discussion with one of our regulatory experts, please contact us. 
  • Unleashing AI to Transform Regulatory Compliance

    Unleashing AI to Transform Regulatory Compliance

    Our Chief Product Officer Rory McLaren recently gave a presentation at EmTech Global in London on the hot topic of Generative AI (GenAI).  He shared a five-step plan for businesses to take a strategic approach, giving examples of what we are doing at Kaizen. Rory emphasised the importance of being careful with IP and uncompromising about the security of customer data.

    (Please note, the images featured in this blog are generated by GenAI with the prompt used below the image.)

    What is GenAI?

    Generative artificial intelligence focuses on generating new content which could be text, audio, images and video. It has the potential to significantly impact regulatory compliance in the financial services industry. It can help with streamlining tasks, enhancing detection of suspicious activities, ensuring compliance, assessing the impact of regulatory requirements, and future proofing risk and compliance.

    However, GenAI is already causing concerns about privacy and questions about the integrity and accuracy of the information being created. There is also fear that GenAI might change jobs and society. As the ancient proverb goes, GenAI is like a tiger – it’s bloody dangerous in the wrong hands.

    Here’s Rory’s five step approach for taming the tiger.

    1. Approach the Tiger

    It’s important to get started and engage with GenAI to understand how it can be used. We recommend starting with simple, safe use cases using public data only. Blocking access within your company has limited long-term benefit. Instead, focus on crafting prompts and understanding how to use GenAI, as learning how to use and understand it is a critical skill we must all get to grips with.

    A monk crouching in front of and looking at a tiger
    Prompt: Draw an image in the style of the Japanese artist Hokusai of a novice monk approaching a crouching fearful looking tiger.

    2. Don’t get eaten

    There are important precautions that need to be taken to avoid getting eaten by the GenAI beast. Firms need to be careful with company-sensitive information and personally identifiable data. Firms should also be cognisant of the regulatory landscape, including the US Executive Order (October 2023), The Bletchley Park Declaration (November 2023), and the EU’s AI Act (December 2023). The technology is changing so quickly so be aware of SAAS software with continually evolving features which may add GenAI without your knowledge.

    A monk carefully placing his head inside the gaping mouth of a very large fierce looking tiger
    Prompt: Draw an image in the style of the Japanese artist Hokusai of a novice monk placing his head in the mouth of a savage looking tiger.

    3. Unleash the Power

    To unleash the power of GenAI, it’s important to focus on areas where it can make a significant difference. There is no point in using it to make small improvements that won’t make an impact on day-to-day work.

    There are examples already where GenAI is making or has the potential to make a large impact. In knowledge management, natural language processing, inference and summarisation can be used to leverage untapped resources, discover best practices and make a consistent approach available to all. This could be wealth managers accessing previous advice for new scenarios, tax companies connecting decades worth of data to gain insights via LLMs (Large Language Models), and law firms tapping into regulatory interpretation and advice they’ve previously provided. Data analysis and pattern matching can also be used to review large data sets quickly, identify patterns and surface possibilities for human review.

    The sweet spot is amplifying humans with AI, not replacing them. We need to see GenAI as a useful coach or another team member that helps us to do our jobs better.

    Fierce looking tiger leaping above waves
    Prompt: Draw an image in the style of Japanese artist Hokusai of a savage looking tiger, leaping in an explosive and powerful manner.

    4. Master the Stripes

    To master the stripes of the GenAI beast, new ways of thinking about problems are required to fully take advantage of the technology. It’s as much about training staff and changing working practices as it is about selecting the right technology. Understanding how to price the value of GenAI will be critical for both customers and suppliers. Not all AI adoption will be through adding a prompt to a product.

    Profile of a tiger's head stylised with geometric stripes
    Prompt: Draw an image in the style of Japanese artist Hokusai of a side on view of a savage looking tiger. The stripes on the tiger should look as natural as possible, whilst at the same time looking like there is some sort of maze or hidden pattern within them.

    5. Live in Harmony

    To live in harmony with GenAI, it’s important to remember that it’s just another tool for people to use. It augments humans, it doesn’t replace them. Firms can successfully integrate GenAI into their processes and workflows if they think strategically about where it can make the biggest difference. It is important to strike a balance and not apply it to all tasks. Junior analysts, developers, and lawyers all need tasks in order to become senior versions of these roles. How will this happen if AI does these tasks? Who will train the models and validate the output if we become too reliant? Where will that leave us?

    A large tiger sitting beside a young monk deep in meditation
    Prompt: Draw an image in the style of Japanese artist Hokusai of a savage looking tiger sitting peacefully next to a novice monk who is sitting in the lotus position with eyes closed.

    Where to from here?

    GenAI is so fast moving, it can be challenging to know where to begin and the best way to approach it.  To summarise:

    1. Approach GenAI now to gain experience and control the way it will transform your business
    2. Ensure you are aware of the legal and regulatory obligations for using the technology
    3. Find the area that has maximum impact for you
    4. Understand how your business and people will change
    5. Embrace the change, understand the ethical implications.
    • Interested to hear more about Kaizen’s experiences with AI?  Please get in touch to arrange a call with Rory. 

    • EmTech Global is the showcase event of Engine, the Investment Association’s FinTech hub.
  • International Women’s Day 2024: Spotlight on Nicole Brown

    International Women’s Day 2024: Spotlight on Nicole Brown

    This month, to mark International Women’s Day on 8 March, we are sharing a series of profiles on inspiring Kaizen women.  Nicole Brown is a data analyst in our G20 Regulatory Reporting Team. 

    What motivated you to choose data analysis as a career?

    My journey towards choosing data analysis as a career began during my time at the University of Kent, where I had the opportunity to immerse myself in a year-long study of data analytics. Through this experience, I delved into learning R code and exploring the manipulation of large datasets.

    I found myself captivated by the ability to solve complex problems and identify patterns within the results.

    What truly solidified my decision was the realisation how versatile data analysis is. It became apparent to me that data analysis is significant in many industries and can be applied to virtually any field, whether it is in finance or healthcare, marketing or even fashion. This versatility appealed to me, making data analysis an exciting career path.

    What is it about your work at Kaizen that interests you?

    I work within Kaizen’s G20 regulatory reporting team and we are responsible for ensuring timely delivery of our ReportShield quality assurance testing and reconciliation solutions to clients.  G20 regulations include EMIR, CFTC, SEC, MAS, ASIC, HKMA and Canadian reporting regimes amongst others. I enjoy extracting, cleansing and enriching data before running tests, to ensure that everything works smoothly.

     

    At the moment, as part of our efforts to make our testing more efficient, I am learning a new coding language which is both challenging and rewarding.

    Not to mention, being part of a great team that collaborates effectively has made working at Kaizen enjoyable. Overall, I appreciate the constant opportunity for growth and learning, which keeps me engaged in my role.

    What positive steps do you think we could take to help women overcome the challenges they face in your industry?

    Taking small but yet meaningful steps in the right direction can make a significant difference in creating a more inclusive environment for women.

    One positive step is to have mentorship and support programmes tailored specifically for women in the industry. These are important as they provide a safe space for women to grow, develop skills, and gain confidence in their abilities.

    Pairing aspiring female professionals with experienced mentors can offer valuable guidance and insights into navigating the challenges of the industry.

    In addition, hosting women’s networking events can be beneficial for women to connect with other aspiring women, providing a sense of community and support. This is something we do at Kaizen which I value.

    Furthermore, programmes focusing on skills such as public speaking can empower women to feel more comfortable and confident in expressing themselves within the workforce. By implementing these positive steps, we can work towards creating a more inclusive and supportive environment for women in the Regtech industry.

    Which women inspire you the most? Why?

    My greatest source of inspiration has always been my mother. Since my early years, she has consistently been my number one inspiration. Her constant support and belief in my abilities have been instrumental in shaping my character and aspirations. Furthermore, witnessing her ability to manage multiple responsibilities has been inspiring. I admire her ability to show that as a woman, there are no limits to what we can accomplish, and nothing should hinder us from pursuing our goals.

    Another woman who inspires me is Michelle Obama. While some may only see her as a former First Lady, her journey is marked by many challenges that she faced with resilience and grace.

    Despite the obstacles, she remained true to herself and worked to make a difference and serve as an inspiration to others.

    During her time as First Lady, Michelle Obama used her platform to advocate for education and empower young girls to fulfil their potential and dreams. Her commitment to uplifting others, even when faced with public scrutiny I find truly inspiring. She serves as a role model for many. Her resilience inspires me to step out my comfort zone and see challenges as opportunity for growth.

    Nicole’s profile is part of a series on inspiring Kaizen women to mark International Women’s Day 2024. Read about Legal Counsel Angharad Bryant and Relationship Manager Coral Durham. 

     

  • International Women’s Day 2024: Spotlight on Angharad Bryant

    International Women’s Day 2024: Spotlight on Angharad Bryant

    This month, to mark International Women’s Day on 8 March, we are sharing a series of profiles on inspiring Kaizen women.  Angharad Bryant recently qualified as a solicitor after completing her training at Kaizen and is now a Legal Counsel in our legal team.

    What motivated you to choose law as a career?

    While studying Ancient Greek at The University of St Andrews, I attended careers fairs where I spoke to solicitors about the nature of their work and the skills needed to be a successful commercial solicitor, such as analytical ability, interpersonal skills and commercial awareness.

    I thought I would be suited to a career in law as I had developed these skills at school and during my degree.

    I gained work experience in commercial firms and in-house legal departments within companies during university holidays and enjoyed the work and professional environment. My first legal work experience was with a team of in-house solicitors at Universal Music, which was very exciting as I love music. In my second week, I was tasked with drafting a licensing agreement concerning the distribution rights of the recordings of an artist’s concerts and began to appreciate how the law is used to facilitate business and manage risk. After graduating from St Andrews, I completed the GDL and LPC at The University of Law and never looked back.

    What is it about your work at Kaizen that interests you?  Why did you choose to do your training with Kaizen?

    The variety of my workload at Kaizen appeals to me. No day is the same and I am constantly confronted by new challenges. As an in-house solicitor, I support the business in a range of legal matters, from drafting, reviewing and negotiating commercial contracts to advising on contentious and litigious matters.

    From previous work experience, I knew that I was suited to an in-house environment and focused on applying for in-house legal roles.

    When the role at Kaizen came up, I immediately applied as the company had a reputation as a market leader in the regulatory technology industry and as a great place to start a career.

    I was also keen to work in a growth company as I expected that I would be involved in corporate matters, such as mergers and acquisitions, and gain the breadth of experience required to qualify as a solicitor.

    Since joining Kaizen, we have incorporated a Dutch subsidiary, acquired a company and invested in a few businesses, which has kept the legal team busy! By training to be a solicitor in-house and working alongside my clients, I have gained a unique insight into Kaizen’s business and truly understand my clients’ goals and priorities.

    Regtech can be male dominated, what positive steps do you think we could take to help women overcome the challenges they face in our industry?

    The Covid-19 pandemic led to a transformation in the way we work. It is now standard for employers to offer flexible and remote working policies to employees, which are particularly valuable to women as they still carry out a disproportionate amount of childcare and household work. Flexible working arrangements make it possible for women with caring duties to work full-time without sacrificing career progression.

    Further, I think that it is important for employers to have competitive maternity policies to attract and retain young, ambitious women in the workplace. By offering women a generous maternity policy, employers are giving women the opportunity to both continue with their careers and start families in the knowledge that their careers will not suffer.

    Establishing support networks is a great way to give women the opportunity to share their experiences and support one another with challenges. For example, at Kaizen, we have an Empowering Kaizen Women (Microsoft) Teams group where people share webinars, articles and events related to women’s career advancement in the Regtech industry. The marketing team also host an annual event in celebration of International Women’s Day, which is always a great opportunity to network and get to know other women in the company and hear their career stories.

    Which women inspire you the most?  Why?

    I am inspired by women who have been key proponents of women’s rights over the last few centuries and women who have broken the boundaries in law, politics, music and literature. For example, I admire Ruth Bader Ginsburg, who was the second woman to be appointed to the Supreme Court of the United States. Throughout her career, Ginsburg advocated for women’s rights and gender equality and is one of the most famous female lawyers in the world.

    Her visibility and power have no doubt inspired a generation of female lawyers.

    As a fan of pop music, musicians such as Taylor Swift and Dua Lipa inspire me as they are incredibly hardworking, talented songwriters and wholly dedicated to their careers. Dua Lipa has appeared in films, has her own podcast, interviewed Douglas Stuart at Hay Festival and launched a collection with Donatella Versace last year. Her confidence, dedication and willingness to step outside her comfort zone are inspiring. Meanwhile, Taylor Swift continues to break records in the music industry, most recently becoming the first artist to win Album of the Year at the Grammy Awards four times.

    Angharad’s profile is part of a series on inspiring Kaizen women to mark International Women’s Day 2024. Read Coral Durham’s profile here. 

  • International Women’s Day 2024: Spotlight on Coral Durham

    International Women’s Day 2024: Spotlight on Coral Durham

    This month, to mark International Women’s Day on March 8, we are sharing a series of profiles on inspiring Kaizen women. First up is Coral Durham, a sales and relationship manager in our European Team.

    How did you get to where you are today? 

    It has been a long road, but I have been fortunate in that I came into the city at a time when there were few women in IT or banking. The 80s were an exciting time and I felt like a pioneer in this new rapidly moving world.

    I started in 1982 in what was then called ‘IT computer operations’ and within two years was managing my first team running DEC PDP 11/70’s (amusingly another similar DEC computer is now on display in the Science Museum).

    Those were the days before email, the internet, laptops, and mobile phones. I worked shifts (nightwork included), soldered hundreds of cables whilst always or nearly always being the only woman, and definitely the only 5ft blonde in make-up and stilettos in IT.

    At the beginning of 1990, I joined ICMA (then AIBD), to set up its technical helpdesk team. I spent the first two years installing Trax systems, diagnosing, and fixing faults across all the Trax subscribers in London ranging from tiny brokers to the biggest global institutions – just me, my trusty soldering iron, a few 5 ¼ and 3 ½ inch floppy disks and an ex-army field telephone in a wooden box (seriously – it was bigger than my briefcase). I learnt so much during that time.

    I loved every moment – it was the early nineties, and the Canary Wharf tower was still being built. There were so many buildings springing up that I once had to install a Trax system via a builders’ lift with a hard hat as the building was still a shell.

    By the time MiFID I was launched in 2007, I was running a team of technical helpdesk analysts, a team of consultants, and a compliance function. Migrating all the Trax subscribers to the new MiFID version was an enormous project but I had an amazing team and together we worked a 24-hour shift system over the final three days with four hours on and four hours off, until the job was done. I worked with the Trax service for over 22 years and will always be grateful for the opportunity I was given to prove myself as a woman in IT and Finance.

    Since then, I have set up customer relationship functions for CHAPS (Clearing House Automated Payment System) and even decided to leave the city for a while, but I so missed the buzz that when I got the call to join Deutsche Boerse in its new Regulatory Reporting Hub venture I was there in a hot minute. This time I moved into a sales and relationship management role utilising the skills gained over the years in supporting and listening to customer needs.

    What motivated you to move into Sales and Relationship Management as a career?

    I didn’t choose relationship management, it chose me and felt like a natural progression. Whenever I’ve been asked what I do for a living, I say ‘I talk for a living’ which is partially true but more importantly I listen.

    My sales and relationship management role at Kaizen allows me to combine my technical knowledge, compliance, risk, governance and regulatory experience with soft skills such as listening and communication.

    Being part of the European Team within Kaizen offers me yet another exciting new opportunity as we navigate along this post Brexit world with its lines of divergence and ever changing Regulatory landscape.

    Regtech can be male dominated, what positive steps do you think we could take to help women overcome the challenges they face in our industry?

    I’m not sure I ever believed in quotas when it came to ‘women in the boardroom’ for example, as inevitably it was the male members of the Board who chose them based on their idea of what a female Board member should bring to the table.

    Sadly, I’m still reading the same articles stating women feel overlooked, ignored and not listened to in the workplace and this may well go back to how we were brought up and how we still bring up our daughters. We may not be able to change that but what we can do is work on a positive continuous framework that addresses and challenges the areas of concern. For example training for women in public speaking, debating, training on building self-confidence and self-worth.

    These suggestions may sound obvious, but they are the foundations from which women can start challenging other inequalities and stereotypes.

    Finally, demonstrating and setting success criteria within this framework will make it harder for it to be ignored and who knows, we may even see a few men taking some unconscious bias training.

    Who’s had the biggest influence on your career? 

    That’s a difficult question as I’ve always followed my own path. Rather the people that have encouraged me to pursue my career in my own way are the people that have shaped my life.

    My earliest influence was of course, my mum – who had to leave school at 15. She was never given the opportunities I had and was determined that I did not suffer the same fate.

    She loved to hear my stories about the banks I had visited and the people I had met and would always wear her best suit or ‘costume’ as she called it if she was meeting me at the office.

    The other major influence would be my mother-in-law who was one of the Windrush generation that came over from St. Vincent in the late fifties and although she was well educated, suffered prejudice. I have never met such a strong woman. Fearless in so many ways, not loud but just magnificent. Between them they have given me the confidence to shape my own career, on my own terms, in my own way and enjoy every moment.

    Coral’s story is part of a series on inspiring Kaizen women to mark International Women’s Day 2024.

     

  • Money market regulation – what’s in store for 2024/25?

    Money market regulation – what’s in store for 2024/25?

    In the world of transaction reporting, we’re always slave to events – economic crises, major fines, unexpected guidelines or Q&As. However, the path of wholesale regulatory development, new regulations and change tends to be slightly better signposted with official announcements, effective dates, regulations coming into force and reporting go-live dates. Relative to the world of derivatives, the regulatory landscape for money markets and SFTR looks significantly quieter in 2024.

    However, this may prove to be the calm before the storm. 2025 and 2026 are set to host two brand new reporting regimes in the USA and it’s highly likely that these will coincide with the onset of the SFTR Review and subsequent Refit.  

    SEC 10c-1a Securities Lending Reporting

    Coming back to 2024: The next known change is the US deadline for the Financial Industry Regulatory Authority (FINRA), the sole Registered National Securities Association (RNSA) to publish implementation rules for SEC 10c-1a Securities Lending reporting. According to the proscribed timeline, this must occur by 2 May 2024. The clock will also be ticking for reporting itself to commence on 2 January 2026. These rules will set out how US securities lenders or their agents will be required to report 12 data elements relating to those loans. We will discover just how many reportable fields those 12 data elements translate into (I would suggest that while not of SFTR proportions it’s likely to be rather more than 12). In instances where a covered securities loan consists of a broker or dealer borrowing fully paid or excess margin securities, only the broker or dealer (the borrower) is required to report and not the lender. The final deadline is 2 April 2026, when FINRA will be required to publish aggregated transaction activity and the distribution of loan rates for each security.  

    OFR’s Bilateral Uncleared Repo Reporting

    The timing is less certain on the next most imminent regulation – it’s now more than 12 months since a 60-day consultation was announced by the Office of Financial Research (OFR) department of the US Treasury on proposed data collection for the bilateral uncleared repo market. In spite of this, we still await the final rule which remains imminent. This regime was successfully piloted in 2022. The reporting requirements are more extensive than 10c-1 and are likely to be a major burden to plan, build, implement and control ahead of a 2025 or 2026 go-live. There are 33 proposed data elements including haircut, rate and optionality. Mooted by the OFR as “The last segment of the US SFT market lacking a transaction-level data source.” They expect approximately 40 reporting institutions, made up of brokers, dealers and other financial companies with large exposures ($10bn+) to the non-centrally cleared bilateral repo market to have to report daily to the OFR.       

    Expansion of Money Market Statistical Reporting (MMSR) in Europe

    Returning to Europe: On 1 July 2024, an additional 24 banks will add to the ranks of Money Market Statistical Reporting (MMSR) institutions, on top of the 45 existing reporters. This follows the first major extension of scope. Following LIBOR decommissioning and a less benign interest rate environment, the regulation has seen greater scrutiny from the European System of Central Banks members in recent months. The new reporters were expected to implement a soft go-live at the beginning of 2024 ahead of a more formal adoption in July. These reports, due 7am CET on T+1 pertain to the four money market segments of Unsecured, Secured, FX Swaps and OIS markets. As the sole mechanism for calculating the benchmark Euro Short Term Rate (€STR) and the principle means for the ECB to monitor the market transmission of monetary policy, it is very apparent that data quality is critical and effective controls, paramount.

    Closer scrutiny on SFTR in 2024

    Last, but certainly not least, ESMA’s SFTR review and subsequent Refit planning is not expected until 2025. Nevertheless, a number of National Competent Authorities (NCAs) appear to be paying closer attention to data quality and compliance in 2024 as SFTR takes its place as a more mature and topical regulation in the current geo-political environment.

    • If you have any concerns about existing or impending money market/securities financing regulation on either side of the Atlantic, please do not hesitate to get in touch with our team of regulatory experts at Kaizen.   
  • MAS updates FAQ ahead of October ReWrite of transaction reporting rules

    MAS updates FAQ ahead of October ReWrite of transaction reporting rules

    The Singapore financial regulator, MAS, has published a revision to its FAQ on Reporting of Derivatives Contracts. The latest revision contains some timely guidance aimed to provide clarity around certain aspects of the MAS reporting ReWrite which will be implemented on 21 October this year alongside ASIC’s similar ReWrite of the Australian reporting rules.

    The new questions can be identified by the tag “[With effect from 21 Oct 2024]” and include guidance on:

    • Reporting CFDs at position level
    • Whether previously reported trades need updating with a UTI that meets the latest standards
    • Reporting collateralisation category when the counterparty has a sub-agreement that differs with the main credit support annex
    • When reporting firms should populate the FX swap link ID and package identifier fields
    • When updating previously reported trades does the reporting firm need to report information that was not previously captured or reported.

    While the latest guidance is timely and will hopefully provide firms with additional clarity around certain aspects of the MAS ReWrite, the industry is still awaiting final rules from MAS.

    Many firms are actively working towards the 21 October deadline implementation based on the message specifications published by the trade repositories. Publishing the final rules would provide much needed clarity for all the firms involved. We hope the publication of these final MAS rules follow soon after this FAQ.

    • The revised FAQ can be found on MAS’ website
    • For a free health check of your MAS reporting ahead of the ReWrite, please contact us. 

     

  • Market Watch 77: FCA calls out organised crime groups as a risk to market integrity

    Market Watch 77: FCA calls out organised crime groups as a risk to market integrity

    It has long been known that insider dealing is typically performed by different types of market participants, from individual opportunists through to organised criminal groups (OCGs).  In the FCA’s Market Watch 77 there is a heavy focus on the risks to market integrity and firms posed by the latter. 

    Helpfully, the UK regulator outlines the characteristics and signs for firms to look out for to prevent and detect such criminal activity, including:

    • the appeal to OCGs of using equity spread bets and CFDs to optimise profits
    • trading ahead of legitimate merger and acquisition (M&A) announcements and speculation about M&A
    • the use of umbrella accounts to help mask the identity of the beneficial owners
    • feeding true and false stories about M&A to the market (the latter being a form of market manipulation)
    • the view that this activity can represent the tentacles of and a link to serious crime

    The FCA adds that suspicions should be aroused if specific clients are frequently the subject of Suspicious Transaction and Order Reports (STORs) or if several clients trade in the same security for the first time at favourable times.

    To help guard against OCGs the FCA provides a number of suggestions, including:

    • communicating to all clients that they have a zero-tolerance approach to market abuse
    • submitting STORs where appropriate, even if no public confirmation of the M&A activity is made
    • Training staff who work in M&A advisory of the risks posed by OCGs and avoid referencing the names of staff engaged in M&A advisory on the firm’s own website

    Market Watch 77 highlights the significant risks posed by OCGs to investment firms and market integrity more broadly. Where investment firms do not have effective controls in place, the FCA reminds firms that they have the option to use their enforcement powers, including requesting a FSMA s.166 report through to the variation of permissions.  

    This Market Watch re-iterates the importance of monitoring trading, communications and news together. The Kaizen surveillance platform comprises both trade and communications surveillance functionalities and is integrated with news stories from thousands of sources, sub-categorised into hundreds of market-impactful areas such as M&A, to optimise a firm’s monitoring effectiveness.

    In addition, our rules engine allows for blended alerts to be set up, for example, when high profit trades are made around significant news events (whether fake or real), making it much easier to focus on this kind of OCG activity that the FCA is keen to clamp down on.

     

    • Please get in touch to see how we can help your firm improve its monitoring controls and achieve peace of mind with regards to detecting any suspicious activity relating to OCGs.
  • US regulators continue to focus on incomplete data being submitted to surveillance platforms

    US regulators continue to focus on incomplete data being submitted to surveillance platforms

    In October last year we communicated that US regulators had imposed substantial fines on several large financial institutions for unauthorised communications on WhatsApp, iMessage and Signal and for poor record keeping and supervisory failures. 

    We also set out our thoughts regarding market abuse risk assessments and the need to have controls in place to identify situations where staff by-pass authorised communication channels while discussing work related matters and business with external parties.

    Multiple enforcement actions

    The US Securities and Exchange Commission (SEC) recently announced that it has charged and fined 16 more investment firms (broker-dealers and investment advisers) for breaching recordkeeping requirements when their employees used “off-channel” communications to discuss company business.

    Employees used personal text messages to make investment recommendations and provide advice. These messages were not recorded, maintained, or preserved in violation of the federal securities laws. These breaches meant that the SEC did not have access to these off-channel communications when conducting their investigations.

    Investigations and controls undermined

    Given that unauthorised communications can significantly undermine regulatory investigations into potential insider dealing and market manipulation, as well as the effectiveness of a firm’s internal market abuse controls, we expect this to remain an area of focus for regulators globally.  Between 2020 and 2022 alone, US regulators imposed fines of $2.7 billion on financial firms for a range of different market abuse behaviours across all asset classes (Source: Deloitte Market Abuse Outlook 2022).

    Financial and reputational damage

    The majority of firms already have trade surveillance platforms in place, but these latest fines, which amounted to more than $81 million, highlight the critical need for firms to implement robust and comprehensive controls and solutions to monitor electronic communications as well. Although the fines have a financial effect on firms, there is the reputational damage that also needs to be considered. For example, the SEC publicly censured the firms and ordered them to “cease and desist” from future violations of the relevant recordkeeping provisions.

    In addition, a fine of $350 million was also recently imposed in the US on an investment bank, as a sub-set of trading and order data had not been feeding into their surveillance platforms. This further highlights the importance of checking the completeness of trading, order and communication feeds from a surveillance perspective. 

    Trade and Communication surveillance controls

    As firms navigate the evolving regulatory landscape and ongoing enforcement actions, the need to adopt and embrace new processes, controls, and technologies for a proactive approach to trade and communication surveillance is now more evident than ever.

    At Kaizen we work with our clients to ensure an understanding of both the regulatory obligations and the business benefits of monitoring trading activity as well as on and off-channel communications. By working with firms across the buy-side and sell-side, we are able to ensure our clients adopt best practices and benefit from the latest technological innovations. 

    • As regulators focus more on this area, please reach out to learn more about the ways we can assist you.
  • This Valentine’s Day, the SEC is sending very little love to 13D Filers …

    This Valentine’s Day, the SEC is sending very little love to 13D Filers …

    Instead, for 2024 the language of love comes in the shape of accelerated deadlines, expanded derivative inclusion and data formatting obligations, in some big changes for beneficial ownership in the US, fit for a machine’s eyes only.

    February deadlines 

    February will stage the first phase of the amendments to Sections 13(d) and 13(g) of the Securities Exchange Act of 1934 (The Exchange Act) by halving the initial reporting deadline to five business days for Schedule 13D filers and two business days to file any amendments. As the reduced deadline is effective from 5 February, the new rules for disclosures mean investors have until 12 February for their initial filings to reach the SEC and any amendments to these submissions to be filed by 14 February. This will result in visibility and transparency of beneficial ownership much sooner to the market than was previously the case.

    Cash settled derivatives added to 13D reporting

    A more complex addition to 13D reporting is the US expansion of the inclusion of cash settled derivatives. Although it is largely understood that derivatives settled exclusively in cash indicate a pure economic interest, our experience is that this isn’t always how and why these derivatives are held. The SEC has now put greater emphasis and clarity on certain circumstances which could result in a holder having voting / investment power or deemed to be a beneficial owner. We therefore urge investors to carefully consider the terms of their derivative contracts to ensure these are not inadvertently subject to the disclosure requirements under the Rule 13d-3.

    Furthermore, 13D filers are now burdened with the task of including cash settled interests within item 6 of Schedule 13D. Here, the requirement to notify “any contracts, arrangements, understandings or relationships with respect to any securities of the issuer,” will now extend to including information concerning cash settled interests and disclosable on a Schedule 13D.

    XML from December 2024

    The amendments impose structured data requirements on those investors who would have typically utilised the more basic platforms for filing reports for Schedule 13D. These will no longer be adequate as the SEC leads investors towards its approved structured, machine-readable XML-based language, effective from December 2024.  Within this short timeframe, investors and Schedule 13D filers will need to undertake technical development and resource given that the XML process requires experience in producing, translating, and generating XML to be consumed correctly.

    Our Shareholding Disclosure system not only has this XML expertise, but it can fully automate the conversion of 13D disclosure information from its standard form into the language readily available for EDGAR consumption, saving you time and the risk of incorrectly filing with the SEC.

    Managing expanded ownership requirements

    These changes demonstrate the SEC’s continuous focus on the transparency of beneficial ownership. They also show the importance of the markets and investors having accessibility to, and visibility of the ownership of shares, and the promptness of this relevant and material information in what is a very fast paced market. 

    With this focus in mind, let’s not forget the changes implemented for those 13G filers scheduled for later this year as a result of the amendments to Sections 13(d) and 13(g) of the Securities Exchange Act of 1934, and Rule 13f-2 which introduces a gross short position regime, causing significant changes to disclosure obligations for investment managers in early 2025.

    Put simply, these adoptions magnify the need for an accurate automated reporting tool to capture these expanded ownership requirements and generate an auto-populated disclosure form within the new tighter deadlines. Kaizen’s platform deals with all these issues, supported by subject matter experts like myself, who have a background in filing global disclosures on behalf of tier one financial institutions. 

    • For more background to the changes, please visit the SEC’s website.
    • To learn more about Kaizen’s Shareholding Disclosure system and service, please get in touch. 

     

     

     

  • FCA Market Watch 76 outlines market abuse risks concerning ‘flying’ and ‘printing’

    FCA Market Watch 76 outlines market abuse risks concerning ‘flying’ and ‘printing’

    The UK’s Financial Conduct Authority (FCA) has shared its recent observations concerning ‘flying’ and ‘printing’ in its recent Market Watch 76 newsletter. The FCA explains that these activities create a false impression of a financial instrument’s liquidity and / or price through communicating in a misleading way.

    Back in 2018, the FCA described these two activities in Market Watch 57, including their expectations on firms in relation to trade, order and communication surveillance. Of greater concern is that in Market Watch 57 the FCA reminded firms that (back in 2015) they had highlighted their concerns regarding firms publishing incorrect volume data in Market Watch 48, including their expectation of firms. A theme is emerging here, and the FCA clearly sees the need to repeat its observations and concerns indicating that perhaps firms are failing to take note?

    The FCA’s most recent observations include cases where firms have failed to deal with ‘flying’ and ‘printing’ behaviour in a thorough or timely manner, including:

    • Failing to recognise the risks of flying and printing
    • Failing to implement proper surveillance
    • Not submitting Suspicious Transaction or Order Reports (STORs) or market observations
    • Taking too long to investigate potential misconduct.

    The FCA recommends that firms mitigate the risks associated with flying and printing in the following ways:

    • Ensuring compliance documentation prohibits this activity
    • Including these activities in (market abuse) training content
    • Ensuring that surveillance procedures to identify these activities are robust
    • Having appropriate disciplinary procedures and ensuring that commercial interests are not drivers of outcomes.

    This Market Watch reinforces the importance of having robust surveillance solutions in place to detect fictitious communications regarding bids, offers or actual trades and to automate reporting of such activity.

    In addition, these examples continue to show that firms can only really achieve assurance around market abuse regulations by having comprehensive, expertise-driven, internal frameworks across the entire compliance process; from risk assessment & policy transparency through surveillance monitoring to training and visible consequences for non-compliance.

    Given these repeated reminders and the severe consequences for firms that get this wrong, this Market Watch newsletter is an important read for all investment firms.

    • Read the Market Watch 76 Newsletter on the FCA’s website
    • For a discussion with Simon or one of our regulatory experts about your market abuse controls, please contact us.
  • SEC fires warning shot to firms on reporting data quality

    SEC fires warning shot to firms on reporting data quality

    The SEC has fired a warning shot across the bows of security-based swap reporting firms, warning them that it is observing failures related to the timeliness, accuracy and completeness of reporting.

    Risk Alert: Observations Related to Security-Based Swap Dealers cites issues the SEC has detected through examinations of, and outreach to, security-based swap dealers. As well as reporting issues it cites the US regulator’s concerns around failures involving:

    • Business conduct standards
    • Security-based swap trading relationship documentation and portfolio reconciliation
    • Recordkeeping

    The SEC’s section on Reporting and Correction of SBS Reporting Errors states:

    “In examinations and other outreach to security-based swap dealers, the Division observed that certain security-based swap dealers failed to:

    • Report certain security-based swap trade data to a registered security-based swap data repository within the required timeframes;
    • Accurately report primary trade information, including by reporting:
      • inaccurate notional amounts, including miscalculated notional amounts and notional amounts that are not economically possible
      • incorrect underlying asset information, such as an incorrect International Securities Identification Number (“ISIN”) or an underlying asset of “Basket,” without identifying specific underlying reference asset(s), reference issuer(s), or reference index as required under Rule 901(c)(1)(i)
    • Accurately and completely report all secondary trade information, such as:
      • counterparty identifications, including reporting an internal identifier for security-based swap transactions that did not involve privacy laws or natural persons; and
      • buyer, seller, receiver, or payer fields.

    In many instances, the failures identified above were the result of weak internal controls and processes for ensuring that information reported was accurate. In addition, examinations of security-based swap dealers revealed that certain security-based swap dealers did not employ procedures that were reasonably designed to identify and correct the trade reporting errors noted above.”

    • See the SEC’s press release here
    • Contact us to find out more about how we can help get your SEC reporting accurate, complete and timely.

     

  • APAC Derivative Reporting ReWrites: An Overview

    APAC Derivative Reporting ReWrites: An Overview

    The year ahead promises to be a busy one for firms caught under OTC derivatives reporting regimes in APAC. Here’s a quick overview of some key dates and some of the more substantive changes that are being introduced by regulators in Japan, Australia, Singapore and Hong Kong.

      JFSA (Japan) ASIC (Australia) MAS (Singapore) HKMA (Hong Kong)
    Timeline / Go-live date 1 April 2024 21 October 2024 21 October 2024 Q3 2025
    NEW ISO 20022 XML format ✓ ✓ ✓ Expected to align
    Unique Product Identifier Field (UPI) Only required from 7 April 2025 ✓ ✓ Expected to align
    Valuation Reporting Fields NEW In Situ In Situ Expected to align
    Margin Reporting Fields NEW Increases substantially NEW Expected to align
    NEW Action Type(s) & Event Type(s) ✓ ✓ ✓ Expected to align
    NEW Repeatable Date and Payment schedules ✓ ✓ ✓ Expected to align

     

    The impact of some of these changes are significant and very nearly on par as when dealing with a brand new reporting regime. So why now? How will this impact firms and what else do firms need to consider beyond what’s obvious?

    Global harmonisation

    When OTC derivatives transaction reporting was first introduced, each region established their own form of reporting structure and format. Although there was a common purpose to monitor systemic risk in financial markets, each region did so in an independent fashion. This was particularly evident when one looked at each regime’s reporting template.

    Admittedly, designing an all-encompassing report template can be highly complex. Not a simple task, given the variety of data points that may or may not be relevant given the type of derivative and differing underlying asset(s) it can reference.

    The overhaul(s) that are taking place aims to reform existing reporting regimes towards global harmonisation to crucially, lead to higher quality data for regulators to monitor and act upon. The ReWrites do this by incorporating many of the Critical Data Elements from the Technical Guidance on the Harmonisation of Critical Data Elements issued by the Regulatory Oversight Committee (ROC).

    A global cause but unitary implementation

    Say the words ‘global harmonisation’ uttered in the context of regulatory reporting and one would be hard pressed to receive objections of any kind from market participants. Everyone is onboard with this collective goal but at the risk of stating the obvious, accomplishing it remains a unitary effort.

    Each affected entity must make their own individual evaluations to ensure that they are able to meet the revised reporting obligations within its respective regime.

    The table shown above is by no means exhaustive but aims to highlight the multi-faceted nature of these changes. Firms will be busy allocating resources to:

    • Create or procure the right technological capabilities to process data in ISO 20022 XML format
    • Identify their ‘UPI’ strategy and implement its corresponding solution which sounds fairly straightforward but firms should not underestimate the magnitude of this task. For more on this see our UPI Explained blog
    • Conduct in-depth business analysis to understand and map internal system workflows to its respective ‘Action Type’ and ‘Event Type’ combination(s)
    • Establish the gap between the requirements of new data fields against internal systems to ultimately build reporting capabilities that adheres to the ReWrite.

    In addition to all of the above, firms need to navigate any potential last minute changes as we have seen thus far with the latest follow-on consultation that was released by ASIC in November. Not an easy task given that many firms are likely to be in their development phase with the majority of specification requirements already finalised.

    Last but not least!

    Whilst firms should rightly devote high focus towards the new build(s) for the ReWrites, they would be remiss to think that their work ends there.

    Firms will have to review and recalibrate existing control frameworks to ensure that they remain fit for purpose. Although the harmonisation in standards should in theory help to simplify the whole reporting process, firms will now be reporting on a larger expanded set of data elements with some of these data elements themselves potentially being derived from complex processes (think UPI).

    After all, this is hardly a new concept and market participants have had time to encounter the various nuts and bolts that go towards securing a robust regulatory reporting framework. It’s crucial that firms do not approach control frameworks as an afterthought and to have the necessary controls in place to ensure that their reported data is accurate and complete.

    • For a conversation with one of our regulatory specialists on the upcoming ReWrites outlined above, please get in touch. 
  • ASIC publishes Consultation CP361a

    ASIC publishes Consultation CP361a

    The consultation paper (CP361a) released by ASIC earlier this month can be seen as a very positive outcome of effective dialogue between regulators and market participants.

    The new data elements that have been put forward are reflective of the feedback provided by market participants and include a clear summary of the need for those new data elements.

    Here’s a summary of the content within CP361a that would no doubt require some attention:

    Seven new data elements:

    • 1a Secondary transaction identifier
    • 7a Counterparty 2 name
    • 59a Lower or only barrier price
    • 59b Upper barrier price
    • 58a Lower or only barrier price notation
    • 58b Upper barrier price notation
    • 105 New Derivative Trade Repository.

    On 24 existing fields:

    • ASIC has provided further clarification on how to report on 17 fields. Some notable clarifications to point out:
      • Alignment with CDE to restrict negative notional amounts to commodity derivatives only
      • Call and Put Amounts are not required for digital options
      • Data elements related to other payments is expected for partial and full terminations
    • Changes to seven fields that are fairly cosmetic in nature (for example, Field 13 ‘Execution agent of the Counterparty 1’ to ‘Execution agent of Counterparty 1’) or updating references from ‘Identifier’ to ‘Indicator’ for Field 86 ‘Identifier of the floating rate—Leg 2’

    Clarifications on any regulatory reporting is always welcome given the complexities. But given the timing, any late changes would undoubtedly put more pressure on existing project workstreams. Firms will have to impact assess the latest changes and work out how best to minimise any negative impacts late changes can bring to any project.

    The consultation closes on 15 December 2023 and a quick turnaround of the publishing of the ‘final’ changes is likely to be on a firm’s Christmas wish list!

    • Read the consultation paper on ASIC’s website
    • For a conversation with one of our regulatory specialists about preparing for the ASIC ReWrite, please get in touch. 
  • Market Watch 75: FCA reminds firms of the importance of market soundings regime

    Market Watch 75: FCA reminds firms of the importance of market soundings regime

    The UK’s Financial Conduct Authority has shared its observations relating to the market soundings regime within the UK Market Abuse Regulation (MAR) in its latest Market Watch newsletter. 

    Having robust market sounding controls in place offers protection to firms from the risk of committing market abuse, as was seen in 2012, when David Einhorn and Greenlight Capital Inc were both fined by the UK regulator.

    The FCA has observed that Market Sounding Recipients (MSRs) have traded the relevant financial instruments having had an initial communication with Disclosing Market Participants (DMPs). Although the DMPs had not specifically disclosed the identities of the financial instruments to the MSRs, the MSRs were still able to identify those details using other information available to them.

    One example involved an MSR selling a financial instrument in the secondary market, then buying the same quantity of the same financial instrument back in a subsequent placing, potentially at a discount.  It’s not clear how similar this example is to when two bond traders, Darren Morton and Christopher Parry were publicly censured for market abuse by the UK regulator in 2009.

    The FCA is concerned that in some instances MSRs could have an unfair advantage over other market participants even before they have agreed to receive inside information.  To help minimise this and other associated risks, the FCA helpfully sets out several ideas and sound processes that would constitute best practice, including the suggestion that DMPs assess the scripts they use at all stages of the sounding.

    Given the serious consequences for firms and market participants that get this wrong, this Market Watch newsletter is an essential read for both sell-side and buy-side firms.

    Kaizen’s integrated surveillance solution allows firms to identify both legitimate market soundings and potential abuses of this process, and then track the trading activity of those receiving the information.

     

    • Click here to learn about our integrated surveillance solution and request a demo.
    • Or, for a discussion with Simon or one of our regulatory experts about your market abuse controls, please contact us.
  • EU legislators agree changes to MiFID II and MiFIR

    EU legislators agree changes to MiFID II and MiFIR

    EU legislators have agreed the proposed changes to MiFID II and MiFIR, bringing us a step closer to their implementation. The changes are expected to be published in the Official Journal in Q1 2024.

    Focusing on Article 26, these amendments will require significant detail to be developed in RTS 22 over the following 9-18 months, meaning that it will not be possible to fully comply until the RTS is in place.

    ESMA is expected to consult on the likely changes to the RTS in Q1 2024. 

    Earlier in the year we explained what we might expect to see in the revised Article. We can now confirm the changes that will impact firms reporting to EU NCAs under the new regulations in what will be the first “real legislative” divergence between EU and UK reporting rules. 

    Broadening the scope of firms caught by the obligation to report

    MiFIR Article 52 now includes a requirement that the Commission will, in close cooperation with ESMA, assess the possibility of extending the requirements of Article 26 to Alternative Investment Fund Managers (AIFMs), and management companies which provide investment services and activities and which execute transactions in financial instruments.  They have 12 months to do so from publication.  

    Strengthening the obligation on NCAs

    ESMA has added three additional requirements on NCAs to distribute the reports to not only;

    • the competent authority of the most relevant market in terms of liquidity for those financial instruments;

    But also,

    • the competent authorities responsible for the supervision of the transmitting investment firms
    • the competent authorities responsible for the supervision of the branches which have been part of the transaction, and
    • the competent authority responsible for the supervision of the trading venues used.

    We can’t be 100% certain whether this obligation will mean any additional data will be required from firms in their reports or whether there is sufficient detail already to enable NCAs to comply with this.

    Instruments in scope

    The OTC derivatives transactions in scope has been amended. All OTC derivatives trades executed on venue will be in scope of transaction reporting – no change. Also in scope will be  off-venue OTC trades which fall within the transparency requirements.

    The amended transparency obligation has removed the link to the “traded on a trading venue”/TOTV concept and now covers OTC derivatives which are denominated in major currencies (Euro, Yen, US Dollar or Pound Sterling) and which are subject to the clearing obligation. Where these OTC derivatives are interest rate swaps, only the most liquid tenor combinations are included.

    TvTIC in Level One

    The TvTIC is now included in Level 1 legislation:

    “Reports on a transaction made at the trading venue shall include a transaction identification code generated and disseminated by the trading venue to both buying and selling members of the trading venue.”

    We are not convinced that bringing the requirement into Level 1 legislation will solve the implementation challenges associated with it.

    Farewell to the short selling flag…

    As expected, the obligation to report the short selling flag has finally been removed which aligns EU legislation with UK Supervisory priority.

    Branch Reporting

    No change to the substance but some of the text from RTS 22 covering third country firm branch reporting has been moved up into Level 1 text.

    Pre-Trade Waiver

    The obligation to report the “applicable waiver under which the trade has taken place” has also been removed. This also aligns EU legislation with current UK FCA Supervisory priority.

    Linking

    Of potential concern is the addition of the following requirement – the details of which won’t be fully realised until we see the amended RTS 22:

    ‘(j) the conditions for linking specific transactions and the means of the identification of aggregated orders resulting in the execution of a transaction;’ and

    ‘(k) the date by which transactions are to be reported.’

    This could result in significant implementation challenges for firms when we fully understand which “specific transactions” they mean and how they are to be linked. With MTCH capacity not solving the problem of linking market-side to client-side fills, it may be that paragraph (j) is ESMA’s solution.

    Paragraph (k) doesn’t seem to add much for regulators but firms will have to build complex logic to determine when exactly is T+1 – over weekends and ever shifting bank holidays.

    Our reaction

    Much of the content has been anticipated for a while and although some of these changes will reduce the reporting burden on firms, others are likely to prove more challenging to implement and report accurately.

    The implementation timeline has not yet crystallised and the changes will also likely require a revision of the reporting guidelines.  For the details we will have to wait for the consultation paper expected early in the New Year. 

    • Read the European Council’s announcement on its website.
    • To find out how you can achieve accurate, complete and timely MiFIR reporting, whether EU or UK, or for a discussion with Matthew on the reporting changes, please get in touch.
  • SEC adopts Rule 10c-1a on reporting securities lending trades

    SEC adopts Rule 10c-1a on reporting securities lending trades

    The countdown begins! Securities lending reporting in the United States is set to go live in 2025, after the US Securities and Exchange Commission (SEC) published the ‘Final Rule on Reporting of Securities Loans’ on Friday 13 October 2023. We’ll have more precise timing as soon as the adopting release is published in the Federal Register (not less than 30 days following the publication of the Final Rule). Securities lending reporting could be upon us as soon as January 2025.

    Our view on the Final Rule 

    Following more than 2,000 consultation responses to the proposed rule from every spectrum of investor and market participant, it seems the SEC has listened and allayed many concerns. It was always going to be a fine balance between satisfying the requirements to monitor, supervise and ensure an efficient, orderly market while providing much greater transparency and a more level playing field, while not appearing punitive towards market professionals or creating an operationally unworkable regime.       

    The final report appears to be less alarming and less onerous than the draft rule published back in November 2021.

    In particular, the proposal that securities lenders would be required to disclose details of securities “available to loan” and securities “on loan” to the registered national securities association (being FINRA – Financial Industry Regulatory Authority) which would be required to publish this information to the general public have both been removed. Also, the most sensitive aspects relating to transaction level loan amounts and individual loan and security identifying information will now be subject to a 20-day deferral period prior to publication.

    Finally, much to the relief of securities lending operations teams across the USA, the 15-minute reporting proposal has been shelved, replaced by “the end of the day on which the covered securities loan is effected.” End of day reporting will be required for new loans and loan modifications.

    Implementation and firms in scope

    FINRA is the organisation that will implement the rules regarding the format and manner to administer collection of information. They must propose rules within four months of the effective date of Rule 10c-1a (with the effective date set 60 days following the publication of the adopting release in the Federal Register).

    Scope of the reporting: 

    • Single-sided reporting from lenders only
    • Any person/entity who loans a security on behalf of itself or another ‘person’ 
    • Alternatively, reporting may be submitted by banks, clearing agencies, brokers, dealers, intermediaries (such as agent lenders) who act on behalf of beneficial owners.

    What must be reported?

    The Final Rule identifies 12 reportable data elements. We anticipate FINRA’s implementation may involve more than 12 fields but the data elements required to report are as follows:

    1. Legal name of the security issuer, and the LEI (Legal Entity Identifier) of the issuer, if the issuer has a non-lapsed LEI
    2. Ticker symbol, ISIN, CUSIP, or FIGI of the security, if assigned, or other identifier
    3. Date the loan was effected
    4. Time the loan was effected
    5. Name of the platform or venue for loans executed on a venue or platform
    6. Amount, such as size, volume, or both, of the reportable securities loaned
    7. Securities lending fee or rate, or any other fee or charges for loans not collateralised by cash
    8. Type of collateral used to secure the loan of securities
    9. Rebate rate or any other fee or charges for a loan collateralised by cash
    10. Percentage of collateral to value of loaned reportable securities required to secure such loan
    11. Termination date of the loan, if applicable
    12. Whether the borrower is a broker or dealer, a customer (if the person lending securities is a broker or dealer), a clearing agency, a bank, a custodian, or other person.
    • Read the press release on the new rule on the SEC’s website 
    • For background read Jonathan’s previous blog 
    • For a conversation with Jonathan on what this new rule means for your reporting, or for a discussion on your data quality concerns, contact us.
  • January 2024 – UPI and CFTC ReWrite Phase 2

    January 2024 – UPI and CFTC ReWrite Phase 2

    The bad news

    January 2024 kickstarts a truly tumultuous year for transaction reporting. January 29 more precisely sees the implementation of the CFTC ReWrite Phase 2 which means the adoption of UPI (Unique Product Identifier). After many years in the making the UPI might be having its debutants ball in the USA but that really just gets the ReWrite/Refit party circuit started.

    At the time of writing, the calendar for 2024 also entails implementation go-lives for:

    Jurisdiction  Regulator Status Description Date
    Japan JFSA Confirmed ReWrite 1 April 2024
    EU ESMA Confirmed EMIR Refit 29 April 2024
    UK FCA Confirmed EMIR Refit  30 September 2024
    Australia ASIC Confirmed ReWrite 21 October 2024
    Singapore MAS Expected ReWrite “October 2024”
    Canada CSA Expected ReWrite Q1 2025
    Hong Kong HKMA Expected ReWrite  Q3 2025

     

    The (somewhat) good news

    Back in 2015 I wrote an article describing transaction reporting as “the gift that keeps giving”. With eight major implementations planned for next year that’s as true today as it was back then. The 2024/5 reporting ReWrites’ schedule is without a shadow of a doubt the toughest we’ve seen since the inception of OTC derivative transaction reporting. But it’s not all bad news. Challenging as this will be there is some good news. The purpose driving all these implementations is harmonisation and they, for the most part, share a lot in common including the adoption of:

    • UPI to provide a consistent product taxonomy for reporting derivative products
    • CDE (Critical Data Elements) to globally agree the fields, the values and the definitions
    • ISO 20022 XML messaging standards for submitting to trade repositories
    • Global UTI standards to enforce common transaction identifiers across the various reporting regimes.

    Therefore the difficulties of managing multiple implementations across various reporting regulations is somewhat offset by the fact the reporting requirements are becoming more standardised and many of the data elements are converging on common globally agreed definitions. Reporting solutions, data dictionaries, analysis and reporting flows in theory become a bit simpler to manage. In theory at least.

    What does UPI mean for reporting?

    Anyone hoping that reporting with UPIs means simply replacing the current product identifier taxonomies with a new shiny UPI and sitting down with a nice cup of tea is going to be sorely disappointed.

    Reporting firms need to map all their current product attributes and then use these attributes to source a UPI from ANNA-DSB for each product. They’ll need to do this for all the product types they currently trade and any open positions previously reported to a trade repository (TR) or swap data repository (SDR).

    Some firms may opt to integrate the UPI data in their reporting solution only. Whereas others may integrate it further upstream in their trading, confirmation and associated systems as well. Either way, care will need to be taken to ensure the correct products are mapped to the correct UPIs. Unlike the current simple taxonomies such as FX Forward, the UPI is comparatively opaque and as such it won’t be easy for a human to see if the wrong UPI is on the trade without first looking up the reference data behind that UPI.

    Finally, firms will need to take a lot of care to ensure the other fields being reported on any given transaction are consistent with the UPI’s product characteristics. For example, if your UPI relates to a GBP/USD FX Forward then you need to ensure Notional Currency Leg 1&2 also contain GBP & USD.

    What does 29 January 2024 look like for CFTC & UPI?

    CFTC Rewrite Phase 2 contains two items of good news:

    1. The CFTC descoped UPI for commodity asset class. So UPI is being implemented for credit, equity, FX and interest rates but not commodity
    2. The CFTC also descoped ISO 20022 messaging because they wanted to wait until UPI is also ready for commodities.

    Some may argue it’s only postponing the pain as the above postponements will result in a Phase 3, likely in 2025, but for the time being given the evident confusion around UPI, this is probably best for most firms reporting to the CFTC.

    Once firms have designed and implemented a functioning UPI process, they will have the joy/pain of ensuring that UPI info is accurately incorporated into regulatory reporting processes given that:

    1. UPI will be required on all* Part 43/PPD submissions to the SDR
    2. UPI will be required on all* Part 45 trade submissions to the SDR
    3. UPI will be required on all Part 45 valuation submissions to the SDR.

    *Terminations and Erroring out (Action Types TERM & EROR) will not require UPI for either Part 43 PPD or Part 45 trade submissions. This is to accommodate removing previous submissions that may have been reported prior to UPI being applicable.

    Looking at the message specifications for one leading SDR, a handful of previously submittable fields have been deprecated. For example, Underlier ID is no longer required as this information is now embedded within the UPI.

    A new paradigm

    More interestingly there are fields which will be reported to the CFTC based on data that is derived from the UPI but are not submitted by the reporting firm, such as UPI Status, UPI Instrument Type and UPI Delivery Type. This is essentially a new paradigm for transaction reporting where a range of fields will be sourced from an external data provider (ANNA-DSB) and reported to the regulators despite not being submitted into the SDR by the reporting firm.

    This will also impact firms’ control frameworks as they need to ensure that the various product attributes within their systems are aligned to the correct UPI which they’ll submit to the SDR. They’ll also need to consider reconciling fields the SDR derived from the UPI to their source systems despite not having actually submitted these fields.

    Conclusion

    The CFTC may be the first off the mark with UPI in January next year but there are several other implementations coming, not least for both the EU & UK versions of EMIR. With only four months to go there is a worrying amount of confusion around UPI. Hopefully the UAT process will help to iron out the kinks and figure out the edge cases. Whether UPI achieves the regulatory aims of standardisation and interoperability, time will tell. Meantime 2024 is looking like a doozy for many reporting firms, ourselves at Kaizen included.

    • To understand the fundamentals of UPI, read Alan’s recent guide, UPI Explained
    • Still scratching your head over UPI?  For a conversation with Alan or one of our regulatory specialists, please get in touch. 
  • Global regulators to continue market abuse clampdown

    Global regulators to continue market abuse clampdown

    More market abuse fines could emerge as global regulators turn their attention to control failings

    Given the importance of maintaining confidence in authorised firms and the world’s financial markets we can expect regulators around the globe to continue to clamp down on participants who commit or facilitate market abuse.

    Control failings will be punished

    In August, the SEC and CFTC imposed substantial fines in the US on several large financial institutions for unauthorised communications on WhatsApp, iMessage and Signal and for poor record keeping and supervisory failures.

    Given that these issues are not confined to the US, further enforcement action can be expected in other major financial centres given how the use of unauthorised communication channels can undermine and jeopardise an otherwise robust market abuse control framework.

    The UK’s Financial Conduct Authority has previously fined firms for having deficient surveillance processes, including communications surveillance.

    Changing landscapes and challenges

    The pandemic which led to more staff working remotely, coupled with the proliferation of new communication channels have both served to increase the challenges faced by firms when developing their market abuse control frameworks. To emphasise this point, US prosecutors recently charged an individual for allegedly disclosing inside information using Xbox audio chat.

    With the patchwork of communication channels now available and ever changing technology, firms are considering whether they should be more selective to make it easier to govern. Although these challenges mean that integrated communications surveillance is more important than ever, there are more solutions available to investment firms.

    In the main, given the challenges with data storage and importance of scalability, the shift is towards using surveillance offerings developed by specialist third parties that offer offsite, cloud solutions.

    In relation to market manipulation, layering and spoofing continues to be one of the most common types of abuse being committed. For example, on 22 August two commodity traders were given prison sentences after jury trial convictions in the US for spoofing futures on precious metals.

    Market abuse risk assessments and controls

    Given the need to monitor pre-trade activity, resultant transactions and all relevant communication channels for potential market abuse, there is a need for an automated solution in all but the smallest of firms.

    Although data collection and technology play a leading role when developing a robust market abuse control framework, there are other important factors to consider. General market abuse training for all staff as well as deeper, tailored training for different teams including surveillance analysts is crucial.

    Having a comprehensive understanding of the business conducted, IT systems, applicable regulations and associated market abuse risks is essential. Just as important is the need to capture the firm’s existing market abuse controls that help mitigate these risks. Concentrating on the residual risks associated with insider dealing and market manipulation then becomes the focus when reinforcing the robustness of your control framework.

    The changing landscape and these latest cases emphasise the need for effective controls and the importance of having a holistic and integrated approach to surveillance, including all communications channels.

    • Click here to learn about our integrated surveillance solution and request a demo.
    • Or, for a discussion with Simon or one of our regulatory experts about your market abuse controls, please contact us.
  • Winners of the Barclays RepoHack 2023!

    Winners of the Barclays RepoHack 2023!

    We are thrilled to announce that Kaizen and our colleagues at London Reporting House (LRH) have been crowned winners of the Barclays RepoHack 2023! Congratulations to Kaizen’s Samuel Jackson (pictured far left) and Joseph Awonusi (pictured far right), together with our LRH colleagues Aleksandr Mattal and Dr. Luke Johnson for their tremendous efforts.

    The hackathon, hosted by Barclays Bank, ICMA, ISLA, ISDA, and FINOS was held in London. Organisations including Barclays, JP Morgan, CapGemini, Transcend, TradeHeader, and Lab 49 came together to compete against one another to streamline the post-trade processing of repo trades by integrating the repo Common Domain Model (CDM).

    Participants were tasked with crafting a seamless trade execution process and interface, all while spotlighting post-trade innovations through CDM.

    The team’s winning strategy came down to both innovation and efficiency. Aleksandr, Luke, Samuel and Joseph devised a system, harnessing CDM objects to facilitate the smooth transfer of transaction data between post-trade systems and SFTR reports. By utilising CDM’s consistent and digital trade representation, the team were able to sidestep redundant data reconciliation, thus accelerating the transition from trade execution to in-depth data analysis.

    We are so proud of the efforts of our Hackathon team, what an achievement!

  • How to navigate UK and EU EMIR Refit reporting changes

    How to navigate UK and EU EMIR Refit reporting changes

    EMIR Refit introduces wholesale change at a granular level for EMIR reporting. Firms must be compliant with the new standards from 29 April 2024 in the EU and 30 September 2024 in the UK. Each of these implementations is a large lift, and a headache for all firms concerned.

    Even the lucky firms with just a single UK obligation will need to source regulation from a whole new set of documents and sources. With this comes inefficiency in navigating the material, as well as potential divergence created in the final drafting.

    The main potential source of divergence is in the reporting guidelines themselves. The EU document was published in December 2022 and is currently being digested by firms. We expect the FCA to publish a series of smaller guideline articles for the UK, in contrast to the sizeable Reporting Guidelines published by ESMA in December 2022.  The FCA will use feedback from its industry engagement working groups to help steer the topics and direction of the aforementioned guideline articles.

    Many of those who work within transaction reporting in the UK will only have worked with EU documentation up until this point. Due to the different approaches of publishing documentation between the EU and UK regulators, it can leave compliance and reporting teams asking questions such as “where are the field requirements for the UK?”, “where are the requirements in the FCA handbook?” or, even “how does the UK differ from the EU”?

    The Single Rulebook platform hosts the latest UK and EU EMIR Refit rules, guidance and related documentation. Its intelligent literal and semantic search functionality means that the relevant UK and EU EMIR Refit rules can be located in seconds with the functionality to also find the corresponding UK or EU rule at the same time.

    What are the key changes of EMIR Refit?

    The new regulation will standardise messaging on the ISO 20022 format, implement UPI for more robust product identification, clarify the UTI generation waterfall and crucially, increase the number of reportable fields to 204 in the UK and 203 in the EU.

    How will the UK publish rules for UK EMIR Reporting?

    UK EMIR reporting falls under the FCA’s remit and all new rulemaking is published via policy statements and legal instruments. The following publications relate to UK EMIR Refit:

    • PS23/2 – Changes to reporting requirements, procedures for data quality and registration of Trade Repositories under UK EMIR
    • FCA 2023/3 – EMIR Rules (Procedures for Ensuring Data Quality) Instrument 2023
    • FCA 2023/4 – FCA Standards Instrument: The Technical Standards (EMIR Reporting and Data Quality and Miscellaneous Amendments) Instrument 2023
    • FCA 2023/5 – Technical Standards (EMIR Registration of Trade Repositories and Miscellaneous Amendments) Instrument 2023

    Where are these rules available in the FCA Handbook?

    These rules are not currently available in the FCA Handbook; they will only be published when they enter into force. For the interim period, these PDFs are the only published versions of the new requirements. When published, the main guidance will appear in two places.

    • EMIRR will be published as a new “Specialist Sourcebook”. This contains rules applicable to trade repositories.      
    • Two new FCA Technical Standards will be created:
      • Technical Standards on the Standards, Formats, Frequency and Methods and Arrangements for Reporting
      • Technical Standards on the Minimum Details of the Data to be Reported to Trade Repositories  

    There are also a number of less substantive amendments that will be made to the FCA Handbook, for example adding definitions to the glossary.

    Finally, FCA 2023/4 and FCA 2023 make changes to other “onshored” FCA technical standards. The complete extract is as below.

    Legal Instrument

    Change

    Comment

    FCA 2023/3

    The Glossary of definitions is amended in accordance with the Annex A to this Instrument.

    Add EMIRR definition

    FCA 2023/3

     

    The General Provisions sourcebook (GEN) is amended in accordance with the Annex B to this instrument.

    Legal administrative update

    FCA 2023/4

     

     

    The FCA revokes the following technical standards insofar as they apply in all cases, except in the case of central counterparties:

    (1) Commission Implementing Regulation (EU) No 1247/2012

    and,

    (2) Commission Delegated Regulation (EU) No 148/2013 of 19 December 2012 supplementing Regulation (EU) No 648/2012.

    Partial disapplication of previous rules

     

    The FCA amends the following technical standards in accordance with the relevant Annexes to this instrument:

    ●       Commission Delegated Regulation (EU) No 149/2013 of 19 December 2012 supplementing Regulation (EU) No 648/2012

    ●       Commission Delegated Regulation (EU) No 151/2013 of 19 December 2012 supplementing Regulation (EU) No 648/2012

    ●       Commission Delegated Regulation (EU) No 2016/957 of 9 March 2016 supplementing Regulation (EU) No 596/2014

    Administrative updates to document references and updates to ensure consistency of field names and action types.

    FCA 2023/5

    The following technical standards are amended in accordance with the Annexes to this instrument.

    ●       Commission Delegated Regulation (EU) No 150/2013 of 19 December 2012 supplementing Regulation (EU) No 648/2012

    ●       Commission Implementing Regulation (EU) No 1248/2012

    ●       Commission Delegated Regulation (EU) No 151/2013 of 19 December 2012 supplementing Regulation (EU) No 648/2012

    Administrative updates to document references and updates to operational risk and control requirements for trade repositories.

     

     

    To date, changes to onshored RTS and ITS have not been made available in consolidated form by the UK Government. As a result, firms will need to establish other ways of navigating and retaining control over this type of change.

    You can now find these documents on the FCA’s website by setting a future date and navigating through the folders.

    The EMIRR specialist sourcebook can be found here by opening the Specialist Sourcebooks folder.

    The new technical standards can be found here by opening the European Markets Infrastructure Regulation > 2023 folder.

    Mapping UK to EU rules

    As the rules were drafted within similar timeframes, we can build a map of the rules in the UK with the corresponding EU rules. This helps firms ensure that their reporting is aligned from day one. Firms will also need to monitor and manage the impact of future divergence between these requirements.

    Document

    UK

    EU

    TR Validations and inter-TR reconciliation

    FCA 2023/3

    Annex C

    (EMIRR Sourcebook)

    RTS 2022/1858

    Minimum Details of the Data to be Reported to Trade Repositories

    FCA 2023/4

    Annex A

    RTS 2022/1855

    Standards, Formats, Frequency and Methods and Arrangements for Reporting

    FCA 2023/4

    Annex B

    ITS 2022/1860

     

    In order to demonstrate control and compliance in both jurisdictions, it is also important to map the rules at a more granular level which the Rule Maps functionality in the Single Rulebook platform can provide. 

    Other Content that You Will Need

    The rules themselves are not enough to complete the migration. The full suite of ancillary regulatory documents is below. Firms will also need to refer to the documentation published by their chosen repository and follow their precise instructions.

    Document

    UK

    EU

    Guidelines

     

    EMIR Refit Reporting Guidelines

    Validation Rules

    UK EMIR Validations

    EU EMIR Validations*

    xml Schemas

    Incoming Messages

    Outgoing Messages

    Incoming Messages*

    Outgoing Messages*

    Mapping Table

     

    Mapping table

    Breach Notification

    UK European Market Infrastructure Regulation (UK EMIR) – reporting errors and omissions notification form (fca.org.uk)

    Contained within EU EMIR Validations

    * Please note that the EU Validations, Incoming Messages and Outgoing Messages were updated by ESMA on 6th September 2023 but the version number of each zip file remains 1.0.0.

     

    Conclusion

    Implementing the EMIR Refit transaction reporting changes will require close attention to the fine detail of the changes between EU and UK jurisdictions. Subject matter expertise will again be in short supply and firms will need to plan their project well to decrease the risk of reporting errors and non-compliance.

    Kaizen’s EMIR Refit Toolkit provides support at every stage of your project:

    1. Validations – Firms can test the validity of their submission files to ensure that reports meet the validation rules as defined by the regulator.
    2. Accuracy on Demand –  A new service, ‘Accuracy on Demand’ utilises Kaizen’s award-winning testing methodology to check whether your TR submissions are not only valid but accurate.
    3. Accuracy Testing – Kaizen’s flagship product is the gold standard in regulatory assurance, delivering a complete set of testing, down to every field of every record, tailored to your business.
    4. Single Rulebook – in addition to providing the regulatory content, Single Rulebook’s online platform also provides visual rule maps, traceability and annotation tools for EMIR Refit that can help firms manage the regulatory change brought about by the revised regulation.
    5. EMIR Refit Core Training – Training is an integral part of the systems and controls required for accurate reporting. Our interactive half-day course provides a comprehensive understanding of the EMIR Refit reporting requirements.
    • For a conversation with Chris Dingley on how to navigate your EMIR Refit reporting changes, contact us.
  • Kaizen hosts FCA and industry specialists at Ready, Steady…Refit!

    Kaizen hosts FCA and industry specialists at Ready, Steady…Refit!

    We were delighted to host more than 120 clients and industry experts at Merchant Taylor’s Hall, London on 14 September 2023 for an afternoon of discussion and information sharing on all things EMIR Refit.

    Speakers included Carmel Deenmamode, Market Conduct & Post Trade Policy Manager at the FCA as well as representatives from the Investment Association, FIA, LSEG Post-Trade, ISDA, DTCC, HSBC and our very own EMIR Reporting Director, Tim Hartley.

    The panel discussions focused on the go-live of EMIR Refit in both the UK and EU and how market participants can best prepare for the changes ahead, including how to navigate the nuances between the UK and EU regimes. 

    An insightful audience Q&A session covered the main pain points and queries that firms are still facing, such as:

    • What should reporting firms do when counterparties do not or cannot agree on consistent reporting fields for matching?
    • Will the UK publish similar guidance to ESMA’s Guidance and Q&As for EMIR Refit?
    • What is the UK’s general approach to publishing guidelines and documentation?
    • Will there be a new errors and omissions process in the UK for EMIR Refit?
    • Can firms apply their EU processes to their UK reporting to judge the quality of their submissions, for example using EU calculations for materiality?
    • How do reporting entities and their clients identify errors and what’s causing the errors when they’re using delegated reporting?

    We address some of these questions and more in our guide: How to Navigate UK and EU EMIR Refit Reporting Changes. 

    A huge thank you to our speakers and all our attendees! 

    • If you would like to learn more about our ‘Ready, Steady…Refit’ event or how our EMIR Refit Toolkit can help you prepare, please get in touch.
  • Unveiling key changes in ECB’s MMSR – a closer look

    Unveiling key changes in ECB’s MMSR – a closer look

    The European Central Bank (ECB) recently released revised guidelines for Money Markets Statistical Reporting (MMSR), bringing some key changes to the reporting framework. This comes hot on the heels of an earlier announcement by the ECB that it was expanding the scope of the regime, including 24 new firms that now required to report from next year.

    What do the revised guidelines say?

    • To improve efficiency and reduce reporting burden, transactions below EUR 500,000 nominal amount will not be reported across all money market segments and sectors, to maintain focus on significant transactions.                             
    • Only ‘reverse stock loans’ or ‘reverse securities loans’ economically equivalent to a repurchase agreement, are reportable, focusing on cash-driven transactions with securities loaned. Other SLEBs are out of scope.
    • To simplify and streamline Novations Reporting, ‘RELATED PROPRIETARY TRANSACTION IDENTIFICATION’ and ‘NOVATION STATUS’ fields will only need to be reported in the first rollover after novation, unless another novation occurs.
    • Reporting of UTI in all four segments is strongly advocated however still not enforced; for FX Swaps, the far leg’s UTI needs to be reported if they differ for accurate identification of these transactions.
    • ‘REFERENCE RATE INDICES ISIN CODES’ list truncated; EONIA and LIBOR indices ISINs have been removed. These revisions align with the wider adoption of the €STR benchmark interest rate and the ongoing decommissioning of EURIBOR and LIBOR indices.

    Impact on reporting firms

    Existing reporting firms must adjust their reporting logic to align with the revised guidelines, while the 24 new firms in scope will need to comply with MMSR regulations from July 1 2024, or can adopt early with prior notification to ECB. Adherence to these guidelines is vital for correct and accurate data submission, enabling the daily calculation of the €STR benchmark rate.

    Focus on controls and data quality

    The ECB emphasises the importance of controls and data quality. These guidelines aim to enhance the understanding of money markets, facilitate timely surveillance, improve information on monetary policy transmission, and provide reliable and transparent data to market participants. They guide reporting agents towards accurate reporting and increased market transparency. 

    The revised guidelines represent a significant step in the quest for data accuracy and transparency in money markets. Together with the expanded number of reporting firms, streamlined requirements, and a strong focus on controls and data quality, the ECB aims to bolster market surveillance and strengthen monetary policy transmission. Reporting firms, both existing and new, play a crucial role in this journey towards data excellence, ensuring the integrity of the money markets and providing valuable insights for market participants and policymakers alike.

    • Read the revised guidelines on the ECB’s website
    • For a discussion with Faizal or one of our regulatory experts about your MMSR reporting requirements, please contact us.
  • ECB expands Money Markets Statistical Reporting

    ECB expands Money Markets Statistical Reporting

    The European Central Bank (ECB) has announced a significant expansion of its Money Markets Statistical Reporting (MMSR) regime. From 1 July 2024, 24 new institutions will join the ranks of reporting agents for the MMSR dataset. The list includes some prominent financial institutions and another set of top tier institutions in Europe. This expansion promises to enrich the dataset’s diversity and depth.

    The MMSR dataset is a vital repository of transaction-by-transaction data that provides insights into various segments of the Euro money market. This includes secured and unsecured markets, foreign exchange swaps, and overnight index swaps. Perhaps most importantly the euro short-term rate (€STR) is created off the back of the MMSR data.

    At its core, the MMSR dataset serves as a window into the intricacies of the Euro money market. By collecting granular transaction data, the ECB gains a holistic understanding of market dynamics. This wealth of information, in turn, informs the ECB’s monetary policy decisions, enabling them to navigate market complexities effectively.

    Impact on €STR benchmark rate

    The data provided by the new reporting agents will be incorporated into the calculation of the euro short-term rate (€STR). As such, the expanded reporting population will have a direct influence on this crucial benchmark, which serves as a reference rate for various financial transactions.

    The ECB’s decision to add 24 new reporting agents to the Money Markets Statistical Reporting dataset underscores its commitment to maintaining accurate and comprehensive insights into the Euro money market. This expansion aligns with the ECB’s and other global regulators’ efforts to enhance transparency and make well-informed monetary policy decisions based on robust data.

    • View the list of the new reporting agents on the ECB’s website
    • If you would like to discuss any concerns or issues you have with your MMSR reporting please contact us.
  • How to interpret the EMIR Reporting Broker ID Field

    How to interpret the EMIR Reporting Broker ID Field

    With all the focus on EMIR Refit, it is easy to forget that firms still have a day-to-day EMIR reporting obligation that they have to attend to!   

    Earlier this year, ESMA made a useful and important update to its EMIR Q&A ‘Level 3’ guidance, which impacted the ‘Broker ID’ field.  This short article explores what that means for firms, and how Kaizen can help with ongoing regulatory changes.

    Background

    This is what the ‘Broker ID’ field in both ESMA and the FCA’s RTS for EMIR reporting currently says:

    In the case a broker acts as intermediary for the reporting counterparty without becoming a counterparty himself, the reporting counterparty shall identify this broker by a unique code.

    Despite being a reasonably straightforward field, the Q&A previously included wording (shown below) that threw open the interpretation of what a ‘Broker’ actually was under EMIR reporting, indicating that the Broker ID should always be populated, which was a somewhat controversial interpretation.  March’s update helps to clarify how firms should be populating this field.

    Previous ESMA Q&A

    TR Question 9(e)

    If a broker is itself the counterparty (legal principal) to a trade, should it be reported in both the “broker” and “counterparty” fields?

    TR Answer 9(e)

    Yes

    Latest ESMA Q&A

    TR Question 9(e)

    If a broker is itself the counterparty (legal principal) to a trade, should it be reported in both the “broker” and “counterparty” fields?

    TR Answer 9(e)

    No, when a broker is a counterparty to a derivative, it should report the derivative and identify itself as a counterparty. In line with the RTS on reporting and more particularly with regard to the details to be reported in the field 1.8, the broker is then not required to report its LEI in the field ’Broker ID’.

    Sadly, the validation rules include no corresponding update to help firms adhere to this change, and so it is possible to make submissions to a trade repository, which will contradict the wording under TR Q9(e).  Such submissions fall under trap of being valid, but wrong.

    How can Kaizen help me with this change?

    Kaizen’s award winning Accuracy Testing is constantly being improved and updated in line with regulatory and industry changes.  With this in mind, we immediately amended our testing, so that for all Kaizen clients, we could now check that the Reporting Counterparty field and Broker ID field are no longer populated with the same value, in line with TR Q9(e).  This is a good example of where Kaizen’s assurance testing will capture ‘valid but wrong’ reporting scenarios, as the existing validation rules will not prevent firms from having the same LEI repeated in both the Reporting Counterparty and Broker ID field.

    And finally, this change provides a useful opportunity to remind firms that even though some fields, such as the Broker ID, are listed as ‘optional’, regulators still very much expect them to ‘be populated if applicable’ to the derivative – which is something I have heard regulators and NCAs stress many times.  Where Kaizen sees important optional fields reported without a value, this is highlighted within the thorough results we provide, highlighting potential further ‘valid but wrong’ scenarios.

    Conclusion

    The Reporting Counterparty and Broker ID fields should never be populated with the same value, which may require some firms to amend their current EMIR reporting workflow, but is nonetheless a welcome clarification from ESMA for a field that will continue to be required under EMIR Refit.

    • The EMIR Q&A can be found on ESMA’s website
    • For help preparing for EMIR Refit or to discuss your EMIR reporting data quality with one of our regulatory experts, please contact us.

     

  • UK SFTR Validation Rules – a late twist from the FCA

    UK SFTR Validation Rules – a late twist from the FCA

    The UK FCA finally proposed its own changes to the SFTR validation rules on 1 August 2023, subject to a consultation period ending on 15 September 2023, before taking effect on 4 November 2024.

    This follows ESMA’s announcement in March 2023, due to come into effect in the EU on 11 September 2023. The proposals largely mirror ESMA’s changes with a few sensible twists – that will give small data quality benefits. In particular, the FCA is proposing using the EMIR Refit currency code validations (prohibiting special currency codes) and planning to add major post Libor benchmark interest rates such as €STR, SONIA and SOFR to the list of recognised floating rates and floating rebate rates. This last point is a big win and something that has likely frustrated regulators across Europe, with their inability to aggregate spurious ‘free text’ populated rates.

    ESMA’s mirroring changes are to the list of actions that will mandate reporting counterparty details (nature & sector) and entity responsible for the report. There are clarifications around the method used to provide collateral (conditionality only applying to securities lending), clearing, open term, collateralisation of net exposure, type of collateral component, the uncollateralised securities lending flag and collateral market value. These are in addition to clarifications on report tracking numbers, permitted types of collateral and associated fields for securities lending (cannot be commodities collateral) and UTI for collateral updates when collateralisation of net exposure is false.

    Finally, the UK cements its minor deviation from ESMA’s rules, with no reporting required for non-financial counterparties, through appropriate changes to the validation rules to reflect this.  

    The pressing issue is going to be the two speed validation rules changes, which will be running in parallel for the 15 months between September 2023 and November 2024. For any firm with both UK and EU SFTR reporting obligations, this is likely to prove significantly more onerous than the two and a half month wait that we saw last time…

    • Read the full update on the FCA’s website
    • For a conversation with Jonathan on the new validation rules, please contact us.
  • UPI – Unique Product Identifier Explained

    UPI – Unique Product Identifier Explained

    The Unique Product Identifier (UPI) is the long-awaited new taxonomy for better describing OTC derivative products and the various characteristics of how each derivative is structured.

    At its simplest level the UPI replaces the current simplistic OTC derivative taxonomy values such as “FX Forward” or ISDA’s “ForeignExchange:Forward” with an identifier mapped to far more granular attributes in a centralised database.

    That database is run by ANNA-DSB and much like ISIN codes, will mean that various parties can be sure they are talking about the same OTC derivative because they can look up that UPI in the database and all see the same attributes.

    ROCking out with ANNA

    Alphabetti spaghetti time for the acronyms.

    The ROC gave the mandate to ANNA to establish and run the DSB for UPI.

    Clear?

    No?

    Ok. The Regulatory Oversight Committee (a supranational group of financial market regulators and authorities that amongst other duties oversees the LEI framework) is leading the global rollout of UPI. As well as helping to establish the UPI protocols and taxonomy, the ROC has mandated the Association of National Numbering Agencies (ANNA) with establishing and operating a facility for obtaining and maintaining UPIs. This facility is called the Derivatives Service Bureau (DSB) and is essentially a paid-for service where users can obtain an existing UPI if one already exists or have a new UPI generated if it doesn’t. Think of it as a big centralised Excel spreadsheet that debits your credit card every time you glance in its direction.

    Taxonomies? Attributes? What?

    This stuff is admittedly hard to visualise so let’s break it down with examples.

    Let’s take good old Credit Default Swaps (CDS). Because had they not crashed the world’s economy in 2008 we wouldn’t be here today discussing UPI as part of the remedy for that misadventure.

    A firm has a CDS in its systems with various product attributes that describe things like what the underlying asset the CDS is based on and it wants to obtain the UPI for that CDS.

    The firm submits a query to ANNA-DSB with various inputs describing the CDS.

    The UPI query inputs for a CDS on a corporate bond are shown below:

                                         

    ANNA-DSB searches the UPI database to see if a UPI already exists for a CDS matching these various inputs. If no UPI exists, the DSB will assign a new UPI and create a new record in the database for subsequent users to see.

    The DSB then responds to the query with the resulting UPI (highlighted) and additional characteristics as shown below.

                                         

    Now whenever the firm communicates with another firm, regulator or party they can all use DSB data to know that UPI QZ2093849381 refers to a Credit Default Swap on a European corporate bond with ISIN GB2093849381, with CFI code SCUCCA and issued by LEI 39120071DMHXS09CI766.

    So similarly to the LEI where the database maintained by GLEIF means that firms can use an LEI code to ensure that they are talking about the exact same legal entity, the rationale behind UPI is that a central database of products provides clarity that firms are talking about the exact same OTC derivative product.

    FX Example

    The UPI query inputs and outputs vary based on the asset class and product type.

    If we consider Foreign Exchange then, if a firm has an FX Option in its systems and it wants to obtain the UPI for that FX Option.

    The firm submits the below query to ANNA-DSB with various inputs describing the various characteristics of the FX Option.

                                           

    DSB then responds to the query with the resulting UPI (highlighted) and additional characteristics as shown below.

                                           

    Now all parties can use DSB data to know that UPI QZV9SHRJ8KZG refers to an FX Option on a EUR vs USD, with CFI code HFTAVP, that’s a European-style physically settled call option.

    Interest Rates Example

    Next if we look at interest rates, if a firm has a cross-currency fixed-float swap and it wants to obtain the UPI for that swap.

    The firm submits the below query to ANNA-DSB describing the rates swap.

                                           

    DSB then responds to the query with the resulting UPI (highlighted) and additional characteristics as shown below.

                                             

    Now all parties can use DSB data to know that UPI QZ7M47SKZL15 refers to an cross-currency fixed-float swap on USD vs JPY, with CFI code SRCCCP that’s physically settled.

    So UPI is like an ISIN then?

    UPI essentially sits between a CFI code and an ISIN in terms of how granular or specific it gets.

    The CFI code describes the basic attributes but does not get as far as underlying assets, currencies etc.

    Taking the CFI from the previous rates example, we see that SRCCCP is the CFI code for a physically settled, cross-currency, fixed-floating, rates swap.

    Diagram below generated using ISDA’s CFI Code Generator:

                     

    The UPI takes it to the next level of granularity by telling us this rates swap is also based on USD vs JPY, uses the USD-LIBOR-BBA floating rate and has a six-month period for that reference rate. So the UPI is far more specific than the CFI which just outlines the broad characteristics.

    ISIN would take it even further in terms of granularity because ISIN also tends to reference the trading venue where it traded and any venue specific characteristics such as the currency it’s traded/priced in.

    Why not just use ISIN?

    Two main reasons…

    1. The more forgiving reason is that since ISINs are often specific to the trading venues this means that using ISINs makes it more difficult to aggregate products with the same characteristics that are traded on different venues. Given the whole OTC derivative reporting framework is geared towards systemic risk, the regulators want the ability to aggregate transactions at product level, rather than venue level, when examining counterparty exposure. So UPI being venue agnostic is beneficial for this surveillance.
    2. The less forgiving answer is that outside of EMIR (EU & UK versions) no other regulators use ISINs for OTC derivatives. EU and UK reporting is therefore the outlier and much like the reporting of Exchange Traded Derivatives (ETDs) that underpins it, the use of ISINs for OTC was widely considered crazy but nonetheless made it into the rulebooks.

    So whilst ESMA and the FCA pushed ahead with ISINs for OTC derivatives the remainder of the regulators globally have patiently waited for UPI to be ready as a global solution much like the LEI.

    UPI Pay to Play

    Unlike LEIs (where the legal entity obtaining an LEI has to pay an annual fee for that LEI but the database and data is essentially free to all), ANNA-DSB will charge users for creating UPIs and accessing the UPI data in general. This is a little more controversial as UPI’s adoption across many of the OTC derivative reporting regimes amongst other use-cases means that many firms will have no alternative other to register with ANNA-DSB and pay for the privilege.

    Time will tell whether other cottage industries and resources pop up around UPI data in much the same way as you see a plethora of LEI websites and utilities whenever you search for an LEI these days. I personally hope so because ANNA-DSB needs remuneration for creating and maintaining the UPI services, that much is reasonable. But everyone having to repeatedly pay to access the same data seems a lot less reasonable in the long run.

    Similarly to the LEI rollout, we’d expect an explosion of new UPIs at the start (when the CFTC goes live with UPI in January) and another explosion when EMIR Refit follows in April next year. But that growth in new UPI population will theoretically tail off and eventually slow right down where only exotic edge-case UPIs are requested, or UPIs on newly created credit or equity underlying instruments.

    Conclusion – The Big Short rerun

    The UPI is a good concept in general and, after what seems like a very long time in the making, it is finally becoming a reality. It should help to improve clarity and consistency across the industry and for regulatory reporting in general. However we see a great deal of confusion around what UPI really means and with six months to go until the CFTC UPI go live, this is concerning. 

    If the UPI allows various regulators to aggregate similar derivative contracts together to better assess the systemic risk then that can only be a good thing. I’ll happily watch the excellent The Big Short film again but I don’t need to relive the crisis itself. There is clearly a great deal of work ahead to get UPI up and running and fully integrated across many firms and many systems.

    Tables (apart from ISDA’s) sourced from ANNA-DSB.

    • Still scratching your head over UPI?  For a conversation with Alan or one of our regulatory specialists, please get in touch. 
    • Is your firm prepared for EMIR Refit? To find out more about our EMIR Refit Toolkit, please contact us.
  • ESMA report shows market manipulation related STORs outnumber insider dealing

    ESMA report shows market manipulation related STORs outnumber insider dealing

    ESMA recently published a report relating to suspicious transaction and order reports (STORs) and reiterated their importance as a source of market abuse investigations. 

    The report makes it evident that Brexit has had a significant impact on the STOR-related statistics. Because of this, ESMA decided to primarily focus the main part of their analysis on STORs received during 2021 and 2022.

    ESMA found that there were no major changes to the statistics over this two-year period, as the breakdown by all measures remained relatively consistent between 2021 and 2022, including:

    • the total number of STORs received totalled 6,125 in 2021 and 5,833 in 2022. Germany submitted the most raising 42% of the total STORs in 2021 and 40% in 2022, followed by France
    • the ratio of notifications by trading venues and investment firms
    • the percentage of STORs by instrument type (87% equities and bonds 7% in both years, with derivatives and other instruments covering the remainder)
    • the type of violation – alleged market manipulation accounted for 52% of the total in both years. Whereas insider dealing-related STORs accounted for 45% of the total in 2021 and 44% in 2022.

    Market manipulation

    One of the interesting aspects of the report is that more STORs now consistently relate to market manipulation than insider dealing. Previously (between 2010 and 2018) most STORs raised related to insider dealing. 

    The increase in STORs relating to market manipulation could be a sign that firms are becoming more sophisticated in their approach to detecting potential market abuse, but it’s probably too early to say. The continued increase in electronic and algorithmic trading could also be a factor.

  • FCA publishes Market Watch 74 highlighting common transaction reporting errors

    FCA publishes Market Watch 74 highlighting common transaction reporting errors

    The FCA has published its latest newsletter, Market Watch 74, and once again has used it to draw firms’ attention to common transaction reporting errors.

    This Market Watch is of particular interest as it tackles several issues not highlighted in the past, as well as reminders for some more familiar issues. 

    MDP data

    Despite the number of firms downloading data from the regulator’s Market Data Processor (MDP) showing a steady increase year-on-year, the FCA has reminded firms of their legal obligation to reconcile their records to MDP data and note that they have contacted firms who haven’t done so. 

    Not all EU NCAs make this as straightforward as the FCA, and the legal obligation remains to reconcile front office records to the latest point at which the data is available, be that from the ARM or NCA. 

    However, despite the increase in the number of firms accessing their data from the MDP there has been a fall in the number of firms raising errors and omission forms. This is somewhat surprising and contrary to our experience at Kaizen where although quality is – as noted by FCA – improving, many firms are still finding and resolving issues dating back to MIFIR go-live in 2018, resulting in costly and time consuming replay exercises.

    Identification of IDM and EDM

    There has not been much written guidance here from NCAs in the past as to “who” firms should populate in this field. The FCA has given some clarity and suggests that an individual named in either of these fields should have more than “limited practical involvement in those decisions at a transaction level.”

    Complex Trades

    The ESMA guidelines here have always, in our opinion, been clear but the FCA has reminded firms that reports linked by a Complex Trade ID should be reported with the same price. The regulator has also reminded firms that adherence to ESMA guidelines is still expected. 

    Transmission Agreements

    When is an agreement not an agreement, or perhaps when is an arrangement not an arrangement, those are the questions…

    The legislation is not prescriptive but the receiving firm needs to populate its report with data received from the transmitting firm. This, in itself, implies that the transmitting firm has to seek some assurance that the “receiving firm” has a mechanism in place to take this data and will make the necessary reports to ensure its obligation to report will fall away under Article 4.

    Unfortunately, some firms relying on Article 4 didn’t get that assurance and have therefore not been making the correct transaction reports.

    Transmitting firms must make certain they have evidence of the provisions in place with their receiving firms to benefit from Article 4. 

    Inconsistent Price & Quantity Notation

    The devil is in the detail here but there should be no excuse for firms not reporting the majority correctly. ESMA/FCA validation rules will only prevent some of common errors.  ESMA also mentioned price discrepancies reported for CDS in its recent Data Quality Report albeit from a slightly different angle. 

    TVTIC on Negotiated Trades

    The FCA has clarified this is an optional field where the trade is bought under the rules of the venue. 

    Chains

    The FCA has clarified the reporting of the Fund Manager and not the Fund, and the subsidiary and not the client of the subsidiary.

    Fields 42 – 56

    The regulator has reminded firms of the importance of getting supplementary instrument data correct where an ISIN is not used in Field 41.  They have commented on this several times in previous editions of Market Watch.

    Could it happen here?

    Following the arrival of any Market Watch, best practice dictates that firms now take steps to reassure their Senior Managers that all is well and that these errors wouldn’t, couldn’t, or shouldn’t, be happening on their watch. 

    In Market Watch 74, the FCA makes it clear that firms should heed their warnings: 

    “….some firms are not paying sufficient attention to our warnings on the importance of reporting transactions to us in a complete, accurate and timely manner.”

    And:

    “We may conduct further work on the areas covered in our Market Watch articles to ensure appropriate remedial actions are undertaken by firms.” 

    Perhaps firms would be wise to read “may” as “will”. 

  • A Guide: The Importance of Money Market Statistical Reporting (MMSR)

    A Guide: The Importance of Money Market Statistical Reporting (MMSR)

    What is MMSR?

    The Money Market Statistical Reporting (MMSR) regime is the European Central Bank’s (ECB) official and only source of data on daily money market transactions. Accurate reporting of this statistical information is crucial for decision-making at the ECB. This data provides a view of not just collateralised but also the unsecured, FX swaps & overnight index swaps (OIS) elements of the money markets.

    Why is it important?

    The ECB has been particularly keen on monitoring and regulating this aspect of the market, as it directly impacts economic activity across Europe. The regulator relies on MMSR reports to make informed decisions on monetary policy, financial stability, financial regulations and more importantly, the daily Euro benchmark computation of €STR (European Short-Term Rate).

    One of its measurements so far has been the withdrawal of the ECB’s quantitative easing. As the ECB scaled down its bond-buying programme, market participants watched the impact of the decision by tracking the money markets performance.

    What are the consequences of getting it wrong?

    The ECB requires financial institutions to report their data promptly, accurately, and transparently. Additionally, the legislation states the requirement that all statistical data reported is:

    “…tested frequently and adequate data quality checks are implemented by the reporting.”

    If a discrepancy is found, the ECB can impose fines on the institution responsible, ultimately holding them accountable for their actions.

    “ECB and the NCBs carry out frequent data quality checks on submitted reports to assess and question the quality and consistency of the data; Appropriate internal testing procedures and health checks of trading and reporting systems; Early detection of failures and gaps in reporting flows.” Reporting Instructions for the Electronic Transmission of Money Market Statistical Reporting (MMSR), version 3.5. (20 December 2021)

    The repercussions of inaccurate reporting are severe for firms and also have broader long-lasting effects on trust and stability within the financial markets. These issues range from simple errors in reporting to more complicated instances of data misrepresentation.

    Common errors

    Any small discrepancy in reported values can have a ripple effect that can cause significant damage to the economy and the financial industry.

    When testing our clients’ data we see a number of common errors occurring:

    • Enormously high or irrelevant haircuts and spreads
    • Erroneous rates, cash and nominal fields misinterpretation
    • Misreporting on collateral indicators and collateralisation values.

    These errors can lead to a distortion of the true state of the market and paints a completely different picture, undermining the existence of such data-driven and effective benchmark reporting in first place.

    How Kaizen can help

    Financial institutions should regularly test their data to ascertain the production of accurate results. Kaizen’s ReportShield™ quality assurance services have been developed by former regulators and industry specialists to provide firms with robust controls including continuous independent testing and validation of submitted data. Our testing is unique because we test every single data field on every report, so firms can be confident that they’re receiving a comprehensive assessment of their reporting quality.  

    One of our mantras is ‘don’t mark your own homework’ when it comes to your regulatory reporting data. Using an independent specialist provider gives far greater rigour than what can be achieved internally.

    Our services include:

    Final remarks

    Failure to report accurate statistical data creates risk of regulatory fines and reputational damage for the firm involved jeopardising the stability of financial markets. It’s crucial for firms to prioritise the importance of achieving maximum accuracy in their MMSR reporting, both to ensure that the economic environment remains stable and robust in the long run and to avoid serious consequences for the firm. Investment in assurance activities will provide significant cost savings as well as reducing regulatory risks.

    • Do you have the right controls in place for your MMSR reporting? Are you 100% certain on the data quality and accuracy of your reporting?
    • For a discussion with Faizal or one of our regulatory experts about any of the topics above, please contact us.

     

     

  • ESMA’s spotlight on data quality – Part 3: SFTR – a case of ‘valid but wrong’

    ESMA’s spotlight on data quality – Part 3: SFTR – a case of ‘valid but wrong’

    Identifying SFTR errors should be rather like shooting fish in a barrel. In spite of this, ESMA’s latest data quality report simply did not uncover the bodies.

    In this edition, there was no smoking gun, more of a smoking peashooter. In relation to SFTR, only one low-key material issue was uncovered in which three entities in a single jurisdiction had reported unfeasibly large securities loans.

    Our SFTR testing experience indicates that there is a sea of price unit errors, haircut issues, incorrect quality, incorrect price, incorrect type, under-reporting (collateral, re-use, cash reinvestment & funding sources) among a litany of other errors. On top of that, many aspects of SFTR remain only partially defined or undefined, such that the resultant data is of dubious value, full of uncertainty and contradiction.

    Data quality indicators dashboard

    ESMA stated that it had been transitioning to a new data quality indicators (DQIs) dashboard for both EMIR and SFTR, with the SFTR implementation to be completed during 2023. Together with a data-sharing framework, this is how ESMA is proactively monitoring and engaging with National Competent Authorities (NCAs) on data quality issues.

    In the existing case for EMIR, it includes 19 DQIs to detect and measure various types of misreporting, including under and over reporting, inconsistent reporting vis-à-vis the other counterparty, incomplete information in the key fields of the report, late reporting, abnormal values, and a lack of correct identifiers of the counterparties. This is computed by ESMA monthly, based on the entire EMIR dataset.

    The empirical evidence we have from our quality assurance testing services indicates that ESMA’s methods – with dependency on extraordinary values, the validation rules and TR reconciliation processes – may only scratch the surface of errors present in reported data.

    False comfort

    In ESMA’s EMIR data, there appears to be a lot of false comfort to be had from the reduction in the percentage of errors identified under these DQI methods from a high of 27.6% to a low of 7.8%. If we were to speculate that ESMA’s methods identify only 10% of true outstanding errors, then a decline from 27.6% to 7.8% equates to less than a 2% improvement in actual data quality.

    On SFTR specifically, ESMA identified implausibly high loan values (field 2.56) for securities lending trades, where loans from three entities in a single jurisdiction accounted for 77% of the total loan value in the market as a whole. On further investigation, it proved to be misreporting. This emphasises the importance of having SFTR reporting controls in place to identify ‘fat fingers’, spurious values and issues with units.

    Five fields responsible for most errors

    We repeatedly state that the validation rules, or indeed validations in conjunction with TR reconciliations are woefully inadequate measures for establishing high standards of data quality. We have also harboured doubts that the validation rules were always applied in their entirety, as we repeatedly see accepted messages we would expect to be ‘NACKed.’ However, ESMA has chosen to perform a “revalidation” process, largely to ensure that the TRs have applied the validation rules correctly. During this exercise, it identified issues with between 23 and 43 fields depending on which month’s run. However five fields were responsible for 95% of total failures:

    1. Collateral basket identifier (by far the biggest)
    2. Classification of a security
    3. Spread
    4. Floating rate reset frequency – multiplier, and
    5. Floating rate reference period.

    We have observed a number of issues with the population of the collateral basket identifier and ways in which this field can be ‘abused.’ In some cases, we’ve seen individual bond ISIN codes entered (that are clearly not collateral basket ISINs), proprietary (non-official) ISIN codes and frequent use of the collateral basket identifier (typically in relation to securities lending business) to avoid having to provide further collateral detail.

    With regards to classification of a security (CFI code), until very recently (and the publication of Q&A 15), it has been the only SFTR field with a golden source, namely the ANNA ASB database. In our experience, it is common to see the default character ‘X’ used in place of correct characters, CFI codes that bear no relation to the security in question and inconsistencies with the values published in the ANNA ASB database.

    The final two fields mentioned, floating rate reset frequency – multiplier and floating rate reference period – time period, in our experience, are both impacted by default values (particularly one) and inconsistent inputs that do not make economic or standard market practice sense.

    Fit for purpose?

    Sadly, the conceptual issue remains, the vast majority of incorrect reports pass the validation rules – the classic ‘valid but wrong’ problem. SFTR is crying out for greater regulatory certainty, precisely defined fields with limited acceptable parameters. The doctrine “counterparties should agree amongst themselves” simply does not work. A regime with a litany of errors and extraordinary operational burden, is simply not fit for purpose.

    • Read the Data Quality full report on ESMA’s website
    • Read our insights from our regulatory experts on the EMIR and MiFIR aspects of the report
    • For a free healthcheck of your SFTR reporting or a conversation with Jonathan or another regulatory expert, please contact us.
  • ESMA’s spotlight on data quality – Part 2: the use and quality of MiFIR transaction data

    ESMA’s spotlight on data quality – Part 2: the use and quality of MiFIR transaction data

    MiFIR transaction reporting data was a surprise inclusion in ESMA’s recent data quality report which has previously focused on EMIR and SFTR. The report includes some noteworthy updates around the key developments affecting data quality and colour on additional use cases that go beyond the traditional uses of the data. One notable area is where National Competent Authorities (NCAs) are using transaction reporting data to understand the behaviours of retail investors.

    This work is contributing to ESMA’s wider work on retail risk indicators, again highlighting the importance of complete and accurate identification of natural persons.

    The report also details ESMA’s consistent approach to monitoring data quality and reminds readers that the cornerstone for the efficient and effective fulfilment of the authorities’ mandate is high-quality data.

    ESMA hopes that based on the lessons learnt and the development of a revised strategic approach to supervisory convergence on data quality, there will be further strengthening in its outcome-focused, data-driven, and risk-based approaches to supervising the reporting regimes.

    Key developments and the supervisory actions affecting data quality across MiFIR

    • ESMA becomes the supervisor of significant Data Reporting Service Providers (DRSPs)

    To meet the need for improved data quality convergence across the EU, ESMA became the direct supervisor of the most significant DRSPs in January 2022. In total, this accounts for almost 99% of reported transactions amongst registered ARMs. In the second half of the year, the volumes stabilised at around a monthly average of 650m transactions, but this was preceded by some volatility in the first half of the year, with the first quarter having an average of over 900m. Approximately half of the reports received by NCAs were received directly, ie. they were not reported through an ARM.

    • Insights from the analysis of CDS prices

    ESMA is looking to provide clarifications or modifications to the reporting of certain fields, with the aim of improving consistency. It provides a clear use case when highlighting the reporting of the price of Credit Default Swaps (CDS). Out of 260k reported CDS transactions, 200k were reporting with basis points as the applicable price type. Out of this population of 200k, 89% of the trades were reported with a standardised coupon and the remaining 11% were reported as a quoted spread.  This should give firms food for thought and the opportunity to review how they are reporting CDS transactions.

    • Lessons learnt from the analysis of MiFIR transactions data for the Carbon Market Report

    Another use-case comes from the Carbon Market Report where MiFIR transaction reports were used to provide important insights into the trading of emission allowances from H2 2021. The reported data was supplemented with information from other sources which will be familiar to many: ANNA, MiFIR Reference Data (FIRDS), GLEIF and ESMA counterparty data based on the EMIR trade repository data and public registers of counterparties. ESMA notes “unprecedented analysis” and the “multiple challenges associated with reconciling the various data sources”.

    This could point to areas of inconsistency with the transaction reporting data. In addition, other challenges called out were duplicated buy-sell chains and aggregation of the data. What is particularly interesting about this line is that ESMA may be proactively addressing this challenge through the proposed changes to the legislative text: “(j) the conditions for linking specific transactions and the means of the identification of aggregated orders resulting in the execution of a transaction.”

    • Consistency of transaction and transparency data

    ESMA has also undertaken a project to analyse the data from transaction reporting and post-trade transparency reporting to identify gaps in completeness in either domain. To add to this, ESMA has initiated ad-hoc supervision to assess the consistency between APA and ARM data from transaction and transparency reporting.

    ESMA’s focus on transaction reporting data quality is clear, so too is the emphasis on using the data to go beyond investigating market abuse. MiFIR transaction reporting data is increasingly providing ESMA the opportunity to delve deeper into tangible use-cases assessing and supporting the functionality of the market. Increasingly, transaction reports are cross-referenced and supplemented by additional data sources, which helps ESMA to highlight poor data quality and increasingly shape policy developments across transaction reporting and beyond. We can also see examples of this approach in the UK.

    • Read the full report on ESMA’s website
    • Read our blog on the EMIR aspects of the report
    • If you would like to discuss your MiFIR reporting data quality with Robert or one of our regulatory experts, please contact us.

     

     

  • Improving Equity Secondary Markets: A Debrief

    Improving Equity Secondary Markets: A Debrief

    The FCA has released its much-anticipated policy changes on the back of last year’s consultation: ‘Improving Equity Secondary Markets’, part of the Treasury’s Wholesale Markets Review (WMR).  As suggested, the aim is to enhance execution quality, increase liquidity and ultimately strengthen the UK’s position and competitiveness in global wholesale markets.

    This first Policy Statement relates to equities only, RTS 1 of MiFIR, and the majority of proposals will enter into force in April 2024, although it is noted that, for investment firms, changes in areas like pre-trade waivers will apply immediately (per the FCA’s existing powers). So please read through the document and understand the impact on you and your organisation…

    The Future Regulatory Framework (FRF) Review gave responsibility of retained EU law to the regulators and subsequently moves the UK MiFIR/MiFID II regime into the FCA Handbook.  Improving the content of Post-Trade Transparency (PTT) Reporting with a clearer identification of transactions that contribute to the price discovery process in a consolidated way, was important. The simplification of reporting by delineating the Systematic Internaliser (SI) regime from the new Designated Reporter Regime (DRR) was also key.

    The changes by the FCA should lead to:

    • improved market liquidity
    • more efficient prices
    • greater competition, choice and access between trading venues, SIs and investment firms
    • lower operating costs for firms
    • lower costs of trading
    • greater activity on UK trading venues.

    In this article I focus on three main areas – Exemptions, Flags and DRR.

    1. Exemptions

    The FCA was keen to expand on the list of transactions that are exempted from PTT reporting due to their non-price forming nature. The changing of conditions for when investment firms are required to PTT Report should simplify and lower costs. Article 13, RTS 1 lists the transactions exempt from PTT, adding noise to the market unnecessarily, but for consistency links to Article 2(5) of RTS 22.  Going forward, this list would include intra-group transactions, deemed non-price forming and which do not constitute addressable liquidity and are mainly used for the purpose of Risk Management (mirroring market conditions but not contributing to price). ‘Inter-affiliate transaction’ means a transaction between entities within the same group carried out exclusively as part of centralised booking for intra-group risk management purposes.”  The FCA would also streamline the overlap between Article 2, 6 & 13 of RTS 1.

    2. Flags

    The deletion of Pre & Post-Trade Transparency flags was proposed and has now been confirmed.  For post-trade this means the deletion of ‘SIZE’, ‘ILQD’ & ‘RPRI’ plus ‘ACTX’ & ‘DUPL’, taking into account the limited use of them today.  ‘ALGO’ will be maintained. Merging existing flags into one was discussed but ‘TNCP’ and ‘BENC’ will be maintained.  ‘CLSE’ has been introduced for Closing Prices and ‘PORT’ introduced to align with EU standards for Portfolio Transactions.

    The FCA highlighted that the removal of waivers would mean improved access to liquidity under the reference price waiver. In line with post-trade flags, there’s the aggregation of existing pre-trade flags ‘NLIQ’, ‘OILQ’ and ‘PRIC’ to ‘NETW’ for different types of negotiated trades.  A new flag will also be introduced for pre-trade large in scale ‘NTLS’, which has not been in place since MiFID II inception.

    It was noted that some of the pre and post trade flag changes will have an impact on fields 61 & 63 of Firms Transaction Reporting under RTS 22.

    3. DRR

    The proposal was to remove the SI status as a criterion in establishing when an investment firm is obligated to report a transaction. Under the DRR, firms could elect to register themselves as a designated reporter (DR) by notifying the FCA. A firm would be able to register as a DR regardless of its SI status. Registration would apply at entity level. This would mean DR status would apply to all that firm’s reportable trades across all eligible financial instruments. Where firms are trading with a non-DR, a DR would be responsible for reporting all trades. The seller would report where both, or neither, of the counterparties are a DR.

    Concerns were raised by some sell-side firms but the FCA clarified DRs can bilaterally agree, explicitly and in advance, which party shall fulfil the reporting obligation. The seller will always have the regulatory obligation to report but may discharge this by entering into an agreement with the buyer whereby the buyer agrees to report on its behalf. This option addresses the situation of having a reporting obligation but no arrangements to make the report public. DRR firms that wish to register as a designated reporter will need to submit a notification to the FCA. The FCA has said it will announce further details of this process in ‘due course’.

    Other points to note; the slight adjustments to the ‘Price’ field (numerical values only) ‘Price Currency’ field (incl. minor ccys) and the introduction of a new field called ‘Price Condition’ (already an existing FIX field but not published) to be populated with ‘PNDG’ when the price is not available at point of execution.

    Lastly, the FCA continues to highlight that it is developing the Consolidated Tape (CT) regime with the Treasury. The FCA intends to consult on this in the near future as part of work towards having a regulatory regime in place for a CT by 2024. A framework for CT will initially be for bonds but will have the scope to be built upon and adapted for equities.

    To summarise, the FCA post-Brexit consultation has been discussed for a while now and should not come as a surprise but there is still an impact on Investment Firms, (SIs & DRs) and APAs alike.  Careful consideration is needed on the Front Office IT development required and the understanding, across the market, of the DR responsibilities and communication with the buy-side.  Lots more to come and we hotly anticipate the non-Equities RTS 2 review in due course.

    • Read the full Policy Statement: Improving Equity Secondary Markets on the FCA’s website
    • For a conversation with Chris on any of the MiFID II Post-Trade Transparency Reporting matters raised above, please contact us.
  • FCA highlights lack of formal market abuse controls among some CFD providers

    FCA highlights lack of formal market abuse controls among some CFD providers

    What has the Financial Conduct Authority (FCA) said?

    In Market Watch 73, the FCA sets out its observations from its recent market abuse peer review into Contracts for Difference (CFD) providers. While the report was largely positive it did highlight some areas of weakness. In this blog we summarise some of its key findings and why the findings matter.

    The FCA observes that the surveillance of insider dealing is soundly covered compared to market manipulation, albeit further improvements could be made. The main concerns relate to firms not considering unrealised profits when determining whether insider dealing has potentially taken place.

    In comparison, it finds that the monitoring for market manipulation is weaker. Cross product manipulation was flagged as possibly on the increase, for example manipulating the underlying asset to profit from a related CFD or spread bet.

    ‘Narrowing the spread’ – a key area of weakness

    Although most firms were aware of ‘narrowing the spread’ behaviour, with some submitting suspicious transaction and order reports (STORs), no firms had listed this type of abuse in their risk assessments or had any ‘compliance-based’ surveillance to detect it. This behaviour is harder to detect when manipulation is conducted across multiple providers or via a dealing ring.  

    Two things can help here: communications surveillance tools can help identify different parties acting in concert and across markets. Secondly, the FCA can access MiFIR transaction reporting data to help detect such behaviour across firms. They also receive order level data covering the main UK equity markets.

    Lack of surveillance for non-equity asset classes

    Market Watch 73 also reports that most firms do not have effective surveillance for non-equity asset classes. Although a common and recurring theme over the years, firms still need to consider if insider dealing or market manipulation has occurred in retail derivatives referencing any asset class, not just equities.

    A tailored Market Abuse Risk Assessment (MARA) is key to helping identify market manipulation

    Some organisations lack a formal market abuse controls framework. Firms that undertake a Market Abuse Risk Assessment (MARA) can demonstrate that they are considering relevant market abuse risks. Furthermore, a tailored MARA is much more effective at identifying such risks.

    When conducting a MARA and building a surveillance framework, it’s important to consider:

    • All asset classes
    • Cross product and cross market manipulation
    • Trading activity in its historical context
    • Unrealised as well as realised profits
    • The different ways transactions are executed
    • How pre-trade activity (Orders, RFQs, IOIs) can manipulate prices and mislead market participants
    • The level of liquidity and pre and post trade transparency at instrument and market level
    • How electronic and voice communications are monitored
    • Keeping your MARA up to date!

     

    • Read the full Market Watch 73 on the FCA’s website
    • To learn more about Kaizen’s trade and communications surveillance solutions through our acquisition of Red Deer, please contact us.
  • ESMA’s spotlight on data quality – Part 1: a missed opportunity for EMIR?

    ESMA’s spotlight on data quality – Part 1: a missed opportunity for EMIR?

    ESMA’s latest Data Quality Report (DQR) presents a noticeable change in style and content from previous years.  Out are the detailed areas of concern or ‘tellings off’, and in are optimistic future endeavours, coupled with over-comforting graphs and statistics, and importantly the promise of systematic warnings of data quality breaches!  This blog discusses the key EMIR aspects of this year’s DQR.

    The best is yet to come

    With high quality data absolutely essential for the monitoring of derivative exposures, and reporting data quality known to be lower than desired, substantial changes are needed to address the previously admitted shortcomings.

    Change comes via the finalisation of EMIR Refit, bringing wholesale change to the reporting of derivatives in Europe, aligning standards more closely with the CDE guidance. Revised technical standards and a reasonable volume of guidance documentation will assist firms greatly, and ESMA is correct to highlight this important regulatory change.

    ESMA highlights its own process and controls. Since May 2022, ESMA has been implementing a data quality ‘dashboard’, which uses 19 data quality indicators (DQIs) to compare EMIR data on a monthly basis against an ‘EU benchmark’, which focuses on metrics including:

    • Under/over reporting
    • Inconsistent reporting v the other counterparty
    • Incomplete key fields
    • Late reports
    • Abnormal values
    • Lack of correct identifiers of counterparties

    Data is then shared with National Competent Authorities (NCAs), who in turn target and remediate ‘significant’ issues with entities, via a prescribed ‘NCA Engagement Framework’.  The framework aims to promote efficacy and efficiency of ESMA and the NCAs’ limited resources, stating that for remediation, they will focus on a ‘limited subset of entities with the highest volume of incorrect reports’.

    So firms with reporting obligations will and are being targeted for data review and remediation with the implementation of ESMA’s DQIs and Engagement Framework.

    Minor telling offs and comforting graphs

    Previous versions of the DQR discussed targeted areas of concern, whereas the ‘key developments’ section this year provided a far more watered down view of issues seen in the last 12 months.

    The majority of statistics provided a tale of decline in certain offending activities, such as late or missing valuations.  But this section misses a vital opportunity to critique existing reporting issues, such as the difficulty of reporting ‘CFI’ codes, poor interpretation of collateral fields, and unrealistic reported exposures.  Admittedly many of these areas will be targeted under EMIR Refit, but most entities are actively trying to remediate reporting issues well ahead of 2024, so that such problems do not become exponentially hard to fix once the regime is updated. More detailed examples of areas of concern are not easy for firms to hear, but provide important regulatory insight and help significantly with workload prioritisation for firms who are equally limited in resources.

    Could do better

    Overall, this year’s DQR represents a missed opportunity to give valuable insight into the key areas of concern for the quality of EMIR regulatory reporting.

    Significant changes via the DQIs, Engagement Framework and EMIR Refit updates are clearly crucial for significant and accelerated improvements to data quality going forward, as ESMA and NCAs adopt a more data driven approach to their supervisory duties. Impacted firms will be systematically targeted for their data quality issues, from which NCAs will expect to follow remediation projects until resolution.

    ESMA has provided some useful insights into areas of improvement, such as the completeness, timeliness and accuracy of submissions, but as a ‘flagship’ regular report in the regulator’s arsenal, future iterations would greatly benefit from more detailed examples of the issues across a much wider array of reporting topics.

     
  • The clock ticks for SEC Rule 10c-1/OFR Sec Lending and Uncleared Bilateral Repo Reporting

    The clock ticks for SEC Rule 10c-1/OFR Sec Lending and Uncleared Bilateral Repo Reporting

    SEC Securities Lending Reporting and OFR Uncleared Bilateral Repo Reporting cannot come too soon. US regulators face renewed pressure from all sides.

    Not to put too fine a point on it, US regulators find themselves lagging their international peers when it comes to securities financing transactions (SFT) regulation. US SFT regulation stands accused of being too light touch, fragmented and incomplete. In an environment of heightened inflation, rapidly rising interest rates, deteriorating credit conditions and where solvency concerns abound, this is undoubtedly making US authorities rather uncomfortable and eager to close out the gaps as a matter of priority.

    The US has a key role to play in identifying global and domestic SFT market systemic risk and in forewarning and tackling market crises. In the recent past, SFTs have certainly played a role in market failures such as the Gamestop short squeeze, UK pension LDI solvency crisis, and the collapses of Silicon Valley Bank and Credit Suisse banks.

    Gaps in reporting mean US regulators cannot get a firm handle on market events and are letting down their international partners in identifying and quantifying global systemic issues.

    Following the last financial crisis, SEC and Federal Reserve Board representatives played a very active role in the early discussions held by the newly formed Financial Stability Board (FSB) between 2012-2015. This culminated in the publication of “Standards and processes for collecting and aggregating global data on SFTs”. Subsequently, with the exception of the Office of Financial Research Centrally Cleared Repo Data Collection (beginning late 2019) taken directly from the DTCC and tri-party repo data that the Fed has supervisory authority over, it all went rather quiet in the US.

    The two major gaps in US SFT reporting are the securities lending market and the uncleared, bilateral repo market – currently operating in almost complete darkness. Steps are underway by both the SEC and Office of Financial Research (US Federal Reserve Board) respectively to bridge the gaps in these two unreported segments. In market conversation, at this juncture, we anticipate little resistance from either the securities lending nor repo industries in pushing ahead with these new reporting regimes.

    SEC 10c-1 Securities Lending Reporting has already been subject to extended delays.

    Thus far, consultations have dragged on significantly longer than first anticipated, especially in relation to SEC 10c-1 Securities Lending Reporting, in which the final rules were initially expected at the beginning of 2022. The need to significantly extend the consultation period and subsequent rule making perhaps demonstrate both the overly ambitious reporting time lines (initially proposed to be within 15 minutes of a securities loan being agreed) and transparency publication objectives, together with the competing interests of Wall Street (agent lenders), institutional investors (beneficial owners) and retail investors (craving a level playing field).

    OFR uncleared bilateral repo reporting is certainly more fully formed, following a successful pilot reporting exercise conducted with nine dealers over three days in June 2022. The scope of uncleared bilateral repo reporting is also much narrower, focused only on the largest collateral givers (with daily outstanding loans of $10 billion+). Therefore, it is also quite likely that OFR bilateral repo reporting goes live over a similar timeline to the SEC Securities Lending Reporting, quite possibly during 2024.

    Both regulators and the man on the street are losing patience. Retail investors in particular have been highly vocal in demanding greater transparency and fairness in equity markets.

    Regarding uncleared bilateral repo reporting, the Federal Register stated that is was,“a critical blind spot in a market that plays a key role in financial stability.”

    Regarding the SEC consultation on securities lending reporting, it has solicited close to 2000 responses, the vast majority of which have come from angered, frustrated retail investors, annoyed at the slow pace of regulatory change, the inability to address market failure, and craving far greater stock lending transparency. Retail investors have come out overwhelming in support of SEC 10c-1 Securities Lending Reporting in its current form as a bare minimum.

    Here are some quotes from the consultation responses:

    “I support these rule changes, the truth needs to come out.”   

    “Please for the love of America. Please stop shorting/naked shorting only to benefit Hedge Funds and the loss of the retail investor. Only allow 100% of the float to be obtained. The technology is available Please invest in a program to be able to see illegal shorting and spoofing. Lastly please FINE more then they made off their illegal tactics. As a member in the US Air Force I do my job no matter what the cost and get paid peanuts. Please do yours make it a fair market.”

    With extensive experience in helping firms comply with securities financing and money market reporting regimes, Kaizen Reporting can assist in putting together controls and quality assurance around impending securities lending and bilateral uncleared repo reporting. Please get in touch to kick off a conversation to get ahead and comply with impending regulation.

  • Does your firm have an SMF for trade and transaction reporting?

    Does your firm have an SMF for trade and transaction reporting?

    The Senior Managers and Certification Regime (SM&CR) may be under review but that doesn’t mean it’s not still in place.

    The FCA and PRA recently published a joint discussion paper which asks for feedback on the operational aspects of the SM&CR.  At the same time HM Treasury also published a Call for Evidence seeking views on the legislative aspects of the regime.  This follows the announcement in December 2022 that there would be a review of SM&CR as part of the Edinburgh Reforms.  Responses to the discussion paper are due on 1 June.

    This could not come at a more crucial time for the industry with so much regulatory change afoot with expected divergence in MiFID II reporting, EMIR Refit upcoming, as well as various other rewrites concluding. 

    But in the meantime, we wanted to remind firms of their SM&CR responsibilities. Do firms have a Senior Management Function (SMF) in place for their trade and transaction reporting requirements, accuracy and approvals?  Who is your SMF16?

    SM&CR takes three key elements:

    • Senior Managers Regime – Understanding and mapping out of the SMF responsibilities and consequences of actions, personal accountability
    • Certification regime – Documenting, demonstrating, and certifying that SMFs are suitable and ‘fit & proper’ for the role, with annual assessments. “Have my SMFs been trained?”
    • Conduct Rules – Governance and documentation, procedures & policies that have been brought into line for SM&CR and controls in place for recording the implementations, steps and the decisions made by your firm to comply with the Conduct Rules across all staff within your organisation.

    Kaizen can help firms through the understanding of the accuracy of their regulatory reporting, so SMFs have a valued and independent view of their reporting.  We also provide governance and controls with our structured Control Framework services, designed by former regulators and our industry specialists experts, making sure internal GRC structures and procedures are acceptable.

    Only a few months ago, the FCA issued a Dear CEO letter to wholesale brokers reminding them of their regulatory obligations and to take proactive steps towards ensuring compliance, in particular highlighting that individuals in compliance risk personal liability when something goes wrong under the SM&CR.

    • If you’d like some help getting the right controls in place to ensure your firm meets the requirements of the SM&CR from regulatory reporting perspective, please get in touch.

     

  • UK gilt market crisis leads regulators to dig deeper

    UK gilt market crisis leads regulators to dig deeper

    Bank of England working paper underlines the importance of getting regulatory reporting right

    The Bank of England’s recently released working paper ‘An anatomy of the 2022 gilt market crisis’ reminds us why regulatory reporting is so crucial to the healthy operation of the financial markets.

    The paper, published in March, is a subject for further debate rather than a policy document. Nevertheless, the production of a 95-page document has clearly been prompted by a very keen interest.

    A quick recap – what happened last year?

    The Bank of England intervened on three separate occasions during September and October 2022 in order to maintain financial stability and prevent pension funds collapsing, following the Kwarteng/Truss ministerial statement, ‘The Growth Plan’ of 23 September 2022.

    The paper’s author identified such extreme concentration in the liability driven investment (LDI) pension insurance industry that just 3 firms were accountable for 70% of UK gilts they were forced to sell to primary dealers in the eye of the storm.

    Rapidly rising interest rates and inflation expectations at this time played havoc with the balance of assets and liabilities at these funds, particularly as real yields plummeted to new extreme negative levels.

    The demands of future pensioners necessitate real, rather than nominal returns, i.e. pension funds need to be able to lock in a certain level of future spending power for their members, irrespective of the future path of inflation. When you discount future liabilities with ever more negative real yields, those liabilities grow alarmingly.

    The LDI pension insurance industry faced the double whammy of significant bond market losses being compounded by margin calls on repo, inflation swap and OIS swap positions, meaning that they had to sell yet more gilts in order to cover these margin calls. Subsequently, the gilt market entered into something of a downward spiral, that it took BoE intervention to bring to a close. 

    What does this mean for regulatory reporting?

    On the first page of this working paper, the author places a quote prominently at the top of the page:

    “It was not quite a Lehman moment. But it got close.”

    (ref: Sep 2022, senior London-based banker).

    One of the outcomes of the last financial crisis was the additional regulatory reporting obligations that were placed on firms to ensure that both prudential and conduct regulators had sufficient transparency of derivative markets, securities financing markets and greater transparency of securities markets.

    This was achieved through the regulatory reporting regimes introduced post-crisis – EMIR, SFTR/MMSR/SMMD (financing & money markets) and a significant broadening of the MiFID transaction reporting requirements via MiFID II.

    These obligations allow regulators to quantify and respond effectively to the macro-systemic risks around solvency, market stability and concentration risks.  The Bank of England has been able to use this data; MiFIR RTS 22 transaction reporting (UK government bond, inflation linked and conventional ‘gilt’ markets), EMIR reporting (inflation & OIS swaps, UK gilt futures) and Sterling Money Market Daily (SMMD) reporting (UK gilt repo market) to produce this.

    Clearly, if the bank’s efforts were thwarted by low quality data stemming from firms’ transaction reports, the firms’ CEO and compliance officers would be the first to hear about it in no uncertain terms! Any reporting errors could lead to costly audits or investigations and potentially substantial fines and reputational damage. Firms need to ensure they have robust controls and procedures in place, including how accurately they report under these regimes.

    • Read the full working paper on the Bank of England’s website
    • If you have concerns about the quality of your transaction reporting under any of the regimes referenced in this blog or for a conversation with Jonathan Lee. Please contact us. 

     

  • SFTR: Which jurisdiction is the issuer?

    SFTR: Which jurisdiction is the issuer?

    ESMA publishes Q&A 15

    SFTR reporting is saddled with a number of hidden mysteries. The lack of regulatory certainty frustrates reporting counterparties, regulators and quality assurance providers alike. Any field, especially a matchable/reconcilable field that has multiple permissible answers will forever be a quandary. 

    The publication of ESMA’s SFTR Q&A 15 finally answers one of the great mysteries of SFTR reporting! 

    When reporting the jurisdiction of the issuer of either a loaned security (field 2.53) or a collateral security (field 2.92), the question has remained unanswered until now – which jurisdiction should be used?

    Question 15 was published in a new version of the SFTR Q&As by ESMA on 31 March 2023. The question raised is:

    “Should the fields 2.53 and 2.92 ‘Jurisdiction of the issuer’ be populated with the country code of the registered office of the issuer or of the country where the head office is located?”

    The answer ESMA has given is:

    “These fields should be populated with the country of the registered office of the issuer (fields 2.54 and 2.93 ‘LEI of the issuer’), corresponding to the ‘Legal address’ in GLEIF data.”

    In practical terms, always use the jurisdiction of the registered office (equivalent to incorporation) of the ultimate parent, or, if not known, the jurisdiction of the subsidiary if the issuer does not feature in the GLEIF database.

    • To read the latest Q&A, please visit ESMA’s website
    • For help navigating through the maze of ESMA and FCA rules around SFTR reporting, or for a conversation with Jonathan Lee, please get in touch.
  • UPDATED: A tale of inflation, solvency & regulatory jeopardy

    UPDATED: A tale of inflation, solvency & regulatory jeopardy

    We first published this article in November 2022 but given current market events, we’re republishing it this week with some updated opening paragraphs. 

    There is a common perception in securities trading that getting the timing right when taking positions in the market is far more difficult than having the right idea to begin with. In hindsight, the below blog, written in November 2022, was a classic example of this. Regulatory concerns I raised five months ago in relation to rising interest rates, badly positioned market counterparties, bond market losses, capital adequacy, solvency issues and fears of contagion were well placed, but four months too early…

    In a similar manner to government preparations for a flu pandemic in 2020, following the 2008-2011 financial crisis, regulators were well prepared for a series of credit events. Unfortunately, the pre-cursor to the current situation is not a credit event but an interest rate event, for which preparations are far less appropriate, regulators simply find themselves looking in the wrong direction. Regulators will be quantifying counterparty exposures, collateral concentrations, leverage, levels of collateralisation and evidence of any further systemic risks. The principal tools for identifying these risks include SFTR, MMSR, SMMD and the likes of PRA Liquidity Reporting. If this data is poor, regulators will be active in their response. For a conversation about your data quality, please contact us.

    ***

    21 November 2022

    The deflation that followed rapid Chinese industrialisation has kept interest rates on a declining and ultimately stagnant path for decades since the 1990s.  In recent years, interest rate and government bond markets could have been politely described as being as dull as ditch water.

    However, as with all things in the market, the trend is your friend, until it isn’t…

    UK Treasury 2050, 0 5/8% Bond Price – theoretically one of the safest investments…

    Source: London Stock Exchange

     

    Supply chain and booming inflation

    Supply chain issues stemming from Covid, compounded by the emergence of China as a new superpower with massive domestic consumption and to a lesser extent Brexit, saw the price of the long dated UK Gilt (above) dip from around 100 (or par) into the 80s in February 2021. This c.20% fall in value accelerated as war broke out in Ukraine in February 2022 resulting in a dramatic jump in global inflation, with central banks increasing official interest rates in an attempt to ensure that this inflation is transitory. The downward trajectory in UK bond prices troughed with the fallout from the misguided September UK mini-budget on 8 October 2022 when the price hit 36.40 – a fall of 64% in the 2050 Gilt price from its high to low.

    Rates markets have become sexy again

    Higher interest rates, volatility, differing views on inflation expectations all of a sudden bring bond markets, money markets and securities financing markets back into sharp focus. While this may be to the delight of rates traders, it will have been highly unwelcome by the pensions industry as the value of many of their key ‘low risk’ assets are needed to service pensioners of the future evaporated. The moves were so dramatic, some pension funds’ solvency was called into question, resulting in intervention by the Bank of England to support the Gilt market in October.

    What does all this mean for regulatory reporting?

    Central banks and regulators will be on heightened alert to identify large interest rate exposures, the effective transmission of official central bank interest rates, solvency issues, credit default risk and the potential for contagion. Trade and transaction reporting regimes are among their principle means of performing this supervisory oversight and analysis. This will encompass everything from MiFID, SFTR, EMIR, MMSR, SMMD, CFTC, FinfraG, SESTA and many more besides. When faced with something of a crisis or an emergency situation, there is a risk that regulators need to react quickly with punitive measures if their investigative work is thwarted by reporting data quality issues.

    Enforcement has been notable in its absence for a number of years, just don’t be too surprised if this now goes the way of the bond market.         

    • If your money markets reporting (under SFTR, MMSR & SMMD), your bond market transaction reporting (under MiFIR) and your interest rate derivatives reporting (under EMIR, CFTC, MAS & HKMA) is not in perfect order or you are unaware of how good (or bad) it is, please get in touch.
  • EU’s legislative procedure steps up the pace on revised MiFIR and MiFID II

    EU’s legislative procedure steps up the pace on revised MiFIR and MiFID II

    Matthew Vincent takes a look at what we might expect to see in the revised EU MiFIR Article 26, “Obligation to report transactions”.

    After many months of discussions starting from ESMA concluding its EU MiFID Review, the EU Parliament has caught up with the EU Council and has reached its own negotiating position on amendments to MiFID II and MiFIR.  We have now reached the “trilogue” stage during which time the Commission, Council and Parliament will work to agree on the final wording of the legislative text. Trilogues are set to commence in April and we expect to see the final legislative changes agreed during Q3 2023.

    Level 1 agreement though is only the start, as ESMA will consult and draft an amended RTS 22 before we really know all the details and the impact on firms.

    That said, a comparison of the two “negotiating” versions of the Level 1 texts gives us some idea of where we’ll likely end up by Q3.

    1. The short selling flag seems very likely to be removed as it has been removed from both versions.  
    2. The reporting obligation will probably be extended to derivatives “subject to the clearing obligation set out in Article 4 of Regulation (EU) No 648/2012 executed outside a trading venue.”
    3. Powers may be granted to ESMA to assess the possibility of extending the reporting obligation to include AIFM and management companies.
    4. The problems associated with TvTIC will probably not all be solved by its promotion to Level 1
    5. ESMA is also instructed to draft regulatory technical standards to specify:
    • The conditions for linking specific transactions and the means of the identification of aggregated orders resulting in the execution of a transaction.
    • The date by which transactions are to be reported.

    As always, the devil will be in the detail of the RTS and perhaps a revised set of guidelines will also be forthcoming.  But for now at least we can get ready to say farewell to the short selling requirements and do our collective best to avoid the temptation to say “we told you so”.

    • For a conversation with Matthew on the upcoming changes to EU MiFIR, please get in touch.
  • ESMA’s new SFTR validation rules – still playing roulette with data accuracy

    ESMA’s new SFTR validation rules – still playing roulette with data accuracy

    The highly anticipated new ESMA SFTR validation rules (and corresponding minor XML schema changes) were finally published on 8 March, coming into effect on 11 September 2023, leaving nothing but a damp squib in their wake.

    Having been pre-warned by ESMA that no new guidelines or the delayed SFTR Review were imminent, nor likely this year, it was something of a disappointment to find so little advancement on the path to regulatory certainty. This is a missed opportunity to enrich the ‘Conditional validations, format and content’ and ‘Details to be reported’ columns to capture new post-Libor interest rates, precise definitions of collateral/security type, and provide clarity around jurisdictions, haircuts and other contentious fields. We will continue to roll the roulette wheel as to whether “valid” reports are right or indeed remain “valid but wrong.”

    The changes only affect the ‘General information’ and ‘Cpy_Transaction’ tabs. General information simply clarifies that correction “CORR” messages can only be used to repair loan data or loan and collateral data but not only collateral data. Any collateral changes, corrections or not, should be made using a collateral update “COLU.”

    The ‘Cpy_Transaction’ tab contains the bulk of the changes:

    • The additional sector classification field (1.6) has now been made consistent across all action types, conditionally required for errors, early terminations, collateral updates and valuation reports.  
    • Unique transaction identifiers (UTI) (Field 2.1) are now mandatory for repo, buy-sellback and securities lending collateral updates where collateralization of net exposure is false. This does close a loop-hole and ensures collateral can be more easily accounted for.
    • Type of collateral component (2.75) has had conditional validations clarified, around the need for it to be populated for corrections containing collateral information and position components. This removes the previous anomaly where it required for corrections and position components, even on uncollateralised securities loans. 
    • Collateral unit of measure (2.84) is no longer required under any circumstances for securities lending trades. This is slightly curious as it is still permissible (albeit highly unlikely) to have commodities collateral on a securities loan.
    • Haircut or margin (2.89) – still misnamed (margins are not acceptable), has a single somewhat confused additional condition that “The absolute value of this field should range between 0 and 100.” However, quite rightly it still allows negative as well as positive values and capping it at 100 only partially prevents the incorrect reporting of initial margins (as opposed to haircuts) as specified in the “Details to be reported.” The cap could have been set rather lower than 100 to make this condition truly effective.
    • Finally, the Level field (2.99) has been tweaked, no longer required for new or modified margin loans (only transaction level reporting is possible) and the position component action type (have you ever seen one?!) is only valid for transaction level reports.  

    That’s all folks! Hopefully the UK FCA will follow suit without delay, preventing two-speed SFTR re-occurring later this year and into 2024.

  • MiFID II reporting five years on: The future of post-trade transparency reporting

    MiFID II reporting five years on: The future of post-trade transparency reporting

    MiFIR trade & transaction reporting was five years old in January. In the third of our blog series on MiFIR, Chris Machin reviews what’s ahead for MiFIR post-trade transparency reporting in Europe and the UK.

    As mentioned by Simon Appleton in part two of this blog series, there has been significant focus on post-trade transparency (PTT) reporting in the last year by both the FCA and ESMA.

    Since the foundations of MiFID II were put in place in 2018, the main area of consternation has been RTS 2 non-equities (rather than the vanilla RTS 1 equities). Leading up to go-live, the industry had been clear that bracketing all non-equities into one RTS wouldn’t work. If we could start again, segregating out OTC derivatives from bonds and the other asset classes would be essential. Five years on, this debate still painfully rumbles on.

    What we are now seeing post-Brexit, is an interesting mix of divergence and convergence from the UK and EU regulators, with a common debate around liquidity vs transparency.

    ESMA issues positive opinion on amended RTS 1 and 2

    ESMA loves to share an update just before a holiday season and so it did just before Christmas 2022, confirming its support for the European Commission’s proposed amendments to the regulatory technical standards on RTS 1 and RTS 2. The amendments are an attempt to establish increased transparency, strengthen data integrity and availability, and create a level playing field. However, it should be noted that this was the same mandate and message used more than five years ago when MiFID II went live in January 2018.

    So, is anything actually changing? And is ESMA’s approach in line with the potential changes announced by the FCA in its post-Brexit consultation paper earlier last year?

    Liquidity vs transparency

    Liquidity vs transparency, as mentioned earlier, is still the burning argument. By increasing transparency, will this improve liquidity?  A consolidated tape has been proposed since 2014 as consolidated tape providers (CTPs) were listed amongst approved publication arrangements (APAs) and approved reporting mechanisms (ARMs) as data reporting service providers (DRSPs), but none have materialised to date. It’s complex. The industry sees shares and bonds in scope for consolidation, but the complexity of OTC derivatives is still a derided topic, with trade associations like ISDA at the forefront of lobbying what members are saying. Is a derivatives tape needed? There’s also the terminology of MiFIR Article 13 and ‘reasonable commercial basis’. How do the exchanges and APAs feel about this when data sales are a big revenue driver for them?

    Dark pools/trading

    Limitations on dark trading and moving to a single volume cap have been discussed and in practice for a while. But ESMA’s latest update demonstrates how it is diverging from the UK.  ESMA is trying to increase transparency with the aim of encouraging trading on lit markets, by keeping the cap in place, whereas the UK is trying to increase liquidity by reducing these restrictions and pulling back the liquidity that was lost when the UK exited the EU.

    Clarity on transparency fields

    Clarity on transparency fields is welcomed although the somewhat ambiguous ‘price’, ‘quantity’ and ‘notional amount’ are not always relevant, depending on the asset class being traded. More clarity is required on defining non-price forming transactions and deferrals aside, however it will be interesting to see how 2023 plays out.

    FCA’s update on MiFIR transparency

    ESMA’s opinion still needs to be negotiated through the European Parliament and it is likely the new ‘Manual’ described in the guidance, will replace or co-exist with the transparency Q&A, whereas in the UK, HM Treasury has given the FCA the power to change the rules accordingly.  

    With the FCA, we know the share & derivatives trading obligations (STO & DTO) have to change as the statements from the respective articles 23 and 28 in the regulation no longer apply now the UK has segregated. Traded on a Trading Venue (ToTV ) is questionable but the biggest draw may be the delineation of the systematic internaliser (SI) regime from the reporting responsibility.  It seems that this responsibility will be at entity level which still brings uncertainty around communication of status between SI and the Non-SIs and buy-side.  A central evergreen source is needed, something like Smartstream RDU’s SI register which was made available in preparation for 2018.  This was crucial to market participants and APAs alike on the identification of who has the publication obligation, given RTS 1 and 2 post-trade transparency reporting is single-sided.

    Though trying to achieve extra transparency, the regulators need to keep one eye on creating undue risk in the market to those that are providing the much needed liquidity. On the UK side, there is mention of change in deferral flags, providing more precise information and less ambiguity, but caution should persist. RTS 1 and 2’s goals were OTC price transparency, level playing fields, and encouraging investor confidence, whilst reducing investor risk and allowing informed investment decisions for all. If the FCA and ESMA keep this in mind as 2023 progresses, taking on the feedback from the industry, the battle of liquidity vs transparency could harmonise into achieving both, a match made in heaven!

    • For a conversation with Chris about the upcoming changes to RTS 1 and 2 requirements or a free healthcheck of your MiFIR post-trade transparency reporting, please contact us.
  • What took so Elon-g?

    What took so Elon-g?

    A breakdown of Twitter shareholding lawsuit

    Elon Musk is being sued due to his delayed shareholding disclosure of a large stake in Twitter from March 2022.  Under US law, anyone who acquires more than 5% of a class of voting equity securities must disclose their holdings to the SEC within ten calendar days, Musk failed to do this and only disclosed 21 days after acquiring the disclosable amount, taking more than double the length of time required by law. 

    Twitter share price jump

    Once Musk announced his 9.2% stake, the share price jumped 27% from US$39.31 to $49.97.  This indicated two things about the 11 days preceding Musk’s eventual disclosure:

    • Musk was able to continue to buy shares at a lower share price, amassing his stake for a cheaper price. It has been estimated that he saved approximately $200 million as a result of this
    • Anyone selling shares during this time would have sold them for below their true value.

    Earlier this week Musk asked a US judge to throw out the lawsuit, denying that this was a deliberate attempt to defraud.  The case is still ongoing.

    What the Elon Musk case tells us about shareholding disclosures

    We can see from this example why disclosing on time is important, however shareholding disclosures are important for many other reasons. They provide transparency to the market, the issuer, and the relevant regulator, about positions and voting rights that are being accumulated. 

    These regulations have a common purpose but differ greatly across the world.  In the US, shareholders are to calculate exposure through shares and some physically settled derivatives of the same class (excluding put options and anything that isn’t exercisable within the next 60 days) and report anything above 5% within ten calendar days.  This is a longer time frame than many other countries such as Hong Kong, Japan, China and most European, where the reporting deadline is normally between two-five business days.  These countries also include cash-settled derivatives in their holding calculations, something that was brought about after the Volkswagen short squeeze in 2008. The SEC has made some proposals to bring the US requirements in line with those of its international peers including shortening the disclosure deadline to five days and the inclusion of cash-settled derivatives.  These proposals are currently under consideration following the public comment period.

    Better monitoring for Musk

    Musk has made it known that he has fulfilled these obligations in the past for other issuers, including Tesla Inc, on multiple occasions, and is claiming this late filing was ‘inadvertent’.  If this is the case, we can only suggest that Musk puts better monitoring in place to prevent this from happening again in the future.

    At Kaizen our fully automated, customisable solution will calculate your holdings under each jurisdiction, allowing for increased efficiency and accuracy. Our service processes your position and trade data and alerts you to your disclosure obligations. We also provide the option to export your disclosable holding on to the relevant regulators forms. Using our solution means that you save time and remove the risk of human error and late reporting.

    Did you know there are over 100 countries globally that have a form of Substantial Shareholding Disclosure requirements?  We cover those too.

    • For a demo of our Shareholding Disclosure Service, or for a conversation with Sam or one of our regulatory specialists, please contact us.
  • How-to Guide: SFTR repo day-count conventions

    How-to Guide: SFTR repo day-count conventions

    Day-count conventions – a land of confusion

    Anecdotal evidence from regulatory testing, reported data, questions we’re asked and the helpdesk queries we receive indicate that confusion reigns when it comes to repo market day-count conventions. This is an issue both in terms of ensuring SFTR reports are accurate but also an issue as a matchable field reconcilable at the Trade Repository (TR).

    Market craves standards and best practice

    The problems arise primarily from two factors:

    1) A tendency to report the underlying collateral bond interest accrual day-count convention instead of the correct repo interest convention.

    2) The prevalence of a large number of irrelevant conventions (in the context of SFTs) on the ESMA/FCA validation rules list of options including many bond coupon conventions and derivative interest conventions too.

    Very tellingly, the latest proposals from the Office of Financial Research in the US state that they believe the ISO 20022 definitions to be too broad and that they were going to insist on everything being reported on the US market convention Actual/360 basis.

    Until now, there simply has not been a definitive guide to which day-count conventions to use in which markets.

    Only two repo day-count conventions in regular use

    In the vast majority of cases, we foresee only two of the listed day-count conventions being relevant and correct when reporting repo transactions. While not all market participants will necessarily follow the market convention associated with the particular market in question, nevertheless, they tend to abide by Actual/360 or Actual/365. In rarer cases, we see Actual/Actual (notably in Russia). We would also expect these to be repo market specific conventions and not derivatives related ISDA ones for example. Indeed, if the SFTR reported convention is not A004 or A005 and it is a major market, the reported convention is quite probably incorrect.

    Actual/360 covers Euro, USD, JPY (international) and CHF

    In the Euro, USD, CHF and international repo markets in Japan, Canada, Australia and New Zealand, the standard convention is Actual/360 , the actual number of days interest (the numerator), divided by an assumed 360 days in a year (the denominator). This is denoted under SFTR as A004.

    Actual/365 covers Euro, USD and JPY (domestic) 

    In the UK and Japanese, Canadian, Australian and New Zealand domestic markets the convention is Act/365 Fixed, the actual number of days interest divided by 365 days in a year, regardless of leap-years. This is denoted by A005.

    Japan, Australia, New Zealand and Canada conventions differ between international and domestic. Do not be surprised to see repo trading under the international (Actual/360) convention in the repo markets in any of these jurisdictions.

    There are some smaller markets such as Brazil (that uses a business day convention) and Burundi, Ethiopia and Rwanda that use an Actual/364 convention that would need to be reported using the free-text option. This option should only be used when reporting activities in smaller, non-standard markets. The ICMA provide some guidance on the reporting of unlisted conventions in recommendation 5.17 of its recommendations for reporting under SFTR. Using this as a context for the reporting of non-standard conventions should limit instances of TR reconciliation breaks on this field too.

    NB: When referencing domestic repo markets, this relates to trades between two onshore counterparties, potentially on a domestic platform or venue, settling in the domestic location, often using a domestic interest rate, e.g. Tibor in Japan. International repo trades are typically cross-border, off-exchange (although some is now exchange traded), cleared through an  International Central Securities Depository (iCSD) such as Euroclear and executed using an internationally recognised common rate standard.

    Day-count conventions and SFTR codes per jurisdiction

    Actual/365F (A005 SFTR)

    Actual/360 (A004 SFTR)

    Actual/Actual (A006)

    UK

    US

    Russia

    Japan (domestic)

    EUR

     

    Australia (domestic)

    Japan (international)

     

    Canada (domestic)

    China

     

    Israel

    Switzerland

     

    India

    Sweden

     

    New Zealand (domestic)

    Denmark

     

    Singapore

    Norway

     

    South Africa

    Australia (international)

     

    South Korea

    New Zealand (international)

     

    Taiwan

    Canada (international)

     

    Thailand

    Turkey

     

    Sri Lanka

    Mexico

     

    Kenya

    Argentina

     

    Kuwait

    Algeria

     

    Malawi

    Angola

     

    Malaysia

    Bahrain

     

    Mauritius

    Barbados

     

    Pakistan

    Botswana

     

    Poland

    Bulgaria

     

    Tanzania

    Chile

     

    Zambia

    CFAF

     
     

    Colombia

     
     

    Congo DRC

     
     

    Czechia

     
     

    Egypt

     
     

    Hungary

     
     

    Iceland

     
     

    Indonesia

     
     

    Morocco

     
     

    Oman

     
     

    Philippines

     
     

    Qatar

     
     

    Romania

     
     

    Saudi Arabia

     
     

    UAE

     
     

    Vietnam

     
     

    WAMU

     

     

     

     

    • If you have any concerns about the quality of your firm’s SFTR reporting or require training, please contact us to discuss your requirements.
    • Many thanks to Richard Comotto for his assistance in compiling this list. 
  • MiFID II reporting five years on: what does the future hold?

    MiFID II reporting five years on: what does the future hold?

    MiFIR transaction reporting is five years old this month. In the second of a three-part blog series on MiFIR, our reporting director Simon Appleton looks ahead at some of the upcoming changes expected in Europe and the UK.

    Status check

    Five years after MiFID II’s implementation and nearly three years after Brexit, the EU and UK transaction reporting regimes are under review.  Both regimes are generally working well hence, in the UK for example; other parts of MiFID appear to be being assessed with a greater sense of urgency, such as Post-Trade Transparency.

    Transaction reporting data quality has improved steadily over the last five years, albeit accuracy levels vary greatly across firms, asset classes and data fields. Firms conducting deep, regular testing have seen reporting standards improve significantly and those with robust control frameworks have seen the greatest progress.

    However, the fact that only a third of the investment firms reporting under UK MiFIR have requested data via the FCA’s Markets Data Processor, confirms that two-thirds (over 850 UK MiFID investment firms), are at risk of being in breach of their reporting obligations.

    Pre-MiFID an independent review established that there is no viable alternative to transaction reporting that would allow regulators to monitor investment firms and markets effectively. Regulators are increasingly describing themselves as being data-led and so clearly the receipt of accurate, complete and timely reports has never been so crucial.

    MiFID transaction reporting in the UK

    Given that the rules were implemented five years ago, the FCA is reviewing its policy options to ensure that the reporting regime is not only effective but also efficient for firms and that the requirements are not disproportionate when compared to the benefits. They will be aware of the impact of divergence from EU MiFIR but will also want what works well for UK firms and the FCA.

    The FCA will be very considered in its approach to reviewing the transaction reporting requirements. This will allow it to determine which parts of the regime need to be updated, taking into account feedback from industry, as well as experience gained since 2018. 

    Which aspects of the technical standards, guidelines and Q&A require amendment or additional clarity and guidance for firms? Areas such as corporate actions and the reporting of swaps are ripe for review.

    In addition, before considering when to engage with industry, the FCA needs to absorb the UK Treasury’s:

    The Treasury’s policy statement for “Building a smarter financial framework for the UK” and Edinburgh Reform plans were both only published last month, so the publication of the FCA’s transaction reporting discussion paper (DP) may be some way off.

    Areas of likely change in the UK

    • Removal of the Securities Financing Indicator: the requirement to report securities financing transactions (SFTs) under UK MiFIR ceased with effect from 31 March 2022 and so this field is effectively redundant
    • Changes to the OTC Post-trade indicator: Given the UK Treasury’s Wholesale Markets Review it is highly likely that there will be changes to the applicable values for this field
    • Removal of the Short Selling Indicator: Given previous communication from the FCA, it would be highly surprising if they did not follow ESMA’s lead and remove the Short-Selling Indicator
    • OTC derivatives and crypto: The reporting scope for OTC derivatives is to be considered, as will the development of Unique Product Identifiers (UPIs), which could help resolve issues with the use of ISINs. Crypto-related instruments could form part of the discussion given the expected greater scrutiny on these
    • Cross-regime alignment: The UK Treasury is keen to understand where overlaps lie between MiFID II and EMIR reporting and where different reporting formats are used. Given the significant differences between the two regimes as to what constitutes a reportable event or valuable information, it’s anticipated that the use of consistent and international data standards, reportable values, formats and methodologies is where further efficiencies can be made. MAR and Benchmark Regulation are both likely to form part of the cross-regime analysis
    • ESMA’s proposals: The FCA will consider which proposals from the EU’s review (below) will form part of the forthcoming discussion paper.

    EU review of MiFID transaction reporting

    ESMA’s proposals for changes to transaction reporting under EU MiFIR were published back in March 2021 and so the EU’s review is much further advanced than the UK’s. As a reminder, the headline changes include:

    • AIFMs and UCITS management companies providing one or more MiFID services to third parties will be required to transaction report for the first time
    • Replacement of the “Traded on a Trading Venue” (ToTV) commonalities concept with a simplified “SI approach” for determining whether an OTC derivative is reportable
    • A new field, a Buy-back Programme flag, to identify trades in buy-back programs conducted on behalf of an issuer
    • Introduction of a MiFID client categorisation flag, to identify whether the transaction was for a professional, opted-up professional or retail client.
    • Replace ‘INTC’ with a unique code to the reporting firm when aggregating orders across more than one client
    • Removal of the Short Selling Indicator.

    In December 2022, the EU Council announced that it had voted in favour of final compromise amendments to the commission’s MIFID II and MiFIR proposals in the EU MIFID Review. The texts will represent the council’s negotiating position for trilogues, which are expected to commence around Q2 2023 (as the European Parliament is still working towards its final compromise position in Q1).  

    The MiFIR Article 26 level 1 text, dated 16 December 2022, was published on 21 December 2022 and includes reference to other additional information, for example, the due date for the transaction report, which could prove challenging for firms in certain scenarios. The short-selling flag has indeed been removed and a new designation for aggregated orders has been included.  For the detail though, we will have to wait for the revised RTS 22.

    Estimated timelines for implementation are contained within a recent Kaizen blog.

    Focus on data quality

    Regulators, both in the EU and the UK have frequently stated the importance of accurate reporting to support them maintain clean and orderly markets. They remain unlikely to look kindly on a firm when either mis-reporting has hampered a market abuse investigation, or where they fail to act upon observations made by regulators, either through general communications (e.g. Market Watch newsletters) or through those made directly to firms. 

    It’s now nearly 30 years since the Investment Services Directive and 2023 looks likely to be a busy year as ESMA’s MiFIR review leads to its legislative conclusion and the UK FCA digests the impact of the government’s reforms.

    Read the first part of this blog series MiFID II reporting five years on: a retrospective.

    • We at Kaizen will stay on top of any developments and continue to work with new and existing clients to detect and remediate their reporting issues. 
    • For conversation with Simon about anything raised in the commentary above, please contact us.
  • EMIR Refit 2024 – Five key changes every EEA & UK company should know

    EMIR Refit 2024 – Five key changes every EEA & UK company should know

    ESMA recently published the final reporting validations for EMIR Refit for European (EEA) based firms.  As firms prepare for the go-live date of 29 April 2024 (Europe) and 30 September 2024 (UK), this article highlights some of the key changes that firms face for derivatives reporting under EMIR.

    1. A large number of changes to the reportable fields

    There’s no better place to start than the data fields themselves. In short, the vast majority of fields will change. The addition of 89 new fields, the withdrawal of 15 and updates to the name, definition or format of how to report a field. 

    This brings the total number of reportable fields from 129 to 203, which is twice the size of MiFIR trade and transaction combined, and even outstrips the weighty SFTR reporting requirements.

    A lot of the additions are logical, such as asset class specific fields, the removal of ‘Beneficiary’ and ‘Trading Capacity’ (something I’ve championed for some time). Other fields will be more of a challenge for firms, specifically ‘Clearing Threshold of Counterparty 2’, ‘Reporting Obligation of Counterparty 2’ and ‘Corporate Sector of Counterparty 2’ require firms to know more detail on the counterparties they have traded with in order to fulfil their own reporting obligation.  I expect that ‘Prior Unique Trade Identifier’ and ‘Subsequent Position Unique Trade Identifier’ will be difficult for many firms.

    2. EMIR reporting via XML

    Next, the way to report these fields will change. Firms have long favoured the flexibility of reporting in CSV, chiefly due to its ‘pick up and go’ style.  With no need for specific CSV training, organisations could simply populate fields and amend the same submissions when they encounter validation errors. 

    EMIR reporting will be the latest derivative regime to adopt XML submissions using ISO 20022 standards, as favoured in the CDE Guidance.

    But the move to XML submissions is a heavy lift, and is the primary reason why the proposed changes will be implemented in 18 months, rather than the usual 12. The corresponding benefits of this change are important. They include a much more ‘level playing field’ for reporting to a trade repository (TR), whichever repository you use. And porting between TRs will be much easier given the uniform format across jurisdictions.

    On the flip side, multiple TR specific submission specifications across the same derivatives reporting regime is far from ideal. Further to this, the ability to add repository specific fields in my opinion only adds work, confusion and ambiguity for reporting firms within a regulation that is already complicated enough.

    3. Inter-TR reconciliation pulled into regulatory documentation

    This change has been a long time coming, but the Inter-TR reconciliation process is now being formally dictated. I remember being present at the first Inter-TR reconciliation meeting between EMIR trade tepositories, who, in earnest, wanted to create a suitable reconciliation process for separate submissions, but with virtually no guidance from the regulators on what was required or how to achieve it. Six trade repositories, six different preferred ways to achieve it! That said, the smart folk at the TRs agreed on a process reasonably quickly, but the formalising of this inter-TR reconciliation process is welcome, and comes with some significant improvements –  such as the minimum time requirements (10am next day), and later, explicit requirements for the TRs to send mismatched fields with corresponding data to the firms each day.

    One subtle but sensible proposal from the FCA/BoE for UK EMIR reporting has been not including the reconcilable fields and their tolerance levels in the technical standards. Instead they will be provided as guidance, allowing for relatively quick amendments, and avoiding any unduly high mismatches relating to the reconciliation criteria.

    This trial and error approach is unusual, but sensible in its rationale, indicating that the slow and steady approach may be the most pragmatic going forward.

    4. Unique Product Identifiers (UPI)

    Long before EMIR came into force in 2012 and reporting began in 2014, the industry had not been able to agree on a unique reference type for identifying product types. As a result, EMIR has had over seven years of reporting with a mix of ISINs, Classification of Financial Instrument (CFI) codes with other fields, and sometimes nothing at all! Interpretation of these identifier related fields has been widespread, often confused and almost always inconsistent.

    The use of CFI codes is often wrong, and simply doesn’t correspond to the same data reported elsewhere in the same report (such as delivery type). Indeed populating just the first two characters of six, leaving the remaining characters as XXXX (for example JRXXXX) is unfortunately an all too common misconception. The introduction of the UPI under ANNA DSB is therefore a welcome improvement. One centralised place for UPIs will surely reduce inconsistency and importantly, will hopefully reduce the volume of reportable fields in the future, as many separate data fields can be obtained from the UPI.

    But these advantages will not be without cost and effort for firms. Firms will need to apply for UPIs, and will be charged for the pleasure of doing so.

    They will also need to allow enough time to have a UPI allocated and still adhere to its T+1 reporting requirement, or otherwise need to make regulatory notifications for missed/late reporting. This will require planning with checks and balances in place for derivatives trading firms, banks and asset management houses, especially when new derivatives are executed.

    5. Unique Trade Identifiers (UTIs)

    Rounding up the top five important changes, the consultation paper has made changes to the use of the Unique Trade Identifier. Unlike the UPI, reporting firms are well versed on the use and merits of the UTI, which has been used since reporting inception.

    The changes to the UTI’s format are not ‘show stoppers’ (e.g. no special characters), and are generally welcome, but the revision of the UTI generation waterfall will prove challenging for many reporting counterparties.

    Today, firms are expected to agree bilaterally who will create and disseminate a UTI, so that both counterparties to a trade can meet their T+1 reporting requirement. Where no agreement exists, firms fall back on the UTI waterfall for generation of this identifier. Under these new proposals, the bilateral agreement between firms is no longer the default choice, and falls much further down the waterfall, following Critical Data Elements (CDE) guidance, with significantly more prescriptive steps inserted above, dictating which firm should create the UTI for different reporting situations. Market participants will argue the benefits of such an approach are primarily aimed at global reporting harmonisation, and many will comment that the flexibility of the bilateral agreement as default option is the strength of the process, and the most flexible option too. One welcome change here has to be the specification that the UTI must be provided to the other firm by 10am T+1, allowing both firms to report their trade on time.

    One more thing…

    I hope this blog has helped to highlight the significant size and scope of the amendments under the EMIR Refit, and the granularity to which changes are being applied. One notable addition to this list is the requirement to amend all outstanding derivatives to adhere to these new technical standards within six months from go-live.  This easily missed requirement is no small feat, and could present problems for firms that may not have all the required data points for historically executed derivatives.

    The move to harmonise derivatives reporting globally via the Regulatory Oversight Committee’s CDE Guidance (formerly issued and overseen by CPMI IOSCO) is a welcome enhancement, and will hopefully help to achieve a high quality of reported data, as desired by ESMA, but may undoubtedly result in a significant change request for firms caught by EMIR reporting.

     
  • MiFID II reporting five years on: a retrospective

    MiFID II reporting five years on: a retrospective

    MiFIR transaction reporting is five years old this month. In the first of a three-part blog series on MiFIR, Kaizen’s regulatory subject matter expert Matthew Vincent looks back at the origins of the regulation and some of the significant changes that have occurred since go-live.

    Let’s start with some positives. The additional data captured by MiFIR transaction reporting has improved regulators’ ability to monitor and detect for market abuse whilst firms have made significant efforts to get their reporting correct and remediate mistakes of the past.

    On the flip side, whilst the regulation may have harmonised reporting requirements which was positive for the industry, differences of interpretation still arise which could potentially be resolved more quickly. In addition, the changes and centralisation have resulted in a loss of flexibility and responsiveness to change. 

    There is no doubt that the industry has congratulated regulators for their efforts in producing the reporting guidelines however, as experience has shown, you can never quite find a guideline that matches the exact scenario that you are trying to report.

    Why transaction reports?

    For UK and EU regulators transaction reports are essential to allow them to monitor for market abuse and maintain orderly financial markets. Without reports regulators would be blind to any market abuse that might occur.

    “Accurate and timely reporting of transactions is crucial for us to perform effective surveillance for insider trading and market manipulation in support of our objective to ensure that markets work well and with integrity.” – FCA, April 2015

    Transaction reporting within the European Economic Area (EEA) can trace its history back to 1993. Since then, the obligation on firms has steadily increased with MiFID I introduced in November 2007 and MiFID II/MiFIR in January 2018.

    How was MiFIR different to previous reporting obligations?

    The obligation to report and the details to be reported were incorporated into a regulation not a directive, limiting the ability of member states to implement different rules.  Some interpretation differences arise although these are subtler than historically.   

    • The data to be reported increased from 24 fields to a maximum 65 fields
    • The scope of reportable instruments was broadened to include ‘over the counter’ derivatives and certain derivatives over FX, commodity and interest rates.
    • Data quality checking and reconciliations became legally mandated in RTS 22, Article 15. 
    • ESMA produced guidelines and Q&As to assist firms with implementation of the regulation.

    What’s changed since January 2018?

    ESMA Q&A on MiFIR data reporting

    The document predates MiFIR go-live with the first question answered April 3 2017.  A further 13 questions have been answered with the latest in September 2020.

    ESMA validation rules – valid but wrong

    The validation rules are designed to improve the quality of the data received.  There have been five versions with incremental changes made over the course of the five years.  All until version 1.5 were applicable to both UK and EU regulated firms.  Versions 1.6 and 1.7 have been optional for UK regulated firms and UK ARMs alike. 

    However, validation rules can only go so far in improving data quality.  The validation rules capture approximately 400 data quality issues. Regulators have stressed that passing validation is not the only way a firm should validate its data quality.  Our comprehensive quality testing demonstrates that there are many more ways of reporting valid but incorrect data.

    “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.” – FCA Market Watch 59 (April 2019)

    “The CSSF continuously monitors the quality of the transaction reporting data. During the last year, the CSSF not only carried out the standardised quality tests developed together with the other competent authorities and ESMA, but also conducted a series of data completeness and quality enhancement campaigns.” CSSF, February 2022

    Data Reporting Services Providers (DRSP) regime 

    Immediately post MiFIR go-live, Approved Reporting Mechanisms (ARMs) were supervised by their National Competent Authority (NCA).  On 1 January 2022, ESMA took on its new mandate as direct supervisor and now supervises firms that represent almost 99% of the transactions reported by an ARM.

    This is unlikely to have an immediate effect on firms – although there have been some concerns raised about the additional costs of this supervision. But in time this should further harmonise the implementation of the regime across member states in the EU.  UK ARMs are still supervised by FCA. 

    Brexit – limited impact so far 

    So far, the impact of Brexit on reporting firms has been limited. For example, UK nationals must now be identified using their passport numbers when a report is made to an EU competent authority – yet should still be identified using the National Insurance number when a report is made to the FCA. Other alterations have had to be made as the status of UK venues has changed, when reporting to the EU and that has impacted the way in which certain fields should be populated, TVTIC, Pre-Trade Waiver and Country of Branch Membership.  A more significant change has been to the ‘in-scope instruments’ with the introduction of UK FIRDS, and the most recent change that came into effect on 30 December 2022 are the changes to the exempt securities under the UK short selling regulation. 

    Supervisory priority

    The only significant supervisory change was made by the FCA on 13 January 2022 when the regulator announced it was in the early stages of considering policy options for the UK reporting regime which included the future of the short selling indicator.  

    “Until the future of the short selling indicator field…has been determined, we will not take action against firms who do not meet these requirements. We do not expect firms to notify us about issues affecting the short selling indicator field through an errors and omissions notification form. We will keep this position under review.” – FCA, January 2022

    Validation rule – January 2023

    This month’s five year anniversary is marked by the awakening of validation rule – 269 which states the trade date cannot be earlier than five years before the submission date. Where this is the case, reports will not be accepted by the NCA and the firm will receive a CON-281 rejection.  Hence, firms will no longer be able to correct some mistakes of the past.

    What hasn’t changed at all?

    ESMA’s table thumping Guidelines – Transaction reporting, order record keeping and clock synchronisation under MiFID – has been the go-to place for firms seeking guidance for their implementations. It is somewhat surprising that there hasn’t been a single revision to any one of its 291 pages since it was last corrected on 7 August 2017.   

    Some final thoughts

    Fields like TVTIC and the short sell indicator have been difficult to implement, and we expect some of these issues to be addressed in the next iteration of the regulation.

    In our second blog in the series Simon Appleton will look ahead at the changes to MiFIR reporting we are expecting to see this year and beyond.

  • SFTR ‘ish’ USA

    SFTR ‘ish’ USA

    New daily reporting obligations for bilateral repo trades have been proposed in the US. Our regulatory subject matter expert Jonathan Lee looks at the background to the announcement and reviews what’s being proposed. 

    It’s been a long time coming…

    The G20 Financial Stability Board agreed a mandate to enact securities financing reporting at the end of 2015 as a direct result of the last financial crisis. There were significant concerns stemming from the crisis about the role played by ‘shadow banks’ (non-banks offering credit intermediation) and the repo, securities lending and margin lending markets. Given how opaque the US repo market remains, recent market episodes and rising rates have raised alarm within the US Treasury and have heightened the need to implement Dodd Frank Act responsibilities. Finally we’re starting to see signs of SFTR USA, albeit a rather piecemeal, fragmented affair in comparison with the European regulation. The US approach is also significantly more pragmatic and cost-focused.

    Since November 2019, the only SFT data collection taking place was a process where the Office of Financial Research (OFR) of the US Treasury department took details of centrally cleared funding transactions in the US repo market directly from the DTCC, together with tri-party repo activities facilitated by Bank of New York acting as tri-party agent. In March 2022, the SEC released a consultation to start to tackle reporting requirements for the US securities lending market (Regulation 10c-1) but further feedback on the results of that consultation remain imminent. This leaves a significant gap for reporting of the US uncleared bilateral repo market.  

    Reporting regime for US uncleared bilateral market proposed

    On 5 January 2023, the OFR published a 60-day consultation on implementing a reporting regime for the US uncleared bilateral repo market. Responses to this consultation are due on 6 March 2023 (OFR reserve the right to extend this). This follows a pilot data collection study conducted by the OFR over three days in June 2022, in which nine dealers volunteered to take part. This new proposal, in conjunction with the SEC proposals covering securities lending will start to bridge the significant regulatory gaps in the US SFT market reporting coverage. The OFR found that the gap represents 60% of total repo lending by primary dealers and 37% of total repo borrowing.

    Approximately 40 US repo counterparties in scope

    At present, the proposals will focus on a reporting requirement for US brokers, dealers and other financial counterparties whose extended guarantees in the uncleared repo market exceed $10 billion, with these approximately 40 market counterparties accounting for more than 90% of the market by volume. In addition, they propose to capture any other financial companies with over $10 billion in extended guarantees where non-cleared borrowing from non-broker, non-dealer lenders takes place to prevent any data gaps now or in the future.

    ISO 20022 – field definitions ‘too broad’

    The OFR is considering reporting in either its own data elements format or the existing definitions under the ISO 20022 format. However, its initial thought is that ISO 20022 field definitions are too broad for its purposes. For example, the OFR wants all rates to be quoted on an Act/360 day-count basis, not using the 14 permissible conventions in ISO 20022 schemas. Primary focus is on reporting by borrowers (collateral givers).

    Current proposals include:

    • Trade executed under (but not limited to) Master Repurchase Agreements (MRA) and Global Master Repurchase Agreements (GMRA)
    • To potentially exclude sell-buyback as well as any securities lending transactions
    • Collection of in-scope transactions settled internationally or denominated in currencies other than USD would be included to prevent regulatory avoidance and to provide greater insight into cross-border activities.

    OFR repo reporting looks set to establish LEI and UTI as truly global standards

    • To adopt Legal Entity Identifiers (LEIs) to identify market participants
    • To adopt Unique Transaction Identifiers (UTIs) for ease of systemic risk monitoring.

    Required fields currently limited to 33 (vs. 155 in Europe)

     

    33 Reportable fields are proposed

    File observation date

    Trade timestamp

    Floating rate

    Covered reporter LEI

    Start date

    Floating rate reset frequency

    Cash lender LEI

    End date

    Spread

    Cash lender name

    Minimum maturity date

    Securities identifier type

    Cash borrower name

    Cash lender internal identifier

    Security identifier

    Cash borrower LEI

    Cash borrower internal identifier

    Securities quantity

    Guarantee

    Start leg amount

    Securities value

    Netting set

    Close leg amount

    Securities value at inception

    Transaction ID

    Current cash amount

    Securities value currency

    Unique transaction ID

    Start leg currency

    Haircut

    Trading platform

    Rate

    Special instructions notes or comments

     

    The consultation in full, together with its supporting documents, can be accessed here.

    Responses to the consultation can be submitted online or by mail to: Office of the Chief Counsel, Office of Financial Research, 717 14th Street NW, Washington, DC 20220.

    • For a confidential discussion about the quality of your existing SFT and money market reporting obligations or impending US obligations, please get in touch.
  • What’s the latest with ESMA’s MiFIR Reporting Review?

    What’s the latest with ESMA’s MiFIR Reporting Review?

    In this blog we look at what’s happening with MiFIR Reporting in Europe and what we can expect to see in 2023 and beyond.

    Under the mandate granted by MiFIR Article 26(10), ESMA shall submit a report to the Commission on the functioning of Article (26); a consultation on MiFIR began 24 September 2020 and the conclusion summary report was released on 23 March 2021.

    The report contains recommendations and possible legislative amendments to MiFID II/MiFIR to simplify the current reporting regimes yet maintaining the quality and ensuring the usability of the reported data.

    The headline changes are as follows:

    • Replacement of the TOTV concept with the SI approach for OTC derivatives, bearing in mind the conclusions of ESMA’s Final Report on the transparency regime for non-equity instruments and the trading obligation for derivatives
    • Removal of the short sale indicator
    • Alignment with other regulations e.g., MAR, EMIR and the Benchmark Regulation
    • The reliance on international standards, including LEIs, ISINs and CFIs; and
    • The inclusion of three additional data elements to harmonise the way that they are reported and to avoid inconsistent and duplicative reporting.  In particular, these are indicators for:
      • Buyback programs
      • Information on MiFID II client categories
      • Transactions pertaining to aggregated orders.

    You can read Kaizen’s FAQ on the changes here or watch our webinar, ESMA’s MiFIR Review – what does it mean for transaction reporting? here.

    Distributed Ledger Technology (DLT) pilot

    Meanwhile in response to the rapidly changing landscape across Europe for the trading and settlement of ‘tokenised securities’, ESMA conducted a call for evidence earlier this year. ESMA released its conclusions on the DLT Pilot Regime and its impact on the regulatory technical standards (RTS) developed under MiFIR relating to certain pre- and post-trade transparency and data reporting requirements. The regulation, which is on a pilot regime for market infrastructures based on DLT, (‘the DLT Pilot’) aims to develop the trading and settlement for ‘tokenised’ securities. The DLT Pilot entered into force on 23 June 2022 and will start applying on 23 March 2023.  ESMA conducted a call for evidence from 4 January 2022 to 4 March 2022 in order to seek feedback and on September 27, ESMA released this feedback received and included proposals for the way forward.

    The conclusions of that report will have been greeted as good news for firms and infrastructure providers in that “ESMA does not consider it necessary to amend the RTS” now, however it will work on supervisory guidance clarifying the application of certain elements of the RTS and experience gained during the pilot will be considered during any MiFIR review.

    So where are we on the ‘ordinary legislative procedure’ timeline?

    EU Commission amendments to MiFIR and MiFID II were the output of the MiFID II review that was carried out, as mentioned above by the EU Commission. The consultations were wide ranging and Commission proposals for the amendments are subject to the ‘ordinary legislative procedure’ which means the European Parliament and the Council negotiate a final legislative text on the basis of the Commission’s proposals. The EU legislative procedure usually takes approximately 18 months.

    The Commission’s proposals were published towards the end of last year (2021) so we are coming towards the end of the legislative procedure.

    The European Parliament has published its amendments and the Council has drafted its own compromise proposals. More discussion is needed to finalise their respective positions before trialogue can commence.

    What happens next?

    If the European Council and Parliament reach a compromise by the end of December 2022 and Q1 2023 respectively, then trialogues between the European Commission, Parliament and Council will follow before a final position is agreed – maybe by Q3 2023. 

    Legal language review and translation will then take place before the final changes to MiFIR and MiFID II can be published in the Official Journal. Based on the timings above, we could anticipate that this will be sometime in the last quarter of 2023.

    The changes to MiFIR are likely to apply 21 days later and changes to MiFID II will need to be implemented in member states within 12 months. Changes to underlying RTS will also be required. 

    What can we expect to see in 2023?

    Change to MiFIR itself is likely to be fairly limited vis a vis Article 26 with most of the detail once again to be found in the amendments ESMA will make in Level 2.

    Looking back at history is no guide to the future, as the final MiFIR and MiFID II texts were published in the Official Journal of the EU on 12 June 2014 and entered into force 20 days later on 2 July 2014. Entry into application was supposed to follow 30 months after entry into force on 3 January 2017. This of course was delayed until 3 January 2018. 

    It’s unlikely to take that long this time around as the scale of the change is significantly smaller than the changes under MiFID II. Assuming that there is no major derailment in the political negotiations, ESMA is likely to produce consultation and discussion papers setting out its proposed advice to the Commission on changes to the RTS and ITS, with implementation during 2024. 

    We will be watching this space and will update you further as progress is made. 

    For a conversation with Matthew or one of our regulatory specialists about the upcoming changes to MiFIR or how to prepare for regulatory change, please contact us. 

  • Tim Hartley writes for S&P Global on regulatory reporting predictions for 2023

    Tim Hartley writes for S&P Global on regulatory reporting predictions for 2023

    In the recent S&P Global Market Intelligence Cappitech blog on regulatory reporting trends and predictions for 2023, Kaizen’s Director, EMIR Reporting Tim Hartley shares his insights on data quality and assurance.

    “2023 is a crucial year for data quality and assurance testing. With so many reporting regimes facing rewrites/refits/re-do’s poised for go-live in 2024, firms will use 2023 to ensure that the quality of their regulatory reporting is fit for purpose ahead of these major regulatory changes.”

     

    Read more

  • FCA releases Market Watch 71

    FCA releases Market Watch 71

    In today’s Market Watch 71, the Financial Conduct Authority (FCA) has taken the opportunity to highlight to firms the importance of compliance with obligations laid out in the UK Market Abuse Regulation (MAR) to include personal information in insider lists. The regulator also reiterates the importance they attach to firms maintaining accurate insider lists and reducing access to inside information to employees to prevent market abuse.

    Insider lists

    The newsletter draws attention to firms that have provided insider lists in response to regulatory requests which do not contain personal information. The lists should include telephone numbers, dates of birth, and national identification numbers. The FCA uses this data to cross reference the information with MiFIR transaction reports, MAR suspicious transaction and order reports and other information sources. Without accurate and complete information, the FCA’s ability to review potentially suspicious trading is hindered. Firms are reminded that insider lists must be in the format and include the information set out in the UK version of Implementing Regulation (EU) 2016/347 and that these technical standards are legally binding.

    Personal identifiers

    Personal information is also required in firms’ transaction reports and must be used to identify the ‘investment decision maker’ and ‘execution decision maker’ (i.e. a firm’s employees), whilst also being used to identify clients of the firm who are natural persons and where applicable, the client’s decision makers. The same standards are used for completing the details provided in ‘insider lists’ and a firm’s transaction reports. These are found in Article 6 of RTS 22. The FCA reminds firms that the first priority national identifier for UK nationals is the national insurance number when reporting to the FCA, and of course the passport number when reporting UK nationals in the EU. Read our recent blog on this topic.

    Getting these identifiers correct in a transaction report is clearly important to the FCA as it has reminded firms of their duty to get this right several times. In both Market Watch 59 and 62, it highlighted that first priority national identifiers must be used wherever available to identify natural persons in transaction reports. Again the FCA mentioned this obligation in October’s Market Watch 70.  The regulator stressed the need for firms to capture this information correctly at onboarding and drew attention to firms who offer services to retail clients electronically, as being particularly weak in this area.

    Important for all NCAs

    Correctly identifying individuals is important to all national competent authorities in Europe and they all have similar duties to the FCA in monitoring for market abuse. 

    The CSSF in Luxembourg stressed the importance it attaches to this field in a notice to firms in February this year and highlighted the following failings:

    • Use of CONCAT code for nationals where this code is not allowed
    • The CONCAT code was not used for nationals where it is the only possible identifier
    • Use of an identifier for non-EEA nationals other than the National Passport Number or CONCAT code
    • The CONCAT code is not correctly constructed when compared with the other personal data provided in the report
    • The national identifiers provided in the transaction reports do not comply with the format as described in ESMA’s Q&A on MiFIR data reporting.

    Clearly getting the personal identification correct within reporting is very important to regulators allowing them, borrowing British television presenter Shaw Taylor’s phrase, to ‘Keep ‘em peeled’, in their efforts to keep markets clean. And perhaps equally important to individuals keeping on the right side of MAR, correct identification allows regulators to quickly ‘eliminate people from our enquiries’.

    • Read Market Watch 71 on the FCA’s website. 
    • For a conversation with Matthew about the topics above, or how Kaizen can help you achieve accurate and complete transaction reporting, please contact us. 
  • A monumental day for CFTC Reporting

    A monumental day for CFTC Reporting

    Congratulations to all of the firms reporting under the CFTC and SEC swap data reporting rules, and of course the SDRs, on the massive achievement implementing the CFTC ReWrite this weekend.

    Situated in our unique place in the derivative reporting ecosystem, we know better than most the herculean efforts that go into achieving such a momentous implementation. Personally as someone who has worked twice at a major Trade Repository (TR) I’ve also experienced first-hand the colossal TR exertions that go into implementing a project of such magnitude whilst simultaneously supporting your clients efforts. And here at chez Kaizen we’ve been, let’s say, ‘a wee bit busy’ ourselves supporting our clients and ensuring our own systems’ readiness.

    As I’ve been banging on for years now to anyone that would listen, the CFTC ReWrite has been a long time in the making. The CFTC’s 2015 ‘Request For Comment’, led to the 2017 ‘Roadmap to Achieve High Quality Swaps Data’, which in turn led to the new rules and data standards that are finally going live today.

    I’ve repeatedly commended the CFTC for its smart adoption of best practices and emerging standard such as the components they’ve modelled based on ESMA’s EMIR framework and global harmonisation workstreams such as CDE. Factor in the onerous ‘Part 49’ requirements to verify, correct or notify on any accuracy or completeness errors and the US regulator’s clear intent to pressure reporting firms into focusing on continually improving data quality, and it’s clear that 5 December 2022 is a monumental day. And not just for CFTC Dodd-Frank reporting and SEC SBSR reporting (which inherits a great deal of the new CFTC ReWrite standards) but for OTC derivative reporting globally as the industry experiences the first major adoption of the CDE standards.

    Congratulations to the SDRs, SEFs, DCOs, swap dealers, major swap participants, other reporting firms and of course the CFTC itself, on achieving this huge accomplishment. Now let’s see how that all important data quality is looking and what the relatively near future looks like for the other OTC derivative reporting regimes also adopting CDE.

    • For help with any aspect of the new CFTC reporting requirements including Part 49 or for an independent assessment of the quality of your reporting, contact us.
  • Singapore FX growth highlights importance of complete and accurate MAS derivatives reporting

    Singapore FX growth highlights importance of complete and accurate MAS derivatives reporting

    Singapore – Top three FX centres in the world

    The latest Triennial Central Bank Survey of FX and OTC derivatives markets published by the Bank for International Settlements (BIS) makes for very interesting reading. In the survey, the BIS confirms that Singapore has retained its position as the third largest FX centre in the world behind the U.K and the U.S. Moreover, in the report the BIS confirms that Singapore’s share of global FX volumes rose to 9.5% in early 2022, up from 7.7% since the last BIS survey in 2019, which includes FX Swaps, Options and Forwards which are all reportable under the MAS derivatives reporting regime.

    Why is it important to firms?

    With Singapore in the top three FX centres in the world, it brings opportunities (commercial and technological), and of course risks. It also brings increased scrutiny from regulators and central banks as they have their own mandates for monitoring systemic risk, and that means that the quality of the reporting data will be more important than ever. This, as we know is part of a significant ongoing effort from the industry ever since reporting went live.

    Reacting to the survey, MAS welcomed the growth and collaboration with the industry in Singapore in the FX space. As we know with any commercial or regulatory change there will be additional scrutiny of regulatory reporting, and this will be no different as we approach the 2024 rewrites including MAS, ASIC, EMIR (both EU and UK) and beyond. Firms should take more than just a note of these statements and factor the importance in planning and implementation for reporting rewrite go-lives.

    So, what can firms do to keep up-to-date with regulatory obligations?

    With the BIS survey and the MAS press release both highlighting the growing volume of the FX market in Singapore, there is a resulting effect on FX regulatory reporting requirements and as a result, more firms are impacted. It is important that firms continually test  their reporting data now and beyond the 2024 go-lives as regulators continue to use this information to monitor for systemic risks.

    With data quality being a continual discussion point in the regulatory community, the opportunity also exists to not only test reporting data, but enhance a firm’s framework, which includes policies, procedures and improving knowledge through training which are all elements of a firm’s controls.  

    So, as an industry, the concentration of FX flows in the region brings opportunities, but with such a huge volume of FX activity it’s clear that accurate and complete data is paramount for both firms and regulators. Firms need high quality controls to function properly and to enable accurate reporting. Regulators need accurate data reporting to supervise the markets and any excessive risks that are building up.

    • For a free healthcheck of the quality of your MAS reporting, or a conversation with Francesco about the topics above, please get in touch.

     

     

     

  • Transaction Reporting How-to Guide: Personal Identifiers

    Transaction Reporting How-to Guide: Personal Identifiers

    The FCA recently released Market Watch 70 providing a reminder to firms of the importance it attaches to the transaction reports it receives.  Transaction reports are used to help them detect and investigate cases of market abuse, combat financial crime, support conduct supervision and examine market events.  For the regulator to be able to do that efficiently, reported data must be complete, accurate and sent on time.

    Despite MiFIR heading for its 5th birthday in January 2023, Kaizen’s testing is still finding a high number of personal identifier errors within transaction reporting, something also highlighted in Market Watch 70:

    • Buyer/Seller identifiers
    • Buyer/Seller decision maker identifiers
    • Investment decision within firm
    • Execution within firm

    These codes are essential to regulators for their work in detecting market abuse.  Harmonisation of the population of this field is vital for regulators attempting to identify individuals insider dealing through several trading accounts held at a number of different firms.  Regulators can only attempt to detect such activity if all the firms use the same and correct code to identify these unscrupulous types. 

    Personal Identifier Essentials

    The first thing to remember is that all personal identifiers start with the ISO two character country code of the individual’s nationality (e.g. ‘GB’, ‘US’, ‘FR’ etc.) followed by the national identifier relevant to that country.  Kosovo being the one outsider here in that it doesn’t have an official ISO-3166 code but its unofficial “XK” is now being recognised by competent authorities.

    National identifier taxonomies

    A list of the national identifier taxonomies can be found in the RTS 22 Annex.  For some countries, there is a single taxonomy; for example, for German nationals, only the ‘CONCAT’ can be used. For other countries, there are up to three taxonomies.

    In all cases you can only use the ’Priority 2’ taxonomy if the ‘Priority 1’ taxonomy is not applicable to that individual.  For example, the ‘Priority 1’ taxonomy for UK individuals is the National Insurance Number (NINO) and priority 2 is ‘CONCAT’.  So if you are identifying a British person, you should only use a ‘CONCAT’ if that person does not have a National Insurance Number.  In theory every British person over the age of 16 is issued with a National Insurance number so for the purposes of transaction reporting you should not be identifying any British person over the age of 16 with a CONCAT code.

    What is ‘CONCAT’?

    ‘CONCAT’ is the concatenation of the following four elements:

    • 2 character ISO country code (as for all personal identifiers)
    • Birth date – in the format YYYYMMDD
    • First five characters of first name (right pad with hashes if less than 5 characters)
    • First five characters of surname (removing prefixes and right pad with hashes)

    Further rules:

    • For the name elements, there is a conversion/removal of diacritic characters, apostrophes, hyphens, spaces etc using the transliteration table in ESMA’s Guidelines
    • Prefixes to surnames must be removed unless they are ‘attached’
      e.g. ‘Von der Leyen’ is ‘LEYEN’; McNeil is ‘MCNEI’ (rather than ‘NEIL#’)
    • The individual’s full name should form the basis of the CONCAT – incorrect abbreviations or nicknames must not be used (e.g. ‘JAMES’ rather than ‘JIM##’)
    • Titles (e.g. ‘Prof’, ‘Dame’ etc) should be removed
    • All UPPER CASE

    So, for example, the CONCAT code for that well known French chanteur Jacques Dutronc, born 28 April 1943, would be: FR19430428JACQUDUTRO.

    What about joint nationalities?

    • If both countries are within the EEA, use the country code of the first nationality when sorted alphabetically by its ISO 3166-1 alpha-2 code
    • If one country is within the EEA and one outside, use the EEA code
    • If both countries are outside the EEA, use the country whose ISO 3166 code is first when sorted alphabetically

    So if it’s joint German and French – use the German taxonomy as ‘DE’ comes before ‘FR’.

    For joint Swiss and French – use French taxonomy even though ‘CH’ comes before ‘FR’ (as Switzerland is outside the EEA).

    Post Brexit reporting to an EU NCA

    So post-Brexit, for the purposes of reporting to an NCA based in the EU, the UK is now outside of the EEA which impacts two things: 

    • Joint nationalities, see above
    • And, as the UK now falls into the category of “All Other Countries”, according to RTS 22 Annex II, UK individuals can no longer be identified using their National Insurance number, the passport number becomes the 1st priority identifier and CONCAT the 2nd priority identifier.

    One final pitfall – the code type

    Because these are XML fields, you need to identify the ‘code type’.  This might vary from ARM to ARM, but the standard code types are as follows:

    ‘CCPT’       – if you’re using the passport

    ‘CONCAT’   – if it is a CONCAT code

    ‘NIDN’    – for any other national identifier

    Where to go to for help

    If you are unsure about any of the reporting standards or just need a refresher, join our upcoming MiFIR core training course which will help ensure you are interpreting the MiFIR transaction reporting requirements correctly.

    Our ReportShield™ Accuracy Testing identifies all transaction reporting errors including those related to personal identifiers, providing a regular health check of all your reported data. 

    • To find out more or for a conversation with one of our regulatory specialists, please contact us.
  • Canada publishes guidance on transition from CFTC ReWrite to CSA ReWrite

    Canada publishes guidance on transition from CFTC ReWrite to CSA ReWrite

    The Canadian Securities Administrators (CSA) body that represents the various regulatory provinces in Canada has published some much needed (if somewhat late) guidance on how firms reporting under the Canadian Derivatives Data Reporting rules should deal with the interim period between the CFTC ReWrite and the Canadian rules being revised.

    The CFTC ReWrite is implemented in less than a month on 5 December and the Canadian rules revision, proposed here, is anticipated to be introduced in 2024. 

    The Canadian proposals for the most part, align with the CFTC revisions as I discussed in a recent blog. But given some of the trade repositories support both CFTC & CSA reporting there is the potential impact on Canadian reporting in the interim. 

    The CSA guidance is intended to clarify what firms should do for the next couple of years, but given the proximity to 5 December, it isn’t likely to materially impact any firms’ reporting solutions as they are in the final stages of testing and ready to go-live next month. 

    This guidance therefore for the most part just provides assurance but will still be welcome, as anything that provides regulatory clarity is always a step in the right direction.

    Spoiler alert, the guidance basically says follow the CFTC for the most part, apart from where you don’t!

    • For a conversation with Alan or one of our regulatory specialists about the quality of your Canadian or CFTC reporting or any of the topics mentioned above, please contact us.
  • FCA’s Market Watch 70 cites progress but areas for improvement on transaction reporting

    FCA’s Market Watch 70 cites progress but areas for improvement on transaction reporting

    The FCA has released its latest Market Watch newsletter which has a heavy focus on transaction reporting. The UK regulator says it is encouraged by the progress firms are making in terms of data quality and has released data showing the number of investment firms taking data extracts via their Markets Data Processor (MDP) is continuing to rise each year. 

    What is interesting is that although 716 firms requested data from the FCA’s MDP in 2021 to assess the accuracy and completeness of their reporting, this suggests that more than half of all UK MiFID firms are not doing so, a clear breach of their reporting obligations.  

    While the number of error and omission notification forms continues to rise, the data quality alerts suggest to the FCA that many firms are not conducting sufficient data checks including across asset classes. The quality of the E&O notifications (see our recent blog for tips on how to complete these) also varies, with the FCA explaining the usefulness of including examples of how fields have been misreported.

    Other concerns include the over-use of second and third priority identifiers for natural persons as well as how firms are identifying appointed representatives. Greater improvement and consistency is needed in relation to branch activity and determining when trades are being ‘executed’ thus leading to a reporting obligation.

    The order aggregation ‘INTC’ account is also being misused in certain cases and there is a warning to trading venues that they are responsible for the transaction reports made on behalf of their non-MiFID participants. It is stated that some venues have been putting too much responsibility on their members. The misreporting of the venue and the instrument full name fields is also mentioned.

    Trading venues are also reminded of their obligations in relation to instrument reference data and Systematic Internalisers are often sending instrument reference data to FIRDS in error which is confusing reportability for firms under RTS 22. Instrument testing is of particular sensitivity due the dependence on the quality of the data for the wider transaction reporting regime.

    While the FCA has seen improvements in transaction reporting, today’s comments show that the regulator’s expectations around transaction reporting are increasing, and robust and comprehensive testing must be in place for all firms. 

    Read the newsletter on the FCA’s website.

    • If you are unsure about any of the reporting standards, or just need a refresher, we would heartily recommend our core training course which will help ensure you are interpreting the MiFIR transaction reporting details correctly.

    • Kaizen’s ReportShield quality assurance services are designed to detect all reporting errors including those mentioned in the FCA’s Market Watch 70.  Contact us for a conversation about how we can get your transaction reporting in the right shape.
  • Canada, the CSA and the CDE greatest hits

    Canada, the CSA and the CDE greatest hits

    These days reading a transaction reporting consultation paper is like going to see a classic band.  Everyone is wanting the old favourites and groans when they announce anything from the new album.  The long awaited Canadian proposals were published in June and everyone is relieved they’re playing the familiar classics we can singalong to from the multi-platinum CDE greatest hits album.

    The following attempts to distil the various proposal documents (request for comment, amended rules, companion policies and the technical manual) into something a bit more digestible. The Canadians are proposing a 2024 implementation so we will see how this plays out.

    I’ve assembled a Spotify playlist below and will attempt to discuss some of the proposals. 

    The laundry list includes:

    • Harmonisation to CDE (Critical Data Elements) and CFTC fields and values
    • Harmonisation of UTI with global UTI rules
    • Revised UTI dissemination hierarchy
    • Adoption of UPI in-line with global alignment to use UPI
    • Introduction of collateral and margin data reporting
    • Part 49-like requirements for the SDR to perform validations on the data and for reporting firms to perform verifications
    • A proposed alternative reporting hierarchy
    • Reporting of packages in-line with CFTC approach
    • The option to report certain lifecycle events at position level
    • Updated requirements for the operation of Trade Repositories
    • Updated definition of “derivatives dealer”
    • A new ‘Multilateral Derivatives Data Technical Manual’, a tech spec very similar to the CFTC’s
    • Termination of an original derivative by a clearing agency.

    So, assuming both you and my editor have indulged me with this many bullet points, then let’s dive in.

    Harmonisation to CDE and CFTC fields and values

    Adoption of CDE fields and harmonisation towards the CDE standards is front and center. The main driver of all these reporting rule revisions globally is harmonisation and interoperability so the focus on CDE fields is sensible and welcome.  The Canadians attribute the remainder of the fields to the following sources:

    • CSA
    • CFTC
    • ESMA

    The Canadian tech spec has 140 fields compared to the CFTC’s 128 fields.  This is in part due to the CSA retaining fields such as Master Agreement Version & Master Agreement Type (with new snazzy types) and Broker ID that the Americans dispensed with.  Adoption of some ESMA-inspired fields such as Derivative Based On Crypto-assets helps towards the higher field count.  But the 140 fields still pales in comparison to the 203 fields ESMA is squeezing into the EMIR REFIT.

    Where the CFTC only requires a true/false flag for Custom Basket Indicator, the CSA are also proposing Source of the identifier of the basket constituents and Identifier of the basket’s constituents to better understand what’s in the shopping cart.  However, despite being CDE fields both the format and valid values of these fields are defined in the Canadian consultation as “tbd” so it’s more of a statement of intent as it stands. Last month’s ROC consultation on updating CDE to version 3 attempts to (and arguably fails to) provide clarity by suggesting a 350 variable character format maintained by the UPI service provider.

    Part 49-like requirements

    One proposal that might not be universally welcomed but is understandable is the adoption of Part 49-like proposals around verification “to ensure that all reported derivatives data is accurate and contains no misrepresentation”.  The CSA is proposing that all derivatives dealers and clearing organisations verify the data accuracy at least once every 30 days much like the corresponding CFTC rules.  But unlike the CFTC requirement for certain reporting counterparties (that are not swap dealers, major swap participants or clearing agencies) to undertake a quarterly verification every 90 days, the Canadians are not requiring this and citing the excessive burden.

    Thankfully the proposals are not mandating the draconian seven-day limit for fixing any errors discovered in the verification process.  But the proposals are harsher than the CFTC equivalents by enforcing a time limit of the end of the following business day from discovery of an error for notification of that issue.

    Option to report certain lifecycle events at position level

    Another proposal that’s no doubt well intended but I fear isn’t a good move is the proposal to introduce the ability to report at position level in certain instances where the individual transaction;

    (a) has no fixed expiration date, and

    (b) is in a class of derivatives in which each transaction is fungible.

    This is intended to alleviate the burden of reporting lifecycle events on the individual transactions but regardless of the good intention, I’m not a fan of this proposal as it introduces complexity. ESMA has had position level reporting under EMIR for years and it’s caused more problems than it’s solved. This diverges with the CFTC approach, creates different values for Action Type, divergent workflows and message choreography for reporting firms that are very likely to have a US footprint as well. Clarity and consistency are vital for data quality and this detracts from both.

    Termination of an original derivative by a clearing agency

    The final contentious proposal is the requirement for the Clearing Agency to terminate the original trade despite not reporting that trade themselves. So Big Bank (BB) trades with Small Hedge Fund (SHF) and BB has the obligation to report the original transaction. This trade (the alpha) is then cleared and replaced by two new trades;

    • The beta – cleared trade between BB and Clearing Agency
    • The gamma – cleared trade between SHF and Clearing Agency

    Here the Clearing Agency would have the obligation to report both the beta and the gamma which is fairly standard and unremarkable.  But the Canadians are proposing that the Clearing Agency also has the obligation to report the termination of the original alpha trade which is a new concept and throws up several logistical and practical considerations for both the Clearing Agency and the party that reported the original transaction.

    Multilateral derivatives data technical manual

    The final item which I suspect will be welcomed with open arms is the introduction of a much needed Technical Manual. The Canadian regulators are trudging down the same path the CFTC has already trodden from principles-based reporting rules to far more prescriptive (and let’s be honest, more ESMA-like) rules.

    If regulators want firms to report accurate high quality data then the clarity of the reporting requirements is paramount. The draft Technical Manual, which clearly owes a lot to the CFTC’s equivalent Parts 43 and 45 Technical Specification, is a huge step towards providing that all important clarity. I suspect and hope that both the CFTC and the Canadians over time will find themselves having to publish further so-called ‘level 3’ guidance such as FAQs and reporting guidelines but in the meantime I commend the Canadian authorities for publishing this Technical Manual.

    Next steps

    The proposed 2024 implementation is really not that far away. However, it’s likely that the Canadian implementation will be in a year already congested with ESMA’s EMIR Refit and several other reporting rule revisions such as ASIC, MAS and HKMA going live. Some aspects such as the alignment with other reporting regime formats and rules are very welcome.  The production of the technical specifications and the clarity it enables is likewise laudable.  Other aspects such as the verification/notification timelines will see industry pushback.  But at least we have a relatively clear picture of where the Canadian reporting rules are headed and when.

    • For a conversation with Alan or one of our regulatory specialists about the quality of your Canadian reporting or any of the topics mentioned above, please contact us.
  • Errors and omissions notifications: the regulatory reporting confession letter

    Errors and omissions notifications: the regulatory reporting confession letter

    Regulatory reporting is hard, and mistakes inevitably do happen. But knowing what action to take once you’ve discovered errors and omissions in your reported data is equally challenging. Sometimes issues are found via internal means, but they can also be discovered by regulators who then begin asking questions.  At Kaizen, we regularly help firms in this position, supporting them with their communication to the regulator and correcting and re-reporting the transactions via our Accuracy Testing.  Here, we share some of our insights on errors and omissions notifications and what to do once your firm finds regulatory gremlins lurking.

    1. Regulatory clarity – clarify your mis-reporting

    Before enthusiastic (or defensive) emails are sent to the regulator, you must clarify exactly how deep the problem goes.  What volume of trades have been missed or impacted, over what time period?  Coupled with this is the need to understand exactly what the mis-reporting actually was.  Vague explanations will inevitably lead to further questions from a puzzled regulator.

    At this stage of issue discovery, many firms choose to perform assurance and accuracy testing on their reporting population, to ensure that any other hidden powder kegs are uncovered well before further regulatory scrutiny prevails.  Independent assurance testing is the most efficient and complete way of undergoing such checks and can also help paint a good picture to the regulators when it comes to submitting an errors and omissions notification.

    Regulatory reporting is the counterparty’s responsibility. Firms must be able to understand and explain why the reporting was wrong or incomplete. Importantly, this is true for those making direct reporting submissions to a trade repository/ARM/SDR, and it is equally true for those utilising a form of ‘delegated reporting’.

    2. Preparing the Errors and Omissions notification

    If you’ve completed the above, now it’s time to own up to all the things you’ve got wrong. To do this, most regulators expect firms to fill in an errors and omissions notification.  The ideal point to draft the notification is not the same for all situations. Generally though, only once a firm has performed satisfactory checks and is confident with the known scope of the errors, can the notification be drafted. The UK FCA Errors and Omissions form* and the Central Bank of Ireland’s form* are good starting points to illustrate what details you should include, but each regulator will have its own variation on this theme and some even simply ask for a free format email.

    The notification should ideally confirm:

    • The full scope of the mis-reporting
    • Remediation steps undertaken
    • The cause of the issues
    • How these errors will be avoided in future.

    The regulator needs to see that you have control over these issues and over the reporting in general.  Failure to demonstrate strength in this area will undoubtedly prompt the regulator to probe for more information and place demands on how and when further data is provided, often citing how and when remedial actions are carried out.

    In our experience, it is exponentially better to provide all the information in advance. The motive here is to answer all the questions the regulator may have before they are asked.  Providing the bare minimum of detail, in an evasive or defensive manner, can backfire and lead to further scrutiny and the possibility of fines.  

    In all cases, you should be ready for follow up questions from the regulator.  The more thorough and prepared you have been with your scope investigation, the more comfortable you will be in answering such questions. In addition, it’s important to remember that the aim here is to close out as many questions as you can before there is a chance to ask them.  Therefore, the deeper the dive in reviewing existing reporting quality and completeness, the better prepared you will be and fewer questions will arise.

    3. Frequency and strength of notifications

    In our experience, fewer but stronger, notifications is the optimal strategy here.  As mentioned earlier, the aim of the notifications is to demonstrate the strength of your regulatory reporting, and control over the errors at hand.  Some firms have legal and compliance policies in place to notify their supervisor for each and every error uncovered on an ad-hoc reactive basis. However when it comes to the regulator, too frequent notifications risk demonstrating a lack of control over issues and procedures, and can lead to further regulatory scrutiny.  Some regulators may request regular updates for known issues or existing independent reviews, but usually only for many errors across large data arrays.

    Whatever frequency is explicitly committed to, you must ensure that any deadlines are adhered to, or give reasonable written notice with clear sensible justifications as to why a specific date is no longer feasible.

    4. Remediating errors and other useful actions

    Notifications should demonstrate an organisation’s remediation plans, taking into account factors such as technology build requirements, prioritisation alongside existing commitments, and it is always a shrewd move to add contingency for unforeseen delays.  Firms would also be wise to use this opportunity to:

    • Create or enhance deep, tailored and universal accuracy and completeness testing controls incorporating all fields and all reports submitted
    • Ensure supporting policies and procedures are up to date and fully cater to avoid a repeat of the identified issues
    • Check that reporting errors are escalated appropriately with clear and written action points for defined responsible stakeholders
    • Confirm access to the reported data from the regulator or trade repository/ARM/SDR which is regularly saved down for future endeavours
    • Engage in annual regulatory training to ensure that all impacted internal parties are up to date on reporting requirements.

    5.  Final thoughts

    Demonstrating the appropriate controls and strength of process regarding how you approach errors and omissions notifications, and the manner in which information is relayed to the regulator, is absolutely crucial to that working relationship, and will proactively influence the nature of any further regulatory scrutiny, fines or demands that follow. Having a well thought through errors and omissions notification policy will help ensure that communication with the regulator is open and effective.

    • If you find yourself in this position and would like a discussion with one of our regulatory specialists about this process, please get in touch.

    *Both forms will download rather than open in a webpage.

  • SFTR – The Terrible Twos or Yesterday’s News?

    SFTR – The Terrible Twos or Yesterday’s News?

    SFTR reporting is now two years old for banks and investment firms and after a challenging gestation period and turbulent infancy, it’s toddling along with growing maturity.

    Nobody involved is ever likely to forget the scale of the challenge to go-live in the epicentre of a global pandemic. Nor, the market fragmentation and change involved in implementing Brexit before SFTR had begun to find its feet. Just as we were looking ahead to a thorough regulatory review and ultimately SFTR Refit, war in Ukraine really placed a spanner in the works of the EU legislative process and has likely set us back a couple of years.

    Data quality issues

    Given the current state of the EU regulatory agenda, the onus has fallen upon the National Competent Authorities (NCAs) to be the principle guardians of reporting data quality. The EMIR & SFTR Data Quality Report 2021 perhaps set the tone in April this year, with glaring reporting misdemeanours highlighted (notably one major party reported a lot of open term business but failed to ever report a close!). Since then, it has become apparent that identifying data quality issues, under-reporting in particular, has been akin to shooting fish in a barrel for some of the NCAs.

    Reporting quality is improving, particularly among our clients, even if in some cases it has required something of a regulatory stick from the most proactive NCAs. Demand for back reporting (correcting historic errors and adding under-reported activities) and assistance with back reporting is growing fast.

    If any further prompts were necessary, here is a summary of the findings from 24 months of ReportShield™ Accuracy Testing for SFTR:

    Reference and static data challenges

    Many issues continue to present themselves, particularly in the realm of reference and static data and in particular in relation to fields that have no function within the trade lifecycle or settlement function. The decision to include fields that are not recorded in risk management systems or trade books and records has been highly questionable from the beginning. The concept that clients should agree the most appropriate field populations amongst themselves is also deeply flawed. There are also significant elements of uncertainty about how they should be populated (in some instances with multiple permissible answers). In particular, security/collateral type, credit quality, master agreements, jurisdiction of issuers, security maturity dates and CFI codes all present ongoing challenges.     

    Trade economics woes

    In terms of the economics, the picture is not entirely rosy either, much to regulators’ anguish as spurious data is compounded by aggregation in the public data and potentially globally shared SFT data too. Many of the issues relate to incorrect interpretation, application of the rules, poor reporting logic or under-reporting (notably of collateral and valuations). The good news here (and the beauty of independent Accuracy Testing) is that once identified, these issues can often be quashed for good with relatively simple reporting logic changes (rather than the relentless and ongoing battle with reference data). We continue to witness instances of missing direction of collateral, significantly overstated haircuts (where initial margins have been used in error), incorrect pricing (prices & rates) and incorrect rate indices among other issues. Some of these issues are compounded by late reporting or misleading report timing (given the lack of effective data under SFTR).

    How to cope with the early years?

    Like caring for small children, there is no shame in calling for help! Not marking your own homework and an independent assessment of your ‘child’s’ performance gives great perspective. If you’d like some help in dealing with those sleepless nights, please contact us.

    Jonathan is delivering an SFTR Core Training Course on 14-15 September.  For more details or to book your place please visit our training pages.

  • Collateral Reporting – Past, Present and Future

    Collateral Reporting – Past, Present and Future

    The year is 2012

    Rising K-pop star Psy has just released Gangnam Style (but you probably haven’t heard it yet). London is preparing to host the Summer Olympics and if you’re not reading 50 Shades of Grey you’re probably reading Appendix 1 of CFTC’s Part 45: The minimum primary economic terms of a swap.

    The CFTC simply wants to know how each reportable contract is collateralised using a simple code to indicate partially, fully, one-way collateralised etc. There is no need to report any collateral valuations or margin data.

    This should be easy.

    The year is 2014

    Gangnam Style has reached 1 billion views on Youtube (you can do the dance too).

    England fail to bring football home at the Brazil World Cup and if you’re not taking part in the ‘Ice bucket challenge’ you’re probably getting up to speed with the new craze of ‘EMIR reporting’ that has swept Europe by storm.

    EMIR reporting goes live in February and six months later collateral & valuation reporting begins.  Firms are required to report how each trade is collateralised and the ‘value of the collateral’ is required to be updated daily.  Many questions are asked about whether this should be a combination of initial and variation margin or something in between.

    The ‘collateral portfolio code’ is introduced to link multiple trades to the same collateral pool.

    It’s a bit more complicated than the CFTC requirements but should be manageable.  Surely the CFTC will follow suit soon?

    The year is 2017

    The world is trying to figure out what Donald Trump means by his ‘covfefe’ tweet.

    After weeks of analysis, the only conclusion is that he was trying to tell us ‘Collateral Valuation Fields Expand For EMIR’.

    He is referring to the EMIR RTS 2 go live of course. The number of collateral fields has increased from 4 to 15.  Reporting parties now need to split out the reporting of initial and variation margins.  They also need to report margins that were received as well as posted. Excess collateral needs to be reported separately.  There is still confusion as to whether margins reported should be pre or post haircut values.

    Fittingly, LaLa land has won the Best Picture Oscar, hasn’t it?

    The year is 2018

    Gangnam style is a thing of the past.  You are now learning how to do The Floss instead.

    England fail to bring football home at the Russia World Cup and if you’re not attending Harry and Megan’s Royal Wedding you’re probably reading ‘Harmonisation of critical OTC derivatives data elements’; the technical guidance published by CPMI-IOSCO.  The paper becomes commonly referred to as the CDE.

    They propose that 19 fields are required to report collateral accurately.  They have gone one step further than EMIR and suggested that pre and post haircut values of initial and variation margin should be separated.

    A white paper published by the CFTC states that they should implement the CPMI-IOSCO standards and that ‘the reporting of fewer, yet better defined and standardized, data fields should improve the quality of swaps’.

    There shouldn’t be long to wait until that gets implemented…

    The year is 2022

    Chris Rock is still massaging his jaw after ‘The Slap’ and the England women’s team are still celebrating after bringing football home at the Euros.  The celebrations come to an abrupt stop as CFTC Rewrite reporting goes live on 5 December.

    The US and European regulators have finally agreed on the spelling of ‘collateralisation’!

    After a very long wait, prolonged by several delays, the CFTC reporting rules have finally been modernised.  The collateral reporting rules are mostly aligned with the CDE but with a few exceptions.  Notably, the CFTC requires separate portfolio codes for initial margin and variation margin and an indicator for portfolios that contain non-reportable trades.  They have ditched the CDE proposal to include post-haircut values for variation margins.

    Christmas is cancelled as emergency post implementation fixes need to be prioritised.

    The year is 2024

    Notre-Dame reopens to the public as Paris prepares for the Summer Olympics.  Whilst cruising in your driverless car you have time to reflect on the EMIR Refit go live.

    ESMA and the FCA require all the CDE fields with one addition, the ‘collateral timestamp’, which indicates when the value of the margins was calculated.

    The gradual separation of different types of margins for reporting have made some reporting firms upset. Their systems were not made to deconstruct this data. Other firms are happy because this is exactly how their systems are built.  There are still complexities getting collateral data from some third parties and how margins are being reported.

    The world is slowly moving to a more harmonised approach of reporting but there is still a long way to go.

    The year is 3033

    Alien contact has been made with Kepler-452b.

    Humans live on Mars.

    Interplanetary regulators are still trying to agree the correct way to report collateral data but feel it’s surely within reach.

    • When do you think regulators will agree how to report collateral data?  For a conversation with one of our reporting specialists or a free healthcheck of your reporting, please contact us.
  • Too little, too late – ESRB attempts to amend EMIR Refit

    Too little, too late – ESRB attempts to amend EMIR Refit

    Just as the EMIR Refit has been endorsed and looks to be sailing into EU law for final sign-off, the European Systemic Risk Board throws a potential spanner in the works with a recent letter to the European Commission with its recommendations for Refit.

    Some of the recommendations in the letter look to be questionable, burdensome, and too little, too late given what the industry has already gone through as part of the extensive consultation process for EMIR Refit. 

    Let’s take a look at these in more detail:

    Scope of reporting

    The ESRB recommends adding additional data fields to support the monitoring and mitigation of systematic risks as required. Adding in additional fields becomes problematic and is counterintuitive in trying to improve data quality.

    Planning, preparation and budgets are in full swing as the industry believes the Refit requirements to be final and understood. To ask for more at this late stage from the industry, and outside of the normal legislative process would prove too burdensome.

    Quick check

    The ESRB recommends that reporting counterparties “should perform a quick, aggregative-level check” on the data that they send to the trade repository. The ESRB goes on to say that these quick checks would come about as a result of amending such items as the Q&As. This shouldn’t be anything new for the majority of counterparties, especially the larger firms, and this recommendation is strange given that counterparties already have an obligation to report completely and accurately.

    The EMIR Refit already adds additional controls and checks by both the trade repositories and also the reporting counterparties (much of the industry will have/or are already looking to enhance their checks as part of their own systems and controls process). 

    Once again, the question should be – would anything outside of the EMIR Refit process that the industry has already started planning for, add any true value?

    Reporting handbook

    The ESRB recommends that a separate reporting handbook is produced to aid a common understanding on how certain fields and specific scenarios need to be reported. We think the ESRB would have been better to recommend that additional clarity is provided via the existing Level 3 guidance which would support the industry to improve data quality, rather than adding more documentation for firms to manage. This is why we’re seeing the industry want more clarity, and what prompted the trade association best practices document.

    The ESRB also goes on to say that regulators’ supervisory attention and actions towards the reporting counterparties could be linked to the reporting handbook.  Asking regulators to take enforcement actions based on non-legally binding guidance like the proposed handbook is potentially controversial. The Level 3 Q&A documents have long been a source of contention regarding ‘how’ and ‘if’ they’re legally binding. 

    Appointment of a responsible officer

    The ESRB recommends that reporting counterparties make a mandatory appointment of an officer for all reporting. The requirement for a responsible individual already exists in the form of ‘Senior Management Functions‘ within the UK, and under the ‘Controlled Functions’ (which will already look after reporting matters) that many EU regulators also impose on counterparties to have in place, which will be supported by the relevant teams within those counterparties.

    Machine-readable/ automated reporting

    The ESRB recommends ‘making reporting requirements readable and executable by machines’. This would mean that reporting counterparties would need to adapt their internal risk management and reporting systems, with the ESRB stating that this would ‘contribute to an improvement in the quality of available data more generally and thus to facilitate the monitoring of financial stability risks’.

    Moreover, if the Commission were to agree with this proposal, the implementation period would stretch beyond the proposed go-live of EMIR Refit which would bring further issues for the industry.

    Flexibility of reporting requirements

    The ESRB asks for additional information during times of crisis when trying to monitor systemic risks, which is outside of the mandatory reporting requirements.  The industry is used to receiving ad-hoc requests, but they have to be of value in order to assist the regulators, especially during times of market impact to the firms which without clarity (which improving data quality should be about), could be an unnecessary burden.

    What’s next?

    As ESMA sits on the ESRB and has been involved in these discussions, we hope caution will be exercised in imposing any new/or additional requirements for EMIR Refit at this late stage, especially as reporting counterparties are planning for multiple reporting regime changes. Adding requirements outside the normal process may bring more risks than the industry needs.

    • For a conversation about the above or any aspect of EMIR reporting including the upcoming EMIR Refit, please contact us.
     
  • ESMA publishes SFTR Q&As 13 and 14

    ESMA publishes SFTR Q&As 13 and 14

    ESMA struggles to hit the spot in terms of tackling the most pressing issues with its latest Q&As but there is some benefit for reporting firms from Q&A 14, published alongside Q&A 13 on 19 July 2022.

    Q&A 14 clarifies the requirements around reporting collateral and validation updates on the last day of an SFT (including overnight and intraday transactions). The answer is that firms should not send either collateral or valuation updates for the last day of an SFT. In the case of intraday transactions, the day of conclusion (execution date) is the last day of the SFT. For overnight transactions, counterparties should report valuation and collateral updates for trade date (T).

    The second Q&A 13 applies to trade repositories, reiterating that they need to include SFTs in the trade state report up until their maturity date / end date unless they have been errored or early terminated. 

    • For a conversation with Jonathan about your SFTR reporting headaches or to find out how we can improve the accuracy of your SFTR reporting, please contact us. 
  • ESMA concedes – third-country issuer LEIs only where they exist

    ESMA concedes – third-country issuer LEIs only where they exist

    ESMA has published a third statement on the requirement to provide the Legal Entity Identifier (LEI) of the issuer of securities loaned or used as collateral, in instances in which the issuer is domiciled outside the European Economic Area (in a third country) for SFTR reports. They have decided that it is only mandatory to provide the issuer LEI for securities from third country issuers where it exists.  ESMA has requested that Trade Repositories (TRs) will not reject SFTR reports without a third country issuer LEI for securities lent, borrowed or provided as collateral in an SFT.

    Backtracking 

    This concession backtracks somewhat on the second statement published in April 2021 that indicated “No LEI, No trade” by October 2022. ESMA reflects that at present, around 14% of all open SFTs still do not have an issuer LEI.  The fundamental problem is that holders of collateral (in many cases a very fleeting relationship) or securities lenders and borrowers have very little leverage over securities issuers to compel them to obtain an issuer LEI when they are established in third countries outside Europe.  It is very different to the amount of leverage firms had over their counterparties to a transaction when this requirement for counterparty LEIs was mandated under MiFID II.

    ESMA to monitor situation 

    ESMA has taken the decision that instead of rolling forward the deadline for a third time, they will continue to monitor the situation and give six months’ notice prior to changing the validation rules to mandate issuer LEIs.  In the meantime, ESMA expects counterparties and other parties to a transaction (such as agent lenders and triparty agents) to encourage third country issuers to adhere to SFTR requirements and obtain an issuer LEI.  We anticipate that the UK FCA will provide very similar guidance shortly, having taken a more pragmatic view from the outset.     

    • For a conversation with Jonathan about your SFTR Reporting or a no-obligation review of the quality of your reporting, please contact us.
  • FCA consults on improving equity secondary markets

    FCA consults on improving equity secondary markets

    Earlier this week FCA released its Consultation Paper (CP) on improving Equity Secondary Markets.  Although some elements cover ALL asset classes, the expectation is that we will see the staggering of topics and the equivalent for the more complex Non-Equity asset classes released soon too. 

    Since Brexit there has been the gradual transition of MiFID II/MiFIR into UK Law, without the need for a ‘bonfire of regulations’, but with the indication that the UK and HMT (see Wholesale Markets Review WMR) look to right some of the ambiguity and unnecessary complexity caused by the regulation since its inception in 2018.  HMT’s first step was to give the FCA the power to change and adapt the regulation, without the bureaucracy of legislative changes.

    With that, we now see this CP, seeking feedback from the industry, with responses due by mid-September 2022.

    For this blog, I’ll concentrate on Post-Trade Transparency Reporting (PTT) RTS 1, in which the FCA’s plan, along with the WMR, is to lower costs and improve the information content of trade reports and how Equity Markets operate;

    “We want to change our rules to enhance the quality of execution for investors and improve the information content of post-trade transparency”.

    So as we dig into the details, we can see the aim of improving the content of PTT reporting by enabling market participants to better identify transactions that contribute to the price discovery process and to improve the consolidation of trade reports from multiple sources.  Price Discovery being the key element to close to real-time reporting, within 1 minute of execution for RTS 1. In addition, a high priority is simplifying the reporting of OTC transactions by removing the Systematic Internaliser (SI) status as a criterion for establishing when an investment firm is required to report transactions.  The FCA is proposing to adopt a new regime based on designated reporting firms, thus segregating the SI requirements from reporting responsibility.  n.b. SI’s will not go away.

    Two of the main issues identified within the PTT regime;

    1. The current system of flags does not always provide sufficiently precise information to separate price forming transactions from technical trades
    2. There is ambiguity as to which flags should be used leading to different firms adopting different standards which lowers the comparability of trade reports and the ability to consolidate them.

    These shortcomings negatively impact the quality of the information contained in post-trade reports, increase compliance costs for the reporting entities as well as the costs for firms that use post-trade data to inform their trading decisions.

    Yes there is an overlap of descriptive flags and a tidy up will make things clearer e.g. clarification of TNCP and NPFT but the removal of some flags should be closely reviewed with feedback from the industry as to whether there is any exposure to undue trading risk to some firms.

    The Designated Trade Reporter adoption is stepping back into what looks like more of a MiFID I reporting regime.  Investment Firms electing themselves as the designated reporter, with notification to the FCA mandatory and regardless as to whether they are an SI in the instrument or asset class, delineating the SI regime from the reporting responsibility.  This will certainly favour the buy-side but as a reminder, there is still the possibility of reporting if neither party to the trade is an SI or a Designated Reporter and as before the seller will report.

    In my opinion, for this to work, a central source, database or register has to be consolidated and maintained with the emphasis on the SIs and Designated Reporters to register and communicate to their buy-side clients.  We saw this succeed leading up to MiFID II go-live with the APAs coming together as a consortium along with Smartstream RDU to create the SI Register (SIR), which was imperative to understanding reporting obligation.  Ultimately with a change in rules, there will be reporter uncertainty or missing reporter status’s which could lead to under or over-reporting, which is a key area Kaizen’s PTT testing service highlights.

    The FCA is aware and did highlight the high costs associated with regulatory changes. These can be seen across multiple teams within firms that regulatory reporting affects and industry conversations have been and will continue to be had.

    What the industry wants from any change or divergence around PTT is; simplification, less ambiguity meaning consistency of reporting across firms and ultimately better quality trade reporting data, so investors can be better informed on pricing, liquidity and best execution.

    • For a conversation with Chris about the topics above or for help with your trade reporting data quality please get in touch.
  • Sunshine and surveillance star in FCA’s summer update

    Sunshine and surveillance star in FCA’s summer update

    The FCA’s data-led approach is clear to see in a welcome update that sheds light on the regulator’s Markets Data Processor (MDP), which is described as a “source of regulatory sunshine that allows us to oversee the market…with dedicated software…to detect potential issues.”

    The FCA’s MDP receives over 30 million transaction reports and over 100 million order reports a day which are then analysed for a variety of offences, including insider dealing and market manipulation.  This surveillance effort is supplemented with Suspicious Transaction and Order Reports (STORs) received from market participants which averaged more than 90 per week last year and represented an increase of almost 15% on 2020.

    Market abuse approach

    In this update, the regulator highlighted the importance of the deterrence factor offered by transaction reporting and monitoring, explaining that ‘intensive scrutiny’ meant that participants are less likely to abuse markets if they know they are being watched. 

    The FCA gave an insight into its approach and powers to monitor, detect and prosecute market abuse as well as a general overview of its current case load.  When the perpetrators of market abuse are more organised and operate across borders, the FCA continues to collaborate and exchange data and intelligence with regulators globally. The efforts of 90 FCA enforcement staff reinforced with specialist cyber, legal, intelligence and primary and secondary market oversight teams are focused on tackling market manipulation and insider dealing.

    Data-led strategy

    One common theme running through this update is the obvious importance of the FCA’s data-led approach to surveillance and regulation. It will therefore be interesting to see whether the FCA’s forthcoming MiFID transaction reporting consultation paper proposes to follow ESMA’s lead with the introduction of new data fields to assist with firm-based supervision and monitoring the compliance of conduct of business-related rules.

    With the FCA’s data strategy being published in the coming months, prioritising the monitoring of firms’ more general trading and a broader range of activities through transaction-related data will require more granular information. 

    Simplification of reporting?

    If the transaction reporting consultation paper is published before the full data strategy, it could be that ‘simplification’ and a focus on increased data quality is given priority over the data strategy in the short-term. Although, through the quality assurance testing we do at Kaizen, we can see that data quality is still very poor*, starting to incorporate the FCA’s data strategy into the MiFID transaction reporting consultation paper will bring it in line with the FCA’s strategy as a whole.

    As misreporting can lead the regulator down blind alleys and cause market abuse and other offences to go undetected, we can see from this interestingly timed update, that accurate and complete transaction reporting is still of paramount importance to the FCA.

    • For a conversation with Simon about the topics above or for help with your transaction reporting data quality please get in touch.

    *Only 10% of transactions are successfully reported under MiFID II. 

  • Are the APAC regulators planning a 2024 April Fools?

    Are the APAC regulators planning a 2024 April Fools?

    I’m not sure if Aprils Fools and spending the first day of April each year playing practical jokes on each other is a western concept or whether it’s more universal and embraced by our Asian friends and colleagues.

    Even if it’s more universally adopted I struggle to picture serious national regulators engaging in Aprils Fools pranks. It’s hard to picture the UK’s FCA releasing a statement on the morning of 1 April saying they are about to repeal MiFID II and then adding in the afternoon, ‘Gotcha, April Fools!’.

    I’m pontificating about this because 1 April 2024 is starting to look pretty interesting for the APAC transaction reporting regimes. As it stands here at Kaizen Reporting we’re tracking several reporting timelines starting to coalesce around this date.

    • In Japan the JFSA have a consultation on their proposed changes due in July 2022. Implementation of these changes which will include harmonising to CDE (critical data elements), UPI (unique product identifier) and UTI (unique transaction identifier) – all being widely adopted by other global regulators – is expected to be implemented on 1 April 2024

     

    • Down under in Australia, ASIC have taken a slightly different approach with a small batch of changes due on 1 October 2023. These will then be followed by the main event (harmonisation to CDE, UPI, UTI etc) being implemented on 1 April 2024

     

    • The HKMA in Hong Kong also has a consultation on CDE & UPI due second half of 2022. Implementation of these changes along with adopting of collateral and margin reporting is currently slated for “no sooner than 1 April 2024”

     

    • Over in Singapore MAS is keeping us guessing as it is reviewing the responses received from their recent consultation on harmonisation including CDE, UPI and UTI. At the time of writing they haven’t published firm dates but a 2024 go-live is looking very likely.

    And as if that wasn’t plenty to keep the regulatory transaction reporting community busy that’s just the APAC side of things.

     

    • In Europe the European Commission has finally approved the EMIR Refit RTS which assuming the EU parliament sticks with its allocated three months to pass the Refit into law then points towards a late Q1 to early Q2 2024 go live

     

    • Over in Canada the CSA authorities released a consultation on 8 June that also sees the Canadians wanting to get in on the CDE, UPI, UTI harmonisation party and they too are proposing – you guessed it – a 2024 implementation.

     

    And finally closer to home for me, the UK Treasury and FCA are pointing towards a summer policy statement that should clarify the implementation timeline for the UK version of the EMIR Refit. Here at Chez Kaizen we’re tracking late 2024 for the UK Refit but I guess it’s not too late for the FCA to go for April Fools Day 2024!

    • Kaizen can help firms prepare for the regulatory changes mentioned above. For a conversation with Alan or one of our regulatory specialists, please contact us.
  • CFTC warns firms to fix swap data errors before the ReWrite

    CFTC warns firms to fix swap data errors before the ReWrite

    With just under six months until the implementation of the CFTC ReWrite, the CFTC’s advisory letter 22-06 (Friday 10 June) is a timely reminder of the upcoming verification, correction and notification requirements. These rules [Part 45.14 – Correcting errors in swap data and verification of swap data accuracy] include obligations for firms to:

    • Frequently verify the “completeness and accuracy” of the data held at the Swap Data Repository (SDR)
    • Fix any errors they discover “as soon as technologically practicable” following discovery of the error
    • Notify the CFTC where they have determined they cannot fix any errors within the maximum 7 days permitted for “timely corrections”.

    One element of these rules that is proving contentious amongst the reporting firms is the requirement to verify the errors based on the open trades on the ‘Open Swaps Report’ produced by the SDR but to also fix any dead swaps that are terminated, matured, or otherwise closed within the same seven day time limit as the open swaps. Trying to determine the population of dead trades impacted by the same issue is likely to be challenging in itself. And then submitting the corrections to those dead trades within the seven day period is likely to be very challenging.

    Advisory letter 22-06 provides some additional details around how the firms should notify the CFTC (by email) when they determine they will be unable to correct them within the prescribed seven day period from detection of the error.

    The advisory goes on to specifically call out an issue that Kaizen Reporting frequently detect in our CFTC Accuracy Testing: Cleared trades remaining as open swaps in the SDR long after the clearing process would have replaced them and swaps that have been terminated but left open in the SDR.

    Swaps that erroneously appear in SDRs as open swaps, despite having been terminated, account for a significant number of existing swap data errors that staff have identified. This type of error results in the accumulation of erroneously open swaps at the SDRs over time, which impedes staff’s use of the swap data.

    Another aspect that might prove controversial or contentious is the statement that a reporting counterparty may have an obligation to correct errors and terminate trades where the error was reported by another entity such as a clearing house. And by extension of this principle presumably also where the original error was reported by a SEF.

    Regulation 45.4 requires reporting swap terminations as an element of continuation data, thereby providing SDRs with the information needed for them to change a swap’s status from open to closed. For example, in the case of cleared swaps, the obligation to report the termination of an original swap at the SDR is on the derivatives clearing organization (DCO). In addition to this continuation data reporting obligation, counterparties to the original swap have an independent obligation to correct errors of this nature.

    So a reporting counterparty detects an issue in the ‘swap creation data’ submitted by a DCO and as well as having an obligation to notify the DCO of the error the counterparty might also have an obligation to fix that error themselves. I think more details will be needed from the CFTC for firms to understand these seemingly conflicting obligations and put workable procedures in place around it. It would be good if the CFTC could also confirm whether this principle is applicable to SEF submitted ‘swap creation data’ errors as well, given the example cited was a DCO.

    The advisory then reminds firms that the obligation to fix errors dates back to the original 2012 rules, stating that firms have been aware of the upcoming part 45.14 obligations since September 2020 and tells them to get cracking with fixing stuff before the CFTC ReWrite go-live on 5 December.

    Accordingly, SEFs, DCMs, and reporting counterparties should review, as early as possible, their open swaps data in order to identify and correct any errors. Correcting outstanding errors in swap data, including swap data for swaps that are no longer open swaps but are maintained by an SDR as if the swaps were still open swaps, in advance of December 5, 2022, may reduce the number of Swap Data Error Correction Notification Forms that SEFs, DCMs, and reporting counterparties will be required to submit to self-report swap data errors.

    Kaizen has been advocating precisely this approach for a long time now. Use the time before the ReWrite implementation as a window to find and fix as many errors as possible before you need to start notifying the CFTC of these errors.

    So what are you waiting for? Get cracking and fix stuff!

    • Read the full press release on the CFTC website.
    • For a conversation with Alan or one of our regulatory specialists about the topics mentioned above, please contact us.
  • New body for APAs and ARMs grows legs

    New body for APAs and ARMs grows legs

    Authors: Simon Appleton and Chris Machin

    Last week’s announcement of the formation of APARMA, a Trade Association (TA) for Approved Reporting Mechanisms (ARMs) and Approved Publication Arrangement (APA) providers, is long overdue. The implementation of MiFID II brought with it a significant increase in the rules and regulations covering ARMs and APAs (which took over from Trade Data Monitors (TDMs), under MiFID I) and with it a lot more risk and the potential to be penalised for breaching their obligations. 

    Collectively known as Data Reporting Services Providers (DRSPs), ARMs and APAs facilitate the effective supervision and transparency of financial markets allowing regulators and investors to receive timely and comprehensive trading information. 

    The other category of DRSP is Consolidated Tape Providers (CTPs) which collect trade reports from APAs and Trading Venues. Forthcoming changes to regulations in the UK and EU could mean that it’s just a matter of time before this new trade body brings CTPs into the fold but likewise there is huge debate about the need and effectiveness of such a requirement.  That debate will surely continue…

    The rules governing Data Reporting Services Providers are substantial and are defined in the FCA’s Regulatory Framework, which comprises:

    MiFIR also outlines in Regulatory Technical Standard (RTS) 13 the obligations covering the authorisation, organisational requirements and the publication of transactions for DRSPs. The most significant aspects are in Articles 10 and 11, which set out the rules governing how ARMs, APAs and CTPs should manage incomplete or potentially erroneous information.

    The European Securities and Markets Authority (ESMA), recently published Draft RTS setting out criteria for the sound and prudent management of DRSPs as well as for their operational effectiveness under MiFIR.  Many reasons have contributed to the reduction in the number of ARMs and APAs over time, including additional regulations, data and rule complexities, operational risks, Brexit and reduced margins to name a few.

    However, the formation of APARMA will give members renewed purpose, momentum and a unified, louder voice when speaking with regulators and clients alike.

    Following yesterday’s ‘Dear CEO’ Letter from the FCA, we are seeing the regulator outline their approach to supervision:

    “This letter outlines our view of the key risks of harm in the DRSP portfolio and communicates what we expect DRSPs to do to minimise potential risks to consumers and market integrity from failures to meet regulatory requirements”. 

    The FCA will also expect the DRSPs to evidence the actions they have taken in response to this letter. 

    Along with this, the FCA have reiterated that enforcement, reviews and assessments will be applied “with real and meaningful consequences for firms who do not follow the rules” and highlighted their take on the key risk of harm:

    • The Market is concentrated among a small number of DRSPs, limiting the opportunity for clients to change provider and may lead to lower incentives to provide high quality services
    • DRSPs may have inadequate systems and controls to identify incomplete and potentially erroneous trade or transaction reporting data
    • Insufficient operational resilience may lead to disruption for market participants, consumers and Regulators, or the loss, compromise, or lack of availability of data

    This is a clear indication that competition is essential and encouraged to create higher levels of reporting services, along with complete and accurate data, that has been clearly defined over many years, since pre-MiFID II inception. APARMA lobbying will be key to this evidencing of operational resilience but the FCA have stated their expectation of an “Open and co-operative relationship”, which I’m sure will be tested from both sides.

    From Kaizen’s perspective, we have been checking the accuracy and completeness of trade and transaction reporting across multiple regimes for a nearly a decade now, identifying potentially erroneous reporting.  The FCA’s guidance is clear and firm but the new trade association for APAs & ARMs is perfectly timed to build their point of view around the complexities of MiFID II. Hopefully, all parties can work together to create an improved and innovative framework in a post-Brexit regulatory environment.

    • For a conversation with one of our regulatory specialists about the topics mentioned above, please contact us.
  • ASIC Rewrite Consultation #2: Seeing Double?

    ASIC Rewrite Consultation #2: Seeing Double?

    The Australian Securities and Investments Commission (ASIC) has published their second consultation on updates to their Derivative Transaction Reporting rules, building on their first consultation (CP 334) and addressing issues that they had previously deferred. As expected, ASIC continues to explore the correct blend of data elements sourced from the CPMI-IOSCO Critical Data Elements (CDE), foreign jurisdictions, and of their own making to determine the final reporting requirements.

    Unexpectedly, ASIC is now proposing to implement these changes through two separate rewrites, taking effect in October 2023 and April 2024 respectively. Here we’ll be discussing Phase 1, the “draft remade ASIC rules” and Phase 2, known as the “draft amended ASIC rules”, as well as the continued focus on data quality by ASIC.

    Phase 1

    The first phase introduces format and validation requirements for existing fields at the regulatory level for the first time for ASIC reporting, as well as redefining and renaming many fields.

    ASIC stresses that their intent is not to require substantive changes to reporting practices beyond the UTI and LEI during Phase 1, as reflected in the proposed format requirements, but widespread changes to field names and definitions may make current practices incorrect even if the Trade Repository (TR) continues to accept such reports.

    Moreover, even if changes that reporting entities make to their workflows are limited in scope and scale, the shift to ISO 20022 XML for Phase 2 means these changes will not last beyond the six months that Phase 1 will be in effect. As Phase 2 also requires the updating of outdated reports to comply with the new rules, including those made during Phase 1, there will also be no long term effect on the coherence of data at the TR.

    Beyond specification changes, Phase 1 cleans up the rules, removing outdated provisions and consolidating exemptions, and fully implements the UTI and the LEI. LEI implementation is as expected, with the significant clarification that non-LEI identifiers are not required to be updated for existing transaction reports that contain non-LEI identifiers.

    Responding to feedback in the first consultation, the UTI generation waterfall now prioritises bilateral agreements, allowing reporting entities to bypass challenges in reconciling strict hierarchies between different jurisdictions. Unlike other regulators, ASIC has also included a safe harbour provision where the non-UTI generating party does not receive a UTI in time for reporting.

    Phase 2

    The proposed second phase of the rewrite implements many of the changes originally proposed in CP 334, implementing various CDE, UPI, and ISO 20022 XML for reporting. ASIC also proposes the re-reporting of existing transactions with a minimum remaining maturity, in line with MAS and ESMA proposals.

    The CDE are largely implemented as originally proposed although ASIC has removed and edited a number of data elements. One area of concern is the number of changes ASIC proposes to make to CDE field definitions, which may limit a reporting party’s ability to easily standardise their reporting. Even where these are clarifications or improvements, they still introduce an additional analysis requirement that the CDE were designed to resolve.

    ASIC intends to require the UPI to be reported but also proposes to include a number of data elements to account for product data which cannot be included when generating a UPI and may complicate standardisation of ISO 20022 XML for reporting these products. ISO 20022 is not discussed at length during this consultation, but ASIC does intend to require ISO 20022 XML for Phase 2 reporting and we expect to see more detail in the third consultation.

    Surveillance and Data Quality

    In the first consultation ASIC discussed ‘alternative reporting’ under the current rules, where some non-Australian entities can fulfil their ASIC reporting obligations by complying with their domestic reporting requirements. ASIC intended for these foreign trade reports to be additionally designated as ASIC-applicable and for the TR to provide ASIC with access to these reports, but this has never happened, and ASIC has never had access to this data.

    Understandably, ASIC are considering removing the alternative reporting provision altogether from the rules and applying the standard reporting requirement, as well as other options to enforce ASIC’s access to the relevant trade data. ASIC has not concluded this discussion, but all options lead to much more scrutiny of this data in future, so affected parties should ensure that they are prepared to fulfil their obligations under the final rules.

    ASIC also proposes to remove the delegated reporting safe harbour provision in Phase 1, following objections during the first consultation, citing low data quality, and will hold entities who delegate strictly responsible for the quality of reporting. Entities who delegate their reporting will need to ensure they can adequately assure the quality of reporting on their behalf, especially in the face of ASIC’s stated dissatisfaction with current data quality.

    Summary

    Throughout the consultation, it’s striking how frequently ASIC includes analytics from existing reporting data to justify its reasoning, discussing reporting practices across many fields and at times, cutting through aggregated data to the reporting behaviour of just a few entities. Alongside plans for greater scrutiny of alternative and delegated reporting, it’s evident that ASIC is already taking a closer look at derivatives data.

    With re-reporting on the horizon, two rewrites, and a third consultation still to come, ASIC clearly sees room for improvement on all sides of the reporting equation and is prepared to put in the effort and focus to get it right. On their part, reporting entities will need to make sure they have the resources and knowledge to match.

    • For a conversation with John or one of our regulatory specialists about the topics mentioned above, please contact us.
  • UK Takeover Panel change: Miscellaneous Code Amendments

    UK Takeover Panel change: Miscellaneous Code Amendments

    The UK Takeover Panel released its response Statement on Miscellaneous Code Amendments on 5 May 2022.  From a shareholding disclosure perspective, the main change is the exclusion of custody and depository positions, which will take effect on 13 June 2022.

    “A custodian or depository acting in the normal course of its business will not be treated as having an interest in the securities it holds as a result of that activity” Source: RS 2021/1, 5 May 2022 published by The Takeover Panel. 

    Complex Reporting

    UK Takeover Code Rule 8 is complex to comply with; especially if your business is connected to a Takeover deal or has a structure including both investment banking and asset management activity. 

    Understanding which disclosure form applies to a specific deal and trading activity is complicated, due to the many factors affecting which disclosure form you should be using for your disclosure submission. These include:

    • Are you connected to the deal?
    • What business type is holding the position?
    • Was it a proprietary trade?
    • Do you have recognised intermediary status?
    • Is the trade for a discretionary or non-discretionary client?
    • Do you have EPT status?
    • Do you have EFM status?

    Source:  UK Takeover Panel Website

    In addition, the submission deadlines themselves are difficult to comply with, especially if you are utilising a manual process. If you are connected to a deal you must disclose by no later than 12pm on the following business day, otherwise the deadline is 3:30pm.

    Automate your position and trade data

    Kaizen has a fully automated solution that will remove the decision making process for you, allowing for increased efficiency and accuracy. Our service processes your position and trade data and alerts you to your disclosure obligation in the format of the relevant Takeover Panel form. This means that you are ready to disclose first thing in the morning; simply click on “generate disclosure” and away you go! 

    Using our solution means that you save time and remove the risk of human error and late reporting.

    Did you know there are over 20 countries globally that have a form of Takeover Reporting requirement?  We cover those too. 

    • For a conversation with Lucy or one of our regulatory specialists about the topics mentioned above, please contact us.
  • Data at the forefront of FCA’s annual business plan

    Data at the forefront of FCA’s annual business plan

    The FCA recently published its 2022/23 business plan and short to medium-term strategy.  The three-year strategy and yearly business plan are of significant interest as they provide an insight into current areas of primary focus for the regulator.  In this blog, we highlight the matters that are most likely to impact regulatory reporting as well as other areas of interest to us and our clients.

    Data led regulation

    In terms of how the FCA will operate going forwards, the key changes relate to the way the regulator will make use of data and use real time intelligence to see how firms and markets are performing generally but also to help them recognise and detect risks at an early stage. 

    Although the FCA’s data strategy will be published in the coming months it’s already clear that the regulator is keen to become data-led and is looking to establish what information, technology and staff are needed to achieve its objectives.  Over time, it will become increasingly likely that any rule changes will be based on actual data.

    Market integrity and confidence

    The FCA actively monitors transaction reports and other data to identify insider dealing and market manipulation and has emphasised that it’s looking to deliver assertive action on market abuse, and increase the perceived effectiveness of their action to promote market integrity, by introducing a new perception metric.

    Separately, the FCA is looking to deliver the Market Surveillance Refresh project and Market Data Processor (MDP) refresh to improve alerting, triage, enquiry analytics and increase their detection capability through advanced analytics and improved data coverage.

    Promoting competition and positive change

    One of the FCA’s three areas of focus will involve tailoring rules to better suit UK markets in a global context to help prepare financial services for the future.  Ensuring the UK is one of the leading markets of choice for issuers, intermediaries and investors alike is designed to reinforce the UK’s position in global wholesale markets.

    Interestingly, the eagerly awaited MiFID Transaction Reporting Consultation paper will indicate how much weight the FCA places on each of the three priorities outlined above.  In the meantime, it’s clear that the role of data is assuming more and more importance with the regulator as they determine exactly what data they want to receive and how to best use the vast array of reports, transactions and information received since the financial crisis.

     

    • For a conversation with Simon or one of our regulatory specialists about the topics mentioned above, please contact us.
  • ESMA’s Data Quality report (EMIR) – five critical takeaways

    ESMA’s Data Quality report (EMIR) – five critical takeaways

    During April, ESMA released the latest version of its EMIR and SFTR Data Quality report.  Kaizen’s Jonathan Lee commented on the SFTR elements in an earlier blog. Below we take a deep dive into the key takeaways regarding EMIR Reporting.

    1. Valuation and collateral submissions are a hot topic for ESMA

    Using a simple word count, collateral and valuations are mentioned more than any other topic in this report.  Collateral and valuation reporting is a daily requirement for Financial Counterparties (FCs) and Non-Financial Counterparties that are above the clearing threshold for OTC trading (NFC+s).

    ESMA stresses the ‘importance of valuation data for economic and financial risk analysis’, evidencing what is clearly a key component of EMIR Reporting and a continuing area of scrutiny for authorities.

    The report highlights that ‘more than 20%’ of open derivatives do not receive an updated valuation, despite the clear reporting requirement to do so.  As mentioned in Jonathan Lee’s SFTR analysis, many of the metrics included are ‘flawed’, including this ‘20%’ figure, as the sample analysis only took into account derivatives with valuations over 15 days old, rather than those over one day old.  As part of their daily reporting requirement, firms are expected to provide collateral and valuation updates every day, and if this is truly a key focus for ESMA, future analysis would be far more accurate (and more damning), if it followed the actual reporting requirement.  For this reason, it is a fair assumption that far more than 20% of open derivatives are not receiving daily collateral or valuation updates.

    Firms would be wise to note this important discrepancy and ensure that all collateral and valuation reporting reflects the daily reporting requirement ahead of future iterations of the report. More importantly, ensure all collateral and valuation reporting is accurate ahead of enhanced scrutiny by regulators for this key area of EMIR reporting.

    2. Pairing remains a problem for EMIR Reporting

    An important issue the report highlights is the lack of successful reconciliation.  An important and telling statistic is that only ‘60%’ of pair-able submissions do successfully pair.  This shows an upward trend from 40% to 53% and now 60%, since ESMA began tracking the yearly statistic.

    The pairing phase of reconciling the two sides to each derivative relies on the reporting counterparty LEI, other counterparty LEI and the UTI to create a unique ID for that submission. These allow the trade repositories to search for the other report submission pertaining to the same derivative.  Only derivatives where both sides are required to be reported in the same jurisdiction are included in these statistics.

    The whopping 40% of all reportable derivatives that fail to pair will be due to a limited range of factors, such as one counterparty having not reported the derivative successfully, one or both counterparties reporting with an incorrect LEI or UTI, disagreement on the number of trades to be reported for that derivative, and finally, general processing issues within the trade repository pairing process.

    ESMA condemns this large volume of unpaired derivatives as ‘not satisfactory’, notably as the reporting of these fields has been mandatory since reporting began in 2014.

    The pairing of derivatives is vital to the success and efficiency of EMIR Reporting, which is inherently focused on the level of risk and exposure in the market.  If two successful reporting submissions for the same derivative do not include the correct identifiers to enable pairing, the authorities will simply think that two unrelated single sided submissions have been completed, and that they are (incorrectly) awaiting the other side of the derivative to be reported.  Not only is this poor from a completeness and accuracy point of view, but vitally the exposure could potentially be seen as double the volume of market risk currently live for both counterparties and the economy at large.

    3. Data provided to the NCAs isn’t always the same as data provided to ESMA

    Generally, the data reported to the trade repository is the regulator’s view of derivative activity at each firm.  NCAs view the specific sections of EMIR data that they have been mandated to view, and ESMA has the ability to see all data, due to its regulatory oversight of EMIR Reporting for EEA firms.

    However, the report highlights that data is provided to the various authorities in different ways, such as ‘TRACE’ or via sFTP.  Also highlighted was the admission that when the trade repositories allocate data to each NCA, this does not necessarily match what ESMA believes the NCA should see, resulting in both over and under reporting of data to the NCAs.

    Whilst this finding does not impact the ability of counterparties to submit reports successfully, it does limit the ability of NCAs to efficiently supervise all firms to which they are mandated. And in practical terms it is extremely hard for an NCA to identify such shortcomings in the quality of data that they have been provided.

    4. Non-reporting and timeliness of reports

    Approximately ‘10%’ of the sample of EMIR reporting tested under the report are reported late by counterparties.  Non-reporting dropped sharply to ‘5%’ but this figure is likely to be due to Brexit splitting the two EMIR Reporting regimes across EEA and UK based firms.  Again, this is a good example of a likely ‘flawed’ metric used in this report.

    Strangely the analysis does not take into account the conversion from local to UTC Coordinated Universal Time, despite UTC being a well-used reporting format under many EMIR fields, including reporting timestamp.  Further to this, the analysis does not take into account ‘public, bank or national’ holidays, even though ESMA admits in this report and other sources that they should be taken into account and adding to the flawed nature of many metrics included in this report.  As previously argued, such analysis should absolutely follow the reporting requirement to which firms are required to adhere to, instead of ‘moving the goal posts’ for the ease of data analysis.

    The report also mentions the sharp decline in non-reports to less than ‘5%’, but admits that this has been dramatically impacted by Brexit (reported derivatives dropped ‘by 50%’) which split the reporting requirement into two separate EMIR jurisdictions.  For this reason, it is worth noting that it is now significantly harder to gauge an accurate view on non-reporting for the same derivatives, where counterparties are split across the EEA and UK.

    5. ESMA has great expectations for all impacted bodies

    The final key takeaway from the report is that a lot more is explicitly expected from all stakeholders of EMIR Reporting.

    For reporting counterparties, ESMA includes strong language on the expectations of firms, namely that they are expected to have all necessary checks and balances in place ‘to ensure completeness, accuracy and timeliness’ of reported derivatives.  In addition, firms are expected to ‘actively engage’ in identifying and remediating any report rejections, reconciliation breaks, and other data quality issues for ‘already reported data’.

    In short, firms are required to take ownership and ensure high quality data for both new submissions and anything previously reported.  Importantly, this will include all delegated reporting, remembering that even if firms delegate the action of reporting, the obligation of reporting remains with the counterparty to the derivative.  In addition, it will also impact firms required to perform what has informally become known as ‘mandatory delegated reporting’, where an FC has executed an OTC derivative facing an NFC- in the same reporting jurisdiction.

    For the authorities, they have an explicit commitment to continue perusing improved data quality under EMIR.  ESMA and the NCAs ‘will take further action’ to improve the quality of data where ‘insufficient quality’ has been identified and prevails.Q

    And finally for trade repositories, they have been identified as required to increase the quality of reports provided to the NCAs, as well as ensuring the consistency and accountability across standard ‘end of day reports’ to firms, such as the ‘trade state report’ and the ‘trade activity report’.

    What’s next?

    In summary, the report continues data quality themes initiated in last year’s report, but with renewed vigour, more examples of wrongdoing, and arguably significantly stronger wording from ESMA. 

    Valuations and collateral reporting will be a key focus of NCA scrutiny over the next 12 months, and firms would be wise to prioritise this in their data accuracy reviews, not only of future reporting, but also of any historical submissions to the trade repository.

    We welcome the focus of such reports, but are keen to see future versions encompass all reporting requirements, and importantly, we urge ESMA to ensure that all metrics at least mirror the prescribed reporting requirements, instead of being influenced by ease of calculation. 

    And finally, we are very keen to see the same style of scrutiny for UK EMIR reporting from the FCA, giving UK firms ample opportunity to review any reporting shortcomings ahead of the looming EMIR Refit changes for derivatives reporting. 

    Read the consultation paper on the FCA’s website.

    • Do you know the true state of your EMIR reporting data quality? If you are in any doubt about how the quality of your EMIR trade and position level reports measure up, please contact us.
  • ESMA’s Data Quality report (SFTR) – window dressing or reliable data?

    ESMA’s Data Quality report (SFTR) – window dressing or reliable data?

    ESMA’s EMIR and SFTR data quality (DQ) report 2021, published on Friday 1 April is the first to truly incorporate SFTR, after the very limited feedback provided in the 2020 report given the newness of the regime. We have covered the EMIR aspect of the report in a separate blog.

    It is important to give careful consideration to the DQ report as it reflects some of the National Competent Authorities’ (NCA) and ESMA’s areas of focus. However we would caution firms against using this as the principle measure of data quality. This is because the methods used are flawed and unlikely to reflect the much broader scope of analysis used by NCAs (who are after all, your regulators) in order to detect market abuse, systemic risk and ensure complete, accurate and timely reporting.  

    We continue to advocate the best, most pressing data quality consideration that ESMA should address is the need for regulatory certainty and tightly defined reporting field definitions where they do not exist today. On a more positive note, we have it explicitly in writing for the first time that,

    “Reporting counterparties are expected to have processes, systems and controls in place to ensure completeness, accuracy and timeliness of the reported information.”

    and

    “Counterparties are strongly encouraged to use the regulatory data in their own internal risk and compliance management processes.” 

    On a completely different note, one of the most interesting things to come out of the report centres on one reporting counterparty’s failure to report terminations of open SFTs, resulting in a significant exaggeration of the value of outstanding transactions across the market for most of 2021.  This is something firms should take note of and ensure that they are not putting themselves in the same position.

    The 2021 DQ report focus

    • ESMA launched the Data Quality Engagement Framework (DQEF) for SFTR in 2021 to coordinate efforts to supervise reporting counterparties and trade repositories (TRs) with the NCAs
    • The DQEF was tasked with focusing on the timeliness of reporting, rejections and pairing. We would caution that while some (but not all) timeliness issues may be identified, neither rejections nor pairing statistics will give a material measure of data quality issues
    • Even this round, not all NCAs were able to contribute to this analysis and in the meantime will focus on building systems and supervisory engagements
    • The 2021 SFTR DQ exercises were performed on weekly datasets taken in June and November 2021, focusing on timeliness of reporting, reports rejected under the validation rules and unsuccessfully paired reported records.

    ESMA’s conclusions

    1. Reported volumes fell by approximately 50% following Brexit
    2. Approximately 10% of SFTs are reported late (after T+1)
    3. Rejections have been low (around 2%)
    4. Duplicate reporting “does not pose major issues” although there is limited scope for identifying duplicates reported across two TRs, only intra-TR
    5. Reconciliation pairing rates “have been only around 60%”
    6. Reconciliation rates for loan and collateral data “have been low but increasing to around 40% and 30% respectively”
    7. TRs do not agree on the number of records they reconcile against each other, indicating possible inter-TR reconciliation issues
    8. ESMA believes that the use of ISO 20022 XML end-to-end reporting has brought quality and accessibility benefits and that it is already seeing positive trends in rejections and reconciliations
    9. ESMA was able to identify one counterparty failing to terminate their open SFTs (presumably a systemically significant counterparty given the size of the apparent bias), a factor that continued to inflate the volume outstanding until November 2021 when the NCA ensured it sent back-loaded early terminations.

    Kaizen conclusions

    1. The vast majority of reporting issues that Kaizen’s ReportShield™ Accuracy Testing identifies relate to reports that have passed the TR validation rules. Our testing tells us that there remains widespread issues with ‘valid but wrong’ reports. These are reports that pass validation but still contain incorrect data. Likewise, having an SFTR report accepted by the TR is setting the bar very low.  Sadly, the revised validation rules will do little to alleviate this, with limited true “validation” (many totally implausible values will still pass as valid) and a significant lack of effective rules on field conditionality too.
    2. To suggest that even a fully reconciled SFTR report is accurate is naïve in itself, given the prevalence of delegated reporting and data aggregators and enrichers in the reporting space.  Two wrongs may match each other but it does not make them right.
    3. In order to illustrate how ineffective reliance on pairing & matching is with regard to data quality, it is important to estimate the proportion of reports that are subject to the reconciliation, paired and successfully reconciled. The honest answer is that these figures are extraordinarily low.

      For example, the public data* tells us that at most during any period, on average, only c.20% of reports are two sided.  Of these, ESMA states that around 60% of them pair (12% of total reports). Of this 12% of paired reports, 40% of loan reports match (less than 5% of all reports) and around 30% of collateral reports match (less than 4% of reports).

      Continued and persistent focus on ineffective DQ measures that encapsulate less than 5% of reports seems a very inefficient mechanism for ensuring “the usability of the data for monitoring of financial stability risks.”

    4. If you wish to truly establish the data quality of your SFTR reporting, we recommend that reporting counterparties receive independent quality assurance through frequent, periodic regulatory testing.

    To reflect on the most poignant observation from this data quality report, a reporting firm’s internal controls should bear in mind that transactions remain live in the database until they reach their contractual maturity date, a modification adds a contractual maturity date or they are early terminated. Reporting open transactions and forgetting is likely to be met with the wrath of the NCA.    

    • For a conversation with Jonathan about your SFTR Reporting data quality or a no-obligation review of the quality of your reporting, please contact us.

    *For a consolidated view of the public data, visit ICMA’s website.

  • Crypto to remain under the spotlight: MiFID view

    Crypto to remain under the spotlight: MiFID view

    It seems like not a week goes by when we don’t hear something about the regulation of crypto. It is clear that regulators globally are looking closely at the risks posed by digital assets to consumers, markets and the financial system.

    More regulation is on the way

    In the past few weeks, Russia’s invasion of Ukraine has brought crypto into sharp focus due to concerns that it could be used to circumvent economic sanctions.  More generally, in the EU, the proposed Markets in Crypto-Assets Regulation (MiCA) will change the regulatory perimeter for crypto-currencies and derivatives on crypto currencies. 

    In the UK, the FCA recently reminded regulated firms of their obligations when interacting with cryptoassets and related services, whilst also looking to set up a new crypto department.  Across the pond, the Senate is showing increasing interest in crypto, holding several hearings on digital assets and their regulation, an area the CFTC and SEC are actively looking at.

    How regulators are handling crypto assets differs greatly in Asia. Crypto transactions are now considered criminal financial activity in China, whereas retail cryptocurrency advertisements have been banned in Singapore.  The HKMA’s recent discussion paper on Crypto-assets and Stablecoins talks about a risk-based approach to handling risks posed to monetary and financial systems.

    Additional regulation will be broadly welcomed by the crypto community and investors, but that is still some time away.

    So what are the reporting obligations for crypto currencies under MiFID?

    Since 2018 when we saw the FCA comment that “we do not consider cryptocurrencies to be currencies or commodities for regulatory purposes under MiFID II”, there has not been much change in the reportability of crypto derivatives under MiFID.   

    Spot trading in crypto currencies is not in scope for MiFID reporting and as with FX and commodities, where there is a derivative with a currency or commodity underlier, they will not be reportable unless the derivative itself is admitted to trading on a trading venue (TOTV).  This is irrespective of the classification of crypto currencies by regulators.

    ESMA’s Opinion Paper in May 2017, expanded the scope of reportable instruments to include OTC derivatives “sharing the same reference data details” as TOTV instruments. In practice, this process is managed by the ANNA Derivative Services Bureau (DSB).  The DSB sets out the relevant instrument data details, after consultation with the industry, that are to be assessed to determine effective equivalence to TOTV instruments.  These go beyond the reference data details pointed to by ESMA.   This change made it harder for firms to establish reportability on an instrument by instrument and trade by trade basis. 

    What instrument types are transaction reportable under MiFIR?

    • Spreadbets and Contract for Difference (CFDs) with crypto-currency underliers that do not share the same reference data details as TOTV instruments admitted to trading are not reportable.
    • Exchange traded options and futures with crypto underliers that are admitted to trading on a third country venue are not reportable. For example, the trading of bitcoin futures on the CME is not reportable because the CME is not a trading venue.

    Based on our review of UK Financial Instruments Reference Data System (FIRDS) we have identified the following categories of crypto related instruments. The table below shows the number of crypto related financial instruments on UK FIRDS by instrument category ISO 10962.

     

    Instrument category   

    Number of instruments

    FX Forwards   

    8

    Entitlements (rights)   

    433

    Equities   

    126

    Debt instruments   

    133

    Collective investment vehicles   

    3

    Total   

    703

     

    There are some venues that do admit to trading crypto currency futures.  Where those instruments are traded they are reportable. Examples are:

     

    Post Brexit    

    UK reportable   

    EU reportable   

    Spot crypto-currencies   

    N

    N

    LMAX Digital (Gibraltar)   

    Y

    N   

    Crypto Facilities   

    Y

    N

    CME Bitcoin Futures     

     N

    N  

     

    Under UK MiFIR, the instrument has to be traded on a trading venue, or the immediate underlying has to be traded on a UK, EU or Gibraltar trading venue to be reportable.

    Under EU MiFIR, the instrument has to be traded on a trading venue, or the immediate underlying has to be traded on a trading venue within the EEA, to be reportable.

    A path away from complexity

    As can be seen from the above, assessing reportability of crypto instruments under MiFIR is challenging and it is built on an ever-changing set of data.  This makes the likelihood of under-reporting much higher should venues start admitting DSB crypto derivatives. 

    Assessing instrument reportability under EU MiFIR will be simplified after the recent MiFID review by partially moving away from TOTV for derivatives and incorporating an ‘SI approach’ but that’s a couple of years away.

    We are waiting to hear from the FCA to know whether the UK regulator intends to follow ESMA’s lead to simplify this area. Whether the FCA mentions crypto specifically in its long-awaited MiFIR Transaction Reporting consultation paper remains to be seen but it is something we would welcome.

    • For a conversation about reporting crypto under MiFIR or any other regulation, please contact us.
  • Focus réglementaire de l’union Européenne – Qualité des données déclarées sous MiFID II

    Focus réglementaire de l’union Européenne – Qualité des données déclarées sous MiFID II

    Peu importe où vous regardez, quelqu’un, quelque part est en train de parler des révolutions technologiques et de données en générale. Les données sont désormais omniprésentes dans nos vies, que ce soit à travers le nombre de pas que nous faisons quotidiennement ou via la quantité d’actions négociées chaque jour. Il est donc impératif que ces données consommées soient très précises pour nous permettre de prendre des décisions très importante. Cette philosophie et cette approche est reprise par les régulateurs financiers de toute l’Europe avec leur attention qui se concentrent sur l’amélioration de la qualité des données pour 2022.

    Parmi la liste des priorités de supervision du secteur des services financiers récemment publiées, l’Autorité des Marchés Financiers (l’AMF) a souligné et a mis beaucoup d’importance sur la qualité et la précision des données déclarées par les entreprises d’investissement et les échanges financiers. Il est indispensable que ces déclarations soient précises pour la surveillance des activités de trading et pour détecter les manipulations et les abus du marché.

    Ce n’est, par ailleurs, pas un hasard si la « qualité des données » figure parmi les deux seuls thèmes des régimes déclaratifs introduits par la directive MiFID II. En effet, l’Autorité européenne des marchés financiers (ESMA) engage les autorités nationales compétentes (NCA) à tenir compte dans le cadre de leurs activités de surveillance en 2022. L’autre thème concerne les frais et les commissions facturés par les sociétés de gestion.

    L’accent mis sur la qualité des données est en partie un sous-produit du fait que les sociétés de gestions ont commencé à déclarer leurs transactions qu’en vertu de la MiFID II depuis 2018, alors que le côté vendeur fait des déclarations en vertu de la MiFID I depuis 2007. Ceci représente un autre exemple d’élaboration de politiques axées sur les données par les régulateurs qui, de manière compréhensible, deviennent de plus en plus axées sur les données.

    Devenir davantage axé sur les données élimine la nécessité pour les régulateurs d’allouer leurs ressources limitées en fonction du risque, où l’accent est principalement mis sur les grandes entreprises, par exemples à travers des visites de supervision et de correspondance, permettant ainsi que les petites entreprises soient supervisées à l’aide d’une approche basée sur des événements ou des revues thématiques. En utilisant à meilleur escient les données qu’ils reçoivent à l’aide d’outils d’analyse de données permet une revue plus systématique et plus approfondie de toutes les activités des entreprises autorisées concernées. Ils ne seront plus contraints d’examiner des échantillons d’activité car les capacités informatiques disponibles aujourd’hui permettent d’analyser toutes les données minutieusement.

    La prévention des abus de marché au sein du secteur des sociétés de gestion était également l’une des priorités thématiques de surveillance de l’AMF pour 2021. Certes, mieux vaut prévenir que guérir, on sait que les régulateurs européens utilisent également les déclarations de transactions transmises par les acteurs buy-side comme sell-side pour surveiller des délits initiés et des manipulations de marché ainsi que rechercher les anomalies du marché.

    Cependant, il existe depuis longtemps un gap dans le réseau de surveillance en ce qui concerne les gestionnaires de fonds d’investissement alternatifs (Alternative Investment Fund Managers) et les sociétés de gestion UCITS qui fournissent des services MiFID à des tiers. L’ESMA prend donc des mesures supplémentaires et propose que ces entreprises commencent à déclarer les transactions sous MiFID pour la première fois à la suite de leur revue de l’année dernière.

    L’ESMA suggère également d’introduire un indicateur de catégorisation de client de MiFID, un exemple qui démontre que les régulateurs utiliseront les rapports des transactions déclarés non seulement pour surveiller ‘les marchés’ mais également pour surveiller les ‘entreprises d’investissements’.  Cet indicateur de catégorisation des clients MiFID permettra aux régulateurs européens d’évaluer à grande échelle et de manière automatisée si des produits inadaptés ou risqués sont vendus aux clients de détail.

    Un régulateur guidée par les données

    Jessica Rusu, responsable des données, de l’information et du renseignement de la FCA, a déclaré lors du forum RegTech de la FCA le 10 février 2022 qu’une industrie axée sur les données a besoin d’un régulateur axé sur les données. La FCA donne la priorité à l’utilisation de la science des données, des technologies numériques et des capacités de renseignement pour suivre le rythme des changements dans les services financiers.

    Leur division de données, technologie et innovation cherche à construire une révolution numérique grâce à des projets de science des données et à créer un environnement d’intelligence numérique unifié pour réévaluer la façon dont FCA collecte et analyse les données. Le recrutement des scientistes experts en données est au premier plan de la stratégie de la FCA et permettra au régulateur d’être plus innovant et flexible dans sa façon de réagir aux changements de l’industrie.

    La CSSF explique que des données de mauvaise qualité peuvent engendrer des faux positifs

    La Commission de Surveillance du Secteur Financier (CSSF), le régulateur luxembourgeois a récemment émis un communiqué de presse pointant le doigt sur la qualité médiocre des déclarations de transactions qu’il reçoit en vertu de la directive MiFIR.  Attentive à la qualité des données, la CSSF a identifié un certain nombre d’erreurs reportés fréquemment par les entreprises. Elle reconnaît toutefois que ses observations ne sont pas à la mesure de la montagne de problèmes rencontrés par ces entreprises et ne sont peut-être pas les plus flagrantes.

    Le régulateur luxembourgeois souligne l’importance cruciale des déclarations de qualité pour pouvoir détecter des abus potentiels du marché. Elle indique en outre que des données de piètre qualité peuvent engendrer des faux positifs et représenter une violation grave, notamment si les erreurs déclaratives provoquent la dissimulation de possibles cas d’abus de marché.  La CSSF fait rappelle à l’article 47, qui fixe les sanctions, mesures et pénalités pouvant être infligées aux entreprises d’investissement en cas de déclarations erronées en vertu de l’article 26 de MiFIR.

    La période de grâce est donc bel et bien terminée pour les entreprises d’investissement avec les directives de MiFID II étant désormais en vigueur depuis plus de quatre ans.  Ainsi, de la même manière que nous exigeons des données précises dans toutes nos activités quotidiennes, les régulateurs ont besoin de données de meilleure qualité de la part des entreprises d’investissement et échanges financiers.

    Il ne serait pas surprenant que nous commencions à voir des mesures d’activités forcée au cours des 12 prochains mois en ce qui concerne les échecs de déclaration des transactions, en particulier en Europe, où l’ESMA a encouragé les régulateurs à être plus proactives avec leur pouvoir d’exécution.

    • Kaizen Reporting peut non seulement aider les entreprises à détecter les problèmes de qualité dans leur reporting réglementaire, mais aussi les aider à comprendre les obligations de reporting et les mesures correctives
    • Pour une conversation avec Simon ou l’un de nos spécialistes en réglementation, veuillez nous contacter.
  • ESCB transactions to be reportable under UK SFTR

    ESCB transactions to be reportable under UK SFTR

    The FCA has announced that Temporary Transitional Power (TTP) will end at the close of business on 31 March 2022 and that UK established financial institutions and UK branches will be required to report transactions facing European System of Central Banks (ESCB) member banks from 1 April 2022.  This brings UK SFTR further into line with EU SFTR, where the Bank of England is treated as a third country central bank and transactions facing them are reportable. 

    The FCA reiterated, to avoid duplication and in contrast with EU SFTR, no SFTs will be reportable under UK MiFID Transaction Reporting from 1 April 2022. Therefore, SFTs facing the Bank of England will neither be reportable under SFTR nor MiFID.

    This announcement is further evidence that the FCA is keen on limiting the regulatory burden that follows divergence from EU rules.  These changes see greater harmonisation and equivalence with EU SFTR, following the adoption of identical schemas and validation rules from 11 April.

    However, the FCA have demonstrated their pragmatism with steps to reduce the regulatory burden of SFTR reporting where it adds little or no value from a regulatory perspective. Examples of this include the removal of SFTR reporting obligations for non-financial institutions and the removal of any MiFID Transaction Reporting requirements for SFTs.

    Read the full announcement on the FCA’s website.

    • For a conversation with Jonathan about your SFTR Reporting or a no-obligation review of the quality of your reporting, please contact us.
  • SEC proposes new short position reporting disclosure

    SEC proposes new short position reporting disclosure

    As we have seen, shareholding disclosures are already off to a busy start in 2022 and here we go again!  The US Securities Exchange Commission (SEC) has released another disclosure proposal, however this is not an amendment to an existing disclosure rule. This time it is for a new short position reporting rule; Exchange Act Rule 13f-2 and amendments to regulations SHO and CAT to increase market transparency regarding short selling.

    More transparency to short-selling

    On 25 February 2022 the SEC unanimously voted to propose rules and amendments to broaden the scope of short sale-related data available to the investing public and to regulators.  After the 2008 financial crisis, Congress directed the SEC to bring more transparency to short selling. The proposed changes are a response to Congress’s mandate under Section 13f-2 of the Securities Exchange Act, added under Section 929X of the Dodd-Frank Wall Street Reform and Consumer Protection Act, to make certain short sale data publicly available. The SEC states that the proposed rule will help them address future market events, striking a balance between the need for transparency and the price discovery process. This new data will supplement the short sale data that is currently publicly available from FINRA and stock exchanges.

    As we saw with the proposed changes to 13D and 13G beneficial ownership reporting, again the US is not going as far as the EU, UK and certain Asian jurisdictions, which have daily short selling position reporting obligations with thresholds as low as -0.1%. 

    What is proposed?

    Proposed Rule 13f-2 would require institutional investment managers exercising investment discretion over short positions to file the confidential Proposed Form ‘SHO’ with the SEC via EDGAR. The requirement would be to do this within 14 calendar days after the end of each calendar month, with regard to each equity security and all accounts over which the manager meets or exceeds either of the following thresholds:

    1. For any equity security of an issuer in which the manager meets or exceeds either:
      • a gross short position in the equity security with a US dollar value of $10 million or more at the close of any settlement date during the calendar month, or
      • a monthly average gross short position as a percentage of shares outstanding in the equity security of 2.5 percent or more; or
    2. For any equity security of an issuer that is not a reporting company issuer as described above in which the manager meets or exceeds a gross short position in the equity security with a US dollar value of $500,000 or more at the close of any settlement date during the calendar month.

    What detail would they report?

    • the name of the eligible security
    • end of month gross short position information
    • daily trading activity that affects a manager’s reported gross short position for each settlement date during the calendar month reporting period.

    The SEC would aggregate the data by security, maintaining the confidentiality of the reporting managers, and publicly disseminate the data to all investors. 

    What is EDGAR?

    EDGAR is the SEC’s Electronic Data Gathering, Analysis, and Retrieval system.  It is their primary system for submitting documents under the Securities Act of 1933, the Securities Exchange Act of 1934, the Trust Indenture Act of 1939, and the Investment Company Act of 1940. 

    When does the consultation close?

    In light of Proposed Rule 13f-2, the SEC reopened the comment period for Proposed Exchange Act Rule 10c-1. Comments should be received on or before 30 days after publication in the Federal Register or 26 April 2022 (which is 60 days after issuance), whichever is later. 

    How can Kaizen help?

    Kaizen will be closely monitoring these proposals and ensuring our shareholding disclosure monitoring and reporting system is ready for this new reporting regime immediately upon implementation. 

     

    • To read more on the proposal, visit the SEC website
    • To discuss the proposed new rule with one of our regulatory specialists or for a demo of our system, please contact us.
     
  • EU regulatory focus – MiFID II reporting data quality

    EU regulatory focus – MiFID II reporting data quality

    Lire cet article en français

    Everywhere you look, someone somewhere is talking about the tech revolution and data. Data is now an integral and unavoidable part of our lives, from the number of steps we make to the number of stocks traded each day. It therefore goes without saying that the data we consume and use as the basis for important decisions must be accurate. This ethos is being echoed by financial regulators throughout Europe who are turning their focus to improved data quality for 2022.

    The Autorité des Marchés Financiers’ (AMF) recently published its supervisory priorities for the financial services industry, highlighting the importance of accurate data and high quality regulatory reporting from investment firms and trading venues. Accurate reporting data is of paramount importance to the oversight of trading activity and the detection of market abuse and manipulation.

    ESMA MiFID II guidelines

    It is quite revealing that ‘data quality’ in the various reporting regimes introduced by MiFID II is one of only two themes flagged by ESMA, that national competent authorities (NCAs) should take into account, in their supervisory activities in 2022. The other theme relates to costs and fees invoiced by asset managers.

    The focus on data quality is partly a by-product of asset managers only having to transaction report under MiFID since 2018, whereas the sell-side have been reporting under MiFID I since 2007. This is another example of data driven policy making by regulators that are understandably becoming more data led.

    Becoming more data driven removes the need for regulators to allocate their limited resources based on risk where the focus is primarily on larger firms, e.g. through supervisory visits and correspondence, with smaller firms being overseen using event based supervision or thematic reviews. Clever use of the data they receive using data analytics tools allows more routine and closer scrutiny of potentially all activity by authorised firms covered by the data. They will no longer be constrained to reviewing samples of activity, the computing power now available allows all the data to be subjected to scrutiny.

    The prevention of market abuse within the asset management sector was also one of the AMF’s thematic supervisory priorities for 2021. Whilst prevention is better than cure, we know that European regulators are also using transaction reports submitted by buy-side and sell-side firms alike to monitor insider dealing and market manipulation as well as to look for market abnormalities.

    However, there has long been a gap in the surveillance net when it comes to Alternative Investment Fund Managers and UCITS management companies that provide MiFID services to third parties. ESMA is therefore taking further action and proposing that these firms will start to transaction report under MiFID for the first time as a result of their review last year.

    ESMA is also proposing to introduce a MiFID ‘client categorisation flag’ which is an example of where regulators will use transaction reports to not just monitor ‘markets’ but to also monitor ‘investment firms’ specifically. The MiFID client categorisation flag will allow European regulators to assess on a large scale and, in an automated way, whether unsuitable or risky products are being sold to retail clients.

    The FCA, a data-led regulator

    Jessica Rusu, the FCA’s Chief Data, Information & Intelligence Officer, stated at the FCA’s RegTech Forum on 10 February 2022 that a data driven industry needs a data-led regulator. The FCA is prioritising the usage of data science, digital technologies and intelligence capabilities to keep pace with changes in financial services.

    Their Data, Technology and Innovation division is looking to build a digital revolution through data science projects and building a Digital Unified Intelligence Environment to reassess how FCA collects and analyses data. The recruitment of data scientists is at the forefront of the FCA’s data strategy and will allow the regulator to be more innovative and flexible in the way it reacts to changes in the industry.

    CSSF on MiFID II data quality

    The Commission de Surveillance du Secteur Financier (CSSF), the Luxembourg regulator, recently issued a press release regarding the poor quality of transaction reports it receives under MiFIR. The CSSF’s continued focus on data quality has identified a number of errors repeatedly being made by firms. However, the regulator acknowledges that their findings will not represent the universe of issues firms are facing nor potentially the most egregious.

    The Luxembourg regulator emphasised that high quality transaction reports are essential if they are to detect potential market abuse. Furthermore, they stated that poor data quality can trigger false positives and may constitute a serious breach, particularly if reporting errors lead to the concealment of potential market abuse cases. The CSSF is, therefore, recalling Article 47 which determines the sanctions, measures and penalties that may be imposed against investment firms for misreporting under Article 26 of MiFIR.

    Essentially, the honeymoon period is over for firms as it’s now over four years since MiFID II went live. So, just as we demand and want accurate data in our everyday lives, regulators need and expect better quality data from investment firms and trading venues.

    It wouldn’t be surprising if we start to see some MiFID II enforcement activity over the next 12 months in relation to transaction reporting failures, particularly in Europe, where ESMA has been encouraging NCAs to be more proactive with their enforcement powers.

    • Kaizen Reporting can help firms not only detect quality issues in their regulatory reporting, but also help them understand the reporting obligations and corrective measures.
    • For a conversation with Simon or one of our regulatory specialists, please contact us.
  • Shareholding Disclosure: What’s the issue with Issuer Requests?

    Shareholding Disclosure: What’s the issue with Issuer Requests?

    Issuer Requests can be a nuisance for those of us working in shareholding disclosures.  Large financial institutions can receive more than 50 of these notices a week.  At least this was my experience when I was responsible for shareholding disclosure monitoring and reporting at UBS and Morgan Stanley.

    Earlier this month, the FSA of the Isle of Man issued a consultation paper on sanctions for non-compliance with the Beneficial Ownership Act.  Although the Isle of Man has no legal requirements for investors to disclose substantial shareholdings (in Isle of Man incorporated companies), the FSA do require compliance with what is referred to more broadly as an “Issuer Request”.

    What is an Issuer Request?

    In some jurisdictions, a legal obligation exists for an ultimate beneficial owner to provide details of their shareholdings (and on occasions including details of ‘other’ interested parties). This request can be made in the form of a letter by the Issuer itself or an investor relations representative.  The aim of these requests is to provide the issuer with transparency of their shareholders on request, without having crossed a particular threshold. 

    What is challenging about them?

    The calculation basis for an Issuer Request can be entirely different to that of a substantial shareholding (also referred to as beneficial ownership, major shareholding, or long) disclosure.  In many jurisdictions there is little to no direction on exactly which financial instruments are included, what type of holdings are included, whether netting instruments is allowed and if the percentage is based on a notional number or votes held etc. 

    There is also the serious risk of reporting sensitive or client confidential information where there is no obligation to respond; several investor relations companies send out requests for information where there is no legal requirement.  If you are including positions held by your clients in any external disclosure, it is critical that you know if you are legally required to provide the information, otherwise you could be breaching contractual agreements.

    Where are the most frequent requests from?

    The most prevalent requests are the UK Section 793 Companies Act and Australian Section 672 Corporations Act notices.  In addition to volumes, many internally-built disclosures systems do not include the functionality to automate a response to these notices.  

    What is the Isle of Man FSA proposing?

    The Isle of Man FSA intends to broaden the scope of contraventions and offences for which a civil penalty can be considered (Draft Beneficial Ownership (Civil Penalties) Regulations 2022), including those where currently only criminal sanctions are available. 

    Within their consultation paper the FSA note that the topic of beneficial ownership is attracting increasing scrutiny from international parties.  It is expected that we will see more jurisdictions increasing disclosure obligations and the sanctions imposed, as this focus increases.   Aosphere (the leading providers of shareholding disclosure rules and used as part of the Kaizen Shareholding Disclosure Service) noted that in a 12 month period last year, 15 jurisdictions published 68 sanctions, not including all those private fines that are administered.

    Take the pain away from Issuer Requests

    Our regulatory subject matter experts can provide a suggested calculation methodology addressing all the grey areas highlighted above which is then teamed with our simple-to-use automated shareholding disclosure interface. 

    All you need to do is select the legal obligation on the platform and provide the issuer’s identifier and hey presto! just like magic, you have a response created for you. 

    Further features:

    • We can upload your own preferred template response letter or provide connections to investor relations portals.
    • Select an investor relations company from the platform’s drop down which includes their details into the response, reducing that manual effort and reducing time spent on these requests to a nominal amount, giving you confidence in the response itself and increasing efficiency.
    • Built in functionality that only allows responses to permitted requests to be created.  This will remove the risk of responding to requests where no legal requirement exists, eliminating the risk of confidential client information being incorrectly disclosed.
    • Our flexible rules configuration engine allows your own legal or in-house interpretation of the calculation methodology.

     

    Because we designed the system from our own in house experiences, we know the importance of tailoring the configuration of the rules to your requirements.  This is what makes our system work so well for our clients.

     

     

     

    • If you would like to hear more or have a demonstration of this feature, please get in touch.
    • Additionally, if you would like more information on the consultation mentioned above, please contact us (feedback has been requested by 28 February 2022).
  • SEC proposes significant amendments to beneficial ownership reporting

    SEC proposes significant amendments to beneficial ownership reporting

    The US Securities and Exchange Commission (SEC) has proposed significant changes to beneficial ownership reporting (Schedule 13D & 13G reporting).  These shareholding disclosure rules have not changed since the 1970s so the proposals are long overdue and something to be welcomed.

    What’s the background?

    Looking back, there may have been hints that the SEC was looking to review the 13d and 13g reporting requirements. In March 2021, the non-profit organisation ‘Americans for Financial Reform’ wrote to Allison Herren Lee, the acting chair of the SEC, urging for change to one of the US regimes, 13F. US reporting has long faced criticism for its lengthy deadlines and simplistic view on the inclusion of certain financial instruments. This has resulted in reports that are of little value to issuers or the market at large – and seemingly the SEC themselves: in their Review of the SEC’s Section 13(f)’s Reporting Requirements in August 2021, the regulator confessed that “…no SEC division or office conducts any regular or systematic review of the data filed on Form 13F”.

    They are now ready to address similar issues with Schedule 13D and 13G reporting, stating that changes in financial markets and technology now require them to reassess and modernise their reporting.

    What are the new SEC reporting requirements?

    The SEC has proposed expanding Schedule 13D & 13G reporting to include certain cash-settled derivatives.  This will bring the US more in line with European and some Asia-based regimes, which have included cash-settled derivatives for a number of years.  Holders of cash-settled derivatives, with the exception of an equity swap, will be deemed to be the beneficial owner of the underlying equity securities.

    The new Schedue 13G reporting requirements (ie. qualified institutional investors and exempt investors), would shorten the initial filing deadline from 45 days after year-end to five business days after the end of the month in which the investor beneficially owns more than five per cent.  In addition, the new SEC 13D reporting requirements would shorten the initial filing deadline from 10 days to five days for 13D reporting and any amendments to the holding would need to be filed within one business day.

    The proposals include beneficial owners reporting using a structured, machine-readable data language, which the SEC believes will make compiling and analysing the information disclosed on the 13D and 13G reports easier.

    The consultation period is open for 60 days following publication of the proposed change on the SEC’s website or 30 days following publication of the proposing release in the Federal Register, whichever period is longer.

    What is Schedule 13D and Schedule 13G reporting?

    This is a shareholding disclosure obligation that requires that an investor who beneficially owns more than five per cent of a covered class of equity securities to publicly file either a 13D or a 13G form.

    13D is intended to provide transparency to the market about shareholders and their intentions for taking a significant stake in an issuer.  A 13G disclosure is a shorter version of the 13D and can be filed in lieu of a 13D if certain exemptions apply to the beneficial owner.

    Automated beneficial ownership reporting

    Kaizen continuously monitors and implements all changes to global shareholding disclosure including beneficial ownership rules, so that our service and technology platform are primed and ready to go with alerts and automated reports, ensuring your compliance from day one of the change.  In addition, our team of shareholding disclosure subject matter experts work with our clients to help them understand the requirements and the subsequent amendments to regulation.

  • SEC Part 43 Real Time Reporting takes the romance out of Valentine’s Day

    SEC Part 43 Real Time Reporting takes the romance out of Valentine’s Day

    Difficult as it may be to believe, many people I talk to don’t seem to appreciate the romance of regulations, the passion for data quality, or even the sexiness of standards. I know, right!

    Well naysayers, the tide is turning and the link between regulations and romance is becoming harder to dispute.

    Last week we had the CFTC issuing an advisory on online dating and the risk of being ripped off when Mr/Miss Right really isn’t very right at all.

    And never one to be knowingly outdone by its regulatory rival, today sees the SEC massacring Valentine’s Day for many with the introduction of Part 43 real-time price dissemination reporting.

    For the many technologists and reporters diligently working on a smooth go-live of the SEC’s second major milestone in their rollout of SBSR reporting, there’ll be no chance of sloping off for a romantic meal. 

    We here at Kaizen would like to wish all the SEC reporting firms a smooth and successful, if ultimately unromantic, go-live today.

    And there’s just the trivial matter of backloading every expired SBS since 2010 before the third and final instalment of the SEC rollout on April 14 to tackle now. (I’ll need to start working on my Easter puns for that one)…

  • SFTR’s ongoing settlement fails saga

    SFTR’s ongoing settlement fails saga

    ESMA has published an amendment to Q&A no.2 on “Reporting of settlement fails” but unfortunately it leaves as many outstanding questions as answers. 

    An out of the blue requirement

    Securities Financing Transaction (SFT) markets, the repo market in particular, operate on the basis of perfect settlement. At most firms, there is no feedback loop between settlement systems and SFT risk management systems to enable firms to reliably capture the fact that a transaction closing leg is failing. Therefore, many firms have lacked the technical ability to disconnect their SFTR reporting from their risk management books and records, and report fails in accordance with the regulation. This seemed an out of the blue requirement when it first appeared in the ESMA SFTR Guidelines document in January 2020 and many firms still struggle or fail to meet this requirement as it stands today.

    Industry consternation

    As a result of the consternation expressed by the industry regarding this requirement, ESMA felt the need for reiteration in the first set of SFTR Q&A published in November 2020. This month, ESMA has quietly revised this Q&A further, giving additional guidance and clarifying expectations for SFT markets outside the repo market.

    So what does it say?

    The primary expectation is that if one or both parties to the transaction have failed to report an amended maturity date/end date to reflect the failing status of the transaction, then both parties will agree a new UTI and book a new transaction to reflect the risk that ESMA perceives to be outstanding. Unfortunately, ESMA neglects to mention what a party who has correctly reported an amendment to the original transaction should do, nor what start date/value date to use on this new hypothetical transaction.

    In addition, ESMA reiterates that reporting of settlement fails of the closing leg applies to all types of SFT. ESMA also states that this applies to CCP-cleared SFTs, providing any settlement fails are attributable to individual SFTs.      

    So all in all, this Q&A update is a missed opportunity from ESMA to truly clarify exactly what its expectations are of the industry, leaving many firms still struggling to adhere to this rather onerous requirement. 

    • Read the Q&A in full on ESMA’s website.
    • For a conversation about your SFTR data quality with Jonathan or one of our regulatory specialists, please contact us.
  • Five key changes proposed for the UK EMIR Refit

    Five key changes proposed for the UK EMIR Refit

    Derivative reporting ‘rewrites’ are trending globally at present. Authorities in Europe, Asia, America and beyond have committed themselves and the firms they regulate to full-scale reviews of their reporting regimes.

    Late last year the UK’s FCA and the Bank of England (BoE) joined forces to launch the next phase of their consultation for almost all aspects of UK EMIR Reporting.  The consultation paper notably follows ESMA’s ‘EMIR Refit’ reporting guidelines 2021 and whilst the FCA/BoE is not first away from the line, a slow and steady approach may prove to be the most efficient way forward for this large array of changes. The FCA/BoE have been able to learn from the extensive (and much delayed) ESMA Refit consultation (which included UK firms at the time of consultation).  Specifically, whilst the UK consultation paper is primarily following the global trend of aligning with CPMI IOSCO’s CDE Guidance, in practise it also takes into account ESMA’s post-consultation report. In other words, it has taken the end result of its European counterpart’s process and used this as its starting point for the UK EMIR rewrite consultation.  And so, as per the children’s fable, the hare and the tortoise, it’s not always advantageous to be the first mover!

    These proposals represent significant changes for UK EMIR Reporting, many of which are welcome. Let’s look at five important areas of change to be aware of.

     

     

     

     

     
  • FCA shows flexibility on Short Selling Indicator for MiFIR transaction reporting

    FCA shows flexibility on Short Selling Indicator for MiFIR transaction reporting

    The FCA has made public its position on the Short Selling Indicator (SSI) for UK MiFIR transaction reporting. 

    Although we have been liaising with clients on this point for some time, it’s now been confirmed that where firms are aware of misreporting in relation to the SSI, they are not required to both cancel and replace those reports or notify the FCA of the misreporting via an errors and omissions notification form.  The FCA will keep this temporary measure under review.

    However, given this measure only addresses back-reporting, we would surmise that the FCA still expects firms to address erroneous reporting in their daily reporting flow until further notice.  Therefore Kaizen will continue to identify issues with the SSI that arise in our testing.

    This is an interesting development and a good example of a flexible and pragmatic approach by the FCA that will certainly be welcomed by the industry. Is this the shape of things to come from the FCA?

    Reporting obligations to EU regulators continue to apply and are unaffected by this announcement however ESMA announced it will be dropping the short-selling flag following its MiFID II Review in April last year.

  • LIBOR decommissioning brings SONIA and SMMD reporting to the fore

    LIBOR decommissioning brings SONIA and SMMD reporting to the fore

    The death knell for GBP LIBOR began to sound back in March this year with the FCA’s announcement that most of the LIBOR tenors will cease to operate by 31 December 2021. LIBOR’s legacy dating back to 1980s was deeply tarnished and irreparably damaged by the LIBOR scandal of the 2000s.

    SONIA and Sterling Money Market Daily reporting

    GBP LIBOR is being replaced by the Sterling Overnight Index Average (SONIA). SONIA is a new regulatory report-driven unsecured benchmark rate for Sterling Money Markets. Sterling Money Market Daily (SMMD) reporting is the dataset used by the Bank of England (BoE) in order to calculate the daily publication of SONIA benchmark interest rates. This reporting also plays a vital role in the BoE’s monetary and financial policy decision making. SMMD reporting aids the BoE in monitoring the economic impact of monetary policy, setting interest rates, market financing and money market surveillance. It provides much needed transparency on short-term wholesale borrowing and lending activities within the Sterling area.

    Accurate reporting is expected by regulators 

    LIBOR reporting became a painful episode for a number of UK financial institutions, with firms and traders finding themselves in the courts.  As a consequence the controls around SMMD reporting are stringent and the penalties for getting it wrong are dissuasive.  The mandatory control requirements for SMMD reporting institutions are framed by the Bank of England Money Markets Code and the FCA’s Senior Managers and Certification Regime (SMCR).

    What are the reporting requirements?

    • Periodic and comprehensive testing of the reporting firm’s data, including reference data
    • Early detection of failures and gaps in reporting flows
    • Controls to ensure both secured and unsecured borrowing and lending activities are captured
    • Governance arrangements to ensure compliance with industry standards and market best practice with a minimum of annual attestation by both a senior compliance officer and a relevant business area representative.

    “Each reporting institution’s internal controls for SMMD Reporting should include comprehensive testing of automated processes and documented change control processes, procedures to detect failure to capture a segment of eligible transactions and failure to exclude non-eligible transactions.”

     – Bank of England, SMMD Reporting Instructions Version 4.6, December 2020

    The global view

    The UK is not alone in phasing out the LIBOR benchmark.  The Euro area is also resorting to new regulatory report-driven overnight unsecured benchmark interest rates.  The Euro Short-Term rate (€STR) has been published since October 2019, driven by transactions reported under the Money Markets Statistical Reporting (MMSR) regulation.  €STR will be officially adopted on 3 January 2022 as the replacement of Euro money markets benchmark superseding the Euro Overnight Index Average (EONIA) and the Euro Interbank Offered Rate (EURIBOR).  Indeed, across the globe new alternative interest rates are replacing LIBOR such as the Office of Financial Research report based Secured Overnight Financing Rate (SOFR) in the US, and the Tokyo Overnight Average Rate (TONA) in Japan.

    The right controls

    What controls does your firm have in place for SMMD and MMSR reporting?  Are you satisfied that your firm meets the requirements listed above? Kaizen can provide quality assurance through regulatory testing of these regimes though our multi-award winning ReportShield™ services, giving you confidence that you are meeting your regulatory obligations. 

    • For a conversation with Faizal or one of our regulatory specialists about putting the right controls in place for SMMD or MMSR reporting, please contact us.
  • SEC Rule 10c-1 Securities Lending Market Reporting Proposals  – a blessing or a curse?

    SEC Rule 10c-1 Securities Lending Market Reporting Proposals – a blessing or a curse?

    New US Securities and Exchange Commission (SEC) proposals for a securities lending trade reporting regime have the potential to turn global securities financing transaction (SFT) reporting on its head.  The proposals introduce near real-time transparency to SFT markets, while significantly reducing the operational burden on market participants to report their trades.  On the flip side, get it wrong and we could see a mass exodus from the US securities lending market, a significant reduction in liquidity and higher financing costs affecting wholesale capital markets in the United States.  

    The SEC shows its hand

    It was likely to be only a matter of time under President Biden’s administration before US regulatory attention turned to SFT data collection under the 2015 Financial Stability Board (FSB) mandate.  To date, the only element of Standards and Processes for Global Securities Financing Data Collection and Aggregation (FSB 2015) implemented in the US was the Office of Financial Research requirement.  This was introduced in October 2019 for central clearing houses (DTCC in particular) to report details of centrally cleared repo transactions to the Federal Reserve Bank of New York on a business day+1 basis – a significant but small subset of the overall US SFT market.  Amidst much more comprehensive reporting requirements in Europe and Japan, the SEC has chosen now to show its hand.

    What’s being proposed?

    In summary, this proposal is in a moderately late stage of development and seems highly likely to come to fruition.  Plans are afoot for any lenders, oft represented by agent lenders or broker dealers to report basic details (12 fields) in relation to their securities lending transactions and any modifications to a Registered National Securities Association (RNSA) – almost certainly the Financial Industry Regulatory Authority (FINRA), within 15 minutes of execution. Lenders are also required to report details of the total amount of securities available to lend and the total amount of securities on loan by end of day each business day.

    More transformational are plans for RNSAs to publish details of securities loans, potentially on an intraday basis (ticker tape style).  In particular, proposals include publishing the legal name of the issuer of the securities to be borrowed, the ticker symbol of those securities, time and date of the loan, name of the platform or venue (if applicable), amount of securities loaned, rates, fees, charges and rebates for the loan (as applicable), type of collateral provided for the loan, percentage collateralisation of the value of the loaned securities, termination date of the loan (if applicable) and borrower type (e.g. broker, dealer, bank, customer, clearing agency, custodian).  In addition, aggregated information on securities on loan or available to loan would also be published on a timely basis, likely the following business day.

    Transformative

    The reporting obligation is intended to be far more timely (within 15 minutes of execution or a modification being made) but with far fewer fields (12 fields for a transaction report) than existing regimes such as SFTR in Europe.  If SEC rule 10c-1 reporting of securities lending transactions works (with flaws ironed out and without unintended consequences), then it is likely to prove revolutionary and could prove quite transformative of regulatory regimes across the globe.  It puts end investors, transparency and market efficiency first, is operationally (comparatively) light/low cost, while meeting both the micro surveillance as well as macro systemic aims of SFT reporting regimes.

    The pros of this proposal are:

    • The intention to eliminate pricing and security availability (for loan) information asymmetry between broker dealers, agent lenders, beneficial owners, borrowers and end investors in the securities lending market.  The primary focus is in providing market transparency and creating a level playing field, enabling all market participants to understand market conditions and ensure best execution
    • Single-sided reporting is proposed by lenders only (who are seen as closest to the data – reducing the regulatory burden)
    • The SEC have stated that the reporting would be a means to achieve in-depth monitoring of lending activity and surveillance of securities markets, enable the identification of the build-up of risk by market participants, provide colour on broker-dealer strategies to source securities for customer lending and cover for settlement fails.  Furthermore, the SEC expect to build a greater understanding of investor behaviour in the securities lending market and the broader securities market more generally
    • Reports require just 12 simple, precise fields to populate at the trade level.  Even fewer fields are required for end of day position and availability for loan reporting.

    Challenges:

    • Beneficial owners and securities lenders can be a shy bunch.  A sizeable proportion of beneficial owners are established or domiciled outside the US and subsequently may take fright at the level of transparency on offer and withdraw from the market entirely, lend in the UK, EU or a jurisdiction not subject to such transparency or simply execute equivalent, unpublished repo transactions instead
    • The domestic US securities lending market may in part or on a larger scale migrate to the repo market, where economically equivalent transactions can be executed.  A large proportion of these repo transactions, under current rules, would not be subject to any reporting requirements or transparency
    • 15 minute reporting, presumably proposed because the majority of TRACE securities trade reports to FINRA are required within 15 minutes, is likely to prove both challenging and optimistic in the comparatively manual and less automated securities lending market.

    Next steps

    This regulation is set to develop very quickly from here, with the SEC inviting comments and answers to the 97 questions posed in the consultation by 7 January 2022 (30 days after its publication).  They have stated that a decision will be made concerning the collection of information between 30 and 60 days after publication of the consultation.  This regulation looks set to be one, if not the biggest focus of SFT market attention in 2022, certainly in the US, if not throughout the world. It may well go ahead in close to its current form but we suspect that for the reporting requirement to be truly successful (and not result in damaging unintended consequences) then it will have to be extended to the repo market.

    • To read the SEC’s press release and the full proposal, please visit the SEC’s website.
    • For a conversation with Jonathan or one of our regulatory specialists about the above topics, please contact us.
  • ESMA emissions report provides clarity on EMIR reporting fields

    ESMA emissions report provides clarity on EMIR reporting fields

    With COP26 just last month and ESG at the top of the business agenda, ESMA’s recently released Preliminary Report on Emission Allowances and derivatives thereof, is timely.  The report discusses the EU’s objective of reducing net greenhouse gas emissions after the European Commission (EC) asked ESMA to analyse the trading of emission allowances (EUA). 

    The document highlights some useful clarifications relating to EMIR reporting:

    • Emission allowances are considered a financial instrument and therefore should be reported under EMIR
    • Product Identification (2.6) – this field must contain an ISIN to identify the derivative
    • Commodity Details (2.66) – This field should be populated with ‘EM’ for emissions – this is called out as crucial for emission identification, notably if the derivative is not highlighted as such within the aforementioned Product Identification field.

    Looking ahead – EMIR Refit

    ESMA will use EMIR Refit as an opportunity to increase the level of detail reported for such emission trades, including:

    ‘More granular classification of the commodity and emission allowances derivatives, including a breakdown between Certified Emission Reductions (CERs), Emission Reduction Units (ERUs), European Union Allowances (EUAs) and Aviation European Union Allowances (AEUAs).’

    Coupled with other reporting requirements, such as the use of ISINs, enhanced lifecycle events, and transparent business activities of counterparties, which should increase ESMA’s market view into EUA.

    Next steps

    ESMA plans to release its report on the trading of emission allowances next year, which is likely to lead to further clarifications for EMIR reporting and useful analysis regarding the important topic of net greenhouse gas emissions.

     
  • FCA proposes ending transaction reporting of SFTs under UK MiFIR

    FCA proposes ending transaction reporting of SFTs under UK MiFIR

    The FCA recently published a quarterly consultation paper (No 34) in which they propose to completely exclude securities financing transactions (SFTs) from any MiFIR transaction reporting obligations under RTS 22. In particular, at present, while SFTs facing the Bank of England or a European System of Central Banks (ESCB) member as ‘Other counterparty’, are excluded from SFTR reporting, they are required to be transaction reported under UK MiFIR.  The proposal is for the requirement to report these transactions under UK MiFIR to cease, with effect from 31 March 2022.

    The industry will be very grateful for this very sensible change.  At present the requirement to provide MiFIR reports on central bank SFT transactions is very much a case of trying to push a round peg into a square hole. The MiFIR taxonomy is wholly inappropriate for reporting SFTs, with very little guidance available.  The resultant MiFIR reports appear sufficiently meaningless as to add no apparent value to regulators.  This proposed change comes alongside the FCA’s earlier removal of the obligation to report SFTs executed by non-financial counterparties. The additional move to eliminate all MiFIR SFT reporting demonstrates further pragmatism in keeping UK SFTR equivalent to the EU regime while listening to the industry’s operational concerns and taking a more pragmatic approach.

    Comments are to be sent to FCA by 17 January 2022.  

    • To read the consultation paper, please visit the FCA’s website.
    • For a conversation with Jonathan or one of our regulatory specialists about the above topics, please contact us.
  • FCA uses MiFIR transaction reports to bring enforcement action

    FCA uses MiFIR transaction reports to bring enforcement action

    The recent FCA fine of an interdealer broker is another good example of how the regulator is repeatedly using transaction reporting data to investigate market abuse and financial crime. 

    In the final notice, released on 12 November, the FCA referenced that their investigation and conclusions in respect of the purported trading were based on a range of information including, in part, analysis of transaction reporting data received from six broking firms.

    The interdealer broker was fined £642,400, of which £407,273 was disgorgement, for having:

    • inadequate systems and controls to identify and mitigate the risk of being used to facilitate fraudulent trading and money laundering; and
    • not exercising due skill, care and diligence in applying its AML policies and procedures and in failing to properly assess, monitor and mitigate the risk of it being used to facilitate financial crime

    The interdealer broker ignored or failed to notice a series of red flags in relation to a trade in a stock it executed on behalf of a broker client.  The circumstances of the on-boarding and trading relating to that broker client ought to have prompted interdealer broker to consider the serious financial crime risks the trade posed, particularly given it was executed at nearly twice the prevailing market value of the stock.

    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 a circular pattern of transactions that included extremely large-scale purported OTC equity trading, back-to-back securities lending arrangements and forward transactions.

    The interdealer broker stated that it took a risk-based approach and deemed that it was not necessary to carry out any pre-trade or post-trade surveillance for a number of reasons, including that all transaction reporting was to be provided by regulated firms. 

    As well as emphasising the importance of the transaction reporting regime, this final notice reiterates the need for firms to have effective systems and controls to monitor their own trading and payment activity, regardless of whether MiFIR transaction reports have been submitted to the regulator.

    To read the final notice visit the FCA website.

    • For a completely independent assessment of the accuracy and completeness of your Transaction Reporting, please contact us.
  • Unpacking the SEC Reporting FAQ

    Unpacking the SEC Reporting FAQ

    SEC Security-Based Swaps Reporting (SBSR) goes live today and to mark it, what better than a review of the FAQ guidance recently released by the SEC.  In this blog, we’ll attempt to unpack some of it and ask whether it’s helpful for firms.

    Please click on the headings below to view each Q&A (in bold italics) and our analysis of each. 

  • Top five changes in the final CFTC reporting Technical Specification

    Top five changes in the final CFTC reporting Technical Specification

    Last month the CFTC published what they and the industry are hoping is the final version of the Technical Specification for Parts 43 & 45 reporting under the ReWrite of the CFTC swap data reporting rules.  Unless there is a delay (as is much rumoured and debated) this means it’s now only seven months until the May 2022 compliance date.  Factor in Thanksgiving and the holiday season and that’s really not a long time assuming this really is the final version.

    At Kaizen HQ we’ve been analysing the impact and here are the five most significant changes in this latest version.

     

    1:  Multiple validation changes

    I’ll dispense with the obvious one first and get the low hanging fruit out of the way.  There are many, many changes throughout this version of the technical spec.  See the red-line version and it’s littered with changes.  These range from non-substantive wording changes, to revised definitions, to tweaks to the field-by-field validations.

    It would be impossible to cover them all here so instead I’ll just point out the obvious – the sheer number of changes is one of the main aspects for firms to deal with.

     

    2:  Short-form exit messages

    The final tech spec has wisely concurred with a suggestion the SDRs and the industry were pushing for and added language to support so called short-form exit messages:

    Nothing in this Technical Specification should be read to prohibit an SDR from limiting the number of data elements required to be submitted, to a subset of part 43 or 45 data elements, for Action Type TERM, PRTO, and EROR.  Submission of all parts 43 and 45 data elements is mandatory for all other Action Types.

    This is good progress because it simply makes sense that firms don’t need to worry about ensuring every single field is correct and contains an up-to-date value when they are trying to terminate a position or remove a position that was submitted in error.

    I’m reporting Swap Creation data or Swap Continuation data on an open trade so I need to ensure the data is accurate and complete.  Absolutely.

    I’m terminating a position that no longer exists or worst case removing something that should never have been reported and I need to ensure every single field is accurate and complete.  Not so much.

    The action to remove or terminate is far more important here than a full representation of the trade so limiting the fields to a short-form subset that identifies the firms involved, submitter and the trade identifiers is a common sense practical approach.

     

    3:  Event Timestamp for Collateral Valuation dates

    Again the Commission deserves credit for closing a gap that the industry was pushing for.  In this case there is a requirement to submit Collateral Valuations (Action Type MARU – Margin Update) but the industry was pointing out there was no method to distinguish between submitting a MARU for the current date versus a correction of an older MARU for a previous reporting date.

    The CFTC revised the tech spec to facilitate this but instead of adding a new specific ‘valuation date’ field they commandeered the definition of existing field Event Timestamp, by adding:

    In the case of collateral update (Action type = ‘MARU’), this is the date for which the information contained in the report is provided. Time portion should be reported as “00:00:00”. 

    Whilst I applaud the CFTC for addressing the gap, their choice of mechanism feels a bit of a fudge.  And given the global momentum towards harmonised standards it might have been better addressed by adopting a CDE-based field better aligned to this purpose.

    Apart from global harmonisation alignment there are two main problems with this solution:

    1. Collateral Valuation Date is not an Event as per the CFTC definition of Event.
    2. The field is a Timestamp and not a Date so the guidance doubles down on the messy approach by suggesting firms add 00:00:00 as the timestamp part.

    At Kaizen we often advise firms not to use default timestamps as it’s just not good practice and is often not compliant.  So it’s pretty frustrating to see another regulator recommending the use of a dummy timestamp to circumvent a shortcoming in the way the regulator is using the field.

     

    4:  Upgrading Event Type

    As well as aligning some of the Event Type codes to better align with CDE (TRDE deposed by TRAD for example), the CFTC has thrown in two new Event Types:

    CORP = Corporate event

    UPDT = Upgrade

    CORP is alas more geared towards a Corporate Action affecting an equity instrument rather than a company soiree with free drinks, snacks and a bit of a skive away from your desk.

    UPDT is therefore more interesting – especially as it unexpectedly spells Upgrade.

    Upgrade: An upgrade of an outstanding transaction performed in order to ensure its conformity with the amended reporting requirements.

    So this event type allows me to UPDT my pre-ReWrite reported swap transaction in order to Upgrade it to the latest data standards.  OK that now makes a bit more sense and we’ve seen similar proposals in other jurisdictions.

    But other jurisdictions such as ESMA for EMIR have gone further in terms of stating the expectations around how such an UPDT to the new standards should be used and crucially the expected timeline.  Firms have 180 days from the implementation of the EMIR REFIT in Europe to bring any open transactions/positions into line with the new standards.

    Without such explicit guidance from the CFTC, the reporting firms will need to discuss and decide upon the best way to tackle bringing all open swaps into line with the new standards.  Big bang and update everything on day one versus track them and update those not updated via a natural lifecycle event submission over time.  Although when you factor in the complexities arising from the CFTC rules around moving from USI to UTI, things start to get complicated pretty quickly.  I suspect the SDRs are bracing themselves for really high volumes with lots of firms submitting an UPDT for everything on day 1 in order to just get it done.

     

    5:  Removal of the ‘no translation’ language

    The following clause in section 1.2.1 has been struck out:

    No translations or mappings are permitted, i.e., ‘Yes’ or ‘No’ should not be mapped to ‘True’ or ‘False’.

    The regulators intentions here seem fairly clear and would point towards what has often been described as the ‘dumb trade repository’ model.  The Trade Repository (TR) function is to accept data, store it and make it available to the regulators.  The TR should not therefore map, convert, derive, enrich or invoke any other kinds of data alchemy that obfuscates the of the data the firms submitted versus the data the regulators then see.

    This no translation language has proved controversial as it had been interpreted in some quarters as meaning the SDRs should not accept FpML submissions.  Given that the ISO 20022 message schema is still a long way off being ready for CFTC reporting then this led to a debate around whether the firms that currently use FpML would need to migrate to CSV as a temporary solution until such a time as ISO messaging was implemented by the CFTC.

    This in turn led to louder calls for a delay to the May 2022 compliance date for the CFTC ReWrite.  Especially amongst the bigger Wall Street banks that tended historically to be the main users of FpML.  The CFTC striking this language out of the latest Technical Specification is therefore likely to be welcomed by some firms.  However the no mapping and no transformation concept still exists in the CFTC reporting legal texts so it will be interesting to see whether any more guidance or even a No Action Relief letter follows to further clarify this one.

     

    Bonus item: final thoughts

    This is the final version of the Part 43 and 45 Technical Specification.  Or is it?  I have no doubt that the CFTC intends and very much hopes that this is the final draft. But in my experience these things often need tweaked and revised when real world experience collides with theoretical rules.

    The CFTC deserves credit for the thoughtful, collaborative and engaging approach it has taken in moving from principles-based reporting regulations to this far more prescriptive approach. It has moved slowly, consulted with its peers and the industry, and communicated well throughout.  So I am not trying to be critical here when I say that the CFTC is learning one of the problems with prescribing this level of detail.  The pesky questions and problems that arise!

    You sit in meeting rooms and draft, redraft and fine tune the wording until it’s as clear as it can be.  Multiple teams, committees and stakeholders all agree it’s as crystal clear as it’s possible to make it.  You then release it into the big bad world and it turns out everyone’s a critic.  There are questions aplenty and worse still some of them have a point.  It’s unclear or in some cases plain wrong.

    No disrespect whatsoever to the Commission but they are learning the hard way that this prescriptive stuff is hard.  This stuff is hard to do and takes a lot of time and effort to get right. Kudos to the CFTC for the collaborative approach and along with ISDA, the SDRs and the reporting firms we’ll get there.  Regardless of whether this version is final or not.  Now, about that delay…

     

    • For a conversation with Alan or one of our regulatory specialists about the above topics, please contact us.

     

     

     

     

  • ESMA updates MiFIR Transaction Reporting validation rules

    ESMA updates MiFIR Transaction Reporting validation rules

    In case you did not catch it, ESMA recently published updated 2022 MiFIR validation rules.  The changes are applicable from 31 May 2022.

    It is unlikely that any of these changes will impact Kaizen clients as these validations are already covered in our tests.  Firms should expect the additional validations to be implemented by their Approved Reporting Mechanisms and Competent Authorities going forward.

    Although the additional validations and clarifications make sense, this was a missed opportunity as a lot more could have been done and additional strengthening and tightening of the validation rules would have been helpful to firms.

    Here are the changes:

    • New validations have been introduced to check that the Buyer and Seller date of birth (fields 11 and 15), Buy and Sell decision maker date of birth (fields 20 and 24) should not be later than trading date.
    • Since sending an order to a trading venue does not constitute transmission, a new validation has been introduced to check that if the transmission of order indicator (field 25) is ‘true’, then the venue (field 36) must either be XOFF or XXXX.
    • As the country of branch membership (field 37) should only be populated for the market side of a transaction executed on a trading venue or on an organised trading platform outside of the Union, a validation has been introduced to check that this country of branch membership (field 37) is blank where the venue (field 36) is populated with ‘XXXX’ or ‘XOFF’ or a MIC pertaining to a Systematic Internaliser.
    • In addition, rule ID 117 relates to field 37 (Country of the branch membership) and previously included clarification that this field should not be populated for transactions executed on Systematic Internalisers (SIs). This clarification has now been removed given that this field is not applicable to SI executions.
    • Rule IDs 027, 043, 056 and 072 were updated to include clarification that the ‘EntityStatus’ shall be Active on the trading date in relation to Buyer & Seller ID codes and Buyer & Seller Decision Maker codes.
    • Rule ID 220 was updated in relation to Error Code CON-412 to clarify that the MIC also needs to be valid in the reference data on transaction date.
    • Rule ID 228 relates to field 57 (Investment decision within firm) and was updated to include clarification for cases when Buyer Decision Maker (Field 12) and Seller Decision Maker (Field 21) are left blank.

    • Rule ID 270 relates to field 36 (Venue): Clarification was provided that if ‘XXXX’ is populated in field 36, the full instrument description must be provided and the ISIN reported must not be present in reference data for the relevant trade date.

    • All other changes related to the addition of a number of CFI codes to a variety of validation rules and data fields, namely rule IDs:

    • 111 and 262 which relate to field 35 (Net amount);
    • 140 and 250 which relate to field 45 (Notional currency 2);
    • 154 and 264 which relate to field 48 (Underlying index name); and
    • 166 which relates to field 53 (Option exercise style).

    • For a conversation with Simon about the updated rules or to find out more about the quality of your MiFIR transaction reporting, please contact us.
  • Trade Reporting vs Transaction Reporting

    Trade Reporting vs Transaction Reporting

    Regulatory trade and transaction reporting is a strange beast.  I think most people fall into it by accident rather than choosing it (including myself), but people still get confused with the terminology and understandably so, as it does get complex.  Inconsistent wording across regulations doesn’t help, as they interchange between using the term ‘trade’ and the term ‘transaction’ and if you are lucky, a bit of ‘position’, even when it is the same regulator writing the rules. If you are sitting comfortably then I’ll begin (to confuse you)…

    MiFIR trade reporting

    Let’s start with MiFIR trade reporting (RTS 1 and 2). This is real-time trade transparency reporting, made public at the point of execution via an Approved Publication Arrangement (APA). Simple enough but MiFIR also has transaction reporting (RTS 22).  This is T+1 reporting of all transactions, either directly to the regulator or via an Approved Reporting Mechanism (ARM), to allow the European regulators to monitor market abuse.  Similar by name but very different in nature…

    Not to forget MiFIR also has its Commodities Derivatives Reporting (RTS 21) but that’s at position level.  Hold on…

    EMIR trade reporting

    EMIR has trade reporting where you report your derivative transactions to a Trade Repository (TR). That is of course unless you take up the option under EMIR to report some of your trades at position level instead! Keep up!

    Even though EMIR is more similar to SFTR transaction reporting than MiFIR trade reporting, both EMIR and SFTR mandate reporting to a Trade Repository and not a Transaction Repository. Yep, I’m lost…

    The good news is that the sensible people in the Asia Pacific region have tried to keep it consistent and retain the model of transaction reporting. HKMA, MAS & ASIC all use transaction reporting terminology.  Phew…

    Dodd-Frank Act price reporting

    The US Dodd-Frank Act (DFA) Part 43 price reporting, similar to MiFIR trade reporting, reports through a Swap Data Repository (SDR) that accepts data relating to (you guessed it) swap transactions, not a standalone publication tool like an APA.  Part 45 transaction reporting or swap reporting, also uses trade reporting terminology throughout.  Full circle, for CFTC commodities position reporting, all the terms trade, transaction and position are used.  HELP!!

    • Clear as mud?  Our team of ex-regulators and regulatory reporting specialists love talking about this stuff and can guide you though any reporting challenge. For a conversation about your trades, I mean transactions, across any of the global reporting regimes, please contact us.
  • CFTC fines and selling the reporting dream

    CFTC fines and selling the reporting dream

    Anyone that’s worked with me or read more than a couple of my ramblings will know that I don’t do sales.

    I’m not being boastful or even modest. It’s just not my forte so I tend to give anything ‘salesy’ a wide berth. I mean no disrespect to the world of selling or the talented people that work in sales. I’m just so bad at it and so far out of my comfort zone that I’d probably give the product away for free rather than get into discussing the dreaded commercials.

    Breaking my rule

    The third quarter of 2021 or more specifically the last four days of September saw a flurry of enforcement actions and fines from the CFTC, that after some careful consideration are leading to me breaking my nothing-salesy rule. Not because I’ve had a change of heart or want to move in a different direction. But the themes within the CFTC enforcement actions are so closely aligned to what we do here at Kaizen Reporting it’s almost impossible to not go there.

    So kindly bear with me whilst I set out the stall.

    Taking back controls

    I always advise clients of the importance of devoting a significant effort to building controls into their reporting systems as well as layering additional controls onto the reporting systems and the reporting data generated. Over the last few years I’ve seen an interesting trend where many firms are moving those controls further up the stack towards the trading systems rather than downstream in the data lake or reporting hub. The ethos being that it’s better to flag the errors at source rather than further downstream where the remediation workflow can be more elaborate, involve multiple systems and take longer.

    I stand by this advice and maintain that it’s not only best practice but it’s absolutely crucial to help detect and prevent errors within your reporting.

    Marking your own homework

    However there is a key limitation which means that these controls, no matter how well designed and implemented are not enough. Simply put, at some stage you inevitably end up marking your own homework. Whether the controls were developed at the same time the reporting system being built or were added later, the vast majority of the time it was the same teams, relying on the same documentation and same interpretations that ended up owning both the reporting and the controls.

    [First salesy spoiler alert]. Independent controls and that unbiased second opinion are key to detecting the issues that your controls and vigilance missed.

    I could labour the point but there’s no need as it’s really that simple.

    [Second salesy spoiler alert]. At Kaizen we offer the best in class data Accuracy Testing (checking the integrity of the reported data), Reconciliations (testing the completeness and accuracy of the reported data versus your source systems) and Reference Data Testing (testing the accuracy of the reference data that your reporting systems utilise to do the reporting). We offer these because it’s our experience of working with many, many clients over many different regulatory regimes that this is what is needed to fully assess the quality of the reporting data.

    We’ve seen it many times over the years in various regulations where an upstream reference data change causes an unforeseen reporting issue downstream. Your own controls might catch such instances, but they also might not. A static data change results in a different value flowing downstream to the reporting system. The value goes out the door and is reported because it’s a valid value, but it’s the wrong valid value.

    CFTC enforcement actions

    Looking at the themes in the recent CFTC enforcement actions will hopefully shine a light on why I’m breaking my embargo.

    • Failure to report LEIs or report the correct LEIs

    Accuracy Testing, Reference Data Testing and Reconciliations.

    • Failure to report swap valuation data or accurate valuations to an SDR

    Accuracy Testing and Reconciliations.

    • Reporting inaccurate swap data to an SDR.

    Accuracy Testing, Reference Data Testing and Reconciliations.

     

    As a firm that spends its entire energies and focus on the world of trade and transaction reporting we know more than most just how challenging these ever changing regulations can be. [Third and final salesy spoiler alert]. That’s why Kaizen Reporting was founded – to help firms with exactly these challenges. 

    The recent CFTC enforcement actions prove that the US regulator is paying close attention and expects the swap data to be reported accurately. With better and more prescriptive data standards coming in the form of the CFTC ReWrite we can only expect their tolerance of reporting issues to decline even further. The CFTC have spent years and a lot of effort on the ReWrite and they are going to expect high quality data reported from the start.

    • For a conversation with Alan or one of our regulatory specialists about the above topics, please contact us.
  • UK SFTR – Desynchronised Harmony

    UK SFTR – Desynchronised Harmony

    UK announces SFTR validation rule changes

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

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

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

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

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

    *Please note this date was updated from 14 April.

    • If you have concerns about your firm’s SFTR data quality and regulatory compliance, working through the changes to the validation rules or undergoing trade repository migrations, we can help.  Please contact us for a conversation with Jonathan or one of our regulatory specialists to discuss your challenges.  
  • ESMA admits MiFID II transparency still not achieved in derivatives

    ESMA admits MiFID II transparency still not achieved in derivatives

    There were some interesting comments at the recent FIA International Derivatives Expo (IDX) in London, where Natasha Cazenave, ESMA’s new executive director, discussed the EU regulator’s priorities in the derivatives markets and how its MiFID II review reports showed that it had met its “objectives of establishing sounder, more transparent and more integrated EU capital markets.”

    Cazenave summarised by recommending “less complexity, more effectiveness”, which is music to the ears of participants, investment firms and the regulatory infrastructure alike but surely that is what MiFID II was trying to achieve in the first place?

    Almost four years since the inception of MiFID II, frustratingly, transparency is still very much a work in progress.

    Data quality and transparency

    Cazenave does identify that poor data quality, complexity of transparency regimes and provisions for waivers and deferrals have not improved the level of transparency.  Again, for those of us covering MiFID II for a number of years, this was obvious. Hopefully, ESMA will simplify this going forward and perhaps as we continue to see divergence, the FCA will soon come out with its own streamlined requirements for optimum transparency. Cazenave highlights the CFTC success story in this space, in that market integrity can still be maintained alongside a more transparent trading landscape.

    Potential solutions

    And likewise, it has finally dawned on ESMA that a consolidated tape is not an easy thing to achieve. Frameworks need to be in place, complexity needs to be reduced, synergies in reporting increased and data costs are still high (let’s be honest, they always have been and always will be. We live in a data-centred world).

    So the question is, is ESMA finally going to bow down and admit that by de-facto it is actually the golden source of MiFID II European data and can hence go a long way to help with this?

    We saw earlier in the year the memorandum of understanding between ESMA and the FCA and there will be a further transition period. It makes sense that this is maintained, as Cazenave says, “given the interconnectedness of EU and UK Markets”.  My hope is that we will keep capital markets open, orderly and liquid as well as competitive, and one day we’ll get to true transparency.

    What’s next?

    In addition to the lack of transparency in derivatives, Cazenave explained that although ESMA is on a journey with regards to data quality, it is a key priority to make the best use of the data that it collects. ESMA is also keen to promote data-driven regulation, she said.

    Cazenave said that the numerous initiatives ESMA had put in place as part of its data strategy had really helped it improve data quality and that it is trying to work on standardisation of reporting requirements wherever possible including making sure that data is more usable for the relevant authorities and market participants alike. Something that will definitely be welcomed by the industry.

    To read the read the full speech, please visit ESMA’s website.

  • What’s coming up next in shareholding disclosure?

    What’s coming up next in shareholding disclosure?

    One of our Shareholding Disclosure Service’s main points of difference is the regulatory expertise that develops and supports the system. We are delighted to welcome Senior Regulatory Reporting Specialist Michelle Rowe who recently joined Kaizen’s Shareholding Disclosure Team from a tier 1 investment bank. 

    We caught up with her to find out about the latest in the shareholding disclosure space, and more about her background and career to date. 

    What developments are we seeing in the world of shareholding disclosure?

    We have seen a noticeable increase, since the COVID-19 global pandemic, in foreign investment restrictions and increased short selling position reporting. We are seeing this continuing into 2022; in the UK we have the introduction of the National Security and Investment Act (NSIA), in France there are restrictions in ownership of the renewable energy industry, and reforms in Australia regarding foreign direct investment (FDI). I believe we will continue to see these type of sensitive industry and foreign ownership reporting and pre-approval regulatory changes as the global economy strives to recover from the effects of the pandemic.

    What makes shareholding disclosure so challenging?

    The world of shareholding disclosures is a highly complex, pressured, challenging and at times a very stressful environment to work in, particularly when things go wrong. Things can be turned upside down very quickly when a disclosure is missed, incorrectly filed, or even triggered in unfamiliar territory. Trying to build monitoring systems in-house has been a considerable challenge – I have been a part of such projects. When you are trying to do this as a side project to your day-to-day role of complying with shareholding disclosure rules, it’s almost impossible and projects often fail.

    I am excited to be working for a firm that has an impressive existing disclosure system, which even those key players within the banking sector struggle to achieve. Kaizen Reporting has a true depth of knowledge which is invaluable in this space.

    Tell us a bit about your background…

    It all started from completing a law degree and the drive to initially practice law. Completing my Legal Practice Course (LPC) at London’s Inns of Court helped steer me into the world of compliance, soon realising that I was much more focused on the corporate side of law and the regulations governing the business and financial sectors. Shortly after the completion of my LPC, I was lucky enough to land a position within compliance at tier 1 investment bank, Morgan Stanley. This was a fantastic learning experience and I started my career in shareholding disclosures there. I then went on to work at two other top tier investment banks, Barclays and Deutsche Bank.

    Why did you join Kaizen?

    The thought of moving away from my career of 14 years in investment banking compliance wasn’t an easy decision, but I very quickly knew it was the right one. This year I decided to seize the opportunity to work for Kaizen; I was excited to put all my in-house experience into making a difference and being able to share that experience with a large client base.

    For me, Kaizen’s experienced team and its vision of continuous improvement was the main driver – to always change, evolve and improve.

    It is exciting to be part of something which doesn’t want to simply provide a ‘tick box IT solution’, but one which wants to create a timeless solution for all types of clients, to interpret and automate its way past those never ending ‘grey’ areas. We want to have a positive effect on those shareholders who want to expand into new jurisdictions, new products, new business strategies, knowing that they will be fully compliant with the shareholding disclosure rules.

  • SFTR: Time for reflection or a fresh start for the buy-side?

    SFTR: Time for reflection or a fresh start for the buy-side?

    Time to reflect on the past year: the anniversary of the SFTR reporting go-live for pension funds, insurance & re-insurance companies, AIFs and UCITs falls today. Firms got over the line but how confident are Compliance teams that the firm is truly compliant? The trade repository (TR) public data has highlighted data quality issues and with it, potential systemic issues. Collateral reporting in particular appears to be a pain point but also something that may raise alarm at national competent authorities – with fears of under or over collateralisation. ICMA’s recent report provides a good summary of exactly what the TR data has revealed.  

    When will regulators act?

    Tackling the lack of visibility around the functioning of SFT markets, together with preventing the next financial crisis being caused by excess leverage or interconnectedness were the foundations on which SFTR was built. Without high quality data, this simply is not possible and regulators will be poised to take action against parties preventing this transparency through low quality reporting.

    Questions buy-side firms should be asking  

    Many buy-side firms opted to take advantage of delegated reporting offerings from their broker dealers. Delegated reporting maybe out of sight but are you receiving sufficiently detailed management information from broker dealers for it to be out of mind? How much visibility do you have around the completeness, timeliness and accuracy of your firm’s reporting? Are you able to see the trade repository acceptance status of your firm and your fund’s reports? Are you able to keep on top of the status of new reports and lifecycle events? Have you experienced any issues over the generation, transmission, receipt or onward reporting of collateral re-use or cash re-investment? While you may delegate the physical act of reporting, unfortunately, you cannot delegate the legal obligation to ensure that SFTR reporting is complete, accurate and timely.

    Have you noticed variation in the quality of the regulatory reporting services you receive? Are certain report submitting parties filling you with less confidence? Have you reviewed how consistent the reports are between different brokers? Are securities being classified in the same, correct way across different report submitters?

    Clarity on the rules

    Uncertainty has been the bane of all reporting parties under SFTR. While reporting counterparties like clear sets of rules, the current, rather immature state of the guidelines and Q&A mean that regulatory and compliance certainty is sadly lacking. The latest SFTR Q&A backs this up.

    What’s next?

    In our experience, sell-side firms are facing significant challenges in ensuring the quality of their own reporting, never mind their client’s reporting. That SFTR has been as successfully adopted as it has amid dramatically shifting landscapes has been quite remarkable. The pandemic (with no additional delays for the buy-side) has been compounded not only by Brexit (with obligations to report under two distinct jurisdictions and in some instances both regimes) and now the withdrawal of one of the trade repositories that perhaps initially had the keenest buy-side focus. This withdrawal has introduced scheduling and porting challenges together with a renewed focus on the quality of reporting. No better time than a migration to take a fresh look at whether everything is being reported, that validation and reconciliation queries are being addressed and that reports are not only valid (they pass TR validation rules) but are also correct.

    • As we enter year 2, please feel free to contact us to learn more about our SFTR quality assurance services and how we can assist in ensuring 100% compliance.   
  • ESMA EMIR Q&A – September 2021

    ESMA EMIR Q&A – September 2021

    With ESMA’s open hearing and the FIA’s IDX in London behind us, it’s quite timely that we saw a new Q&A published across many of the regulations last week, including EMIR. At IDX, ESMA’s Natasha Cazenave delivered a keynote speech noting their approach for “less complexity, more effective” rules as part of their data-driven approach and ongoing review of the legislative frameworks. Unfortunately ESMA’s latest Q&As have not quite caught up with this approach and we see a common theme amongst them –  a missed opportunity to provide the industry with increased clarity.

    ESMA has provided the following brief updates as part of their latest Q&A.

    TR Question 3b (f) – Reporting valuations

    (f) *new* Should counterparties send valuation update on the last day of a derivative and for intraday derivatives? (i.e. derivatives that are concluded and terminated on the same day)?

    TR Answer 3b (f)

    (f) No, it is not required to send valuation and collateral data in those cases.

    This isn’t anything new from ESMA under the reporting valuations section, as we know that Intraday reporting is mandatory under EMIR.

    TR Question and Answer 40 – LEI changes due to mergers and acquisitions

    A very brief update here, but hopefully nothing new in the world of reporting.

    This section deals with the processes that Trade Repositories (TR) should follow and how firms should update their TR of a merger or restructuring where we see changes in the Legal Entity Identifier (LEI).

    TR Q&A 40 can provide much confusion for the industry and many of us who have worked in reporting at either a TR or in the frontline at a firm have seen the issues that can arise, namely the expectations of the TRs and the requirements on the firm to communicate changes in a timely manner.  As part of this update, ESMA provided the following:

    “TR(s) should inform the relevant reporting counterparties, report submitting entities, entities responsible for reporting (to the extent that they are participants to the TR) as well as third parties which have been granted access to information under Article 78(7) of Regulation (EU) No 648/2012, as applicable, involved in the derivatives contracts concerned by the LEI change.”

    Firms still need to not only continue to meet their obligations under EMIR Article 9, but effectively Article 78(7) which notes that a TR shall have objective, non-discriminatory and publically disclosed requirements. This is an obvious thing once you sign up be a TR participant and/or gain access to your relevant data, so with the above we’re not really seeing anything new or material from ESMA.

    All in all, a very brief update to this version of the EMIR Q&A, but with ESMA’s keynote speech, fingers crossed we will truly see that effectiveness that ESMA speaks about in the not too distant future…

     

    • To read the latest Q&A please visit ESMA’s website.
    • For a conversation about the latest Q&A or the quality of your EMIR reporting, please contact us.
     
  • SFTR Q&A 11: Reporting LEI changes following Corporate Actions

    SFTR Q&A 11: Reporting LEI changes following Corporate Actions

    SFTR reporting parties and those involved in the business of promoting SFTR data quality are forever grateful for all of the Q&A and guidance they receive given the complex and imprecise nature of what is still a relatively immature regulation.

    Uncertainty is after all the curse of operations and compliance managers when it comes to ensuring compliance with transaction reporting regimes. Certainty is very much the Holy Grail….

    Unfortunately, the latest Q&A is really such an edge case that it does very little to relieve that uncertainty. There remain many unanswered questions and uncertainty in how to populate many of the fields that are required for the majority of SFTR reports (such as which jurisdiction to use (incorporation or headquarters) and what type is the definitive answer to security/collateral type fields). We urge regulators not to sit on the fence but either to provide precise, exact answers or ultimately remove fields from the schema.

    Question 11 “LEI Changes due to Mergers & Acquisitions” was published on 21 September and answers a) Which data fields should be updated in case of corporate restructuring events affecting the LEI?  and b) To which entities the information on the LEI update should be broadcasted?

    In response to:

    1. ESMA stated that following receipt of a notification regarding a corporate restructuring, Trade Repositories (TRs) should identify all outstanding SFTs in which the LEI of the Reporting counterparty, Other counterparty, Entity responsible for the report, Report submitting entity, Beneficiary, Tri-party agent, Broker, Clearing member, Central Securities Depository (CSD) participant, Agent lender, CCP or LEI of the issuer have changed and replace the old identifier with the new LEI.
    2. For other corporate restructuring events e.g. partial acquisitions and spin-offs affecting only a subset of outstanding SFTs, the new entity should provide the TR with the UTIs of the SFTs impacted by that event. The TR should then inform all of the other relevant parties to the transaction of the change.
    • If you require help to navigate through the complexity of SFTR reporting or would like to explore the benefits of quality assurance through regulatory testing then please contact us.
  • The End of the Beginning for MAS Reporting

    The End of the Beginning for MAS Reporting

    The final phase of MAS reporting has finally come to pass, and all firm types in scope for MAS reporting are now required to report trades in all asset classes. Hopefully this shouldn’t be news for any affected firms, but there’s no time to sit back and relax, with MAS finally having joined the range of derivatives regulators looking to rewrite their rules.

    MAS proposal: CDEs, UPIs, UTIs

    The first consultation on enhancements to the MAS OTC derivatives reporting regulations is now closed, with proposals to introduce the global UTI, and many of the CDEs, in line with global harmonisation efforts, as well as introducing collateral and margin reporting, to come into effect in Q2 2023. MAS currently plans to implement the Unique Product Identifier (UPI) separately later on, despite the expected go-live of the UPI reference data system in July 2022, and so they’ve retained a wide range of product data elements that may quickly become redundant, sure to be a source of frustration if left unchanged in the final rules. We look forward to seeing what feedback firms have given and how MAS takes it on board.

    Re-Reporting: a fresh start

    Outside the content of trade reports, MAS has proposed the use of ISO 20022 XML for reporting, and has offered a variety of approaches to a global UTI generation waterfall to resolve the challenges of differences in cross-jurisdictional reporting deadlines. MAS has also proposed to require reporting counterparties to re-report all open trades above a minimum remaining maturity once the proposed reporting standards come into force, which is sure to be a pain for entities which have only just started reporting under the current rules to begin with.

    Despite the pain that digging up new data on old trades is sure to cause, at Kaizen we know from experience looking at mixed RTS 1 and 2 EMIR reports that trying to squeeze trade reports from an old specification into a new structure following the rules update would result in messy, incoherent trade state data, so it makes perfect sense that MAS is mirroring ESMA in pushing to wipe the slate clean once they complete their rules rewrite.

    Renewed focus on data quality

    Mandating updates to old reports is a sure-fire indication that MAS is getting serious about data quality and reporting firms will want to ensure that they’ve captured any existing issues while they develop their new reporting framework, not to mention checking over their old reporting before they update open trades for the new requirements.

     

    • Is your MAS Reporting accurate and complete? Can you evidence this? We can help. Contact us for a complementary consultation with one of our regulatory experts and find out how you can stay on the right side of the Singapore regulator.
  • And Then There Was One

    And Then There Was One

    The London Stock Exchange Group has announced that they are closing their SFTR trade repository (TR) with effect from 31 January 2022, the same day that new ESMA schemas and validation rules are due to be introduced.

    Dwindling number of vendors

    This development should perhaps not be any great surprise as SFTR services in general are gravitating towards a dwindling number of vendors. However, it may cause some concern at regulators, leaving a sole TR in the UK and effectively a duopoly in the EU too (with KDPW perhaps having most relevance only to the Polish market). UnaVista itself originally spawned from the UK FSA (now FCA) sale of their Transaction Reporting System (TRS) for securities transaction reporting, having subsequently expanded into the TR space. Could the FCA consider entering the fray again, to offer SFTR reporting parties an alternative and circumvent any monopolistic issues in future?

    More accurate reporting?

    A greater concentration of SFTR reports is not without benefit. Reconciliations become more centralised, with fewer if any inter-TR reconciliations necessary. It will also concentrate expertise and users in fewer places to work together to tackle reporting challenges and data quality. The FCA overseeing a single TR could also choose to be more pragmatic in addressing schema, validation rules and other reporting issues, to prioritise accurate, high quality reporting over the strict application of the rules governing a TR.

    Tone from the top

    In terms of what will benefit both the industry and regulators most, we continue to put the spotlight on measures to tackle data quality. In our opinion, this needs to come from the top, from regulators themselves. This includes a stronger partnership with industry in writing a far more comprehensive and watertight set of rules, standards and definitions to remove any room for ambiguity or controversy. This would be reinforced if reporting parties were encouraged to adopt regulatory testing and reconciliation to ensure continual improvement in the quality of their reporting.

    How Kaizen can help

    Firms who are required to migrate their activities from UnaVista to another TR, either in the EU or the UK may take this opportunity to go back to basics and thoroughly review their reporting scope and methodology, prior to onboarding at the new TR. Kaizen is uniquely placed to uncover all of the errors and questionable elements of your SFTR reporting to date, through our Accuracy Testing and Advanced Reconciliation services, enabling firms to start on a solid footing at the new TR.

    • For advice about moving TRs or a no-obligation conversation about how we can help you get your SFTR reporting into shape please contact us.

     

  • New SFTR Validation Rules – Same Old Challenges

    New SFTR Validation Rules – Same Old Challenges

    Looking back on the first year of SFTR, we’ve highlighted the ineffectiveness of the validations and the trade repository (TR) reconciliations as a means of ensuring data quality. Given the global nature of SFT markets and post-Brexit in particular, the vast majority of transactions are simply non-reconciled by the TRs. According to DTCC, just 24% of EU SFTR reports are eligible for the TR reconciliation (dropping to 14% in the UK).

    The recently released new schemas and validation rules (due to come into force on 31st January 2022) were a real opportunity to provide the clarity the industry craves and have a material impact on data quality. Unfortunately, the published changes are minor and will result in very limited improvement without significant further guidance / Q&As.

    Why is data quality so bad?

    When entering into data quality discussions, we are in effect doing the regulators’ bidding for them. The two greatest stumbling blocks we face are:

    1) A significant lack of clarity around the rules, particularly in relation to security & collateral classification fields where far more explicit definitions and specifications are required (or else they should be removed)

    2) The need for more explicit, official acknowledgement that no field is truly optional (or better still making all optional fields conditional). For example, why are CSD participant, branch of reporting/other counterparty, triparty agent, broker, beneficiary, agent lender, earliest call-back date, adjusted rate, price currency, market value, floating rate parameters, currency of collateral nominal amount and price currency not conditional? Clearly, the regulators’ intention was to extract this data if it were applicable to the transaction or event, so why do they not stamp their authority on this?   

    So, what are the changes?

    The changes themselves amount to more granular counterparty data being required across more action types and a number of clarifications around the loan and collateral data fields.

    The most sensible of these include:

    • UTIs becoming mandatory for margin loan collateral updates,
    • Clarification that issuer LEIs must not be branch LEIs,
    • Individually cash collateralised securities lending trades must either have fixed or floating rebate rates
    • The value date of collateral becoming optional for collateral updates and corrections
    • Commodities have been ruled out as securities lending collateral
    • Further clarification has been given that action types termination (ETRM) and position component (POSC) can only be reported once for a given UTI and pair of counterparties.

    Pain and expense for market participants

    One loophole being closed for repo is that previously the type of collateral component was effectively optional on new reports and consequently parties were reporting repo loans without any collateral detail whatsoever (even single piece of collateral repos where the collateral was known at point of execution). Repos are effectively driven by the underlying collateral. However, this same change to securities lending (loan driven) has caused some consternation where parties must either report the type of collateral or a collateral basket identifier for collateralised SL trades. The workaround is likely to be the routine reporting of not available (NTAV) collateral baskets in relation to SL transactions. This will cause pain and expense for market participants while adding no additional information to reports.

    A missed opportunity

    In conclusion, this is a significant opportunity missed. Data quality is poor and a continual focus on tweaking validation rules (and associated schema) will do very little to tackle this. Measures to mandate regulatory testing, quality assurance controls and reconciliation (as per MiFIR) would have a far greater impact on ensuring regulatory submissions are fit for the dual purposes of identifying macro systemic risk and market manipulation.  

    The new schemas and validation rules are available on ESMA’s website.

    • For a conversation with Jonathan about your SFTR Reporting or a no-obligation review of the quality of your reporting, please contact us.

     

  • SEC Swap Reporting – SBSR, The long journey

    SEC Swap Reporting – SBSR, The long journey

    November 2021 sees a landmark milestone marking the fulfilment of a decade long journey towards SEC Security-Based Swap Reporting (SBSR). If we track the origins of the story further back to the 2007/8 financial crisis, then the distance travelled to reach this implementation is pretty epic.

    SBSR and the reporting of Security-Based Swaps (SBS) is the SEC’s slice of the Dodd-Frank reporting requirements introduced after the US and the other G20 governments and regulatory bodies agreed to mandatory reporting of all OTC derivatives transactions.

    The 2010 Dodd-Frank Act empowered the SEC to implement reporting of swap trades relating to so- called ‘single-name’ Security-Based Swaps i.e. an equity or credit derivative based on an underlying security that trades on a regulated exchange.

    SEC or CFTC Swap Reporting? Single & mixers

    The phrase ‘single-name’ is a bit misleading here as swaps relating to more than one underlying security are also reportable under SBSR. The rule of thumb being that if the swap relates to an index compromising nine or less securities then it’s deemed a “Narrow-Based Security Index” and reportable to the SEC under SBSR. And if it relates to ten or more securities then it’s reportable to the CFTC instead.

    And if that wasn’t already confusing enough there are also ‘mixed swaps’ that are reportable to both the SEC and the CFTC. These are swaps that generally meet the criteria to be considered Security-Based Swaps but also have one or more elements that derive their value from interest rates, currencies or commodities (i.e. asset classes not in scope for SEC reporting). For mixed swaps the two Commissions are jointly mandated to prescribe the regulations.

    And just in case ALL of that wasn’t confusing enough for you to be reaching for the aspirin, there are also rules governing what happens when an index migrates from being considered a narrow-based security index to becoming a broad-based security index. Or of course if they should migrate in the other direction from broad to narrow to complete the hakuna matata circle of life. Well life of an index rather than say an animated lion.

    SEC Part 43 – Faster than Sonic the Hedgehog

    The SEC has mandated that reporting firms need to report ‘real-time’ pricing data almost immediately upon execution. The actual data that gets publicly disseminated is heavily anonymised but through showing the pricing trends for the various swap instruments provides price transparency to ensure a level playing field.

    The rules for the real-time prices reporting are often referred to as ‘Part 43 reporting’. Only a small number of fields are required to be sent for a Part 43 submission but the rules state that these submissions must be sent “as soon as practicably possible”. This chop-chop, pronto requirement for real-time reporting can be quite onerous on the firms as in many cases the expectation is that the report will be compiled, verified and submitted within seconds of the trade being executed.

    The SEC has also prescribed Part 45 reporting which entails the firms submitting the full details of the swap data such as the parties, the economic terms and various other details of the transaction. Firms have until T+1 to submit these details which unlike the real-time reports are available only to the regulators and not made public.

    Seeing the value

    SBSR verges off into a different direction from the CFTC Part 45 reporting though as the SEC has not required the firms to report valuation data. Swap data reporting under the CFTC rules requires the firms to submit a daily valuation that specifies what the reporting firm (or clearing house for cleared swaps) calculates as the current value of each open trade position. The SEC has raised eyebrows by not requesting the same and instead stipulating that firms must submit “the data elements necessary for a person to determine the market value of the transaction”.

    Critics of this approach argue for a reporting regime that is predominantly focused on systemic risk it’s a mistake not to compel the firms to report their internal valuations. Valuation Reporting would allow the SEC to assess whether any firms are being overly optimistic on the value of their traded positions and are hence taking on too much risk.

    SEC Swap transaction (Part 45) reporting commences on 8 November. And SEC real-time (Part 43) reporting commences on 14 February 2022. Price transparency for single-name Security-Based Swaps. Just what your sweetheart was hoping for on Valentine’s. But nonetheless the fruition of a very long process and a huge amount of effort contributed by the reporting firms, the trade associations, the swap data repositories and of course the SEC itself.

     

    • For a conversation with Alan or one of our regulatory specialists about the above topics, please contact us.
  • FCA Publishes 2021/22 Business Plan

    FCA Publishes 2021/22 Business Plan

    The FCA recently published its 2021-2022 Business Plan covering many areas within the wholesale and retail space. This provides further evidence and also aligns with its recent updates on regulatory reporting that it’s looking to be more assertive across the industry. We note that the FCA states that it needs to transform and change the way it does things given the recent challenges such as Brexit, the pandemic and technology are placing on them, and have outlined three key changes which are:

    • More innovative – taking advantage of data and technology to increase their ability to act decisively in the interests of consumers
    • More assertive – testing the limits of their powers and engaging with partners to make sure they bring their powers to bear
    • More adaptive – constantly learning and always adjusting their approach as consumer choices, markets, services and products evolve.

    In addition, there are several references to data quality, technology, automation and innovative data analysis that will allow them to identify risks to concentrate on more closely.  Hence, they will focus on the following during the next 12 months:

    • Data: Strengthen the foundations of their data, improving accuracy and accessibility. This will mean they can use it more effectively to identify harm and intervene more quickly
    • Information: Build capabilities to deliver automation and efficiencies, improve systems infrastructure and use technology to make operations more efficient
    • Intelligence: Use advanced analytical techniques to proactively identify and prioritise firms or harms for investigation.

    • To read the full FCA Business Plan visit its website.
    • For a conversation with Francesco or one of our regulatory specialists about the above topics, please contact us.
  • SFTR One Year On

    SFTR One Year On

    Following on from our recent webinar ‘SFTR Reporting – the highs, the lows and the year ahead‘, Senior Consultant Richard Comotto and Kaizen’s Jonathan Lee look back at the first year of SFTR and ask what’s next for this most complex of reporting regimes.

    Impressive, ambitious delivery in the midst of a pandemic

    The initial SFTR delivery was a remarkable success story given the Covid pandemic, delivered as it was from employee’s bedrooms and breakfast tables. More prescriptive regulatory texts helped to an extent with many lessons learnt from EMIR and MiFID II, particularly regarding the creation and sharing of unique trade identifiers (UTIs). Following the pain of EMIR, all credit should really go to the industry for such a successful delivery in such difficult circumstances.

    Trade repository ACK rates were extraordinarily high

    The trade repository (TR) accepted rates were exceptionally high from day one, aided by the three-month delay to implementation and an extended user acceptance testing period. However, merely meeting the validation rules requirements has been the easy part of this delivery.

    SFTR public data has been poor but telling

    TRs published data has been poor, but has indicated lower volumes and notional traded than expected or anticipated. Methods used to compile the data have been opaque and together with published data vary significantly between TRs. The lack of useful market data as part of the TRs published data has also been a source of frustration.   

    On one hand, data indicates some under-reporting of collateral data and possibly loans too. On the other hand, signs of double counting of loans exist where both counterparties have a reporting obligation, especially when reporting to different TRs. Potentially, some firms trading SFTs have not reported any transactions at all, while others lack collateral updates, valuation updates, re-use updates, margin updates or modifications as required under the regulation.

    Many grey areas and regulatory requirements that lack clarity

    The lack of clarity in areas such as bilateral margin reporting, collateral re-use & cash reinvestment reporting, and the reporting of commodity financing transactions has led to an apparent lack of reports covering these areas. In spite of repeated industry presentations prior to go-live about the significance of bilateral margining for repo, it has proved something of an after-thought in the reporting taxonomy. Indeed, Jonathan stood up at the ESMA Paris hearing in November 2016 suggesting that bilateral margining had such significance, it warranted its own reporting table under SFTR – sadly, this fell on deaf ears. Under-reporting is often easy to spot, particularly in the wholesale lack of collateral updates relative to market convention in repo markets.

    Late publication of guidelines, the final report and Q&As, often incomplete, muddled, confusing and not without error, have further diminished data quality and completeness. There has been a tendency to answer one question, while posing others, leaving the industry rather perplexed. We hope that the schemas, validation rules, guidelines and Q&As will evolve and improve but this is likely to be a slow process.      

    The majority of reported activities are valid but wrong

    Kaizen’s quality assurance indicates that a large proportion of reporting counterparties benefit tremendously from regulatory testing. The majority of reports tested for the first time by Kaizen exhibit errors and questionable population, typically reported with valid (they pass trade repository validation rules) but wrong data. A survey poll of respondents during our recent webinar indicated that only 22% acknowledged the scale of the data quality issue (selecting 76%-100% of reports as valid but wrong). The actual figure is 93%.

    Reporting statistics on iceberg graph

    The TR reconciliation process is woefully ineffective as a data quality control

    The principle mechanism regulators put in place for promoting data quality under SFTR is the TR reconciliation. The concept is that if both firms submit reports directly from their books and records then trades and post trade lifecycle events should ultimately match and provide assurance that if both sides agree the data must be correct. This has proven to be a rather naive premise for two key reasons:

    1. The vast majority of SFTR reports are single-sided and not subject to the reconciliation. According to DTCC, these figures currently stand at 76% in the EU and 86% in the UK. When surveyed during our latest webinar, only 32% of webinar participants polled began to appreciate the ineffectiveness of the trade repository reconciliations (selecting the level of TR reconciliation at 0-25%).
    2. SFTR was so ambitious in its data reporting requirements that a large proportion of reporting counterparties don’t have enough reference data or static data to complete a report. Therefore, much of the data is sourced from third parties, not the reporting firm’s books and records and is of mediocre to poor quality.

    SFTR data infographic

    Firms are committing significant resources to addressing TR reconciliation breaks, but potentially at the expense of ensuring the accuracy and completeness of their own reporting. From a data quality standpoint it looks grossly ineffective. Unfortunately, the costs of SFTR to the industry thus far, appear to far outweigh the benefits to regulators.

    Regulatory testing is the key to unlocking SFTR data quality

    At Kaizen, we have repeatedly urged our clients to focus on the quality of their own SFTR reporting, empowering them to be in a position to stand up to their counterparties in the TR reconciliation space and to regulators where necessary.

    Regular, periodic, full universal quality assurance through regulatory testing enables firms to gain a tight grip on the reporting errors they are making. Armed with this information, they are able to prioritise fixes to maximise efficiency, keep regulators on-side and nip issues in the bud. Subsequent test runs ensure necessary remediatory progress is being made, new business deliveries do not break reporting accuracy and new Q&A, guidelines, schemas and validation rules are accounted for.

    • If you would like to explore how Kaizen Reporting can help your firm be truly SFTR compliant, please contact us.
  • Complexity from simplicity – the INTC story

    Complexity from simplicity – the INTC story

    The replacement of the INTC code when aggregating client orders is one of the changes proposed by ESMA in its recent review of MiFIR Transaction Reporting.  On the surface this is to be welcomed, but do ESMA’s proposals go far enough?

    How INTC currently works

    When investment firms aggregate orders across more than one client, they are required to enter a value of ‘INTC’ in the relevant Buyer or Seller identification code field in their MiFIR transaction reports.

    It is by necessity that firms must use the ‘INTC’ aggregate client account as it’s generally not possible to allocate individual fills to specific clients until the aggregated order has been completed and an average price is known.  For example, if a firm is buying 100,000 Vodafone shares on behalf of three clients where Client A wants 25,000 shares, Client B wants 30,000 shares and Client C wants 45,000 shares, when reporting a first execution fill of 9,000 shares it’s not possible to accurately allocate the shares pro rata to all three clients in a single transaction report, so they must be linked using the INTC account.

    Essentially, the ‘INTC’ account is used to facilitate the reporting of the market-side executions and ‘warehouse’ the Vodafone shares until the order is completed.  Once the order is fulfilled, e.g. 100,000 shares at an average price of 113 pence then the three allocation transaction reports can be made showing the shares switching from the ‘INTC’ account into the accounts of client A (25,000), client B (30,000) and client C (45,000) all at the average price of £1.13 GBP.

    The INTC rules

    Use of INTC comes with a few simple rules:

    1. The INTC account must be flat at the end of each reporting day.
    2. INTC can only be used where orders from more than one client are being aggregated prior to execution. A client here, means a single LEI or single National Client Identifier.
    3. The timestamp on the allocations must be the time of the first fill trade
    4. Allocations would be at the average price of each of the fills.

    These rules seem simple enough, however in practice, they do lead to a great deal of complexity when trying to apply them to real world activity.  This has led reporting firms and system providers alike to struggle with certain real-world scenarios. A few examples are shown below:

    • Firstly, ensuring the INTC account is flat at the end of the day.  Firms that work orders over midnight UTC are effectively required to close their books at midnight and apply the allocations based on the fills accrued at that point, then start again with any post-midnight fills.  This of course would double the amount of allocation transaction reports required but also presents a scenario in which most systems have not considered. Trading in the APAC region often faces this challenge.
    • Secondly, some asset managers group orders across entities.  This is primarily driven by their best execution policy and group trading arrangements.  Where this happens, scenarios arise where only a portion of the fills may be allocated to reportable activity. 
    • Thirdly, where systems operate at sub-fund or sleeve level but they roll up to the same LEI, INTC should not be used.  Many systems are unable to cope with this.
    • Fourthly, regulators have asked where INTC is used for multiple client orders, but some allocations relate to the same LEI that they are rolled up into a single allocation for that LEI so that there are never two allocations with the same LEI for the same group order.

    ESMA’s proposal

    Challenges with the INTC account have led ESMA to suggest some changes which will allow NCAs to more easily review how an order is being reported.  ESMA is proposing that the generic and consistently applied ‘INTC’ account code is replaced by a code, internal to the investment firm but that uniquely links the market-side execution reports and the client-side allocation reports.

    What makes sense about ESMA’s proposal

    In terms of usefulness, it makes sense to replace the generic ‘INTC’ code with a unique code that links market side executions with the related client-side allocations.  This linkage is currently often difficult to do, particularly for firms that aggregate multiple orders in the same financial instrument at different points or throughout the same trading day.  It will also make it easier for firms to ensure that the ‘INTC’ account is flat at the end of every day and to more efficiently identify which specific transaction reports are leaving a position in the ‘INTC’ account.

    But….

    However, not proposing a separate field for what is effectively a “Group Order ID” could be a missed opportunity as it could have involved fewer coding changes for firms.  Importantly, it would have linked transaction reporting data with the related order record-keeping information. This would be hugely advantageous from a market abuse detection perspective.  The “Order ID” could also be applied to non-INTC related trades to further enhance the effectiveness of surveillance more broadly.

    Additionally, ESMA’s final report does not provide guidance or direction for instances where client orders are aggregated across more than one investment firm within the same financial group. This is a scenario where we have seen several firms have difficulties.

    Time will tell whether the FCA will follow ESMA’s lead or propose to use this as an opportunity to go further and create a powerful link between transaction and order data.

    • While ESMA’s proposed changes to MiFIR Transaction Reporting are at least a few years away, adequate implementation time will be required for firms to make the necessary changes.  For a conversation with Simon or one of our regulatory subject matter experts about these changes or how to get your transaction reporting into better shape, please contact us.  

    • Read our recent Industry Q&A on ESMA’s proposals here.
  • October 2021 – The End of Part 1 for MAS

    October 2021 – The End of Part 1 for MAS

    On 1 October 2021 the Monetary Authority of Singapore (MAS) implements the final phase of the reporting of OTC derivatives that it began in 2014. The Singapore regulator has extended the reach of its reporting obligations incrementally based on asset class, the type and size of the firm, and whether the OTC contracts were booked or traded in Singapore.

    The upcoming October milestone sees the reporting of FX, equity and commodity contracts which began for the banks years earlier (2015 for FX and 2018 for EQ & CO) extended to other firm types. Essentially the buy-side is now obligated to report these three asset classes and this completes the rollout of the reporting rules as legislated in the Securities And Futures (Reporting Of Derivatives Contracts) 2013 Act.

    Proceed with caution

    The 2021 deadline was delayed a year due to the Covid-19 pandemic and marks the end of the line for the original reporting requirements after a series of consultations with the industry and a determinedly collaborative approach with MAS peers including ESMA and ASIC. However if the recent 5 July 2021 consultation is any indicator, the Singapore regulator is far from ready to rest on its laurels.

    Slicing and dicing

    Some regulators rolled out their reporting obligations incrementally based on factors like report type. For example ESMA staggered collateral and valuation reporting to commence six months after the transaction reporting began. In Singapore MAS has taken a far more granular approach and staggered the start dates based on four different criteria:

    • Asset class: credit, interest rate, FX, equity & commodity
    • Firm type:
      • banks and merchant banks licensed in Singapore
      • finance company licensed in Singapore
      • subsidiary of a bank incorporated in Singapore
      • insurers licensed in Singapore
      • holders of a capital markets services (CMS) licence
      • significant derivatives holders
    • Activity type: whether the OTC was ‘booked’ or ‘traded’ in Singapore
    • The groups of fields to be reported:
      • Main transaction and counterparty details
      • Additional transaction details
      • Trader and booking location details.

    Additionally the insurers, bank subsidiaries and holders of CMS licenses are subject to a threshold and need to trade over S$5 billion annual aggregate gross notional amount of specified derivatives.

    Stepping stones

    • April 2014 saw reporting begin for credit & interest rate contracts booked in Singapore, with banks and merchant banks licensed in Singapore being the first firm types obligated to report.Credit and interest rate reporting was quickly extended to other firms including bank subsidiaries, insurers, finance companies in July 2014, and significant holders of derivatives in October 2014.
    • May 2015 saw the banks and merchant banks begin reporting FX derivatives booked in Singapore
    • November 2015 was a busy month as the reporting obligation for the banks was expanded to include FX, credit and interest rates traded in Singapore
    • October 2018 saw the banks being asked to start reporting equity and commodity contracts booked or traded in Singapore
    • October 2020 was originally scheduled to extend the reporting of FX, equity and commodities begin for the other firms types (bank subsidiaries, insurers, finance companies etc.) but this was delayed a year due to the impact of the global pandemic
    • October 2021 therefore sees the completion of the journey with all Singapore firm types reporting all five asset classes, all fields and all trading/booking activities.

    Further over the horizon

    Seven and a half years of reporting implementations isn’t the end of the story by any means. Like many of its G20 counterparts, MAS has been closely following developments elsewhere and heavily engaged with harmonisation efforts such as CDE. And like its peers at the CFTC, ASIC, HKMA, ESMA and the JFSA, the Singapore regulator will be implementing its own rewrite of the reporting rules. As mentioned earlier in this piece the consultation processes are underway in Singapore and we will share our observations as this process evolves.

    Is your MAS Reporting accurate and complete? Can you evidence this? If you are a buy-side firm preparing to report for the first time, we can help.  Contact us for a complementary consultation with one of our regulatory experts and find out how you can stay on the right side of the Singapore regulator.

  • FCA update: Reporting under UK EMIR and transition from LIBOR

    FCA update: Reporting under UK EMIR and transition from LIBOR

    Seven months into 2021, and the industry continues to receive updates on UK EMIR and EMIR. In the past week we’ve had an update from the Financial Conduct Authority (FCA) on UK EMIR. Before we look at the technical update, I wanted to note the FCA’s closing statement where they continue to reference their ‘proportionate and risk-based’ language:

    “While we expect you to make the necessary preparations to ensure the relevant UK EMIR reports are updated in a timely manner, we will apply our supervisory powers for this requirement in a proportionate and risk-based manner.”

    The FCA uses this language across many of their publications, including the Supervision Section of the FCA Handbook. However, given that they’ve used it in consecutive updates (see March 2021), could the FCA finally be getting ready to show its teeth when it comes to UK EMIR?

    Now onto the fun of the guidance they’ve provided as part of their UK EMIR update. This time we see the FCA’s guidance/rules on using a fallback reference rate in place of LIBOR and how they expect this to be reported under UK EMIR. The important and relevant updates are summarised below:

    Reporting of fallbacks in accordance with the ISDA protocol

    • The FCA guides us here by stating that when reporting a fallback reference rate that action type M should be used. The application of the fallback reference rate should be reflected in field 2.55 (floating rate leg 1) and as applicable in floating rate leg 2 by adding the suffix “fallback” to the four-letter code that described the floating rate prior to the application of the fallback. The example that is provided on the FCA’s page is “LIBO” should be changed to “LIBOfallback”
    • If an ISIN has been used prior to the application of the fallback, then this should be updated to reflect the update to the reference rate. If an ISIN is not available/cannot be generated then the FCA is not expecting an update here.
    • We all know that data quality issues persist under EMIR, and the FCA is showing appreciation and how this will work in practice as part of this UK update. They have noted that in order to mitigate data quality issues, including matching issues, that the modifications should be reported no later than the working day after the application of the fallback. This is the day when all LIBOR settings will cease.

    The examples provided are for Sterling, Euro, Swiss Franc and Japanese Yen where the modification should be reported one working day after 31 December 2021.

    In the case of US Dollar, the modification should be reported one working day after 30 June 2023.

    Reporting of bespoke fallbacks

    • Where fallback rates are agreed on a bespoke basis, the FCA guidance here is to report modifications consistent with the above.

    Reporting where a reference rate is otherwise amended

    • The FCA also notes that where the terms of a contract are changed that an alternative reference rate (e.g. SONIA) applies in place of LIBOR then this is also a reportable modification under UK EMIR.
    • Once again, the expectation here is to use action type M where a reference rate is amended, and also update all relevant fields to that contract. The Trade ID should remain the same.

    • To read the latest FCA EMIR update visit its website.
    • The FCA has also released a consultation on EMIR Refit this week.  Find out more on its website. 
    • For a conversation with Francesco or one of our regulatory specialists about the topics above, please contact us.
     
  • UPI Implementation: The Approaches of Regulators

    UPI Implementation: The Approaches of Regulators

    Throughout 2020 and 2021, regulators across G20 jurisdictions have undertaken revisions to their derivatives reporting rules, with an eye to greater standardisation across jurisdictions and the implementation of lessons learned. Regulators’ experiences with derivative trade data is behind the drive to improve the quality of data available for systemic risk assessment.

    While many consultations, reports, and publications have been devoted to the CPMI-IOSCO Critical Data Elements (CDE), and understandably so, given the fine-tuning required to ensure they fit every regulator’s needs, the harmonised Unique Product Identifier (UPI) is also central to ensuring that derivative products are fully identified in an efficient manner.

    Unique Product Identifier (UPI) Reference Data System

    The UPI identifies derivative products at a level of detail less specific than the OTC ISIN but more specific than the CFI Code. Once the UPI system is live, trade data reports across jurisdictions will all link to a single reference data library for product data, simplifying the work of regulators in accurately determining the details of traded derivative products. The Derivatives Service Bureau (DSB), which maintains the OTC ISIN library, is responsible for the development and implementation of the UPI reference data system, which is expected to be widely available for use from July 2022.

    The ROC recently hosted presentations by the DSB on the current status of UPI development to promote awareness among market participants globally. APAC and North American regulators were in attendance to set out how they anticipate UPI implementation to fare once participants are able to register and access the UPI system.

    There were a number of core takeaways, as well as a range of comments on how the UPI timeline will intersect with planned and ongoing regulatory changes.

    Key Takeaways

    • Regulatory staff encouraged market participants to engage with the DSB on gaining access to the UPI system as early as possible to ensure that they can fully link it into their reporting workflow in time for compliance.
    • There is confidence in the DSB’s implementation timeline and regulatory staff were comfortable setting out their own actions in anticipation of a July 2022 go-live date.
    • UPI implementation for derivatives reporting obligations is expected to take place for the first jurisdictions in Q3-Q4 2022.

    At present, outside the EU and UK, the requirement to connect to an external system to generate and obtain product identifiers is an unfamiliar step in the derivatives reporting process. Participants globally should start work early to ensure that they are ready once UPI obligations start rolling in.

    • For a summary of different global regulators’ approach to UPI implementation, please click on the tabs below.
  • ESMA’s MiFID Review:  An FAQ on the Significant Changes Proposed to MiFIR Transaction Reporting

    ESMA’s MiFID Review: An FAQ on the Significant Changes Proposed to MiFIR Transaction Reporting

    It may seem just like yesterday when the industry was grappling with the introduction of new regulatory reporting requirements following the introduction of MiFID II.

    However, following the publication of ESMA’s MiFID II Review in April, there will be further changes to MiFID II, including to the Transaction Reporting regime.  The idea of MiFID 2.1 was hard baked into the MiFID directive.  As with MiFID I, it was recognised that the significant changes MiFID II introduced would necessitate a finessing of the rules at a later stage.

    In April and May, Kaizen Reporting held three events to brief clients and the industry on ESMA’s final report and the changes it recommends on the Level 1 text i.e. both MiFID and MiFIR.

    Approximately 250 clients attended our series of webinars on the MiFID Review. We received a great deal of positive feedback on the sessions as well as questions from the audience which we have published below as an FAQ for the industry. 

    ESMA’s MiFID II Review – Frequently Asked Questions (FAQ)

    1. Changes to INTC

    Will the INTC be replaced by a new code to recognise a firm, what will that new code do?

    The aim of the new code is not to identify the investment firm that’s aggregating orders across multiple client accounts. It is to replace INTC (order aggregation account) with what is effectively a grouped order identifier code.

    So, this could eventually link the transaction reporting regime with the order record keeping regime which is immensely powerful from a market abuse monitoring perspective. It will be a code that is unique to the firm and can be any code the firm wishes to use but it does need to be unique over time to the aggregated order and the related market-side executions and client-side allocations.

    However, we believe it would be more useful for ESMA to retain the ‘INTC’ flag as it is and introduce a separate field/flag for the new code so that firms won’t have to make changes and it becomes more visible where INTC and grouping is taking place. We would suggest the new code to be the order ID of the grouped order which should already exist in firms’ systems for the aggregation of client orders.

    Regarding the order ID, will this help the regulator identify combined reporting scenarios where there are multiple fills with one underlying client?

    Where you have a single client and multiple fills for that one client, these multiple records cannot be linked by the reviewer because INTC is not used in that circumstance. That is another reason why having a separate field for the grouped order ID would be useful.

    For more insights on INTC changes, please read Complexity from simplicity – the INTC story.

    2. The SI approach for determining reportability

    If you are given an ISIN through confirmation of an FX derivative but are not facing the SI directly, would you deem that as non-reportable even if the ISIN then appears on FIRDS following the RTS 23 submission?

    Unfortunately, it is more nuanced than that. You must decide if the ISIN is TOTV. If you trade an FX derivative and that derivative is admitted to trading on a trading venue, then it would still be reportable as it is today. However, if it is only on FIRDS via the SI and you are not facing the SI directly then it will not be reportable. The same will apply to interest rate derivatives.

    Is there a database for firms to search and therefore identify if they are trading with an SI? In particular for FX and CFDs.

    There is an existing, market solution called SmartStream RDU. If an SI wants to partake, they submit their data to this mechanism but it’s not mandatory and so it does not provide 100% coverage although participation in the scheme is high. Going forward, ESMA is hoping to create such a database. ESMA wants to have a proper solution with universal and comprehensive look ups, covering all instruments.

    3. Removal of the short-selling flag

    As the Short Selling indicator is being dropped, will the FCA expect corrections of historic reports where they may have been wrong?

    The changes proposed by the MIFIR Review have been published by ESMA and so we are yet to see the FCA’s stance in this regard.

    There is a backwards compatibility question. Under EMIR, we had multiple iterations of validations being introduced and changes to EMIR reporting, however, there was no backward compatibility. So, if you were being asked to re-report a trade under EMIR you would have to comply with the latest reporting obligations which is the retrospective application of the rules.

    Therefore, with the MIFIR Review, we would recommend raising the importance of backwards compatibility with trade bodies, ESMA and the FCA so that firms aren’t asked to put any new flags on historical reports or to assess reportability based on the revised instrument scope.

    In respect of how the short selling flag stands today, the FCA will continue to expect that to be reported. There’s currently no change on the FCA’s stance on backwards reporting so they’re still asking for 100% of records to be replayed.

    4. Scope changes for UCITS and AIFMs

    Can you run through the scope changes applied to UCITS management companies and AIFMs – where these are entities within the same Firm group entity (and not outsourced). Will this mean they are brought into scope?

    AIFMs and UCITS management companies providing one or more MiFID services to third parties will be required to transaction report.  Activity in relation to their own AIFs and UCITS funds will remain out of scope but reporting activity falling under their MiFID and so called MiFID “top-up provisions” will become mandatory.  This activity is a gap in the current surveillance net which ESMA is looking to close by levelling the playing field with asset managers authorised under MiFID.  Where AIFMs and UCITS management companies are required to report, there remains the option for them to transmit their orders to another MiFID investment firm under an Article 4 transmission agreement which would remove the need for them to make separate transaction reports. 

    5. Consistency with other reporting regimes

    Do the proposed changes create any inconsistencies/misalignment with reporting expectations under other regulations such as EMIR?

    Despite some calls to do otherwise, we believe it is sensible that ESMA continues to focus its efforts on harmonising the MiFIR and EMIR reporting regimes, where possible, without attempting to fully replace one regime with the other.  Given the significant differences between the two regimes as to what constitutes a reportable event or valuable information that is captured by each regime, the use of consistent and international data standards, reportable values, formats and methodologies is where further efficiencies can be made. This will naturally reduce costs and also help to increase the accuracy of data being reported.

    Will the FCA follow ESMA on the changes resulting from the MiFIR Review?

    We think that the selection by ESMA of which proposals to move forward with and which ones to drop has been sensible. If there is going to be divergence we expect the FCA to consult with trade bodies and then more broadly with firms to ensure everyone has their say. The FCA will consider the views of firms dual-reporting in the UK and EU and their desire for harmonisation. They’ll also consider firms that solely report to the FCA that may want a lighter touch. We have to remember that the FCA was the main advocate of transaction reporting in the first place and now relies heavily on these reports. We think they’re likely to adopt the vast majority of these proposals. We have yet to see what level 2 changes will be proposed by ESMA.

    6. Implementation timeline

    What is the timeline for when these changes will go-live and how long will firms have to implement the changes?

    We know that these proposals still have to go to the European Commission for approval and then to the European Parliament. That will take some time. The EMIR Refit is also happening at the same time and we would like to see an alignment of timings for the EMIR Refit and the MiFIR Review.

    In addition, we expect more changes under Level 2 and in the detailed RTS. Realistically, it is therefore likely to be 2-3 years before these changes go-live, and could be up to 3-4 years, so we anticipate it being 2023 to 2024.

    In terms of timing of implementation, it is costly for firms to make these changes, so adequate implementation time is required and it will be up to firms and their representative trade bodies to request and lobby for adequate implementation time.

  • Latest CFTC reporting fine highlights the need for robust controls

    Latest CFTC reporting fine highlights the need for robust controls

    The recent announcement by the Commodity Futures Trading Commission (CFTC) that it had fined a tier one Swap Dealer $1.5m for failing to comply with swap data reporting obligations is a timely reminder of the importance of ensuring accuracy when reporting.

    A simple valid but wrong issue

    The issue related to valuation submissions where the firm submitted daily valuations for each open position but a “single issue within the reporting engine” resulted in the wrong mark-to-market value being populated for 91% of the equity swap positions.

    This is a very timely reminder of something I’ve been advocating for years and the team here at Kaizen are very passionate about. This is what we call the ‘valid but wrong’ problem. It’s not enough to get the submissions accepted into the SDR and call it job done. The data may have been validated but it doesn’t mean it is accurate. This is why it’s crucial that firms have robust controls to continually assess the integrity, completeness and accuracy of the data. Once it’s in the SDR it is regulated data and no longer your own.

    Sleepless nights

    The apparent simplicity of this issue – supposed to source from Field A but instead picked up Field B and both look like good valuations – will alarm many a reporting firm. Such a simple mistake in the original code or a defect that was introduced later but with very serious consequences. Aside from the fine there’s the costs of the investigation, the time spent discussing with the regulator, the adverse publicity and remediating 22 million records across several years’ submissions.

    Clearer standards means more scrutiny

    With the long awaited ReWrite due in May 2022 facilitating the CFTC’s stated mission of prescribing clearer standards to enforce better data quality then it goes without saying that improved standards will mean increased scrutiny. Replacing the current differences in reporting formats across different asset classes and the different SDRs will make it easier for the regulator to monitor and analyse the data. Better standards means higher expectations and less excuses. We’ve seen this before for example in Europe where the introduction of the EMIR Article 9 RTS revision in 2017 led to increasing levels of enforcement from the European authorities.

    Testing times

    Our advice remains simple. It’s all about the controls, and firms need to be testing their data now. Worst case scenario there is a specification that says source from Field B when it should be Field A. Nine times out of ten UAT testing is not going to find that before go-live because it’s to spec. Firms need to be assessing their data during the project phase, ongoing into production and continually from there on.

    The CFTC is on record since the 2015 ‘Request for Comment on Draft Technical Specifications for Certain Swap Data Elements’, that kickstarted the ReWrite of the DFA reporting rules, as saying that clearer standards will “assist the Commission in fulfilling its regulatory mandates”. After nearly nine years of struggling with inconsistent data formats I can see very little appetite within the Commission for accepting data quality issues when the new standards come into force next spring.

    At Kaizen we are already very focused on the CFTC ReWrite and SEC SBSR reporting and are committed to helping our clients meet these new obligations and report accurate data from the start. Contact us if you’re concerned your reporting might be valid but wrong or to discuss how we can help you get ready for these important changes.

  • ESMA updates its EMIR Q&A – delivery type for credit derivatives and reference rates

    ESMA updates its EMIR Q&A – delivery type for credit derivatives and reference rates

    Another month, and another new Q&A from ESMA clarifying some key points for us all.

    New TR Q&A 58

    This time we see the new TR Q&A 58 which focuses on how to populate field “Delivery Type” for credit derivatives in the case of a credit event auction. As ESMA notes, “auctions are organised, and counterparties may subscribe to it only once a given credit event occurs”. Now at the time of concluding the derivative, we won’t know whether the counterparties would participate in the auction, and if they do, they may subscribe individually. In summary, and thank you ESMA for providing some much required clarity as the credit derivative would be cash settled, and therefore their guidance here is to populate field “Delivery Type” with “C”. This includes where one or both counterparties subscribe to the credit event auction.

    TR Q&A 37

    For the first time in the EMIR Q&A, we now see a reference to FIRDS under TR Q&A 37 – Access to data by the competent authorities. By now we’re all familiar FIRDS under MiFIR, and this particular amendment provides clarity when the field “Underlying Type” is populated with X for Index, or B for Basket and the field “underlying identification type” is populated with either of these. This will allow the regulator where that ISIN is associated with and belonging to the component of that underlying basket, to have full access to that transaction data. This aids the regulator in trying to observe the counterparties they supervise as well as trying to view the potential build-up of systemic risk, the purpose of the regulation.

    TR Q&A 53

    We’ve also seen ESMA amend TR Q&A 53 – Reporting of reference rates not included in Regulation (EU) 2017/105.  ESMA confirms that the same approach as previously noted under TR Q&A 53(c) must be followed, and now provides the example where LIBOR is removed as the reference rate that counterparties should report a “modify” where the fallback reference rate is triggered. Moreover, ESMA also provides the guidance that the fallback rate will have a different ISIN. Field “Product Identification” should also be updated.

    All in all, some welcome guidance from ESMA given the evolving regulatory landscape.

    • To read the latest Q&A please visit ESMA’s website.
    • For a conversation about the latest Q&A or the quality of your EMIR reporting, please contact us.
     
  • MiFIR Transaction Reporting and the meaning of a ‘transaction’

    MiFIR Transaction Reporting and the meaning of a ‘transaction’

    Article 2 of RTS 22 outlines what does and does not constitute a ‘transaction’ for the purposes of transaction reporting under Article 26 of MiFIR.  What’s interesting is that only seven bullet points make up what is deemed a ‘transaction’ and therefore potentially reportable, whereas there are twice as many exclusions.

    It would be easy to assume that the shorter list is more important. However it should be remembered that not only does over-reporting constitute a rule breach, determining what must not be reported is where most of the complexity sits. 

    Many of the reporting problems we see in our quality assurance testing sit within the world of corporate actions and events. So the importance of documenting which actions and events are included and excluded from a firm’s reporting (including the rationale) cannot be over-stated.

    ESMA Q&A update

    ESMA has recently added to the list of examples of what does not constitute a reportable transaction by updating its MiFIR data reporting Questions and Answers (Q&A) document as part of its May 2021 publications. The key point to note is that “a voluntary switch to risk-free rates” is not transaction reportable under Article 26 as it would fall under the RTS 22 Article 2(5)(i) exemption. This means firms have some clarity around the impact of the decommissioning of LIBOR: there will not be a need to re-report LIBOR based swaps, including equity swaps that have a LIBOR component, as well as LIBOR-based interest rate swaps.

    This specific exemption covers the creation, expiration or redemption of a financial instrument as a result of pre-determined contractual terms, or as a result of mandatory events which are beyond the control of the investor where no investment decision by the investor takes place at the point in time of the creation, expiration or redemption of the financial instrument.

    All other minor changes to the Q&A also relate to section 18 which covers the ‘reporting of rates not included in RTS 22 and RTS 23’.

  • 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.
  • SMCR and Regulatory Reporting: Setting the ‘tone from the top’

    SMCR and Regulatory Reporting: Setting the ‘tone from the top’

    The FCA gave an interesting speech this Monday around compliance and the evolving regulatory landscape and expectations. It highlighted how the Senior Managers and Certification Regime (SMCR) has forced firms to allocate and align senior managers’ responsibilities to controls and oversight. This starts with setting the ‘tone from the top’ and making every person engaged and accountable to focus on the ‘tone from within’.

    Kaizen sees this on a daily basis. Through our Accuracy Testing and Advanced Reconciliation services, we detect errors and data quality issues. The key question for consideration is whether regulatory reports are being signed off by senior managers under the SMR in the belief that they are accurate or inaccurate with remediation work to fix the problems.

    “The focus on points of failure not only encourages greater awareness, it also promotes better calculations of judgement.” Mark Steward, Executive Director of Enforcement and Market Oversight, FCA

    Valid but wrong

    Kaizen’s quality assurance testing identifies errors and ‘valid but wrong’ scenarios. This supports senior managers in their role and provides them with a level of independent evaluation across their whole dataset instilling confidence in the sign off process, as well as certification that their firm is compliant with their regulatory reporting obligations.

    Highlights of the speech:

    • SMR changes the way firms allocate responsibilities
    • Five Conduct Questions (5CQ), ‘tone from the top’, all persons are personally accountable
    • Every employee is subject to conduct rules
    • SMR & 5QC requires firms to understand the risk of non-compliance
    • Failures are not necessarily due to compliance but consequences of choices.
    • For a virtual discussion of your own with Chris or with one of our regulatory reporting specialists, please contact us.
    • To read the speech in full please visit the FCA’s website.
  • Solving the EMIR Reporting data quality problem 

    Solving the EMIR Reporting data quality problem 

    SFTR insights provided by Jonathan Lee

    Data quality – the two words that are perhaps most likely to annoy ESMA and the NCAs when associated with EMIR reporting. We all know that EMIR reporting data quality has been poor for some time – in fact, since the regime was introduced.  Our testing results confirm this is the case.  So what did the first EMIR and SFTR Data Quality Report (DQR) released by ESMA last week, tell us?  Well to be honest, not a huge amount we didn’t already know.  But for a regime now seven years old, the statistics make for some grim reading for regulators and firms alike.

    What’s the background to the report?

    Since September 2014, the Data Quality Action Plan (DQAP) has been in place between the NCAs and ESMA to try to improve the quality of the data. Part of the plan requires NCAs to perform a quantitative assessment of the data reported by counterparties in their Member State.  This is known as the Data Quality Review (DQR) and has enabled the NCAs to compare specific data of their own supervised counterparties, with the data of other counterparties based in other E.U. Member States. ESMA produced an NCA peer review in 2019 into this process across six regulators with a mixed review of their assessment.  The FCA in particular came under criticism from ESMA as not being proactive enough.  It is worth noting that due to Brexit, a lack of data sharing between the FCA and ESMA/EU NCAs will change future peer reviews. 

    Pairing and matching rates

    Pairing and matching rates have been low since EMIR’s inception in 2014. But what is interesting is that ESMA didn’t even publish matching rates in the DQR.  Its most recent published figures had matching rates at 29% so we have to assume it has the data  – why not include it?  The DQR puts pairing rates at 53% which is slightly lower than the 59% it has previously quoted. Does that mean data quality is going down, not up? Regardless, pairing rates should be a lot higher given that counterparties still only have to agree three fields[1] to pair.

    So what does this suggest?

    Confusion and communication issues between counterparties still exist when trying to meet their ongoing T+1 reporting obligation. ESMA also emphasises this view and that this further boils down to firms not reporting at all (!), not reporting in a timely, complete and accurate manner, as well as disagreements about the Unique Trade Identifier (still!).  Some other key components from the report are mentioned below:

    • Based on early 2021 data, around 7% of daily submissions are being reported late by counterparties;
    • Up to 11 million of open derivatives did not receive daily valuation updates;
    • According to ESMA estimates, there tend to be between 3.2 and 3.7 million of open non-reported derivatives on a given reference date during 2020.

    What needs to happen for EMIR data quality to improve?

    1. More guidance to improve understanding of the obligations

    Greater clarity needs to be provided by the regulators specific to the data fields. The trade bodies put together Best Practice Guidance for firms on how to populate fields last year.  We applauded this at the time and would also welcome further initiatives from regulators, especially where confusion still exists between Regulatory Technical Standards/Implementing Technical Standards and the ESMA Q&A. One example where we see consistent confusion amongst firms is the use ‘Broker ID’ field.

    1. Better communication within firms

    Firms already have a packed working day in order to meet their existing obligations, but the fact that ESMA are drawing out issues over the UTI and not reporting at all provides concern. If there are ongoing issues, appropriate and documented escalation should be occurring within firms and where appropriate, if material issues are arising, escalation to your supervisory team at your NCA.

    What will happen if things don’t improve?

    Ultimately we could still see more fines being levied on firms for their EMIR reporting.  The main reason why firms get fined is due to ‘Management and Control’ related issues. This is especially prominent in any EMIR and MiFID fine we see. Kaizen can very much assist on this matter and identify why your reporting isn’t accurate, complete or provided in a timely manner. Once your reported data has been tested, we then provide you with several different data quality reports which can be used to present to your senior management/committees.

    What about SFTR?

    ESMA has been keen from the outset to bring SFTR governance, oversight and controls in line with EMIR reporting. To this end, SFTR is included in the 2020 DQR for the first time. At this stage, it is a rather token inclusion given the July 2020, October 2020 and January 2021 go-live dates for sell-side and market infrastructures, buy-side and non-financial counterparties respectively.

    The report plots the growth in open SFTRs, with the subsequent decline in January 2021 as the UK drops post-Brexit. ESMA also plots the lion’s share of open SFTs being securities lending & borrowing transactions (with repos coming a distant second) and where investment firms and credit institutions continue to report the majority of SFTs.

    In this first report, there is limited feedback on SFTR data quality given the lack of maturity of the regime. Comments and a chart are used to demonstrate the decline in rejection rates during the regime’s short life. At Kaizen, we would caution that trade repository rejection rates alone are a very poor measure of data quality. SFTR is a new, complex and challenging regulatory reporting regime in which our regulatory testing routinely flags a multitude of valid but wrong reports.   

    If your EMIR or SFTR reporting isn’t up to best practice or if you’re unsure of its quality, we can help. Please get in touch for a conversation with one of our regulatory specialists to discuss your reporting challenges.

    Our EMIR and SFTR reporting core training courses also cover all aspects of the reporting requirements to gain an excellent overall understanding of the scope, drivers, trading scenarios and key fields that make up an EMIR and SFTR report. Book your place now.

     

     

     

    [1] Reporting counterparty ID’, ‘ID of the other counterparty’, and ‘Trade ID’

     

     

 
  • Significant changes proposed to MiFIR Transaction Reporting by ESMA

    Significant changes proposed to MiFIR Transaction Reporting by ESMA

    It may seem just like yesterday when we were all grappling with the sweeping changes being brought by the introduction of MiFID II. But we all need to brace ourselves for the further changes that ESMA’s review of the MiFID II Transaction Reporting regime will bring.  The idea of MiFID 2.1 was hard baked into the MiFID directive.  As with MiFID I, it was recognised that the significant changes MiFID II introduced would necessitate a finessing of the rules. 

    ESMA’s review, partly delayed by both Brexit and Covid-19, has now delivered its final report on the changes it recommends on the Level 1 text i.e. both MiFID and MiFIR.  

    The revised reporting rules stemming from this review are expected to be finalised in a couple of years following the completion of the review of the Level 1 text and after more detailed industry consultation and approval by the EU Commission.

    ESMA’s key decisions around which proposals to pursue further and which ones to drop seem sensible at first glance and it seems that detailed consideration of responses to the consultation process has been made. That said, there are some potential missed opportunities too. 

    Here are some of the key changes being proposed or dropped:

    Which firms will need to report for the first time?

    Alternative Investment Fund Managers (AIFMs) and UCITS management companies providing one or more MiFID services to third parties will be required to transaction report this activity.  Under the proposed changes, activity in relation to their own Alternative Investment Funds and UCITS funds will remain out of scope for reporting but reporting activity falling under so-called MiFID top-up provisions will become mandatory. 

    This activity is a gap in the current surveillance net which ESMA is looking to close.  Where AIFMs and UCITS management companies are required to report, there remains the option for them to transmit their orders to another MiFID investment firm under an Article 4 transmission agreement which would remove the need for separate transaction reports to be made. 

    ESMA had originally proposed to make it an obligation for the receiving investment firm to report the transaction which pertains to a transmitted order, when the transmitting investment firm requests to transmit its orders.  However, this proposal has been dropped.

    What are the changes in reporting scope?

    One of the aims of MiFID II was to extend the reporting obligation to cover FX, interest rate and commodity instruments that had been subject to manipulation and abuse. Increased transparency in this area was seen as being vital to ensure the cleanliness and orderliness of the markets in which these instruments were traded. 

    It was expected that the majority of trading activity would be driven onto venues and would therefore be captured by the “Traded on a Trading Venue” (ToTV) obligation.  This then led to an extension of this concept to capture instruments that had commonalities to ToTV instruments leading to the need for lookups to ANNA DSB as well as FIRDS to establish reportability.  In reality this is a difficult and expensive process so one proposal is to replace the ToTV commonalities concept with the “SI approach”. Under this approach, derivative instruments that are exclusively traded through SI systems and all derivatives belonging to the same sub-asset class would have to be reported under Articles 26 and 27 of MiFIR and made transparent. 

    This extension to scope would only be applicable to SIs and their counterparties. It would not be applied to non-SI firms trading against each other in the same instruments nor interestingly, would it apply to any DEAL trades with underlying clients carried out by the non-SI counterparties.

    The idea is that this proposal will succeed in giving a more complete view of the market whilst simplifying some of the existing reporting complexities. We can see a few challenges and issues with this proposal however, which we will cover in more detail in a future blog.

    What changes are being proposed to the data content?

    Two new additional data elements are being added to the transaction reports. These are:

    • A buy back programme (BBP) flag
    • MiFID client categorisation flag

    The BBP disclosure obligations are seen as been overly burdensome across the industry.  So including a flag in the transaction report may enable the obligation under Article 5(3) of MAR to be removed and could also facilitate a more efficient approach to monitoring compliance with this ‘safe harbour’ within MAR.  

    The MiFID client categorisation flag is being proposed to allow NCAs to monitor the distribution of certain complex products to investors or identify market trends when analysing the data on transaction reporting. 

    These changes would be consistent with the idea of improving the efficacy and efficiency of overall data provision by firms but it also means that the accuracy and completeness of the transaction reports becomes even more vital for regulators.

    It is not surprising to see the regulators looking to utilise transaction reports for the monitoring of suitability and other areas beyond market abuse.  This is consistent with ESMA’s data strategy which involves using data more efficiently to minimise the number of separate data requests submitted to firms. 

    INTC changes

    Where orders are aggregated across multiple clients a pseudo account “INTC” is used to provide linkages between the market-side fills and the allocations to the clients.  The proposed change is to require firms to use a code unique to the reporting firm instead of the simple character set “INTC”.

    This change will certainly make the data more meaningful to the regulators but will also help firms internally when analysing their transaction reports.  The use of INTC and the specific rules around its use represent one of the most difficult aspects of transaction reporting.  As grouping of client orders prior to execution is typical of asset and wealth management firms, this change will lead to significant new challenges for these firms and their system providers.

    My view is that it would be preferable to keep the status quo in terms of how systems are coded to handle the reporting of the INTC account but introduce a separate field to hold what is effectively a grouped order ID. Such a field would also be useful in allowing all transaction reports related to a single order to be grouped together.  This transparency is often very helpful when analysing trading activity and is a missed opportunity as it would involve fewer coding changes and would provide a link between the transaction reports and the orders maintained under the order record-keeping requirements. 

    What’s going?

    The short selling indicator.  One of the most frequently misreported fields is to be removed. This will certainly be welcomed by firms not least because we now have divergent requirements between the FCA and EU reporting rules.  However, the need for regulators to have transparency of short selling activity seems to be greater than ever given the real possibility of short selling squeezes being coordinated through social media.

    Going forward

    As all firms know, applying corrections to historic transaction reports is mandatory under RTS 22 Article 15.  Any proposals to change reporting obligations should consider and deal with the question of backward compatibility.  To require back reports to be made under new reporting requirements is effectively the retrospective application of the regulations.  So, to avoid this, any proposals for change should include provisions to deal with any such back reporting so that replay records would not need to implement the new flags or the replacement INTC code. 

    From an implementation perspective, it would be best if the timing of implementation of these changes is aligned with any transaction reporting changes proposed by the FCA.  We believe a lot of the proposed changes will be welcomed by the FCA and we would support consistency of reporting across regulations which reduces costs and increases data accuracy. 

    Our verdict?

    These are just the level 1 changes.  Most of the action takes place at level 2 and 3 in the delegated regulations, guidelines and Q&As.  There are a whole slew of areas where improvements can be made here and we look forward to ESMA’s proposals.  

    Whatever the outcome, ESMA recognises the need to have better quality data and to ensure it meets the needs of 21st century regulation.  This is just the second step in that journey. 

    • Kaizen exists to help improve the quality of regulatory reporting data.  For a conversation about ESMA’s proposed changes to MiFIR transaction reporting or any transaction reporting challenges, please get in touch.

    • To read ESMA’s Final Report please visit their website.
  • ESMA plays catch-up on Issuer LEIs as the deadline passes

    ESMA plays catch-up on Issuer LEIs as the deadline passes

    Maintain the status quo

    ESMA has finally published a statement to clarify how SFTR reporting firms should treat the end of the initial deadline for populating issuer LEIs for third country issuers. They have extended the deadline and require all issuer LEIs to be reported where they exist but will continue to permit reports without issuer LEIs for third country issuers until 10 October 2022. They advise market participants that this is the latest date by which firms will be permitted to report without issuer LEIs, while also committing to updating their position on issuer LEIs in advance of 10 October 2022:

    “Considering the still unsatisfactory level of LEI coverage on a global scale…ESMA expects competent authorities to continue not prioritising their supervisory actions in relation to reporting of LEIs of third-country issuers.”

    This announcement indicates another slight divergence from the UK FCA, where the exemption has been extended until 13 April 2022 at the earliest. Again in practical terms, the UK and EU are now fully aligned; an issuer LEI is required where available in third countries but can be reported without where it does not yet exist.

    Kaizen is always on hand to assist firms in ensuring compliance with this complex and evolving regulation. Please get in touch to discuss any SFTR reporting challenges or to find out more about how our multi-award winning ReportShield™ quality assurance testing can get your reporting accurate and complete.

  • New SFTR Q&A: Question 9 – Portfolio Manager Reporting

    New SFTR Q&A: Question 9 – Portfolio Manager Reporting

    ESMA have updated the SFTR Q&As to add Question 9: “Reporting of SFTs where an external portfolio manager participates.” This does clarify the requirement but this isn’t necessarily the helpful guidance the industry was looking for.  This means that unfortunately the challenges for the funds industry will persist.

    In Part a) How should a portfolio manager be identified in an SFT report? The short answer is that they should not be identified unless formally performing a role as an agent lender or broker. Therefore, the trade repository reconciliation process remains very tricky where trades cannot readily be associated with a particular fund manager.

    In Part b) In order to report estimated collateral reuse or cash reinvestment where a fund executes SFTs with several counterparties, those counterparties have a responsibility to provide the report submitting entity with relevant details to enable them to report. This includes the obligation for the reporting counterparty or report submitting entity to either calculate estimated reuse themselves, or provide the relevant details to the party taking delegated responsibility for performing the calculation.

    Finally, Part c) Asks how variation margining on a net exposure basis should be reported when a financial counterparty or entity responsible for reporting uses multiple portfolio managers. In addition to this consideration for bilateral margining, they also raise the same issue in relation to triparty securities lending, also collateralised at the net exposure level. Again, the responsibility falls upon the reporting counterparty or report submitting entity to either perform relevant calculations themselves or provide necessary details to the party to whom it has been delegated to.     

    At Kaizen, we are committed to helping reporting counterparties improve the quality of their SFTR reporting and ensure compliance with the regulation. Where the guidelines and Q&A still lack clarity, we can assist reporting parties through our ReportShield Accuracy Testing and Advanced Reconciliations to ensure that these obligations are met.

    We eagerly await the ESMA response to the impending deadline for reporting third-country issuer LEIs, where the current exemption is due to end on 13 April 2021. 

  • ESMA EMIR Q&A – Intragroup reporting exemption updates (plus some added UK EMIR guidance too)

    ESMA EMIR Q&A – Intragroup reporting exemption updates (plus some added UK EMIR guidance too)

    You know the saying when you’re waiting ages for a bus, then three come along all at once? Well, that’s how it feels with the recent EU EMIR and UK EMIR validation updates, and then last week ESMA published an update to its EMIR Q&A.

    The updated TR Q 51 provides further clarifications on the intragroup transactions (IGT) reporting exemptions, specifically on the following:

    • Reporting of details of derivatives when the IGT reporting exemption ceases to be valid; and
    • Location of parent undertaking for purposes of the IGT reporting exemption.

    So what exactly are the updates?

    Any form of legislation can be quite confusing as it tells you to cross-refer to this, that and all manner of documents in order to get to the final conclusion, and this isn’t any different here. The latest round of updates to the EMIR Q&A points the reader to take into account EMIR REFIT, but we’ve gone slightly deeper and also looked at the impact under UK EMIR REFIT too.

    ESMA EMIR TR Q 51 (I)

    “Once the reporting exemption ceased to be valid due to a change in any of the conditions, referred to in the third sub-paragraph of Article 9(1) EMIR, as amended by Regulation 2019/834 (EMIR REFIT), what actions should the concerned counterparties undertake with regards to the derivatives that are outstanding? “

    TR A 51 (I)

    “The counterparties concerned should report the outstanding derivatives with Action type “N = New” and provide all the relevant details of those derivatives as they stand on the date when the exemption ceases to be valid, and report all subsequent lifecycle events as they occur. It is not necessary to report the modifications to the derivative that occurred between the date of conclusion of that derivative and the date when the exemption ceased to be valid. If the outstanding derivatives were previously cancelled with Action type “E = Error” at the moment when the exemption was granted, the counterparties should report such derivatives with a new UTI so that the reports are not rejected in accordance with the EMIR validation rules”

    As a footnote to the above, ESMA provides the following guidance too here “Validation for the field 2.93 Action type: “Only one report with the action type “New” for a given combination of Counterparty ID – ID of the other counterparty-Trade ID shall be accepted”.

    Some important points

    EMIR REFIT (and also UK EMIR REFIT*) made updates to the original Article 9(1) of EMIR, specifically for IGT:

    • Reporting obligation shall not apply to derivative contracts within the same group where one of the counterparties is a non-financial counterparty or would be qualified as non-financial counterparty if it were established in the Union, and provided that:
    • both counterparties are included in the same consolidation on a full basis; and
    • both counterparties are subject to appropriate centralised risk evaluation, measurement and control procedures;
    • the parent undertaking is not financial counterparty.

    EU EMIR REFIT

    Any counterparties meeting the above criteria and wishing to apply for the exemption shall notify their regulator. The exemption shall be valid unless the regulator doesn’t agree that all the relevant criteria has been met within the three months from the notification being made.

    UK EMIR REFIT

    An interesting point under UK EMIR REFIT is the timing that that exemption will apply from. Under UK EMIR REFIT, we note that if the FCA provides no objection, that the exemption will be valid from the end of the three-month period after the notification has been made.

    As an additional point, and for further guidance, once the FCA provides notification of exemption, the counterparties “…should send reports with Action type “E = Error” for all open derivative contracts with the counterparties for which the reporting exemption is valid.”

    *Under UK EMIR REFIT the same conditions as per EU EMIR REFIT have to be met, but the first bullet point is amended as follows:

    • “any intragroup transaction where at least one counterparty is a non-financial counterparty (or would be qualified as a non-financial counterparty if it were established in the UK).”

    Further guidance on notifications and exemptions under UK EMIR can be found on the FCA’s website.

    ESMA EMIR TR Q 51 (M)

    “In the case of derivatives contracts where at least one of the counterparties is a non-financial counterparty: does the exemption of reporting obligation for intra-group transactions introduced in Article 9(1) of EMIR REFIT apply when the parent undertaking is established in a third country?”

    ESMA EMIR TR Q 51 (M) Answer provided by the European Commission in accordance with article 16b(5) of the ESMA Regulation*

    “The exemption contained in Article 9(1) of EMIR does not cover intragroup transactions for which the parent undertaking is established in a third country, even if the transaction occurs between two counterparties which are both established in the EU. This conclusion is based on the following elements:

    1. The definition of parent undertaking refers to an undertaking governed by the law of a Member State and nothing in EMIR indicates a will to modify that reference.
    2. This interpretation fits the actual purpose of Article 13 of EMIR: deference is granted where there is equivalence with the jurisdiction hosting the parent undertaking.
    3. This interpretation ensures a meaningful use and purpose of the transparency objective of Article 9 while limiting the exemption in article 9(1) to the minimum necessary.”

    What else does this mean?

    In summary, and in keeping with the spirit that EU EMIR applies to EU counterparties (as UK EMIR applies to UK counterparties). Moreover, Article 13 of EMIR and as referenced above, requires ESMA to assist the European Commission in monitoring and preparing reports to the European Parliament and to the Council on the international application of principles in a number of articles, including the reporting obligation under Article 9 of EU EMIR. Therefore the reporting exemption here wouldn’t apply where the parent undertaking is located in a third country such as the UK.

    What do ESMA Q&As mean for UK counterparties?

    For those of you that missed the FCA’s statement from 2020, documents such as ESMA’s Questions and Answer documents (also known as non-legislative material) were not incorporated into UK law. However, the FCA broadly went on to say that firms providing services in the UK should adhere to these as appropriate.

    The FCA’s document entitled Brexit: Our approach to E.U and non-legislative materials can be found on its website.

    • Kaizen provides comprehensive quality assurance testing for firms reporting under both UK and EU EMIR.  We don’t do sample or scenario testing – we test all reported data to give you a full picture of the quality of your reporting, allowing you to evidence where you are right and identify where you are wrong.  For a conversation with one of our regulatory experts about your reporting challenges, please contact us.

    • To read the latest EMIR Q&A please visit ESMA’s website.
  • The Kaizen Helpdesk one year on

    The Kaizen Helpdesk one year on

    A year ago, at the start of the pandemic, we launched the Kaizen Helpdesk to provide our clients with direct access to our team of regulatory specialists and test analysts. Our goal was to improve support and enable clients to raise any questions about their ReportShield™ testing and reconciliation results while many were working remotely from home. 

    What is the Kaizen Helpdesk?

    The Kaizen Helpdesk provides an instant way to communicate with our team of specialists either for technical queries relating to the regulation itself, or for data issues with your ReportShield Accuracy Testing and Reconciliation results. When submitting an enquiry, clients can highlight the exact service and regulation their question relates to, ensuring it reaches the correct recipients immediately. Clients can also attach documents, spreadsheets, emails and screenshots directly into the comment box for the Kaizen team to review.

    Any question can be submitted to the Helpdesk and it’s designed to encourage:

    • Efficiency – direct access to the entire team of Regulatory Specialists, Data Analysts and Relationship Managers, avoiding your message being lost in crowded inboxes or receiving an Out Of Office reply
    • Transparency – your request will be shared with your fellow colleagues with Helpdesk access
    • Auditability – requests are never archived and don’t disappear if the user leaves the organisation
    • Traceability – to prevent duplication of Q&A and provide evidence of decisions made
    • Tracking  – of changes to client’s business and data discovery profiles or Kaizen’s test parameters.

    How long will it take to process my enquiry?

    The Helpdesk is monitored by our team of regulatory specialists, relationship managers and support functions to ensure that queries are dealt with as quickly as possible. We aim to respond to clients and resolve enquiries within 24 hours.  If you need urgent assistance, please contact your Relationship Manager or support contact quoting your Kaizen Helpdesk reference and they’ll assist with escalating your enquiry.

    Future Plans

    We have received great feedback on the Kaizen Helpdesk over the past year and the number of clients using the service continues to grow.  As a result, we have been gathering feedback to design and launch a new, improved Helpdesk which is currently in testing. Watch this space for further announcements on the new Helpdesk service with additional functionality in due course.

    • As always, if you have any suggestions or feedback on how we can improve any of our services, including the Helpdesk, please contact us. And keep raising those questions…
    • If you’re not a client and would like more information about our ReportShield services and how you can access our Helpdesk, please also get in touch! 
  • FCA updates recent UK EMIR validation rules

    FCA updates recent UK EMIR validation rules

    **IMPORTANT UPDATE 29 March 2021**

    On 29 March ESMA published the exact same amendments, but an important point to note is ESMA’s update to the EU EMIR validations are effective from 30 April, 2021. The FCA’s effective from date on these changes to the UK EMIR validations rules still remain as the 21 June 2021.**

    The FCA has made a minor amendment to the EMIR validation rules that went live earlier this month.  The amendment applies from 21 June.

    In a statement at the end of last week, the FCA said:  “On 18 March 2021, we published an update to the UK EMIR validation rules. Following the go-live of the last update to the Validation Rules on 8 March 2021, we were made aware of an issue relating to the instructions under field 1.30 (XXXX). This update reflects the amendment to the instructions in that field only which will apply from 21 June 2021.”

    So what does this mean?

    Field 1.30 – Variation Margin received – The FCA removed the following reference “If field 1.21 is populated with “U”, this field shall be left blank.”

    This is all makes sense as if you’re marking Field 1.21 Collateralisation as Uncollateralised, then Variation margin will definitely not be posted. This also aligns with the previously issued Regulatory Technical Standards issued at a European Level, and also with the industry best practice issued by the trade associations. 

    So what next?

    Kaizen provides quality assurance services across a number of regulatory regimes including the UK and EU versions of EMIR, and populating any of the margin fields where a firm marked field 1.21 as Uncollateralised would’ve definitely raised a flag in our testing results.  We provide a completely independent and comprehensive review of the quality of your reporting through our Accuracy Testing and Advanced Regulatory Reconciliations so you can be sure you are meeting regulatory requirements for accurate and complete reporting.

    • For a conversation on how Kaizen can help you to meet your obligations for the UK EMIR and EU EMIR regimes, please contact us.
     
  • Lies, LEIs and SFTR Reports

    Lies, LEIs and SFTR Reports

    Tuesday 13 April should be crunch time for the removal of the 12-month waiver for the need to report issuer Legal Entity Identifiers (LEIs) for collateral or loaned securities issued outside the EU. However sometimes regulator desires are incompatible with the reporting realities. According to the study conducted by the joint trade associations (ISLA, ICMA, Amafi and AFME) and forming part of a joint letter to ESMA and national competent authorities (NCAs), there are at least 37,207 outstanding ISINs that don’t have issuer LEIs, of which 36,505 were issued outside the EU. This is prevalent in two of the world’s biggest securities markets, the USA and Japan…

    Trade Associations request guidance

    The trade associations have requested guidance from ESMA and NCAs about how to proceed, as the prospect of “No LEI, No Trade” really isn’t viable given the scale of the issue. It also reflects the fact that by merely being a holder of a security without an LEI as opposed to facing a counterparty without an LEI  gives you very little leverage to coerce the issuer into getting one.

    The guidance requested by the trade associations focused on two options, either the use of a dummy LEI where none exists or maintain the status quo of leaving the LEI blank. We await feedback from ESMA and NCAs as to the preferred approach to take but would caution adopting any changes even at this late stage.

    What is the best approach?

    During trade association meetings trade repositories have shared that they have not yet been advised to prepare for any changes in the validation rules regarding either of the issuer LEI fields to date. In practical terms, this means that if you continue to report issuer LEIs only where they exist (you should have controls in place to ensure you always report them where they exist), then your reports will continue to be accepted into the trade repository, even where the LEI is blank.  Until we hear words to the contrary, this would seem the best approach with full disclosure in the spirit of the regulation and neither misreporting (such as dummy LEIs) or underreporting (omitting the securities completely).

    • We are here to help if you have concerns about the quality of your SFTR reporting, with training, accuracy testing and advanced reconciliations available to ensure that you are compliant and remain so, as the regulation evolves. Please contact us to speak to Jonathan or one of our SFTR specialists about your challenges and how we can help.

    • Jonathan is speaking on the issues above in “SFTR Implications” at the FOW Buy-Side Repo and Regulatory Forum at 11.50am GMT on 24 March. Registration is free for market participants. Find out more and register here. 
  • What does March 8 mean for UK EMIR and EU EMIR – and for you?

    What does March 8 mean for UK EMIR and EU EMIR – and for you?

    With the Brexit transition period behind us, the path forward for regulatory reporting is now moving at pace for both UK EMIR and EU EMIR. Following ESMA’s statement on changes to the EMIR validation rules in September last year, we were originally due to see these implemented on 1 February. However this was pushed back to 8 March because the industry felt they didn’t have enough time to implement these updates because of the Brexit changes that were also fast approaching.

    Couple this with the new UK EMIR validations and the requirements from the FCA’s EMIR Statement in late 2020, and we find ourselves asking what does this all mean for UK EMIR and EU EMIR ahead of 8 March implementation…

    So what happens on 8 March?

    Apart from being International Women’s Day, it’s also an important day for EMIR Reporting. 

    On the regulatory reporting front, the trade repositories will implement these new validations to ensure that reporting is performed in line with the respective EMIR regime, and will reject reports received that are not in line with these requirements. This is why firms should ensure that they comply with not only with these validations, but also their ongoing obligations under both UK EMIR and EU EMIR.

    Below, we provide a summary of the key changes:

    Clearing obligation – Field 2.34: Both EMIR and UK EMIR

    UK EMIR

    • For trades concluded after 31 December 2020 and the field 2.15 (venue of execution) is not populated with a Market Identifier Code (MIC) that was a UK regulated, or a third country market considered equivalent to a UK market at the time of conclusion, the field shall be populated and contain only a “Y” or “N”.

    • Trades concluded prior to 31 December 2020 (while we were all in transitional pre-Brexit phase), and the Field 2.15 was not populated with a MIC code for a trading venue that was a UK or EEA regulated market, or a third-country market which was considered as equivalent to an EEA market at the time of conclusion – the field shall be populated and shall contain only one of the following values “Y” or “N”.

    Now this is interesting for EU firms in particular as our sometimes forgotten EMIR amendment (hidden away as an EMIR amendment within SFTR….Article 2(A)) made third country trading venues where Exchange Traded Derivatives (ETDs) are traded as Over The Counter (OTC) contracts, until (if) equivalence is received, which impacts the UK trading venue.

    EU EMIR 

    • ‘If Field 2.15 (Venue of Execution) is not populated with a MIC code of a trading venue that was a regulated market or of a third-country market considered as equivalent to a regulated market at the time of conclusion, this field shall be populated and shall contain one of the following values “Y” or “N”.

    Given the language here, we can work on the basis that the reference to UK regulated markets refers to those which were in scope at the time. However, and as noted in ESMA’s statement from 10 November 2020, UK counterparties are not expected to report to EU trade repositories any derivative concluded prior to 31 December 2020 that was rejected as of 31 December 2020, nor to report amendments to any derivative concluded prior to 31 December 2020.

    Intragroup Field 2.38 – Both EMIR and UK EMIR

    • EU EMIR – If Field 2.15 (Venue of Execution) is not populated with a MIC code of a trading venue that was a regulated market or of a third-country market considered as equivalent to a regulated market at the time of the conclusion, this field shall be populated and shall contain only one of the following values: “Y” or “N”.
    • UK EMIR – If the trade was concluded after 11pm on 31 December 2020 and Field 2.15 (Venue of Execution) is not populated with a MIC code of a trading venue that was a UK regulated market or a third-country market considered as equivalent to a UK regulated market at the time of the conclusion of the derivative, this field shall be populated and shall contain only one of the following values “Y” or “N”.
    • BOTH – If the trade was concluded prior to 11pm on 31 December 2020 and field 2.15 is not populated with a MIC code of a trading venue that was a UK or EEA regulated market or a third-country market which was considered as equivalent to an EEA market at the time the trade was concluded, this field shall be populated and shall contain only one of the following values “Y” or “N”.

    Once again, as per our comments above, these provide for some interesting implications given the definition of regulated markets under each reporting regime and specific timings around these dates.

    Timestamps – both EMIR and UK EMIR

    Both regimes introduce validations to the historical timestamps, which should have very little impact on reporting firms. The key aspects are as follows:

    • Reporting timestamp (Field 1.1) – the reporting timestamp should be equal or later than the execution timestamp reported in the field 2.25. The reporting timestamp under both regimes should now be equal to or later than 12 February 2014.
    • Valuation Timestamp (Field 1.19); Maturity date (Field 2.27); Maturity date of the underlying (Field 2.82) –  All these fields under both reporting regimes should be should be equal or later than 12 February 2014.

    Initial and Variation Margin fields – Both EMIR and UK EMIR

    EMIR has taken a leaf out of Kaizen’s book and turned some of our tests into validations! We see these kind of errors quite frequently so if you have not fixed them yet, it’s best to act quickly to avoid getting rejections.

    EMIR and UK EMIR Field 1.24 Initial Margin posted – this was previously Optional for Action type “V” and the change impacts both reporting regimes:

    • If Field 1.21 (Collaterisation) is populated with One-way collateralized (“OC”) or Fully Collateralised (“FC”), field 1.24 shall be populated
    • If Field 1.21 is populated with Uncollateralised (“U”) or Partially Collateralised (“PC”), then field 1.24 shall be left blank

    EMIR and UK EMIR Field 1.28 Initial Margin received – this was previously Optional for Action type “V” and the change impacts both reporting regimes:

    • If Field 1.21 (Collaterisation) is populated with Fully Collateralised, then this field shall be populated.
    • If Field 1.21 is populated with “OC” then field this field shall be left blank.

    EMIR and UK EMIR Field 1.26  Variation Margin Posted – this was previously Optional for Action type “V” and the change impacts both reporting regimes:

    • If Field 1.21 (Collateralisation is populated with Partially Collaterarised (“PC”), “OC” or “FC”), one of the fields 1.26 or 1.30 shall be populated (with a positive value or zero) while the other field shall be left blank or populated with zero.
    • If Field 1.21 is populated with “U” or “PC”, this field shall be left blank.

    EMIR and UK EMIR Field 1.30 Variation margin received – this was previously Optional for Action type “V” and the change impacts both reporting regimes:

    • If Field 1.21 is populated with “PC”, “OC” or “FC”, one of the fields 1.26 or 1.30 shall be populated (with a positive value or zero) while the other field shall be left blank or populated with zero.

    • If Field 1.21 is populated with “U”, this field shall be left blank.

    UK EMIR – don’t forget…

    The FCA has conveniently highlighted in yellow certain conditions that will apply to the UK regime to a number of fields. These include references to particular UK legislation and UK markets.

    So what now?  And what should you be doing…?

    Make sure that your systems are prepared for the updated validations. Reports will be rejected from 8 March unless they comply with the new regimes. 

    And remember – while you’re updating your systems – a report passing trade repository validations doesn’t mean it’s correct!  Kaizen has tested over 100 million EMIR records across the industry and we’ve found over 390 million errors across these reports. Moreover, 42% of those passed trade repository validation, but had at least one query. Firms are expected to submit complete and accurate reports – just passing validation is not enough.

    Update 18 March:  The FCA published a minor amendment to the rules on 18 March – read our blog on this change.

    • For a discussion on how Kaizen can assist you with the two separate EMIR regimes, please contact us.
    • Your regulatory reporting has passed validation. But is the data in it correct?  Find out more.
  • New iteration of the ESMA EMIR Q&A

    New iteration of the ESMA EMIR Q&A

    The latest EMIR Q&A contains two elements impacting trade reporting. Firstly, there’s clear advice on how to populate the buy/sell indicator in position level reports and then there is altogether more confusing text defining how to delete trades where a counterparty “ceases to exist”.

    Populating the buy/sell indicator at position level

    There is a small amendment in TR Q&A 3b which provides a clarification on the population of the buy/sell indicator on a position level report when the position is reduced to zero.  If a firm reported a ‘sell’ at a trade level which resulted in the position being reduced to zero, then the firm would populate the buy/sell indicator on the position level report with ‘S’ for sell. As this appears entirely logical, I hope that this doesn’t constitute a change for many firms.

    Procedure for terminating ‘dead trades’ by Trade Repositories (TRs)

    ESMA has included an entirely new question, TR Q&A 57, defining a procedure for the termination of ‘dead’ trades by TRs. Whilst this requirement is largely aimed at the TRs, there is some responsibility on firms as well.

    By ‘dead trades’, ESMA means trades that have been reported to a TR, but where one of the counterparties has subsequently “ceased to exist”. Unfortunately, the wording of this new question renders the procedure incomprehensible. It is not helped by an apparent requirement to submit reports with action types (sic) of “ETRM”, which doesn’t actually exist for EMIR. 

    FCA and the Q&A

    UK firms must be wondering how much longer the FCA will continue to support a Q&A that it no longer has the ability to influence. Obviously, it is a massive issue as there is strong pressure to minimise any divergence in the respective reporting regimes even if it only stems from the Q&A. Whilst there is a huge amount of valuable information in the Q&A, there is room for improvement. Anybody doubting this should look at TR Q&A 9 a little closer and see how elements of this actually contradict the RTS. As evidenced by the joint trade associations’ best practices, the industry has highlighted some areas of trade reporting where more clarification is required so that it can submit better quality reports.

    Problems following Brexit

    EMIR was already a very complex reporting regime, but the impact of Brexit has added to this complexity – particularly for those firms with dual-reporting obligations. Our ReportShield quality assurance testing takes into account the different nuances of reporting to an EU TR or to a UK TR (or both!). If the two regimes continue to diverge, Kaizen’s testing will continue to be updated in line with the latest guidance and we can also provide advice on ensuring your reporting has been updated for both EU and UK obligations.

  • The (Trade) State We’re In: SFTR Q&A #2

    The (Trade) State We’re In: SFTR Q&A #2

    ESMA has updated its SFTR Q&As (28 January) to provide clarification on three areas:

    • (6) How to report past modifications,
    • (7) How to update a trade state report belonging to a SFT, and
    • (8) Reporting of SFTs by the FC on behalf of a SME-NFC pursuant to Article 4(3) SFTR.

    The clarifications provided in Q6 and 7, while not appearing to make any of the reporting simpler, should ensure that activity corrections and modifications provide an accurate picture of past trade lifecycle, while maintaining an accurate current trade state.

    Late Reporting Guidance – Question 6

    In Question 6, ESMA explains that whether you are reporting one or a number of events (e.g. modifications or corrections) with past event dates (prior to reporting date -1), then you should submit these reports with the correct historic events dates. Since these will not be captured in the current trade state report, you must also send a modification report of the latest version (its current state), with the date in which the report is made (i.e. the same date as in the reporting timestamp field).

    Integrity of the Trade State Report – Question 7

    ESMA’s response to question 7 clarifies the treatment of events in the creation of trade state reports.

    Part a), explains that only actions reported where event date is equal to or one business day less than reporting date should be included in the trade state. This should take into consideration non-working days in the jurisdiction of the reporting counterparty or entity responsible for the report.

    Part b), states that the trade state of an SFT relates only to outstanding transactions and that while changes to terminated or matured SFTs should be incorporated in the event log, they cannot be reopened. Trade repositories (TRs) should not update the latest state of an SFT if the event date of a report is prior to Reporting date -1.

    Parts c) & d) explain that while it is possible to report a termination late, using the action type – Termination (ETRM) and the relevant event date and termination in the past. The TRs should subsequently update the latest trade state report and remove these SFTs. The TRs should also remove these SFTs from their reconciliation 30 calendar days after a termination is reported.

    Mandatory Delegation for Small NFCs – Question 8

    Question 8 is focussed on full clarification of how financial counterparties (FCs) provide mandatory delegated reporting for small non-financial counterparties (NFCs).

    Part a) lays out the counterparty & reuse table fields and data that will need to be supplied by the NFC. It also reiterates the FCs responsibility to report the trades as soon as they are in receipt of the necessary information, even when late.

    Part b) explains the situation in which the NFC has allowed their LEI to lapse – in which case, the FC must submit reports as soon as it has been renewed by the NFC.

    Part c) reiterates that it is the responsibility of the NFC to keep its status as a small NFC up to date with the FC. Where this status is updated late, the FC should submit the missing reports (new trades, modifications & terminations) ASAP.

    Finally, Part d) explains that in the unusual situation in which the FC and NFC are reporting to different TRs and the status of the NFC changes such that they become eligible for mandatory delegated reporting by the FC, then the NFC should transfer its outstanding SFTs concluded with the FC to their TR. 

    • Kaizen provides Accuracy Testing on SFTR reports to provide assurance that your SFTR reporting is accurate and complete. For a conversation about your SFTR reporting challenges, please contact us.
    • To read the Q&A visit ESMA’s website.          
  • SFTR: Six months on – what have we learned?

    SFTR: Six months on – what have we learned?

    As we look back on six months of SFTR, it’s fair to say that as a regulatory reporting quality assurance firm, we are perhaps the harshest critics of regulatory regimes and reporting firms. We do however wrap our criticism in a velvet glove as opposed to the enforcement actions that may follow for firms that do not take heed.

    Brexit has taken over

    With Brexit also live, there is perhaps as much uncertainty now as there was in the run up to July go-live. Brexit has hijacked the agenda and brings about new fears and challenges such as some dual reporting requirements. We have already seen the first signs of divergence (with non-financial counterparty reporting live in the EU but not required in the UK), with more to follow if the UK fails to make a breakthrough on passporting. EU beneficiary countries taking business from London have yet to show their true colours in terms of their levels of surveillance, regulatory interpretation and enforcement, adding to the uncertainty.

    Regulatory concerns

    There was certainly a lot of virtual back-slapping following SFTR go-live with very high trade repository (TR) acceptance rates (particularly relative to more mature regimes) but regulator concerns remained. Reported volumes, while hard to judge during a global pandemic, have been trending below regulator expectations. Collateral reporting, its quality and in some cases, its apparent absence, appear something of a black mark.

    How could the UK improve the regime?

    Though our Kaizen Accuracy Testing we have been able to glean far greater insights into reporting logic than the validation rules ever could. We can see that firms are struggling to populate certain data fields. The haircut and margin fields are good examples of where we are seeing significant numbers of errors. The concerns that I expressed with the FSB and ESMA with regard to reference data quality have also been borne out of the reporting delivery. The need for fully specified reference data and genuine golden sources is more evident than ever. The UK could be minded to take out much of this reference data, significantly simplify reporting and dramatically improve data quality by independently sourcing much of the security data themselves. “If you ask 10 different reporting counterparties, you’ll get 8 or 9 different answers!”  

    Next steps:

    1. Don’t try to game the regulation and take advantage of the current poor state of the validation rules. Expect tighter regulation and enforcement as the newly involved EU national competent authorities find their feet and their teeth and the UK FCA looks to re-assert its authority.
    2. Ensure that controls are in place to provide certainty around completeness of reporting, with particular attention to full collateral lifecycles and collateral reuse.
    3. Finally don’t be afraid to reach out to get help! There is a lot to be said for not marking your own homework and employing expertise and regulatory testing to bring the true quality of your SFTR reporting into sharp focus.
    • If you would like help with your SFTR reporting post-Brexit or to speak to one of our specialists, please contact us.
  • EMIR Q&A –UK derivatives to be considered OTC

    EMIR Q&A –UK derivatives to be considered OTC

    ESMA thoughtfully delivered a new Christmas edition of its EMIR Q&A on 21 December. It may not have been at the top of everyone’s Christmas list, but at least it hasn’t brought any unexpected pain. So, let’s unwrap it and see how it’s impacted EU EMIR trade reporting.

    UK trading venues confirmed as OTC

    As the UK has left the EU and its derivative markets haven’t been granted equivalency, it should be no surprise that any new derivative contracts traded on UK derivative markets will be considered OTC for EU EMIR reporting purposes. This will have the following implications for trade reporting to an EU trade repository:

    • ‘Venue’ (2.15) – for trades in UK derivatives concluded OTC, the code ‘XXXX’ shall be used (as opposed to ‘XOFF’)
    • ‘Clearing obligation’ (2.34) – this field will now need to be populated for trades executed on UK derivative markets
    • ‘Intragroup’ (2.38) – this field will now need to be populated for trades executed on UK derivative markets.

    This is exactly as we expected and consistent with previous post-Brexit transition communications.

    There is no change to current practices when reporting to UK trade repositories. The UK FCA has taken a pragmatic approach and doesn’t treat EEA derivatives as OTC for EMIR trade reporting purposes.

    What else is in the new Q&A for trade reporting?

    ESMA provides wording to clarify the reporting technique for derivatives executed on a third country venue and cleared on the same day. So long as certain criteria are met, the reporting scenario for third country ‘ETDs’ is the same as EEA ETDs.

    In practice, this is what the industry has already been doing – there is no real change.

    Changes to Kaizen testing post transition period

    Clearly, there are some changes to both the UK EMIR and EU EMIR reporting regimes after the Brexit transition period. Whether you are reporting to an EU trade repository, a UK trade repository or if you are unfortunate enough to have a dual reporting obligation, you can be rest assured that our quality assurance testing will continue to adapt to the changing regulatory requirements.

    • If you would like more information on this, or to speak to one of our specialists, please contact us. 
    • To read the new EMIR Q&A, visit the ESMA website.
     
  • ESMA releases SFTR data reporting Q&A

    ESMA releases SFTR data reporting Q&A

    ESMA published the first Questions and Answers on SFTR data reporting document on 5 November 2020. For those of you that have been paying attention, there is remarkably little news or need to make any further changes – everything here has been flagged to the trade associations well in advance

    The optimists among us will be disappointed that no concessions have been made to the challenging and cumbersome need to keep rolling the maturity date/end date on failing repo transactions.

    The key questions addressed in this Q&A include:

    1. Treatment of working days from a reporting perspective and differing calendars/ time zones between counterparties. The message is clear, use local times and calendars, with branches expected to report within the working day of the member state from which they operate.
    2. No change on treatment of fails. Temporary fails on the value date (start date) that do not result in modification or termination are not reportable. Transactions failing over their maturity date (end date) continue to need to be modified on contractual maturity date +1 – to roll the date forward one business day until they settle, regardless of SFT type. Failing closing legs of CCP cleared SFTs should only be reported (with modification) if the fail can be attributed to individual SFTs.
    3. Repo transactions subject to bilateral margining post trade should be reported as Collateralisation of net exposure TRUE throughout their life. These transactions should then be subject to both trade level collateral updates (with UTIs) and net exposure bilateral margin collateral updates without UTIs throughout their lives.
    4. Use of trading venue: When executed on a trading venue, the segment MIC code of the venue should be reported. If the particular SFT is admitted to trading on a venue but executed off venue then XOFF should be used. In all other cases, including executing through a Systematic Internaliser (SI), then XXXX should be used.
    5. In order to report zero collateral for margin lending, counterparties should use the European Financial Stability Facility ISIN code EU000A1G0EB6 to report zero collateral for margin loans.    
    • For help to ensure that your firm is compliant with SFTR data reporting or to talk to one of our regulatory experts, please contact us.

     

  • Brexit and SFTR – Your questions answered

    Brexit and SFTR – Your questions answered

    We’ve had a great response to our Brexit webinar on EMIR and MiFIR, but it’s left some of our clients asking “what about SFTR?” We asked our Senior Regulatory Reporting Specialist for SFTR, Jonathan Lee, about what firms need to know.

    This Q&A looks specifically at the SFTR reporting obligations (as distinct from any other disclosure requirements) and the period following the end of the transition period from 1 January 2021. 

    What are the reporting differences?

    The key difference between EU SFTR and UK SFTR is that under UK SFTR, non-financial counterparties (NFCs) established in the UK will not be required to report under SFTR, either directly (if large in size) or via mandatory delegated reporting (if small or medium-sized).

    As a further point of clarification, if a financial counterparty established in the UK has traded with an NFC, then they will only be required to provide a single transaction report with the FC as reporting counterparty. In the EU, transactions executed by NFCs will be required to be reported from 11 January 2021.

    Which regimes do I need to report under?

    • Financial counterparties established in the UK will need to report under UK SFTR.
    • Financial and non-financial (from 11 January 2021) counterparties established in the EU will need to report under EU SFTR.
    • UK established firms trading through EU branches will need to submit reports under both UK SFTR and EU SFTR.
    • EU established firms trading through UK branches will need to report under both EU SFTR and UK SFTR.
    • Third country established firms trading through UK branches will need to report under UK SFTR.
    • Third country established firms trading through EU branches will need to report under EU SFTR.

    Which trade repository should I register with?

    • Financial counterparties established in the UK will need to sign up to a UK SFTR trade repository (TR) if they have not already done so.
    • Financial counterparties established in the EU or any third country, trading through UK branches will also need to sign up to a UK SFTR TR.

    What about reconciliations?

    Reconciliations going forward will only take place between intra-jurisdiction (EU vs EU or UK vs UK). Simply, you will only be subject to trade reconciliations when both parties have an obligation to report under that jurisdiction (whether UK or EU). This applies to both pairing and matching of transactions and lifecycle events.

    Anything else for firms to consider? UTI creation, sharing, pairing and matching…

    At present, the unique trade identifier (UTI) creator is determined by either bilateral agreement with the counterparty or a mechanism determined by the ESMA defined waterfall. In essence, this will not change, the issue is that it will only continue to formally apply across a single jurisdiction. Therefore, if you currently have a bilateral agreement to receive UTIs from an EU counterparty, while you will be required to report under UK SFTR, then they will no longer be bound to provide it, nor will it be subject to pairing and matching and vice versa. There is no reason why you cannot continue to supply and receive UTIs in the same way as pre-Brexit, but you may meet reluctance from some counterparties and without dialogue with your counterparties, it should not be assumed, if crossing jurisdictions.

    Since these cross jurisdictions become single-sided transaction reports, some dealers have expressed a desire to simplify processes by unilaterally assigning UTIs to cross jurisdictional transactions, thereby no longer offering UTI sharing and pairing for these reports.

     

    • For a conversation with Jonathan or one of our regulatory experts about reporting under SFTR after Brexit, please contact us.
  • Short position reporting enforcement by the UK’s FCA

    Short position reporting enforcement by the UK’s FCA

    The UK’s Financial Conduct Authority (FCA) has taken its first enforcement action for a breach of the Short Selling Regulation (SSR) which require holders of short positions to disclose to the FCA and the issuer. The FCA fined a Hong Kong based hedge fund, £873,118 for their failure to disclose their short positions in Premier Oil plc, a UK incorporated and listed company. Premier Oil announced its proposed merger with Chrysaor Holdings Limited on 6 October after a reduction in its share price since 2017.

    The hedge fund said it hadn’t realised it had built up a short position of 16.9% of the issued share capital of Premier Oil and reported it as soon as it was aware. In total the hedge fund had missed 155 mandatory net short position disclosure filings.

    The FCA reduced the fine by 30% for good behaviour during the investigation. The FCA told Securities Lending Times, “That makes this a substantial fine, given there was no profit, which reflects how seriously we take this type of misconduct.”

    Short selling position disclosure obligations

    The obligation to report short positions began in 2008 as a result of the financial crisis. Since then, more countries have implemented short position reporting.  This was introduced to identify those building short positions which could damage the stability of the financial markets. In comparison to other shareholding reporting obligations, the thresholds for short position reporting are very low.  Across Europe, the reporting threshold begins at -0.2%, however as a result of COVID-19, ESMA issued a decision in March this year lowering the reporting threshold to 0.1%.  Other changes are afoot for the UK reporting regime as it leaves the EU on completion of the Brexit transition period on 31 December 2020.

    How could the hedge fund not be aware of such a substantial short position?

    It may seem strange that the hedge fund was not aware it had built up such a large short position of 16.9%.  However this IS possible, as those responsible for reporting are often part of Compliance or Operations functions of financial organisations and therefore are not aware of the investment decisions made by traders or fund managers, unless they have access to an automated system that calculates positions in the many different ways that are required by each reporting regime and in each different jurisdiction.

    Those responsible for reporting require knowledge of the myriad of global shareholding disclosure rules and subsequent changes to those rules.  Managing shareholding disclosure obligations is not an easy task; I know because I have managed it for some the largest global financial institutions.

    How important is it to understand and comply with these regimes?

    The complexity of these disclosures is often misunderstood as purely being a case of monitoring thresholds.  When in fact each shareholding disclosure requirement, whether it be the major shareholding* obligations or the short selling disclosures, all require different derivatives to be included, different netting to apply, different aggregation methodology and different exemptions. Even within the EU short position reporting regime, there are netting differences applied to those who hold a position as a fund manager compared to those on the trading desk of an investment bank.

    Mark Steward, the FCA’s executive director of enforcement and market oversight, highlighted the importance of compliance with these shareholding disclosure regimes when he said, “Failure to report disclosable short positions undermines the integrity and efficiency of financial markets”.

    This fine clearly marks the importance of monitoring global shareholding rules and the dangers of not doing so. 

    Kaizen can offer peace of mind with our easy-to-use platform and hosted customised rules engine incorporating aosphere LLP’s (an affiliate of Allen & Overy LLP) shareholding disclosure rules library as a basis for the service.  The system further enhances and interprets this with our regulatory expertise, alerting you of your reporting obligations so you do not miss these critical filing deadlines.

    *also referred to as substantial or long reporting.

    • Find out more about our automated Shareholding Disclosure System and watch our video here or for a conversation with Angie, please contact us.

     

  • Why mandatory shareholding disclosures matter to your firm

    Why mandatory shareholding disclosures matter to your firm

    In a previous blog we provided a summary of what shareholding disclosures are; now we will explain why these matter to your firm.  The “in a nutshell” answer is sanctions!  Having worked in the financial industry managing this process myself I have seen the pain that firms suffer with sanctions for incorrect or late disclosure filings, where they not only have a regulator breathing down their neck but all the attention of senior management who want to know what/where/why and who’s head will roll. 

    Sanctions in the shareholding disclosure world are often a result of simple human error, a manual process, or a lack of resource or a combination of all three!  In such a complex world, where so many things can go wrong, there are some very serious sanctions.  Across Europe the Amended Transparency Directive suggested non-compliance should result in fines of up to 10m euros or 5% of annual turnover, suspension of voting rights and public statements.  There are even more serious sanctions, for example, in Switzerland, Vietnam, Hong Kong, Belgium, Israel, and Japan where non-compliance is a criminal offence.

     

    Why is this significant? 

    Being publicly sanctioned can cause significant reputational damage to your firm and this is something that many financial institutions try hard to avoid.  Whilst there are some significant fines that have been reported in the media for breaches of shareholding rules many sanctions occur behind closed doors, therefore the real number of those who have been subject to penalties is not in the public domain. 

    In my 13 years working in Compliance within the financial industry I have dealt with a number of regulators regarding sanctions, I have fought against the removal of a Head of the Compliance department’s passport by the Vietnamese regulator, have been interviewed by investigators and lawyers and have been in the uncomfortable position of reporting on these censures to Boards of Directors. These sanctions are not uncommon across the financial industry; I have spoken to many peers at industry meetings or socially where we shared our woes of facing off to a regulator.

    Although some regulators have more punitive sanctions others require very strict compliance to their rules and regularly censure and it’s those regulators that cause firms the most concern.   Some regulators make use of these sanctions more often; for example, the German regulator, BaFin, is renowned for fining for some of the smallest of issues.    

    Whilst on occasion incorrect disclosures may be the result of some fraudulent activity, more often than not they are a result of lack of resource, difficulty in interpreting the rules, lack of understanding of the derivative products and the data, a lack of automated processes and the result of manual error.  I left the financial world to design and build a solution for the industry to solve the many issues faced when trying to comply with the hundreds of global shareholding rules.  Whilst it may be impossible to avoid every sanction, if you can automate your disclosure process you can reduce significant risks; key-man, human, resource, operational, data and market. 

     

    Our SDS Service

    Kaizen’s Shareholding Disclosure Service “SDS” allows you to automate a process that is incredibly complex.  If you try to manage this process manually then there are number of issues you will face:

    • A lack of in house knowledge of the rules globally
    • applying complex rules that are different across each of the 95+ jurisdictions
    • ensuring each rule has its own calculation methodology (which products you include, exemptions, various holdings capacities, different denominators etc)
    • manually calculating a holding / calculation error
    • tracking and updating these rules
    • alerting users to disclosures
    • managing internal data and market data
    • late disclosure
    • management oversight

    All of the above opens a firm up to the risk of getting it wrong and left facing sanctions.  Kaizen’s SDS uses aosphere LLP’s (an affiliate of Allen & Overy LLP) shareholding disclosure rules library as a basis for the service and further enhances and interprets this with our regulatory expertise to apply the rules to a firm’s specific business model.  This can help a client where this kind of expertise may be absent within their department.  Automated processing of data files against these rules means that calculations are consistent, easily updated and are calculated quickly.  Users are immediately alerted to a disclosure that requires filing and automated disclosure forms means there is no room for manual error.   In addition, the user interface is packed full of useful tools to ease the process and make it as simple as ABC, protecting you and your organisation from these sanctions.

     

    • Please contact us if you would like to learn more about our Shareholding Disclosure Service.

     

     

     

     

     

     

     

     

  • SFTR Reporting Challenges for Buy-Side firms

    SFTR Reporting Challenges for Buy-Side firms

    SFTR Reporting go-live in July seemed to go fairly smoothly (at least on the surface) but how will the buy-side fare now it’s their turn? Jonathan Lee outlines some of the challenges facing buy-side firms.

    Almost five long years since the SFTR regulation was published in November 2015, the reporting requirements finally go live for the buy-side* and UCITs today (Monday 12 October). In practice, the first reports are likely to wait until tomorrow given the lack of trading on a Sunday.

    Delegated reporting

    Buy-side SFTR reporting brings with it many new nuances and challenges, particularly given the greater dependence on delegated reporting and the management structure surrounding some funds. Where the reports become essentially single-sided reports with delegation, any perceived reporting quality benefits from pairing and matching disappear (although the results from our ReportShield™ Accuracy Testing leads us to believe these benefits are somewhat tenuous anyway). The lack of a reporting aggregator will present significant report sequencing challenges too, where one manager or delegated reporting broker dealer can inadvertently overwrite the reports of another. This is particularly relevant to collateral reuse and cash reinvestment reporting (Table 4) and repo market bilateral margin reporting too.

    Reporting counterparties are ultimately responsible

    Unfortunately for the buy-side, SFTR reporting is not something you can wash your hands of through delegation. The reporting counterparty (you, the fund) retains the legal obligation to submit complete, accurate and timely reports to a registered trade repository (TR). In addition, the lack of necessary data at the delegated reporting party, coupled with commercial confidentiality concerns around revealing positions, means you retain the obligation to provide collateral reuse and cash reinvestment details too. Together, this means that ensuring that the reporting firm has an effective controls environment is a key requirement for all financial counterparties in the securities financing transaction (SFT) markets.

    Controls are key

    At Kaizen Reporting, we are firm believers in not marking your own homework when it comes to quality checking your own reporting. We are working closely with our clients to ensure the right controls are in place to keep delegated reporting parties on their toes. Our ReportShield Accuracy Testing and Advanced Regulatory Reconciliation are outsourced, managed services that aid firms in doing this, providing fund managers, compliance and senior management with confidence that they are meeting their SFTR reporting requirements.  

    • Watch Jonathan speaking about these issues in this short interview.
    • If you are a buy-side firm and would like a conversation about the contents of this blog or the accuracy of your SFTR reporting, please contact us.

    *pension funds, insurance & re-insurance companies, alternative investment funds (hedge funds)

  • How is the Covid-19 pandemic affecting shareholding disclosures?

    How is the Covid-19 pandemic affecting shareholding disclosures?

    Covid-19 may not be having quite the impact on shareholding disclosures that the 2008 financial crisis did, however it has had an impact, and this has been at the same time as the world is dealing with something quite extraordinary. The financial services industry has had to move quickly to get entire workforces working from home safely and securely, and this had its own challenges. During a time of much in-work and out-of-work stress, compliance and operations teams are having to respond quickly to changes in shareholding disclosure rules globally as a result of the financial impact Covid-19 is having on the financial markets. 

    40 changes to rules within one month of lockdown

    Many regulators swiftly implemented changes to the shareholding rules in order to safeguard certain industries/issuers from the impact of the volatile stock markets around the world. These changes were announced with no consultation and took immediate effect. Within the first month of the lockdown there were over 40 changes to shareholding disclosure rules.  We saw the focus of the change being on lowering the percentage thresholds for substantial shareholding* and short selling disclosure reporting, additional disclosure of details of intention, and there were also outright bans on short selling.  The lowering of thresholds provided greater transparency to the market and respective regulators whilst the short selling bans prevented the kind of activity that was witnessed in 2008 during the financial crisis where companies were shorted until their share price nose-dived. 

    How are we helping our clients during this difficult time?

    We continually monitor and update our rules library. We react very quickly to inform our clients and make any necessary changes to our monitoring and reporting service. We have seen changes globally including but not limited to the European Union, Italy, South Korea, Belgium, Malta, France, Greece, Spain, U.K, Malaysia, UAE, Bulgaria, Jordan, Jersey, Bahamas, Croatia, Japan, Monaco, India, Nigeria, Ghana, Germany, Taiwan, Australia, Oman and the Philippines. Regulators have little sympathy for non-compliance even in these globally challenging times.

    Rule changes on your behalf

    As our clients were already using our service, their life was already made simpler as the system is accessed through a web browser there were no issues with them accessing this from home (even with the normal security procedures for accessing the service). With our monitoring of any shareholding disclosure rule changes our clients had peace of mind that we were continually monitoring any rule changes on their behalf and due to our ability to make these changes on their behalf, there was little they needed to do to respond to these rule modifications. If they had been using an internal system it would have been more challenging for them. During times of additional stress our service really can provide you with additional comfort that your business is still compliant despite the speed of change. 

    Even though we are now many months into the pandemic, we are seeing some of the emergency legislation being extended as the markets are still very fragile and it is still impacting on the global financial markets.  We are likely to see its impact more permanently in the shareholding disclosure world, in particular as governments look to protect their key industries. 

    *also known as major shareholding or long disclosure reporting

    • For more information about our Shareholding Disclosure Service or to watch our short introductory video, visit our SDS service page.
    • For a demonstration of the system or a conversation with Angie Huff about your shareholding disclosure challenges, please contact us. 
  • RTS 2 Non-Equities Trades: Are you ready to publish within five minutes?

    RTS 2 Non-Equities Trades: Are you ready to publish within five minutes?

    In January, with a year to go, I reminded people in a blog that the timing for the publication of RTS 2 non-equities trades was reducing from 15 minutes to five minutes. The change in January 2021, comes three years after MiFID II’s inception. One of the regulation’s objectives was to push investment firms for further transparency through automation and electronification, specifically of the fixed income market where voice-trading still plays a major part.*

    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 five minutes after the execution of the relevant transaction.”

    Three months to go

    Now we are in October, we find ourselves only three months away from this change in regime.  Are you ready?  Does Front Office IT have this on their book of work to implement over New Year?  Have traders been made aware of the procedural changes?  If not, you are running out of time and with multiple other regulatory moving parts, as well as the B-word to contend with, my advice is make sure this gets raised as soon as possible.

    My four main areas to prepare are:

    • Make sure your Front Office IT have this on their book of work and FIX messaging is tested
    • Ensure communication to Front Office happens well in advance, for any non-automated trading flows and to those teams that are monitoring real-time trade reporting and rejections
    • Work with your APAs if there is any uncertainty. Make sure you understand rules or logic that you have in place and keep up-to-date with the latest version of their FIX specification
    • Validate that Senior Manager Functions for SMCR are aware and happy with the changes to reporting and they have been proceduralised.

    9% of trade reports currently don’t meet the deadline

    Through Kaizen’s Accuracy Testing we have found that nine per cent of tested RTS 2 non-equities trade reports are not meeting their 15 minute real-time obligation after execution. If you’re not able to meet the 15 minute deadline, how will your internal processes meet the five minute requirement of MiFID II RTS 2, come January next year?

    This is where we can help.  Our Accuracy Testing Service for MiFID II Post Trade Transparency Reporting (PTT) for RTS 1 & 2 helps firms identify and understand errors in their reported data to ensure that you are able to meet your regulatory reporting obligations.  Please contact us for a conversation with Chris or one of our regulatory specialists.

    *RTS 1 Equities remains unchanged at 1 minute.

  • How to report UK nationals if there is a no-deal Brexit

    How to report UK nationals if there is a no-deal Brexit

    We were hoping for a different outcome but unfortunately for firms reporting to EU National Competent Authorities (NCAs), the approach to reporting UK nationals will change if there is a no-deal Brexit.

    Happily there is no change for firms reporting to the FCA. 

    Wouter van Bronswijk who leads reporting at the AFM, the Dutch regulator, confirmed at a recent Infoline Trade and Transaction Reporting Conference that based on the regulations, the UK would become a third country. This means that firms reporting to EU NCAs will have to change the way in which:

    1. They prioritise the nationality to use for individuals who have more than one nationality of which the UK is one;
    2. They change the preferred identifier to use for UK nationals.

    Determining the nationality to report

    Where an individual has multiple nationalities there is a waterfall approach to determine what nationality to include in the transaction reports. This will apply to traders and clients that are natural persons. 

    The steps are:

    • Use the first EEA country based on the country code when sorted alphabetically
    • If there are no EEA nationalities then it is the first non-EEA nationality based on a sorted country code
    • If the UK is the nationality, then the passport number is the preferred identifier and if that does not exist the CONCAT should be used.

    All those UK National Insurance numbers that firms had been diligently collecting cannot be reported to EEA NCAs post-Brexit. 

  • FCA continues its focus on data quality and market abuse

    The FCA recently published its Annual Report and Accounts for 2019/20 wherein they discuss their sector priorities.

    Market abuse takes centre-stage but they highlighted their aim of improving the quality of firms’ transaction reports. As we know, these are the main tools used by the regulator to surveil the market but also for the investigative process where the reports act as the first port of call when analysing suspicious activity highlighted by Suspicious Transaction and Order Reports (STORs). 

    The FCA notes that they are using technology to review for both suspicious activity and for data quality. Indeed, we know that data quality is a necessary condition for an effective surveillance capability. The good news is that they noted a significant improvement in data quality. 

    Where is EMIR?

    What was surprising to me, was that EMIR reporting was not raised as a key priority.  We are currently facing unprecedented uncertainty and market volatility.  Now is the time where we need an early warning system to head off any financial sector tsunami the most. And yet, EMIR reporting was not mentioned. After more than six years and two upgrades, EMIR reporting is still not fit for purpose. Indeed, ESMA recently singled out the UK for its failure to enforce compliance with EMIR amongst the regulated community. We at Kaizen know from our extensive quality assurance testing across the sector that EMIR reporting is in a worse state than MiFID. 

     

    Annual Market Cleanliness Statistics and number of events per year

    Potentially Anomalous Trading Ratio

    During 2019/20, the FCA received 5,336 STORS and a further 788 external notifications. These resulted in 415 preliminary reviews and 53 enforcement investigations being opened. FCA activity and the level of market abuse is not necessarily the same thing, so to add to the existing estimates of market cleanliness, they have added a new measure –  the Potentially Anomalous Trading Ratio (PATR). This looks at suspicious activity rather than just correlating price movements ahead of takeover announcements. PATR is primarily based on the activity of the trading participant and whether this is outside of their normal activities. 

    The diagram below shows a price sensitive announcement (represented by the red line) and illustrates the time periods considered when constructing the PATR.

    Price sensitive announcement - FCA

     

    What stands out is the short benchmark period to assess “normal trading behaviour” of 30 days. With all the data at their fingertips, a more sophisticated measure of normal would be warranted, as a too short a measure will overstate the level of potentially abusive behaviour.  The post-announcement period is also questionable. Any parties not taking their profits in the five-day window are excluded thereby reducing the activity that falls within scope of the period resulting in an understated measure. Added to this, the records in scope exclude where individuals make a profit of less than £5000 on their trade and £50,000 for legal entities. 

    As with all measures, it has its shortcomings but it is helpful when considered with the other indicators. 

     

    Potentially Anomalous Trading Ratio results - FCA

    More to do

    Based on the measures, the FCA states that 99.2% of activity did not occur during a sensitive time period before the announcement of price sensitive information. However, 6.7% of the trading around price sensitive announces was anomalous. This may not seem like a large proportion but, when you consider the statistic is looking only at the 0.8% and is calculated in a period when there has been little takeover activity compared to prior years.  Indeed, if this is accepted as a basis for consideration of impact, it can be argued that it weakens the cost-benefit case for market-wide obligations to apply anti-market abuse measures. Insider traders are still taking a reasonable slice of the pie, so there is more to do to ensure fair markets. 

    2019 Summary - Trading Activity FCA

    • To discuss the contents of this report with Dario or one of our regulatory specialists please contact us.
    • To read the report in full visit the FCA’s website.
    • All graphics and diagrams © Financial Conduct Authority. 
  • FCA: The five key reporting challenges for firms preparing for Brexit

    FCA: The five key reporting challenges for firms preparing for Brexit

    The FCA has outlined what it sees as the key challenges for firms reporting to the FCA in respect of Brexit. 

    Speaking at the Infoline Trade and Transaction Reporting Conference last week, Ana Fernandes, who leads the Markets Reporting Team at the FCA, gave her views alongside Wouter van Bronswijk from the Netherlands’ AFM, Rob Knight (Chair) and myself. 

    It was great to get an opportunity to hear the thoughts of both EU and UK regulators as a possible no-deal Brexit lurks around the corner.

    Here is a summary of the key takeaways for firms reporting to the FCA.

    • Pre and post Brexit reporting consistency:  The FCA has been working to keep disruption to a minimum.  Hence there is broadly full consistency between pre and post Brexit reporting to the FCA. The regulator is in the process of drafting the Statutory Instrument text, which will be published next year. This will look to address some current deficiencies encountered since MiFID II go live and there will be a consultation undertaken with the industry on the proposals to seek their views. 
    • No Transitional relief: “Market Abuse does not go on holiday” so transaction reports are required from Day 1 post-Brexit.  There will be “no excuses”. The current transition period is operating up to 31 December. 

    • UK firms must use UK FIRDS: The scope of instruments within the regime is being maintained to include all of the EU FIRDS instruments but will also include UK-only instruments. Further, the UK version of an instrument will take precedence over any EU version instruments which may cause differences between the two data sets.

    • Loss of Article 4 Transmission: UK firms and EU firms transmitting to each other can no longer make use of the Article 4 transmission process as the UK will become a third country. Firms have to make sure they are connected to FCA FIRDs by the cutover date. UK FIRDS has been live and operational since March 2019 to support this.

    • Final point: Firms have to be ready on Day 1, there is no transitional period or holiday.  The FCA’s expectation is that all firms should be compliant.

    Many thanks to Richard Horsler and the team at Infoline for organising the conference.

    If you’d like guidance or advice on preparing for Brexit from one of our regulatory specialists, please contact us. 

  • Are the tectonic plates shifting in the Data Reporting Services Providers (DRSP) market?

    Are the tectonic plates shifting in the Data Reporting Services Providers (DRSP) market?

    Not too long after the CME announced it was shutting down its NexAbide ARM service, the Deutsche Boerse announced today that it is selling its “regulatory reporting hub” to MarketAxess’s Trax NL B.V, an existing ARM.  The Hub provides both ARM and APA services which will complement the services provided primarily in the UK through Xtrakter Limited. With a stroke of a pen MarketAxcess has a very large chunk of the EU ARM market. 

    Limited ARM options for UK

    In the UK, the ARM options available to firms are limited to three providers following the withdrawal of NexAbide:

    1. Bloomberg Data Reporting Services Limited
    2. London Stock Exchange plc (UnaVista)
    3. Xtrakter Limited (MarketAxess)

    Whilst in Europe there is a more diversified market for ARM services and therefore more choice, Deutsche Boerse represented the largest EU ARM with very competitive pricing.

    So what’s next? 

    I presume all existing clients will seamlessly migrate to the Trax NL B.V. ARM.  The transaction is meant to conclude in the fourth quarter of 2020 along with the closedown of NexAbide on 30th November and Brexit at the end of the year. 

    I am sure there will be more information on that front from MarketAxess shortly but the focus is likely to be on continuity of service and ensuring firms are ready of the Brexit transition. 

    Today at the Trade and Transaction Reporting conference, Ana Fernandez, the manager of the FCA’s Transaction Monitoring Unit, made it clear that firms need to be ready for Brexit and there will be no transition period. 

    EU ARMs list courtesy of ESMA:

    1. Euronext Paris SA
    2. BME REGULATORY SERVICES
    3. AQ Metrics Limited
    4. Hellenic Exchanges – Athens Stock Exchange SA
    5. Bloomberg Data Reporting Services B.V.
    6. Trax NL B.V.
    7. Deloitte Solutions
    8. Krajowy Depozyt Papierów Wartościowych S.A.
    9. Nasdaq Stockholm AB
    10. UnaVista TRADEcho B.V.
    11. Regulatory Services GmbH
    12. vwd TransactionSolutions AG
    13. Nasdaq Broker Services Aktiebolag
    14. Raiffeisenlandesbank Oberösterreich Aktiengesellschaft
    15. Raiffeisenverband Salzburg eGen
    16. Raiffeisen-Landesbank Tirol AG
    17. RAIFFEISENLANDESBANK NIEDERÖSTERREICH-WIEN AG
    18. Raiffeisen-Landesbank Steiermark AG
    19. Raiffeisenlandesbank Vorarlberg Waren- und Revisionsverband registrierte Genossenschaft mit beschränkter Haftung
    20. Raiffeisenlandesbank Kärnten – Rechenzentrum und Revisionsverband, registrierte Genossenschaft mit beschränkter Haftung
    21. KELER Központi Értéktár Zrt.
    22. Raiffeisenlandesbank Burgenland und Revisionsverband eGen.

    Kaizen is offering CME clients moving to a new regulatory reporting provider a free healthcheck of their regulatory reporting data quality. Allowing Kaizen to independently test your reporting quality will ensure you meet your regulatory obligations and will also provide early identification of issues, allowing you to correct any errors before you move to a new ARM or Trade Repository.  Contact us to find out more. 

  • Systematic Internaliser (SI) regime for OTC derivatives comes into play

    Systematic Internaliser (SI) regime for OTC derivatives comes into play

    Today the Systematic Internaliser (SI) regime for OTC derivatives comes into play, over two and a half years after MiFID II’s inception. Whereas the equities SI regime was introduced a few months after go-live, and bonds in September 2018, the reference data quality for OTC derivatives was not of the standard required for Systematic Internaliser thresholds to be understood and calculated, hence the delay until now.

    Systematic Internalisers must now comply

    Previously, the main sell-side SIs had ‘opted-in’ to being an SI, without having the mandatory requirements that come with being an SI.  Now, if firms are meeting the various thresholds for trading  – Organised, Frequent, Substantial and Systematic – they have to comply with the obligations set out by MiFIR and MiFID II in relation to pre & post trade transparency, best execution and reference data. Importantly, they also have to keep their buy-side clients informed.

    Multiple asset classes

    The complexities arise with OTC derivatives and the multiple sub-asset classes and sub-classes. We are working with the industry solution for the source of Systematic Internaliser aggregated data, Smartstream RDU. Their SI registry is crucial so that we can understand the granularity of SI status, which in turn helps us to understand the reporting responsibility. This is an essential part of Kaizen’s MiFID II Post-Trade Reporting Accuracy Testing service. If you would like to check the accuracy of your Post-Trade reporting, please contact us for a conversation with one of our specialists.

  • Seven tips for navigating collateral reporting under SFTR

    Seven tips for navigating collateral reporting under SFTR

    Our SFTR specialists Jonathan Lee and Tony Weedon, list their key recommendations for addressing the challenges of collateral reporting which is proving to be one of the most difficult aspects of SFTR. 

    1. Install data guardians. Ensure every data item is appropriately sourced and has an accountable owner.
    2. Make your vendors earn their keep! Devote significant effort to sourcing SFTR data internally or around installing effective governance around externally sourced vendor data. 
    3. Prioritise data sources i.e. ESMA demand official sources for data points such as CFI codes, so use official sources such as the numbering agencies and FIRDS rather than data vendors wherever possible.
    4. Be upfront, transparent and timely in all of your SFTR reporting including the collateral. Do not withhold know transaction details and ensure daily collateral updates of changes and pricing. Ensure executions are always reported on a trade date +1 basis.
    5. Collateral updates. If the pricing of collateral or the quantity of collateral has changed in relation to open and outstanding term transactions, then provide settlement date +1 collateral updates accordingly.
    6. Stay honest to the transactions: if the master agreement indicates that the transaction is collateralised at the trade level, then report accordingly. Do not allow net collateralisation reporting to absorb what should be trade level collateral reporting if this is not consistent with the contract.
    7. Follow ICMA’s ERCC best practice on bilateral margin reporting for repo until such time that ESMA have provided a Q&A or clear guidelines regarding any alternative approach. This process will involve maintaining two distinct sets of collateral and collateral updates (trade level and portfolio level) in relation to the repo book.
  • FCA release Market Watch 65

    FCA release Market Watch 65

    Another day another Market Watch newsletter.  Without a commute out to Stratford, the FCA’s Markets Reporting Team (MRT) has been busy during lockdown using that additional time to look at the quality of some of the transaction reports they’ve been receiving. They’ve issued some further reminders on areas where they are seeing reporting issues, and what control arrangements firms are required to have in place.  

    Systems and controls

    In its commentary, the MRT point out that firms need to have access to a deep understanding of the reporting requirements that is sufficient to identify errors that may not be highlighted by a reconciliation.  In my experience, most reconciliations being performed only scratch the surface and fail to reconcile back to source; which will be the trade table in each Order Management System. Even the full reconciliations we conduct at Kaizen will not identify all issues. Where a value in the source system is dutifully carried through to the transaction report, it does not prove it is correct.  Timestamps, incorrect reference data, price and price type, these are all areas where accuracy testing is required. 

    Further, as we get deeper into MiFID, both EU regulators and the FCA will expect deeper accuracy testing where all issues can be tested for.  Only by performing deep testing can management and the FCA alike take comfort that the test results provide a true picture of reporting quality.  Lighter touch testing, whilst a cheap and easy fix, will not satisfy this obligation.

    Cessation of ARM services

    As a reminder, the FCA notes that where a data reporting service provider has indicated it will cease provision of its services, it is up the affected firms to make the necessary arrangements to ensure their reporting continues unimpeded. 

    Firms that currently use NEX Regulatory Reporting will by now know they need to put alternative arrangements in place.  If you need any assistance, either in selection of an alternative provider, or in the implementation and quality control testing that would be required, we can help.

    Specific reporting issues commented upon in Market Watch 65

    Unreported transactions: it seems the FCA believes some firms are not assessing reportability properly.  This can be a problematic area and firms must be very careful when making their assessments.  Fortunately, we re-perform all reportability assessments which helps ensure completeness of reporting but also captures changes in reportability due to late changes to FIRDS. 

    Late reports: this is an interesting one because despite the best efforts of firms, there will always be some instances where transaction reports will be submitted late after the T+1 deadline has passed.  What the FCA is most concerned with, is where the systems and controls to enable timely reporting are not in place.  

    Country of branch for the buyer/seller: MRT reiterates that these fields are to be populated only for clients and with the branch or head office country code that received the order or generated an order under a discretionary mandate.

    We often see issues with this field but it is a relatively easy one to fix and will help greatly improve reporting quality. 

    Trading Venue Transaction Identification Codes (TVTICs)

    Firms are failing to report the right code consistently.  This can be caused by processing issues or a failure to convert the values received in FIX messages in line with the specific trading venue’s instructions. If you are not sure on the requirements here, please get in touch.

    Immediate underlying

    Again, MRT is at pains to remind firms that they should be evaluating reportability of a derivative instrument based on the “immediate underlier” where the derivative itself is not found on FIRDS. 

    This problem arises where a derivative has a derivative underlier i.e. there is a chain of derivatives.  In such cases the immediate underlier will be a derivative.  For example, where a CFD is traded on an equity option, the underlier is the option, NOT the equity shares.  This principle will extend to assessing the instrument’s reportability and to filling in the supporting instrument fields 42-56: they should reflect the values for the immediate underlier.

    Dealing with errors and omissions

    The FCA has a standard form that must be completed.  Whilst being quite scary for those named on the form it does assist the FCA in its general monitoring efforts and they have asked that firms submit these promptly and not to wait until after an issue has been fully resolved. 

    They also remind firms that errors and omissions will need to be remediated with back reports/replays of the impacted activity. 

    If you want to know more or need assistance on any of the above please contact us and we’d be happy to help. 

  • My career in shareholding disclosures and the lessons I have learned

    My career in shareholding disclosures and the lessons I have learned

    Let me introduce myself, my name is Angie Huff and if you are reading this then the chances are that I have been in your position at some point during my career.

    Starting out

    I started my career at UBS investment bank in 2000. When I first started in shareholding disclosures there were no vendors in the market offering a solution and accessing the rules globally was a particular challenge. Our team compiled the disclosures not only for the investment bank but also on behalf of the asset management and private wealth management arm of the parent company. At this point I did not really understand what the different derivatives were, which of these derivatives should be included in the calculation or the different ways you could have exposure to shares and derivatives. There was very little information in the market to help with this and no training courses. It was difficult internally calculating the global positions across such a large organisation.

    Meeting the strict disclosure deadlines was a significant challenge. I faced many of the issues you have probably faced or are facing; regulatory enquiries/ investigations, sanctions, internal audits, reporting to the Board, issues with tripping a sensitive industry threshold, coping with a manual process, building out a global solution and interpreting legal rules and much more. 

    Takeover Directive and Transparency Directive

    During my time at UBS there was considerable change in the world of shareholding disclosures with the European implementation of the Takeover Directive and the Transparency Directive.  Whilst it was initially welcomed as it was believed this would harmonise shareholding rules across Europe, sadly this was not in fact the case.  As directives and not regulation, there remained many variations in the shareholding rules from country to country.  It also meant that I had to personally face the challenge of implementing all these rules within a short timeframe.  I think we’ve probably all been there – many long days and nights in the office scrambling to find a solution to complying with the new rules!  

    In 2007 I was head-hunted by Morgan Stanley, then later by Barclays Capital and finally Deutsche Bank.  I faced many of the same challenges at each organisation and throughout my collaborations with peer banks, it became clear this was an industry-wide issue. 

    Financial crisis

    At Morgan Stanley I faced the challenge in 2008 (in the midst of the financial crisis) of the overnight (and I mean literally overnight) introduction of net short position disclosures.  It was a very challenging time as these were introduced without warning, there was no consultation, no FAQs, and no real detail on how to comply, but it was clear that immediate compliance was expected. There was no such short disclosure requirement before this time, therefore our systems and processes were not set up to handle such different calculations.

    I remember sitting at home on the weekend with Google alerts set up, so that I was immediately aware of those other countries who introduced a similar short position disclosure requirement over that fateful weekend. Myself, my team and our IT department worked around the clock to ensure that we complied with the rules. 

    Working with aosphere

    It was during my time at Morgan Stanley that I had conversations with an affiliate of Allen & Overy called aosphere and joined their advisory board to opine on the needs in this area for the financial services industry.  It was a fantastic collaboration with a few others in the industry and out of this was born their shareholding disclosure Rulefinder service. Kaizen’s Shareholding Disclosure Service uses this as a basis to our rules library in the service we offer.  This offering from aosphere made a real difference to me and the industry. We finally had one place where we could access shareholding rules globally. However, to truly apply this to your business and positions you needed considerable understanding of many factors including derivative products, methods of trading/holding positions, corporate structures, and legal and industry terminology.  And there was still another thing missing  – a system solution to the shareholding disclosure challenge. 

    At Barclays Capital I faced another challenge of managing this area globally and at Deutsche Bank I had the challenge of implementing the changes in the German rules shortly after my arrival with little lead time which again meant many hours spent in the office.  

    Challenges I’ve faced

    Throughout my career I have faced many challenges including implementing solutions internally, looking for vendors (many of whom didn’t have any direct experience at the coal face), dealing with the issues resulting from human error with a manual process, answering regulatory enquiries, dealing with the fall-out of regulatory sanctions and reading and implementing the rules myself (where my law degree did come in handy).  You cannot really work in shareholding disclosures without becoming heavily involved in data. Each financial institution has their own data issues and nuances. Market data is also another challenge for shareholding disclosures which has to be taken into consideration in any monitoring and reporting solution.

    All of these challenges really shaped me and gave me greater insight into the needs of those within shareholding disclosure compliance/operations teams. 

    A new start as an entrepreneur

    In 2013 I left the industry to become an entrepreneur and build a solution for all my peers in the shareholding disclosure space. I worked closely with Adam Stearn, our technical architect and lead developer, to design and build a system incorporating solutions to all the problems I had met along the way.  Adam has 19 years’ experience in designing and implementing complex data processing systems and has a background in military IT projects and with that, a real understanding of the security required by our clients. 

    In your shoes

    My 13 years’ of in-house shareholding disclosure compliance experience has been applied to every part of our service to make life simple for you. I truly understand those deadlines and how important it is to quickly react to regulatory change. With our service you can be rest assured that we understand the challenges you are facing.

    Our aim is to take away the pain and stress of shareholding disclosures, to streamline the process, to make compliance with the rules globally simple and make reacting to regulatory change a fast and simple experience.

    With our integration with Kaizen we can really leverage their multi-award winning services and technologies to further improve the service for our clients.

    We offer more than just a system within our service – we have genuine expertise of sitting where you are. For more information about our Shareholding Disclosure Service or to watch our short introductory video, visit our SDS service page.

    For a demonstration of the system or a conversation with Angie Huff, please contact us. 

     
  • FCA Release Market Watch 64

    FCA Release Market Watch 64

    Today, the FCA published Market Watch 64 and it is the shortest Market Watch ever. On the face of it, it appears to have nothing new to say. However, it does contain an important warning for firms that are struggling to be ready for the Brexit changes at the end of the year:

    “..firms and Approved Reporting Mechanisms should comply with the changes to their regulatory obligations by the end of the transition period on 31 December 2020. Firms that are not able to comply fully with the regime immediately following the end of the transition period will need to be able to back-report missing, incomplete or inaccurate transaction reports as soon as possible.”

    It would be easy to forget the significant impact Brexit will have on transaction reporting, but Market Watch 64 clearly signals that this is not an option. If you are unsure how Brexit will impact your reporting obligations, why not talk to Kaizen. Please contact us for further details on Brexit reporting implementation, our quality assurance, reconciliation, governance and training services.

    Market Watch 64 Newsletter

     

  • Transaction Reporting How-to Guide: ‘Venue’ Field

    Transaction Reporting How-to Guide: ‘Venue’ Field

    On the face of it, the ‘Venue’ field in transaction reporting seems to be fairly straightforward – as the RTS states, it is simply the “identification of the venue where the transaction was executed.” Unfortunately, it is not quite as simple as it first seems and we detect a large number of errors with this field in our ReportShield™ Accuracy Testing.

    Why is the ‘Venue’ field so important?

    Every field is important to the regulators and Article 26 of MiFIR demands complete and accurate reporting. However, accurate population of the Venue field is particularly important for firms due to the impact it has on the population of associated fields. If it is populated incorrectly, it could result in a ‘CON 412’ error from the regulator and your report will be rejected.  It also impacts how ‘TVTIC’, ‘Trading date time’, ‘Country of branch membership’ and fields 41-56 need to be populated. So it is essential that you fully understand the intricacies of this field and don’t fall into any of the following traps.

    ‘Segment’ versus ‘Operating’ level MICs

    The Market Identifier Code (‘MIC’) used to be a straightforward standard – you had one exchange and one four character code to identify it. For example, ‘XLON’ was the sole identifier for the London Stock Exchange. However, this was far too easy and exchanges are increasingly moving to a segment level structure resulting in a MIC for each segment. For example, the London Stock Exchange has ‘XLON’ as its ‘operational level’ MIC, but also has the following ‘segment level’ MICs:

    • AIMX – London Stock Exchange, AIM MTF
    • XLOD – London Stock Exchange, Curve Global Markets
    • XLOM – London Stock Exchange, MTF,
    • XLON – London Stock Exchange

    Golden Rules:

    1. Use the segment level MIC for transactions executed on a trading venue, systematic internaliser or non-EEA trading platform.
    2. Only use the operational level MIC where the segment level MIC does not exist.

    This is so important because if you used the operational level MIC by mistake, it will sail through ARM validation, but will probably result in a CON 412 error from the regulator. This is because the ISIN you have used in field 41 doesn’t only have to be on FIRDS on the trading date – it also has to be with the correct segment level MIC. So if you have traded an AIM stock, populated the ISIN correctly but have populated the Venue field with ‘XLON’ rather than ‘AIMX’, it will be rejected.

    The ‘XOFF’ versus ‘XXXX’ conundrum

    Another common error made by firms is in the use of ‘XOFF’ instead of ‘XXXX’ and vice versa. This is understandable as they sound similar and are both used for off market trades. In an effort to be precise, some of the language in the RTS can also appear confusing. It is absolutely essential that you understand the difference between the two as it can have a major impact on whether you need to populate the instrument identifier.

    Golden Rules:

    1. Use ‘XOFF’ for instruments that are tradeable on an EEA trading venue but where the trade has been made off market (i.e. not executed on a trading venue, SI or non-EEA platform).
    2. Use ‘XXXX’ for instruments that are not tradeable on an EEA trading venue and are traded off market (i.e. not traded on a non-EEA platform).

    Exchange MIC or ‘XOFF’/’XXXX’

    Another thorny issue we’ve discovered is the use of an exchange MIC when the trade was actually made off market. The Venue field should only be populated with the exchange MIC if the transaction was executed on a Trading Venue. Section 5.4 in the ESMA Guidelines document is a little complicated, but the key statement is “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.” So if you are making a transaction against a broker and that broker makes a trade on the London Stock Exchange to facilitate the trade, you should populate the venue field with ‘XOFF’ rather than ‘XLON’ as you are not the direct market facing entity.

    How we help

    Firstly, if you are unsure about any of the reporting standards, or just need a refresher, we would heartily recommend our core training course which will help ensure you are interpreting the MiFIR transaction reporting details correctly.

    If you have any doubt about whether you have been reporting correctly, this is what our Accuracy Testing is designed for. We can take all the transaction reports you have submitted over any given period and apply multiple tests for each data field that comprises a report. As many firms have discovered to their cost, there is no point hoping for the best when it comes to reporting. You need to have total confidence that your reporting is complete and accurate to avoid costly remediation and regulatory scrutiny. 

    • Please contact us for further details on our quality assurance, reconciliation, governance and training services.
  • What is shareholding disclosure compliance?

    What is shareholding disclosure compliance?

    Shareholding disclosure rules and the compliance that goes with them are not a new challenge by any means; there have been rules in some jurisdictions for over 50 years. However, the number of jurisdictions requiring compliance, the complexity of the rules and the sanctions for non-compliance are ever-increasing. 

    What are shareholding disclosures rules? 

    There are a number of different types of rules and they serve different purposes;

    • Substantial shareholding rules (also referred to as major shareholding and long disclosures) – these are designed to provide transparency to the market, the issuer, and the relevant regulator, about positions that are being accumulated, provide information on who can vote at the company’s AGM or who has access to voting rights.
    • Short position disclosures – these were first introduced in 2008 as a direct and immediate result of the financial crisis and in particular the HBOS rights issue whose share price was targeted by a shorting strategy resulting in a failed rights issue. These disclosures were designed as a way for regulators to have transparency of those responsible for shorting an issuer. 
    • Takeover disclosures – these were first introduced in the UK in 1968 to oversee the takeover and mergers of issuers as a result of the devastating consequences of dawn raids on issuers. Nowadays more and more jurisdictions have introduced these disclosure requirements, which allow additional transparency whilst a company is under offer to ensure fair treatment of shareholders.
    • Issuer Requests – in some jurisdictions issuers or their investor relations representatives are able to legally request disclosure of your holdings in their issuer and the identity of other parties to that position. This provides the issuer with transparency of their shareholders. 
    • Sensitive Industry – this can often be a pre-approval requirement before you trade in a certain industry above a certain threshold. These are industries that a government want to protect.  These often include the financial industry, defence, and aviation but other industries are affected too.  Restrictions on foreign ownership of issuers can also apply.
    • Articles of Association – companies may include lower thresholds for disclosure within their company’s articles of association and include their own sanctions for non-compliance.

    There are now over 95 jurisdictions that have some type of disclosure rules.  

    Who is subject to these shareholding disclosure rules? 

    Anyone who holds shares or derivatives of these shares (also referred to as financial instruments) can be subject to these disclosure rules.  These can be held in a number of different ways such as, but not limited to; nominee, custodian, prime broker, trading book, as a hedge to client trade, proprietary holdings, on a discretionary or non-discretionary basis for an asset management client.  Borrowed shares and those subject to a repurchase agreement can also fall subject to these rules. 

    Do shareholding disclosure rules in other countries apply to me?

    The short answer is yes!  The rule generally is if you invest in an issuer incorporated in another country you are likely to be subject to their disclosure rules.  There are other concepts involved such as Home and Host Member State, country of listing and country of primary exchange. 

    Are cash settled derivatives captured by these disclosure rules?

    Over the years’ regulators have become more concerned about cash settled derivatives and you will find they are increasingly included in a large number of rules. 

    What are the implications for non-compliance with the shareholding disclosure rules?

    Compliance with these rules is a necessity as the sanctions can be quite considerable.   There are public examples of sanctions as a result of non-compliance, however many sanctions are served privately and therefore they are never known to the wider public.  Here are some examples of the sanctions for non-compliance with shareholding disclosure rules; across much of Europe the sanctions include fines of up to €10 million or 5% of the annual turnover of the discloser and a suspension of voting rights for both the legal and beneficial owners. In Switzerland non-compliance is a criminal office and monetary penalties are up to CHF 10,000,000 (approx. €9.3m).  In South Korea non-compliance is a criminal offence and sanctions include fines, suspension of voting rights and imprisonment of up to 3 years for failure to disclosure and 5 years imprisonment for a disclosure that is false or omits any material information.  The sanctions in Hong Kong are similar but they also include personal liability of a company’s officers. 

    How do I comply with these rules?

    A mis-perception can be that the only difference in the rules are the percentage thresholds that trigger a disclosure, however there is much more to consider.  These rules are complex, and the methods used to calculate your exposure/holding  varies significantly from rule to rule from jurisdiction to jurisdiction. No two rules are the same. Accurate and timely disclosures are key to compliance in this area.  

    In order to comply you need access a global rules library, you also need to have a methodology for tracking and implementing rule changes. Once you have access to the rules you then need a way to calculate your exposure/position specific to each individual rule.  Because there are so many components to these rules the most effective way to reduce your operational and technical risk is to use a configurable rules engine for calculating your global disclosure obligations.  Any rules engine you chose needs to be flexible as there is no “one size fits all” in the world of shareholding disclosures, the solution needs to meet your specific corporate structure, exemptions that apply specifically to your business and any bespoke requirements your firm have, which can be a result of a number of factors including the application of specific legal advice you have received as there is no “one size fits all” in the world of shareholding disclosures.

    Compliance with these shareholding rules is not an easy task; however with our expertise in this specific niche area and industry experience (we’ve been in your shoes) we offer you with a solution that meets your needs and gives you peace of mind. 

     

    • For more information about our Shareholding Disclosure Service or to watch our short introductory video, visit our SDS service page.
    • For a demonstration of the system or a conversation with Angie Huff, please contact us. 

     

     
  • The SFTR Collateral Conundrum

    The SFTR Collateral Conundrum

    SFTR go-live is being hailed by many as a great success. On the banking side, the reporting firm’s ability to submit SFTR reports to trade repositories and have those reports accepted is seen as a significant achievement.

    Pairing and matching rates low

    Unfortunately, if you dig a little deeper, the picture is somewhat less rosy. The initial anecdotal evidence from market infrastructures and dealers is that pairing rates (where the UTIs and counterparties are the same) are quite low. The matching rates (where the further reconcilable fields match the counterparty) on loans are very low (with breaks in most empirical values where ESMA gives very limited or zero tolerance), and in many cases, the pairing of collateral reports is non-existent. Indeed, the trade repositories are mandated to make some aggregated data public on a weekly basis* – these figures corroborate the lack of matching, particularly of collateral. The reported data is also neatly summarised by ICMA in its weekly report. These findings will come as no surprise to many as SFTR requires firms to populate 155 fields, across four reporting tables and 10 action types with many complex rules to adhere to.

    Collateral reporting challenges

    At Kaizen, we predicted collateral reporting was going to be a particular challenge, and wrote guidance on this very subject for industry participants in the latest Securities Lending Times SFTR Annual. Furthermore, our award-winning ReportShield™ Accuracy Testing is now available for SFTR reporting to give you the confidence to stand by the quality of your reporting in dealing with reconciliation queries and in front of your regulators.

    Contact us for a conversation about your collateral reporting or SFTR reporting more generally with one of our regulatory specialists. 

    *(Opens to external websites).See: DTCC, KDPW.

  • James Deehan takes on the Talisker Whisky Atlantic Challenge

    James Deehan takes on the Talisker Whisky Atlantic Challenge

    In January 2020, Kaizen’s James Deehan and his team The Dorabros completed the Talisker Whisky Atlantic Challenge for the Teenage Cancer Trust. The 3,000 nautical mile row took the team an impressive 36 days, 10 hours and 31 minutes.

    We’re delighted to share their race video which follows their journey from the Canary Islands to Antigua.  

    You can also read James’ account on the highs and lows of the experience from sleep deprivation to seeing the most brilliant sunrises and sunsets. 

     

  • Well done to our SFTR Reporting Team!

    Well done to our SFTR Reporting Team!

    It’s been a big week for us and our clients with a new regulatory reporting regime – SFTR – going live.  As our Senior Regulatory Reporting Specialist for SFTR Jonathan Lee said earlier this week – while it’s an end for many project teams, for us here at Kaizen it’s only the beginning with the focus turning to the very reason we exist – improving the quality of the data reported to the regulator. 

    But first – we wanted to say a huge thank you to the core members of our SFTR Reporting team who’ve been working tirelessly for months to get our ReportShield™ quality assurance services ready to test our clients’ reported SFTR data for accuracy and timeliness.

    We asked them what they were most proud of about our SFTR assurance services.

    Tony Weedon – Regulatory Reporting Specialist

    “Having been with Kaizen for just over six months, I am most proud of the unique testing methodology that underpins our services and the fact that we have not shied away from the significant challenges that SFTR poses compared to other regimes.  In fact we have embraced that challenge to not only provide a unique service but be the best in market.  The 100% commitment of everyone to get it right, to give the client the best experience possible to the highest standard, makes me feel proud to be part of Kaizen.”

    Sam Jackson – Data Analyst

    “SFTR is a highly complex regulation, quite distinct from EMIR and MiFIR.  It’s been a great privilege to build testing for a new regime from the ground up.  I’m also extremely proud that, as part of our ReportShield™ Accuracy Testing, we include an additional value-add that shows the reporting fields clients should focus their attention on most, to improve their reporting accuracy.”

    Jiaqi Song – Data Analyst and Developer

    “Our services combine our regulatory specialists’ extensive expertise with advanced technology, enabling clients to identify potential issues in their reporting. Developing SFTR testing has been challenging because it’s a new regulation and many tests can’t be built in the same way as those traditional jurisdictions such as EMIR or MiFIR.  SFTR also requires additional reference data which does not exist in existing databases which has also been a challenge.”

    Jonathan Lee – Senior Regulatory Reporting Specialist

    “SFTR is not rocket science but the level of detail (with up to 155 fields across four reporting tables and 10 action types) is unprecedented.  Our ReportShield™ Accuracy Testing is uniquely comprehensive and powerful in helping firms achieve compliance with SFTR reporting obligations. I believe no other firm can offer a service so focused on reporting accuracy and quality.”

    For a conversation about your SFTR reporting accuracy with one of our regulatory specialists, please contact us.

  • ESMA releases new EMIR and MiFIR Q&As

    ESMA releases new EMIR and MiFIR Q&As

    Hallelujah, it’s positively raining regulatory reporting Q&A!

    Yesterday (8 July), ESMA published new Q&As for both EMIR and MiFIR data reporting. However, you can put away your brollies as there isn’t a great deal happening in either of them.

    EMIR – amendment to TR Question 11(b)

    The EMIR Q&A makes an amendment to TR Question 11(b) to clarify that counterparties should follow their local time and the relevant calendar of their member state to specify the “working day”  in the context of determining the deadline for reporting under EMIR. Of course this does not alter the fact that all timestamps in the EMIR trade report fields should be expressed as Coordinated Universal Time (UTC).

    MiFIR – two reporting scenarios added

    The only addition in the MiFIR Q&A is the addition of two reporting scenarios where an investment firm executes a transaction through an execution algorithm provided by another firm (Transaction Reporting Question 13). We would note that it is essential to carefully read footnote 51 in the Q&A in order to fully understand the reporting scenarios.

    If you have more questions than answers on EMIR trade reporting and MiFIR transaction reporting, our training courses can help you avoid some of the pitfalls of these complex regulatory reporting regimes. During the lockdown period, we are offering these courses remotely at a significantly reduced cost. For more details, please see our training pages. 

  • Less than a week to go until SFTR go-live, what should firms be doing?

    Less than a week to go until SFTR go-live, what should firms be doing?

    Four and a half years after the SFTR regulation was published, we are finally looking at the go-live for investment firms in just under one week’s time!

    I don’t doubt that many operations managers, project leads and regulatory reporting teams wish they were better prepared for 13 July. Final UAT testing is still going on, final system changes and enhancements are still being made but day one looks likely to be far from perfect.

    At this moment, it is important to take stock. Having an understanding of what doesn’t work, what is not going to be reported, what isn’t going to be reported correctly and what controls are not in place will be more fruitful than knowing what works.

    Controls are often the first thing that gets sacrificed in any rushed regulatory go-live. And go-live under lockdown after a less than generous three-month delay is likely to come at the detriment of controls more than ever.

    As we enter the final week, the importance of governance, control frameworks, action plans, management information and periodic regulatory testing cannot be overstated. Ensuring that it is not the same minds perpetuating mistakes that were made in the initial regulatory interpretation and build; that they have independence, is also key to the effectiveness of regulatory testing and controls. 

    At Kaizen, our multi-award winning ReportShield™ quality assurance services are designed to do just that. Our testing and controls have been tailored for SFTR to give you full visibility of the quality of your reporting – giving you confidence that you’re compliant with the reporting obligations.

    Contact us for a conversation about your SFTR reporting accuracy and completeness.

     

  • What’s it like starting a new job during lockdown?

    What’s it like starting a new job during lockdown?

    A huge welcome to our six new Kaizeners who’ve joined us during the past few months of the UK’s lockdown.  Welcome to – from top left across:

    • Andy Nottingham – Information Security Manager
    • Shirley Lau – UI/UX Designer
    • Nicolas Dotto – Software Engineer
    • Costandia Josif – Sales and Onboarding Specialist
    • Yiesse Bading – Sales and Onboarding Specialist
    • Karolina Kondzielewska – Senior Software Test Engineer.

    We asked three of our new joiners – Shirley, Yiesse and Costandia – what it’s been like starting a new job when you haven’t even met your new teammates, or in some cases your manager, face-to-face. 

    How challenging has it been to start a new job during lockdown?

    Shirley: It hasn’t been too challenging as I think everyone at Kaizen has really put in the extra effort, whether it is reaching out to me to ask if I need anything or just a casual chat. So I’ve been really lucky to have new supportive colleagues.

    Yiesse: I didn’t really know what to expect in terms of being onboarded remotely. But my onboarding was well structured and organised; my work is also planned through my daily meetings and I had different individual and group video calls which made things much easier than I thought.

    Costandia: Surprisingly enough, I have not found starting a new job remotely as challenging as expected. It is difficult not having that human interaction of course, however video calling does the job and we can carry on building these relationships when we are finally allowed to meet in person. As an employer Kaizen has made sure I have everything I need to work effectively and comfortably from home.

    What have you learned and what advice would you give others who might be starting a new job under similar circumstances?

    Shirley: Working from home is always challenging as it is easy to get distracted or have work time quickly run into your evenings but I have worked from home before and find it much more productive when you are disciplined and keep to a set working period and time slots for breaks. I’ve also learnt to not be afraid to reach out and have a chat with colleagues outside of the direct team. I think having daily stand ups gives a great insight on what everyone is working on.

    Yiesse: Through this experience I learnt that a company’s atmosphere is detectable despite not being able to be in the office or meet in person. Through the different video calls and messages I could feel the warm welcome of my colleagues. My advice to anyone starting a new position under the same circumstances is to be open, to not hesitate to ask questions and to share your thoughts.

    Costandia: Life can change at any time so being able to adapt is really important. Try to find little positives every day such as being able to wear your PJs to work or having the company of your two little French bulldogs. From somebody who comes from a busy and loud Greek household – don’t let the background noise distract you or make you feel uncomfortable whilst on a call as everyone is in the same boat. Starting a new job from home actually takes away the overwhelming feeling of having to meet so many people all at once! Just embrace it and make of it what you can.

    To find out more about our brilliant staff members please visit our Meet the Team page.

  • EMIR Refit implementation: What June 18 means for you

    EMIR Refit implementation: What June 18 means for you

    ESMA provides additional detail in latest Q&A

    June 18 is a key date in the calendar for EMIR trade reporting.  Financial counterparties (FCs) will become legally liable for the timely and accurate reporting of OTC derivatives contracts for themselves and their NFC clients below the clearing threshold (NFC-s).

    This sounds like good news for NFCs and it appears to meet one of the EMIR Refit’s major objectives in making its compliance burden on firms more proportionate, particularly for the non-financial counterparties (NFCs). However, the devil is always in the detail and it can be argued that it has actually increased the compliance burden on financial counterparties without offering enormous benefit to the NFCs.

    What are the problems?

    The first problem is that the FCs are only obligated to trade report on behalf of their NFC- counterparties; not those NFCs above the clearing thresholds. As NFCs can move above or below the clearing threshold over time, this becomes a moving target which clearly needs to be taken into consideration and monitored.

    Secondly, whilst EMIR requires the reporting of all derivatives, the FC is only obliged to report OTC derivatives on behalf of their NFC- clients; not the exchange traded derivatives (ETDs). Whilst it is more likely that an NFC- will trade OTC rather than ETD, those that do trade ETD need to be aware that their counterparty is not obligated to report these and they may be required to continue reporting. If the NFC- has to continue reporting ETDs, there will be precious little savings for them as they will have to maintain their reporting infrastructure.

    To compound these issues, the NFC- may choose to continue reporting trades itself either by asset class or in total. This means their FC counterparties need to be aware of what they are required to report as a duplicate report must not be sent to a trade repository.

    Trade repository migration

    As there are multiple trade repositories, it is very possible that the FC and their NFC- clients will be using different repositories. It is probable that the FC will not want to report to multiple repositories as this will involve multiple contracts and workflows – it will make far more sense for the FC to send all the reports to a single trade repository. The big issue here is that it is not simply new trades from 18 June that need to be reported – it is also any modification or termination of existing contracts still open. This means that any open trades and positions will need to be migrated from the trade repository used by the NFC- to the trade repository used by the FC. The trade repositories have been busy planning for this data migration, but they cannot perform magic – it is essential that firms should inform trade repositories what reports should be migrated well in advance of 18 June. 

    Communication is key

    It is absolutely essential that the FCs and their NFC- clients communicate and agree what needs to be reported by the FC and what needs to be provided by the NFC-. There might be a temptation by the NFC- to assume they no longer have any role to play in trade reporting as the FC is legally liable for the timely and accurate reporting. This is not the case. The NFC- has to provide the FC with “the details of the OTC derivative, which the FC cannot be reasonably expected to possess”. The latest Q&A from ESMA details ten data items that the NFC- will need to provide. In practice some of these will be ‘static’ data items that will apply to all trades and some other items may not be applicable. Perhaps the key item that the NFC- needs to consider is its Legal Entity Identifier (LEI). It is the NFC-‘s responsibility to ensure that the LEI is renewed every year – if it doesn’t, the trade report will be rejected by the trade repository.

    This is not the end of Refit!

    ESMA is currently consulting on changes to the Implementing Technical Standards to bring them into line with international standards proposed by CPMI IOSCO. There are many sensible proposals in this consultation, but firms may judge some of the proposed changes to be less sensible than others. We are preparing an additional blog detailing their potential impact, which could be as significant and onerous as the changes to the reporting technical standards in November 2017.

    For a conversation with one of our regulatory specialists about your EMIR reporting accuracy and assurance requirements, please contact us. 

  • FCA publishes Market Watch 63

    FCA publishes Market Watch 63

    The FCA signals that it will not relax its demands for complete and accurate transaction reporting.

    In its latest newsletter on market conduct and transaction reporting issues, the FCA sets out its expectations of market conduct in the context of increased capital raising events and alternative working arrangements due to Covid-19. The focus of the newsletter was firmly on market abuse however there was a very clear message that transaction reporting is a key tool in its efforts to combat market abuse.

    While the FCA acknowledged the operational challenges created by the Covid-19 crisis, it also made clear its intention to continue to use its powers to request information and “may ask market participants to provide further information on their activities to explain how they are meeting their regulatory obligations”.

    Right controls around market abuse

    Market Watch 63 stresses that it is “as important as ever that the right controls around market abuse” are in place and we believe that this extends to transaction reporting. These controls are clearly detailed in Article 15 of RTS 22 and if you are not regularly performing quality assurance testing and reconciliation of FCA data against your source system records, you are not meeting these requirements.

  • EMIR, MiFIR, SFTR Reporting Core Training – new course dates announced

    EMIR, MiFIR, SFTR Reporting Core Training – new course dates announced

    We’re pleased to announce new dates for our CPD-accredited EMIR, SFTR and MiFID/MiFIR Reporting Core Training Courses which we are delivering remotely. 

    Developed and delivered by our regulatory specialists David Nowell (EMIR and MiFIR) and Jonathan Lee (SFTR), these popular half-day courses are also at a significantly discounted price for a limited time only!

    Click on the links below for more details and to book your place.

    Training is an integral part of the systems and controls that firms need to have in place around reporting. Despite the coronavirus pandemic, regulators have made it clear that they are monitoring the quality of regulatory reports closely. 

    If you have any questions about our training courses or for enquiries about bespoke options, please email our Training Team. 

  • Social distancing on the Atlantic Ocean

    Social distancing on the Atlantic Ocean

    As many of us adapt to self-isolation, which can mean either being solitary or cooped up with family or friends, we have been reflecting on a great triumph Kaizen employee James Deehan achieved just a few months ago. Taking social distancing to the extreme, on 12 December 2019, James and three of his friends (also known as the Dorabros) rowed across the Atlantic Ocean as part of the Talisker Whisky Atlantic Challenge. The 3,000 nautical mile row from La Gomera in the Canary Islands to Antigua took them 36 days, 10 hours and 31 minutes. In this blog, James reveals the highs and lows of his incredible Atlantic adventure in aid of the Teenage Cancer Trust. 

    What comfort did you miss most being away from dry land?

    “I missed clothing the most. We opted to race as light-weight as possible and that meant getting rid of any non-emergency clothing. What I would have given for a tee-shirt or jumper to shield me from the frosty Atlantic trade winds or a poncho to protect me from the walls of water that would wash over us in the 3am shift!”

    What was the most challenging aspect of the row?

    “The sleep deprivation was by far the most challenging thing about the row.  We rowed in two hour shifts – two hours on, two hours off for 24 hours. I was in charge of navigation and power in my off-shifts. Combining this with the cabin being roasting in the day, it basically limited my sleep to a maximum of five hours in every 24 and in very broken intervals. Physically, multiple times a shift the oar would smash into a shin with the weight of the boat behind it, often breaking the skin. In addition to my shins I also ended up with pretty bad nerve damage in my hands and tears in both my Trapezius muscles which still haven’t quite repaired.”

    What was the best thing you saw whilst rowing?

    “It would be difficult to narrow it down to one. The ocean fauna is incredible – we saw countless Spinnaker dolphins, Dorado (our team’s namesake), two enormous Leatherback turtles, two even bigger Mako sharks, a whale popped up to say hello on new year’s day and a butterfly landed on Lirim’s hand on Christmas Day. The sunrises and sunsets were like none I’ve ever seen – blood red skies, warm orange hues and violet tinted clouds. However, for me it was the stars. We had studied them extensively through our celestial navigation course and knowing that they had guided generations of seafarers across the same waters we were now at the mercy of, was a special thought.”

    Would you recommend the Talisker Whisky Atlantic Challenge to others?

    “It’s definitely not for the faint hearted. We prepared for two years solid and are all slightly unhinged! They say that the ocean will bring out the best or the worst in you – either way you’ll learn a lot about yourself. If you have the appetite and can smile while under extreme duress, no experience could be the same.”

    Why is raising money for Teenage Cancer Trust so important to you and how much have you raised so far?

    “The Teenage Cancer Trust is a phenomenal charity that focuses on the needs of young people in the UK who are fighting cancer. It means a lot to our team because whilst at school, a fellow student lost his life to cancer and it devastated the community. We realised we could make a huge difference – to date we have raised £94,000. We have a few events coming up and hope that they will help us push over the £100,000 mark!”

    In addition to rowing the Atlantic Ocean, James and his fellow Dorabros team members have had a busy year. As if rowing 3,000 miles wasn’t enough, they’ve run the Marathon des Sables (a 250km desert ultra-marathon), swam the English Channel, completed an Ironman triathlon and cycled from Rome to London. You can help them reach their fundraising goal here.

    Follow James and the Dorabros adventures.

    Images: Atlantic Campaigns

  • SFTR – the day that wasn’t

    SFTR – the day that wasn’t

    Today was going to be the day…

    For those of us involved in SFTR reporting, Easter was cancelled, last minute testing was to be cast aside and reporting was going into production. The initial report was expected to be small given that it was to cover securities financing transactions trading during the period Easter Saturday to Easter Monday but nevertheless we all waited anxiously in case of the inevitable teething problems that occur.

    Instead, the world was plunged into crisis and an unexpected delay has happened. It will be more than four and a half years from the publication of the regulation to go-live for the now combined first and second phases – Banks, CCPs and CSDs. Crisis or not, this is a great gift for an industry that was not entirely ready for this regulation to become a reality.

    Here are the top three things that banks should be doing to ensure that the additional three months are maximised:

    1. Test, test, test

    Like Covid-19, the key to reporting accuracy is testing, testing and more testing. Once satisfied that SIT and UAT testing are functioning correctly internally, with files passing the trade repository validation rules and ideally independently checked for completeness and accuracy, then it’s time to test with counterparties, market infrastructures, triparty agents, agent lenders and across the industry.

    2. Put the right controls in place

    Controls around reporting should never have been a Day 2 delivery but invariably were destined to be with an April go-live. This excuse has now gone. Therefore, SFTR reporting should have a full set of procedures, reporting policy and decisions made should be fully documented. A testing and reconciliation plan should be put in place internally, with appropriate management information in place to cover reporting completeness, timeliness, trade repository receipts and reconciliation breaks and the closure of those breaks.

    3. Don’t mark your own homework

    Implementing an independent quality assurance layer through periodic regulatory testing will ensure the regulation, technical standards, guidelines and updates have been implemented correctly and remain correctly interpreted as they and the business evolves. It will ensure that the firm is not marking their own homework and losing sight of the less obvious reporting issues they face. It will also reassure key stakeholders and national competent authorities that the regulatory obligations are taken seriously and managed most efficiently.     

    We are helping a number of firms prepare for SFTR reporting including pre go-live accuracy testing of reports as well as providing a full suite of post go-live assurance services to ensure the accuracy and completeness of your reporting.

    Contact us for a conversation with one of our regulatory experts.

    Join our Kaizen community of regulatory reporting professionals for blogs, events and insights from our regulatory subject matter experts.

  • SFTR latest developments: COVID-19 delays, backloading, MiFID II reporting of SFTs, and a new best practice guide…

    SFTR latest developments: COVID-19 delays, backloading, MiFID II reporting of SFTs, and a new best practice guide…

    In amongst the backdrop of this very human and truly global crisis, it has been refreshing to see how innovative and productive our sector of the financial services industry has remained. Efforts continue to ensure that banks and other securities financing transaction counterparties are able to comply with SFTR reporting requirements. Banks will be joined by market infrastructures in going live on 13 July, while the buy-side will follow on 12 October and non-financial counterparties from 11 January 2021.  

    Following the announcement from ESMA on 19 March regarding efforts to delay the first phase of SFTR reporting, there have been further announcements and clarifications to aid the industry during these difficult times. The particular challenge that ESMA has faced has been in how to enact appropriate changes and delays in a suitably technical way to avoid needing executive approval from the EU Parliament, Council and Commission.

    Backloading is no more

    Backloading has become a particular area of concern and confusion. But we can now say with confidence that backloading (the need to report transactions that were opened before go-live date and still open 180 days later) has been removed as a requirement across all phases of reporting.

    ESMA attempted to clarify this as best it could with an update to the initial public statement on 26 March which stated, “ESMA therefore expects competent authorities not to prioritise their supervisory actions towards counterparties, entities responsible for reporting and investment firms in respect of their reporting obligations pursuant to SFTR or MIFIR, regarding SFTs concluded between 13 April 2020 and 13 July 2020, and SFTs subject to backloading under SFTR, and to generally apply their risk-based approach in the exercise of supervisory powers in their day-to-day enforcement of applicable legislation in this area in a proportionate manner.”

    Much more telling have been the conversations that ESMA has had with trade associations such as ICMA and ISLA and in statements from certain national competent authorities (NCAs). The French regulator (AMF) has been most explicit in stating “Concerning the backloading obligations and following ESMA’s update, market participants are expected to focus exclusively on the reporting of SFTs concluded on or after 13 July 2020.” Other NCAs have also provided off the record feedback to the trade associations to the same effect.

    MiFID II reporting of SFTs with ESCB members is also put back until 13 July 2020

    The ESMA statement above also helps clarify that in line with the delay to SFTR reporting, the need to provide MiFID II RTS 22 Transaction Reports in relation to SFTs facing European System of Central Banks (ESCB) counterparties. These reports are also not required from banks, investment firms and credit institutions until 13 July 2020.

    ISLA issues SFTR Best Practice Guide  

    ISLA published its SFTR Best Practice Guide earlier this week to assist securities lending market participants with their SFTR reporting. The online guide explains how to apply the regulatory technical standards across the SFTR counterparty, loan & collateral and collateral re-use data tables and how to populate each respective field. While only available to ISLA members at present, this provides a good complement to the ICMA Guide to Reporting under SFTR which is freely available.

    We are helping a number of firms prepare for SFTR reporting including offering pre go-live accuracy testing of reports as well as a full suite of post go-live assurance services. Contact us for a conversation with one of our regulatory experts.

     

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

  • EMIR: Lies, damned lies and trade repository statistics

    EMIR: Lies, damned lies and trade repository statistics

    Earlier this month ESMA published its Supervision Annual Report 2019 and Work Programme 2020. These reports are always interesting to gauge ESMA’s view on the adequacy of the quality of trade data reports (and what it’s going to do about it if the data doesn’t reach the required standard).

    How to measure EMIR reporting data quality

    ESMA describes the pairing and matching process as “one of the key data quality processes”. EMIR is a two-sided reporting obligation, i.e. both counterparties to a trade have to report their ‘version’ of the trade. If both sides report it with the same unique trade identifier and counterparty identifiers, then it will ‘pair’. If both parties report with the same common data attributes (such as quantity and price), then it will ‘match’. Clearly, if the trades don’t pair or match, then there is a data quality problem with the report from one or both of the counterparties.

    So the pairing and matching statistics are key data quality metric. Unfortunately, the pairing and matching rates quoted in the report – 59% and 29% respectively – might suggest the quality of the reports is not up to the required standard.

    Is EMIR reporting data quality improving?

    In its 2018 Annual Report, ESMA stated that, as of September 2018, the average pairing rate across trade repositories (TRs) was 86%. We also know from a Freedom of Information request, that the average matching rate was 40%. This suggests that the quality of trade reports has decreased substantially. However, this is where we need to consider Disraeli’s view of “lies, damned lies and statistics” and be very careful with the story they tell. The 2018 pairing figure was derived from information provided by TRs and measured the rates against trade reports. The 2019 figure in the latest report is actually derived by ESMA based on the ‘trade state reports’ at a single point in time, so we are not comparing data produced using the same methodology.

    Use of the trade state report (TSR) is a very interesting choice. The TSR, as the name suggests, is the latest state of a trade, taking into consideration subsequent modifications such as partial terminations. It sounds like a sensible methodology, but it has a big issue when it comes to exchange traded derivatives (ETDs). Unlike most OTC derivatives, ETD trades are immediately netted into a position level report. So the TSR for an ETD is actually a position level report rather than a trade level report. The significance of this is that, unlike trade reports, there is no agreement yet between the counterparties on what UTI to use on a position level report. Therefore, there is a significant probability (I calculate it at 85.256%) that the pairing rates for ETDs is very low.

    However, there is a more important issue related to these statistics (both pairing and matching) – do they or do they not include delegated reports? With delegated reporting, one party reports on behalf of both counterparties – ie. it would be difficult for the reporting counterparty not to report trades that both pair and match. So, for the statistics to not be potentially misleading, we need to know the pairing and matching rates for non-delegated reporting.

    Another interesting statistic in the annual report is the top reason for non-matching fields. Bearing in mind that these top ten breaks are for TSRs as of 9 August 2019, some of the fields, such as Product_ID_2 haven’t existed since November 2017. It is unclear what value offering statistics against fields that can no longer be corrected, actually delivers.

    What is the true state of EMIR reporting data quality?

    At Kaizen, our ReportShield™ assurance services test every field in every single trade state report to ensure that they are populated in accordance with the regulatory technical standards and the ESMA Q&A. We can also test the consistency of all the trade reports submitted against the actual values of the position level report.

    If you are in any doubt about how the quality of your EMIR trade and position level reports measure up, contact us. 

     
  • ESMA pragmatism allows three-month COVID-19 delay to SFTR implementation

    ESMA pragmatism allows three-month COVID-19 delay to SFTR implementation

    ESMA has stepped up in light of the current COVID-19/Coronavirus crisis.

    Following the joint appeal to ESMA and the European Commission by ICMA and ISLA on Monday 16 March, ESMA has today announced a three-month delay to SFTR implementation. They have created this technical delay in three steps:

    1. Requesting that National Competent Authorities do not prioritise supervisory actions until 13 July 2020
    2. ESMA not registering any Trade Repositories (TRs) ahead of 13 April 2020
    3. Stating that ESMA will also not be available to record details of Securities Financing Transactions (SFTs).

    These three actions ensure “counterparties, entities responsible for reporting and report submitting entities will be unable to report by the reporting start date.”

    “ESMA expects TRs to be registered sufficiently ahead of the next phase of the reporting regime, i.e. 13th July 2020 for credit institutions, investment firms, CCPs and CSDs and relevant third-country entities to start reporting as of this date.”

    The ESMA public statement has the full details.

    Kaizen is offering quality assurance testing as well as core training on the reporting obligations. Get in touch to find out more about how we can get you ready for reporting under SFTR.

  • Trade associations publish EMIR reporting ‘best practices’

    Trade associations publish EMIR reporting ‘best practices’

    The trade associations ISDA, EFAMA, EVIA, FIA, GFMA, and GFXD have published ‘Best practice’ guidance for firms on how to populate fields in EMIR trade and position reports. The best practices, released on 3 March, cover both OTC and ETD “and were developed to improve the accuracy and efficiency of trade reporting and to reduce compliance costs”.  If firms follow the new guidance it should also improve the matching rates between the counterparties when they submit a report referencing the same trade (both counterparties have to report their version of the trade and ESMA uses the ‘match’ statistics as a quality indicator).

    The trade association initiative should therefore be applauded as many firms believe there are gaps in the regulatory technical standards and the ESMA Q&A that require the firms to make an interpretation on how the field should be populated. Historically, the matching rates have been disappointing and the new best practices document should help them arrive at the same interpretation of how the fields should be populated resulting in an improvement in matching rates.  However, a number of issues remain:

    Legal status of the best practice document

    In short, it has no legal status as it is not endorsed by ESMA. So although it is a very helpful as an educational document for the industry and it should help improve the matching rates, there is no guarantee that the regulators will consider all the interpretations to be correct (although the trade associations have discussed the best practice document with regulators).

    Potential contradictions with the ESMA requirements (e.g. Clearing member ID)

    This is a difficult one. For example, take ‘Clearing Member ID’. The trade association best practice for ETDs is that this field shall only be populated in instances where the reporting party is not the clearing member. This makes perfect sense to me. Unfortunately, ESMA’s Q&A answers the question: If a counterparty is itself the Clearing Member (CM) to a trade, should it be reported in both the “counterparty” and “CM” fields?” with ‘yes’.  Since the trade association best practice seems aligned with the RTS, rather than the Q&A, perhaps it’s safe to follow best practice.

    However, there are other instances where there seems to be divergence from the Q&A that doesn’t have the clear and obvious support of the RTS. For example, the ETD best practice for deliverable currency is that it should only be populated where the asset class is ‘CU’ for currency. Again, this seems sensible, but TR Q 47 says the field should be populated ‘for all single currency derivatives, as well as those with a specific FX component.’

    Gaps in the best practice document

    Whilst the document provides best practices for many fields, it is not comprehensive. For many fields, best practice is not required – for example, it should be obvious to all how to populate ‘Reporting counterparty ID’ (although we still see a number of errors with this field!). There are a number of others, such as ‘Beneficiary’. ‘Report Tracking Number’ and the infamous ‘Position Level UTI’, where best practice is required. However, trade associations need to complete discussions with ESMA before they can provide best practice for all fields.

    Will all participants adopt the best practices?

    Best practices will only increase the matching statistics if all participants follow them. It is impressive that seven major trade associations have reached agreement on best practices for a number of the fields. However, not all participants will be represented by these trade associations. For example, the CCPs may have differing views. Perhaps this is best evidenced with the ‘Maturity Date’ field where the best practices document notes: “Reporting firms populate this field with the ‘last trade date’ which conflicts with CCP’s interpretation of this field. Most CCPs populate this field with ‘settlement date’.  Regulatory guidance required.”

    So in our view the best practices document is a valuable tool to help firms increase the quality and matching rates of their EMIR trade reports. However it is not a panacea for the myriad of EMIR trade reporting difficulties. As we have said before there are some fundamental issues that make EMIR trade reporting more of a burden than it should be for firms and less valuable than it should be for regulators.

    If your EMIR reporting isn’t up to best practice, we can help. Please get in touch for a conversation with one of our regulatory experts to find out more.

    Our EMIR reporting core training courses also cover all aspects of the reporting requirements to gain an excellent overall understanding of the scope, drivers, trading scenarios and key fields that make up an EMIR report.  Book your place now.

     
  • CFTC / Dodd Frank Reporting gets a KISS

    CFTC / Dodd Frank Reporting gets a KISS

    Since 2017 we have been hearing about the CFTC’s Project KISS, which means ‘Keep it simple, stupid’. The thinking behind the initiative is that complexity and quality are inversely related, so if you want high quality data, the complexity needs to be low.

    With that in mind, the rules surrounding SDR reporting were well overdue a revisit. On 20 Feb, a little late for Valentine’s Day perhaps, parts 43, 45, 46 and 49 of the Dodd Frank Act got the kiss they were waiting for when Chairman Heath P. Tarbert announced the proposal of simplified reporting rules.

    So, just how simplified are the proposed rules and what changes are reporting counterparties going to have to prepare for?

    Well the big winners could be the smaller businesses. That is the non-swap dealers and non-major swap participants. Their reporting deadline could move to “T+2” and it’s been suggested that their requirement to report valuation data for open contracts every quarter should be removed. There’s harmonisation with EMIR here as small Non-Financial Counterparties do not need to report valuation data under this regime.

    There’s no such luck for the bigger reporting entities though as their requirements are actually increasing. Also in line with EMIR, the CFTC is proposing that collateral margins are reported too. This is clearly data that the regulators feel is important to monitor systemic risk.  In 2012 when part 45 initially went live margin data was believed to be too complicated to collect due to the fact that it is mostly dealt with on a portfolio basis.

    Mandatory LEIs

    The new reporting rules could also mandate LEIs for both reporting entities and their counterparties.

    This sounds familiar doesn’t it? We’ve seen several regulatory regimes do this already and the question about who is responsible for ensuring your counterparty has an LEI always crops up. The answer is usually the same, third party registration of an LEI is easy so there is no real excuse for identifying your counterparty without an LEI.

    It’s also being suggested that voluntary reporting is binned. The CFTC has been inundated with garbage data received under the premise of voluntary reports. The CFTC is now looking for quality over quantity and reporting firms will need to ensure they are not over-reporting.

    Other proposed changes – goodbye USIs, hello UTIs, reportable fields

    USIs are set to become a thing of the past with the new proposals as the more generic UTI takes over.

    The CFTC also recommends that where a trade is reportable to multiple jurisdictions that the same UTI should be used for global reporting.

    The proposed rules also provide a finite list of 116 reportable fields in part 45 and 90 in part 43. This is probably the most welcome change to the new rules as firms have been struggling to truly know what trade data regulators really want. Heath P. Tarbert even said in his statement, ‘We have essentially asked [participants] to decide what to report to the CFTC, instead of being clear about what we want.’

    Improved data quality?

    If all these changes are implemented the CFTC certainly will begin to receive data of a much higher calibre than they do today. However, simplifying the rules is still changing the rules and change is always a tricky task to co-ordinate. Firms will need to plan carefully to make sure they meet new requirements correctly and above all – test their data!

    Hint: Kaizen can help with this

    The comment period for the proposed rules ends in May 2020 with the likelihood being that reporting under them will commence towards the tail end of 2020. The DTCC re-architecture of its US repository is tactically planned to align itself with the kissed Dodd Frank rules.

    x

  • Post-Brexit regulatory reporting wish list: EMIR trade reporting

    Post-Brexit regulatory reporting wish list: EMIR trade reporting

    We recently speculated that now might be a good time to think about what changes you might want to see in the UK reporting regimes at the end of the transition period. The UK Chancellor’s assertion that he is seeking “outcomes based” equivalence rather than complete alignment appears to have left the door ajar for some sensible changes to the reporting regimes.

    Previously I shared my top ten suggestions for changes to the MiFIR transaction reporting regime. Now it’s time for my top ten changes for EMIR trade reporting which I believe will make reporting more proportionate for firms without degrading regulator’s ability to use the data for the intended purposes. In fact, some of them may help increase the quality of the data for the regulators:

    1. Eliminating trade reporting for ETDs

    Since the main purpose of EMIR trade reporting is to monitor for systemic risk, there appears to be little value in collecting reports of ETD trades when they are immediately netted into an end of day position report. Additionally, key elements of EMIR trade reporting like lifecycle events and collateral reporting can only really be sensibly applied to the end of day positions for ETDs. Perhaps the only value of ETD trade reports is for the detection of market abuse – but this is the driver behind MiFIR transaction reporting and their inclusion in EMIR is an expensive duplication.

    1. Review some of the roles of the trade repositories (TRs)

    The trade repository ‘layer’ between firms and the FCA appears to be a potential hindrance for the regulator as it needs to access multiple databases which may have their own systems and fields. It would also help the production of useful public data aggregations from a single source and reduce problems in performing the pairing and matching reconciliations. Having multiple TRs appears to increase risks, so given that the regulators have the ability to act as the single repository themselves as the FCA has demonstrated with MiFIR transaction reporting, it should now be reviewed.

    The entities behind the TRs can still have an extremely important role to play, but this would be more akin to the role that ARMs have in helping firms report to the NCAs.

    1. ‘Beneficiary’

    “The party subject to the rights and obligations arising from the contract…” Is there a situation when this party is not going to be the reporting counterparty! OK, there is a small case where it could be argued that a sub-fund could be the beneficiary rather than the reporting fund counterparty, but does this really justify the confusion this seemingly superfluous field causes?

    1. Reporting Timestamp

    “Date and time of reporting to a trade repository”. This used to be populated by the trade repositories as it is the same as the time they receive it. Asking firms to report this field is duplication and leaves firms exposed to making errors.

    1. Trading Capacity

    For EMIR, we have ‘principal’ and ‘agent’ as possible values. However, we are told that only principals to a trade need to report; not any party acting as agent. This field has no value other than to cause confusion in interpretation and should be removed.

    1. Don’t ask for data you’ve already got

    It sounds obvious, but there’s no justification for regulators to ask firms for data that they already have. It creates the potential for firms to supply different data to the ‘golden source’ – do the regulators think it would be a good idea to use this sub-optimal data rather than the pristine data they have? For example, the regulators will already have reference data collected from EEA trading venues (even post-Brexit) for ‘product classification’, ‘underlying identification’, ‘notional currency 1’, notional currency 2’ ‘delivery type’, ‘price multiplier’ and ‘maturity date’ where the instruments is tradeable on an EEA trading venue. If the instrument is an OTC derivative and has an ISIN, a golden source of this data is also available on the ANNA DSB.

    1. Country of the other counterparty

    “The code of the country where the registered office of the other counterparty is located or country of residence in case that other party is a natural person” So, similar to the argument in point six, this information is contained in the GLEIF database for organisations. Asking firms to populate this field for organisations is again unnecessary (firms cannot deal with an organisation unless they have an LEI).

    If the counterparty is an individual, why ask for the country of residence? For a start, it is different from the equivalent field for MiFIR. Additionally, natural persons often have multiple residences and move around. It is difficult to understand how collecting the country of residence for natural person counterparties can be of any use for monitoring systemic risk.

    1. Basket derivatives

    Firms executing transactions in OTC basket derivatives have to populate the underlying ISIN field with all the ISINs that comprise that basket (similar to, but not the same as MiFIR). For example, if they trade a pharmaceutical basket comprising 421 stocks, they have to populate the ISINs of all 421 stocks. Since there is no information of the individual stock weightings, it is extremely difficult to see how any regulatory authority can use the data to help monitor systemic risk. This is very onerous for firms and can be of very little value to the regulators.

    1. Duplicate fields

    There are a number of required fields that can be derived from other fields. For example, the information provided in a CFI code (Classification of the financial instrument) renders the following mandatory fields obsolete:

    • Contract type
    • Asset class
    • Delivery type
    • Option type
    • Option exercise style
    1. Report tracking number (RTN)

    “A unique number for the group of reports which relate to the same execution of a derivative contract”. At Kaizen, we can find very little evidence of this field being populated for the scenarios described in the ESMA Q&A. Where it is mandatory, for the action type of ‘position component’ at a trade level, our findings show that there is a common failing to assign the same code to all the trades that comprise a particular position report. If the field is only mandatory for trades that are going to be netted into a position report, it is questionable whether this troublesome field offers any real value to the regulators.

     

    So these are my top ten and again I have to add the caveat that there may be perfectly valid reasons why the regulators need this information. However, there is a view in the industry that the EMIR trade reporting regime needs a fundamental review rather than simply tinkering round the edges. Nobody can deny the importance of a reporting regime to monitor for systemic risk, but the poor quality of much of the data reported and the lack of appetite amongst certain NCAs to address these deficiencies six years after go-live, suggests that the current reporting regime doesn’t achieve its objectives. 

    Check out the first blog in this series on MiFIR transaction reporting. Forthcoming blogs will detail our wish lists for SFTR reporting and Post-Trade Transparency reporting.

    For help with your EMIR trade reporting accuracy or to discuss your own post-Brexit EMIR trade reporting wish list with one of our regulatory specialists, please contact us.

  • ESMA and the European Commission clarify treatment of Alternative Investment Funds (AIFs) under SFTR

    ESMA and the European Commission clarify treatment of Alternative Investment Funds (AIFs) under SFTR

    The European Commission and ESMA have both dispelled any concerns that non-EU AIFs were being brought into scope for SFTR reporting if their AIFMs were EU-based.

    A paragraph in the Final Report that accompanied the Level 3 Guidelines on SFTR reporting on 6 January, raised concerns as it appeared to bring non-EU AIFs into scope for SFTR reporting if their Alternative Investment Fund Manager (AIFM) was based in the EU. This statement, while apparently contradicting elements of SFTR Level 1 (the regulation itself), Level 2 (the regulatory and implementation technical standards (RTS & ITS)) and other elements of the guidelines, nevertheless raised fears that extra territoriality was sought by EU regulators.

    In response to trade association concerns, both ESMA and the Commission have responded in letters stating that non-EU AIFs will not come into scope for SFTR reporting regardless of where their AIFM is based.

    Furthermore, ESMA provides further clarification about the nature of the Final Report and how to distinguish it from the Guidelines themselves. The Final Report provides feedback on the consultation responses, a summary of proposals in the consultation paper and an assessment of the feedback. They hasten to add that while some of the feedback resulted in amendments to the guidelines, other elements were discarded. They further emphasise that reporting parties should focus on the Guidelines and not the Final Report as it is the Guidelines that contain all the clarifications and examples to enable reporters to be compliant with the Level 1 SFTR regulation.

    The Commission in its response, re-states that SFTR Article 2(1) limits the application of the regulation to “(a) a counterparty to an SFT that is established (i) in the Union, including all its branches irrespective of where they are located; (ii) in a third country, if the SFT is concluded in the course of the operations of a branch in the Union of that counterparty.” Therefore, an AIF not established in the Union is not subject to the obligations set out in Article 4(1) SFTR.    

    Now we can only hope for such definitive feedback from the Commission and ESMA in relation to settlement finality and the reporting of bilateral variation margins…to be continued!

    You can read the letters here.

    We are helping a number of investment firms prepare to report accurately for SFTR.  Please contact us for a complementary consultation with one of our regulatory experts. 

  • Post-Brexit regulatory reporting wish list: MiFIR transaction reporting

    Post-Brexit regulatory reporting wish list: MiFIR transaction reporting

    Wouldn’t you know it; you spend over three years planning and worrying about a hard Brexit, and in the end, right at the last moment, after all the sleepless nights, it doesn’t actually happen! Instead, we now have a nice 11-month transition period. While there may be no changes to the MiFIR, EMIR and, SFTR reporting regimes until 2021, now is a good time to think about what changes you would like to see in the UK reporting regimes at the end of the transition period. While it was assumed that there might be little change in an attempt to assure equivalence, the UK Chancellor’s assertion that he is seeking “outcomes based” equivalence rather than complete alignment appears to have left the door ajar for some sensible changes to the reporting regimes. Starting with MiFIR, here are my top ten suggestions for changes to the transaction reporting regime which we believe will make reporting more proportionate for firms without degrading regulator’s ability to use the data for the intended purposes:

    1. “Country of Branch ” fields

    Perhaps one of the forgotten drivers behind MiFIR transaction reporting is the monitoring of conduct of business. There are five MiFIR “country of branch” fields which the NCAs use to share data amongst each other to help ensure that they can monitor branch activities. At Kaizen, we have discovered that firms frequently have issues populating these fields correctly. Since there will be no systematic sharing of data between the UK and the EEA, there appears to be no regulatory requirement to persist these fields.

    1. “ToTV Opinion Paper”

    ESMA has used this paper to expand the reportable instrument set to include “OTC derivatives sharing the same reference data details as the derivatives traded on a trading venue” Understanding the reportable instrument set has caused firms enough problems without adding to the burden. This is a considerable addition involving the matching of attributes against the ANNA DSB to find potential ISINs and then comparing the attributes associated with these ISINs against FIRDS to see if the instruments are reportable. I do not believe this is proportionate and it can be argued that it is not consistent with the Level 1 regulation. It has to go.

    1. Basket and Index Derivatives

    Firms executing transactions in OTC basket derivatives have to populate the underlying ISIN field with all the ISINs that are traded on an EEA trading venue. For example, if they trade a pharmaceutical basket comprising 421 stocks of which 352 are ToTV, they first need to discover which are ToTV and then populate all of them in the underlying ISIN field. If they make a mistake with any of those ISINs, it will be rejected by the regulator. This is very onerous for firms and can be of very little value to the regulators. There is no information on the weighting, so the information cannot possibly be used by the regulators on a systematic basis.

    Additionally, any changes in the basket composition are not reportable. It is also questionable whether the reporting of an index is of any real value to the regulators as it is doubtful whether they hold the constituent and weighting data. Of course, it is possible to manipulate the index markets (see Flaming Ferraris) but this is likely to stand out like a sore thumb to the participants and should be reported through a STOR. It is very difficult for firms to know whether the OTC index derivatives are reportable as it only takes one of the index constituents to be ToTV and this information is difficult to source – it certainly isn’t on FIRDS.

    1. IPOs

    Under MiFID, we used to say that everything that was knowable about an IPO was contained in the prospectus, so it would not be proportionate to require the resultant transactions to be reported. I’m not sure what’s changed to justify their inclusion for MiFIR. The task has been made more difficult as it is possible that some of the ‘counterparties’ don’t have LEIs as they are not necessarily normal market counterparties. Of course, trades cannot be reported if the counterparty doesn’t have an LEI. To make things worse, reporting firms have often discovered that the ISIN of the IPO is not on FIRDS at the time of the IPO. As some trading venues have not reported dates when an application for trading was made, some IPO trades have been continually rejected.

    1. Trading Capacity

    In the UK, we understand ‘principal’ and ‘agency’; but we don’t always understand the distinction between the new MiFIR values of ‘dealing on own account’ and ‘matched principal’. However, many firms, particularly the buy-side, have discovered that brokers confirming transactions back to them as ‘matched principal’, causes immense difficulties. Additionally, you can describe the same back-to-back principal scenario to a number of firms and I believe 70% of them will report it as two ‘DEAL’ transactions and 30% will report it as a single “MTCH” transaction. If it doesn’t matter which method is observed, why have the element of grey in the first place? Let’s get back to trading capacity we understand (and that are used in other reporting regimes).

    1. Crazy Chains – transmission of order, INTC and individual funds

    I love the Guidelines document, I really do. However, there are times when I’m reading sections 5.26 (Chains and Transmission) and 5.27 (Investment firm acting under a discretionary mandate for multiple clients) that I find it extremely difficult to carry on reading. There are a couple of inconsistencies within these Guidelines which suggests they may not work quite as the regulators envisage. It is just too convoluted and transaction reporting shouldn’t be this difficult. Again, I think it is the buy-side that may suffer most from this and maybe it is an area where the FCA may want to simplify the requirements. For example, are allocations to funds really required when the fund manager reports with the identifier of the individual decision maker within the fund management company? Does the transmission of order indicator actually add any value for the regulator?

    1. Repos & Securities financing indicator

    Exactly what is the logic for requiring a securities financing transaction, such as a repo, to be reportable under MiFIR simply because it has been excluded under SFTR? How was that leap made? If RTS 22, Article 2 sets the precedent that SFTs aren’t reportable under MiFIR (because they cannot be deemed to be abusive) why was it felt necessary to add the proviso that they should be reported if the counterparty is a member of the European System of Central Banks. Simplify the regulation and remove SFTs from MiFIR transaction reporting completely.   

    1. Swaps

    Completing the technical standards and Guidelines was clearly a mammoth task for ESMA and it is inevitable that there would be time constraints. I believe this is particularly evident when it comes to the reporting of swaps. For example, it is questionable whether requiring the price of an equity swap to reflect the interest rate is sensible, as the price of the underlying reference security would appear far more valuable to the regulators in pursuing market abuse. In fact, why require the interest rate side at all – it is not required for CFDs or spread bets, which are essentially swaps anyway. As for the “swap-in” and “swap-out” indicator – does this really bring any value when rules for determining the ‘buyer’ and ‘seller’ are already set out in the regulatory text?

    1. Reference Data Requirements

    Where a reported instrument is not ToTV and is only being reported because the underlying instrument is ToTV, up to 15 additional reference data fields need to be populated to describe the instrument to the regulator. This has proved to be particularly difficult for firms. A lot of these fields are essential for the regulator to detect market abuse – the underlying instrument ISIN is a prime example. However, it is questionable whether some of the others deliver any value. For example, does the ‘instrument full name’ add value when all the details are contained in other fields. Are some of the fields duplicated in the CFI code (e.g. ‘option type’). Does ‘notional currency’ have any relevance for non-FX derivatives?

    1. Short Sell indicator

    This is very onerous for firms to populate correctly and maybe the cost benefit analysis of this field should be reviewed. If there is a permissible value for ‘information not available’ (for clients after acting on a ‘best efforts’ basis) then you have to assume that the overall quality of this information is questionable.

     

    These are my ‘just for fun’ top ten as there may be perfectly valid reasons why the regulators need this information. To be honest, they’re my initial thoughts and I haven’t even mentioned other contenders such as ‘net amount’, ‘waiver indicator’ and ‘OTC post trade indicator’.

    However, there is a serious element here. If there is an opportunity for the UK FCA to tweak its reporting regimes on the basis of ‘outcomes-based equivalence’ rather than alignment, the process needs to start immediately and firms need to feed into that process. Eleven months is not a long time.

    Forthcoming blogs will detail our wish lists for the EMIR trade reporting and SFTR regimes.

    For help with your transaction reporting accuracy or to discuss your own post-Brexit transaction reporting wish list with one of our regulatory specialists, please contact us.

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

  • SFTR reporting final guidelines – ready, steady….go!

    SFTR reporting final guidelines – ready, steady….go!

    In this blog, we explain the securities financing transactions reporting final guidelines

    It was good news last week for those of us who’ve been waiting for ESMA to publish the final guidelines for SFTR reporting. The overriding principle of the regulation which these new guidelines reinforce, is that reporting firms are expected to populate the database in as comprehensive, timely and accurate basis as possible. These guidelines, the final report (responding to consultation feedback), updated validation rules and a statement on non-EU issuer LEIs offer some contradictions and will not please all market participants but do provide much of this framework.

    Of course this blog is no substitute for reading the guidelines but here are some of the highlights:

    Timeline

    ESMA confirmed reporting obligations for credit institutions and investment firms (banks) go-live on Monday 13 April (for EU jurisdictions that do not observe Easter Monday as a public holiday) or Tuesday 14 April for those that do. In either case, reporting firms are required to send reports for any SFTs executed on or after Saturday 11 April. Market infrastructures will follow accordingly on 13 July, buy-side on 12 October and non-financial counterparties on 11 January 2021.

    Non-EU issuer LEIs

    ESMA acknowledged that only 30% of non-EU issued securities currently have an issuer LEI and therefore have removed the need to populate these security loan and security collateral issuer LEI fields for non-EU issued securities until 13 April 2021.

    Third party executed reportable trades

    ESMA have provided clarity on which SFTs executed on behalf of the reporting counterparty through powers of attorney are reportable under SFTR. The following are reportable:

    • CSD fails curing transactions in which securities are automatically borrowed. Credit or securities provided to avoid settlement fails are collateralised with the securities account of the borrowing CSD participant
    • Auto-collateralisation transactions where payment banks or their clients are counterparties.
    • CREST client auto-collateralisation trades.

    However, CCP “daylight lending facilities”, auto-collateralisation trades with an ESCB counterparty and intraday credit/overdrafts resulting from fails-curing transactions are all out of scope.

    Third country reporting obligations

    ESMA has advised that in bringing SFTR into line with EMIR, for a transaction to be in-scope for reporting by an EU branch of a 3rd country entity, the term ‘conclusion’ relates only to instances in where they are a counterparty to the trade. i.e. the counterparty where the SFT is booked. References to the EU branch merely supervising trading in a third country entity have been removed.

    Settlement fails reporting

    The guidelines require reporting parties to modify the maturity date (roll it forward to the next day or an expected settlement date) in the reports they send on settlement date +1 if a transaction is failing. It must be modified on this day because going forwards without modification it will be closed and not possible to re-open it. Providing this feedback loop on settlement status is going to be tricky.

    However, the treatment of partial returns is different where “a delayed settlement that does not result in a cancellation of the partial return, should not be reported.” 

    UTI failure

    There is no prescribed approach in the guidelines about what to do if your counterparty – responsible for creating and sharing the UTI – fails to provide it ahead of the COB T+1 reporting deadline. It simply states that “counterparties should ensure a timely solution.” Essentially reporting parties must chase and not report anything until the UTI has been shared, and document all of the steps taken to obtain the UTI.

    Valuation considerations / market values

    Market values should be reported as of close of business each working day. The values used for collateral and exposure management purposes should use most recent market prices or bilaterally agree valuations with counterparties if none are readily available. This requirement to agree values contradicts with a further statement about the unavailability of price information. This relates to some suspended shares and illiquid fixed income securities where counterparties should report the valuation contractually agreed upon conclusion of an SFT. Only then should the market value be updated with a valuation, when new price information becomes available.

    ECB FX rates should be used for valuations or bilaterally agreed rates if none exists. The need to align FX rates is a concern for the industry, given many reporting parties use an enterprise rate, not only for SFTs but across their businesses.

    Re-use reporting with delegated reports

    If reporting has been delegated, the counterparty to which reporting has been delegated is not responsible for the reporting of the estimated re-use of the collateral. NFCs are responsible for calculating the estimated re-use themselves and in providing the estimate to the counterparty in charge of reporting in a timely manner.

    CFI sourcing

    The guidelines state that counterparties should retrieve CFIs from ANNA, National Numbering Agency (NNA) or, if not available, request it at the relevant NNA of the instrument. Unfortunately by acknowledging that it is reconcilable, they contradict themselves by saying that if it doesn’t exist in the official sources then it should be agreed between counterparties. It certainly seems that official sources should be exhausted and CFIs should be requested from the NNA before attempting to derive CFIs.

    Security / collateral quality

    Ratings should be instrument-based and use internal assessments of credit quality rather than mechanistic reliance on credit rating agencies, who use measurements such as local vs foreign currency, short vs long term investment to reflect security specifics. ESMA acknowledge the resultant higher rate of reconciliation breaks. However, they fail to acknowledge sensitivity around sharing any aspect of internal ratings and the fact that many counterparties will not have fully on-boarded many securities that appear on settlement date in collateral baskets. This is likely to require some industry driven solutions.

    Variation margining 

    There is fresh guidance on how to report the collateral given or taken on a net exposure basis through post on-leg, value date, variation margin calls to complement the original trade level collateral. Counterparties should send single collateral update messages to reflect these bilateral variation margin calls. The direction of the collateral should be expressed with a sign against its market value i.e. negative for rows of collateral given and positive for collateral taken.

    Floating rate transactions

    When reporting floating rates, counterparties should indicate the relevant rate and the applicable spread. They should only provide updates when they agree to change the rate or the spread but not on a daily basis.

    Report tracking numbers (RTN) and open offer trades

    In reporting trades executed on venues where execution is contingent on central clearing (open offer basis), including DBV trades, reporting firms are not required to populate the report tracking number (RTN).  It is important to note that the clearing time and execution time would be expected to match.

    In instances in which a trade is bilaterally executed and subsequently subject to clearing (even same day), it requires the prior UTI to be reported as the RTN.

    Our view of the guidelines is that they do provide some clarity and are a step forward from where we were. However they do not provide all the answers and contradict in some places. Because of the diverse scope of the regulation, one size doesn’t fit all and it’s now for the market to interpret as best we can. Good luck and let us know how you’re getting on. 

    Kaizen’s ReportShield™ accuracy testing, advanced regulatory reconcilation and reference data testing services will help ensure your reporting is accurate from day 1 of go-live.  

    Contact us to find out more about how you can make a smooth transition to SFTR reporting.

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

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

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

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

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

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

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

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

     

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

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

    You better watch out, you better not cry….

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

    Secret Santa?

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

    Don’t panic

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

    Put the right controls in place

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

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

  • €STR versus SONIA

    €STR versus SONIA

    The introduction of the new euro short-term rate (“€STR”) by the European Central Bank (ECB) in October caused potential issues for MiFIR transaction reporting and RTS 23 instrument reporting as there was no standardised four character code in RTS 22 or RTS 23 for the new benchmark rate. Fortunately, ESMA has addressed problem by creating a new four character code of ESTR for the index name and stipulating that the ISIN EU000A2X2A25 should be used to identify the index. Clearly this will be transformative in the number of successful market abuse cases brought by the regulators. ESMA details how these codes should be used for both RTS 23 and RTS 22 reporting in its December MiFIR Data Reporting Q&A.

    However, the ESMA guidance on €STR does highlight certain anomalies with the treatment of other interest rate benchmarks. For example, it’s the only interest rate where the ISIN also needs to be populated in the ‘Underlying Instrument’ code field. But perhaps the strangest anomaly is that there appears to be no equivalent treatment for the Sterling Overnight Index Average (SONIA). This was introduced in March 1997 and is used to value around £30 trillion of assets each year. SONIA derivatives are also traded on regulated markets, but there is no standardised four character code for this sterling interest rate benchmark and ESMA has not addressed this issue in the same way it has for the euro interest rate benchmark. It’s a similar story for EMIR, where the ‘ESTR’ code was added to the list of four character codes to identify floating rates, but no similar additional was made for SONIA. Why is this, I wonder? Answers on a postcard please…

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

  • SMCR: Five key questions to ask on regulatory reporting

    SMCR: Five key questions to ask on regulatory reporting

    The Senior Managers and Certification Regime (SM&CR or SMCR) goes live today for buy-side organisations and other solo regulated firms*. The regime has been in operation for the past few years for banks, building societies, credit unions and branches of foreign banks operating in the UK and the largest investment firms regulated by the PRA and FCA.

    Regulatory reporting controls, governance and ultimately sign off will be key to senior managers in these firms as they take on the additional responsibilities of SMCR. If this is you, what do you need to do from a regulatory reporting perspective? Here are five questions you should be able to answer:

    1. What category is my firm in?  You need to understand the three types of categorisation under the senior managers regime (Limited Scope, Core or Enhanced) and the certification regime, as well as the conduct rules that will apply to the rest of employees’ monitoring and auditing activities.
    2. Have my Senior Management Functions (SMFs) been properly trained? Most functions will be the same as under the previous Approved Persons Regime but have they been trained to understand the responsibility and consequences of their actions?
    3. Is our governance now in line with SMCR?  Are the right procedures & policies and controls in place for recording the implementations, steps and the decisions made by your firm to comply with the regulation?
    4. Have I mapped out my management responsibilities? Who is impacted (e.g. Head of Legal is not) and what Controlled Functions have transferred to SMFs?
    5. Am I protected? We have seen firms fined under various regulatory regimes such as MiFID and EMIR but there have been few penalties or consequences directly for the executives within those firms – yet. With SMCR making individual senior managers within firms accountable, our services can provide you with peace of mind that you have the right controls in place to meet your regulatory reporting requirements and reduce your regulatory risk.

    Join in the conversation over on our LinkedIn.

    More information: https://www.fca.org.uk/firms/senior-managers-certification-regime

    *These include investment firms – brokers, securities firms, asset managers, financial advisers.

  • FCA to increase its scrutiny of EMIR reporting

    FCA to increase its scrutiny of EMIR reporting

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

    What’s the background?

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

    But isn’t EMIR more important than MiFID II?

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

    What does the FCA do currently?

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

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

    What should firms do?

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

    Read the ESMA report on its website.

  • SFTR validation rules and schemas from the ESMA cauldron…

    SFTR validation rules and schemas from the ESMA cauldron…

    Halloween saw some new ghoulish delights appear from the ESMA cauldron with the publication of SFTR validation rules (revised following the summer consultation) and XML schemas for reporting. ESMA has released four documents covering:

    1. SFTR report validation rules
    2. Counterparty and Trade Repository (TR) data exchange XML schema
    3. Intra-TR data exchange XML schema
    4. TR to authority data exchange XML schema.

    We have created a marked changes version of the latest validation rules to highlight the differences.

    Tighter but more logical 

    The validation rules have been tightened up to reflect instances in which fields that business logic dictates should be mandatory or conditional are no longer optional. For example, the loan field ‘security quality’ is now conditional rather than optional for new securities lending transactions. In other instances, fields that were not rationally mandatory (e.g. ‘maturity {date} of the security’ fields for both loan and collateral) are now conditional. The rules generally make more sense, particularly in relation to the two changes noted below.

    Full reporting – not delta reporting

    Modifications and corrections at both trade and position level now require all of the original counterparty table fields to be populated. In most cases, they also require the same fields to be populated in the loan and collateral table as in the original NEWT report in accordance with the same mandatory and conditional rules as the original report. This requirement for full reporting of modifications and corrections should be clarified in the level three guidelines when published by ESMA later this quarter.

    Bilateral Margining Simplified

    The ‘counterparty side’ is no longer required for collateral updates, making bilateral margin reporting simpler. Since stating whether the reporting party is a collateral giver or collateral taker is no longer a pre-requisite of providing a bilateral margining collateral update (COLU) or any other COLU report, it is much more straightforward to report instances of collateral flowing in both directions with the same other counterparty.

    The references to negative values of securities in the ‘counterparty side’ validation field notes on format and content have also been removed (in addition to this field being no longer required for COLU reports). Instead, the ‘collateral quantity or nominal amount’ is now permitted to be negative, enabling you to report collateral moves in either direction – as a margin giver or taker for example. You are also now permitted to use negative values in the ‘price per unit’ field. Again, we hope for further clarification when the reporting guidelines are released.

    The publication of schemas, the cementing of validation rules and a number of key clarifications (as highlighted) puts the industry in a much greater state of readiness for reporting – now only five months away.  Our advice?  Don’t now wait for final reporting guidelines (due later in Q4) but focus full steam ahead on implementation, testing and establishing your controls environment.  And if you’d like to discuss how we can ensure you are compliant with SFTR reporting rules, please don’t hesitate to contact us.

    The new validation rules and schemas are available on the SFTR section of our website.

     

  • 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

  • Look before you leap: Understanding the limitations of AI in the regulatory space

    Look before you leap: Understanding the limitations of AI in the regulatory space

    Last week I went to the Commodity Future Trading Commission (CFTC) in Washington DC to attend the Fintech Forward 2019 conference. I was grateful for the opportunity to speak on a panel about AI in the 21st Century Marketplace: Exploring the Role of AI and Related Fintech in CFTC Markets.

    Artificial Intelligence (AI) is an exciting tool that has shot to prominence in the last few years, with applications spanning the gamut from Snapchat filters and Spotify recommendations to sophisticated systems that catch fraudulent transactions or see the signs of lung cancer before expert radiologists. But how will AI impact the regulatory compliance space?

    AI and data quality: don’t get too excited

    At Kaizen we’re primarily concerned with helping firms check the data quality of the transaction reports that they have to submit under a variety of régimes from around the world such as MiFIR, EMIR and the Dodd-Frank Act. We have to be careful not to be too optimistic about the role AI can play in this. AI is most useful when we don’t exactly know the logic that a computer programme should be following, so we need the AI to ‘learn’ it from the data. But with regulatory reporting, the rules are clearly laid out – meaning that rule-based “expert systems” are the right technology for testing reports.

    Yet, despite the seemingly straightforward nature of accurate reporting, at Kaizen we’ve found that firms can commonly make errors in as many as 90% of records. Firms should be wary of “running before they can walk” by increasing the complexity of their reporting pipelines with AI while they are still making basic mistakes setting up their reporting systems.

    But AI can help with market integrity

    Where AI can really come into its own in regulatory compliance is market integrity – particularly safeguards against market abuse such as insider trading. Under the Market Abuse Regulation firms are required to monitor, detect and report suspicious transactions that take place on their platforms. Unlike with regulatory reporting, there are no hard-and-fast rules of what abusive trades look like. This is where the power of AI and machine learning (ML) can be brought to bear, learning how to find the anomalous needles in the gargantuan haystack of reported transactions.

    AI goes rogue

    At FinTech Forward I also commented on challenges that AI might pose for regulators and market participants. One big challenge regulators may face is the question of accountability: who is to blame if an AI ‘goes rogue’? The notion of a super intelligent AI that understands its actions still belongs in science fiction; contemporary AIs are really just mathematical models that extrapolate patterns, so the idea of holding an AI responsible itself is silly. It isn’t only the programmers who determine how an AI will behave; the AI can be heavily influenced by matters like what data fields the AI can ‘see’, what training data is in scope, and what metric for success the AI will use. Fundamentally, accountability for an AI need not be different from any other automated computer system.

    The challenges of algorithmic bias

    Another challenge for regulators is the issue of algorithmic bias – when an AI can behave unfairly in a systematic way, due to unintended problems with the training data or the question that was posed. One famous example is a recruitment AI that Amazon scrapped because it was unintentionally disfavouring women. Regulators that use AIs for enforcement have to be careful to minimize algorithmic bias. It isn’t only individuals who might get caught up. As a hypothetical example, if regulators only trained their AI on data from Tier 1 investment banks then they might end up unfairly over-flagging transactions from hedge funds.

    Black box models

    One problem for market participants who deploy AIs is the lack of interpretability for “black box” models. State-of-the-art AIs can have millions of parameters and it’s impossible to know what they’re doing, and this means it can be hard to quantify the risks. Moreover, the inherently adversarial aspect of market participation means that AI complexity is more of a risk than it would be in collaborative contexts such as self-driving cars – a counterparty’s AI might learn to persuade a black box AI to misprice securities, for example. Few market participants deploy AIs without a human in the loop.

    In the future, we’ll see AI play an ever increasing role in our lives, including finance and regulation. But as long as the technology is still in its infancy it’s important to temper the hype by understanding the limitations. Deploying AI systems has the potential to add huge value, but as always, firms should look before they leap.

    Watch Sam in action at Fintech Forward 2019.

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

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

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

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

    Be proactive, transparent and open with your NCA

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

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

    Alert your NCA as soon as possible

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

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

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

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

    *Does not open in new window.

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

    FCA warns on further transaction reporting errors in Market Watch 62

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

    First, the basics…

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

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

    The more complex..

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

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

    To summarise…

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

    Our advice…

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

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

    Further reading: Market Watch 62

  • EMIR – Pairing and Matching at Position Level to be implemented in December 2019

    EMIR – Pairing and Matching at Position Level to be implemented in December 2019

    In what will undoubtedly be a surprise to the majority of the industry, ESMA has asked the trade repositories (TRs) to implement pairing and matching at position level. Previously, the pairing and matching had only taken place at the trade level reports. Whilst this undoubtedly makes sense, it could cause massive issues for investment firms as there appears to be no current mechanism or infrastructure to ensure the two counterparties use the same UTI at the position level.

    It also appears unclear which position level reports will be subject to the reconciliation process. Originally, position level reporting was optional, but the requirement for cleared trade reports to use the CCP’s valuation implies that ETDs have to be reported at a position level where the CCP only provides position level valuation. However, there are a number of other derivative types that are not subject to clearing but can be reported at a position level such as spread bets and CFDs. If these are also to be subject to position level reconciliation, it could result in confusion as there appears to be no legal basis requiring both sides to report these instruments at a position level.

    We understand that the position level reconciliation will be deployed by the TRs on 9 December this year. This gives firms precious little time to determine how they will agree on the UTI to be used at a position level and a process for the dissemination of this information to meet the T+1 reporting requirement. It is unfortunate that neither ESMA nor the FCA appears to have widely publicised this imminent requirement. As a new iteration of the ESMA Q&A on EMIR was only published earlier this month, it is surprising that ESMA did not take this opportunity to inform firms of the change.

    At Kaizen, we always update our services to reflect regulatory changes. If pairing and matching is something you’re struggling with, our quality assurance services include checking that your EMIR position level reports truly reflect the corresponding trade reports submitted. For further details of our services please contact us to get your reporting complete and accurate.  

  • Brexit – FCA Statement on EMIR Trade Reporting

    Brexit – FCA Statement on EMIR Trade Reporting

    The FCA has published a statement that will hopefully provide some comfort to firms worried about the impact a hard Brexit will have on their EMIR trade reporting – should there actually be a hard Brexit on 31 October. Although it stresses the need for accurate data, the FCA acknowledges that mid-week changes of this magnitude will be challenging and it promises to adopt a “proportionate and pragmatic” approach – particularly where firms have robust systems and the data reported is accurate. (If you’re not sure the data you have reported under EMIR is accurate, perhaps this is a good time to contact us for a quality assurance check.)

    FCA-registered Trade Repositories (TRs) are required to ensure the migration of all outstanding trades (and historic data) for UK counterparties, so, in theory, it should be a seamless process for firms to transfer reporting to an FCA registered TR. However, because it’s a mid-week change, the chances are that it won’t be an entirely seamless! The FCA has therefore made some sensible concessions to the T+1 reporting requirement and has stated:

    • We expect all UK reporting counterparties to have reported the details of all derivative transactions concluded, terminated and/or modified on 1, 2 and 3 November 2019 to an FCA registered TR by no later than 4 November 2019
    • UK reporting counterparties must also ensure that any details of their derivative transactions concluded, terminated or modified on 30 and 31 October 2019 that cannot be reported by the point of exit are back-reported to an FCA registered TR by no later than 4 November 2019.

    Counterparties within scope of ‘UK EMIR’

    The FCA has also stated that: “UK branches of third-country firms (including branches of firms from EU27 countries after Brexit) are not in scope of the UK EMIR reporting regime and so do not have to report under the onshored UK regime” Whilst this removes one element of potential branch level dual reporting, the FCA also states that branches of UK established firms outside the UK are within scope of the UK EMIR reporting regime.

    The reporting of new and outstanding trades under ‘UK EMIR’

    The FCA states that all new derivative trades entered into by UK counterparties on or after 11.00pm on exit day are in scope of the UK EMIR reporting regime and are required to be reported to an FCA-registered, or recognised, TR. In addition, all outstanding derivative trades entered into by UK counterparties on or after 16 August 2012, need to be held in an FCA-registered, or recognised, TR on exit day. So any firm believing that they no longer need to worry about the completeness and accuracy of their previous reporting are sadly mistaken. The UK authorities will have access to this data and they will expect it to be correct.

    Inter TR Reconciliation

    At least in the short term there will be no inter-TR reconciliation in the UK regime! However, the FCA recognises the role this reconciliation plays in ensuring the quality of the data and will reconsider this issue with UK TRs at a future date.

    Will this all work?

    Yes, but probably not perfectly. Of course, we are still unsure whether there will be a hard Brexit and, if there is one, whether it will be on 31 October 2019. So there are still plenty of ‘unknowns’.

    Of course there shouldn’t be any ‘unknowns’ about the quality of your EMIR trade reports. We expect the FCA to become far more intrusive in ensuring the quality of reports under UK EMIR. If you’re not sure your EMIR reports will meet this scrutiny, please contact us as this is why we here at Kaizen exist – our assurance services can tell you how good or bad your reporting is, identify your issues and get you quickly on a path to good quality reporting. 

    Read the statement on the FCA website.

    ***

    If you need more information about reporting after Brexit, please read David’s Brexit White Paper. 

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

     
  • ESMA postpones review of MiFID II RTS 2

    ESMA has written to the European Commission to postpone the review of MiFID II Regulatory Technical Standards (RTS) 2, which was due in July 2019, as outlined in Article 17 of the RTS regulatory text.

    The review is key to understanding bond transparency thresholds and liquidity assessments. Given the uncertainties around Brexit, it was felt that the analysis should be completed after the UK has left the European Union. This will now be due by 30 July 2020 and recent regulatory commentary suggests it will begin around March 2020.

    This is another rescheduling to RTS 2, as data quality already delayed the SI regime for bonds until eight months after MiFID II go-live. The SI regime for derivatives is still not due to go live (for the same reason) until ‘at some point in 2020’. This Brexit-related delay to the review will almost certainly push the derivatives SI regime to the latter end of 2020, which in turn may delay the transparency reporting requirement under RTS 2 which looks at decreasing it from 15 minutes to five minutes in January 2021.

    For regulatory reporting purposes, this brings further complexities to investment firms. Understanding of trading where the primary market liquidity is sitting, and its subsequent size and liquidity thresholds for deferral eligibility, is key. Ensuring you are reporting to the correct APA in Europe or UK brings transparency challenges too. 

    To discuss any of the issues above or to find out how our ReportShield™ services could help with your Post Trade Transparency reporting, please get in touch. 

  • 10 Lessons from industry responses to the ESMA Guidelines Consultation

    While not an exhaustive list, here are our key takeaways from reading the ESMA SFTR Guidelines consultation responses. The overall level of engagement in relation to the consultation was substantial, with 49 files published by ESMA following the consultation period.

    1. Reporting certainty

    A few fundamental questions are key to providing clarity to support a timely build for SFTR reporting. Banks and credit institutions (due to report from April 2020) need answers to some of the these questions well in advance of the self-imposed Q4 2019 deadline set by ESMA.

    In particular, question 25, whether to provide full reports or the delta of changes for modifications and corrections – respondents overwhelming voted for full reporting.

    2. Reportability of intraday market infrastructures executed SFTs

    Which intraday transactions executed on behalf of firms by CSDs and CCPs remain in-scope for reporting? While T2S Auto-collateralisation transactions are explicitly excluded from reporting, does this also cover UK Crest Auto-collateralised repos? Extracting and reporting this data presents unique challenges.

    3. Scope and third country considerations

    The approach to determining the ‘conclusion’ of a transaction by a branch is far reaching and strays from the EMIR definition. It appears to focus on the activities of individuals rather than risk held in the EU. The practical challenges of reporting SFT activities of non-EU entities where traders are supervised by EU branches are immense and likely to lead to significant confusion in relation to areas such as bilateral margining and reuse.

    Concerns were raised where SFTR does not require non-EU AIFs managed by EU AIFMs to be reported (unlike EMIR), while EU AIFs must be reported regardless of whether the AIFM is based in the EU (again unlike EMIR).

    4. Why are buy-sell backs still treated differently?

    ESMA have specified that documented buy-sell backs should be reported as buy-sell backs listing the master agreement, but it is still unclear why the reporting requirements differ from repo. The inability to apply a repo rate, forward breakeven yield or forward price on a buy-sell back is a particular issue.

    5. Is fails reporting really required?

    There has been some confusion about the reporting of settlement fails (general consensus was that perfect settlement would be assumed unless both parties chose to modify a transaction to reflect a default or extended fail).

    6. How to report bilateral variation margining

    Concerns continue to surround the reporting of bilateral variation margins for repo. Given these margin calls at the counterparty portfolio level are entirely separate from the trade level collateral, there should be a separate end of day collateral update report to reflect bilateral margining. They cannot, as ESMA examples suggest, be incorporated with trade level collateral updates.

    7. Failure to transmit Unique Trade Identifiers (UTI)

    The issue of what to do if a counterparty is responsible for providing the UTI fails to provide it in a timely manner for reporting, remains an open question. The real question is how the party subject to late notification of the UTI by their counterparty can be excused from their obligation to submit timely reports.

    8. Availability & consistency of reportable data

    There are many concerns about the availability of data for reporting. The FSB themselves highlighted in their May 2019 document Thematic Review on Implementation of the Legal Entity Identifier that on aggregate only 55% of all financial instruments in scope have an LEI code (representing 78% of outstanding amounts) and that only 11% of all firms that are issuing securities have so far obtained an LEI. Mandating usage of issuer LEIs when firms that use securities as collateral have no contractual relationship with the issuer of the securities, appears a step too far. Solutions are to make the field conditional or apply a standard dummy issuer LEI.

    Other concerns persist around missing official CFI codes, ISIN codes, differences in credit rating assessments between firms and the collateral type field.

    9. The removal of ESCB transactions from the calculation

    Trade associations reiterated that removing ESCB transactions from both sides of estimated re-use calculations will be both difficult and misleading. Nonetheless, this is understood to be an FSB requirement rather than ESMA specific.

    10. Uncertainly around in-scope commodities financing transactions

    A number of trade associations and other respondents commented on the significant uncertainty felt by the commodities trading industry around the SFTR reporting scope of any of their transactions. Concerns were raised that while commodities financing transactions share attributes with SFTs, they are not executed for financing purposes. Disagreement exists as to which transactions constitute repos and which buy-sell backs, in general they were deemed hard to define under existing SFT definitions. There are also concerns that certain commodity transactions, believed to best fit the repo definition use pledge arrangements and not title transfer. Some power and gas contracts may also be reportable under SFTR as well as REMIT. While exclusions are in place for EMIR, they are not in place for REMIT.

    Did you know Jonathan provides CPD-accredited, CISI-endorsed training on the SFTR reporting requirements? Book your place on one of our upcoming courses here or get in touch for bespoke, in-house training.   

  • Collaborative reporting expected to be in demand for SFTR

    Collaborative reporting expected to be in demand for SFTR

    There is likely to be a high demand for collaborative reporting –  and other forms of delegated reporting – under SFTR, according to the results of our recent webinar with UnaVista. In this blog, we cover the results of the three polling questions asked during the webinar and what they mean for the industry.

    Q: About which of these are you the most concerned with regards to cleared trade reporting?

    1. Timelines of data from the CCP (25%)
    2. Market data availability (20%)
    3. Matching tolerances on collateral valuations (32%)
    4. Accuracy of Margin Reporting (11%)
    5. Correct application of RTNs (11%)

    Cleared trades are by nature significantly more likely to be consistently booked and subsequently reported. The benefits of clearing in counterparty risk reduction and in providing a single data set for many of the reporting fields seems likely to outweigh a number of concerns about the availability of data from CCPs. Nevertheless, pricing anomalies (resulting in concerns by 32% of participants about matching tolerances on collateral valuations) are common among SFT market participants even across different lines of the same business and these differences are likely to promote standardisation, best practices and efficiencies going forward.

    Q: Do you use any form of delegated reporting for other regulatory reporting regimes?

    1. Yes, we use delegated reporting for other regimes (e.g. MiFIR or EMIR) (55%)
    2. No, we have never used delegated reporting (32%)
    3. We have only used assisted reporting (14%)

    Again, interesting to see that 69% of participants use (or claim to use) some form of delegation. It adds weight to the recommendation that these parties focus on the quality of reporting to ensure that they are compliant with the regulation and keeping their reporting counterparty under appropriate scrutiny regarding the service provided.

    Q: How comfortable are you offering optional delegated reporting for SFTR?

    1. Entirely comfortable; this is a mature service for other regimes that we will simply extend to SFTR (37%)
    2. Will reluctantly offer; due to commercial pressures from client dictate we must offer it (23%)
    3. Will offer but not full delegation (7%)
    4. Will not offer any delegated reporting (33%)

    The proportion of participants that stated they were “entirely comfortable” was surprising, particularly given the challenges associated with populating the re-use table for third parties. The “will offer but not full delegation,” option seems more likely where clients use facilities offered by the trade repositories to provide a mirror of the broker dealer’s report to enable ease of reporting but only 7% responded in this way. The 33% stating they will not offer any delegated reporting maybe a little misleading given the mixed nature of participants (both buy-side and sell-side) and the commercial pressures that are likely to fall as reporting deadlines approach.

    In practice, to offer some form of delegated reporting under SFTR is likely to prove a must-do commercially on the sell-side but few operations managers will take it on with much enthusiasm (or resource). We think both parties should be focussed on data quality. The client should ensure that they are meeting their legal obligations (over the completeness, accuracy and timeliness of their reporting – that they cannot delegate). The reporting party should ensure that reports are correct (for both parties) and they do not only meet the trade repository validation, pairing and matching requirements. Two wrongs after all do not make a right! 

    If you’d like support with your SFTR preparation, we can help. Led by our SFTR Reporting Specialist Jonathan Lee, our pre go-live services include programme design and implementation, development of an appropriate controls environment, pre go-live testing of your reporting data and training on the reporting requirements.  Please contact us to find out more or visit our SFTR reporting page for more details.

  • A tsunami of EMIR Q&As

    A tsunami of EMIR Q&As

    Just when you thought it was safe to go back into the water, ESMA has hit us with a third EMIR Q&A in as many months. The impact on trade reporting can be summarised as follows:

    Funds and counterparties (General Question 1)

    The text now states that the fund manager must (rather than can) report on behalf of the funds and that the ID of the fund manager shall be provided as the report submitting entity. Please take care with this statement – we do not think it should be taken at face value. Whilst the amended EMIR Article 9 makes the fund management companies ‘responsible and legally liable’ for the reporting, we do not believe this is intended to prohibit delegated reporting by the broker (or another third party) on behalf of the fund manager (where the third party would be the ‘submitting entity’). It is another example where ESMA needs to be more precise in its use of language and advice to the industry.

    Reporting of outstanding positions following entry into force of EMIR (backloading)

    TR Question 4 has been completely deleted reflecting the removal of the backloading obligation following Refit.

    Intragroup transactions (TR Question 13)

    Again, synchronising with Refit, the text clarifies that intragroup trades are not reportable if certain conditions are met. These conditions are outlined in TR Question 51.

    Blocks and allocations (TR Question 39)

    Similar to General Question 1, we have further imprecise text from ESMA. ESMA states that the fund manager must report to the trade repository on behalf of the individual fund where the fund is identified as the counterparty to the trade. While the fund manager is responsible and legally liable for making the report, it can still delegate the reporting obligation. This ‘change’ applies from 18 June 2020.

    Notional amount field for credit index derivatives

    Where there is a change in index factor due to credit events, counterparties should not modify the notional (field 2.20); they should only change the index faction (field 2.89).

    Conclusion

    Not a huge amount of change in the latest Q&A, but it does demonstrate some of the pitfalls in interpreting the ESMA text and the importance of keeping in touch with the regulatory changes. If you’d like some help interpreting the changes or would like transparency of the quality of your EMIR trade reporting, please contact us to find out more about how our quality assurance and controls can get your reporting accurate.

  • ESMA fines trade repository for data delivery breaches

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

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

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

  • MiFIR transaction reporting goalposts set to shift again

    MiFIR transaction reporting goalposts set to shift again

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

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

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

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

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

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

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

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

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

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

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

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

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

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

  • Ten steps to MiFIR transaction reporting nirvana

    Ten steps to MiFIR transaction reporting nirvana

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

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

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

    2. Do not under-estimate the costs of remediation

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

    3. Training.

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

    4. Valid does not necessarily mean correct

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

    5. Quality assurance checks are essential

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

    6. Firms must not mark their own homework

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

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

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

    8. Heed the words of the regulator

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

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

    9. Get market identifier codes right

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

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

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

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

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

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

  • EMIR Refit – white elephant regulation

    EMIR Refit – white elephant regulation

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

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

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

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

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

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

    Delegated reporting

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

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

    A lost opportunity

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

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

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

  • Sunny ESMA provides some SFTR relief

    Sunny ESMA provides some SFTR relief

    ESMA published a Consultation paper “Guidelines for reporting under Articles 4 and 12 SFTR,” together with the latest consolidated SFTR validation rules. The deadline for responses is 29 July 2019. ESMA plan to consider feedback during Q3 2019 and the final report is scheduled to be published in Q4 2019. This does not give a lot of time, particularly for the 1st phase of reporting counterparties (Banks), due to go-live in April 2020.

    Nevertheless, ESMA provided clarity on many issues and gave reason to be cheerful as many SFTs executed on behalf of financial institutions through powers of attorney during the course of daily clearing, custody and settlement activities at CCPs, CSDs and ICSDs were ruled out of scope. This has undoubtedly removed a major operational headache from the SFTR reporting requirements and will assist regulatory authorities in gaining a better understanding of the data (as they will be significantly less overwhelmed with noise).

    • In particular, Chapter 5 (General Principles), paragraphs 25-27 rule out any reporting of short term credit lines for custody or CCP clearing.
    • Paragraphs 36-41 rule out reporting of any transactions relating to “fails-curing” services offered by CSDs.
    • Paragraph 43 rules out the need to report any transactions associated with Target 2 Securities Auto-Collateralisation.

    The guidelines also clarify the exclusion of the need to report under SFTR in relation to: Retail client lending (except when it is against an irrevocable trust), private banking & Lombard loans, syndicated lending and other corporate lending for commercial purposes, intermediate give-ups and take-ups (in the execution & clearing chain) and transactions involving emission allowances.

    In further points of clarification:

    • Buy-sellbacks and Sell-buybacks should be reported as such with the appropriate master agreement detail where applicable (overruling the original SFTR regulation) (paragraph 61).
    • Margin Loan reporting only applies to Prime Brokerage business (paragraph 11).
    • Modifications that are agreed but have not taken place should not be reported until the actual modification takes place (paragraph 117).
    • Margin loans – where the value of an existing margin loan hits zero, the transaction should be modified (MODI action type) rather than terminated (ETRM action type) (paragraph 83).
    • Securities lending and borrowing transactions can only involve a single ISIN being transferred between a given pair of counterparties (paragraph 65).
    • Backloading: ESMA advises that they like the idea of reporting all open and term transactions executed prior to the date of application whether they meet the requirements for backloading or not. This approach is seen as operationally simpler for many reporting parties and provides authorities with greater information in relation to variation margining (paragraphs 167-170).
    • When trading with sub-funds, each sub-fund should be treated as a counterparty if they have their own LEI (paragraph 52)
    • For cleared SFTs, each SFT between the CCP, its clearing members and the clients of those clearing members should be treated as separate SFTs with different UTIs (paragraph 53).
    • In relation to Repos, collateralised loans in more than one currency constitute separate SFTs. This doesn’t preclude a single SFT having collateral denominated in multiple currencies though
    • Small & medium sized non-financial counterparties trading with a non EU third country entity must either trade with an entity that has been granted equivalence (in which case there is no reporting obligation under SFTR), else they will need to delegate or self-report the transaction/s (paragraph 93).
    • Execution by a branch was clarified to cover the following: a) for a client in accordance with a discretionary mandate given to it by the client; b) where the branch has supervisory responsibility for the person responsible for the investment decision concerned; c) where the branch has supervisory responsibility for the person responsible for execution of the transaction; d) where the transaction was executed on a trading venue or an organised trading platform located outside the Union using the branch’s membership of that trading venue or an organised trading platform (paragraph 102).
    • Counterparties should not report the LEI of the CSD in which they are either a direct or indirect participant (paragraph 122) in the CSD participant field.
    • ESMA acknowledged that updating valuations of securities on loan or used as collateral may not be possible where pricing becomes stale. This can affect suspended shares and some illiquid fixed income securities. In these instances, reporting parties should use contractually agreed values and only update them if new price information becomes available (paragraph 155).
    • ESMA advises counterparties should always use official sources for CFI codes. Those who felt that it would be sufficient to just populate the first 2 characters are likely to be disappointed as ESMA states that X should only be used when a character is not applicable (paragraph 163).
    • Non-bank entities are permitted to start reporting earlier than their date of application if they find it easier (paragraph 188).   

    The consultation also contains an extensive set of sample reports for many different scenarios, detailing how each of the 4 reporting tables should be populated. Once we’ve had the opportunity to review these samples and the latest trade repository validation rules, we will produce a follow-up blog.

  • ESMA publishes new EMIR Q&A

    ESMA publishes new EMIR Q&A

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

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

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

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

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

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

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

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

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

  • FCA insight into Transaction Reporting Feedback

    At the Infoline Trade and Transaction Reporting Conference in London this week the audience were on tenterhooks for the latest update from Ana Fernandes, MRT Manager at the FCA. We thought we would share some insight from the statistics and issues she highlighted:

    Statistics

    • There are over 8.7bn records in the FCA’s Market Data Processor (MDP)
    • There are 23 submitting entities
    • Approximate 7,900 executing entities under ESMA, 3,000 of these are UK firms
    • Over 300,000 LEI’s and over 6.7m National Identifiers
    • FCA has received 1,335 notifications of errors from only 394 firms
    • 20 thematic investigations have been completed
    • 130 firms have been contacted by the FCA
    • FCA have only seen 405 requested and downloaded sample Transaction Reports in 2019

    There was a definite concern on the low numbers of submissions and an encouragement for firms to come forward asap and ‘promptly notify’ as per stated in Article 15(2) of the RTS 22.

    Issues seen by the FCA

    • GMT vs BST (a candid reminder to firms that clocks do change twice a year!)
    • Major vs Minor currencies
    • Price Zero vs NOAP
    • Buyer vs Seller
    • Misreporting of National Identifiers
    • Wrong Buy/Sell with Trading Capacity
    • Inconsistent TV TIC by Trading Venue
    • Use of default trading times

    Food for thought especially as mentioned before, by my colleague David Nowell, that these are still the same issues that firms were fined for as seen under MiFID I. These facts and issues evidence that the FCA are actively pursuing policy and detective activities in order to identify data quality issues. These are issues Kaizen testing is designed to highlight to our clients. Get in touch to discuss the accuracy of your trade and transaction reports. 

  • The effects of Brexit on MiFID II post-trade transparency reporting

    The effects of Brexit on MiFID II post-trade transparency reporting

    “There are known knowns. These are things we know that we know. There are known unknowns. That is to say, there are things that we know we don’t know. But there are also unknown unknowns. There are things we don’t know we don’t know.” – Donald Rumsfeld (Feb, 2002).

    Brexit…the ‘known unknown’ of everyone’s lives (at least for those of us in the UK) and not just in financial services but across all sectors of life.

    MiFID II has not escaped Brexit either.  Let’s call it BRiFID!  My colleague David Nowell has covered in detail the effects of Brexit on EMIR trade reporting & MiFIR transaction reporting but in this blog, I want to delve into the effects on post-trade transparency reporting. 

    Kaizen announced at the beginning of December 2018 that we were to offer post-trade transparency reporting testing following on from our established MiFID II transaction reporting testing service. The need and demand for MiFIR completeness and accuracy across regimes has become very relevant, highlighted even further by the recent penalty announcements from the UK regulator, the FCA:

    The FCA’s Final Notice on 19 March for the first of this year’s transaction reporting fines, stated:

    “Firms must take reasonable steps to ensure the accuracy and completeness of the transaction reports that they submit to the Authority. One way that firms can help to achieve this is by having controls in place to reconcile the completeness and accuracy of their transaction reporting process.”

    The most recent fines were admittedly for transaction reporting inaccuracies under MiFID I, and MiFID II sanctions are not yet known or been broadcast. But it is only a matter of time before the next firm is penalised and this could well be for post-trade reporting inaccuracies (known unknowns). Stephen Hanks, Head of Markets Policy at the FCA, mentioned at an conference on 16th April that, “poor data quality is still being sent to APAs and that the FCA will continue to work with investment firms to improve quality as a priority”.

    What Now?

    MiFID II transaction reporting has clearly taken a regulatory priority since go-live but post-trade transparency reporting, its just-as-important sibling, is just as key. The past year’s Level 3 Q&As have brought clarity to previous ambiguous regulatory text so firms should now have a greater understanding of their reporting obligation but do they have the testing and controls in place?

    Stephen Hanks stated; “There are still issues we see in reports and we are particularly disappointed to still be seeing errors in reports which would have been errors under MiFID I, never mind MiFID II.”

    Really! Why? When??

    Yes, in amongst the turmoil of BRiFID, investment firms and regulated markets have a near to real-time responsibility to make sure their RTS 1 equity-like and RTS 2 non-equity trades are reported within one minute and 15 minutes respectively (reducing to five minutes by 2021). The responsibility wording is key. Firms may think they do not have a reporting responsibility or they may have asked their brokers to report on their behalf but have firms put in place the correct control framework to prove this if the regulators come calling?  Could this highlight a firm’s unknown unknowns?

    MiFID II has now been live for almost 15 months. With Brexit there is the very real situation that post-trade transparency reporting will need to be directed to either the EU or UK APA as well as liquidity shifting away from the main markets and the impact of ESMA’s Trading Obligation views.  This is a good time to make sure you’re also compliant with post-trade transparency reporting as well as transaction reporting. 

    What next?

    If you have any doubts about whether your post-trade transparency reporting and controls are up to the required standard, we can help. We have a proven track record in helping firms tackle their regulatory reporting issues and risks head on – and helping them to avoid censure. Our ReportShield™ quality assurance services provide everything you need for reporting assurance including a bespoke control framework, quality assurance testing of all fields on all reports, reference data testing, reconciliation and completeness checks and training. Contact us to find out more. 

  • FCA publish Market Watch 59

    FCA publish Market Watch 59

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

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

    Valid but incorrect reports

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

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

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

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

    Instrument Reference Data

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

    Errors and omissions notifications forms

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

    How Kaizen can help

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

  • ANNA alleviates the SFTR Issuer LEI Conundrum

    SFTR presents firms with many data challenges, including capturing the correct issuer LEI. There are ten unique instances in which reporting parties are required to provide an LEI and one of the most challenging of these is the LEI for an issuer of a security.     

    The Association of National Numbering Agencies (ANNA) and the Global Legal Entity Identifier Foundation (GLEIF) announced the go-live for their new initiative to start linking ISIN codes with LEIs on the 4th April 2019.

    The published ISIN to LEI mapping will be freely available on the GLEIF website and already contains mappings for in excess of 1 million ISINs. While details of the issuer LEI are already available on the FIRDS database for securities admitted to trade in the EEA, coverage is lacking outside this region. Given the global nature of collateral used in SFT transactions and the requirement to populate the issuer LEI for every piece of security collateral, this is a very welcome development to facilitate the reporting requirements.

    We hope in future that such an initiative extends further into other SFTR reference data elements such as the CFI codes, maturity of the security (where applicable), security type and high level security quality. Nevertheless this is a valuable contribution to successful reporting.

    Did you know Kaizen provides training on the SFTR reporting requirements? For further details, please see our SFTR Reporting Core Training page.

     

  • Lack of training results in transaction reporting breaches

    Lack of training results in transaction reporting breaches

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

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

    Help is at hand

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

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

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


    ¹ FCA Final Notice to Goldman Sachs

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

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

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

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

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

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

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

    What went wrong?

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

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

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

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

    Lessons for MiFIR transaction reporting

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

    Get peace of mind in your reporting quality

    Our blog about the fine two weeks ago asks ‘could it have been you?’ and if you have any doubt, it is important to act now.  These two fines should be a wake up call for senior managers to get their reporting controls up to standard – and fast. This is exactly what we here at Kaizen exist to do.  We have a proven track record in helping firms tackle their trade and transaction reporting issues and risks head on – and helping them to avoid censure whether it is for MiFIR, EMIR, Dodd-Frank or another G20 regulation.

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

  • SFTR Regulatory Technical Standards published in the Official Journal

    SFTR Regulatory Technical Standards published in the Official Journal

    Click to enlarge

    We now have legal certainty around the SFTR Article 4 reporting timelines as the ten delegated acts, implementing regulations and annexes have been published in today’s Official Journal of the European Union. Each respective delegated regulation is available here. These requirements appear to be unchanged from those published and adopted by the European Commission on 13th December 2018.

    Timelines

    The SFTR Regulatory Technical Standards (RTS) and Implementing Technical Standards (ITS) come into force 20 days after publication (11th April 2019). This provides the basis behind reporting obligations becoming live on the following dates:

    • Monday 13th April 2020 – Credit Institutions (Banks) & Investment Firms
    • Monday 13th July 2020 – CCPs & CSDs
    • Monday 12th October 2020 – Pension Funds, Insurance/Reinsurance Companies, AIFs & UCITs (Buy-side)
    • Monday 11th January 2021 – Non-Financial Institutions.

    It’s time to get ready…

    Now that we have legal certainty, firms should be fully engaged in SFTR planning, building, testing and controls initiatives in readiness for go-live. We can help to meet your training, scoping, pre-go live testing, vendor selection, controls agenda and post go-live quality assurance to ensure reporting accuracy for this most complex of reporting requirements.  Please contact us for a complementary consultation or find out more in our SFTR section of our website.

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

    FCA MiFID reporting fine – could it have been you?

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

    Tough line

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

    What failings did the FCA identify?

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

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

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

    Systems and controls

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

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

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

    Lessons to be learned

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

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

    Firms need to react

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

    Senior Managers liable

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

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

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

  • Senior Managers Regime – are you ready?

    Senior Managers Regime – are you ready?

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

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

    The FCA states its aims are to:

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

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

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

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

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

  • Swiss Derivatives Regulator FINMA Recognises UK Derivative Regulations Ahead of Brexit

    In a move aimed at safeguarding regulatory compliance for Swiss derivative market participants trading under foreign law, the Swiss regulator, FINMA has provisionally recognised the derivative regulations of the UK with respect to reporting, clearing and risk mitigation obligations.

    At present, the UK falls under the territorial scope of EMIR and the clearing obligation (Art. 14 EMIR transposition act), reporting obligation (Art. 19 EMIR transposition act) and risk mitigation obligation (Art. 21 EMIR transposition act) offer equivalence with the relevant Swiss legislation (cf. Art. 97 (1) FMIA; Art. 104 (1) FMIA; Art. 107 (1) FMIA). The post-Brexit recognition of equivalence will enter into force when the EMIR transposition act passes into UK law.

    This announcement was made in FINMA Guidance 01/2019 BREXIT: Recognition of UK derivatives regulations. It should mean that firms subject to Swiss obligations to report can continue to use the UK’s ‘Recognition of Equivalence’ in order to report via a UK trade repository using a continuation of the ‘EMIR’ format.

    We are currently developing regulatory testing to meet quality assurance requirements for Swiss FINMA Finfrag and Sesta derivative and securities transaction reporting obligations. Please get in touch to discuss your requirements.  

    We’ve also published a Brexit White Paper which looks at the implications for reporting. Download it here to find out what you need to do to get ready by 29 March. 

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

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

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

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

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

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

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

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

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

  • ESMA updates Q&A on MiFIR and EMIR reporting

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

    Impact on MiFIR data reporting

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

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

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

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

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

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

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

    When should an instrument be terminated in FIRDS?

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

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

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

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


    Impact on EMIR Data Reporting

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

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

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

    Q38 – Trades terminated before the reporting deadline

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

    Q50 – Reporting of Confirmation Means

    ESMA states:

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

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

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

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

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

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

  • MiFIR transaction reporting –  a happy 1st birthday?

    MiFIR transaction reporting – a happy 1st birthday?

    January 3, 2019 marks the first anniversary of MiFIR transaction reporting and what a joy it has proved to be!  The changes introduced last year were truly transformational with new asset classes being brought into scope, new reference data standards to contend with and a massive increase in the number of the fields to be reported. Many operations and compliance staff will still have unhappy memories of last year’s struggle to implement the changes over the festive period to be ready for go-live. Despite the magnitude of the task, most participants will look back in relief that it wasn’t quite the fiasco many had feared. However, even one year on, there are a number of outstanding issues to keep us all awake at night…

    Reference data

    Perhaps the most difficult part of transaction reporting is knowing exactly what instruments are reportable. Many have assumed this is simple as ESMA’s Financial Instruments Reference Data System (FIRDS) contains all the reportable instruments. Unfortunately, this is not quite true! For a start, FIRDS does not provide details of index constituents or the underlyings to third country derivatives and depository receipts – the onus is on firms to work this out for themselves. Perhaps more importantly, the quality of FIRDS, whilst much improved since go-live, is still not good enough. We still have the FCA’s warning in MarketWatch 54: “Please note that ESMA states that it cannot take responsibility for this information being complete, accurate or up to date”. This is frustrating for firms because if they send a report with an instrument identifier that is not contained in this database within seven days of receipt of the report, it will be rejected and sent back to the reporting firm. This is almost a catch-22 situation for firms as it is now a breach to over-report or to under-report, but they still face the possibility of having their reports rejected even if they are correct because of the FIRDS limitations. Whilst the regulators demand “complete and accurate” transaction reports from firms they cannot ensure the quality of the essential reference data firms need to meet this obligation.

    Legal Entity Identifiers (LEIs)

    Many firms were concerned that they couldn’t get LEIs for all their counterparties they traded with ahead of go-live. This was particularly concerning as ESMA’s validation specified that “the initial registration date of the LEI shall be equal to or before the trading date” so firms couldn’t implement a fix if they had made a reportable trade against a counterparty without an LEI. However, an early Christmas present from the regulators postponed this validation until 3 July 2018 and firms have been largely successful in persuading these entities to get LEIs or in getting LEIs on their behalf so that they can continue to trade with them.

    Transaction Reporting Guidelines

    Most participants are grateful for ESMA’s extensive transaction reporting guidelines  and there is no doubt that they helped firms’ preparations enormously (compare and contrast with the EMIR Q&A!). However, nobody can say that they are an easy read or that they cover every trading scenario. This is only to be expected as MiFIR is a very complex reporting regime and regulators cannot envisage all possible trading scenarios across all member states. A number of firms have been frustrated by their local NCA’s inability to respond to every question, but this is a feature of harmonised regulation – it naturally prevents NCAs from offering definitive advice or interpretations outside the ESMA texts. This could present additional risks for firms making their interpretations from the available text.

    Complete and accurate reporting

    This is the simple demand from the regulators, but it is far from simple for firms to meet it. With the scale of the changes, nobody could justifiably expect implementation to be perfect. The industry was grateful for reassuring words from the FCA ahead of go-live that they could continue to work with the regulator to fully meet the requirements, provided that they could demonstrate that they had prepared well for implementation. However, there are now signs that the FCA might be less accommodating.

    In its mid-year industry forums, the FCA fired a warning shot that firms could expect a less tolerant attitude. They’d had six months to ensure their systems and controls were adequate to ensure complete and accurate reporting. We also see a danger in firms assuming that a reduced number rejected reports is an indication that their reporting is up to standard. Unfortunately, the validations only capture the tip of the iceberg of incorrect reports – there are a large number of valid but wrong reports submitted by firms.

    Data quality – round 2

    Basic validation can only capture basic errors and firms should be aware that all the NCAs are now starting to employ more intelligent ‘business rules’ to uncover reports that have passed validation, but are still incorrect. There is a temptation for firms to believe that it is “job done” for MiFIR transaction reporting now a year has passed by, but it is increasingly important that firms test the accuracy of their reports to the regulators and we are increasingly seeing evidence of this as the FCA has begun sending letters to firms pointing out errors.

    Regulators will also want to see evidence of reconciliation of their transaction reports. Firms need to be aware that this isn’t simply checking that their competent authority has received all the reports they have sent.  The requirement is clear; firms must ensure the details of the reportable trades they have made match exactly with those in the reports they have sent to the competent authority and that reports have been made for all the reportable trades.

    But…help is at hand

    Ensuring reports are complete and accurate is an extremely difficult task, not least because the rules and guidelines have become so extensive and so complex. Unfortunately, “difficulty” is not an adequate excuse for firms failing to meet the regulators’ demands and firms need to remember that the FCA has a strong track record of using sanctions, including fines, to encourage firms to submit complete and accurate transaction reports.

    At Kaizen, we provide quality assurance testing of all reportable data to identify incorrect transactions. We can also reconcile all trades in your books and records with data received by the regulator, identifying under and over reporting with matching on specific fields. Additionally, we deliver training on the reporting requirements and provide a control framework tailored to your business. Find out more about our ReportShield™ assurance service or contact us to find out how we can give you peace of mind in your regulatory reporting quality.

  • Santa’s SFTR gift extends to EMIR

    Santa’s SFTR gift extends to EMIR

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

    No real change

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

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

    SONIA

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

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

  • SFTR: The final countdown

    SFTR: The final countdown

    UPDATED 18 December with additional links and further details on timelines for trade repository reconciliations for certain fields.

    Now that the ITS and RTS have been released, we have greater clarity on the nature of the European Commission standards for SFTR as well as the timelines. Our SFTR specialist Jonathan Lee highlights the key changes and the timeline for implementation. 

    On Thursday 13 December 2018, the European Commission (EC) adopted Regulatory Technical Standards (RTS) and Implementation Technical Standards (ITS) covering Article 4 ‘Transparency of SFTs’ reporting requirements under Securities Financing Transaction Reporting (SFTR). This critical step puts the wheels in motion for SFTR to become a live reporting obligation and sets an increasingly clear timeframe for the reporting to start from April 2020.

    Official links: EC RTS, RTS Annex 1, and EC ITS and ITS Annex 1 and RTS for Trade Repositories (TR), RTS for TR Annexes and RTS for Access to details of SFTs held in TRs.

    SFTR go-live timeline 

    The RTS and ITS have been subject to some minor revisions since the ESMA publication, therefore we can confirm that it will be subject to a three month scrutiny period by the European Parliament & Council (not the one- month period for an unchanged RTS, nor the six-month period for an RTS subject to significant, material change). Following this scrutiny, it will be published in the Official Journal of the European Union.

    The timeline from here is as follows in the graphic below, although experience tells us to leave approximately one month leeway around these dates:

    SFTR reporting timeline infographic
    Click image to enlarge

    Changes to the RTS

    While this announcement was much more about certainty of timing (after an extended delay), enabling European SFT counterparties to plan and budget for implementation, nonetheless there are some changes of note relative to the 31st March 2017 ESMA text. We can confirm that:

    1. It will be possible to include agent lenders on repo trades.
    2. There is a not-applicable option on termination optionality for repo and securities lending trades.
    3. There is more substantive guidance on the Unique Trade Identifier (UTI) creation waterfall (see Article 3, page 4 of the ITS).
    4. Timelines for Trade Repository reconciliations for certain fields have changed. The following fields in the Transaction Data table Loan section: Security quality, Maturity of the security, Jurisdiction of the issuer, LEI of the issuer and Security type  – have been brought forward to Day 1. They were previously Day 1 +24 months in the 2017 ESMA text. This will present a more pressing data quality challenge. As a small concession in Transaction Data Collateral section: Collateral unit of measure, Price currency, Price per unit and Collateral market value have been pushed back from Day 1 to Day 1 +24 months. This brings the importance of independent reference data testing to the fore. 
    5. Finally and perhaps most significantly, any bad blood between the EC and ESMA over the adoption of UTIs and branch LEIs appears to have ended. The EC has stated that that once standards are finalised and considered suitable for the purposes of reporting SFTs, the regulation will be amended accordingly. In the interim, ISO codes should be used to identify branches and bilaterally agreed UTIs should be used to identify SFTs.    

    We can help you put the right controls in place

    As we look forward to the festive season and find time to step away from all this talk of SFTR, we would encourage you to ensure that projects are now underway. Now is the time to start SFTR budgeting, hiring, planning, building and thinking about testing, controls and governance if your project has not already begun. 

    Need some help with your SFTR reporting implementation? Contact us for a consultation to find out how you can put the right controls in place to ensure accurate and effective reporting from day one. We are also rolling out an SFTR training course early in 2019 so again, please get in touch to register your interest or find out more.

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

  • “The most exciting thing about Kaizen is the ambition of the company”

    “The most exciting thing about Kaizen is the ambition of the company”

    Apply here to be Kaizen’s next Data Analyst Apprentice

    We’re looking for another data analyst apprentice! To get a taste of what it’s like, we asked our first apprentice Cavan Frier, who started with us in September about his experience so far. 

    Why did you want to work for Kaizen?

    “The most exciting thing about working for Kaizen is the ambition of the company and how it is constantly growing. This appealed to me as I am also at the very start of my career with so much potential, so as a company and an individual we are on similar paths. I think the scope for how much of a success Kaizen could be in the years to come is huge and I am very proud to be a part of it.

    The values of the company are very important to me and I think are key to the success of Kaizen so far.

    The team of people at Kaizen (Kaizeners) you get to work with welcome you like a new family member, which really helps when you join the company as you hit the ground running when you start and settle in really quickly.”

    Why did you want to become an apprentice?

    “I wanted to become an apprentice because I love learning, but I wanted to use what I learn on a day-to-day basis, knowing that what I am learning is purposeful and relevant to the role that I grow into. I could have gone to university but since starting my apprenticeship with Kaizen I am really glad I did not go down that route.

    I love working in the office environment where I learn something new every day and enjoy playing my part in my team.

    The buzz of London is something that gets me up in the morning and the experience I have already gained from my apprenticeship so far is priceless, from collaboration and communication with colleagues, to going on courses and working on projects that develop my skills as a data analyst.”

    What have you been working on?

    “I am currently working on the delivery of our accuracy testing for EMIR and Dodd Frank and am involved in the testing development for MiFID II and SFTR. I have also been on a data analyst’s concepts course and have passed my first BCS exam towards becoming a qualified data analyst.”

    We’re looking for another apprentice. What advice would you give them?

    “Go for it! Being an apprentice is a great way to start your career and you get-on-the job experience most graduates will not gain until after university when they are 23.  In my opinion this experience is invaluable. You will get a real understanding of the working world and what is expected of you in your role and this allows you to know exactly what your job will entail when you finish your apprenticeship.”

    Are you another Cavan?  Apply to be our second data analyst apprentice via the government’s apprenticeship website (please, no recruitment agencies). If you are interested in apprenticeships more generally please contact Firebrand Apprenticeships.

  • FCA data extract will now include transaction submission date

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

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

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

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

    For more information visit the FCA website.

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

  • SFTR RTS endorsement is still wait and see

    SFTR RTS endorsement is still wait and see

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

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

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

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

    (*) The seven technical standards are:

    • RTS and ITS on SFT reporting
    • RTS and ITS on registration and extension of registration of trade repositories
    • RTS on data collection
    • RTS on data availability and access levels
    • ITS on exchange of data between authorities
  • Swaps get swapped. Changes to reporting of FX swaps under EMIR leaves us scratching our heads

    Swaps get swapped. Changes to reporting of FX swaps under EMIR leaves us scratching our heads

    As nerdy as it sounds, updates to ESMA Q&As are usually an exciting time here at Kaizen HQ. They give us fresh ideas for new tests to code up or clarity on topics that we were scratching our heads over. The newest addition however, TR Question 49 – Reporting of FX swaps under EMIR, has left us quite baffled and asking more questions than we had before.

    Since reporting go-live it has been market practice to report the two legs of an FX swap separately. This is true for all G20 regimes, not just EMIR. In FX trading systems, it’s common to book the two forwards separately, confirm them separately and settle them separately rather than book them as an actual swap. With this, it’s understandable why it has become the industry standard to report them this way.

    A new method of reporting swaps

    TR question 49 has flipped this on its head and is requesting firms to report both legs under the same Trade ID. This will mean that for firms with multiple reporting regimes two separate processes will need to be created to report the same trades. The long term goal of regulators globally should be to work towards a harmonized way of reporting. The new guidance feels like a step away from this ideology.

    Reporting of lifecycle events also becomes far more complicated. When one leg of the swap is compressed or terminated, the remaining leg transforms itself into a forward and needs to reported as a brand new report with a separate report.

    From a revenue perspective trade repositories could find themselves feeling a bit short-changed. Many trade repositories charge per trade. If the industry does manage to become compliant with the new way of reporting it would mean significantly less data reported.It’s also important to consider what hasn’t been written in the Q&A. Nothing has been mentioned about what firms should do with the billions of swaps that have already been reported. Surely it would be impractical to expect these to be back reported?

    Timing will harm data quality

    Generally, when new Q&As are published the guidance is effective as of immediately. For this, firms have been given a year to adapt to the new method of reporting swaps. Nothing in the validation has actually changed though, this means that nothing prevents firms from making the changes earlier or not making the changes at all. As a result, different firms will change at different times and this will be harmful towards pairing and matching figures.

    At Kaizen we’re all in favour of having clear rules on how trades should be reported. This is the only way data can be consistent and of high quality. This Q&A certainly meets this criterion but the thing that is surprising is that only selective consultation appears to have taken place in producing these guidelines. Unfortunately, this is something we’ve seen ESMA do before. Surely a better way to get everybody on the same page is to make writing them a collaborative effort.  Having proper time to test and provide feedback before new rules are officially published is considered a pre-requisite by many firms to meet the reporting requirements.

    We don’t believe anyone responsible for EMIR trade reporting is deliberately trying to shirk their responsibilities, but when surprises like this keep happening it’s no wonder that firms become blinded by change and can’t report correctly. 

    If you need help in adapting your EMIR trade reporting to the latest changes or for a discussion about your EMIR reporting quality, please contact us. 

    /fx-swaps-get-swapped-emir/

  • EMIR trade reporting: lifting the lid on pairing and matching

    EMIR trade reporting: lifting the lid on pairing and matching

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

    How do the TRs pair and match the trade reports?

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

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

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

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

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

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

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

    How good are the pairing and matching rates?

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

    Does this matter?

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

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

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

    What can firms do to improve matching rates?

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

  • SFTR: ESMA dismissive of proposed amendments from European Commission

    SFTR: ESMA dismissive of proposed amendments from European Commission

    ESMA have now published their opinion on proposed amendments to SFTR technical standards. This mirrors the letter that they published, sent to the commission on 4 September.

    ESMA dismiss outright the proposed changes made by the European Commission, citing the importance of the original text and the limitations of the Commission’s proposed alternatives. ESMA are adamant that they must continue to include LEIs, ISINs and UTIs in order to be consistent with EMIR and international developments in global standards (Branch LEIs and UTIs). They also state the desire to “Future Proof” SFTR.

    It is fair comment to suggest that some of the EC proposals did water down some of the ESMA proposed data standards for SFTR and that ESMA have made a number of valid points. If ESMA had decided to carry through these proposals then it was likely to introduce some confusion over the timely adoption of UTIs (without which trade repository pairing and matching would have become an even greater challenge). It was also likely to slow the international adoption of branch LEIs. 

    All in all, this would appear to be much ado about nothing. The changes (or lack of changes) from the original “Final RTS” published by ESMA on 31st March 2017 will not have any material impact on the SFTR delivery. It is just unfortunate that the pragmatic steps that the EC proposed to incorporate the option of including agent lenders on repo trades and in providing a not-applicable option for termination optionality on repo and securities lending trades will also be omitted.

    In practical terms, there is likely to be a few additional weeks of delay to the publication of the SFTR RTS into the official journal of the European Union as negotiations between ESMA and the EC continue. The EC could potentially overrule ESMA on some of these matters. This delay is likely to push out the go-live for SFTR reporting further into Q1 2020, starting with the banks & investment firms.

    For a consultation on your SFTR reporting preparation, please contact us.

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

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

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

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

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

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

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

  • Five things we learned at the Regis-TR SFTR workshop

    Five things we learned at the Regis-TR SFTR workshop

    We were delighted to attend the Regis-TR SFTR workshop in Frankfurt yesterday.  Here’s a quick summary of the key insights we picked up: 

    1. Data sourcing was perhaps seen as the greatest challenge, with c.40% of reportable fields not readily available from risk management and trading systems
    2. It is a significant logistical challenge to obtain data from so many sources (siloed businesses acting independently, tri-party agents, agent lenders, CSDs, legal and reference data hubs etc)
    3. Realisation that reporting hard-to-obtain data from such a large and disparate range of sources is an inherently risky business necessitating a rigorous controls environment (something Kaizen can help with) 
    4. Education is key, recent MiFID II experience and industry discussions indicate that many eligible reporting parties are thought to be blissfully unaware of their obligations under SFTR
    5. Pairing and matching obligations at trade repositories mean that firms need to become better at communicating with their counterparties to reap the benefits of a greater level of standardisation and operational efficiency while becoming ever more regulatory compliant.

    For a consultation on your SFTR reporting preparation, please contact us.  

    SFTR: Challenges of implementation

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

  • SFTR: Challenges of implementation

    SFTR: Challenges of implementation

    In Part 2 of our introduction to SFTR, Jonathan Lee looks ahead at the implementation of the regulation and some of the data quality challenges firms need to be thinking about now.

    STOP PRESS! The European Commission broke with protocol in publishing a letter sent to ESMA on 2 August (generally they do not publish in August), stating that they planned to endorse with amendments, the draft Regulatory Technical Standards (RTS) and Implementing Technical Standards (ITS). This gives ESMA a further six weeks to submit revised drafts that reflect these changes.

    The changes whilst minor, are extensive. There are a large number of changes in semantics, providing further clarity through simpler language. The material changes relate to concerns that LEIs for branches and standards around UTIs may not be ready in time for go-live. Furthermore, they have incorporated industry feedback that agent lenders may be used on repo trades and that there needs to be a not-applicable option for termination optionality on repo and securities lending trades.

    These amendments and the six weeks for ESMA to respond will introduce some additional delay to SFTR Article 4 reporting go-live. Nevertheless, we anticipate that the RTS will be published in the official journal of the European Union at the end of 2018 or early 2019 and that reporting will go-live for banks & investment firms in Q1 2020 with market infrastructures, fund managers and non-financial counterparties to follow at three month subsequent intervals.

    A herculean task

    Under SFTR, participants in the European securities financing markets will be required to provide daily reporting to a trade repository (TR) of not only every new trade, amendment, correction, error and cancelation but also the majority of lifecycle events, collateral valuations and legal entity wide collateral re-use statistics. This herculean reporting task will hand a legal obligation to all but the smallest non-financial counterparties to report between 61-128 fields (product dependent) across four reporting tables. Furthermore, reporting parties will be tasked with ensuring that between 36-48 of these fields can be matched between reporting parties (intra and inter trade repository) for ESMA to be able to interpret the data and the ESCB Datastore to be able to create the Europe wide data aggregations. We envisage that handling trade repository reconciliation queries on SFTR is set to become a significant and complex operational task post go-live.

    Bringing together securities financing markets

    Securities financing markets are currently more fragmented and disparate than many other markets currently subject to significant regulatory reporting regimes. There is generally less precedent, less market convention and less infrastructure in place than for many other markets. The regulation seeks implicitly to set about changing this. To put forward the repo market as an example, there are still many instances in which the functioning of the market is very settlements driven, there are many manual processes and any pre-settlement matching is limited in scope or subscription. SFTR will encourage many OTC telephone or messaging based trades to move onto venues. This would certainly help overcome many booking discrepancies, contractual and lifecycle handling differences between counterparties. It will also help in the creation of a common dataset to in turn be reported to the TRs.

    Data sourcing will be painful

    SFTR requires that reporting firms not only provide the common reporting standards (ISINs for collateral, LEIs for counterparties and collateral issuers, MIC codes for venues, CFI codes for collateral classification and unique trade identifiers (UTIs)) – with mandatory use of UTIs and branch LEIs potentially to be introduced later – but also much additional classification and derivation too. Many of the required fields are largely unfamiliar within this industry and will present data sourcing difficulties. Indeed, in many cases, firms will need to look beyond risk management, trading and settlement systems in order to source the data. Siloed securities financing businesses will also need to look beyond their own businesses to capture data across entire legal entities in order to meet requirements such as re-use reporting.

    Less risk, greater transparency

    ESMA and the European regulators have made it very clear that they require SFTR reports to be a true reflection of a firm’s books and records. They have provided very little sympathy for proposed pragmatic reporting solutions that ensure higher degrees of trade repository matching rates if this deviates from original trade bookings or fails to reflect fundamental business practice or booking discrepancies that the securities financing industry is experiencing. The regulators expect firms to be able to prove that they are continuing to evolve and improve both their booking and reporting practices to create an environment of less risk, greater efficiency and the greater transparency that comes from strengthening regulatory reporting compliance. The reporting deadline itself may prove something of a ‘Big Bang’ but ensuring that the controls and quality assurance framework continue to make evolutionary and iterative progress is not.

    Data quality assurance should be part of SFTR plan

    At Kaizen Reporting, we support trade association industry initiatives that encourage securities financing businesses to shape up in advance of SFTR go-live.  We also support bilateral reconciliations to better understand firms’ and industry reporting issues and the creation of industry-wide best practice documents to encourage enhanced booking practices and behaviours. In addition, we would urge reporting parties to embark on the incorporation of trade level and reference data quality assurance within their project plans. Firms should look to perform both internal and external reconciliations to ensure reporting data is complete, accurate and uncorrupted by systems. Furthermore, applying Kaizen’s ReportShield™ to your post go-live plans will help tremendously in ensuring Senior Managers are kept abreast of reporting quality and reassuring the regulatory authorities of the firm’s level of diligence. Contact us for an initial conversation about getting ready for SFTR reporting. 

    Read Part 1: SFTR – if you can’t beat em, join em which focuses on the background and context of SFTR.

  • SFTR: If you can’t beat ’em, join ’em…

    SFTR: If you can’t beat ’em, join ’em…

    In the first of a two-part blog, our newly appointed SFTR reporting expert Jonathan Lee looks at the background and context of the Securities Financing and Transactions Regulation. 

    The author of this blog is about to take an “If you can’t beat ‘em, join ‘em” approach in following our European regulators into their summer recess. The European Commission publication freeze will shortly kick in and the probable timeline for publication of the final Regulatory Technical Standards (RTS) for Securities Financing Transaction Reporting will be held back until September this year at the earliest. This in turn will result in SFTR Article 4 Reporting delayed until Q1 2020 for banks and investment firms, with market infrastructures, fund managers and large non-financial counterparties to follow at subsequent three month intervals.

    Waiting a little longer…

    Many of us working closely on the new Securities Financing Transaction Reporting European regulatory regime have been on tenterhooks ever since the publication of ESMA’s Final Report on Technical Standards under SFTR in March 2017. Indeed, the initial guidance was that the European Commission would decide whether to endorse the technical standards within three months of that date and for reporting for banks and investment firms to follow approximately 15 months later (September/October 2018). We have now slipped approximately 15 months from this original target date. Nevertheless, as September approaches, we are likely to finally have some report timing finality.  

    Securities financing influence is high 

    The premise for SFTR reporting has always been a little different from the mainstream reporting regimes exemplified by MiFIR, EMIR, Dodd Frank and so forth. Securities Financing markets are less widely understood and often seen as a market utility or service offering rather than a mainstream ‘risk’ market. Nevertheless, of the four markets covered by SFTR (Repo, Buy-sellback, Securities Lending and Margin Lending); EUR 7.25 trillion contracts were recorded as outstanding within the scope of the highly respected ICMA ERCC Semi-Annual European Repo market survey (for Repo markets alone) in December 2017. The ability of securities financing markets to influence leverage, liquidity and overall global systemic market function is high.

    Financial crisis

    SFTR Regulation (November 2015) stems from the financial crisis. Repo and other securities financing markets were seen at the centre of aspects of the crisis, perhaps most notably in the collapse of Lehman Brothers (September 2008). Concerns over shadow banking, the lack of transparency, build-up of leverage, interconnectedness and pro-cyclicality inspired much debate and discussion among G20 members from 2011. This culminated in FSB reports on Shadow Banking in October 2011 and further FSB reports specific to Securities Lending and Repo from April 2012 onwards. SFTR itself sets out to enact the FSB 2015 report “Standards and Processes for Global Securities Financing Data Collection and Aggregation.”

    The greatest challenge of SFTR is the extent to which European regulators seek to ‘gold plate’ the global guidelines. The Financial Stability Board (FSB) stipulates the need for retrospective, periodic, single sided, settled position level reporting that can readily be aggregated regionally and globally. The European regulation sets out the need for very granular, daily, two-sided, trade and lifecycle event level reporting. Invariably, this is going to be very challenging to implement, manage and control by reporting parties and perhaps equally tricky for regulators to interpret, comprehend and aggregate.

    Implementation of SFTR and data quality implications will be covered in a second blog from Jonathan early next week.

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

  • Tell me LEIs

    Tell me LEIs

    The six-month grace period granted by ESMA for reporting firms to obtain Legal Entity Identifiers (LEIs) ended earlier this month. At her recent speech in Paris, ESMA’s executive director, Verena Ross, marked that the ‘No-LEI-no-trade’ rule now forces entities trading in EU markets to have an LEI. This allows the regulator to know exactly who is trading and enables market data to be aggregated in a more accurate manner. Verena Ross also recommended that regulators across the globe follow suit and make similar mandates.

    Someone from the HKMA must have been listening, because on the same day as the speech they announced their intention to extend regulation on the use of LEIs. From April 1st 2019, reporting entities, HKTR members, CCPs and clearing service providers must report all new trades with LEIs. Parties that do not identify themselves in the ‘Reporting for’ field and updates to existing trades will not require LEIs just yet. Similar to ESMA’s grace period, reporting entities are expected to have a process in place to request their clients obtain an LEI.

    Our research shows that of the 250 or so HKTR members, 90% of them already have LEIs. Alongside this, DTCC noted in their feedback to the proposal that some 4,200 HK based entities already have LEIs. It’s possible that MiFID II has already broken the back of the burden of obtaining LEIs in other jurisdictions.

    LEIs are becoming the industry’s gold standard for trade party identification and they are evolving too. Last year GLEIF introduced level 2 data that gave birth to LEI parent reference data being embedded in the LEI.

    In the future, we hope that LEIs will continue to evolve and that other entity static data can be hardcoded into their DNA. Features like CFTC US person status or Canadian Local Counterparty Status would do the industry a huge favour in terms of getting their reference data correct.

    Reference data errors account for 50 per cent of errors found in our testing of regulatory reports. Our ReportShield™ reference data testing checks both counterparty and instrument reference data for accuracy and completeness including real-time check of LEIs.  Contact us for a discussion on improving the quality of your reference data.

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

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

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

    Reporting eligibility

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

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

    Incorrect fields being reported and risk of detection

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

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

    Obtaining data from competent authorities and ARMs

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

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

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

    Efficacy of reporting and communication from the NCAs

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

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

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

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

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

  • ESMA updates its EMIR Q&A

    ESMA updates its EMIR Q&A

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

    LEI changes due to mergers and acquisitions

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

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

    New but not new

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

    When a management company can be considered a counterparty

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

    Here’s the link to ESMA announcement here.

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

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

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

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

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

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

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

    Few investigations across Europe

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

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

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

    None

    BU

    CZ

    FI

    HR

    IE

    LV

    MT

    NL

    NO

    SI

    1 to 5

    FR

    EL

    SK

    UK

     

     

     

     

     

     

    6 to10

    AT

    DK

    PL

    SE

     

     

     

     

     

     

    11 to 20

    CY

    ES

    PT

     

     

     

     

     

     

     

    >20

    BE

    DE

    LU

    IT

     

     

     

     

     

     

     

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

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

    Penalties across the EU

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

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

    Country

    Percentage of maximum

    Max € (000)

    Notes

    Spain

    n/a

    –

    Variable no stated maximum

    France

    100.00%

    100,000

    Capped at less than 10x gain made or loss avoided

    United Kingdom

    n/a

    –

    Variable no stated maximum

    Finland (articles 4 & 10)

    10.00%

    10,000

    Capped at less than 10% turnover

    Sweden

    5.00%

    5,000

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

    Belgium (National Bank)

    5.00%

    5,000

    Capped at less than 10% turnover

    Italy

    5.00%

    5,000

    Capped at less than 10% turnover

    Greece

    3.00%

    3,000

     

    Ireland

    2.50%

    2,500

     

    Poland

    2.50%

    2,500

    < 10% of turnover

    Belgium (FSMA)

    2.50%

    2,500

    Capped at 3x gain made or loss avoided

    Luxembourg

    1.50%

    1,500

    Capped at 5x gain made or loss avoided

    Netherlands

    1.00%

    1,000

     

    Cyprus

    0.70%

    700

    Capped at 2x gain made or loss avoided

    Germany

    0.50%

    500

     

    Czech Republic

    0.40%

    400

     

    Austria

    0.15%

    150

     

    Malta

    0.15%

    150

     

    Latvia (legal persons)

    0.14%

    142

     

    Finland (articles 9 & 11)

    0.10%

    100

     

    Slovenia

    0.10%

    100

     

    Croatia

    0.07%

    67

     

    Latvia (natural persons)

    0.06%

    57

     

    Bulgaria

    0.04%

    40

     

     

    NCA powers across the EU

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

    Actions firms should be taking for EMIR reporting

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

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

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

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

  • Baskets, ISINs and bank holidays – ESMA publishes new guidance on EMIR

    Baskets, ISINs and bank holidays – ESMA publishes new guidance on EMIR

    ESMA has been busy updating its Q&As. Last week it was MiFID II and this week it’s EMIR. The newly updated Q&A gives guidance on how some specific fields should be populated and which competent authorities should receive certain data. They emphasise once again that simply passing validations is not good enough; the regulator is expecting accurate submissions.  In this blog, we outline some of the key updates. 

    Maturity date

    If maturity date falls on a weekend or bank holiday this is the date that is expected to be reported and not any adjusted date. From a matching perspective this makes logistical sense as different countries have different bank holidays. As well as this, for trades that have expiry dates many years in the future, bank holidays may not be known at the time of execution. I wonder however, if the trade’s adjusted maturity occurs at a later date than the unadjusted date, if we could see any failures to report some post-trade events that happen in between this period. Should ESMA have provided the same clarity for settlement dates?

    Underlying identification

    The guidance states that if an index does not have an ISIN it should be reported with the name that is identical to the names published by the index provider and include special characters. Trading systems tend to dislike special characters so there could be some circumstances where these are difficult to report. Lucky the S&P 500 has an ISIN!

    Access to data by competent authorities

    If the Cambridge Analytica scandal has taught us anything it’s that people care about who has access to their personal data. The same holds true for business data. Until now the guidance for derivatives where the underlying is a basket or an index has been for TRs to allow access to the data for all EU competent authorities. The new guidance is that authorities will only have access to the data if they share the same country as the ISIN or any ISINs that that basket or index is composed of. Other authorities will be allowed access to the data if they need it to carry out their responsibilities. It’s a well-meaning sentiment but it is a difficult change to implement and there are a lot of questions around this which we will follow up separately.

    Deliverable Currencies

    The new Q&A mandates that deliverable currency should be populated in most cases. Our accuracy testing reveals that this is not usually the case within the industry and repositories generally classify the fields as optional. In order to comply with the regulation some changes will need to be made in participants reporting processes.

    Effective Date

    The last new piece of guidance is that if there is no effective date specified in the contract it should be reported as the same date of the execution of the derivative. This is already fairly common practice in the industry but the guidance does not explicitly mention novation events. In the case of a novation where the contract does not contain an effective date, should it be reported as the execution date of the original contract or the date of step in? You decide … just make sure your counterparty agrees!

  • MiFID II Q&A update: New guidance on complex trades and national ID validations

    We are five full months into MiFID II. Competent Authorities are still experiencing teething issues with the instrument data, validations, response messages and providing reporting firms with extracts of their submitted reports. Firms are increasingly moving their focus from addressing validation issues and handling of response files to looking at the accuracy of their reporting. All parties should be working on the most pressing issues following the 80/20 rule.

    “Firms are increasingly moving their focus from addressing validation issues and handling of response files to looking at the accuracy of their reporting.”

    Working on validations to get all the transaction reports accepted by the regulator may not be the most pressing issue.  Firms can still be reporting 100% of their records inaccurately. It is therefore important that attention is turned away from validations to accuracy testing and identifying the valid but wrong population.

    Whilst there are many areas of reporting uncertainty, ESMA has decided to focus its guidance on strategy trades. Strategy trades are relatively rare in the reporting world and affect only a very small proportion of total reportable activity. 

    This post summarises the new guidance from ESMA.

    Complex Trade ID

    A strategy trade is a trade which is composed of more than one financial instrument or legs, where the execution of the trades are contingent on each other and a single price is given for the strategy contract as a whole. 

    When transaction reporting strategy trades, the Complex Trade ID (field 40), must be populated with a code that links each of the legs. This code must be unique to each strategy trade for the reporting firm. ESMA’s latest update to its Transaction Reporting Q&A on Friday (25 May) provides more guidance on how and when the Complex Trade ID should be populated. 

    The aim of the Complex Trade ID is to notify the users of the transaction report that the instrument reported is part of a broader strategy trade and to enable the user to identify any related transactions.  In the guidance they make it clear that:

    • The price reported is the price of the strategy as a whole not the price of the individual leg being reported.
    • The Trading Venue Transaction Identification Code (TVTIC) should be populated for each reported leg of the strategy. Presumably, this would only apply where the strategy itself was executed on a trading venue and the legs execute as part of that strategy. There is more complexity here and more scenarios which the Q&A does not address.  
    • The Complex Trade ID field must be populated even where only one leg of the strategy trade is reportable. It is still a strategy trade and the price must reflect this.
    • Where the strategy itself is allocated an ISIN you still report the individual legs and not the strategy as a whole.
    • In terms of reference data to be reported for strategy trades, the Q&A makes clear that the reference data for the legs must be submitted, not the reference data for a “strategy instrument”.

    National ID validations

    The only other update in the Q&A relates to the validations published for the national identifiers. We have commented in a previous post as to the complexity the approach gives rise to. This is the second update to these validations that have been published.  The latest is:

    • Czech Republic: “It should be noted that the special character “/” is just a separator and should be omitted in transaction reports.”

    Presumably there have been problems with firms including “/” in their identifiers.

    Kaizen’s accuracy testing checks all MiFID II data fields to ensure your reporting is correct. To find out more about how we can help you avoid the ‘valid but wrong’ problem, please get in touch. 

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

    FCA makes data integrity a clear focus for 2018/19

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

    MiFID II

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

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

    Market integrity

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

    The FCA goes on to state that:

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

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

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

    RegTech developments

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

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

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

    Monitoring firms’ use of data

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

    Cryptocurrencies

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

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

  • CFTC hints it will follow in ESMA’s footsteps

    CFTC hints it will follow in ESMA’s footsteps

    In the world of derivatives reporting the Dodd-Frank Act (DFA) may be the older cousin of EMIR but if we think about which regime is more mature, EMIR takes the cake. Since the reporting go-live in 2014, EMIR has grown through several different amendments to arrive at where we stand today. Its strict validation requirements aim to provide the data quality that is necessary to measure systemic risk. The CFTC on the other side of the Atlantic has remained relatively quiet since reporting go-live at the end of 2012. That is, until now…

    More complete and accurate data

    The CFTC has published a White Paper which gives a view of which direction the US regulation is heading towards. No awards for guessing that they want ‘more complete, more accurate, and higher quality data’. How can this be achieved? The CFTC is proposing to elaborate on requirements of part 49 to ensure that counterparties and repositories are continuously assessing the integrity of their data and insisting that any inaccurate or missing data is corrected. This can only be achieved if the requirements are clear. In the paper, CFTC admits that part 45 data fields are not well defined and this has led to inconsistent reports which cannot be relied upon for any meaningful analysis.

    The proposal is to take on board the CPMI-IOSCO harmonisation of data elements that were published in April. Amongst others, the report details that LEIs should be mandated to identify counterparties and MICs should be used to identify trading platforms. Sounds quite familiar, doesn’t it? As well as this there is an indication that collateral margin fields will be put in scope for reporting as is the case in EMIR and ASIC jurisdictions.

    Relax of timeliness requirements 

    Further harmonisation is suggested by the timeliness requirements being relaxed to a T+1 model. The philosophy is that if Rome wasn’t built in a day, it won’t collapse in a day either. If firms take the time to agree and confirm the terms of an OTC contract before reporting it, then the data received will be of a higher quality.

    Swaps Regulation Version 2.0 won’t be a complete copy and paste of EMIR though. There is no suggestion that the regime will move to dual-sided reporting and the real-time requirements of part 43, although maybe changing as well in terms of notional capsizes, will remain a unique aspect of Dodd-Frank reporting.

    No exact details or timescales are available yet however we’re pleased to remind our clients that our ReportShield™ accuracy testing service already checks the correctness of these fields under Dodd-Frank, so you can be reassured that you’re already one step ahead of the regulator. Alternatively, if you’d like some assurance that your DFA reporting is accurate, timely and complete, please don’t hesitate to contact us.

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

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

  • Kaizen officially presented with Queen’s Award for innovation

    Kaizen officially presented with Queen’s Award for innovation

    Kaizen Reporting has been formally presented with the prestigious Queen’s Award for Enterprise in innovation by the Lord Mayor of London, Andrew Parmley at a ceremony at Mansion House.

    The celebration followed an audience with the Queen at Buckingham Palace attended by our CEO and Founder Dario Crispini and Lead Data Scientist, Tamer Onder in July this year.

    The Queen’s Award was awarded to Kaizen in April this year for outstanding achievement in innovation for our ReportShield™ accuracy testing service that provides financial firms with full visibility of the quality of their regulatory reporting.

    The Lord Mayor said Kaizen was one of only very few firms in the City to receive the award, and that the work we were doing to improve data standards in the industry was pioneering:

    “What you are doing is incredibly important for the future of the city, for regulation and for the country,” he said.

    Kaizen CEO Dario Crispini said, “It’s an incredible honour to receive the award from the Lord Mayor of London at Mansion House, just down the road from our offices.  Winning the Queen’s Award is testament to our fantastic team who has developed and delivered this unique solution for firms with reporting obligations.”

    Read our press release from earlier in the year or find out more about ReportShield™ accuracy testing.

  • FCA’s first EMIR reporting fine highlights importance of robust testing and controls

    FCA’s first EMIR reporting fine highlights importance of robust testing and controls

    The £34.5 million fine issued this week by the FCA is the first enforcement action for failing to comply with Article 9 of EMIR and highlights the increasing importance the regulator is placing on data quality.

    It was generally accepted that the regulator would eventually take enforcement action against a firm for EMIR breaches and there would have to be a firm first in line.  In this case it was Merrill Lynch International, however it could probably have been one of many firms that have struggled to deal with the EMIR reporting requirements. 

    The FCA understands that reporting won’t be 100% all the time however its final notice highlights insufficient testing to ensure the accuracy and completeness of reports as well as weaknesses in oversight arrangements that would have contributed to the under reporting of 68 million exchange-traded-derivatives over a two year period. 

    Poor quality data is industry wide 

    While these are serious failures, we would argue that they are not unique to Merrill Lynch.  Poor quality data is a widespread industry problem, something that the regulator and we here at Kaizen have been highlighting for some time. 

    Just last week Ana Fernandes, of the FCA’s Markets Reporting team, focused on the issue of data quality at an industry conference we attended.  She highlighted the importance of  having comprehensive in-depth testing and reconciliations in place at a frequency appropriate to trading volumes.  Firms must test for the accuracy and completeness of their transaction reports and have the appropriate oversight arrangements to detect and remedy systemic problems.  Ana said there were ‘high expectations’ come 3 January 2018 when MiFID II goes live that they would see better data and this is as essential for EMIR, as it is for MiFID and MIFID II.

    Just the tip of the iceberg

    Last year we published our analysis of FCA MiFID I reporting fines which shows how easy it is to get reporting wrong.  More often than not, firms continue to get false confidence from the validations provided by ARMs and Trade Repositories without testing whether the data at source is correct.  Ana in her speech last week focused on just that, “Don’t think that because the file has gone to the ARM and the FCA that it is done” she said. 

    The final notice clearly demonstrates the FCA’s expectations for robust and comprehensive testing of reporting.  This requirement is more clearly articulated for MiFID II, where testing for accuracy and completeness is mandatory under RTS 22, Article 15 and these controls should be in place at go-live.  Similarly, from 1 November (next week!) when EMIR Level 3 goes live, a lot of reporting requirements currently in the EMIR Q&As become part of the Regulatory Technical Standards and therefore become more easily enforceable by the national competent authorities.

    The FCA says the fine, the largest so far, ‘reflects the importance’ it puts on this type of reporting and the important role it plays in ensuring a transparent market. The action also shows that the regulator will fine you more if you’ve got it wrong previously and that it is applying the same approach to EMIR as it does with MiFID in terms of fining on a per record basis. 

    Expect more fines as regimes mature

    As the G20 reporting regimes mature, we are seeing a general trend of increased enforcement activity.  The CFTC has been active recently re DFA, and we also saw the recent ASIC fine by the Australian regulator so I expect further fines to follow.

    Improving firms’ reporting data quality is the reason we at Kaizen exist.  We have several clients that report over 100k trades per day to a trade repository.  With these types of volumes, it’s very easy to end up facing an eye watering fine which is why we have designed our services to protect both the firm and the individuals with reporting oversight responsibility under the senior manager’s regime. 

    Please don’t hesitate to contact us if you would like to discuss your regulatory reporting data quality or any of the issues raised in this piece.

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

  • CFTC Fines Top Tier Bank for Legal Entity Identifier (LEI) violations

    CFTC Fines Top Tier Bank for Legal Entity Identifier (LEI) violations

    It sounds like MiFID II’s mantra of ‘No LEI, No Trade’ has travelled across the Atlantic and resonated with the CFTC. 

    Last week it was announced that a tier one bank has been fined $US 550,000 for failing to update its counterparty LEI information.  Whilst the CFTC’s regulation is not as strict as its European cousin’s, it does expect that LEI information is provided when it becomes available. 

    Although it’s not one of the largest fines they have ever issued it does give us a new insight to the sort of checks they are performing.

    Specifically, the CFTC’s investigation found that a design flaw in the bank’s architecture failed to update the regulator when an LEI became available for a counterparty and all other aspects of the contract remained the same.  Full details of the penalty can be found on the CFTC website. 

    On first thought it may sound like updating the counterparty identifier is a simple change to implement but dig a little deeper and you can see how it is an easy pitfall to find yourself in.   A small firm that does not have an LEI will not be the reporting party when they are facing a tier one bank.  Realistically, they will be paying little or no attention to their derivatives reporting and have little incentive to notify the bank when they acquire an LEI.  The bank could easily have hundreds of similar small firm clients and tens of thousands of transactions to report each day.  Unless a dedicated process exists to check for an updated LEI, it is a simple thing to miss, especially when none of the economics of the contract change.

    Is your counterparty LEI information being reported correctly? Kaizen’s ReportShield™ accuracy testing and reference data testing identifies all counterparty errors so they can be remedied quickly and easily.  Please get in touch to discuss your LEI or MiFID II reporting challenges.

  • New rules = new tools: DTCC simplifies technology ahead of EMIR rewrite

    New rules = new tools: DTCC simplifies technology ahead of EMIR rewrite

    This week we attended the DTCC’s Partners Forum in London to get a taste of what the future holds for firms reporting data to the global trade repository (GTR).  As reporting rules become more complex across all global jurisdictions, the DTCC is aiming to simplify the functionality of the GTR.  Of course anything that makes reporting more straightforward is something we welcome here at Kaizen but there is a lot of work to do to prepare and resource appropriately to make sure you comply with the both changes in obligations and at DTCC. 

    The next phase of the GTR Re-architecture is going to be aligned with the go-live weekend for EMIR RTS on October 28th and is scheduled to be rolled out globally in 2018.

    If you have access to DTCC’s learning center you can see all of the latest updates here.

    Straightforward ingestion

    The new harmonized template is a ‘one size fits all’ solution to understanding how to format and upload data to the repository.  It acts as a one-stop-shop for finding the required information across all five asset classes and also enables filtering on specific products within asset classes, giving greater clarity on what fields are required to be reported.

    Practical processing

    DTCC have also adopted a new ‘latest is greatest’ approach in trade state calculation.  This removes the complexities of multiple submissions being interdependent on each other. UTI locks will also become a thing of the past which will make successful submission to the GTR easier.  However, this puts more responsibility on data submitters to ensure that counterparties are correct and to remove any incorrect submissions.  Delegated submissions will also be split into two parts and allow for separate processing per counterparty.

    Error messages are also being redesigned and will give greater insight into exactly where the error lies and what needs to be corrected.

    Upgraded reports and portal

    What we view as the greatest benefit of the Re-Architecture is the new way in which counterparties and third parties will have access and visibility to data.  Participants will have absolute transparency on what has been reported to the regulator and who it has been reported for.  Historic data will also be retrievable with the new search tool.  Eventually recurring queries can be scheduled to allow bespoke reports to be generated for every user on a timeline that will suit them.

    Changes in context

    The DTCC Re-Architecture is a big step in the right direction in terms of simplifying the way data is submitted and viewed but there is a lot of work to do to get to a place where you can truly take advantage of its benefits – and the clock is ticking.

    We are helping a number of firms understand and get the correct controls in place for the new EMIR RTS obligations due to come into force on I November, please get in contact if you would like to have a conversation about this or any other upcoming changes to reporting obligations. 

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

  • Big EMIR changes in MiFIR’s shadow and deadline fast approaching

    Big EMIR changes in MiFIR’s shadow and deadline fast approaching

    With so much focus on delivering reporting functionality for the upcoming MiFIR obligations, we shouldn’t forget the substantial changes required from EMIR’s Revised Technical Standards (RTS 2.0).

    The revised RTS was published in January in the Official Journal of the European Union and updated Q&As were published in April.  

    When will obligations come into effect?

    The new legislation will come into effect on 1 November 2017 with the exception of one rule, which came into effect immediately…the extension of the back-loading deadline (which we covered in this blog).  This came as a sigh of relief to those who had not yet started this task yet and a nasty kick in the teeth to those who had spent many painful hours digging through their archives searching for ancient data.  The justification for extending the deadline is that terminated trades do not increase systemic risk.  Given that one of the key objectives of the regulator is to identify systemic risk, the question ‘why does the regulator need this data?’ needs to be asked.  What will happen in 2019 when the new deadline approaches?

    Standardisation is welcome

    Many of the other new rules provide standardisation on how to populate existing fields. This is certainly a step in the right direction.  Counterparties no longer need to quibble over who is the buyer and who is the seller of their contract.  RTS 2.0 provides 10 lengthy rules to determine what is eventually reported out as a single letter – ‘B’ or ‘S’.  Disputes on which party should generate the UTI can be put to rest and altercations on counterparty identification will end as UTI generation responsibilities are created and LEIs are mandated.

    Standardisation is also desired for the ‘classification and precise identification of derivatives’. This is of course more easily said than done in a world where the industry always moves faster than regulation. Spreadbets and swaptions have become newly added contract types as they rise in popularity but ESMA has admitted that not every derivative can be put into a box by allowing the use of ‘other’ contract types.  Does this make the most complicated contracts the easiest to report?

    We also see clarifications and extensions to the allowed values for action type, which was a field that was introduced as part of the Level 2 validations.  ‘C’ is now confirmed to mean an early termination of a contract rather than a more general cancellation. ‘P’ has been introduced to identify the position component of the contract.  The need to report a transaction as ‘new’ followed by ‘compressed’ is replaced by this which should put a smile on some people’s faces as it means substantially less data to submit.  Some things never change though and action type ‘E’ should still be regarded as the kiss of death in terms of EMIR reporting.  Once action type ‘E’ has been reported by either counterparty, you can say goodbye to that UTI. Not even the new action type of ‘R’ for correction will be able to allow the re-reporting of that UTI.

    New fields?

    Lastly, no new legislation would be complete without the introduction of some completely new required fields.  ESMA will require a much more comprehensive view on what collateral details need to be reported. In addition, the party receiving the collateral will also need to report as well as the party posting.  The ‘level’ field has also been introduced so that submissions on a position level can be separated from a trade level.  However, definitions on exactly what is the difference between trade and position level are more difficult to come across.  One notable difference is that positions can have 0 notional whereas trades cannot.

    How we can help

    With such a focus on MiFIR there is a risk that firms may underestimate the material changes introduced by RTS 2.0.  Take the time to check whether you are on track to deliver on the required changes now and contact us if you would like help to understand the new obligations and/or get your testing and controls in place.

  • MiFID II guidelines update uneventful

    MiFID II guidelines update uneventful

    There is very little of note in ESMA’s update to its MiFID II guidelines on transaction reporting announced on Tuesday 8 August.  Most of the changes are to reflect the current references for regulations and a few corrections of CFI codes used in the examples. 

    Of note are the following:

    • Execution within the firm field

    Where an investment firm is instructed on where to execute a trade, the client is instructing the execution.  The original text stated you populated the “Execution within the firm field” with “Client”.  This has now been changed to “NORE” which we think means “No reference”. 

    (See 5.12: Block 5: Execution within the firm field)

    • Reporting as DEA provider

    A more significant update, is in respect of DEA trading where you are the DEA provider.  Previously, the guidelines indicated that the execution within the firm field should be populated with an Algo identifier for the order management system that routed the order to the trading venue.  This has now been changed to “NORE”. 

    (See 5.25: Direct Electronic Access (DEA)

    • Read ESMA’s full notice
    • Download the new guidelines
    • Download a tracked changes version of the new guidelines.
  • Kaizen attends Queen’s Award royal reception

    Kaizen attends Queen’s Award royal reception

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

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

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

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

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

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

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

     

     

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

  • Your ASIC reporting risk just increased

    Your ASIC reporting risk just increased

    The Australian Securities and Investment Commission (ASIC) has issued its first penalty notice for alleged breaches of the derivative reporting rules, which require counterparties to report derivative transaction and position information to derivative trade repositories. 

    The notice was issued to Australian bank Westpac together with a fine for AU$127, 250 (about £75,000) for incorrect transaction reporting. The bank failed to ‘report information about 112,556 reportable transactions,’ between October 2013 to 30 April 2015.

    The example demonstrates the importance of having testing and controls in place to identify data quality issues quickly, as we outlined on our recent webinar.

    Flaw in system caused reporting failure

    ASIC said a flaw in Westpac’s reporting system caused the failure, which the bank was made aware of in July 2014, however it wasn’t aware that the flaw was causing the transactions not to be reported. 

    Westpac decided not to further investigate the flaw and put off the investigation to a later date as it thought only a small number of transactions would be affected. 

    The bank only discovered that it was a ‘material number’ of transactions in March 2015.  It reported the unreported transactions to DTCC in January 2016, but they were reported ‘with the counterparty buyer/seller information inadvertently reversed’.

    Firms must have testing in place to identify issues

    This example demonstrates once again how important it is for financial firms to understand their transaction reporting obligations and – just as crucially – to have testing in place to identify issues quickly. 

    Not only that, but when seeking to address an issue through replays, appropriate testing is needed to ensure that the replays do not introduce new errors as is the case here.  Firms would do well to note the two main ‘banana skins’ that have contributed to the notice, notably Westpac’s failure to:

    • Have testing in place to identify at an early stage any reporting quality issues (both accuracy and completeness testing), and
    • Implement assurance on the replays they were submitting.

    These failures left them exposed to regulatory censure which means not only a fine but also reputational damage, both of which could easily have been avoided with the right controls in place.

    Reporting risk levels have increased

    As a first penalty notice under the derivatives reporting regime, the scale of the fine and the quantum per erroneous trade report should be noted as this sets the level of reporting risk that firms are facing from a fining perspective: around AU$1 per incorrect or missing report. 

    If you consider that reporting volumes are significantly higher for most firms, reporting risk levels just increased.

    No matter what the regulation, Kaizen can help protect you from regulatory fines and penalties.  Please contact us for a chat about your regulatory reporting challenges.  

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

     

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

  • Significant changes proposed for EMIR reporting

    Significant changes proposed for EMIR reporting

    The European Commission has published its legislative proposals to amend European Market Infrastructure Regulation (EMIR).

    If implemented, they will result in significant changes to the current reporting obligations.

    Here is a quick rundown of the key changes being proposed:

    • Good news if you have not reported your historic trades – they are no longer needed
    • ETD reporting is going single sided, with the central counterparties (CCPs) picking up the burden.  The question remains for non-EU CCPs though.
    • Similarly, small non-financial counterparties (NFCs) will be able to rely upon financial counterparties (FCs) to take up the reporting burden.
    • Finally, trade repositories are going to be asked to ensure the quality of the data.

    The proposals follow on from a public consultation on EMIR and the Call for Evidence on financial regulation.  They also form part of the 2016 Commission’s Regulatory Fitness and Performance programme (REFIT).

    Yesterday the Commission also said it intended to present further proposed changes to EMIR on derivatives clearing as its scale and importance grows.

    We’ll be writing a more in-depth analysis of the proposals in the coming weeks.

    More information can be found on the European Commission’s EMIR webpage.

  • ESMA updates EMIR Reporting Q&As for backloading requirement

    ESMA updates EMIR Reporting Q&As for backloading requirement

    ESMA published its latest EMIR Q&As earlier this week to bring it in line with the revised technical standards which come into effect on 1 November this year.  This guidance is supported by the publication of revised validations to be applied by the trade repositories (the so-called L3 validations). Kaizen’s validation service will be available for clients to test their compliance with the validations from 1 May.  We will deal with EMIR RTS re-write in a forthcoming blog that will explore the impact of the EMIR changes. 

    The updated Q&A also deals with the requirements for back-loading of historic trades which is what we address in this article.   

    Back-loading of EMIR reports

    The back-loading obligation applies to firms with trades that were open or entered into after 12 August 2012 (the date from which EMIR took effect) and the commencement of EMIR reporting on 12 February 2014.  This requirement also affects firms that became subject to EMIR after the reporting obligation came into effect due to a relocation or re-categorisation of their business.  Any trades subject to the back-loading requirement must be submitted before the end of 12 February 2019. 

    The back-loading trades can be submitted in their end state and for exchange traded derivatives the concluding position for those cleared contracts.  Where these trades or positions are concluded or terminated after 11 August 2014 (the date when collateral and valuation reporting came into effect), the valuation and collateral fields must also be populated.  

    Reporting firms have been concerned about how to manage the exchange of the Trade ID (UTI) for historic trades.  Such a process would be extremely difficult however ESMA has clarified that where a trade is no longer live at the point of back-loading, the Trade ID or UTI will not have to be exchanged with the counterparty to the trade.

    ESMA has also made clear that following a corporate restructuring, the LEI of the corporate entity that is assuming the obligations for the demised entity’s derivative contracts, must be reported.  If the contracts are not being transferred, the contracts with the liquidated entity would be effectively terminated and should be reported as such.  This makes sense as it will ensure that the risk associated with those contracts is reflected against the entity that holds the risk. 

    A good outcome for firms?

    This is likely the best outcome that could be reached between ESMA and firms in that it allows the EMIR reporting requirement to be met without placing undue burden on reporting firms.  Still, it comes at a time when firms are more than busy with preparations for MiFID II with SFTR closely on its heels.  These changes won’t be the last either, with ongoing guidance via the Q&A process expected for MiFID II reporting both before and after 3 Jan 2018. 

    Dealing with constant change to reporting

    It is clear that firms need to develop speedy and effective processes to implement reporting changes but more than that –  the costs need to be brought under control.  Whilst your reporting solution will be the first area that needs to be addressed, the burden of testing any changes is not insignificant in terms of time, resources and overall cost.  Our testing approach provides early access to validation testing for our clients with full accuracy and completeness testing applied once the reporting solution is completed ahead of go-live.  This testing approach can be used to augment or replace your internal user acceptance testing.  It saves on costs and provides full visibility of your reporting quality, allowing corrections to code or static data to be made before revised reporting requirements take effect.

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

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

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

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

    The other crocodiles circling the canoe

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

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

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

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

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

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

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

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

    Your MiFID II to do list

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

    1. Reporting Solution – Build or Buy?

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

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

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

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

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

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

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

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

    3. Establish what activity requires reporting

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

    4. No LEI – No Trade

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

    5. Short-sell calculation

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

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

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

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

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

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

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

    The reporting “Labyrinth” – new obligations

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

    “Ch-ch-ch-ch changes”

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

    “Ashes to Ashes” for MiFID I transaction reporting

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

    Data Quality? Everything is not “Hunky Dory”

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

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

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

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

    Seasons greetings from us all at Kaizen.

  • 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 first with new Senior Managers and Certification Regime (SMCR) form

    FCA first with new Senior Managers and Certification Regime (SMCR) form

    The FCA has, for the first time, published a notification form* for firms to use when notifying the Transaction Monitoring Unit (TMU) of transaction reporting issues. This may help FCA processes however the form is interesting in that it requires quite a lot of information at the point of notification.

    Not only does the form ask for details on the length and scale of the issue and how it was identified, it asks:

    • What weaknesses there are in the reporting systems and controls of the firm
    • What plans are in place to audit or review transaction reporting and the scope of these reviews
    • But most notably, ‘Who within the firm has oversight responsibility for transaction reporting’.

    Additional responsibilities under SMCR

    Under the recently introduced Senior Managers and Certification Regime (SMCR), an individual within a firm must have overall responsibility for reporting. This is therefore a timely reminder for firms to consider how clear their allocation of responsibilities is, and their ongoing supervision within their firms.

    More broadly, firms should consider if they have an issue management and escalation process in place. They may also want to consider whether that process will deliver all the information the FCA is requesting and to look at their reporting assurance process and whether independent testing may be warranted.

    Read our earlier blog which outlines transaction reporting under the Senior Managers and Certification Regime.

    *The link to the form will download.

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

  • Will Brexit lead to a TRexit?

    Will Brexit lead to a TRexit?

    I spent some time last weekend catching up on the arguments for and against a Brexit. It got me thinking about the implications for reporting for firms in the UK. Now that the UK has voted to leave, will it have a major impact reporting-wise? Will obligations significantly reduce? I’ve come to the conclusion that in the main, I think Brexit will have very little impact on regulatory reporting. Here’s why:

    A transparent market is the ultimate aim

    Having seen the regulatory process and the development of transaction reporting legislation from inside the (then) FSA, my thinking is this: the UK needs clean markets to attract capital. To that end, the FCA has been at the forefront in establishing the transaction reporting regime in Europe as well as its shape under MiFID II. Clean capital markets will be even more important to the UK under a Brexit scenario so I fully expect that the UK would maintain a near identical transaction reporting regime. This could even include negotiating the ongoing exchange of transaction reports with our European neighbours under the existing MiFID model assuming that MiFID II is not adopted in full as a member of the EEA.

    Passporting

    Where an impact is more likely is for firms passporting into Europe today and they will be anxious about the future of their licence. Dependent on the outcome of negotiations on transaction reporting exchange, passported firms may have to report to their local competent authority (as today under MiFID I) and may lose the benefits of centralised reporting set out under MiFID II.

    Similarly, incoming branches to the UK may end up with a double reporting obligation to the UK and to their home competent authority. This would be more of a challenge were reporting obligations to differ between the UK and Europe but if they remain harmonised it reduces to a routing rather than a reporting problem. These risks I feel, will be addressed with a practical solution. After all, transaction reporting exchange is in place to provide that holistic view of activity on our markets. Without an agreed exchange, the FCA is likely to require market operators to report for members who do not have a UK transaction reporting obligation and similarly from the EU’s perspective.

    What about EMIR?

    For EMIR it is a similar story. EMIR needs to be global, not just European, if the data is to be useful for identifying emergent risks to the financial system: its primary aim. ESMA is currently working with Trade Repositories to standardise how information is made available to the array of regulators that have access rights to this information. Creating a UK specific regime, however well designed, would be an unwelcome complication for firms and Trade Repositories.

    Dual-sided vs single-sided

    Recent EMIR discussions have been around dual-sided vs single-sided reporting. My view is very pro dual-sided between financial counterparties as this goes a long way to promoting reporting quality. That said, for those non-financial counterparties delegating reporting to their broker, there is very little benefit for reporting quality of dual-sided reporting so this could easily be dropped. Similarly, many of the larger firms have created centralised reporting solutions and would not welcome divergence from the EU requirements, creating yet another distinct reporting obligation.

    So all in all, due to the added complications, and the UK having been a chief instigator in tougher reporting measures, I expect that the reporting world will continue very much in the same vein despite the UK voting to leave the EU.

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

  • Collateral transfers are to be explicitly excluded from MiFID II transaction reporting

    Collateral transfers are to be explicitly excluded from MiFID II transaction reporting

    ESMA has published a final report on RTS 22 which seeks to amend the original drafting to explicitly exclude collateral transfers.

    The potential introduction of collateral transfers as reportable transactions was of significant concern to the industry so this development will be warmly welcomed.

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

  • Senior Managers Regime and Transaction Reporting: ‘Not about trying to get heads on sticks’

    Senior Managers Regime and Transaction Reporting: ‘Not about trying to get heads on sticks’

    Tracey McDermott, the acting head of the FCA, has said the Senior Managers Regime (SMR) is not about trying to get heads on sticks. Rather, the new regime’s objective is to make sure banks are run better by senior managers who understand their responsibilities more clearly.  So what are the key components of the regime and how will it affect firms’ delivery of their increasingly complex trade and transaction reporting obligations?

    Background and purpose

    The first wave of the SMR came into effect on 7 March with managers at banks, building societies and insurance companies in the firing line.  In 2018 the regime is expected to extend to cover buy-side firms.

    The SMR is a product of the recommendations from the Parliamentary Commission on Banking Standards. It advised, ‘A Senior Persons Regime should provide far greater precision about individual responsibilities’ and recommended a ‘licensing regime as the basis for upholding individuals’ standards of behaviour.’  Through the new regime, senior managers can be held accountable for misconduct that falls within their area of responsibility.

    The FCA will approve approximately 7,000 senior managers who will be in charge of defined areas within their origination and will have their responsibilities outlined.  They will be held to account for anything that goes wrong in their area. In turn the senior managers are required to certify that up to 30,000 of those working in materially important roles within their origination are suitable and honest to hold their roles. These roles are re-certified each year.

    Rules, functions and responsibilities

    Under the regime, there are clear and prescribed rules, functions and responsibilities. All four of the SMR rules are relevant to firms’ reporting responsibilities. The appropriate SM must ensure that:

    a) The business is controlled effectively
    b) They comply with the relevant requirements and standards of the regulatory systems
    c) Any delegation of responsibilities is to an appropriate person and delegation is overseen effectively
    And:
    d) Disclose appropriately any information of which the FCA or Prudential Regulation Authority (PRA) would reasonably expect notice. There are 22 Senior Management Functions (SMF) and at most firms it is likely that trade and transaction reporting will roll up to SMF 6: Head of Key Business Area.

    Impact upon trade and transaction reporting

    The SMR brings into sharp focus the question of accountability within a firm. A senior manager will now be personally responsible if there are material breaches in a firm’s reporting and there is evidence that a senior manager has not fulfilled their duties in relation to controls, compliance with regulatory standards, delegation or regulatory disclosure. The SMR causes a ripple effect where the senior manager is looking for confidence in compliance in reporting from his delegates. It is therefore of paramount importance that an appropriate control framework is in place with an effective governance structure underpinned by comprehensive testing. Being able to evidence the quality of a firm’s reporting through testing is likely to become a common demand from those who have responsibility of reporting under SMR.

    If the history of MiFID transaction reporting since 2007 is used as a reference point then those senior managers who have responsibility for reporting are carrying significant risk. Since 2007, for tier 1 banks downwards, multi-million pound fines have been issued by the then FSA now FCA to firms who have failed to implement appropriate controls and testing. It is worth noting this is for a reporting obligation which is relatively mature and also simple with only 20-odd fields.  EMIR and MiFIR reporting is significantly more complex.  Under MiFIR there is a regulatory requirement to reconcile and test – tasks that firms have traditionally struggled with.  To perform effective and comprehensive testing requires significant knowledge of the regulations and data combined with appropriate technology. Previously firms have not been able to bring these aspects together.

    Kaizen’s accuracy testing and advanced regulatory reconciliations services enable high quality, comprehensive testing and reconciliations that will provide Senior Managers with confidence that they can demonstrate effective controls and are complying with their regulatory obligations.  From a cost perspective it makes no sense for each firm to invest significantly in trying to develop their own testing. Instead they can subscribe to Kaizen’s managed testing service to keep their senior managers’ heads off any future sticks.

  • 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.
  • Why populating the clearing obligation field won’t be so easy

    Why populating the clearing obligation field won’t be so easy

    As we approach the deadline for mandatory clearing ESMA has published a further update to its EMIR Q&As providing guidance on the application of the clearing obligation for swaps resulting from exercise of swaptions.  With mandatory clearing only months away for OTC interest rate derivatives denominated in the G4 currencies (EUR, GBP, JPY and USD) we take a quick look at how mandatory clearing will impact EMIR reporting.

    From 21 June 2016 mandatory clearing will firstly affect firms who are individual or general clearing members of an authorised or recognised central counterparty (CCP).  Six months later, category 2 firms will be caught and category 3 firms a further six months after that. This means that firms will need to assess what category they will fall within, but also what category their counterparties will fall within as that will determine if and when mandatory clearing applies.  See our table at the end of this blog.

    Firms that aren’t in category 1 will need to do some data crunching to calculate whether their group is above or below the €8bn clearing threshold and they should be notifying their counterparties either way, something Kaizen can assist with.  Each of the three categories will need to be wary of the frontloading obligation which captures trades entered into or novated on or after the frontloading date dependent on the instrument and the remaining maturity on the trade.  So they will need to consider pricing based on the potential for eventual clearing of these trades if they remain open once the clearing obligation kicks in.

    Regarding the ESMA Q&A, it makes clear that for in scope derivative instruments and counterparties:

    1. All novations of any type which result in a new counterparty will be subject to the clearing obligation.
    2. For swaptions entered into prior to the frontloading window the resultant swaps will not be subject to the clearing obligation irrespective of when the swaption is exercised.
    3. For swaptions entered into after the start of the frontloading period:
    4. Mandatory clearing applies where the swaption is exercised during the frontloading period and the resultant swap is above the minimum remaining maturity per the RTS.
    5. And for any swaptions exercised after the clearing obligation takes effect the resultant swap will be subject to the clearing obligation.

    Reporting implications

    To report correctly, firms will need to complete the “clearing obligation” flag with the appropriate value.  This will require firms to assess whether each trade is subject to the mandatory clearing obligation irrespective of whether the trade is already cleared or not.  That will mean assessing all trades entered into after the frontloading period begins.  Currently, this field should be populated with an “N” but for Category 1 firms this may change post 21 June 2016.  Trades which will be subject to mandatory clearing entered into prior to this date should be flagged as “N” in the clearing obligation field until the clearing obligation takes effect.  The timing of this will be based on the firm’s category and that of its counterparty.

     

     

     

    Notes:
    NFC+:   Non-financial Counterparty above the clearing threshold, as referred to in Article 10 of EMIR
    AIF:    Alternative Investment Funds

  • MiFID II fee proposals – how will they impact you?

    MiFID II fee proposals – how will they impact you?

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

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

    More transactions, higher fees

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

    Data Reporting Service Providers

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

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

    FCA application fees

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

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

    FCA periodic fees

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

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

    FCA DRSP fees

    [supsystic-tables id=’2′]

    FCA data submitter on-boarding fees.

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

    [supsystic-tables id=’3′]

    FCA ongoing transactional fees

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

    *subject to change

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

  • ESMA’s latest EMIR Q&A provides clarity on notional fields

    ESMA’s latest EMIR Q&A provides clarity on notional fields

    15:57:02ESMA has issued a few new pieces of guidance via its latest EMIR Q&A update.

    The key point for EMIR reporting is the guidance on populating the notional field for futures and options at position level (transaction reporting, question 41).

    1. Notional for futures:  quantity x price multiplier x settlement price
    2. Notional for options: quantity x price multiplier x strike price

    That means that for a future on ICE on the FTSE 100 index the notional will be the quantity (number of contracts traded) x 10 (£10 per index point multiplier) x forward price (in index points).  For a position report this would be the average forward price weighted by quantity.

    The other updates are:

    • Additional default management guidance for CCPs under CCP question 3 (d) and
    • Access to data by the competent authorities under transaction reporting question 37 (a).

    These updates are helpful for firms in that they provide clarity on populating the notional field however questions remain about whether the notional for a buy would be different from a sell for trades.  It is clear that if you have 100 buys of FTSE 100 futures and then you do 50 sells, the notional on your position report would be reduced.  But is ESMA expecting the notional for the trades to be negative for sells?  It doesn’t appear to be the case from the Q&A.  More clarity from worked examples as per the recent consultation on MiFID II transaction reporting would be welcomed.

  • ESMA Data Portal Changes

    ESMA Data Portal Changes

    Firms subject to MiFID and other regulatory reporting obligations should be aware that ESMA is migrating its current data register to a new portal.

    These changes will be of particular interest and relevance to compliance and operations teams.

    The existing portal will be removed from 1 April.  The migration impacts the following published data sets which will have a direct impact on validation to ensure compliance with regulatory reporting:

    • Published list of shares admitted to trading on regulated markets
    • List of exempted shares
    • Register of systematic internalisers
    • List of authorised regulated markets
    • List of authorised multilateral trading facilities (MTFs)
    • Central counterparties

    To enable a smooth transition, ESMA is making the data register available on both portals for the rest of February and until the end of March.  As of 1 April 2016 the old portal will be shut down and not accessible.

    Firms that have established automated access to these lists should refer to the updated web service procedure ESMA has published.

    Developers responsible for the automated processes adopted in respect of the datasets should review the information detailed on ESMA’s website.

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

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

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

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

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

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

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

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

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

  • MiFID II implementation roundtable

    MiFID II implementation roundtable

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

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

  • Good and bad news for transaction reporting under RTS 22

    Good and bad news for transaction reporting under RTS 22

    Fewer reportable fields doesn’t necessarily mean less work.  In this blog, we look at the key changes in RTS 22 from the original  MIFID II consultation proposals and provide some conclusions on the overall impact.

    We carried out a detailed analysis of the reporting fields in the revised draft regulatory technical standards (RTS) released by ESMA.  RTS 22 is the section which sets out the transaction reporting obligations and reportable fields.  The analysis takes the fields in the original consultation paper and compares them to the equivalent versions of the fields in the final report.  In many cases this is a one to one mapping after accounting for some changes in the terminology used.  If you want to take a look or to use the table of fields for your own analysis we have published this as an excel document.

    So what did we find? Taken at face value the number of fields have been reduced from 81 to 65 fields.  A reduction of 16 fields, which is seemingly good news.  However this apparent reduction masks an increase in the information that reporting firms will have to capture and submit – not such good news.

    New fields: Our analysis shows there are 10 new fields which have been added.  The overall reduction in the number of fields results from 13 control fields (code type e.g. LEI vs national identifier) being removed.  We expect that seven of these will be included within the ISO 20022 reporting schema and therefore firms will have to continue to report them.  The remainder are no longer necessary for fields where only one code type is permitted for reporting which again will be enforced through the reporting schema.

    Fully removed fields: Nine fields in total were removed.  “Postcode” and “country of residence” fields have been removed for several identifier fields as has the “consideration” field and the “option exercise” field  is no longer a reportable activity.

    Compressed into another field: Three fields have been compressed into other existing fields, so in essence the information is still to be reported.  The three counterpart fields remain.

    Unchanged: A total of 52 fields remain unchanged in terms of field name.  There are some wording changes embedded which will need further analysis as these will have implications for reporting.

    You can also find our full analysis of the tables below which have the original data fields and revised data fields side by side so you can conduct your own analysis.

    [supsystic-tables id=’6′]

    The 10 new reporting fields:

    Providing these additional fields will in some cases be easy, such as field 5 stating whether you are a MiFID firm or not, whilst others will be very challenging, such as field 40 “complex trade ID” and “instrument full name”.  This latter field is likely to be supported by further guidance given it will be used to identify all derivatives which are not allocated an ISIN code.

    [supsystic-tables id=’5′]

  • Just a second…?

    Just a second…?

    MiFID II introduces the requirement to synchronise the business clocks of trading firms and their customers so that timestamps recorded are standardised across the industry. The idea is that regulators will be able to monitor for market abuse more accurately. Trading systems will need to synchronise themselves to a common source of time. But how will they do this? And what are the implications?

    On the back of the FCA’s MiFID II conference this week we were with the National Physical Laboratory (NPL) to find out. Their workshop, “UTC traceability for the global financial sector, realisation of a unified common clock” attempted to answer some of these questions. Taking the front seat was MiFID II’s RTS 25, which outlines the draft regulatory technical standards on clock synchronisation. The direct impact of this piece of regulation was apparent from the range of professionals from all aspects of the industry including financial firms, exchanges, consultants and scientific organisations.  Most notable was the presence of ESMA and the Bureau International des Poids et Mesures (BIPM) as both have a heavy hand to play in RTS 25. We suggest firms take a look at Table 2 in the Annex of RTS 25 which sets out the level of granularity applicable to their trading activities. It is important that firms are clear on what is expected of them and should be in advanced discussions around the technology to be adopted to meet the new regulatory obligations.

    Here are the key points we took away from the conference:

    1. The industry was concerned about deploying GPS as a means to synchronising their business clocks. It was felt that although it meets the regulators’ authorisation of “satellite systems” as a credited tool, it does not provide traceability back to UTC.  This was further supported by BIPM who claimed that due to the irregular leap second lag incurred through GPS signals, the only credible solution was a direct feed from a National Measurement Institute (NMI). ESMA was clear that both options remain and stood firm, stating that they must be realistic in what they ask from firms and not show any bias to any provider.
    2. The industry feels this needs to be part of the Level 3 discussions but it seems very unlikely that GPSs will be scrapped. We advise all firms to gear up based on the Level 2 RTS 25.
    3. The industry also showed concern around implementing the required technology and sought r advice from the regulator. However, ESMA’s view was very clear in stating it is up to the firm to implement what is required.
    4. ESMA highlighted the importance of firms reviewing their transparency systems on an ongoing basis once deployed. The type of review required is not clarified within the RTS, however we would recommend both internal and third party checks to ensure obligations are met.
    5. FIX is planning to update all versions of its protocol (back to FIX 4.2) to capture the accuracy of seconds in timestamps to 6, 9 or 12 decimal places.
    6. BATS Chi-X Europe is considering providing NPL time source feeds to its clients via a PTP feed if there is considerable demand.

    All in all, the industry is aware of the challenge in implementing this step and the effects it will have on their infrastructures. However, having the same “watch” is very much welcomed by all concerned, agreeing it will lead to better data publication and reporting, thus a more transparent industry as a whole.

    What do you think?  We would welcome feedback or comments about the issues raised in this blog and more broadly, about the MiFID II draft technical standards.

    We’ll be releasing further blogs around the finer details of MiFID II so stay tuned!

    In addition to our testing services, we are offering training courses for firms to help them prepare for the reporting elements of MiFID II. Please contact us to find out more. 

    Read our earlier blog on our reaction to the release of the draft RTSs.

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

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

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

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

    Here are our key take aways from the conference:

    Regulatory Process

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

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

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

    Transparency

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

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

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

    Commodities

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

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

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

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

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

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

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

     

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

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

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

    This means either:

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

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

    Why is this being introduced now?

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

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

    Major headache

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

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

    ESMA writes the control section of your transaction reporting BRD…

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

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

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

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

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

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

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

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

  • EMIR level 2 validations – are you ready?

    EMIR level 2 validations – are you ready?

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

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

    Some background

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

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

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

    Benefits of strict validation

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

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

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

    So what should firms be doing to prepare?

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

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

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

  • ESMA reveals latest on MiFID II progress

    ESMA reveals latest on MiFID II progress

    On 7th July, Clifford Chance hosted a workshop on MiFID II progress and implementation at which ESMA’s Head of Markets Division Rodrigo Buenaventura provided an update.

    Mr Buenaventura outlined the continuing challenges faced by ESMA. He confirmed that the eagerly awaited final Technical and Regulatory Standards will now be published in September. With regards to timeline and what now appears to be building rumours around delay, Mr Buenaventura confirmed that there is no discussion at this time in this regard and ESMA is moving towards the 3rd Jan 2017 date. Despite recognising this would be challenging, they currently consider this as achievable. Furthermore, he advised that there is no current provision for phasing in particular aspects of the legislation, although acknowledged that over time this could be considered but it was too early for such consideration.

    He highlighted the key issues that require further consideration and these are clearly still a concern to market participants. These include:

    • non-equity transparency
    • commodity reporting
    • liquidity classification

    ESMA is considering the most appropriate approach towards liquidity calculation and whether this should be undertaken against individual securities or whether to adopt a group approach, for example a dependency upon issuance size. Their preference is currently unclear and will require further analysis.

    The liquidity calculation determines what instruments must be trade reported for market transparency. ESMA believes that the number of instruments that will be subject to trade reporting obligations will increase twenty fold.

    ESMA highlighted they will have a different role under MiFID II as consolidator of various important market data for transparency purposes in order to calculate liquidity and establish reporting obligations. They consider a single engine for this is beneficial to the financial community, avoiding reporting obligations to multiple CAs.

    ESMA also recognises there are significant challenges in respect of the establishment of position limits and that the European environment is completely different to the US. In the US some 60 limits exist whereas in Europe this runs into the thousands.

    Particularly interesting to those in the regulatory reporting arena was the fact ESMA confirmed it has significant concerns around the quality of the data reported under both the MiFID and EMIR regimes. Mr Buenaventura stated they are determined to ensure improvements in the quality of reporting and are working with the various colleges in an effort to address this.  ESMA recognises the importance of improving the quality of derivative reporting ahead of MiFID II implementation.

    ESMA advised they have undertaken significant analysis of market data, having reviewed more than two terabytes of EMIR data on top of significant bond market data to consider the appropriate way forward. ESMA recognised they will need to work with market providers in an effort to source the appropriate data for liquidity calculation and establishing appropriate position limits.

    Overall, ESMA stated they consider the implementing legislation should be an improvement for market participants given the harmonisation that regulation creates as opposed to a directive. Supervision convergence should ensure consistent approaches around requirements across the EU.

    With regards to the approach around implementation, questions were raised around adopting a similar approach to the EBA and the implementation of CRD given the issues experienced with EMIR Q&A.  ESMA will consider this and acknowledged the level of queries will be considerably higher and possibly ten times the 2000 or so queries that were raised under EMIR.

    Overall, Mr Buenaventura highlighted the importance placed on reporting and the significant changes that are taking place.  Furthermore, he stated that the focus on the problems with current standards provides a clear indication that regulators are serious about ensuring reporting quality is improved in order to implement the new legislation effectively. ESMA clearly recognise that the poor quality of data today is detrimental to the objectives the reporting obligation are attempting to achieve and so firms should take note of the obligation to have a control framework in place at MiFID II go-live.

  • ESMA publishes 13th version of its EMIR Q&As

    ESMA publishes 13th version of its EMIR Q&As

    Is the latest version of the EMIR Q&As a major change or a minor amendment? Well, the Q&As include just two revisions to TR questions but as they deal with validations, the changes can well be considered significant.

    For most reporting entities the EMIR validations will only help provide more visibility over reporting quality. However, it may mean that data problems will prevent firms from reporting at all and so a review of the impact of the validations should be considered before these are applied by the Trade Repositories at the end of October 2015. Not only that, the NCAs are using rejection rates as a proxy for data quality and will be using these to decide which reporting firms to visit.

    The other change that has been slipped into the Q&As via the validations is the approach around “lapsed” LEI codes. These are codes that have passed a 2 year period since issue but have not been renewed.

    Under Q&A TR Answer 10(b), ESMA stated that duly maintained LEI codes must be used however, lapsed codes are to be accepted by TRs when used to identify a counterparty. This is clearly a choice that ESMA is making around the LEI. Such codes are maintained where the owner has reconfirmed the data associated with the LEI record at the LOU, a process that happens every 2 years from issue. As these details change very infrequently, there is little risk in using lapsed LEI codes to identify a counterparty to a trade. Even where the details are incorrect, it is highly probable that the LEI will identify the correct party given that such codes are never reused.

  • ESMA publishes 12th version of its EMIR Q&As

    ESMA publishes 12th version of its EMIR Q&As

    ESMA has published its 12th version of the EMIR Q&As on 31 March 2015. This latest publication principally deals with the application of the clearing exemption.

    This will only impact reporting in respect of the following:

    • Sovereign wealth funds will fall within EMIR as Alternative Investment Funds and will therefore have a reporting obligation.
    • Where an obligation to clear arises and therefore clearing details must be reported.
    • Where an exemption from the clearing obligation is not granted.
    • Where a trade is novated for clearing.

    Further details of each update can be found below:

    OTC Q6(g) Intragroup exemption from the clearing obligation:

    Where counterparties apply to two separate jurisdictions, both Competent Authorities must approve the exemption otherwise it should not be relied upon. The counterparties should wait for responses from both CAs before placing reliance on the exemption.

    OTC Q13(d) Sovereign wealth funds established in third countries:

    “Sovereign wealth fund will qualify as financial counterparty under EMIR where it meets the definition of an AIF and it would be subject to Directive 2011/61/EU (AIFMD) if it was established in the Union. However, where a sovereign wealth fund does not meet the definition of an AIF and is out of scope of the AIFMD, such a sovereign wealth fund shall be treated as non-financial counterparty in accordance with Article 10 of EMIR.”

    OTC Q13(d) Pension scheme arrangements:

    Where pension scheme arrangements, as defined in Article 2 (10) EMIR, are granted an exemption under Article 89 and outsources management of its assets to a third party, the exemption will still apply. The manager should meet the following criteria in managing the exempt assets:

    1. Does not comingle exempt and non-exempt assets.
    2. The derivative contract clearly identifies that it is concluded for an exempt pension scheme under Article 2 (10) and Article 89 (1 & 2) (as appropriate).
    3. Keep the assets and records in a way to allow regulators to check that the derivative contract reduces investment risks directly related to the financial solvency of the pension scheme.

    OTC 17(b) Frontloading period:

    Contracts entered into during the clearing frontloading period do not need to be cleared, where the intragroup exemption is granted before the clearing obligation takes effect.

    OTC Q20 Clearing obligation regarding novations:

    All types of trade novations are covered by the clearing obligation. The example ESMA provides is where a counterparty (being a CCP or another counterparty) steps into the trade and become a new counterparty to the trade. They will therefore be subject to the clearing obligation.

    OTC Q21 Guarantees in respect of third country contracts:

    The responsibility under Art 2.1 of RTS for guarantees in respect of Third Country contracts will lie with the EU guaranteeing party. As such the EU entity will need to make the arrangements to have the required information to assess whether the guarantee should be deemed to have a significant and material effect in the EU.

    OTC Q22 Guarantees in respect of third country contracts:

    Where multiple guarantees are being provided they should be considered in together where the guarantees are provided to the same entity, as the guarantor EU entity will be subject to a single entity’s risk.

    OTC Q23 (a) Guarantees in respect of third country contracts:

    Article 2 RTS on Third Country contracts does not apply to contracts entered into before the RTS comes into force.

    OTC Q23 (b) Guarantees in respect of third country contracts:

    Article 2 RTS on Third Country contracts does apply to contracts entered into after the RTS comes into force but guarantees were given by an EU entity prior to the effective date of the RTS.

    CCP Q6 (f) Under Article 14 of EMIR – Authorisation of a CCP:

    “CCPs cannot be authorised to offer services preventing the interposition of the CCP between clearing members, i.e. preventing clearing members to clear contracts with other clearing members.”

    CCP Q8 (n) Article 39 of EMIR – Segregation and portability:

    Repayment of excess margin to clients under auto repay arrangements.

    According to article 39(6) of EMIR, “When a client opts for individual segregation any margin in excess of the client’s requirement shall be posted to the CCP. As such, any excess collateral allocated to an individually segregated account must either be maintained at the CCP in accordance with article 39(6) or returned to the client.” ESMA go on to say that CCPs should offer clearing members the possibility of switching off auto pay as long as the CCP is permitted to hold the holding excess margin.

  • A review of the key TRUP 3.1 changes for MiFID

    A review of the key TRUP 3.1 changes for MiFID

    The FCA published revised transaction reporting guidance in TRUP 3.1 on 6th February 2015. The key changes come into effect six months after publication on 6 August 2015 whilst other changes which are considered to be for clarification purposes have immediate effect.

    The changes impact the following areas:

    • Trading capacity field
    • Reporting the unit price for bonds
    • Venue field clarifications
    • Strategy trades
    • Self-hitting trades
    • Firms’ systems and controls over transaction reporting activities

    Capturing changes in the firm’s and clients’ positions

    TRUP 3.1 states that “Firms must ensure that the trading capacity field is populated in transaction reports so as to accurately reflect the changes in positions of the firm and its client(s) at the time of the transaction(s).”

    FCA are looking to capture under its rules and guidance what is reportable in terms of changes in position. There are some scenarios where firms’ current use of the trading capacity field results in a change in position of a client or a firm to not be reflected in the transaction reports. This requirement could be interpreted more broadly to require the reporting of all changes in client and firm positions and I don’t think that is the intention. This would introduce full lifecycle event reporting. Lifecycle events are post transaction events which results in changes to existing contracts such as increases in notional or a change of counterparty or beneficiary. Lifecycle event reporting is not being introduced in TRUP 3.1 rather MiFID II sets out the requirements in respect of lifecycle events. The current MiFID II consultation excludes derivative novations, assignments and compressions from reporting which would not enable these changes in position to be captured.

    Trading capacity changes

    Whilst on the surface the change appears straightforward, it masks a great deal of complexity. The cause is the fact that the legal agreements between a firm and its clients and counterparties determines how this field is to be populated.

    In general this can work quite well. Many firms operate in a principal capacity and populate accordingly. Where firms operate in both a principal and an agency capacity, the complexity begins. Where a firm provides a fill from its own book but is acting as agent for its client it is operating in both a principal and agency capacity. The new TRUP guidance requires that both capacities are to be reported. This is achieved by using the “internal” to denote transfers in and out of an internal account. It is expected that positions would always clear from the internal account. The same process will be applied to trades where the firm fills an agency order by trading in a principal capacity against a counterparty or on venue.

    This means firms will have to have reporting processes in place to capture booking scenarios where there is a transfer from a principal book to an agency book/client account. Recoding of systems to put this into effect is likely to be non-trivial exercise particularly where an actual internal account or washbook is not used.

    The TRUP includes brief examples which I would recommend are closely reviewed.

    These changes are to be implemented by 6th August 2015.

    Unit price for bonds and bond futures

    The price to be reported for Bonds has always been the clean percentage price where the percentage is based on the par value of the bond. There has however, been open questions around instruments that are bond like but are traded in a similar way to equities. This would include securitised instruments that pay a coupon. TRUP 3.1 clarifies that such instruments should be reported with the traded price. So if it is traded as based on a percentage of par, the percentage is reported whilst if it has a price in monetary terms that value should be reported (in the major currency).

    As trading conventions for bonds are not uniform, we are still left with the problem of converting prices from the market convention to a percentage. So problematic bond instruments such as French convertibles which are usually traded with a dirty price based on units and Belgian OLOs which are trading with prices agreed in the form of a yield, will now have to be reported in percentage terms. The Belgian OLOs are especially problematic as firms are required to report trading in these instruments to the Belgian FSMA with the price in a yield format which is contradictory to MiFID and FCA requirements.

    Reporting the venue

    Reporting the venue on which a trade is executed remains a problem field for firms and we see many instances where errors have been introduced when capturing the venue identifier. Whilst there are no new obligations emerging from the TRUP changes, the revised text goes some way to clarify how to populate this field however there are still further elements that firms need to consider.

    Sup 17 and TRUP 3.1 require the use of a MIC code when trading under the rules of a “trading venue”. MiFID I provides the applicable definition of trading venue able:

    “(8) ‘trading venue’ means a regulated market, MTF or systematic internaliser acting in its capacity as such, and, where appropriate, a system outside the Community with similar functions to a regulated market or MTF;”

    There are numerous venues within the EU which have been allocated a MIC code. By definition, as they are within the EU they cannot be considered to be a regulated market or MTF (Multilateral Trading Facility). Similarly, there are venues or platforms outside of the Community which have been allocated MIC codes, many of which cannot be considered to be of similar functions to a regulated market or MTF.

    As such it is not sufficient to establish that there is a valid MIC code for the platform upon which the trade was undertaken. An assessment needs to be made as to whether the platform has similar functions to that of a regulated market or MTF.

    MIC segment codes

    MIC codes are now split between an operator code and the segment code. The venue field should reflect the market identifier code (MIC code) of the market segment where the trade is agreed to be under the rules of the trading venue unless the trade is an OTC derivative trade. OTC derivatives are always reported as “XXXX” in the venue field.

    Happily, the FCA has introduced some latitude in those circumstances where the segment traded is unknown or uncertain whereupon the Market Operator MIC code can be reported. This scenario arises when trading on Xetra where exchange fill data does not identify the segment the instrument was traded on and therefore the operating MIC (XFRA) may be utilised.

    Strategy trades

    Strategy trades are trades where a derivative and its associated underlying are traded at the same time. For strategy trades executed on Aii markets, the underlying, which often has an ISIN identifier, cannot be reported using the Aii market’s MIC code as an Aii identifier is expected by the ARMs and FCA’s ZEN system. The guidance clarifies that in such instances “XOFF” should be reported in the venue field and the ISIN of the underlying in the instrument identifier field.

    Self-hitting trades

    Where a firm trades on exchange, particularly if they are trading in significant volumes, they may hit an order on the order-book which has been placed by another desk, algo or DMA client submitting orders for the same firm. The guidance clarifies that such trades are to be considered transactions and are therefore reportable irrespective of subsequent clearing activities which are likely to net out the two trades to zero. Where the trade is immediately cancelled prior to a trade report being published, then an execution is deemed not to have taken place and a transaction report is not required.

    Firms are expected to have implemented reporting in compliance with the above by 6th August 2015.

    Transaction reporting arrangements within firms

    As in previous versions of the TRUP there is guidance on the FCA’s expectations in respect of reporting firms’ controls over the accuracy, completeness and timeliness of their reporting. TRUP 3.1 is more explicit than previously and sets out expectations in respect of the training that those involved in transaction reporting are expected to have (including elements of the training content) and the expectation that firms will conduct front to back reconciliations between front office systems and the reported transactions.

    Whilst many firms will already have controls in place, a review of the controls and whether they satisfy all the areas outlined in the TRUP is recommended.

    Kaizen Reporting Services

    Kaizen offers a suite of services which meet all the requirements of the TRUP 3.1 including execution of front to back reconciliations, reconciliations to FCA data, report testing services as well as comprehensive training on the reporting obligations and reporting health checks.

    If you have concerns or questions about EMIR or Transaction Reporting then please contact us. We would be happy to provide an initial review of your transaction reports at no cost allowing you to try out our report testing service.

  • Obligation to use LEIs picks up pace

    Obligation to use LEIs picks up pace

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

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

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

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

  • NYSE LIFFE MIC changes following migration to ICE Futures Europe

    NYSE LIFFE MIC changes following migration to ICE Futures Europe

    The NYSE LIFFE Market Identifier Code (MIC code) is to change following their migration to ICE Futures Europe including guidance on BClear instruments.

    This change has a direct impact upon firms’ regulatory reporting obligations impacting both EMIR trade repository reporting and MIFID transaction reporting obligations. This note summarises the changes and what action firms should be taking.

    The ICE migration is complicated in that the exchange contracts are being migrated over 5 different dates with the final date of migration being 17th November 2014. Firms should note that fixed income instruments migrated over three different dates therefore the MIC for the respective contract needs to accurately reflect these changes. Further complexity is that close attention is also required in respect of the appropriate MIC being applied for example the MIC code is different for Equity Index Futures (IFLL) and Options (IFLO) contracts and this needs to be identified correctly in firms static data and subsequent reporting.

    What should firms be doing?

    Firms’ static data needs to be amended to reflect the correct MIC code at the time of the changeover for the impacted contracts. Post implementation quality assurance testing should be applied to ensure that EMIR and MiFID transaction reports reflects the MIC changeover and any timing errors are corrected.

    With various LIFFE contracts being migrated to new MIC codes in stages firms will need to take great care to ensure that they use the correct MIC code for the relevant contract at the right time. For quick reference table detailing the precise changes to the appropriate MIC and the respective dates this was applied please refer to the below table which contains the full details.

    LIFEE Contract Migration to ICE Futures Europe

    [supsystic-tables id=’7′]

    BClear

    Firms should also note, that going forward, trading previously undertaken utilising LIFFE BClear for wholesale market activity, will now be undertaken under ICE “block” trading rules. When reporting as per the above table, firms should consider the product sector and contract type and report the appropriate MIC ongoing from it’s respective migration date. Dependent upon the security, this trading activity will be subject to MiFID and/or EMIR reporting requirements. Firms are advised when reporting this activity that they are required to report the appropriate MIC in recognition of the particular security.

    See below for further clarification.

    • “Block” trade on an Equity Index Future the appropriate MIC is IFLL
    • “Block” trade on an Equity Index Option the appropriate MIC is IFLO
    • “BlocK” trade on White Sugar Futures and Options the appropriate MIC is IFLX

    Firms should refer to the “LIFFE to ICE Futures Europe Transition Notice” published September 2014 for further details of the migration impact.