Tag: Market Watch

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

    The important points for firms to note are:

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

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

    4. Change management remains a weak spot across the industry

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

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

    Firms should now consider the following:

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

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

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

    Technical ISINs

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

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

    FX Swaps Clarification

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

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

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

    5. Pairing and matching are now in the spotlight

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

    Key points:

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

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

    6. Looking ahead: expect more collaboration, not less

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

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

    Conclusion

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

    For firms, this means:

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

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

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

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

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

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

    Market Watch 81: Transaction Reporting Vulnerabilities

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

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

    Market Watch 82: Elevated Expectations on Remediation

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

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

    Recent enforcement actions

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

    Key take aways for firms resulting from the final notices

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

    Conclusion

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

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

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

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

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

    FCA warns on further transaction reporting errors in Market Watch 62

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

    First, the basics…

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

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

    The more complex..

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

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

    To summarise…

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

    Our advice…

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

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

    Further reading: Market Watch 62

  • FCA publish Market Watch 59

    FCA publish Market Watch 59

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

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

    Valid but incorrect reports

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

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

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

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

    Instrument Reference Data

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

    Errors and omissions notifications forms

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

    How Kaizen can help

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