Author: Fiona Wilde

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

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

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

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

     

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

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

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

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

     

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

     

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

     

  • 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.
  • 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.
  • 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. 
  • Vote for us in the Regtech Insight Awards Europe 2024

    Vote for us in the Regtech Insight Awards Europe 2024

    We’re honoured to have been nominated for an incredible nine awards at this years RegTech Insight Awards Europe 2024!

    We’re particularly thrilled that this year the nominations cover our broad spectrum of regtech products that we now offer including regulatory reporting assurance, shareholding disclosure monitoring and reporting, trade and e-comms surveillance and regulatory rules management. 

    All you need to do is follow the link below, fill in your details and select yes for question 9, and select Kaizen for categories 3,4,5,6,8,9 and 16, and Single Rulebook for categories 11 and 13. And press submit! 

    Vote here

    The RegTech Insight Awards Europe 2024 recognise solutions that have successfully improved firms’ ability to effectively respond to evolving and ever more complex regulatory requirements across the global financial services industry.

    A huge thank you in advance for your support and congratulations to all the other nominees. 

    Voting closes on Tuesday 26 March 2024.

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

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

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

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

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

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