Tag: FCA transaction reporting

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

    The important points for firms to note are:

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

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

    4. Change management remains a weak spot across the industry

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

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

    Firms should now consider the following:

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

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

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

    Technical ISINs

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

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

    FX Swaps Clarification

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

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

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

    5. Pairing and matching are now in the spotlight

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

    Key points:

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

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

    6. Looking ahead: expect more collaboration, not less

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

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

    Conclusion

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

    For firms, this means:

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

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

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

  • Key changes proposed by FCA on MiFIR Transaction Reporting

    Key changes proposed by FCA on MiFIR Transaction Reporting

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

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

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

    1. Fewer reporting fields, leaner data requirements

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

    2. Smaller instrument universe

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

    3. FX derivatives out, shorter back-reporting period

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

    4. Smarter reporting through conditional single-sided logic

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

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

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

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

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

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

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

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

    What action have we seen from the FCA so far?

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

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

    How can firms be sure they’re reporting accurately?

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

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

    Happy Anniversary MiFID II.