Tag: EMIR trade reporting

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

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

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

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

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

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

    From regulatory change to regulatory scrutiny

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

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

    Diverging timelines but shared direction of travel

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

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

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

    Data quality is the focus for all regulators and firms

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

    Common reporting errors highlighted in the webinar included:

    • Inconsistent counterparty data

    • Collateral and valuation reporting

    • Reference data quality

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

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

    EMIR and other G20 regimes – expanded requirements

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

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

    What does this mean for firms? 

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

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

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

  • Webinar: The Regulatory Reporting Landscape in 2026

    Webinar: The Regulatory Reporting Landscape in 2026

    Date: Wednesday 28 January | Time: 15:00 GMT / 16:00 CET / 10:00 EST

    Watch the recording

    As regulatory reporting enters a new phase in 2026, firms are navigating potential changes to reporting data alongside increased regulatory scrutiny. With regulators continuing to rely on high-quality data to meet their statutory objectives, expectations around accuracy and control are increasing.

    In Kaizen’s annual Year Ahead webinar, our regulatory experts will explore what this means across global trade and transaction reporting regimes, including MiFIR, G20 reporting (EMIR, ASIC and MAS), North America and money markets. 

    Speakers:

    Watch the recording

  • Market Watch 84: Insights from the FCA and Bank of England Livestream

    Market Watch 84: Insights from the FCA and Bank of England Livestream

    Date: 20 November | Time: 09.30 GMT | Location: Livestream

    Following the publication of Market Watch 84 on EMIR Refit, we are pleased to invite you to a livestream of our breakfast briefing exploring what it means for firms.

    Register

    With senior representatives from the Financial Conduct Authority and the Bank of England joining our panel, this session offers a unique opportunity to hear directly from – and put questions to – the regulators on their expectations and priorities for EMIR reporting in the months and years ahead. 

    Speakers:

    • Richard Kind, Technical Specialist, Financial Conduct Authority
    • Will Parry, Leading the Data Team in the Financial Market Infrastructure Directorate, Bank of England
    • Tim Hartley, EMIR Reporting Director, Kaizen.

     Attendees will gain: 

    • A clearer understanding of the FCA and Bank of England’s latest expectations on EMIR reporting data quality 
    • Insights into how Market Watch 84 signals a shift in supervisory focus and compliance expectations 
    • Key actions to take to strengthen data quality and governance in response to the Market Watch and the recent Q&As.

    Register

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

  • 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.
  • EMIR Refit: Five Key Takeaways from Kaizen RegTalk

    EMIR Refit: Five Key Takeaways from Kaizen RegTalk

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

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

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

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

    Here are five key takeaways from our panel discussion:

    1. Learning from the challenges of EU go-live 

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

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

    2. Now is the time to focus on data quality

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

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

    Key issues that firms continue to face include: 

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

    3. Resilience during periods of increased volatility 

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

    4. ‘Regulatory decay’ 

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

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

    5. Regulators ARE using the data

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

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

    Looking Ahead 

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

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

  • Kaizen Appoints Michael Leach as Chief Revenue Officer

    Kaizen Appoints Michael Leach as Chief Revenue Officer

    London, 24 June 2025 — Kaizen, a leading provider of regulatory compliance solutions for global financial institutions, today announced the appointment of Michael Leach as Chief Revenue Officer (CRO). Leach brings extensive experience from his tenure at London Stock Exchange Group (LSEG), where he played a pivotal role in building UnaVista (now LSEG Regulatory Reporting Solutions) into a global brand.

    As one of the original founders of UnaVista, Leach has known Kaizen since its inception and has extensive knowledge of the regulatory reporting industry. Most recently serving as Global Sales and Regulatory Reporting Business Development Group Director at LSEG, he has demonstrated proven expertise in building successful sales teams and expanding market reach on a global scale.

    In his new role as CRO, Leach will oversee Kaizen’s sales strategy, business development initiatives, and revenue operations, with a focus on driving revenue growth and supporting the company’s market expansion objectives.

    Michael Leach, Chief Revenue Officer at Kaizen commented: “I’m excited to join the Kaizen team and contribute to the company’s continued growth. I’ve seen firsthand the value and innovation the company brings to the regulatory reporting and compliance space. I look forward to working with the talented team here to accelerate our market presence and deliver exceptional value to our clients.”

    Dario Crispini, CEO of Kaizen, said: “We are thrilled to welcome Mike to our executive team. His extensive background at LSEG, combined with his deep understanding of our industry and proven track record in building successful sales organisations, makes him the ideal leader to drive our revenue growth strategy. Mike’s leadership and industry expertise will be instrumental in helping us achieve our ambitious growth and market expansion goals.”

    Leach’s appointment comes as Kaizen continues expand its market presence in the regulatory compliance sector.

    (ends)

    For more information, please contact Fiona Wilde, Head of Marketing and Communications, at media@kaizenreporting.com

  • Kaizen wins Best Solution for Sell-Side Regulatory Compliance

    Kaizen wins Best Solution for Sell-Side Regulatory Compliance

    London, Wednesday 21 May – Kaizen, a leading provider of regulatory compliance solutions for global financial institutions, has won ‘Best Solution for Sell-Side Regulatory Compliance’ at the A-Team RegTech Insight Awards Europe 2025 for its ReportShield™ Accuracy Testing service.  

    Kaizen’s ReportShield™ Accuracy Testing is an automated, managed solution that tests the quality of trade and transaction data reported to the regulator. What makes the solution unique is the deep testing of all reportable trades down to field level, providing financial firms with full visibility of their reporting quality.  Accuracy Testing covers all global trade and transaction reporting regimes.

    Clients access their results including detailed management information via the Kaizen Hub, Kaizen’s easy-to-use platform, which also provides actionable insights into reporting quality. They can also assess their ongoing performance with historical trends and compare the quality of their reporting with similar firms, thanks to Kaizen’s large client base.  

    Jean-Marie Mamodesen, Head of European Sales at Kaizen, said: “A big thank you to the editorial and advisory board members who selected Kaizen as the Best Solution for Sell-Side Regulatory Compliance at this year’s RegTech Insight Awards Europe 2025. This award is testament to our commitment to helping financial institutions navigate complex regulatory challenges. As sell-side firms in Europe continue to grapple with the complex changes introduced by EMIR Refit and prepare for the upcoming MiFIR Review, our ReportShield Accuracy testing provides the confidence and clarity they need. By providing detailed insights that go beyond basic validation, we empower our clients to turn reporting from a burden to a business advantage.”

    Angela Wilbraham, CEO of A-Team Group commented: “Congratulations to Kaizen for winning Best Solution for Sell-Side Regulatory Compliance at the fifth annual RegTech Insight Awards Europe 2025. The awards recognise both established providers and innovative newcomers providing RegTech solutions that have successfully improved firms’ ability to effectively respond to evolving and ever more complex regulatory requirements across the global financial services industry.”

    At last year’s RegTech Insight Awards Europe, Kaizen’s Single Rulebook platform won ‘Best Solution for Regulatory Change Management’.

    (ends)

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

  • Kaizen receives £42 million growth investment from Guidepost Growth Equity

    Kaizen receives £42 million growth investment from Guidepost Growth Equity

    London, November 6, 2024 – Kaizen, a leading provider of regulatory compliance solutions for global financial institutions, today announced the completion of a £42 million minority investment from Guidepost Growth Equity, a Boston-based growth equity firm partnering with entrepreneur-led technology companies. The investment will be used to accelerate product development, invest in go-to-market initiatives, expand in North America, and enhance its award-winning compliance technology. This represents Kaizen’s first external investment since its founding in 2013 by CEO Dario Crispini.

    Kaizen is the global leader in regulatory reporting quality assurance with its pioneering ReportShield platform, which enables its clients to fully test the accuracy and quality of regulatory reports at the trade level, identify 100% of errors at scale, and efficiently remediate with global regulatory coverage including MiFID, EMIR, SFTR, CFTC, and SEC, among others. 

    Kaizen has established itself as a trusted partner to the world’s largest and most sophisticated banks, asset managers, hedge funds and brokers to ensure accurate, complete, and timely reporting in an increasingly challenging regulatory environment, evidenced by strong revenue growth since inception.

    More recently, the Company has diversified its product suite to include solutions for managing and reporting shareholding disclosures, regulatory rules management, trade and communications surveillance and research management. Kaizen has also invested in London Reporting House and Cumulus9.

    Dario Crispini, Founder and CEO, Kaizen commented: “We are delighted to be partnering with Guidepost as we enter a new chapter in our evolution. Guidepost has a great track record in helping firms reach their full potential and their investment and partnership will enable us to build and enhance our existing technology, deliver new compliance solutions, and drive our expansion into North America. The solutions we offer at Kaizen are designed to help our clients adhere to their compliance obligations in an efficient and cost-effective manner and we look forward to delivering more solutions that do just that.”

    Gene Nogi, General Partner at Guidepost said: “Kaizen has transformed the transaction reporting and compliance market, helping the world’s largest financial institutions navigate and comply with an increasingly complex regulatory environment with heightened scrutiny from regulators. The Company embodies everything we look for in an entrepreneur-led, capital-efficient, rapidly growing, and highly differentiated technology business operating within a large, dynamic market. We are thrilled to partner with Dario, Ian and the entire team at Kaizen and look forward to working together on the next stage of the journey.”

    As part of the investment, Gene Nogi will join the Kaizen Board of Directors alongside two new independent directors to be named. Raymond James was the exclusive financial advisor on the investment and Norton Rose Fulbright acted as legal counsel to Kaizen. Liberty Corporate Finance, Alvarez and Marsal and Crosslake also advised Kaizen. Choate Hall & Stewart and Stevens & Bolton acted as legal counsel to Guidepost.

    About Guidepost Growth Equity

    Guidepost Growth Equity (“Guidepost”) is a leading core growth equity firm that partners with entrepreneur-led companies utilizing technology to transform industries within application and infrastructure software and tech-enabled and data services. Current and prior investments include ActiveViam (acquired by Nordic Capital), ClassWallet, Lucid (acquired by Cint Group AB), Mineral (acquired by Mitratech), OutSystems, Traction on Demand (acquired by Salesforce), and Tractive. The firm is headquartered in Boston, MA.

    Guidepost Growth Equity provides the flexible capital, operational assistance, and strategic guidance necessary to support the continued success of high-growth businesses and has over $1.9 billion of capital under management. For more information, please visit their website. 

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

     

     

     

  • Tim Hartley speaks to FOW a week after the UK EMIR Refit implementation

    Tim Hartley speaks to FOW a week after the UK EMIR Refit implementation

    How did the first week of UK EMIR Refit go? How did it compare to the EU go live in April?

    Kaizen’s EMIR Reporting Director, Tim Hartley spoke to Luke Jeffs at FOW about how the go live is going and the challenges that firms now face with both sets of reporting rules.

    “The challenge is finding the things that are wrong. When a trade gets submitted, you’ve met the validation rules, which is great, so you’ve formatted in the right way but is the data right? Does it reflect your firm and your derivatives in the right way? That is a much harder question.”

    Read the article on FOW’s website.

  • Video: David Nowell on what is happening with EMIR Trade Reporting

    Video: David Nowell on what is happening with EMIR Trade Reporting

    In this video, David Nowell answers the below questions:

    • Why is EMIR important?
    • Following recent comments from ESMA about the FCA and other NCAs, what changes are we likely to see?
    • What do the changes mean for financial firms?
    • What are the key changes from the recent EMIR re-fit?

    If you need help with your EMIR Trade Reporting data quality, get in touch.

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

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

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

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

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

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

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

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

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

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

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

     

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

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

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

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

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

  • FCA to increase its scrutiny of EMIR reporting

    FCA to increase its scrutiny of EMIR reporting

    The FCA is likely to increase its focus on EMIR trade reporting quality in response to a recent report from ESMA that criticises the regulator’s approach. In its response to the criticism, the FCA has said it is revising its EMIR data quality strategy which will include the creation of a new central data quality team and the upgrading of its cloud infrastructure to receive EMIR data and check for quality issues.

    What’s the background?

    A recent report from ESMA has concluded that there are number of insufficient supervisory controls over the quality of the FCA’s EMIR data. The FCA was not the only NCA called out – six were assessed. ESMA’s findings will probably not have come as a surprise to many firms. UK firms are used to the FCA being extremely proactive in monitoring the quality of MiFID II transaction reporting however as we’ve pointed out previously, less so with EMIR.

    But isn’t EMIR more important than MiFID II?

    EMIR reporting should be considered as the most important regulatory reporting requirement as it is designed to help regulators monitor for systemic risk – ie. helping to ensure that there is not a collapse of the entire financial system. So it is essential that the regulators have a strong supervisory regime to ensure that the quality of the data reported by firms is sufficient to enable the guardians of financial stability to perform their functions. In a statement contained in ESMA’s Final Report, the FCA rightly points out that it is the Bank of England that is largely responsible for financial stability in the UK, so there are more limited ways in which EMIR data can be integrated into its overall supervisory approach.

    What does the FCA do currently?

    Just over two years ago, the FCA issued a fine of £34.5m to an investment firm for failing to comply with Article 9 of EMIR. This is the only fine it has issued so far for the regime. There is also a requirement on firms to report breaches. However, there is a telling story on the number of error forms submitted to the FCA: earlier this year following an FOI request, the FCA confirmed to us that it received notifications from 384 firms for MiFID II transaction reporting breaches since go-live compared to just 75 for EMIR trade reporting in the period since Q2 2018 when the EMIR breach form became available.  

    When you consider that around 9,000 UK entities have an EMIR reporting obligation and 3,000 UK entities have a MiFID II reporting obligation, this statistic becomes even more concerning.  We can say with confidence that this is most definitely not because UK firms’ EMIR reporting is better than their MiFID II transaction reporting. For example,  in our quality assurance testing we detect a significantly larger amount of errors in the EMIR reports than we do in the MiFID II transaction reports.

    What should firms do?

    Be prepared for a far more intrusive investigation of your EMIR reports. Our advice is to look at your EMIR reporting now.  If you are unsure about the quality of your EMIR reports, or just want to know how good – or bad – your reporting is, then this is why we here at Kaizen exist. Our ReportShield™ testing services have been developed to provide a full assessment the quality of your reporting.  Contact us for a discussion on how we can give you full transparency of your EMIR reporting quality.

    Read the ESMA report on its website.

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

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

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

    Register

     

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

  • Why communication and cooperation are the key to avoiding regulatory reporting fines

    Why communication and cooperation are the key to avoiding regulatory reporting fines

    Recently we saw a large inter-dealer broker fined by the FCA for ‘improper trading’. The final notice stated that the firm was “failing to conduct its business with due skill, care and diligence, failing to have adequate risk management systems and for failing to be open and cooperative with the FCA”.

    This led me to think that the same message can be used across all regulations and that this was the same communication we heard from the FCA when it handed out the two MiFID I fines earlier this year. Introducing care and diligence with added controls, governance and independent quality assurance testing is one thing; it’s then communication and cooperation with the regulator that are key.

    Be proactive, transparent and open with your NCA

    Being on the front foot with the regulator should not be deemed a negative or onerous task. It is incredibly important that all firms that have found an issue with their reporting, relay this message to their National Competent Authority (NCA) as soon as they can, through the applicable channels. The key message we see and hear from NCAs is that they always encourage firms to be proactive, transparent and open.

    Once an issue has been identified either internally or externally via a quality assurance testing service, analysis has to be completed and the relevant action decided upon.

    Alert your NCA as soon as possible

    Depending on the regulatory regime, the NCA may require a form to be completed. In the UK, for MiFIR transaction reporting an errors and omissions form* needs to be emailed to the Markets Reporting Team.  For EMIR, a breach notification form* needs to be completed.

    The likelihood is that the sooner the issues are identified and then communicated, the happier the relevant NCA will be that you are being proactive and cooperative to improve the quality of your reporting.

    At Kaizen, as well as helping firms check the accuracy of their regulatory reporting, we have former regulators as part of our team of subject matter experts. Not only does their expertise feed into our testing services, our clients also benefit from our advice through the process of communication and cooperation with your NCA.

    We’ve helped a number of firms provide confidence to the regulator through identification of issues in reporting quality but also through putting the right controls in place. Contact us if you’d like to discuss any of the issues raised in this blog.

    *Does not open in new window.

  • In the news: David Nowell speaks to Practice Insight

    In the news: David Nowell speaks to Practice Insight

    Our Senior Regulatory Reporting Specialist David Nowell recently spoke to Thomas Helm at Practice Insight for a special report on the accumulative impact of post-crisis reforms. In the report Thomas Helm joins the dots of transparency initiatives to reveal the bigger picture. David commented on data quality for the 124 data fields of EMIR trade reporting and the kind of errors we regularly see here at Kaizen. 

    “David Nowell says he frequently comes across errors, such as notional amounts in the “quintillions” in the Emir space, and that these errors can distort the public data aggregations. When compiling the public data aggregations we’d artificially disregard notionals above a certain level because they were obviously false, he says.

    Read the full report.         

  • A tsunami of EMIR Q&As

    A tsunami of EMIR Q&As

    Just when you thought it was safe to go back into the water, ESMA has hit us with a third EMIR Q&A in as many months. The impact on trade reporting can be summarised as follows:

    Funds and counterparties (General Question 1)

    The text now states that the fund manager must (rather than can) report on behalf of the funds and that the ID of the fund manager shall be provided as the report submitting entity. Please take care with this statement – we do not think it should be taken at face value. Whilst the amended EMIR Article 9 makes the fund management companies ‘responsible and legally liable’ for the reporting, we do not believe this is intended to prohibit delegated reporting by the broker (or another third party) on behalf of the fund manager (where the third party would be the ‘submitting entity’). It is another example where ESMA needs to be more precise in its use of language and advice to the industry.

    Reporting of outstanding positions following entry into force of EMIR (backloading)

    TR Question 4 has been completely deleted reflecting the removal of the backloading obligation following Refit.

    Intragroup transactions (TR Question 13)

    Again, synchronising with Refit, the text clarifies that intragroup trades are not reportable if certain conditions are met. These conditions are outlined in TR Question 51.

    Blocks and allocations (TR Question 39)

    Similar to General Question 1, we have further imprecise text from ESMA. ESMA states that the fund manager must report to the trade repository on behalf of the individual fund where the fund is identified as the counterparty to the trade. While the fund manager is responsible and legally liable for making the report, it can still delegate the reporting obligation. This ‘change’ applies from 18 June 2020.

    Notional amount field for credit index derivatives

    Where there is a change in index factor due to credit events, counterparties should not modify the notional (field 2.20); they should only change the index faction (field 2.89).

    Conclusion

    Not a huge amount of change in the latest Q&A, but it does demonstrate some of the pitfalls in interpreting the ESMA text and the importance of keeping in touch with the regulatory changes. If you’d like some help interpreting the changes or would like transparency of the quality of your EMIR trade reporting, please contact us to find out more about how our quality assurance and controls can get your reporting accurate.

  • ESMA fines trade repository for data delivery breaches

    ESMA has announced it has fined a trade repository for failing to provide regulators direct and immediate access to details of derivative contracts. The failures relate to trade terminations and valuations and collateral updates for the period from the start of EMIR trade reporting go live in February 2016 through to October of the same year. According to the public notice, ESMA remained unaware of the error until it was informed by the Dutch national competent authority (NCA) in July 2016.

    The fine should be a reminder to all industry participants that ESMA takes EMIR trade reporting very seriously. ESMA and the NCAs also have a ‘Data Quality Action Plan’ to address quality issues in EMIR trade reports submitted by firms.

    If you are in any doubt whether your reports meet the standards required by the regulators, please get in contact with us to discuss your EMIR data quality. The FCA has already issued a £34.5m fine for EMIR reporting breaches – we can help you put the right controls in place to make sure that you are not at risk too.

  • EMIR Refit – white elephant regulation

    EMIR Refit – white elephant regulation

    Many firms are waking up to the fact that ‘EMIR Refit’ is being implemented on 17 June 2019 and they may be having a coronary over how it might impact EMIR trade reporting. For once, firms can relax as the only big(ish) change for trade reporting takes effect from June 2020.

    Before diving into the detail, let’s take a step back and remind ourselves what EMIR Refit is all about.

    The aim of EMIR Refit is to make its compliance burden more proportionate, particularly for the non-financial counterparties (NFCs). Now that is an absolutely splendid aim, so how has it worked out with trade reporting? After the colossal amount of time spent on the debate, I have to conclude that it’s a massive disappointment for reporting, resulting in the following meagre pickings:

    1. Mandatory delegated reporting on behalf of NFC- firms from 18 June 2020. This is the only meaningful change from Refit. From 18 June 2020 (repeat 2020, not 2019) ‘financial counterparties’ will become responsible and legally liable for reporting the details of derivative contracts they have concluded with an NFC-  on behalf of both. The NFC- can still choose to report on its own behalf if it wants to, but it must give its counterparty notice of its intentions to avoid duplicative reporting.
    2. Removal of the back-loading obligation. There is no longer an obligation for counterparties to report historic data on derivatives that were outstanding on or after 16 August 2012 and which terminated before the EMIR reporting start date of 12 February 2014. This might sound like a welcome dispensation for the industry, but it wasn’t a very practical requirement in the first place – what possible value could the regulators extract from trades terminated five years in the past? The revised reporting technical standards also virtually forced this change as it is highly unlikely that any counterparty will have the required information to report these ancient trades in the post-2017 standards.
    3. Intra-Group Exemption – There may be too many conditions to be met for this to be of much use, but an exemption from the reporting obligation is available for intra-group transactions where all the following criteria are met:
      • at least one counterparty is an NFC;
      • both counterparties are fully consolidated;
      • both counterparties are subject to appropriate centralised risk evaluation, measurement and control procedures;
      • the parent undertaking is not a financial counterparty.

    Additionally, counterparties must notify their NCA of their intention to apply this exemption

    1. Fund management company reporting obligations. Fund management companies and Alternative Investment Fund Managers will become solely responsible and liable for reporting derivative trades made by their UCITS, AIFs and institutions for occupational retirement provision.

    Delegated reporting

    So the only substantial change to trade reporting introduced by EMIR Refit is the mandatory delegated reporting by financial counterparties on behalf of their NFC minuses. Although many financial counterparties provide delegated reporting already, they will be concerned by the addition of legal responsibility for the accuracy of the delegated reporting they provide. This concern may highlight one of the loopholes of EMIR trade reporting – although delegated reporting may boost the pairing rates, it might not actually be very good. There is a great temptation to simply ‘flip’ elements of a trade report and present this as delegated reporting on behalf of the counterparty. The true requirements of delegated reporting could be far more onerous, particularly with the increased complexity of many elements introduced in the 2017 revised reporting technical standards. This is evidenced by Refit stressing the obligation on the NFC- firms to supply all the required information to their financial counterparties in order for them to report accurately on their behalf.

    It is also questionable whether the mandatory delegated reporting will help the NFC- firms that much. It will only work as planned if all their counterparties are EU firms. Many of their current counterparties may already be non-EU counterparties, so they will have to maintain their trade reporting infrastructure. Of course, a hard Brexit would seriously negate the value of this new measure as ESMA would not have any power to force a UK financial counterparty to provide delegated reporting for a non-EU NFC- (but maybe it could force the NFC- to only deal with EU firms).

    A lost opportunity

    Many firms had hoped that the Commission’s review of EMIR during 2015 and 2016 could lead to fundamental changes in the trade reporting requirements. Expectations included the removal of ETDs from the reporting obligation and the removal of the dual-sided reporting obligation. At the very least, many financial counterparties hoped that the review would lead to the removal of the obligation to report individual ETD trades and to rely on the end-of-day position reports. Since the main purpose of EMIR trade reporting is to monitor for systemic risk, there appears to be little value in collecting reports of ETD trades when they are immediately netted into an end of day position report. Additionally, key elements of EMIR trade reporting like lifecycle events and collateral reporting can only really be sensibly applied to the end of day positions for ETDs. Perhaps the only value of ETD trade reports is for the detection of market abuse – but this is the driver behind MiFIR transaction reporting and their inclusion in EMIR is expensive duplication.

    If the purpose of EMIR Refit is to address disproportionate compliance costs and to streamline reporting, then it can only be described as a lost opportunity. The existing EMIR trade reporting regime might be considered white elephant regulation – expensive and onerous to comply with, yet difficult to understand how it meets its objectives. Even the November 2017 revisions failed to disguise the fact that ETDs have been shoe-horned into reporting regime primarily designed around OTC derivatives.

    If you have concerns about whether you are meeting your EMIR trade reporting requirements or would like confirmation your reporting is accurate and complete, please get in touch with us for a conversation with one of regulatory experts.

  • ESMA publishes new EMIR Q&A

    ESMA publishes new EMIR Q&A

    With ESMA publishing documents faster than it’s possible to read them, we ‘welcome’ another EMIR Q&A today. The good news for reporting is that it mainly impacts clearing and there are only two amendments in the trade reporting section.

    The first of these comes in TR Question 36 – the reporting of OTC derivative notations. This is a simple clarification from ESMA, stating that:

    “For reporting purposes, only instances where a counterparty (being a CCP or another counterparty) steps into the derivative contract and becomes a new counterparty to the derivative contract should be reported with Action Type “New”. For the original report relating to the existing transaction derivative, counterparties should send a termination report marked as ’C= Early termination’, completing the field “Termination date”. The remaining counterparty and the new counterparty should then send a new report with action type “New” relating to the new transaction derivative.”

    So, there’s some new words in TR Question 36, but no change to reporting.

    The second change impacts TR Question 42 – population of ‘Clearing Obligation’ and ‘Cleared’ (fields 2.34 & 2.35) – and this marks a welcome simplification with the new instructions becoming applicable from 17 June 2019. The implementation of EMIR Refit removes obsolete references to frontloading leaving the remaining instructions far more digestible:

    “The field [Clearing Obligation] should be populated in following way: 

    • The field is not applicable to the transactions executed on a regulated market and should be left blank
    • In the case of cleared trades, the field “Clearing obligation” should be populated with “N” and the field “Cleared” – with “Y.”

    Even with the Q&A, understanding how to trade report correctly under EMIR can be a complicated and perplexing task. At Kaizen, we find many of the mistakes firms make with their reporting stem from a basic misunderstanding of the requirements.

    If you want to unravel the mysteries of EMIR trade reporting and avoid the potential pitfalls leading to breaches, why not attend one of our CPD and CISI accredited courses. In our experience, a small investment in training can help avoid costly remediation at a later stage.

  • Santa’s SFTR gift extends to EMIR

    Santa’s SFTR gift extends to EMIR

    Santa delivered the long-awaited SFTR technical standards just in time for Christmas to delight SFTR specialists everywhere. But there also appeared to be something at the bottom of Santa’s sack for EMIR trade reporting specialists because the SFTR implementing technical standards also amended the EMIR trade reporting ITS. However, now we’ve taken the wrapping paper off this present, there doesn’t seem to be anything of value inside…

    No real change

    The reference to “Implementing Regulation (EU) No 1247/2012” seems curious as this is the old ITS that has already been amended by the shiny new Implementing Regulation (EU) 2017/105. Putting that aside, the changes appear meaningless. In a nutshell, the only taxonomy that can be used to classify an instrument is the CFI (as the ‘UPI’ alternative doesn’t exist and wouldn’t be a classification taxonomy if it did exist). This is not a real change as ESMA’s validation scheme already ensured only the CFI could be used – NB: the validation scheme is a really (under)handy mechanism to tweak the technical standards without having to bother with tiresome process.

    Annoyingly, Annex II of the SFTR ITS replaces Annex to the EMIR trade reporting ITS (Regulation (EU) 2017/105 rather than the stated (EU) 1247/2012). This is a tricky case of spot the difference – even the amusing typos in the formats of the ‘Collateral portfolio code’ and the ‘Trade ID’ have been persisted. The only changes I could find were on ‘Product classification type’ (only ‘C’ for CFI allowed), ‘Product classification’ (has to be a CFI) and the UPI is no longer referenced as a possible ‘Underlying identification type’ or ‘underlying identification’.

    SONIA

    At a micro detail level, I was disappointed that SONIA wasn’t allowed to join the floating rate index club, despite being set to become a key benchmark. The publication of the ‘new’ ITS annex might have been an ideal time to add it to the list of permitted codes for floating rate indices alongside other key benchmarks such as JIBAR and BUBOR. As a paranoid Briton, I like to think of it as a slight against UK standards, but maybe we were nebulous in just not asking for it. Still, it might be a good one for firms to remember if they ever get lectured by the regulators on the importance of putting “EONA” in their floating rate fields instead of “EONIA”.

    We will be providing EMIR trade reporting half-day training courses from early next year.  Please contact us to register your interest and for further details. 

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

    Stockholm conference: New regulatory insights on EMIR and MiFIR reporting

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

    European Commission’s Fitness Check

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

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

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

    MiFIR data quality issues in Europe

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

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

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

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

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

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