Tag: MiFIR transaction reporting

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

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

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

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

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

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

    From supporting a statutory objective to a strategic data asset

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

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

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

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

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

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

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

    Reduced burden should increase data quality

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

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

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

    Improving competitiveness is not deregulation

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

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

    What happens next?

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

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

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

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

  • 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.
  • Do not adjust your (transaction reporting) clock

    Do not adjust your (transaction reporting) clock

    This weekend, the UK clocks spring forward to British Summer Time. While you may need to adjust the clocks and watches at home, please remember that the time fields for MiFIR trade and transaction reporting and EMIR trade reporting should be populated in Coordinated Universal Time (UTC). Firms were required to report in UK local time under MiFID I but this is no longer the case for MiFIR transaction reporting.

    The regulators are not likely to have any sympathy if you make errors following these time transitions as they have warned firms of such mistakes in Market Watch 59:

    “The time when the transaction was executed should be reported in Coordinated Universal Time (UTC). We continue to see errors in transaction reports when UK clocks transition to and from British Summer Time, as well as errors driven by inaccurate clock synchronisation. Firms should have arrangements in place to ensure consistent and accurate reporting of trading date and time.”

    How Kaizen can help

    As part of our ReportShield™ quality assurance services, we can run a number of tests to detect instances where the wrong time has been populated. Our accuracy testing service can test all fields in all reports submitted over a given period to give you confidence that your reporting is complete and accurate. For more details or a discussion with one of our regulatory experts, please contact us. 

    Pub quiz trivia

    It may appear strange that the official abbreviation for Coordinated Universal Time is ‘UTC’ rather than ‘CUT’. This abbreviation arose from a desire to use the same abbreviation in all languages. Whilst the abbreviation ‘CUT’ makes sense for English speakers, French speakers advocated ‘TUC’ for ‘temps universel coordineé’. In the end, they agreed to compromise on ‘UTC’, which doesn’t make sense in either language…

    Why not join in the conversation in our Kaizen community on LinkedIn?

  • Video: David Nowell on MiFID II reporting

    Video: David Nowell on MiFID II reporting

    Kaizen’s Senior Regulatory Reporting Specialist David Nowell provides us with his view on:

    • What the regulators will be expecting now on MiFID II reporting
    • How investment firms can ensure reporting accuracy

    Read David’s blog MiFID II 2nd anniversary – ready for the terrible twos?

    Thank you to the Wealth Mosaic. 

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

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

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

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

    What action have we seen from the FCA so far?

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

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

    How can firms be sure they’re reporting accurately?

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

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

    Happy Anniversary MiFID II.

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

  • No market abuse sanctions by FCA in 2018

    No market abuse sanctions by FCA in 2018

    ESMA has published its peer review on how national competent authorities handle suspicious transactions and orders reports (STORs) under the Market Abuse Regulation. It is fully compliant in four of the ESMA metrics and broadly compliant in the other two.  So congratulations FCA – pretty much top of the league in this review.

    However, what is interesting is that despite this near-perfect report card, the FCA has not imposed any measures and sanctions on firms.  Surely the true measurement has to be the number of successful market abuse cases the regulator has brought? The ESMA report has a handy table showing the number of measures and sanctions imposed for market abuse infringements and the UK figures for 2018 show no sanctions.

    Without wanting to appear like the Christmas Grinch, in our view this is a very disappointing figure. Bearing in mind that 2018 marked the introduction of a dramatically more complex transaction reporting regime which offers regulators a far richer data set to monitor market abuse more effectively, this failure to sanction would indicate to us that something isn’t right.

    Whilst many firms are making great efforts to report STORs and to submit transaction reports, the FCA can only do its job effectively if those transaction reports are complete and accurate. If you are not completely confident that your transaction reports meet this requirement, talk to us about our ReportShield™ data quality, reconciliation and training services.

    What do you think about this peer review from ESMA? Join in the conversation over on our LinkedIn.

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

  • The scariest regulatory reporting changes facing you this Halloween

    The scariest regulatory reporting changes facing you this Halloween

    It’s Halloween! And what better time to cover off some of the scariest regulatory reporting changes that you need to keep very very close to, following the full-moon…

    Quoting Macbeth’s three witches, “By the pricking of my thumbs, something wicked this way comes”, here are three key regulations affecting everyone in the coming months:

    In Thunder comes Brexit

    31 October was always going to be a horror Halloween show but the EU have prolonged the agony for another three months to 31 January. The good news is that most firms have prepared for the October exit but do keep an eye on any unknown regulatory changes in the coming months – or read our Brexit White Paper to help with your preparations.  

    In Lightning comes SMCR

    Ghosting quietly in, don’t forget if you’re an Core or Enhanced Firm, as categorised by the FCA, your CF Approved Persons change to SMFs under the Senior Managers and Certification Regime (SMCR) on 9 December. Encouraging a culture of taking responsibility for actions and demonstrating a clear understanding of where that responsibility lies, are the key messages. You can’t use a magic wand to sign-off on the accuracy of your regulatory reporting, a key task for your SMFs.

    In Rain comes SFTR

    As we speak on the day of the devil, SFTR is only 166 days away.  This is frighteningly close.  Are you prepared and testing in UAT for this new reporting regime coming into effect on 14 April 2020? Contacting our very own SFTR expert Jonathan Lee is much less scary than a letter from the regulator.

    When the hurly-burly’s done, when the battle’s lost and won, Kaizen is here to help with the most scary of regulatory reporting challenges. Please contact us if you’re worried about any of the above and we can turn your regulatory reporting obligations from a trick to a treat!

    Author: Chris Machinbeth

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

  • 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

  • ESMA clarifies FX forwards transaction reporting in new MiFIR Q&A

    ESMA clarifies FX forwards transaction reporting in new MiFIR Q&A

    ESMA has provided a very useful example of how to report FX forwards in its latest Q&A on MiFIR data reporting. In particular, we would urge firms to take note on the practice of populating the ‘quantity’ and ‘price’ fields:

    • The ‘quantity’ (and ‘quantity currency’) should reflect the amount of the FX forwards in the base currency
    • The ‘price’ (and ‘price currency) should show the forward rate expressed as a price of base currency in the quoted The monetary value XML tag should be used (if reporting to an ARM in flat file, ‘price type’ is monetary value.

    The only additional changes appear to be in the table of national identifier formats. This details a change in the format of Portuguese passports issued after April 2018 and corrections to the Romanian National Identification Number and national passport formats.

    Whilst the new MiFIR Q&A signals only relatively minor changes, it clearly demonstrates the need for firms to remain on top of regulatory developments. Our regulatory reporting training courses help firms stay abreast of the reporting requirements and help identify any interpretational errors. For further details, please see our training courses.

     
  • In the news: David Nowell speaks to Practice Insight on regulatory change

    In the news: David Nowell speaks to Practice Insight on regulatory change

    Senior Regulatory Reporting Specialist David Nowell spoke to Alice Tchernookova from International Financial Law Review’s publication Practice Insight about the future of regulation now that MiFID II has bedded down within the industry. 

    “We have almost reached a stage where we must ask ourselves whether being fully compliant is actually possible,” said David Nowell.

    Read the full article. 

  • MiFIR transaction reporting goalposts set to shift again

    MiFIR transaction reporting goalposts set to shift again

    Whilst it may be a bit more of a tweak than a wholesale change, firms need to be aware and plan for changes to the ESMA validations that are targeted to come into effect on 23 September this year. 

    The changes were agreed back in July 2018 but delayed by the Brexit postponement and are mainly amendments to cover mistakes in the validation previously introduced. The changes, cut and pasted from the ESMA version history, are as follows:

    • rule id 010: field 3 must not be populated. This also pertains to SIs;
    • rule id 014: add provision for the case when an LEI is in the “Lapsed” status for a certain period;
    • rule id 096: validation of field 28 against the reception timestamp;
    • rule id 117: field 37 not mandatory for SIs;
    • rule id 136: check against additional CFI codes;
    • rule id 154: check against additional CFI codes;
    • rule id 227: correction of a typo in one of the CFI codes.
    • Clarified description of rules 228 and 267.

    For me, the most important of these changes is the change to Rule 117.  From the implementation of this change, firms should no longer populate ‘Country of branch membership’ for trades against systematic internalisers. Of course, this field should never have been populated for trades against systematic internalisers in the first place as this contravenes the Regulatory Technical Standards (“This field shall only be populated for the market side of a transaction executed on a trading venue or on an organised trading platform outside of the Union.”). I think it is important to highlight that this oversight has forced firms to make an error in their transaction reports in order for them to be accepted by the NCAs.

    I don’t wish to criticise the regulators for making errors, as I believe it is inevitable that there will be some initial errors in the implementation of such a complex regulatory reporting regime – for both regulators and firms. However this issue clearly raises the question about whether the NCA would expect every firm to submit a form when they are forced to report incorrectly in order for the NCA to accept the report. There has to be a degree of common sense and this is not reflected in the wording of Market Watch 59.

    It is also fair to say the changes have not been widely publicised. ESMA has made a notification of changes but I’m sure most people, like me, will find this notification extremely difficult to understand. I’m sure people will also be confused by the validation version history that still states that the changes were “applicable from the end of 2018”. Perhaps the FCA is waiting for more confidence in the 23 September implementation date before it makes an announcement. However, whilst these changes aren’t major, firms need time to assess the changes, code and test any required system changes. September 23 already appears very close.

    Kaizen will of course be updating our ReportShield testing to include the latest validation changes in time for September 23. We provide validations as part of our accuracy testing service at no extra charge to clients – saving significant costs in avoiding outsourcing an additional validations service. Please contact us for a discussion with one of our regulatory experts to find out more.

  • Ten steps to MiFIR transaction reporting nirvana

    Ten steps to MiFIR transaction reporting nirvana

    Firms face a daunting array of complex regulatory requirements, but one of the most fiendishly difficult to comply with appears to be transaction reporting. The recent substantial fines levied by the UK Financial Conduct Authority (FCA) showed that even tier-one firms have difficulty meeting the transaction reporting requirements. Considering that these breaches relate to the previous Markets in Financial Instruments Directive (MiFID) reporting regime, firms are becoming increasingly perplexed about how to meet the far more complex Markets in Financial Instruments Regulation (MIFIR) transaction reporting regime. While regulators continue to stress the importance of complete and accurate transaction reporting, the following 10-point path can lead firms closer to transaction reporting nirvana:

    1. Do not be in denial about the costs of doing business

    Budgets are tight everywhere, but investment firms need adequate resources to meet the regulatory requirements, and transaction reporting is one of the most important of these.

    2. Do not under-estimate the costs of remediation

    Being fined by the FCA is never pleasant, but despite recent evidence, fines are likely to remain an exceptional outcome. The regulator is, however, likely to make firms correct and back-report everything they have got wrong. The cost of this remediation will probably far outweigh that of establishing systems and controls to help avoid mistakes and in some cases may even cost more that the fine itself. In addition, if the FCA feels a firm has insufficient controls in place then it can impose a costly skilled persons review under s166 of the Financial Services and Markets Act 2000.

    3. Training.

    This is probably the quickest and cheapest win. In our experience, many of the mistakes firms make with their reporting stem from a basic misunderstanding of the requirements. They are not simple and one mistake resulting from inadequate training can lead to millions of incorrect transaction reports.

    4. Valid does not necessarily mean correct

    This is why we here at Kaizen exist. The regulators apply an extensive validation check on all the reports they receive. There is, therefore, a natural inclination for firms to believe that if a report passes the validation then it must be correct. This is not the case. Our accuracy testing finds that around 70% of reports which passed the validation checks contain at least one error.

    5. Quality assurance checks are essential

    Not least because it is the law: one of the requirements of the “methods and arrangements” for reporting set out in Article 15 of the Regulatory Technical Standards (RTS) 22. It is also one of the main requirements necessary for firms to be confident that their reports are accurate and ensure they do not perpetuate errors.

    6. Firms must not mark their own homework

    Using an independent quality assurance service to test every submitted transaction report will provide a thorough, impartial analysis giving absolute certainty about the state of the firm’s reporting.

    7. Reconcile trades from front-office systems to records received by the regulator

    This is a hard and fast requirement clearly stated in RTS 22. Some firms mistakenly believe this simply involves checking that the number of trades concluded matches the number of reports received by the regulator. This is simply not good enough. The reconciliation must include checking “the accuracy and completeness of the individual data fields and their compliance with the standards and formats specified in Table 2 of Annex I.”  The FCA actively monitors whether firms have requested data from it to complete this check, and so any firm failing to perform this end-to-end reconciliation will be on the regulator’s radar.

    8. Heed the words of the regulator

    The FCA does not really want to sanction firms; it would much prefer that firms’ reports were complete and accurate so that it could do its job of monitoring for market abuse. The regulator sends a consistent and strong message to firms about what they need to do to achieve this goal, which firms must heed. The core message is that firms need adequate systems and controls for transaction reporting. This starts with a solid governance framework, supported by reconciliation and a data accuracy checking. The FCA also publishes information about many of the significant failings it sees, and its latest Market Watch 59 identifies the following errors:

    • Incorrect time (especially after the transition to British Summer Time).
    • Price not reported in the major currency.
    • Re-use of identifiers for multiple clients.
    • Incorrect client type code.
    • Inconsistency between trading capacity and buyer/seller IDs
    • Transposition of the “buyer” and “seller” identifiers.

    9. Get market identifier codes right

    It might sound innocuous, but the correct venue field is very important due to the associated validation and data accuracy checks. One of the most common mistakes is using an “operating level” market identifier code (MIC) rather than the correct segment-level MIC. This can result in the firm’s report eventually being rejected by the regulator because the instrument identifier is associated with the segment MIC rather than operational-level MIC. It can also affect how the firm populates other fields such as “country of branch membership”.

    10. Do not be afraid to submit an “errors and omissions” form

    The regulatory sky will not fall in if a firm submits an errors and omissions form. The FCA has reported that it has so far received around 1,300 errors and omissions forms from more than 390 firms, so those firms which do decide to report will not be alone. Failure to submit this form at the right time can, however, land firms in a lot more trouble: the FCA noted in Market Watch 59 that it is unhappy about firms making corrections without first submitting the form.

    MiFIR transaction reporting is a very complex requirement which firms almost universally find difficult to meet (whisper it quietly, but some competent authorities have had their own difficulties too). Failure to make complete and accurate reports will result in costly remediation issues and can prove risky for the senior manager in charge of transaction reporting. Taking due note of the 10 points above will help firms reach their transaction reporting nirvana.

    For more information on any of the points above, please get in touch for a conversation with one of our regulatory experts. 

    This article was first published by Thomson Reuters Regulatory Intelligence on 7 June 2019.

  • Lack of training results in transaction reporting breaches

    Lack of training results in transaction reporting breaches

    One of the most interesting statements from the FCA Final Notices following the recent fines for MiFID transaction reporting breaches concerned the general lack of expertise around transaction reporting in the industry. The firm impacted was clearly trying to do the right thing, but was hampered by “…a scarcity across the Firm and the industry of personnel with the expertise and systems knowledge required both to implement the enhanced controls and remediate the issues identified during the course of the project”¹ 

    It is difficult to understand why this lack of expertise should still afflict such an important area of compliance. Whilst it may not appear to be the most glamourous area of regulation, the FCA has shown a continued willingness to take action against firms for breaches. Many of the errors highlighted by the FCA appear to have been simple mistakes in the interpretation of the reporting requirements and might have been avoided through a more effective training programme. It should also be remembered that these fines relate to the old MiFID transaction reporting which is relatively simple compared to the greatly increased scope and complexity of the current MiFIR transaction reporting regime.

    Help is at hand

    At Kaizen, we believe effective training is an essential element in ensuring complete and accurate transaction reporting. We offer a half day CPD-accredited training course, endorsed by the Chartered Institute for Securities and Investment (CISI), which gives candidates a core understanding of the transaction reporting requirements and the fields that comprise a transaction report. The course can be taken at Kaizen HQ or at your own offices and is accompanied by an exam which enables you to demonstrate your understanding of the reporting requirements. Similar courses are available for EMIR trade reporting and SFTR. Visit our training page for further details and to book your place on one of our upcoming scheduled dates. 

    Are you a Transaction Reporting guru? Why not take part in #TransactionReportingTuesday over on LinkedIn.

    Every Tuesday, on the Kaizen LinkedIn we will be publishing a MiFIR Transaction Reporting question from our training exam. The answer will be posted a week later along with a new question. 


    ¹ FCA Final Notice to Goldman Sachs

  • ESMA updates Q&A on MiFIR and EMIR reporting

    ESMA seemingly delivered a double whammy on 4 February with the publication of Q&As for both MiFIR and EMIR data reporting. However, there’s nothing to get too excited about, although firms do need to understand the ‘clarification’ and adjust their reporting accordingly.

    Impact on MiFIR data reporting

    Bit of a damp squib. There is only one question that relates to transaction reporting (TVTIC on complex trades); the others all relate to RTS 23/MAR reference data reporting. The clarifications can be summarised as follows (italics indicate direct quote from the Q&A):

    How should the TVTIC (field 3 of RTS 22) be populated in transaction reports of a complex trade?

    Bit of a change here. Previously, firms were required to put the same TVTIC on each leg of the reported trades (if they were traded on a trading venue). New instruction is to use the TVTIC provided by trading venue for each leg of the complex trade (where the trading venue uses multiple TVTICs)

    How should Field 15 (Maturity date) of Table 3 of the Annex to RTS 23 and related MAR RTS and ITS be populated in case of trading in bonds after their originally intended maturity date?

    “For bonds that were not paid out on the originally intended maturity date (and therefore have not expired, because, for example, they defaulted), the maturity date should be set to 9999- 12-31 …until they are finally paid out, in which case the maturity date should be updated with the actual date of redemption”.

    How should field 15 (maturity date) and field 24 (expiry date) of Table 3 of the Annex to RTS 23 and related MAR RTS and ITS be populated, if these dates are non-trading dates, e.g. a weekend or a bank holiday?

    “The maturity date/expiry date defined by the issuer or the prospectus of the financial instrument should be used. No adjustment should be made to the next or previous working day for the purpose of instrument reference data reporting.”

    When should an instrument be terminated in FIRDS?

    “When field 12 (termination date) of Table 3 of the Annex to RTS 23 and related MAR RTS and ITS is initially left empty, the reporting entity is expected to fill it in when the instrument is going to be terminated. This also includes the cases when the given instrument has matured/expired, i.e. where fields 15 (maturity date) or 24 (expiry date) are applicable to the given instrument and are populated in the report.

    The termination date should be earlier than or equal to the maturity/expiry date in the cases where the maturity/expiry date is populated.”

    (RTS 23)What action should be taken by the operator of the trading venue or the systematic internaliser in the cases where the LEI of the issuer cannot be obtained?

    Tell the issuer that they should get an LEI (!!!).


    Impact on EMIR Data Reporting

    There are only three clarifications in the EMIR data reporting Q&A – the first two are amendments to previous trade reporting questions whilst the third is a brand new question:

    Q34 – Reporting of contracts with no maturity date (e.g. CFDs);

    ESMA simply reminds firms that they can also report new trades for instruments with no maturity date with an ‘Action Type’ of ‘P’ (“position component”) if it is to be included in a position level report on the same day. This is in line with previous comments from ESMA.

    Q38 – Trades terminated before the reporting deadline

    All trades must be reported even if they are terminated before the reporting deadline and ESMA is simply clarifying that these reports could also be made with an Action Type of ‘P’ if the trade is to be included in a position level report, on the same day.

    Q50 – Reporting of Confirmation Means

    ESMA states:

    The value ‘N’ (not confirmed) should be used either when:

    • The derivative has to be confirmed by the counterparties but has not been confirmed yet;
    • The derivative does not have to be confirmed by the counterparties because it has been traded on a trading venue and once traded all the terms of the contracts are known and agreed by the parties.

     In other cases, the counterparties should report the ‘E’ or ‘Y’ value for this field depending on the confirmation means used (electronic or non-electronic).

    I think this is the one element in the new Q&As that may surprise some firms as it clearly states that trades on a trading venue should have a value of ‘N’.

    So, not a lot really going on with the new Q&As. It is tempting to think that little news is good news. Personally, I don’t subscribe to this point of view; I think there is still plenty of grey in there that would benefit from further clarification, which is natural given the fundamental changes brought in by MiFIR. I also think there are a few elements in the Guidelines that, with hindsight, could have been better – (equity swaps is my favourite bugbear today).

    If you have a burning MiFIR or EMIR reporting question keeping you awake at night, why not contact us at Kaizen.

  • MiFIR transaction reporting –  a happy 1st birthday?

    MiFIR transaction reporting – a happy 1st birthday?

    January 3, 2019 marks the first anniversary of MiFIR transaction reporting and what a joy it has proved to be!  The changes introduced last year were truly transformational with new asset classes being brought into scope, new reference data standards to contend with and a massive increase in the number of the fields to be reported. Many operations and compliance staff will still have unhappy memories of last year’s struggle to implement the changes over the festive period to be ready for go-live. Despite the magnitude of the task, most participants will look back in relief that it wasn’t quite the fiasco many had feared. However, even one year on, there are a number of outstanding issues to keep us all awake at night…

    Reference data

    Perhaps the most difficult part of transaction reporting is knowing exactly what instruments are reportable. Many have assumed this is simple as ESMA’s Financial Instruments Reference Data System (FIRDS) contains all the reportable instruments. Unfortunately, this is not quite true! For a start, FIRDS does not provide details of index constituents or the underlyings to third country derivatives and depository receipts – the onus is on firms to work this out for themselves. Perhaps more importantly, the quality of FIRDS, whilst much improved since go-live, is still not good enough. We still have the FCA’s warning in MarketWatch 54: “Please note that ESMA states that it cannot take responsibility for this information being complete, accurate or up to date”. This is frustrating for firms because if they send a report with an instrument identifier that is not contained in this database within seven days of receipt of the report, it will be rejected and sent back to the reporting firm. This is almost a catch-22 situation for firms as it is now a breach to over-report or to under-report, but they still face the possibility of having their reports rejected even if they are correct because of the FIRDS limitations. Whilst the regulators demand “complete and accurate” transaction reports from firms they cannot ensure the quality of the essential reference data firms need to meet this obligation.

    Legal Entity Identifiers (LEIs)

    Many firms were concerned that they couldn’t get LEIs for all their counterparties they traded with ahead of go-live. This was particularly concerning as ESMA’s validation specified that “the initial registration date of the LEI shall be equal to or before the trading date” so firms couldn’t implement a fix if they had made a reportable trade against a counterparty without an LEI. However, an early Christmas present from the regulators postponed this validation until 3 July 2018 and firms have been largely successful in persuading these entities to get LEIs or in getting LEIs on their behalf so that they can continue to trade with them.

    Transaction Reporting Guidelines

    Most participants are grateful for ESMA’s extensive transaction reporting guidelines  and there is no doubt that they helped firms’ preparations enormously (compare and contrast with the EMIR Q&A!). However, nobody can say that they are an easy read or that they cover every trading scenario. This is only to be expected as MiFIR is a very complex reporting regime and regulators cannot envisage all possible trading scenarios across all member states. A number of firms have been frustrated by their local NCA’s inability to respond to every question, but this is a feature of harmonised regulation – it naturally prevents NCAs from offering definitive advice or interpretations outside the ESMA texts. This could present additional risks for firms making their interpretations from the available text.

    Complete and accurate reporting

    This is the simple demand from the regulators, but it is far from simple for firms to meet it. With the scale of the changes, nobody could justifiably expect implementation to be perfect. The industry was grateful for reassuring words from the FCA ahead of go-live that they could continue to work with the regulator to fully meet the requirements, provided that they could demonstrate that they had prepared well for implementation. However, there are now signs that the FCA might be less accommodating.

    In its mid-year industry forums, the FCA fired a warning shot that firms could expect a less tolerant attitude. They’d had six months to ensure their systems and controls were adequate to ensure complete and accurate reporting. We also see a danger in firms assuming that a reduced number rejected reports is an indication that their reporting is up to standard. Unfortunately, the validations only capture the tip of the iceberg of incorrect reports – there are a large number of valid but wrong reports submitted by firms.

    Data quality – round 2

    Basic validation can only capture basic errors and firms should be aware that all the NCAs are now starting to employ more intelligent ‘business rules’ to uncover reports that have passed validation, but are still incorrect. There is a temptation for firms to believe that it is “job done” for MiFIR transaction reporting now a year has passed by, but it is increasingly important that firms test the accuracy of their reports to the regulators and we are increasingly seeing evidence of this as the FCA has begun sending letters to firms pointing out errors.

    Regulators will also want to see evidence of reconciliation of their transaction reports. Firms need to be aware that this isn’t simply checking that their competent authority has received all the reports they have sent.  The requirement is clear; firms must ensure the details of the reportable trades they have made match exactly with those in the reports they have sent to the competent authority and that reports have been made for all the reportable trades.

    But…help is at hand

    Ensuring reports are complete and accurate is an extremely difficult task, not least because the rules and guidelines have become so extensive and so complex. Unfortunately, “difficulty” is not an adequate excuse for firms failing to meet the regulators’ demands and firms need to remember that the FCA has a strong track record of using sanctions, including fines, to encourage firms to submit complete and accurate transaction reports.

    At Kaizen, we provide quality assurance testing of all reportable data to identify incorrect transactions. We can also reconcile all trades in your books and records with data received by the regulator, identifying under and over reporting with matching on specific fields. Additionally, we deliver training on the reporting requirements and provide a control framework tailored to your business. Find out more about our ReportShield™ assurance service or contact us to find out how we can give you peace of mind in your regulatory reporting quality.

  • FCA data extract will now include transaction submission date

    Great news! The FCA has announced that from 15 December its data extract schema will include the transaction submission date.

    At Kaizen, we consider this to be very good news as it will now be possible to identify the latest version of the trade report. Instead of simply reconciling the accuracy and completeness against data from the ARMs, we will now be able to reconcile the data against the records held by the FCA. This makes it far easier for firms to be fully compliant with the obligations detailed in RTS 22 Article 15(3):

    “Investment firms shall have arrangements in place to ensure that their transaction reports are complete and accurate. Those arrangements shall include testing of their reporting process and regular reconciliation of their front-office trading records against data samples provided to them by their competent authorities to that effect.”   

    We look forward to substantially increasing our use of FCA-provided data samples for testing and reconciliation, providing confidence to firms that they are meeting their MiFIR transaction reporting obligations.

    For more information visit the FCA website.

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