Category: MiFID II Transaction Reporting

MiFID II transaction reporting is an obligation under the second Directive of the Markets in Financial Instruments Directive (MiFID) / Markets in Financial Instruments Regulation (MiFIR). A legislative framework instituted by the European Union (EU) to regulate financial markets in the bloc and improve protections for investors. Its aim is to standardize practices across the EU and restore confidence in the industry, especially after the 2008 financial crisis. Check out Kaizen’s insights into MiFID II transaction reporting.

  • Kaizen returns to Eurex Derivatives Forum 2026

    Kaizen returns to Eurex Derivatives Forum 2026

    Date: 25 and 26 February | Location: Congress Center Messe Frankfurt | Hear us speak: 13:40, 25 February in breakout room: Illusion 3

    We are delighted to be returning to Frankfurt for the leading European event focused on trading and clearing for derivatives across asset classes. 

    On Wednesday 25 February from 13:40, we hope you can join Matthew Vincent, Managing Director, Tim Hartley, EMIR Reporting Director and John Graham, Senior Director of Regulation, FIA for a deep dive session into Regulatory Reporting in Transition. 

    The regulatory reporting landscape is undergoing significant transformation, with firms expected to manage evolving requirements while maintaining high-quality, accurate submissions. This session will examine ESMA’s latest updates to EMIR and MiFIR reporting, focusing on both the practical challenges and the opportunities arising from these changes. In this session, speakers will:

    • Break down the latest ESMA updates, including key changes to EMIR and MiFIR reporting requirements
    • Explore the wider regulatory reporting landscape, focusing on implementation challenges, supervisory expectations, and data-quality considerations
    • Share practical and actionable insights to help firms prepare effectively for the upcoming changes and strengthen their reporting frameworks.

    You can find the team in the exhibit hall throughout.

    Redeem your free ticket using code: Kaizen-DFF

    Register

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

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

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

    Market Watch 81: Transaction Reporting Vulnerabilities

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

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

    Market Watch 82: Elevated Expectations on Remediation

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

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

    Recent enforcement actions

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

    Key take aways for firms resulting from the final notices

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

    Conclusion

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

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

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

  • EMIR, MiFIR, SFTR Reporting Core Training – new course dates announced

    EMIR, MiFIR, SFTR Reporting Core Training – new course dates announced

    We’re pleased to announce new dates for our CPD-accredited EMIR, SFTR and MiFID/MiFIR Reporting Core Training Courses which we are delivering remotely. 

    Developed and delivered by our regulatory specialists David Nowell (EMIR and MiFIR) and Jonathan Lee (SFTR), these popular half-day courses are also at a significantly discounted price for a limited time only!

    Click on the links below for more details and to book your place.

    Training is an integral part of the systems and controls that firms need to have in place around reporting. Despite the coronavirus pandemic, regulators have made it clear that they are monitoring the quality of regulatory reports closely. 

    If you have any questions about our training courses or for enquiries about bespoke options, please email our Training Team. 

  • LISTEN: Kaizen CEO Dario Crispini on The Regis-TR RoundUp podcast

    Tune in to Dario Crispini on Episode 4 of The Regis-TR RoundUp!

    Dario covers off his early days at the UK regulator, the FSA (now FCA) and the launch of MiFID reporting. He also discusses whether the EMIR Refit can really make EMIR an effective early warning system for global financial crises, and how to prepare for the delayed SFTR roll-out and the problems it could cause for both market participants and regulators.

    The podcast also highlights the incredible efforts of Kaizen’s James Deehan in rowing 3,000 miles across the Atlantic to raise money for the Teenage Cancer Trust.

    Click on the green arrow below to listen!


     

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

  • Post-Brexit regulatory reporting wish list: MiFIR transaction reporting

    Post-Brexit regulatory reporting wish list: MiFIR transaction reporting

    Wouldn’t you know it; you spend over three years planning and worrying about a hard Brexit, and in the end, right at the last moment, after all the sleepless nights, it doesn’t actually happen! Instead, we now have a nice 11-month transition period. While there may be no changes to the MiFIR, EMIR and, SFTR reporting regimes until 2021, now is a good time to think about what changes you would like to see in the UK reporting regimes at the end of the transition period. While it was assumed that there might be little change in an attempt to assure equivalence, the UK Chancellor’s assertion that he is seeking “outcomes based” equivalence rather than complete alignment appears to have left the door ajar for some sensible changes to the reporting regimes. Starting with MiFIR, here are my top ten suggestions for changes to the transaction reporting regime which we believe will make reporting more proportionate for firms without degrading regulator’s ability to use the data for the intended purposes:

    1. “Country of Branch ” fields

    Perhaps one of the forgotten drivers behind MiFIR transaction reporting is the monitoring of conduct of business. There are five MiFIR “country of branch” fields which the NCAs use to share data amongst each other to help ensure that they can monitor branch activities. At Kaizen, we have discovered that firms frequently have issues populating these fields correctly. Since there will be no systematic sharing of data between the UK and the EEA, there appears to be no regulatory requirement to persist these fields.

    1. “ToTV Opinion Paper”

    ESMA has used this paper to expand the reportable instrument set to include “OTC derivatives sharing the same reference data details as the derivatives traded on a trading venue” Understanding the reportable instrument set has caused firms enough problems without adding to the burden. This is a considerable addition involving the matching of attributes against the ANNA DSB to find potential ISINs and then comparing the attributes associated with these ISINs against FIRDS to see if the instruments are reportable. I do not believe this is proportionate and it can be argued that it is not consistent with the Level 1 regulation. It has to go.

    1. Basket and Index Derivatives

    Firms executing transactions in OTC basket derivatives have to populate the underlying ISIN field with all the ISINs that are traded on an EEA trading venue. For example, if they trade a pharmaceutical basket comprising 421 stocks of which 352 are ToTV, they first need to discover which are ToTV and then populate all of them in the underlying ISIN field. If they make a mistake with any of those ISINs, it will be rejected by the regulator. This is very onerous for firms and can be of very little value to the regulators. There is no information on the weighting, so the information cannot possibly be used by the regulators on a systematic basis.

    Additionally, any changes in the basket composition are not reportable. It is also questionable whether the reporting of an index is of any real value to the regulators as it is doubtful whether they hold the constituent and weighting data. Of course, it is possible to manipulate the index markets (see Flaming Ferraris) but this is likely to stand out like a sore thumb to the participants and should be reported through a STOR. It is very difficult for firms to know whether the OTC index derivatives are reportable as it only takes one of the index constituents to be ToTV and this information is difficult to source – it certainly isn’t on FIRDS.

    1. IPOs

    Under MiFID, we used to say that everything that was knowable about an IPO was contained in the prospectus, so it would not be proportionate to require the resultant transactions to be reported. I’m not sure what’s changed to justify their inclusion for MiFIR. The task has been made more difficult as it is possible that some of the ‘counterparties’ don’t have LEIs as they are not necessarily normal market counterparties. Of course, trades cannot be reported if the counterparty doesn’t have an LEI. To make things worse, reporting firms have often discovered that the ISIN of the IPO is not on FIRDS at the time of the IPO. As some trading venues have not reported dates when an application for trading was made, some IPO trades have been continually rejected.

    1. Trading Capacity

    In the UK, we understand ‘principal’ and ‘agency’; but we don’t always understand the distinction between the new MiFIR values of ‘dealing on own account’ and ‘matched principal’. However, many firms, particularly the buy-side, have discovered that brokers confirming transactions back to them as ‘matched principal’, causes immense difficulties. Additionally, you can describe the same back-to-back principal scenario to a number of firms and I believe 70% of them will report it as two ‘DEAL’ transactions and 30% will report it as a single “MTCH” transaction. If it doesn’t matter which method is observed, why have the element of grey in the first place? Let’s get back to trading capacity we understand (and that are used in other reporting regimes).

    1. Crazy Chains – transmission of order, INTC and individual funds

    I love the Guidelines document, I really do. However, there are times when I’m reading sections 5.26 (Chains and Transmission) and 5.27 (Investment firm acting under a discretionary mandate for multiple clients) that I find it extremely difficult to carry on reading. There are a couple of inconsistencies within these Guidelines which suggests they may not work quite as the regulators envisage. It is just too convoluted and transaction reporting shouldn’t be this difficult. Again, I think it is the buy-side that may suffer most from this and maybe it is an area where the FCA may want to simplify the requirements. For example, are allocations to funds really required when the fund manager reports with the identifier of the individual decision maker within the fund management company? Does the transmission of order indicator actually add any value for the regulator?

    1. Repos & Securities financing indicator

    Exactly what is the logic for requiring a securities financing transaction, such as a repo, to be reportable under MiFIR simply because it has been excluded under SFTR? How was that leap made? If RTS 22, Article 2 sets the precedent that SFTs aren’t reportable under MiFIR (because they cannot be deemed to be abusive) why was it felt necessary to add the proviso that they should be reported if the counterparty is a member of the European System of Central Banks. Simplify the regulation and remove SFTs from MiFIR transaction reporting completely.   

    1. Swaps

    Completing the technical standards and Guidelines was clearly a mammoth task for ESMA and it is inevitable that there would be time constraints. I believe this is particularly evident when it comes to the reporting of swaps. For example, it is questionable whether requiring the price of an equity swap to reflect the interest rate is sensible, as the price of the underlying reference security would appear far more valuable to the regulators in pursuing market abuse. In fact, why require the interest rate side at all – it is not required for CFDs or spread bets, which are essentially swaps anyway. As for the “swap-in” and “swap-out” indicator – does this really bring any value when rules for determining the ‘buyer’ and ‘seller’ are already set out in the regulatory text?

    1. Reference Data Requirements

    Where a reported instrument is not ToTV and is only being reported because the underlying instrument is ToTV, up to 15 additional reference data fields need to be populated to describe the instrument to the regulator. This has proved to be particularly difficult for firms. A lot of these fields are essential for the regulator to detect market abuse – the underlying instrument ISIN is a prime example. However, it is questionable whether some of the others deliver any value. For example, does the ‘instrument full name’ add value when all the details are contained in other fields. Are some of the fields duplicated in the CFI code (e.g. ‘option type’). Does ‘notional currency’ have any relevance for non-FX derivatives?

    1. Short Sell indicator

    This is very onerous for firms to populate correctly and maybe the cost benefit analysis of this field should be reviewed. If there is a permissible value for ‘information not available’ (for clients after acting on a ‘best efforts’ basis) then you have to assume that the overall quality of this information is questionable.

     

    These are my ‘just for fun’ top ten as there may be perfectly valid reasons why the regulators need this information. To be honest, they’re my initial thoughts and I haven’t even mentioned other contenders such as ‘net amount’, ‘waiver indicator’ and ‘OTC post trade indicator’.

    However, there is a serious element here. If there is an opportunity for the UK FCA to tweak its reporting regimes on the basis of ‘outcomes-based equivalence’ rather than alignment, the process needs to start immediately and firms need to feed into that process. Eleven months is not a long time.

    Forthcoming blogs will detail our wish lists for the EMIR trade reporting and SFTR regimes.

    For help with your transaction reporting accuracy or to discuss your own post-Brexit transaction reporting wish list with one of our regulatory specialists, please contact us.

  • FIRDS: Are trading venues contributing to poor quality transaction reporting?

    FIRDS: Are trading venues contributing to poor quality transaction reporting?

    Perhaps the biggest irony about MiFIR transaction reporting is that reports submitted by investment firms need to be complete and accurate, but ESMA states it cannot provide any guarantee that one of the key tools firms need to do this, the ESMA FIRDS reference database, is “complete, accurate or up-to-date”. This is particularly harsh on firms as they can report with the correct ISIN to identify the financial instrument, but if that ISIN (or underlying ISIN) is not on the FIRDS database within seven calendar days, then the report will be rejected by the competent authority. The onus is then on the firm to investigate whether they should re-submit the report.

    This is unfair on firms as most of them are trying to do the right thing by only reporting transactions in instruments that are reportable, but they are frustrated with limitations of ESMA’s FIRDS database. It would be easy to blame ESMA for this, but I believe that also is unfair. The quality of FIRDS can only ever be as good as the information submitted to it and it is the EEA trading venues that are obliged to submit this data through the requirements detailed in RTS 23. The quality of FIRDS data has improved dramatically since go-live, as you would expect over the course of two years, and many trading venues may be reporting perfectly. However, other trading venues are not, and deficiencies in this reference data was highlighted in Germany’s Ministry of Finance’s position paper on MiFID and MiFIR.

    Germany’s Ministry of Finance concludes that “ further analysis is needed on the question of how to ensure the provision of accurate, reliable and timely reference data. The analysis should also explore ways to make FIRDS the golden source for reference data.” Well I’m sure we all know the obvious answer to this one – there is nothing quite like a sanction, perhaps in the form of a fine and public censure, to ensure data quality is taken more seriously. We have seen sanctions used for firms’ poor transaction reporting and how this can focus attention, so maybe trading venues need to be wary of the possibility of sanctions if they don’t improve the quality of their reference data. If you are a trading venue that has doubts about the quality of its reference data, now might be a good time to look at quality assurance solutions.

    The quality of FIRDS data also impacts the thorny issue of the ESMA opinion paper on OTC derivatives traded on a trading venue. In this paper, ESMA expands the reportable instrument set to include “OTC derivatives sharing the same reference data details as the derivatives traded on a trading venue”. This paper has caused much consternation in the industry. Whilst some firms have paid as much attention to the opinion paper as a London cyclist does to a red light, many other firms are desperately trying to do the right thing in trying to match the reference data attributes of their OTC derivatives against the attributes of derivatives on the FIRDS database to see if they are reportable. The quality of the FIRDS data, and the flexibility of FIRDS itself, often makes this a frustrating and imprecise task. This appears particularly true for FX and interest rate derivatives and prompts the question (also asked by Germany’s Ministry of Finance) of whether the concept of ‘traded on a trading venue’ should be applied to OTC derivatives. Anybody who thinks it should, needs to try assessing whether some OTC FX swaps are reportable or not. They would probably find that they first need to match attributes against the ANNA Derivatives Service Bureau to find potential ISINs and then compare the attributes associated with these ISINs against FIRDS to see if the instruments are reportable (not forgetting to check if the underlying forwards have reportable ISINs). They may well struggle with the flexibility of FIRDS in this task and may possibly be perplexed by the quality of much of the data – for example, the lack of consistency between the financial instrument long name and the attributes, particularly the expiry date. 

    Whilst the MiFIR definition of reportable instruments appears easy on paper (MiFIR Article 26(2)), there is plenty of devil in the detail and many firms struggle to fully understand them. These firms are unlikely to understand the implications of the ESMA ToTV opinion paper and it does appear to be too complex a requirement for the associated regulatory benefit. The current data quality and flexibility of FIRDS does not seem fully adequate to support this requirement. More importantly, it appears that the quality of FIRDS reference data may be causing issues with the overall quality of transaction reporting. Whilst many trading venues are on top of the task of their RTS 23 reporting, it appears that some trading venues need to up their game to avoid regulatory attention.

    If you’re worried about the quality of your reported data, this is why we here at Kaizen exist. Our accuracy testing and reference data testing services check all data fields in every trade or transaction report submitted to the regulator so you have a full picture of the quality of your reporting.  Contact us for a discussion on how we can help. Join in the conversation over on our LinkedIn.

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

  • You better watch out, you better not cry….

    You better watch out, you better not cry….

    The worst Christmas present I ever received was a jar of mustard. To be fair, it was a large jar and it did come from Fortnum and Mason, but it was still a jar of mustard. And I don’t like mustard. What on earth was going through their minds when they thought this dodgy coloured and foul tasting condiment would be a suitable festive gift?

    Secret Santa?

    However, there are worse Christmas presents, especially if your Secret Santa this year was the FCA and you received a letter asking you to explain numerous errors in your MiFID II transaction reports. Many firms fail to appreciate that the FCA Santa really does know if you’ve been naughty or nice with your transaction reporting. It has systems designed to find errors in transaction reports and you will not be alone if you have received a letter from the FCA (as 223 UK investment firms have so far been contacted to explain reporting errors).

    Don’t panic

    Communications from the FCA can often cause alarm within firms, but they shouldn’t necessarily induce panic. The MiFID II transaction reporting requirements are extremely complex and we have discovered errors through the quality assurance testing we have performed for every firm. No NCA can sanction every firm when they find errors in their transaction report and nor do I think they would want to. However, they cannot perform their role of monitoring for market abuse unless they receive complete and accurate transaction reports. The UK FCA has now twice signaled in Market Watch newsletters that firms are making unacceptable errors in their transaction reports and its patience must be wearing thin. It is quite possible that they may be thinking of imposing further sanctions for transaction reporting breaches and, who knows, maybe there’s one going through the enforcement process as we speak.

    Put the right controls in place

    If you receive a less than cheery Christmas missive from the FCA, it is an opportune moment to consider whether you have adequate controls over your transaction reporting processes. We believe the FCA is far more likely to take a collaborative approach with firms if they can see that the firm is trying to do the ‘right thing’ – i.e. implementing the controls detailed in Article 15 of RTS 22. In particular, performing quality assurance testing and regular reconciliations of data within source systems with the reports sent to the FCA. If these controls are not in place, you’re far more likely to find yourself on Santa’s naughty step.

    If you don’t know if your reporting’s bad or good, please speak to us at Kaizen. We have a full suite of quality assurance and reconciliation solutions that can ensure that you are good for goodness sake…

  • €STR versus SONIA

    €STR versus SONIA

    The introduction of the new euro short-term rate (“€STR”) by the European Central Bank (ECB) in October caused potential issues for MiFIR transaction reporting and RTS 23 instrument reporting as there was no standardised four character code in RTS 22 or RTS 23 for the new benchmark rate. Fortunately, ESMA has addressed problem by creating a new four character code of ESTR for the index name and stipulating that the ISIN EU000A2X2A25 should be used to identify the index. Clearly this will be transformative in the number of successful market abuse cases brought by the regulators. ESMA details how these codes should be used for both RTS 23 and RTS 22 reporting in its December MiFIR Data Reporting Q&A.

    However, the ESMA guidance on €STR does highlight certain anomalies with the treatment of other interest rate benchmarks. For example, it’s the only interest rate where the ISIN also needs to be populated in the ‘Underlying Instrument’ code field. But perhaps the strangest anomaly is that there appears to be no equivalent treatment for the Sterling Overnight Index Average (SONIA). This was introduced in March 1997 and is used to value around £30 trillion of assets each year. SONIA derivatives are also traded on regulated markets, but there is no standardised four character code for this sterling interest rate benchmark and ESMA has not addressed this issue in the same way it has for the euro interest rate benchmark. It’s a similar story for EMIR, where the ‘ESTR’ code was added to the list of four character codes to identify floating rates, but no similar additional was made for SONIA. Why is this, I wonder? Answers on a postcard please…

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

  • SMCR: Five key questions to ask on regulatory reporting

    SMCR: Five key questions to ask on regulatory reporting

    The Senior Managers and Certification Regime (SM&CR or SMCR) goes live today for buy-side organisations and other solo regulated firms*. The regime has been in operation for the past few years for banks, building societies, credit unions and branches of foreign banks operating in the UK and the largest investment firms regulated by the PRA and FCA.

    Regulatory reporting controls, governance and ultimately sign off will be key to senior managers in these firms as they take on the additional responsibilities of SMCR. If this is you, what do you need to do from a regulatory reporting perspective? Here are five questions you should be able to answer:

    1. What category is my firm in?  You need to understand the three types of categorisation under the senior managers regime (Limited Scope, Core or Enhanced) and the certification regime, as well as the conduct rules that will apply to the rest of employees’ monitoring and auditing activities.
    2. Have my Senior Management Functions (SMFs) been properly trained? Most functions will be the same as under the previous Approved Persons Regime but have they been trained to understand the responsibility and consequences of their actions?
    3. Is our governance now in line with SMCR?  Are the right procedures & policies and controls in place for recording the implementations, steps and the decisions made by your firm to comply with the regulation?
    4. Have I mapped out my management responsibilities? Who is impacted (e.g. Head of Legal is not) and what Controlled Functions have transferred to SMFs?
    5. Am I protected? We have seen firms fined under various regulatory regimes such as MiFID and EMIR but there have been few penalties or consequences directly for the executives within those firms – yet. With SMCR making individual senior managers within firms accountable, our services can provide you with peace of mind that you have the right controls in place to meet your regulatory reporting requirements and reduce your regulatory risk.

    Join in the conversation over on our LinkedIn.

    More information: https://www.fca.org.uk/firms/senior-managers-certification-regime

    *These include investment firms – brokers, securities firms, asset managers, financial advisers.

  • Kaizen Reporting wins Regulatory Reporting Product of the Year

    Kaizen Reporting wins Regulatory Reporting Product of the Year

    FOR IMMEDIATE RELEASE

    27 November 2019, London: Leading regulatory reporting firm Kaizen Reporting, developer of the multi-award-winning assurance service, ReportShield™, announced today that it has won ‘Regulatory Reporting Product of the Year’ at the Risk Markets Technology Awards 2020. Hosted and run by Risk, the awards were set up in order to recognise market-leading technologies and third-party vendors that enable sell-side firms to operate more efficiently and transparently.

    The 2020 awards drew 180 pitches across nearly 30 categories and recognised companies that were able to demonstrate they had responded to the market’s changing needs. The winners were decided by a panel of nine global industry experts and two from the Risk.net editorial team.

    Dario Crispini, CEO of Kaizen Reporting, commented: “At Kaizen our aim is to transform the quality of regulatory reporting data through providing our customers with the best possible solutions when it comes to trade and transaction reporting. The continued enhancements and services we have introduced in the past year show our commitment to our customers and in retaining our reputation as an industry-leader in reporting services and RegTech solutions.”

    The award caps off a fantastic month of accolades for Kaizen. Yesterday it was announced it had been selected as one of the world’s most innovative RegTech companies for the second year in a row in the prestigious RegTech 100 listing. Earlier in the month, it was also recognised with the Regulation Asia award for Data Assurance in Singapore.

    Kaizen’s ReportShield™ is a set of services that act as a shield against reporting issues, helping investment firms to meet their reporting obligations and effectively manage their reporting risks. The service includes a number of controls required for complete and accurate trade and transaction reporting including Kaizen’s flagship accuracy testing, advanced regulatory reconciliation service and testing of reference data.

    (ends)

    For media inquiries, please contact Fiona Wilde on media@kaizenreporting.com or +44 (0) 20 3912 3271.

  • Kaizen Reporting “one of the world’s most innovative RegTech firms” for second year

    Kaizen Reporting “one of the world’s most innovative RegTech firms” for second year

    FOR IMMEDIATE RELEASE

    26 November 2019, London: Leading regulatory technology firm, Kaizen Reporting today announced that it has been selected for the RegTech 100 listing, an exclusive directory of the world’s leading RegTech companies, for the second year in a row. The RegTech 100 companies were chosen by a panel of analysts and industry experts as the world’s best solution providers that address the challenges and opportunities of dealing with regulatory issues within financial services.

    Chosen from a longlist of over 1,000 companies, Kaizen was selected for its innovative solutions for trade and transaction reporting. The company’s ReportShield™ quality assurance services combine regulatory expertise and advanced technology to deliver a full assessment of regulatory reporting quality.  Many financial firms use ReportShield™ to assess the quality of their data for reporting regimes such as MiFIR, EMIR, Dodd Frank, MAS, Canada and HKMA reporting as well as the upcoming SFTR regime.

    Dario Crispini, CEO of Kaizen Reporting, said, “We are delighted to have been included in the RegTech 100 list for the second consecutive year. Being listed again is a real honour and testament to our team here at Kaizen who have worked so hard to put us at the forefront of the RegTech sector.”

    Mariyan Dimitrov, head of research at RegTech Analyst, said, “Having reviewed over 1,000 RegTech companies from around the world, Kaizen Reporting stood out as a worthy contender for this year’s RegTech 100. The services they offer and their all-encompassing testing method allows clients to see the full picture of the quality of their trade and transaction reporting.”

    Kaizen’s ReportShield™ is a set of services that act as a shield against reporting issues, helping investment firms meet their reporting obligations and manage their reporting risks effectively. ReportShield™ includes a number of controls required for complete and accurate reporting including Kaizen’s flagship accuracy testing, advanced regulatory reconciliation service and reference data testing.

    Earlier this month, Kaizen was also recognised with a Regulation Asia Award for Excellence for Data Assurance in Singapore.

    (ends)

    For media inquiries, please contact Fiona Wilde on media@kaizenreporting.com or +44 (0) 20 3912 3271.

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

  • Kaizen Reporting Wins Singapore Regtech Award for ReportShield™ Data Assurance Solution

    Kaizen Reporting Wins Singapore Regtech Award for ReportShield™ Data Assurance Solution

    FOR IMMEDIATE RELEASE

    14 November 2019, London – Kaizen Reporting is delighted to announce it has won the Regtech Award for Data Assurance in the 2nd Regulation Asia Awards for Excellence 2019 at a ceremony in Singapore.

    Following a rigorous selection process involving a judging panel of subject-matter experts and the Regulation Asia editorial team, Kaizen Reporting emerged as the category winner for its ReportShield™ quality assurance solution, a set of services developed to solve the problem of poor quality regulatory reporting. The solution is unique in its all-encompassing testing approach which fully assesses the quality of data that firms have reported to the regulator.

    One judge called the service “one-of-a-kind”. Multiple users have attested to its effectiveness in helping to ensure higher quality data in regulatory reports. According to one user, regulators have also provided “extremely positive” feedback on the data assurance processes applied.

    Ian Rennie, Managing Director of Kaizen Reporting (pictured) said, “We are honoured that Kaizen has been recognised in the Regulation Asia Awards for Excellence. Complete and accurate regulatory reporting is expected by regulators across the region and globally and we are delighted that our automated testing services are helping clients meet regulatory expectations and providing them with peace of mind in their reporting quality.”

    Brad Maclean, Co-founder and Executive Chairman, Regulation Asia said: “Kaizen Reporting has developed a unique solution to address a wide range of issues around regulatory reporting. This award recognises the firm’s continued success in developing superior technology and helping firms navigate challenging data environments and ever-changing regulatory requirements.”

    Earlier this year Kaizen Reporting was also awarded Best Reporting Platform or Service for the Sell side at the Sell-side Technology Awards in London and Best Technology Provider for Regulatory Compliance by the Fintech and RegTech Global Awards. In 2017, Kaizen’s testing was recognised by the UK government with the Queen’s Award for Enterprise for innovation, one of the UK’s highest business accolades.

    About Kaizen Reporting

    Kaizen Reporting are regulatory reporting experts on a mission to improve the quality of reporting in the financial services industry. Kaizen has combined regulatory expertise with advanced technology develop its multi-award winning ReportShield™ quality assurance services which are unique in providing full visibility of reporting quality. Kaizen’s services are used by some of the world’s largest banks, asset managers, hedge funds and brokers. Whether it’s MiFIR, EMIR, MAS, HKMA, ASIC, Dodd Frank, SFTR or another G20 regulation, Kaizen helps its clients reduce costs, improve quality and increase confidence in their regulatory reporting.

    About the Regulation Asia Awards for Excellence 2019 

    Regulation Asia Awards for Excellence recognises technology companies, legal and consulting firms, and exchanges that have shaped the regulatory landscape in Asia Pacific, as well as outstanding technology projects both in mature and emerging markets by large tech firms and innovative startups that help meet the requirements of a specific regulatory change infrastructure. For a full list of award winners, visit www.regulationasia.com/awards.  

    For more information, please contact Fiona Wilde, Head of Communications, on +44 (0) 203 912 3271 or media@kaizenreporting.com

     

     

  • Look before you leap: Understanding the limitations of AI in the regulatory space

    Look before you leap: Understanding the limitations of AI in the regulatory space

    Last week I went to the Commodity Future Trading Commission (CFTC) in Washington DC to attend the Fintech Forward 2019 conference. I was grateful for the opportunity to speak on a panel about AI in the 21st Century Marketplace: Exploring the Role of AI and Related Fintech in CFTC Markets.

    Artificial Intelligence (AI) is an exciting tool that has shot to prominence in the last few years, with applications spanning the gamut from Snapchat filters and Spotify recommendations to sophisticated systems that catch fraudulent transactions or see the signs of lung cancer before expert radiologists. But how will AI impact the regulatory compliance space?

    AI and data quality: don’t get too excited

    At Kaizen we’re primarily concerned with helping firms check the data quality of the transaction reports that they have to submit under a variety of régimes from around the world such as MiFIR, EMIR and the Dodd-Frank Act. We have to be careful not to be too optimistic about the role AI can play in this. AI is most useful when we don’t exactly know the logic that a computer programme should be following, so we need the AI to ‘learn’ it from the data. But with regulatory reporting, the rules are clearly laid out – meaning that rule-based “expert systems” are the right technology for testing reports.

    Yet, despite the seemingly straightforward nature of accurate reporting, at Kaizen we’ve found that firms can commonly make errors in as many as 90% of records. Firms should be wary of “running before they can walk” by increasing the complexity of their reporting pipelines with AI while they are still making basic mistakes setting up their reporting systems.

    But AI can help with market integrity

    Where AI can really come into its own in regulatory compliance is market integrity – particularly safeguards against market abuse such as insider trading. Under the Market Abuse Regulation firms are required to monitor, detect and report suspicious transactions that take place on their platforms. Unlike with regulatory reporting, there are no hard-and-fast rules of what abusive trades look like. This is where the power of AI and machine learning (ML) can be brought to bear, learning how to find the anomalous needles in the gargantuan haystack of reported transactions.

    AI goes rogue

    At FinTech Forward I also commented on challenges that AI might pose for regulators and market participants. One big challenge regulators may face is the question of accountability: who is to blame if an AI ‘goes rogue’? The notion of a super intelligent AI that understands its actions still belongs in science fiction; contemporary AIs are really just mathematical models that extrapolate patterns, so the idea of holding an AI responsible itself is silly. It isn’t only the programmers who determine how an AI will behave; the AI can be heavily influenced by matters like what data fields the AI can ‘see’, what training data is in scope, and what metric for success the AI will use. Fundamentally, accountability for an AI need not be different from any other automated computer system.

    The challenges of algorithmic bias

    Another challenge for regulators is the issue of algorithmic bias – when an AI can behave unfairly in a systematic way, due to unintended problems with the training data or the question that was posed. One famous example is a recruitment AI that Amazon scrapped because it was unintentionally disfavouring women. Regulators that use AIs for enforcement have to be careful to minimize algorithmic bias. It isn’t only individuals who might get caught up. As a hypothetical example, if regulators only trained their AI on data from Tier 1 investment banks then they might end up unfairly over-flagging transactions from hedge funds.

    Black box models

    One problem for market participants who deploy AIs is the lack of interpretability for “black box” models. State-of-the-art AIs can have millions of parameters and it’s impossible to know what they’re doing, and this means it can be hard to quantify the risks. Moreover, the inherently adversarial aspect of market participation means that AI complexity is more of a risk than it would be in collaborative contexts such as self-driving cars – a counterparty’s AI might learn to persuade a black box AI to misprice securities, for example. Few market participants deploy AIs without a human in the loop.

    In the future, we’ll see AI play an ever increasing role in our lives, including finance and regulation. But as long as the technology is still in its infancy it’s important to temper the hype by understanding the limitations. Deploying AI systems has the potential to add huge value, but as always, firms should look before they leap.

    Watch Sam in action at Fintech Forward 2019.

  • 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 and Chris Machin speak to FOW

    In the news: David Nowell and Chris Machin speak to FOW

    Our Senior Regulatory Reporting Specialists David Nowell and Chris Machin recently sat down with James Thursfield from FOW to discuss the results of the German Ministry of Finance industry consultation. The article highlights the need for a golden source for reference data and the role of the FIRDS database.

    “The regulators are well aware of deficiencies with the FIRDS reference data and already state that it cannot be relied to be complete, accurate and up-to-date,” Nowell told FOW. 

    “Esma has always, even before go-live, stated that they would not be the Golden Source (even if de-facto they actually are) and no solution has been suggested,” Machin said.

    Read the full interview.

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

  • MiFIR versus EMIR – which is the most important reporting regime?

    MiFIR versus EMIR – which is the most important reporting regime?

    There are many similarities between the MiFIR transaction reporting and EMIR trade reporting requirements. Both are T+1 reporting regimes and there is a large overlap in the instrument set that they cover. However, there are distinct regulatory drivers behind each regime: MiFIR transaction reporting is primarily used to detect market abuse whilst EMIR trade reporting is used primarily to monitor for systemic risk.

    There is no doubt that combating market abuse is a very important regulatory service; everybody benefits from clean markets. Complete and accurate transaction reports are vital to help the regulators perform this task effectively. However, systemic risk is even more important as it represents the risk of collapse of the entire financial system -there is no point monitoring for market abuse if the financial system has collapsed around you.

    It is very interesting therefore to compare the number of errors and omissions forms for MiFIR breaches against the number of equivalent forms for EMIR trade reporting breaches. Statistics from the UK Financial Conduct Authority (FCA) obtained through a Freedom of Information Act request show that it received notifications from 384 firms MiFIR transaction reporting breaches since go-live compared to a paltry 75 for EMIR trade reporting in the period since Q2 2018 when the EMIR breach form became available. So, it is tempting to believe that firms recognise the relative importance of EMIR trade reporting and are making greater efforts to ensure the accuracy of data they report. Sadly, this is not the case. At Kaizen, we perform data quality checks on firms’ transaction reports and trade reports. For EMIR we initially find that a much lower number of EMIR trade reports are accurate than compared with the MiFIR reports we test. This reflects the complexity of the reporting regime, but we find firms’ reporting quality rapidly improves once we have highlighted and explained the errors to them.

    So this presents an apparent anomaly. The evidence suggests the quality of EMIR trade reports is at a lower level than the quality of MiFIR transaction reports, yet over five times as many firms have notified the FCA of MiFIR transaction reporting errors than they have for EMIR trade reporting. It is not difficult to understand why this is the case; the FCA is constantly reminding the industry on the need to notify them of MiFIR transaction reporting breaches, and to correct those errors, but it appears to be comparatively silent on the need to notify them of EMIR reporting breaches. What is more difficult to understand is why the FCA appears to be less active in meeting its G20 commitments in ensuring the same level of high quality in EMIR trade reporting data.

    If you’re concerned about the quality of your MiFIR transaction reporting data or EMIR trade reporting data or would simply like confirmation that it is accurate and complete, please get in touch for a complementary consultation with one of our regulatory experts.

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

  • FCA insight into Transaction Reporting Feedback

    At the Infoline Trade and Transaction Reporting Conference in London this week the audience were on tenterhooks for the latest update from Ana Fernandes, MRT Manager at the FCA. We thought we would share some insight from the statistics and issues she highlighted:

    Statistics

    • There are over 8.7bn records in the FCA’s Market Data Processor (MDP)
    • There are 23 submitting entities
    • Approximate 7,900 executing entities under ESMA, 3,000 of these are UK firms
    • Over 300,000 LEI’s and over 6.7m National Identifiers
    • FCA has received 1,335 notifications of errors from only 394 firms
    • 20 thematic investigations have been completed
    • 130 firms have been contacted by the FCA
    • FCA have only seen 405 requested and downloaded sample Transaction Reports in 2019

    There was a definite concern on the low numbers of submissions and an encouragement for firms to come forward asap and ‘promptly notify’ as per stated in Article 15(2) of the RTS 22.

    Issues seen by the FCA

    • GMT vs BST (a candid reminder to firms that clocks do change twice a year!)
    • Major vs Minor currencies
    • Price Zero vs NOAP
    • Buyer vs Seller
    • Misreporting of National Identifiers
    • Wrong Buy/Sell with Trading Capacity
    • Inconsistent TV TIC by Trading Venue
    • Use of default trading times

    Food for thought especially as mentioned before, by my colleague David Nowell, that these are still the same issues that firms were fined for as seen under MiFID I. These facts and issues evidence that the FCA are actively pursuing policy and detective activities in order to identify data quality issues. These are issues Kaizen testing is designed to highlight to our clients. Get in touch to discuss the accuracy of your trade and transaction reports. 

  • FCA publish Market Watch 59

    FCA publish Market Watch 59

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

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

    Valid but incorrect reports

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

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

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

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

    Instrument Reference Data

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

    Errors and omissions notifications forms

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

    How Kaizen can help

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

  • 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

  • Second fine for transaction reporting breaches in two weeks is a record £34.3m

    Second fine for transaction reporting breaches in two weeks is a record £34.3m

    The FCA has issued a record fine of £34.3m for incorrect transaction reporting, hot on the heels of a fine two weeks ago for similar breaches. 

    According to the FCA, the firm in question failed to provide accurate and timely reporting relating to 220.2 million transaction reports between November 2007 and March 2017.

    If any firm doubts the FCA’s resolve in its pursuit of complete and accurate transaction reporting, they need to take note of these fines and the accompanying warning from Mark Steward, the FCA’s Director of Enforcement:

    ‘The failings in this case demonstrate a failure over an extended period to manage and test controls that are vitally important to the integrity of our markets. These were serious and prolonged failures. We expect all firms will take this opportunity to ensure they can fully detail their activity and are regularly checking their systems so any problems are detected and remedied promptly, unlike in this case.’

    The two recent fines are almost double the amount of the previous 12 fines for MiFID reporting combined.

    What went wrong?

    The FCA’s Final Notice tells a very familiar tale of what happens when a complex organisation, acting in good faith, attempts to deliver upon these very complex regulatory obligations; a significant, material, and widespread set of issues left undetected for many years.

    The key message is that these errors result from inadequate systems and controls over transaction reporting. In particular, the FCA found issues with:

    1. Change management
    2. Accuracy and completeness controls – again signalling issues with an approach that only tests data samples
    3. Reference Data – identification of counterparties

    The FCA is evidently tired of sounding like a broken record as these three control issues continually result in transaction reporting failings. The message should be familiar to firms and their SMCR managers responsible for reporting.  It’s not a secret that if firms don’t test the accuracy of their reporting, don’t test their reference data and change management processes, and don’t have adequate reconciliation from front office systems to the reports received by the FCA, then they cannot have confidence their reporting is correct.

    Lessons for MiFIR transaction reporting

    It is important to note that both fines are for failures under the previous MiFID transaction reporting regime. It is possible that this now marks the end of sanctions for the MiFID reporting regime and that the FCA’s focus will turn to the MiFIR reporting regime which is considerably more complex than the MiFID reporting regime. The FCA has already warned about the unsatisfactory quality of some transaction reporting under the new regime and the potential future consequences. There are many more things that can go wrong under the new regime and it is essential that firms are confident that they have adequate controls over their transaction reporting. Firms need to take note that the reference period for this fine’s transaction reporting breaches started on 5 November 2007 – the very first day of the MiFID transaction reporting; no grace period. 

    Get peace of mind in your reporting quality

    Our blog about the fine two weeks ago asks ‘could it have been you?’ and if you have any doubt, it is important to act now.  These two fines should be a wake up call for senior managers to get their reporting controls up to standard – and fast. This is exactly what we here at Kaizen exist to do.  We have a proven track record in helping firms tackle their trade and transaction reporting issues and risks head on – and helping them to avoid censure whether it is for MiFIR, EMIR, Dodd-Frank or another G20 regulation.

    Our ReportShield™ quality assurance service marries our regulatory expertise with data science, and uniquely tests every single record at source avoiding the pitfalls of testing only a sample of data.  The service includes everything you need for reporting assurance including a bespoke control framework, quality assurance testing, reference data testing, advanced reconciliation and training. Please contact us for a discussion with one of our regulatory experts to find out how we can give you peace of mind in your reporting quality. 

  • FCA MiFID reporting fine – could it have been you?

    FCA MiFID reporting fine – could it have been you?

    Many firms were wondering when the first fine for MiFIR transaction reporting breaches would be levied by the FCA, so it might have come as a surprise to see a fine for a breach under the previous MiFID transaction reporting regime. We have seen strong signals from the FCA that it is disappointed with quality of some of the transaction reports it receives and it has been tireless in explaining that complete and accurate transaction reports are essential to monitor for market abuse effectively.

    Tough line

    Despite these warnings, some might have been thinking that the FCA was too occupied with Brexit to take enforcement action for transaction reporting breaches. The latest fine, at £27.6m after a 30% early settlement discount, is over twice as large as the previous fine for MiFID transaction reporting and should leave firms in no doubt that the FCA will continue to take a hard line with reporting breaches of both the MiFID and EMIR variety.  Many may be left considering what they should be doing to make sure they’re not the next subject of enforcement action.

    What failings did the FCA identify?

    Purely in terms of numbers, between 5 November 2007 and 24 May 2017, the firm:

    1. Failed to report 3,658,423 transactions;
    2. Inaccurately reported 83,074,015 transactions, and
    3. Erroneously reported 49,152,274 transactions.

    These look like very large numbers, but they have to be taken in context: In the period in question approximately 1.8 billion transactions were reported. This implies that the FCA didn’t raise any issues for approximately 1.665 billion transaction reports, or 92.5% of the submitted reports. It would be interesting to know how many senior managers are confident their firm is reporting more than 92.5% of its transactions correctly. Of course, they should be aiming for 100% complete and accurate reporting, but it is possible that many senior managers don’t actually know their accuracy rate.

    Systems and controls

    Of course, it isn’t just a numbers game. The accompanying Final Notice highlights a lack of sufficient systems and controls. In particular, the FCA stated there was a breach of Principle P3 by:

    1. Failing to have adequate systems and controls to ensure that reference or ‘static’ data used for various mandatory fields in the transaction reports submitted to the authority were complete and accurate;
    2. Failing to have in place adequate change management controls to manage changes affecting transaction reporting processes and systems, and
    3. Failing to undertake appropriate testing to ensure the completeness and accuracy of transaction reports.

    It is particularly interesting to note the criticisms in the Final Notice of the control framework calling out that it “did not adequately test and reconcile the completeness and accuracy of all transaction reporting data from its front office systems to the ARM reporting to the Authority.”

    Lessons to be learned

    The obvious lesson is that the FCA is actively enforcing transaction reporting. If your firm does not have adequate systems and controls in place or doesn’t even know how good (or bad) its reporting is; you could be at risk.

    Interestingly, in reference to the weakness of the reconciliation and testing controls, the notice called out the “periodic, sample based” nature of them. The limitations of sample testing and the false confidence that it provides has been one of the root causes of many a fine. At Kaizen, we provide quality assurance testing on all transaction reports and our reconciliation service tests all trades in the front office systems, determines whether they should be reported, and only then reconciles against the reports submitted to the regulator. We can also advise on the control framework, test all reference data (including ISINs, counterparty LEIs and for natural persons) and provide training on the regulatory requirements.

    Firms need to react

    When issues are identified by the FCA the clock is ticking. Firms should take any issue identified by the FCA as a trigger to not only investigate the issue raised but to look across all of its reporting to make sure it is correct. Flushing out issues quickly is critical in maintaining the confidence of the FCA. The industry is littered with examples of firms that have completed reviews and improved procedures only to have issues found many months and sometimes years later.

    Senior Managers liable

    The Senior Managers and Certification Regime (SMCR) has increased the reporting risks by making senior managers personally liable for transaction reporting controls.  The SMCR is soon to extend to all core firms at the end of the year.  Firms and their senior managers need to examine the systems and controls they have over transaction reporting and ask themselves whether they truly understand whether they are meeting the FCA requirements or whether they could be potentially next in line for enforcement action.

    If you have any doubts whether your reporting and controls are up to the required standard, we can help.  We have a proven track record in helping firms tackle their transaction reporting issues and risks head on – and helping them to avoid censure.Our ReportShield™ quality assurance service provides everything you need for reporting assurance including a bespoke control framework, quality assurance testing, reference data testing, reconciliation and training.  

    Please contact us for a discussion with one of our regulatory experts to find out more.

  • Kaizen’s reaction to the £27.6 million fine issued by the FCA for incorrect reporting

    Kaizen’s reaction to the £27.6 million fine issued by the FCA for incorrect reporting

    Our Senior Regulatory Reporting Specialist, David Nowell, commented on the £27.6 million fine issued by the FCA today for breaches under the MiFID reporting regime:

    “Many may be surprised that the FCA should levy such a large fine for breaches under the previous MiFID reporting regime. However, it is a clear sign of the FCA’s tenacity and determination to strive for complete and accurate transaction reporting. It is also a message that could strike fear in the hearts of many senior managers as the new MiFIR transaction regime is far more complex than the previous MiFID regime. The requirement for adequate systems and controls over transaction reporting are clearly set out in Article 15 of RTS. Having a strong governance framework, regular reconciliations, quality assurance testing, and reference data testing are key elements in meeting these requirements. The FCA has been clear and consistent in its demands for complete and accurate transaction reporting; this latest fine is a strong and timely reinforcement of this message.”

    For accurate and complete reporting please contact us.
    For media inquiries, please contact Fiona Wilde on media@kaizenreporting.com or +44 (0) 20 3912 3271.

     

  • White Paper – Brexit can damage your MiFIR transaction reporting and EMIR trade reporting

    White Paper – Brexit can damage your MiFIR transaction reporting and EMIR trade reporting

    UPDATED – 19 February 2019

    As we get closer to the withdrawal date, we have seen a flurry of statements from ESMA and the FCA on the impact of a hard Brexit on MiFIR and EMIR reporting obligations. As a result, we have revised our Brexit White Paper to take account of the recent statements.

    One of the most interesting developments was the statement from ESMA that EMIR trades and positions submitted to an EU trade repository by a UK counterparty would not need to be modified or updated post 29 March. The onus will be on the trade repositories to terminate these reports in the event of a hard Brexit. Before UK firms start celebrating, it should also be noted that these trades and positions could be ported to the newly established UK trade repositories and it is expected that firms will have to update and modify these trades as per usual. In effect, it is quite a seamless solution for firms and regulators alike. 

    As we’ve all discovered, Brexit is a fantastic opportunity to upset friends and family by sharing our expert views on the subject.

    Unfortunately, it will also have a profound effect on MiFIR transaction reporting and EMIR trade reporting.

    If there weren’t enough things to consider, we need to assess the impact it could have on branches, delegated reporting, outstanding trades, reportable instruments and personal data standards, just to name a few.

    Whilst it is tempting to bury our heads and wait for it all to blow over, the sad fact is that the impact on reporting could be brutal.

    We recommend that you put on your tin hats, batten down the hatches and prepare for a bumpy ride. What better way to start than reading our revised White Paper on the potential impact Brexit could have on your reporting? 

  • Valid but wrong: FCA warns on MiFIR transaction reporting data quality

    Valid but wrong: FCA warns on MiFIR transaction reporting data quality

    Senior Managers will not need a crystal ball to predict what will happen when the first MiFID II enforcement case is completed…

    In a speech on 7 February, the FCA’s Head of Market Policy, Stephen Hanks, warned about the unsatisfactory quality of some transaction reporting and the potential future consequences. The FCA stated that it was “particularly disappointed” to see fundamental errors in transaction reports that would have been incorrect under the previous MiFID reporting regime, let alone the far more complex MiFIR reporting regime.

    To demonstrate this type of error, the FCA noted that it was seeing zero in the price field in many reports. This is a classic example of what we call the “valid but wrong” problem. A zero price will pass the ESMA validation, but that doesn’t make it correct – we would only expect a zero price to be seen in exceptional cases, such as certain swap contracts where the spread is zero.

    The FCA also warned that just because there has been no enforcement action so far under MiFiD II, it doesn’t mean that it is happy with how firms have met the MiFID II requirements. Of course, formal sanctions are not the only tool at the FCA’s disposal and many firms have discovered how problematic remediating transaction reporting failures can be when issues are discovered. At Kaizen, we recommend four key areas that firms need to focus on to avoid the worst of the FCA’s wrath:

    1. Accuracy Testing
      • Quality assurance testing of all reportable data to identify incorrect transactions, using independent sources of data where possible
    2. Reconciliation
      • Reconcile all trades in your books and records with data received by the regulator
      • Note that the RTS 22, Article 15 reconciliation requirement includes “checking the timeliness of the report, the accuracy and completeness of the individual data fields and their compliance with the standards and formats specified in Table 2 of Annex 1”
    3. Reference data testing
      • Testing of counterparty and instrument static data for accuracy and completeness
    4. Control Framework
      • A risk and accountability framework tailored to your business
      • Process documentation, steering groups, training and remediation process.

    There is no need to have a crystal ball to understand what will happen when the first fine is issued under MiFID II. Senior management teams (which now include the SM&CR Manager responsible for transaction reporting) in organisations large and small will know exactly how well placed their organisation is in terms of judging the data quality of their reports. The call will go out to Compliance, Operations, Business and IT teams to run an immediate and urgent review of controls and data quality. This takes up valuable management and SME time and firms often don’t end up with the full picture. This is the typical response of firms who have not put in place effective controls and emphasises the need to be proactive and get these controls operational.

    At Kaizen Reporting, we have a team of specialist regulatory experts and data analysts delivering excellence on each of these four transaction reporting assurance requirements. Contact us to find out more about how we can give you peace of mind in the quality of your regulatory reporting and keep you on the right side of the regulator.

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

  • Another year of significant growth, success and development for Kaizen

    Another year of significant growth, success and development for Kaizen

    FOR IMMEDIATE RELEASE

    17 December 2018, London: Leading regulatory reporting firm Kaizen Reporting, developer of the multi-award-winning assurance service, ReportShield™, has rounded off a successful year of exciting expansion, both of its specialist team and its services, consolidating its market-leading reputation. With several influential senior hires, the launch of a tailored, expert-led regulatory reporting training service and numerous prestigious award wins, Kaizen has continued to set itself apart at the forefront of the industry.

    Kaizen began the year with a significant partnership with challenger consultancy Elixirr to deliver a complete end-to-end regulatory reporting remediation service for financial institutions, a much-needed partnership for responding to increasing levels of complexity in market regulations.

    This was followed with the hiring of two senior staff: the former chair of the ICMA taskforce on SFTR, Jonathan Lee, and the former regulator and EMIR and MiFIR expert, David Nowell. The addition of two highly-respected regulatory veterans further consolidated Kaizen’s position as market leader, bringing clients even greater assurance services for EMIR, MIFID II transaction reporting, Dodd-Frank and SFTR.

    Kaizen continued to win awards, and in December ReportShield was named ‘Best New Regulatory Reporting Product’ by the FOW International Awards. It was also one of a select group of companies chosen to exhibit at the fourth annual FIA Innovators Pavilion in Chicago, launched to showcase forward-thinking solutions for the global derivatives market. In addition, Kaizen was listed in the RegTech 100, a global directory of companies providing the most innovative solutions in regulation.

    Earlier this month Kaizen announced an expansion of its MiFIR offering, adding APA trade reporting. At the same time Chris Machin, a MiFIR trade reporting specialist, joined Kaizen to head the development of its new service.

    Dario Crispini, CEO of Kaizen, commented: “Our successes in 2018 are down to the commitment and innovation of our fantastic team here at Kaizen. We have doubled our client base and increased the staff numbers supporting our clients by a third. We have made even greater strides towards solidifying our position as the leading regulatory assurance provider. It’s not only a testament to our hard work, but also to the value of the service we are delivering to our clients.”

    “Our successes in 2018 are down to the commitment and innovation of our fantastic team here at Kaizen”

    Ian Rennie, Managing Director of Kaizen, added: “What I think has particularly differentiated this year from previous years is the expertise we have brought on board in the form of Jonathan, David and Chris. We now not only offer an unrivalled service across more regimes but also the specialist expertise from well-known players in this space, bringing even more peace of mind to our clients.”

    Dario continued, “Looking ahead to 2019, we will see regulators increasingly focus on the quality of data being reported for MiFID II, EMIR, Dodd-Frank and other G20 regulations. For MiFID II in particular, the UK regulator, the FCA, is already writing to firms to warn them about improving their data quality. We will also see the extension of the SMCR regime which will put further pressure on senior individuals within financial institutions to ensure their reporting is accurate and complete. And now that the regulatory technical standards have been approved, preparation for SFTR reporting will also increasingly demand time and focus from financial institutions. Putting the right controls in place at an early stage will result in compliant and efficient reporting from go-live”

    ReportShield is a set of services that help financial firms meet their reporting control obligations and effectively manage their reporting risks.  The service includes Kaizen’s award-winning accuracy testing which is unique in its ability to test all reported data, providing firms with full visibility of the quality of their reporting.

    (ends)

    For media inquiries, please contact Fiona Wilde at communications@kaizenreporting.com or +44 (0) 20 3912 3271.

  • Deep into the soul of regulatory reporting in 2018

    Deep into the soul of regulatory reporting in 2018

    We look back at the regulatory reporting year that was through the songs of Aretha Franklin (sorry Aretha).

    We saw yet another true legend sing her last note this year as the world stood United Together and said a fond farewell to the awe-inspiring Aretha Franklin. We apologise to any fan and most importantly to the great lady herself as we look back at the key regulatory reporting developments of 2018 through her songs and lyrics. I am afraid we have not learnt from our 2016 Bowie travesty….

    MiFIR transaction reporting go-live

    This time last year many of us were running through go-live lists rather than Santa lists and thinking, “I’m going to Drown in my own Tears“. However all that hard work did pay off and all involved deserve their very own Dr Feelgood feeling for their efforts. On the whole, firms got across the line despite the headwinds that presented themselves in the form of instrument data issues (FIRDs / DSB teething issues, understanding TOTV implications, identifying reportable indices), missing LEIs, rogue validation rules at ARMs and the regulator (to mention just a few).

    Though what January really signaled was the beginning of the journey and not the end. Firms’ efforts in the first months of the year were focused on reporting as much of their business as possible and dealing with the inevitable spike in validation breaks from the ARMs and competent authorities. Now the equally hard part of putting in controls to comply with RTS 22 Article 15, to check that what is reported is accurate and complete, before the regulator does, is the new priority.

    ESMA has been very busy

    We always say that regulatory reporting is the gift that keeps on giving, but ESMA can be a little like your eccentric Aunt Vera in delivering something you didn’t ask for and didn’t really want. Well, Vera has certainly been busy this year.  We had new iterations of the EMIR Q&A from ESMA on 12 July and 26 July. And since MiFIR reporting went live on 3 January, we had updates to the Q&A on 25 May and 26 September and some tweaks to the validation schemes as well.

    To be fair to ESMA, we haven’t had the avalanche of information overload we experienced in 2017 and the Q&A mechanism is an essential tool to help bed-down the new reporting regimes so we are Willing to Forgive. Whilst change can often be painful, you can always rely on Kaizen to ensure our ReportShield™ testing reflects the very latest gift from ESMA to keep you One Step Ahead.

    The FCA and SMCR

    When it comes to the Senior Managers and Certification Regime (SMCR) regime it is plain for all to see that the FCA is expecting firms to demonstrate some Respect. In the coming year, the regime will be extended to the core SMCR firms under which an individual within a firm will be ultimately responsible for ensuring that a firm complies with the conduct rules and expectations. Being able to evidence their firm’s reporting is accurate and complete will be a key demand from those who hold this responsibility.

    SFTR

    Having published its Final Report: Technical Standards under SFTR and certain amendments to EMIR back in March 2017, ESMA and the market anticipated that by December 2018 this would be a live reporting regime for investment firms and credit institutions (banks). All that was needed was European Commission endorsement and the legislative steps that follow….

    The European Commission had a Think and after 15 long months eventually piped up I Knew You Were Waiting in late July 2018, albeit with a long list of proposed amendments; largely semantics. Unfortunately, the Commission also decided that A Change is Gonna Come in reference to the rights that ESMA claimed to govern UTI and branch LEI standards endorsement. They left it with ESMA, Call Me.

    ESMA responded to the proposed amendments in September 2018, but unfortunately, it was not with Amazing Grace but rather a dismissive ‘Non,’ rejecting all the changes. The ball is now firmly in the European Commission’s court and as for the bickering, we’re sure It Hurts like Hell but to date, they have not yet found a Bridge Over Troubled Water and endorsed a final RTS for European Parliamentary and Council scrutiny. May the market sing Oh Happy Day when ESMA and the EC stand United Together and we get some certainty over the timing of SFTR go-live.

    Trade reporting and Jumpin’ Jack Flash

    So quite like Jumpin’ Jack Flash, trade reporting for MiFIR started on 3 January 2018 like a cross-fire hurricane with levels of uncertainty and clarity over different aspects of the regulation and the whole market frowned at the crumbs of a crust of bread at the quality of data.

    Firms howled at the morning driving rain with the barrage of Q&A updates throughout the year but as mentioned previously, this has certainly helped bring clarity to many grey areas within the regulation.  DVC, LEI and SI regime delays helped investment firms that felt drowned, washed up and left for dead by the various regulatory demands placed on them.

    What does 2019 hold for us?  The derivatives systematic internaliser regime. Could we start to see a penalty or sanction regime set out by ESMA and the NCAs which could leave investment firms crowned with a spike right through my head?  Questions still do remain though as to whether transparency and a level playing field has really been achieved…

    A view from across the Atlantic

    The CFTC has also been busy in 2018. Two White Papers published suggest that in these Ever Changing Times it is necessary to refresh the Dodd Frank(Iin) Act.

    The first paper, ‘Swaps Regulation Version 2.0’ sets out new proposals to change reporting to a T+1 model and bring in more detail to collateral data requirements. The second paper, which had us singing Border Song, sees The Weight of regulatory burden somewhat lifted for non-US entities where risk is sufficiently monitored by their home regulations.

    No official new rules or timeline has been given yet but we hope the CFTC will Get It Right when legislation is published. We’ll work with our clients to Jump To It and make the necessary preparations when the time comes.

    Brexit – I say a little prayer

    As we approach the end of the year the shadow of Brexit looms large for everyone.  We will share our thoughts on the impact on reporting early in the New Year but in the meantime, season’s greetings from all of us at Kaizen and we wish you a restful break with your family and friends. We thank you for your continued support and we look forward to helping you feel Rock Steady about your reporting quality in the New Year and beyond.

    If nothing else, we hope you have enjoyed listening to some fantastic and enduring classics…you can listen to our Spotify playlist here.

    With thanks to Kaizen Reporting’s industry leading reporting experts for their contributions. Dario Crispini, David Nowell, James Mooney, Jonathan Lee and Chris Machin.

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

  • Book now! Kaizen launches regulatory reporting training service led by industry expert David Nowell

    Book now! Kaizen launches regulatory reporting training service led by industry expert David Nowell

    FOR IMMEDIATE RELEASE

    23  October 2018, London: Leading regulatory technology firm Kaizen Reporting today announced that it is launching a training service led by the company’s new Senior Regulatory Reporting Specialist, David Nowell. The training will initially focus on MiFIR transaction reporting before expanding to include EMIR trade reporting and the upcoming Securities Financing Transaction Regulation (SFTR).

    A former regulator, Nowell has 30 years’ financial services experience. Having previously worked as a transaction reporting technical specialist at the UK FSA, as head of transaction reporting for a tier-1 investment firm and head of compliance for an Approved Reporting Mechanism and Trade Repository, David has a thorough understanding of both the importance and the challenges in meeting the regulatory reporting requirements. He also has extensive experience of client training on both MiFIR transaction reporting and EMIR trade reporting.

    Dario Crispini, CEO of Kaizen, commented: “David is widely seen as a leading authority in the industry. The FCA frequently warns about the risk to institutions of inadequately trained regulatory reporting teams and in many of its warning notices cites a lack of training as a factor in its decision to censure a firm for incorrect reporting.  Expanding our services to include training makes sense for us, and we are looking forward to helping our clients improve their knowledge in this space.”

    David Nowell, Senior Regulatory Reporting Specialist at Kaizen, commented: “Training is an integral part of the systems and controls that firms need in place to be reporting accurately. It’s impossible to get your regulatory reporting correct unless you understand the legislation from the Level 1 text down to the regulatory technical standards, guidelines, Q&A and validations. Our new courses are designed to help get our clients up to speed quickly, allowing them to understand what needs to be done to report correctly as soon as possible.”

    David adds, “Ensuring your staff are properly trained on the reporting regulations can save costs in the long run as it will increase a firm’s chances of avoiding regulatory sanctions for incomplete or inaccurate reports and the additional expense of costly back reporting exercises.”

    The training service includes four-hour classroom-style workshops as well as in-house sessions for financial institutions. 

    (Ends) 

    For more information please visit our training page or for inquiries about the service please email training@kaizenreporting.com

    For media inquiries, please contact Fiona Wilde at media@kaizenreporting.com or +44 (0) 20 3912 3271.

  • Tales from the crypt – the great cryptocurrency derivatives EMIR reportability debate

    Tales from the crypt – the great cryptocurrency derivatives EMIR reportability debate

    Cryptocurrencies are often seen as a great way to get rich quick, or poor quicker. To be honest, if I wanted to lose a shed load of money, I’d much rather nip down the bookies and put it all on Tripod Lad to win the 3:30 at Kempton Park. Whilst it might fall at the first fence, at least I would have some idea about the mechanics preventing it reaching the winning post. However, my approach to losing money is looking increasingly old school. It appears that there’s nobody left on the planet who doesn’t know somebody holding a fraction of a bitcoin in the hope that it will miraculously increase in value enough to put their grandkids through university.

    So, how worrying is the rise of the derivatives on cryptocurrencies? Well, we’ve certainly seen extreme volatility in this asset class, commonly attributed to investor behaviours of herding and regret-aversion. Does this create systemic risk? Well, it’s tempting to believe this asset class isn’t mature enough yet to represent a risk to the entire financial system. However, the launch of exchange traded derivatives on cryptocurrencies has led to involvement of increasing numbers of systemically important financial institutions in this asset class. The CFTC Chairman J. Christopher Giancarlo has warned whilst cryptocurrency derivatives are a relatively small market in terms of systemic risk, it is one that the CFTC needs to watch carefully.

    So, we hope this is a development the EEA regulators are also watching carefully. Surely this is one of the good things about EMIR trade reporting – ESMA and other EEA regulators will have had 6 years of analysing cryptocurrency derivatives to assess whether they could have the potential to grow and become a new threat to financial stability. Or have they? Possibly not, as there is a great deal of confusion in the industry as to whether cryptocurrency derivative instruments are actually reportable at all under EMIR. Whilst some firms have decided to trade report them to trade repositories, others have not. The confusion stems from the definition of reportable derivatives. EMIR takes this definition from MiFID and the FCA has explained that whilst cryptocurrency derivatives are “capable” of being financial instruments under MiFID II, it does not consider cryptocurrencies to be currencies or commodities under MiFID II. This is unfortunate as it leaves firms with the added dilemma that if these derivatives are EMIR trade reportable, exactly how should they be reported. Those firms that have chosen to report have taken the decision to report as commodity derivatives; mainly because the ESMA validation for currency derivatives requires an official ISO currency code and cryptocurrencies do not have one.  However, it is debatable whether reporting cryptocurrencies as commodities will deliver much value to the regulators as they will not be recognisable as cryptocurrencies from the report. Maybe the perfect opportunity to address this issue would have been through the fundamental changes to the reporting technical standards implemented in October 2017.

    The reporting of cryptocurrency derivatives may be one of the “known unknowns” in EMIR reporting. However, there are many known reporting errors in EMIR trade reporting that make it through the ESMA validation scheme. Just because a trade repository has accepted a report doesn’t mean it is error free. Some firms consider EMIR trade reporting to be a “fire and forget” reporting regime apparently forgetting the obligation for “complete and accurate” reporting so long as “T+1” is achieved. However, ESMA’s 2017 Annual Report and 2018 Work Programme makes it abundantly clear that the quality of data reported to TRs is not good enough and needs to be improved.

    How good is your EMIR trade reporting? Our ReportShield™ quality assurance service delivers an independent and comprehensive analysis of the accuracy and completeness of your EMIR trade reports. For a consultation with one of our experts, please contact us.

  • In the news: David Nowell on the FCA’s ‘first warning’ to industry on transaction reporting improvement

    In the news: David Nowell on the FCA’s ‘first warning’ to industry on transaction reporting improvement

    Kaizen’s senior regulatory reporting specialist David Nowell spoke with Thomson Reuters Accelus about the recent forums where the FCA’s markets reporting team set out the common mistakes that firms had made on reports and urged them to focus on accuracy and completeness. 

    David’s recent blog covered the mistakes in detail, and when speaking to Thomson Reuters he said, “The temptation with MiFID II transaction reporting is to get across the line. With EMIR some firms took the fire and forget approach to reporting. With MiFIR, the recent transaction reporting forums should have woken up firms to the fact that improving their reporting is an ongoing job.” 

    If firms fail to correct the mistakes, eventually there will be fines. 

    David said, “Firms should be in no doubt of what needs to be done to achieve complete and accurate reporting. A firm may get away with a private warning, but it will be asked to back report and engage in remediation. Even then, the firm might not find everything that’s wrong with its reporting and will incur the cost of re-reporting again.”

    Read the full article: First warning: UK FCA sets out expectations for MiFID II transaction reporting improvement (a subscription-only site). 

    • Kaizen’s award-winning ReportShield™ quality assurance service checks transaction reporting data for accuracy, completeness and timeliness. What sets ReportShield™ apart is that it tests every single data field so you get a complete picture of what’s wrong and right with your reporting. 
    • ReportShield™ includes accuracy testing, advanced reconciliation, reference data testing and a control framework – everything you need to be compliant with your regulatory reporting obligations. 
  • MiFID II reporting: what we’re seeing six months in

    MiFID II reporting: what we’re seeing six months in

    Six months in, MiFID II is still leaving practitioners and regulators alike scratching their heads with a number of seemingly intractable problems. The reporting of derivatives in particular is causing difficulty as firms continue to struggle with reporting eligibility concerns, the misreporting of certain fields and validation issues. Firms have sometimes been unable to get a copy of what they reported to their regulator or approved reporting mechanism (ARM). Taken together, this reduces the efficacy of transaction reporting, says our managing director Ian Rennie.

    Reporting eligibility

    The trials of applying the concept of “traded on a trading venue” (TOTV) are well documented. Although ESMA’s opinion (issued on 17 May 2017) sought to establish a clear meaning of TOTV, concerns persist. There are still teething problems with the infant Derivatives Service Bureau (DSB) service particularly with the interaction of the DSB’s instrument normalisation and the reporting requirements.

    Aside from TOTV there are problems with applying the reportability criteria to transactions involving indices. Identifying accurately which indices contain MiFID instruments is problematic. One obvious example is Boeing which is dual listed as LON: BOE and NYSE: BA. There is, however, no regulatory requirement on index providers to make public the constituents of any index, which are dynamic in nature; moving in and out on a regular basis.  As a result, smaller firms may find it prohibitive to source the appropriate and relevant data to identify reportable index derivatives.

    Incorrect fields being reported and risk of detection

    There have also been instances of inaccurate or superfluous fields being reported. The commodity indicator flag is being populated on non-commodity instruments. Similarly, instrument fields are being populated unnecessarily when the transaction in question is reported with a valid Financial Instruments Reference Data System (FIRDs) International Securities Identification Number (ISIN). Volatile attributes were a late addition to the reporting obligations and overall the industry is still looking to implement this change.

    The UK Financial Conduct Authority (FCA)’s investment in its Market Data Processor (MDP) platform has been significant and gives the regulator a greater capacity to detect circumstances where two parties to a transaction have reported divergent values for the same transaction. This is particularly the case in instances where transactions are traded on a venue and now, as mandated, firms must persist the trading venue ID for the transaction. The FCA can use that ID to pair transactions and then match fields to highlight any discrepancies, which it can then automatically fire out to both firms.

    Obtaining data from competent authorities and ARMs

    Regulatory Technical Standard 22, Article 15, obliges firms to reconcile and test between their internal systems and data provided by competent authorities. Failing the provision of the data by the relevant national competent authority (NCA), firms should use data from their ARM or, as a last resort, use the transaction reports submitted by the firm to their NCA.

    The FCA appears to be a frontrunner, through its MDP system, in providing data back to the firms it regulates. Commitment by other NCAs to provide back to firms their data is not clear and should be closely monitored. That said, the current FCA extract service is not fit-for-purpose; even where firms obtain FCA data through the MDP portal they are unable to reconcile back safely to their own source systems.

    As mentioned above, RTS 22, article 15 points firms to obtain data extracts from their ARMs if not available from the competent authorities. Approved reporting mechanisms have had teething problems as well in their ability to provide data back to firms. In some instances, firms have been limited by the number of transactions they can obtain and there have been problems with the methods available for the data transfer. All ARMs have made significant progress in the area, which is most welcome.

    Efficacy of reporting and communication from the NCAs

    The primary objective of MiFID II reporting is to aid NCAs in the detection of market abuse. Any issues that prevent the correct application of the reporting criteria, reporting inaccuracies or unneeded fields or roadblocks facing firms’ efforts to conduct assurance activities, therefore, will reduce the efficacy of the reporting regime, as will inappropriate requirements.

    One simple example that illustrates this is the reporting of pricing of equity swaps when compared with contracts for difference (CFDs). For equity swaps ESMA’s guidelines require the financing charge to be reported — a piece of information that appears wholly irrelevant to market abuse — while for CFDs, which are economically the same instrument, the price of the underlying is reported.

    In summary, both firms and the regulator still need to do plenty of work to get MiFID II reporting into shape. This is likely to be a long and difficult road.

    Our ReportShield™ quality assurance service gives financial firms peace of mind in the accuracy, completeness and overall quality of MiFID II reporting data. If you would like an assessment of the quality of your MiFID reporting six months in, please contact us.

    A variation of this article was published by Thomson Reuters Accelus, a subscription-only site, on 12 July 2018.

  • Media release: Leading regulatory expert David Nowell joins rapidly-growing Kaizen team

    Media release: Leading regulatory expert David Nowell joins rapidly-growing Kaizen team

    We’re delighted to announce another senior new hire in the space of a week! David Nowell, the former head of regulatory compliance at London Stock Exchange’s UnaVista, will be joining us next week. Nowell will be a Senior Regulatory Reporting Specialist, bringing with him extensive experience including over ten years at the Financial Services Authority (FSA). The news about David comes at an exciting time for us, with several new hires from tier 1 banks and the recent recruitment of Jonathan Lee, former SFTR taskforce leader at ICMA, and the addition of Elixirr (announced in March) to existing partnerships, with companies including UnaVista.

    David’s impressive knowledge of and involvement in regulatory compliance is evident in his responsibilities at UnaVista, the largest Approved Reporting Mechanism, where he was tasked with ensuring continued compliance with EMIR and MiFID reporting requirements as well as liaising with various regulatory authorities. These duties and his advice to and training for firms helped to consolidate his reputation as a leading voice in regulation and an important factor in Kaizen’s decision to enlist his services.

    Dario Crispini, CEO of Kaizen, commented: “I’m delighted for David to be joining the team to further enhance the service we provide to our client base of tier 1 and 2 banks, fund managers and brokers. Our formula of combining market-leading data scientists with industry experts is what sets us apart from competitors, and with David fitting perfectly into the latter category I’m confident he’ll be a crucial part of our operations in the months and years ahead.”

    Ian Rennie, Managing Director of Kaizen, added: “Many years of direct involvement with regulatory authorities as well as product and solution development makes for a perfect background for the service we provide to our clients. Our effective and proven quality assurance service gives financial institutions the confidence they need to focus resources elsewhere in the knowledge that they are fully compliant with ever-more stringent reporting requirements.”

    David Nowell said: “Kaizen has built a reputation of being at the forefront of its field, so this step in my career was the natural choice. I very much look forward to working together with Kaizen’s talented team and being part of the innovation and expertise that the firm consistently produces.”

    Editorial contacts

    Fiona Wilde
    Email: media@kaizenreporting.com
    Tel: +44 (0) 20 3912 3271

     

     

  • In the news: Dario Crispini speaks to Best Execution on the challenges of regulation on derivatives

    In the news: Dario Crispini speaks to Best Execution on the challenges of regulation on derivatives

    Our CEO Dario Crispini spoke to the Editor of Best Execution Lynn Strongin-Dodds about the ongoing trends and challenges of regulation on the derivatives industry and how market participants are leveraging technology to enhance processes and data management.

    Extract: 

    While the trading dynamics of derivatives will continue to focus the mind, coming to grips with the data burden – present in almost all other sets of regulation – is also consuming time, money and resources. Detailed reporting of trades across a range of asset classes is now required but, as with trading, asset managers just crossed the MiFID II finishing line and are planning to enhance their services.

    Dario Crispini, CEO of Kaizen Reporting believes that the “biggest challenges are data quality, reporting accuracy and getting a complete picture,” he adds. “There is a lot of choice in terms of the number of reporting systems but choosing one is not the end of the story. There needs to be a strong control and governance element.”

    Read the full article. 

     

  • MiFID II Q&A update: New guidance on complex trades and national ID validations

    We are five full months into MiFID II. Competent Authorities are still experiencing teething issues with the instrument data, validations, response messages and providing reporting firms with extracts of their submitted reports. Firms are increasingly moving their focus from addressing validation issues and handling of response files to looking at the accuracy of their reporting. All parties should be working on the most pressing issues following the 80/20 rule.

    “Firms are increasingly moving their focus from addressing validation issues and handling of response files to looking at the accuracy of their reporting.”

    Working on validations to get all the transaction reports accepted by the regulator may not be the most pressing issue.  Firms can still be reporting 100% of their records inaccurately. It is therefore important that attention is turned away from validations to accuracy testing and identifying the valid but wrong population.

    Whilst there are many areas of reporting uncertainty, ESMA has decided to focus its guidance on strategy trades. Strategy trades are relatively rare in the reporting world and affect only a very small proportion of total reportable activity. 

    This post summarises the new guidance from ESMA.

    Complex Trade ID

    A strategy trade is a trade which is composed of more than one financial instrument or legs, where the execution of the trades are contingent on each other and a single price is given for the strategy contract as a whole. 

    When transaction reporting strategy trades, the Complex Trade ID (field 40), must be populated with a code that links each of the legs. This code must be unique to each strategy trade for the reporting firm. ESMA’s latest update to its Transaction Reporting Q&A on Friday (25 May) provides more guidance on how and when the Complex Trade ID should be populated. 

    The aim of the Complex Trade ID is to notify the users of the transaction report that the instrument reported is part of a broader strategy trade and to enable the user to identify any related transactions.  In the guidance they make it clear that:

    • The price reported is the price of the strategy as a whole not the price of the individual leg being reported.
    • The Trading Venue Transaction Identification Code (TVTIC) should be populated for each reported leg of the strategy. Presumably, this would only apply where the strategy itself was executed on a trading venue and the legs execute as part of that strategy. There is more complexity here and more scenarios which the Q&A does not address.  
    • The Complex Trade ID field must be populated even where only one leg of the strategy trade is reportable. It is still a strategy trade and the price must reflect this.
    • Where the strategy itself is allocated an ISIN you still report the individual legs and not the strategy as a whole.
    • In terms of reference data to be reported for strategy trades, the Q&A makes clear that the reference data for the legs must be submitted, not the reference data for a “strategy instrument”.

    National ID validations

    The only other update in the Q&A relates to the validations published for the national identifiers. We have commented in a previous post as to the complexity the approach gives rise to. This is the second update to these validations that have been published.  The latest is:

    • Czech Republic: “It should be noted that the special character “/” is just a separator and should be omitted in transaction reports.”

    Presumably there have been problems with firms including “/” in their identifiers.

    Kaizen’s accuracy testing checks all MiFID II data fields to ensure your reporting is correct. To find out more about how we can help you avoid the ‘valid but wrong’ problem, please get in touch. 

  • FCA makes data integrity a clear focus for 2018/19

    FCA makes data integrity a clear focus for 2018/19

    The FCA recently published its business plan for 2018/19.  In this blog, we highlight the areas impacting regulatory reporting and other areas of interest to us and our clients.

    MiFID II

    As we are now six months into MiFID II, the FCA has signalled its intention to focus on market cleanliness, leveraging the more granular transaction reports that MiFID II requires. Another priority is to look closely at the operation of the primary and secondary markets where transaction reporting data, if it is of high quality, will be useful in its analysis.

    In the business plan’s introduction, FCA Chief Executive Andrew Bailey explains how the major changes resulting from MiFID II requirements will improve “market integrity in wholesale markets”. One consequence, he says, is the “strengthening of the transaction reporting…regimes” and that the FCA “will closely monitor how well firms are complying with these new requirements”.

    Market integrity

    MiFID II’s expanded scope will provide the FCA with more information on transactions. The plan says the FCA will “monitor, detect and investigate potential abuse in these markets and enforce against unlawful behaviour where appropriate.” It will focus “supervision monitoring on the fixed income, commodity and non-standard derivative markets,” and will use “indicators such as market cleanliness data and the number of suspicious transaction and order reports to assess the potential harm from market abuse which damages confidence and participation in the market.”

    The FCA goes on to state that:

    “MiFID II provides us with better tools to deal with potential harms from algorithmic High-Frequency Trading (HFT) by introducing new obligations and systems and controls for both traders and venues. We will focus supervisory efforts on monitoring compliance with these new rules and increasing our understanding of the use of trading algorithms and other innovations across the wholesale financial markets. We will use existing diagnostic work on HFTs, circuit breakers and mini-flash crashes to inform this work. This will enable us to anticipate and deal with potential harms this kind of technological advancement may create.”

    We expect much of the analysis is conducted by using transaction reports as well as using the granular order data from trading venues.

    The FCA plans to publish a report in Q4 of 2018/19 detailing its approach to market integrity. However, the business plan points to the active use of transaction reports by the FCA in the coming year.  It would be reasonable to assume that preceding use of the data, the FCA will undertake some assessment of reporting quality and completeness: the types of business rules alluded to by Ana Fernandes in last year’s Transaction Reporting Forum run by the BBA (now UK Finance). Any errors or incomplete reporting will become more visible to the regulators so we should expect activity in this area probably more likely in 2019 once firms have had an adequate amount of time to iron out wrinkles in their reporting systems. 

    RegTech developments

    The FCA is continuing with its TechSprints and work on the use of advanced analytics. As a RegTech firm, Kaizen is participating in these. An area of obvious interest is its proposals to utilise artificial intelligence/advanced analytics as part of the supervisory process to detection areas of non-compliance. Transaction and EMIR reporting would be obvious candidates for this type of activity as well as:

    • automated detection of unauthorised business activity on the internet through a variety of new technologies
    • testing advanced Natural Language Processing (NLP) technologies and semantic language models in an effort to automate what would otherwise be manual supervisory tasks
    • automated evaluation and detection of misleading advertising.

    The FCA will also be following up on its Call for input on Machine Executable Regulatory Reporting.

    Monitoring firms’ use of data

    The use of data by financial services firms is of obvious interest to the FCA and a potential source of new benefits as well as risks. To address this they will be monitoring the use of machine learning the use of big data pools, algo trading developments and the wider use of artificial intelligence within the regulated community.

    Cryptocurrencies

    Some of our clients execute transactions in cryptocurrencies.  This has been an area of difficulty as there is no clear or consistent treatment of cryptocurrencies across jurisdictions. The FCA sees cryptocurrencies themselves (i.e. those designed primarily as a means of payment/exchange) as being outside their regulatory perimeter. As a regulator, the FCA is concerned about protecting consumers: Initial Coin Offerings (ICOs) and cryptocurrency derivatives represent risks that potentially fall within its remit so the FCA will participate in a forthcoming Treasury Committee inquiry.

    You can read the FCA’s 2018/19 business plan in full on its website. 

  • In the news:  Dario Crispini on post-2008 world and how MiFID has altered the landscape

    In the news: Dario Crispini on post-2008 world and how MiFID has altered the landscape

    Kaizen’s CEO Dario Crispini spoke to Best Execution’s Lynn Strongin-Dodds about MiFID a decade on.

    At the time MiFID was introduced Dario was the head of the then FSA’s Transaction Monitoring Unit and managed the regulator’s transition to MiFID reporting including introducing the approach to fines for incorrect transaction reporting. 

    Here’s an exert from the article:

    Long before the financial crisis wreaked havoc on stock markets and investment banks, MiFID I was being hatched in the hallowed halls of the European Commission. It was officially launched in 2007 with the aim to shake up the status quo in the equities landscape. However, as events the following year proved, much more work was needed to be done to corral the worst of the excesses and improve transparency.

    The dispersion of liquidity has been another major challenge. “The removal of the concentration rules under MiFID I was a good thing, in terms of competition, but one of the unintended consequences was the fragmentation of the liquidity,” says Dario Crispini, founder and CEO at Kaizen Reporting and former manager of the transaction monitoring unit of the Financial Service Authority between 2001 and 2010. “As the market evolved, this led to more complex trading strategies and high frequency traders and algorithmic trading which caused distortions.”

    You can read the full article here. 

     

     

  • Media release: Kaizen and Elixirr partner to bring new level of transaction reporting compliance

    Media release: Kaizen and Elixirr partner to bring new level of transaction reporting compliance

    Kaizen and Elixirr, the challenger consultancy, have announced a new partnership, which will deliver a complete end-to-end regulatory reporting remediation service for financial institutions. We will collaboratively offer clients greatly-improved assurance testing, governance and support on their trade and transaction reporting remediation projects.

    This is a significant milestone in responding to the increasing levels and complexity of regulation faced by the industry. Kaizen is unique in its approach to compliance assurance, checking every single item of transaction data for accuracy and completeness, while Elixirr provides practical and hands on support to resolve the reporting issues highlighted by the Kaizen assurance assessment.

    Data quality has been a continual problem under the original MiFID reporting regime[1] but the increased complexity of EMIR and MiFID II reporting obligations means that this will be even harder to achieve. At the same time, regulators’ capacity to identify issues has widened, and the UK’s Senior Managers’ Regime puts additional pressure on individual managers within firms to ensure they are reporting correctly.

    Firms which do not fully address reporting issues are at risk of multi-million pound fines, reputational damage, and the cost of internally remediating the problem, which is often significant. In an industry first, Kaizen’s technology solution, combined with Elixirr’s remediation skills, will identify reporting issues quickly and ensure they are resolved and replayed, in a cost-effective, seamless way. 

    Barry Lewis, Partner at Elixirr who led the formation of the partnership, says “Kaizen have developed a service that is invaluable to the financial services industry, so we’re delighted to partner with them in such a value-added offering. This partnership means we can combine robust data quality assurance tools with the analysis and remediation expertise of our team, and help our joint clients respond even more effectively to the increasing needs for reporting compliance.”

    Dario Crispini, Kaizen CEO , says, “I see the partnership as an important step forward in compliance evolution. By combining the skillset and expertise of the two companies we are able to provide clients with greatly enhanced confidence and accuracy when reporting to regulators. Elixirr has a strong reputation, attention to detail and unwavering passion to really help firms succeed and we trust them to provide the best remediation solutions for the companies we work with. The market is already responding well, and I have full confidence that this partnership will quickly benefit our clients and go from strength to strength in the months and years to come.”

    Recently awarded the Queen’s Award for Enterprise in innovation, one of the UK’s highest business accolades, Kaizen has combined data science with leading regulatory expertise to develop ReportShieldTM, a quality assurance service that provides firms with a complete set of controls to ensure the accuracy, timeliness and completeness of their reporting data.  ReportShield tests all of a firm’s records, avoiding the shortcomings of other approaches which test only small data samples.

    Elixirr has a proven track record of working with financial services firms internationally to help them identify issues and achieve full and sustainable reporting compliance.

    -ENDS-

    For media inquiries, please contact Fiona Wilde, Head of Communications and Marketing on 07834 731 602 or media@kaizenreporting.com.

    [1] Kaizen’s analysis of transaction reporting fines issued by the FCA found that 65% of transactions were incorrect, and that firms were unaware of these inaccuracies. See our infographic here. 

  • In the news: Dario Crispini talks LEIs with Funds Europe

    In the news: Dario Crispini talks LEIs with Funds Europe

    Our CEO Dario Crispini spoke to Nicholas Pratt at Funds Europe about some of the challenges of the introduction of Legal Entity Identifiers (LEIs) which are an important component of MiFID II.

    Extract: 

    Each fund managed in Europe has to have a registered LEI and the ESMA has imposed a ‘no LEI, no trade’ rule to underline the importance of the initiative.

    Currently there are 1.1 million LEIs in issue. However, many people think that’s some way off the desired total.

    “I would expect there needs to be a lot more LEIs registered to cover the market,” says Dario Crispini, chief executive of Kaizen Reporting, who has previously worked for the Financial Conduct Authority in the UK.

    Read the full story here. 

  • In the news: Dario Crispini on transaction reporting data quality with Thomson Reuters

    In the news: Dario Crispini on transaction reporting data quality with Thomson Reuters

    Now MiFID II go-live has taken place, the FCA’s focus is starting to turn to the quality of the transaction reporting data being received by its Market Data Processor (MDP).

    Kaizen’s CEO Dario Crispini spoke with Rachel Wolcott at Thomson Reuters Accelus about the enhanced new tools the FCA has in place for monitoring transaction reporting data quality under MiFID II.

    “Fixing data quality problems early will help firms manage regulatory risk as well as the overall cost of reporting, perhaps even bringing it down,” Dario told Thompson Reuters. 

    “The sooner they (firms) do the data quality assessments they’ll be in a better place to get fixes done without having to reallocate resources to new IT projects. When we look at EMIR and Dodd-Frank Act reporting there’s still issues known about for a long time but there’s just not enough resources to put in those fixes,” he said.

    The FCA’s Market Data Processor (MDP) has far superior analytical tools and exception alerts which will make the FCA’s surveillance more proactive and timely.

    Read the full article: UK regulator to check MiFID II reporting data quality shortly, despite systems glitches (a subscription-only site).

    Trade repositories need constant supervisory hand holding to manage data quality-ESMA

    Dario also spoke to Thomson Reuters about the challenges trade repositories in Europe are facing when it comes to managing data quality issues.

    Read the full article Trade repositories need constant supervisory hand holding to manage data quality-ESMA (subscription-only site).

  • ESMA’s LEI solution is a Grandma-like gift

    ESMA’s LEI solution is a Grandma-like gift

    Thank you Santa, you have delivered the first wish on our Christmas list –  a solution for firms with clients without LEIs!

    Well…kind of.  ESMA has blinked first but late in its long standing game of Chicken with the industry and today announced it has relaxed its approach on the LEI requirements for reporting entities and issuer of financial instruments.  There was very little wriggle room for ESMA as it has no powers to amend the regulation and instead has had to relax one of the validations and pass on significant operational difficulties to firms and trading venues.

    ESMA recognises industry concerns

    In its statement, ESMA recognises three key concerns of the industry. First, that firms will not succeed in getting LEIs for all of their clients prior to 3 January 2018. At the same time, it acknowledges that these clients will still approach firms to trade with them post 3 January regardless of not having an LEI.  Finally, trading venues will face similar problems with non-EU issuers who will not have obtained LEI.  There is a fourth issue of handling corporate actions for clients without LEIs.  These are issues that Kaizen reflected previously in our blogs and publications and ESMA has now been persuaded by the consequences of the LEI obligations. In short, the LEI mandate would result in a scenario where clients without an LEI have no option but to trade with a US located bank or venue resulting in a material outflow of business from the EU financial system.

    A Christmas gift but not for life…

    ESMA’s proposal is a temporary but messy solution so as not to breach the regulations. For a period of six  months from 3 January, investment firms and trading venues can continue to provide trading services to clients without an LEI that would trigger a transaction reporting obligation. But only if two obligations are met:

    • The investment firm obtains the necessary documentation from the client to apply for an LEI on the client’s behalf
    • The trading venue reports its own LEI instead of the  LEI code of non-EU issuers whilst reaching out to them to get one

    Investment firms will have to apply immediately for the issuance of an LEI on behalf of the client and then submit all required reports for that client once the LEI has been issued.  ESMA and the NCAs accept that this solution will cause a delay in reports being made and they will actively monitor the timeliness of late reports.  At the same time, they will amend their validation rules to allow the acceptance of transaction reports where LEI issuance date is after the transaction reporting execution date.  But the FCA have already communicated that they will not be able to make this change for the 3rd January!

    ESMA and your Grandma

    Like Christmas presents from your Grandma, ESMA’s LEI ‘present’ is well meaning but does not quite hit the spot.  Worse of all, it doesn’t come with a receipt that will allow you to exchange for a better gift. The effect upon firms is a messy one:

    • Outreach: Firms will have to, at short notice, reach out to clients to obtain the required data to register them for an LEI and what happens if the client doesn’t want to play?
    • Register and pay for LEIs: Put in place a process at short notice to process LEI requests
    • First Mover Disadvantage: Those firms who respond first will end up paying for LEIs that then also benefit their competitors
    • LEI Duplication: Although the GLIEF system is meant to prevent duplication of LEI issuance, it will likely face its greatest test as multiple firms apply on behalf of clients
    • Excluding Reports: Firms will have to put in place processes to identify and exclude transactions without LEIs and then report once the LEIs issued
    • NCAs not ready: The FCA have already said they will not be able to make the validation changes in time, meaning that they will reject reports even if they follow process outlined by ESMA
    • ARMs and firms not ready: ARM validations and for some firms their own internal validation processes will have to be altered to allow the historic reports to be submitted with newly minted LEIs.

    So –  not quite the present we all wished for and we may well be left scratching our heads in January wondering how to put it together and make it work.  Fingers crossed we have better luck on our other nine items on our Christmas wish list…

  • MiFID II Q&A updates – an early Christmas present from ESMA

    MiFID II Q&A updates – an early Christmas present from ESMA

    ESMA has, this week, published updates to three of their Q&As on MiFID II which you need to be aware of for your MiFID II programmes as we approach go-live. 

    For transaction reporting, the latest update reiterates how you determine reportability for some specific instruments.  We believe that key amongst these is ESMA’s confirmation that units in collective undertakings and ETFs need only be assessed on the instrument itself and not on their underlying holdings. This point has been outstanding since the original data reporting consultation paper. 

    There are also other updates to Q&As including transparency topics and Market structure topics.

  • Dear Santa…a MiFID II Christmas wish list

    Dear Santa…a MiFID II Christmas wish list

    Dear Santa

    I have been very good this year. I planned my MiFID II transaction reporting project early. I read Levels 1, 2 & 3 (well maybe not all of level 3…). I put enough money in the budget, identified my risks and spoke to my peers.  In short I think I have done everything possible but I still think I might be in a little bit of trouble. So this year for Christmas I have one or two wishes that I hope you can grant so I can start the new year with a cheery grin as big as yours.

    Could you and Ruldolph please drop into my stocking this year:

    1. An LEI for all my clients who are refusing to get one even though I have offered to help many times in doing so.  I do want to keep talking to them next year!
    2. Help trading venues send the fields they need to for me to make my report.
    3. May my ARM be able to onward report to the FCA without any issues.
    4. A bright and sparkling new reconciliation that reconciles all my trades and not just the ones I sent
    5. Change ESMA’s mind and let them agree that the FIRDs list is a golden source of data
    6. Please just make ‘shortselling’ either go away or send me a new magical toy that will calculate it every day and correct it even  after I need to include a trade that was not captured the previous day
    7. Some really clever testing that identifies any of my mistakes so I can tell my Senior Manager Regime (SMR) manager all is well and he/she won’t lose their house
    8. Make all corporate actions involuntary even though they aren’t (our secret, Santa)
    9. Now I have lots of friends from different countries and I would like just one way of identifying them not several.
    10. An Xbox with the latest version of Overwatch

    Now Santa I hope you don’t think me too greedy, but compared to my friends in America and Hong Kong I think I might be in more need for Christmas presents than them.

    I’ll leave a mince pie for you and some carrots for Rudolph . Even if you can send me a few of the items I have asked for, I will be happy and I promise I’ll ask a lot less for next year.

    Love from…
    Little Johnny

    P.S If you can’t do 4 and 7 then please drop this letter over to those lovely people at Kaizen Reporting, I am sure they will be able to help!

  • In the news: Kaizen speaks to CNBC about what to expect from MiFID II

    In the news: Kaizen speaks to CNBC about what to expect from MiFID II

    Kaizen’s Managing Director Ian Rennie was live on CNBC this morning where he gave a rundown of what to expect from MiFID II when it goes live in just a few weeks.

    Watch the interview here. 

  • Media release: Kaizen announces an excellent 2017, with new clients, offices and award wins

    Media release: Kaizen announces an excellent 2017, with new clients, offices and award wins

    For immediate release – Thursday 14 December 2017

    Kaizen Reporting, the leading provider of regulatory reporting quality assurance, has had another very successful year. Strong demand for Kaizen’s automated testing services has seen it double its client base and number of employees, which necessitated a move to new offices. Kaizen has also extended its services to cover more G20 jurisdictions and regulations including EMIR 2.0 and the upcoming MiFID II. Kaizen was recognised for its pioneering approach to quality assurance with the Queen’s Award for Enterprise, one of the UK’s highest business accolades.

    Dario Crispini, Kaizen CEO, says, “2017 has been a fantastic year for Kaizen and I think we will look back on this year as our ‘breakthrough’ year. Demand for our services has really taken off.  Our revenues have grown by nearly 150% and we have signed a large number of new clients including four tier 1 banks and several of the world’s biggest asset managers, hedge funds and brokers; we also made some significant new hires. 2018 is looking to be just as successful with new services, partnerships and growth already in the pipeline.”

    As well as winning the Queen’s Award earlier this year, Kaizen’s flagship ReportShield™ service also won Best Compliance and Regulatory Solution at October’s Fund Services Awards.

    Crispini added, “The awards we’ve received have been the icing on the cake this year and we see them as further acknowledgement of the impact our services are having on the industry.  Regulatory reporting is getting more complex and challenging for firms, but we take that burden away from our clients and give them confidence in their reporting.”

    ReportShield™ provides firms with an automated set of controls that give full transparency of reportable data, detecting even minor errors. This gives financial firms the ability to identify and manage their regulatory reporting risks, building real confidence in their reporting – and most importantly, avoiding regulatory censure. 

    Dario continues, “Looking ahead to 2018, the MiFID II pain will continue and we expect firms to turn their attention to the deployment of appropriate controls for MiFID II. At the same time EMIR and DFA reporting quality, resulting in remediation of reporting issues, will become more important, along with the challenges of SFTR implementation and the impact of the Senior Manager’s Regime on reporting.”

    ***ends***

    For media inquiries, please contact Fiona Wilde, Head of Communications and Marketing on 07834 731 602 or media@kaizenreporting.com

  • In the news: Kaizen speaks to Global Risk Regulator about MiFID II data quality

    In the news: Kaizen speaks to Global Risk Regulator about MiFID II data quality

    Our CEO Dario Crispini spoke to Justin Pugsley at Global Risk Regulator about his concerns for data quality in the lead up to MiFID II go-live. 

    “Some of that data is of poor quality due to different processes and formats within a bank’s systems and due to different ways of interpreting it. Then there’s an issue of knowing which parts of it are wrong,” Dario told Justin. 

    Meanwhile, regulators are collecting vast quantities of this data and could draw misleading impressions of what’s going on in the markets. “This can raise red flags for an issue that might not exist,” he said. 

    Read the full article here. 

  • Q – Who should read the latest MiFIR Q&A?

    Q – Who should read the latest MiFIR Q&A?

    A – Those involved in: portfolio management outsourcing, IPOs, corporate actions and trading of swaps which contain an index.

    ESMA has published its latest version of its Questions and Answers on MiFIR with updates exclusively on the topic of firms’ transaction reporting obligations under MiFIR article 26 and ESMA RTS 22. There are four questions raised, each marked with the update date of 14 November 2017.  Here we briefly explore the key points of each question and answer.

    Q7: How should transactions be transaction reported where portfolio management has been outsourced? (page 33)

    ESMA provides a new detailed scenario and answer to the question in the form of diagrams, example reports and narrative explanation. In this scenario, where firm (B) is outsourcing the portfolio management to another firm (Z), who is making the investment decisions on behalf of firm (B), ESMA confirms that firm B needs to report the algo or person who is primarily responsible for the decision to delegate.

    Q8: What are the reporting obligations for a primary issuance?

    ESMA has confirmed that all members of a syndicate need to report all execution legs by the ‘coordinating bank’ (CB) and the ‘billing and delivery bank(s) (B&D).  A CB is defined as a bank that will buy from the issuer/seller and sell to another bank or banks in the syndicate. A B&D bank will then sell to the clients, noting that a CB can also act as a BD. In relation to the time that needs to be reported, this should be the date time at which the pricing and the allocations are finalised between issuer and the syndicate, normally the first listing. ESMA has provided worked out examples for other fields.

    Q9: When are corporate events reportable?

    The industry is going to have to pick through the answers to question 9. ESMA reiterates that corporate actions are reportable where the investor has an opportunity to make an investment decision. It then goes on to recognise in practice that many corporate actions are as a result of mandatory events that bring them within the exclusions under 2(5)(i) of Article 26. This still leaves an element of interpretation on behalf of firms to identify these exclusions.  There is clear guidance on corporate events resulting from a default option and where an investor has given standing instruction.  For both categories a report is required.

    ESMA also confirms that it is the transaction resulting from the event that should be reported and provides a worked example. There are other points to review but in short and at first glance, this guidance reiterates that firms will need to put in place measures to identify reportable corporate actions.

    Q10: Are both legs of a swap reportable, when one leg contains an index such as LIBOR or EURIBOR?

    I think the answer simply says ‘look at example 106 in section 5:35.7.1’ but uses many more words than that to say this!

    The main purpose of this blog was to draw your attention to the latest Q&A and to highlight some of the key points. In terms of readiness for 3 January, I think the most significant impact will be the reporting of corporate actions and firms’ ability and capacity to separate those that are reportable from those that are not.

  • FCA’s first EMIR reporting fine highlights importance of robust testing and controls

    FCA’s first EMIR reporting fine highlights importance of robust testing and controls

    The £34.5 million fine issued this week by the FCA is the first enforcement action for failing to comply with Article 9 of EMIR and highlights the increasing importance the regulator is placing on data quality.

    It was generally accepted that the regulator would eventually take enforcement action against a firm for EMIR breaches and there would have to be a firm first in line.  In this case it was Merrill Lynch International, however it could probably have been one of many firms that have struggled to deal with the EMIR reporting requirements. 

    The FCA understands that reporting won’t be 100% all the time however its final notice highlights insufficient testing to ensure the accuracy and completeness of reports as well as weaknesses in oversight arrangements that would have contributed to the under reporting of 68 million exchange-traded-derivatives over a two year period. 

    Poor quality data is industry wide 

    While these are serious failures, we would argue that they are not unique to Merrill Lynch.  Poor quality data is a widespread industry problem, something that the regulator and we here at Kaizen have been highlighting for some time. 

    Just last week Ana Fernandes, of the FCA’s Markets Reporting team, focused on the issue of data quality at an industry conference we attended.  She highlighted the importance of  having comprehensive in-depth testing and reconciliations in place at a frequency appropriate to trading volumes.  Firms must test for the accuracy and completeness of their transaction reports and have the appropriate oversight arrangements to detect and remedy systemic problems.  Ana said there were ‘high expectations’ come 3 January 2018 when MiFID II goes live that they would see better data and this is as essential for EMIR, as it is for MiFID and MIFID II.

    Just the tip of the iceberg

    Last year we published our analysis of FCA MiFID I reporting fines which shows how easy it is to get reporting wrong.  More often than not, firms continue to get false confidence from the validations provided by ARMs and Trade Repositories without testing whether the data at source is correct.  Ana in her speech last week focused on just that, “Don’t think that because the file has gone to the ARM and the FCA that it is done” she said. 

    The final notice clearly demonstrates the FCA’s expectations for robust and comprehensive testing of reporting.  This requirement is more clearly articulated for MiFID II, where testing for accuracy and completeness is mandatory under RTS 22, Article 15 and these controls should be in place at go-live.  Similarly, from 1 November (next week!) when EMIR Level 3 goes live, a lot of reporting requirements currently in the EMIR Q&As become part of the Regulatory Technical Standards and therefore become more easily enforceable by the national competent authorities.

    The FCA says the fine, the largest so far, ‘reflects the importance’ it puts on this type of reporting and the important role it plays in ensuring a transparent market. The action also shows that the regulator will fine you more if you’ve got it wrong previously and that it is applying the same approach to EMIR as it does with MiFID in terms of fining on a per record basis. 

    Expect more fines as regimes mature

    As the G20 reporting regimes mature, we are seeing a general trend of increased enforcement activity.  The CFTC has been active recently re DFA, and we also saw the recent ASIC fine by the Australian regulator so I expect further fines to follow.

    Improving firms’ reporting data quality is the reason we at Kaizen exist.  We have several clients that report over 100k trades per day to a trade repository.  With these types of volumes, it’s very easy to end up facing an eye watering fine which is why we have designed our services to protect both the firm and the individuals with reporting oversight responsibility under the senior manager’s regime. 

    Please don’t hesitate to contact us if you would like to discuss your regulatory reporting data quality or any of the issues raised in this piece.

  • FCA to focus on reporting data quality in 2018

    FCA to focus on reporting data quality in 2018

    The Kaizen team’s previous visit to The Royal Garden Hotel in Kensington was just a few weeks ago when we picked up the Best Compliance & Regulatory Solution award at the Fund Services Awards.  We found ourselves at the hotel again at City & Financial’s one-day conference last week to get a flavour of how ready the industry is for the go-live of MiFID II in the new year. Kaizen’s Ian Rennie is pictured and spoke about how Senior Managers can ensure they’re compliant with MiFID II under the Senior Manager’s Regime. 

    All eyes on reporting data

    The keynote address came from the Financial Conduct Authority’s (FCA) Ana Fernandes and she made one thing very clear: The FCA expects firms to be ready come January 3rd 2018.  Excuses about the complexity of the new regime will be no use to anybody, especially given the amount of time firms have had to prepare for it, she said.  Ana also made the point that a firm’s reporting requirement does not simply end after successful data submission. Constant monitoring is expected post-reporting and any corrections that need to be made should be done quickly. There is going to be a lot of eyes on this data and firms will be called out on anything that looks suspicious.

    LEIs are a key focus for regulator

    Ana went on to explain that one third of the fields in MiFID II are related to counterparty information and that this is a key area that the FCA is focusing on. They want to know exactly whose investments will have a negative knock-on effect in the market.  Of course with this, the mandate of the LEI is justified in the eyes of the regulator.  If firms are still disputing this decision at this stage and have not looked into the deeper complexities of the regulation, they have a lot to be worried about.

    Data quality must be good at source

    The comments on the importance of LEIs were echoed by the next speaker, Francis Gross, Senior Advisor at the Directorate of General Statistics at the European Central Bank. His main focus was on increased harmonisation and standardisation of data and believes that in order to identify market abuse before it is too late, data quality must be good at the source.  He compared financial services data unfavourably to that of retail, saying, “if shops had same data quality as financial services then shop shelves would be bare and there would be queues in the street’.  The reality is that there is no time to cleanse it at the regulators’ end given the quantity of data they receive every day.  

    It’s all about data accuracy

    My take home point of the whole conference was that gone are the days where firms only need to worry about under or over reporting of data.  2018 will bring a shift of focus to the accuracy and completeness of data reported.  Both EMIR RTS 2.0 and MiFID II bring more rigid definitions of data that needs to be reported and firms need to have controls in place to prove they are reporting correctly and completely, something Kaizen is helping its clients with as they prepare for MiFID II.  

    Please contact us if you would like to discuss any points raised in this blog or discuss your preparations for MiFID II transaction reporting.  

  • In the news: Dario Crispini speaks to Best Execution on derivatives identifiers

    In the news: Dario Crispini speaks to Best Execution on derivatives identifiers

    Our CEO Dario Crispini spoke to Lynn Strongin-Dodds of Best Execution about the steps being taken towards greater standardisation of data contracts, content, identifiers and post-trade procedures. 

    Last year the International Swaps and Derivatives Association (ISDA) published a paper entitled “Future of Derivatives Processing and Market Infrastructure” which called for firms to work together to develop standardised data contracts, content, identifiers and post-trade procedures. While few expected to see the industry change overnight progress has been slower than expected.

    “Under EMIR and MiFID, you have regulatory pressure to standardise instruments that are traded OTC because of the clearing and margin rules. However, one of the problems with the ISINs in the derivatives space is that they are only focused on Europe and are not global. If you trade an ETD on a third country market you will need an alternative. Another point of contention around OTC derivatives is that the DSB is run by ANNA, whose members are all profit-making companies and I am not sure that is the right approach,” Dario told Best Execution. 

    Read the full article here. 

  • CFTC Fines Top Tier Bank for Legal Entity Identifier (LEI) violations

    CFTC Fines Top Tier Bank for Legal Entity Identifier (LEI) violations

    It sounds like MiFID II’s mantra of ‘No LEI, No Trade’ has travelled across the Atlantic and resonated with the CFTC. 

    Last week it was announced that a tier one bank has been fined $US 550,000 for failing to update its counterparty LEI information.  Whilst the CFTC’s regulation is not as strict as its European cousin’s, it does expect that LEI information is provided when it becomes available. 

    Although it’s not one of the largest fines they have ever issued it does give us a new insight to the sort of checks they are performing.

    Specifically, the CFTC’s investigation found that a design flaw in the bank’s architecture failed to update the regulator when an LEI became available for a counterparty and all other aspects of the contract remained the same.  Full details of the penalty can be found on the CFTC website. 

    On first thought it may sound like updating the counterparty identifier is a simple change to implement but dig a little deeper and you can see how it is an easy pitfall to find yourself in.   A small firm that does not have an LEI will not be the reporting party when they are facing a tier one bank.  Realistically, they will be paying little or no attention to their derivatives reporting and have little incentive to notify the bank when they acquire an LEI.  The bank could easily have hundreds of similar small firm clients and tens of thousands of transactions to report each day.  Unless a dedicated process exists to check for an updated LEI, it is a simple thing to miss, especially when none of the economics of the contract change.

    Is your counterparty LEI information being reported correctly? Kaizen’s ReportShield™ accuracy testing and reference data testing identifies all counterparty errors so they can be remedied quickly and easily.  Please get in touch to discuss your LEI or MiFID II reporting challenges.

  • Transparency is still an issue 10 years post financial crisis

    Transparency is still an issue 10 years post financial crisis

    “If these things were so large, how come everyone missed them?”
    The Queen – 5 November 2008

    It’s ten years this month since the financial crisis began and we’re reminded that it was Her Majesty The Queen who spoke for the nation when she asked why it had taken so many financial experts by surprise.

    Her Majesty asked the question at a visit to the London School of Economics a few months after the collapse of Lehman Brothers.  The reply?  “At every stage, someone was relying on somebody else and everyone thought they were doing the right thing.”

    Could it happen again?

    August 9 2007 is largely known for being ‘the day the world changed’ when BNP Paribas froze three of their funds, indicating they had no way of valuing the assets inside them.  The run on British bank Northern Rock began a month later.  One year later in September 2008, Lehman Brothers filed for bankruptcy, prompting worldwide panic.

    Now, ten years on, could it happen again?  Have efforts to prevent another financial crash been successful?  The Governor of the Bank of England Mark Carney thinks so.  Last month he said that the things that caused the last financial crisis had been fixed.  Carney believes that the reforms agreed by the G20 have created a safer, simpler and fairer financial system.  

    Part of this reform agenda was a substantial increase in reporting requirements which are meant to bring greater transparency and allow regulators to be able to spot the build-up of systemic risk.  But persistent data quality issues continue to thwart making good on this objective.

    Data quality is the big issue

    Why?  The regulations that have arisen out of the ashes of the financial crisis including EMIR, Dodd Frank Act and the soon to be live MiFID II are meant to put in place reporting regimes that give regulators all the information they need to identify the build-up of systemic risk and detect market abuse.  The idea being that if there is to be a next time, regulators can’t stand behind the reason that they had limited visibility.  However, the increase in breadth and depth of information required has led to a corresponding and manifest increase in complexity which has led in turn to a decrease in data quality – which, if left undetected, can have serious and dire consequences for firms and regulators alike.

    We’ve highlighted before the problems that banks are having with their regulatory reporting quality – the very reason Kaizen is kept in business!  Last year the FCA found 65,000 data quality breaches in a week when testing only four of the MiFID transaction reportable fields.  Our own analysis has found at least 65% of transactions are being reported incorrectly with firms completely unaware of the inaccuracies of their data.  And this is in a mature regime which is comparatively simple compared to MiFID II, EMIR and DFA. 

    Stuck between a rock and a hard place

    If regulators, having asked for a substantial increase in reported data, are then unable to identify the build up of systemic risk, this will ring hollow in the corridors of power of the G20 governments.  Under this pressure regulators will have increasingly low tolerance with firms who persist with reports that have significant data quality issues.  

    For the industry to be able to add ‘improved transparency’ to Carney’s list of positive changes since the financial crash, there needs to be a sustained and comprehensive improvement in the quality of the data that firms report to regulators.

    Regulators cannot afford to allow data quality issues to persist.  They will take the necessary actions and we can expect increased censure and fines to follow as required.

    What next?

    In this context and environment it is critical for firms to be able to identify and quantify data quality issues in their reporting, which is exactly what Kaizen does for our clients and how we explained what we do to the Queen in our recent conversation with her at Buckingham Palace!  

    In all seriousness, please contact us if you have concerns about the quality of your regulatory reporting or would like confirmation of its accuracy and completeness.  We are here to help. 

  • Big EMIR changes in MiFIR’s shadow and deadline fast approaching

    Big EMIR changes in MiFIR’s shadow and deadline fast approaching

    With so much focus on delivering reporting functionality for the upcoming MiFIR obligations, we shouldn’t forget the substantial changes required from EMIR’s Revised Technical Standards (RTS 2.0).

    The revised RTS was published in January in the Official Journal of the European Union and updated Q&As were published in April.  

    When will obligations come into effect?

    The new legislation will come into effect on 1 November 2017 with the exception of one rule, which came into effect immediately…the extension of the back-loading deadline (which we covered in this blog).  This came as a sigh of relief to those who had not yet started this task yet and a nasty kick in the teeth to those who had spent many painful hours digging through their archives searching for ancient data.  The justification for extending the deadline is that terminated trades do not increase systemic risk.  Given that one of the key objectives of the regulator is to identify systemic risk, the question ‘why does the regulator need this data?’ needs to be asked.  What will happen in 2019 when the new deadline approaches?

    Standardisation is welcome

    Many of the other new rules provide standardisation on how to populate existing fields. This is certainly a step in the right direction.  Counterparties no longer need to quibble over who is the buyer and who is the seller of their contract.  RTS 2.0 provides 10 lengthy rules to determine what is eventually reported out as a single letter – ‘B’ or ‘S’.  Disputes on which party should generate the UTI can be put to rest and altercations on counterparty identification will end as UTI generation responsibilities are created and LEIs are mandated.

    Standardisation is also desired for the ‘classification and precise identification of derivatives’. This is of course more easily said than done in a world where the industry always moves faster than regulation. Spreadbets and swaptions have become newly added contract types as they rise in popularity but ESMA has admitted that not every derivative can be put into a box by allowing the use of ‘other’ contract types.  Does this make the most complicated contracts the easiest to report?

    We also see clarifications and extensions to the allowed values for action type, which was a field that was introduced as part of the Level 2 validations.  ‘C’ is now confirmed to mean an early termination of a contract rather than a more general cancellation. ‘P’ has been introduced to identify the position component of the contract.  The need to report a transaction as ‘new’ followed by ‘compressed’ is replaced by this which should put a smile on some people’s faces as it means substantially less data to submit.  Some things never change though and action type ‘E’ should still be regarded as the kiss of death in terms of EMIR reporting.  Once action type ‘E’ has been reported by either counterparty, you can say goodbye to that UTI. Not even the new action type of ‘R’ for correction will be able to allow the re-reporting of that UTI.

    New fields?

    Lastly, no new legislation would be complete without the introduction of some completely new required fields.  ESMA will require a much more comprehensive view on what collateral details need to be reported. In addition, the party receiving the collateral will also need to report as well as the party posting.  The ‘level’ field has also been introduced so that submissions on a position level can be separated from a trade level.  However, definitions on exactly what is the difference between trade and position level are more difficult to come across.  One notable difference is that positions can have 0 notional whereas trades cannot.

    How we can help

    With such a focus on MiFIR there is a risk that firms may underestimate the material changes introduced by RTS 2.0.  Take the time to check whether you are on track to deliver on the required changes now and contact us if you would like help to understand the new obligations and/or get your testing and controls in place.

  • MiFID II guidelines update uneventful

    MiFID II guidelines update uneventful

    There is very little of note in ESMA’s update to its MiFID II guidelines on transaction reporting announced on Tuesday 8 August.  Most of the changes are to reflect the current references for regulations and a few corrections of CFI codes used in the examples. 

    Of note are the following:

    • Execution within the firm field

    Where an investment firm is instructed on where to execute a trade, the client is instructing the execution.  The original text stated you populated the “Execution within the firm field” with “Client”.  This has now been changed to “NORE” which we think means “No reference”. 

    (See 5.12: Block 5: Execution within the firm field)

    • Reporting as DEA provider

    A more significant update, is in respect of DEA trading where you are the DEA provider.  Previously, the guidelines indicated that the execution within the firm field should be populated with an Algo identifier for the order management system that routed the order to the trading venue.  This has now been changed to “NORE”. 

    (See 5.25: Direct Electronic Access (DEA)

    • Read ESMA’s full notice
    • Download the new guidelines
    • Download a tracked changes version of the new guidelines.
  • Transaction reporting tops concerns at MiFID II conference

    Transaction reporting was chief amongst concerns at today’s UK Finance MiFID II implementation conference, where Stephen Hanks from the FCA was keynote speaker.

    At one of the first conferences since the BBA merged with other financial trade associations, Stephen Hanks spoke widely on the expected MiFID II implementation issues, focusing on four main areas of interest:

    • The publication and content of the FCA policy document published 3 July
    • Recent European Commission and ESMA activity
    • Transaction reporting issues
    • Some shared thoughts on how the FCA intends to act over next six months.

    Policy document is technical not guidance

    The publication of the 1000-page policy document had been accompanied by a loud sigh of relief within the FCA but left financial journalists scratching their heads on where to start! Stephen explained that documentation’s primary purpose should be seen as a technical exercise of translating EU legislation, of both the MiFID and non-MiFID variety, into the FCA handbook. There is no significant inclusion of guidance in the document as the FCA wishes to deliver this through their participation in ESMA’s efforts.

    That said, Chapter 2 of the handbook outlines where the FCA is adding additional requirements over and above the EU legislation. The four main areas outlined by Stephen were:

    • Policy and taping of corporate financials and discretionary managers
    • Divergence with ESMA over the appropriate test
    • Research
    • Client classification.

    FCA to provide clarity on issues before 3 January 2018

    On the topic of the appropriate test, Stephen explained that the FCA has decided to ignore ESMA; a decision not taken lightly. Rather it is a decision taken based on the specific prevalence of UCITs and Investment trusts in the UK compared to the rest of Europe  and as such, the FCA will continue to follow to advice previously provided by ESMA’s predecessor, CESR in 2010.

    Over the coming months the FCA, with the European Commission (EC) and ESMA will be focusing on a number of issues to try and provide required clarity before go live on 3rd January 2018. On both share and derivative equivalence, expect further consultation between NCAs, ESMA, EC and the industry and subsequent publications of Q&As. . The topic of commodity limits is taking up considerable time and effort at the FCA with a focus on arriving at the appropriate level of limits. The FCA is placing reliance of ESMA guidelines on how entities should determine trading venue status but are taking  wide and varied soundings from UK firms on whether they should be treated as a trading venue  or a brokerage model.

    FCA has significantly enhanced ability to detect data issues

    Stephen made special reference to transaction reporting highlighting that Zen’s replacement Market Data Processor (MDP) went live with industry testing on the 3rd July with ARMs, to be followed swiftly with APAs and trading venues. He described transaction reporting as a “particular challenge” and recognised that there will “be serious challenges” but made it clear that the “FCA wanted to work with the industry”. That said he explained that MDP will have in-built business testing, similar to that run by Kaizen, to detect data quality issues. In short the FCA ability and capacity to identify data quality issues will be significantly enhanced with the introduction of functionality provided by MDP.

    During the 200 days left to go for MiFID II go-live the message from the FCA was to take all reasonable steps to comply with the obligations, that the FCA recognised the material increase in complexity that MiFID II brings and that these two points will shape the supervisory environment in 2018. If firms do have significant or expect to have significant issues they should be flagged to the regulator as soon as possible and before go-live.

  • Top ten takeaways from the BBA’s transaction reporting forum

    Top ten takeaways from the BBA’s transaction reporting forum

    The head of the FCA’s Transaction Monitoring Unit, Ana Fernandes, gave a clear indication of the FCA’s position on MiFID II reporting at the BBA’s Transaction Reporting Forum this morning. 

    Here are our top ten takeaways from the event:

    1.  “The devil is in the detail” – Ana acknowledged the tension between being prescriptive with detailed rules vs providing general principles for firms to adhere to. 
    2. “MiFID II is an enhanced regime,” not a new regime.  The FCA and the industry are leveraging 20 years or more of transaction reporting experience. Our take on that is expectations for good quality data will be higher than for a new reporting regime.
    3. MDP applications need to be submitted as soon as possible.  The FCA isn’t seeing “as much traction as expected”.  If you delay too much, don’t expect the FCA to turn it around and they won’t differentiate between the types of entities onboarding whether it is ARMs, trading venues or directly submitting firms.
    4. The FCA is ready to commence industry testing on 3rd July but not all reference data will be available due to dependencies on FIRDS.  Any test cases firms are planning will therefore need to take this into consideration.
    5. The FCA is still not seeing many queries from firms and they would expect more.
    6. Traded on a Trading Venue (TOTV) didn’t get much attention other than to say that the FCA expects the scope will apply to a small proportion of instruments once the trading obligation for derivatives is in force.  We will be publishing a blog shortly with our views on TOTV.
    7. New Q&As are being finalised by ESMA covering amongst other things:
      • Increases and decreases in notional
      • Reference data
      • Corporate actions
      • ISINs.
    8. The FCA will be conducting business validations as well as technical validations.  The technical validations have been published but she did give some indication that the business validations will cover quality tests including matching between reports across firms and other data such as order book data and trade reports.  The FCA expects firms to do the same as part of their data quality efforts.
    9. Where issues are identified, notifications to the FCA should take place in the same manner as today. 
    10. Leniency – on prompting from the floor regarding leniency in the early days post go-live, Ana stated that the FCA will consider each case on its merits. 

    It is clear the importance of effective data quality tools especially reconciliations is paramount in the mind of the regulator.  Ana was clear the FCA expects firms to have reconciliations in place at go-live.  Kaizen will be offering cross-entity reconciliations where there’s agreement between parties to help firms meet this requirement.  Do get in touch if you’d like to discuss this or any of your MiFID II reporting requirements further. 

  • Q: Which ‘reporting crocodile’ will be nearest the canoe in 2017?

    Q: Which ‘reporting crocodile’ will be nearest the canoe in 2017?

    A: MiFID II, and it’s only 358 days away…

    In our last blog we looked back on the reporting events and challenges that shaped 2016 through the hits of Bowie; but as we begin 2017 we find ourselves asking, ‘where are we now?’ (last Bowie reference…promise!). In short, there are many reporting regimes that are contenders to win the accolade of the ‘reporting crocodile’ nearest the canoe for UK firms in 2017. However, the characteristics and specific demands that MiFID II requires of firms, establishes it as the most demanding and challenging regulatory reporting ask of 2017. The clock is ticking and as at the time of writing, we have 358 days until go-live!

    The other crocodiles circling the canoe

    For those of you who came back into the office to deal with the aftermath of your firm’s Bank of Israel Reporting go live, 3 January 2018 may seem a long way off. Equally if you are responding to the CFTC review of your DFA reporting through the NFA and their 4s letters or an official examination by them, again MiFID II seems a distant problem to contend with. Worse still, your firm may be facing regulatory censure on longstanding commitments such as MiFID I or, as we are seeing increasingly, fines from the CFTC in relation to accuracy of reports under the DFA regime. Then there is pressure from ESMA and competent authorities to improve the quality of EMIR reports. In addition to the EMIR Review and MiFID II, European firms need to contend with consultations on SFTR.  For those who have US and HK obligations there are the new SEC and HKMA obligations due throughout the first three quarters of the year.

    These ‘crocodiles’ are not just circling but hitting the canoe at the same time and of course, you cannot pick and choose which ones to deal with; all need to be grappled with. But what makes MiFID II stand out as the crocodile you need to deal with most?

    What are the characteristics of MiFID II that require special attention?

    In a nutshell – in many respects, MiFID II confers materially different obligations on firms and runs a much greater risk of regulatory censure following go-live compared to other G20 reporting obligations. There are three characteristics which mark out MiFID II for special attention:

    First, the sheer number of fields, many different from what has been asked of before. E.g. Trader ID, algo ID, short-selling field, pre-trade waivers, and precise execution time to the millisecond and beyond!

    Second, MiFID II builds upon an existing regime where competent authorities, most notably the FCA, have developed expertise in detecting data quality issues and have a regime in place to issue sanctions. Ana Fernandes of the FCA made it clear at the recent FCA TMU Transaction Reporting Forum, that expectations will remain high and the ability of the TMU to detect errors will be improved come 3 January 2018.

    Third, the sheer complexity of the MiFIR requirements dwarfs that of competing regimes. Whether it is determining what transactions need to be reported, what business events need to be excluded, notwithstanding ‘no LEI no trade’, the short-selling calculation, or how to put in place the mandated regulatory controls, the level of complexity is materially different than what has been expected before.

    Next, we explore some of these complexities and discuss what firms need to be doing now to ensure successful delivery this time next year.

    Your MiFID II to do list

    It’s the New Year and what better time to draft your ‘MiFID II Transaction Reporting to do list’?  Better still, we’ve done it for you…

    1. Reporting Solution – Build or Buy?

    Key to meeting the complex obligations of MiFID II is putting in place the appropriate reporting solution.  There is no fixed answer on whether to buy or build as it depends completely on your firm’s size, previous investment in meeting reporting obligations, and expected reporting volumes.

    At one end of the spectrum there are the large tier 1 banks who have been investing heavily in their reporting solutions over the last six years. In this case, it is most likely that there will be an extension of recent builds to cater for MiFID II requirements. A word of warning, IT architects and IT leads that expect a similar build to EMIR should think again, see below for examples of why.

    At the other end of the spectrum, are firms who have previously had little or no reporting obligations who are only now looking to make the decision on whether to build or buy. On balance, due to the complexity involved and time remaining, buying a solution and adapting it to your needs is probably the least risky option and you should choose a provider with a track record of providing reporting solutions that are ready to roll off the production line.

    2. Determine what trades are reportable, based upon instrument being traded

    At first glance it appears straightforward how to determine what instruments needs to be reported. Firms will be able to rely, to a certain degree, on the list that ESMA is mandated to provide under RTS 23. But even here there are significant implementation and operational issues with this list. For example, if it is not produced or there are issues with it then firms still have the obligation to report correctly, irrespective of the provision of the list.

    It become more complicated when you have to identify instruments which reference those traded or admitted to trading on trading venues.  How will firms identify and report the below examples?

    • Third country futures that reference instruments admitted or requested for trading on trading venue (RM, MTF or OTF)
    • OTC derivatives and 3rd country ETDs that reference instruments admitted or requested for trading on trading venue (RM, MTF or OTF)
    • How to identify, at the time of trade, the index constituents.

    Due to these inherent problems; determining which instruments are reportable becomes a materially more complex proposition compared to MiFID I, EMIR and DFA. Firms need to be working now with their counterparts, vendors and participate in discussions with their Trade Associations to put in place workable solutions.

    3. Establish what activity requires reporting

    Having figured out what instruments need reporting firms need to turn their attention to determining what activity is reportable. In short, take a look at RTS 22, Article 2 and the 14 different sets of activities that need to be excluded. The fact that many of these business activity exclusions have not been seen in EMIR, demonstrates again the material difference in the type of reporting solution required for MiFID II compared to previous reporting regimes. Firms will have to look at their trade data and ensure their reporting solutions are able to identify activity that should be excluded, as MiFIR does not allow for over-reporting.

    4. No LEI – No Trade

    Both the FCA and ESMA in recent public meetings have reiterated the point that firms must not trade with entities that do not have a LEI. This has been reiterated in the first MiFID II Q&A published by ESMA. There is considerable work for client onboarding teams and relationship managers to reach out to clients without LEIs and ensure compliance by 3 January 2018. Good luck!

    5. Short-sell calculation

    We will not discuss here the merits or otherwise of the short-selling requirement for transaction reporting (ok well, a little passing reference…suffice to say the value of this field is a best questionable.) Transactions in cash equities and government securities will require a calculation to identify transactions that take the firm short at any given point. Making an accurate calculation that takes into account late trade bookings and busts will be problematic and firms should not underestimate the time and cost that will be needed to ensure compliance.

    6. Under RTS 22, Article 15, ESMA high priests did say upon to firms, ‘thou shall test and reconcile one’s transaction reports….’

    Ok, maybe not as dramatically as that but ESMA now makes the obligation to test and reconcile mandatory under MiFIR. The important point to note is that controls are often the first casualty of delivery, as go-live approaches. For MiFID II this is not an option; firms need to ensure effective testing and reconciliations are in place at go-live. Failure to do so will be a breach. Looking to third party providers who have mutualised the costs of testing and reconciliations may make sense to ensure comprehensive and effective controls are in place prior to go live in 358 days time.

    There are many more items to add to the MiFID II Transaction Reporting to-do list.  Of course in the current environment there is no choice between which regimes you implement. That said, the complexity and the introduction of new demands on firms by MiFID II means it should be treated as the largest crocodile nearest the canoe when firms are planning their 2017 regulatory reporting delivery.

  • 2016: The reporting (Jean) Genie is well and truly out of the bottle

    2016: The reporting (Jean) Genie is well and truly out of the bottle

    David Bowie was many things to many people but a transaction reporting aficionado he was not. That said, in the year that saw the great man leave on his own “Space Oddity“, we use some of his most loved hits and lyrics to help us look back at reporting in 2016 …. and only hope he is not looking down to see us take such a liberty! David, we’re truly sorry…

    The reporting “Labyrinth” – new obligations

    Every year since the 2009 G20 Pittsburgh summit, which gave birth to the G20 reporting commitments, the industry has had to plan for and comply with new regulatory reporting obligations across the globe and 2016 has not been any different. Added to the “Labyrinth” of existing regulatory obligations, we have seen Canadian G20 reporting go live in July, the introduction of branch reporting in Hong Kong, and closer to home we have seen changes to EMIR reporting brought about by the introduction of clearing obligations. To cap the year off, firms will need their own “Heroes” working during the holiday season to make sure they can go live with Bank of Israel reporting on 1 January 2017!

    “Ch-ch-ch-ch changes”

    In regulatory reporting that has only recently gone live, 2016 has seen “Changes” or consultations on changes to their obligations. In accordance with Article 85(1) EMIR, the European Commission launched a review of the legislation on 21 May 2015 and published its final report on 23 November 2016.  As a result, the Commission has committed to a legislative review of EMIR in 2017 which will include an attempt to streamline trade reporting requirements.  In the US, we have seen no action relief expirations for CFTC DFA (Dodd Frank Act) reporting and the advent of SEC reporting drawing closer. The election of Donald Trump aligned with a Republican majority in the US Congress could mean substantial changes with the repeal of certain sections of the DFA in 2017 a distinct possibility.

    “Ashes to Ashes” for MiFID I transaction reporting

    As transaction reporting under MiFID I enters its final year, throughout 2016 firms have found themselves “Under Pressure”, trying to prepare for the much more demanding and complex ask of MiFID II.  Both buy side and sell side firms have been grappling with their understanding of the obligations imposed by MiFIR Article 26, the supporting RTS 22 and final guidelines.  The final guidelines document published in October represents a substantial investment by ESMA and the competent authorities.  Ana Fernandes of the FCA’s Transaction Monitoring Unit stood in public and compared the physical size of TRUP to the MiFIR guidelines. Her conclusion –  they have invested significant time and effort in the drafting of the regulations and supporting guidelines and their expectations of the standard of reporting is higher than that of  regimes that have recently gone live.  Throughout 2016 firms have been busy digesting what is required of them to comply with MiFIR transaction reporting obligations, realising it is significantly more complex than either EMIR or DFA.  In short, the significant increase in complexity of MiFIR reporting combined with the greater scrutiny of regulators means MiFIR could prove all-consuming for firms in 2017.

    Data Quality? Everything is not “Hunky Dory”

    As the year ended, the industry received messages both from the FCA and ESMA about the quality of the data that is being reported to them. Ana Fernandes and Olga Petrenko both struck the same chord at last month’s Transaction Reporting Conference at the BBA when they called out the poor quality of data still being reported.  Ana outlined that reporting under MiFID I, now live for nine years, still has significant errors – something that we highlighted when we analysed transaction reporting fines earlier this year.  Olga explained that ESMA is still receiving complaints from other bodies such as central banks about the quality of the data they are receiving from the reports made under EMIR.  Consequently, ESMA will have the improvement of data quality as its primary objective of 2017.  Both bodies are investing heavily to develop the capacity to identify data quality issues where they will increasingly compare reports, use independent sources of data, and introducing ‘business’ validations to identify errors and hold firms accountable in meeting their obligations.

    If these years are to be the “Golden Years” of reporting and less a “labyrinth” of competing demands, then the industry needs to invest heavily in accurate advice and appropriate solutions throughout 2017 so the quality of the data they report meets the increasing expectations of the regulators.

    There’s a lot to do as we head into 2017 but to soften the blow perhaps have a listen to Bowie over the festive season.

    Thank you for your support in 2016 and we wish you a restful break with your friends and family.

    Seasons greetings from us all at Kaizen.

  • Camels are horses: the problem of identifiers under MiFID II

    Camels are horses: the problem of identifiers under MiFID II

    This article was first published by Thomson Reuters Accelus (a subscription only service) on 21 November 2016. 

    We seem to be surrounded by questions of identity these days; a problem that was recognised and typified by the story of Theseus’s ship by the early Greeks. When Theseus and his young crew returned to Athens from Crete they did so in a ship with 30 oars. The ship was preserved by the Athenians down the ages by renewing the timbers as they decayed. Is this renewed ship, where none of the original timbers actually made the journey from Crete, still Theseus’s ship or has it become something different?

    Today we face this question of identity in a slightly different form in terms of nationality. Whether we are European or British, British or Scottish, and what determines nationality in any case. The topic “Mistaken identities” is the title of this year’s Reith Lectures by Professor Kwame Anthony Appiah. In his lectures, he looks at what gives people their national identity, a question firms will be faced with when trying to categorise their clients.

    In the regulatory sphere as well, questions of identity appear in several forms.  The Know Your Client (KYC) and Politically Exposed Persons (PEP) mean firms need to know that the person they are looking to deal with is who they say they are.  In reporting, firms need to identify who we are trading with; both individuals and companies. We also have to identify the traders within the firms themselves, and we need a way to identify the products being traded.

    This piece will focus on the question of nationality and the use of identifiers for individuals and companies under MiFID II and some of the challenges that this will bring. We will deal with identifiers for instruments at another time.

    MiFID II transaction reporting requirements seek to provide regulators with greater visibility of who is trading and who is making the investment decisions. This contrasts with MiFID where financial firms can often be identified with a global identifier (BIC or FRN codes) whilst other companies, partnerships and individuals are identified at a firm level using each firm’s internal identifiers. The lack of global identifiers makes it much more difficult for regulators to see what is going on across the market.

    Identifying individuals under MiFID II

    Under MiFID II ESMA has opted to use a suite of identifiers for individuals where the identifier to be used is to be based on the individual’s nationality. To my mind, it is unfortunate that they took a fragmented approach because it introduces an additional problem of what type of identifier to use, making reporting much harder. I presume this was a 28-country committee decision. As they say, a camel is a horse designed by committee!

    The requirements for identifying individuals are specified in the Regulatory Technical Standards (RTS) 22 and a table of the required identifiers by nationality is illustrated in annex II of the RTS. The annex tells you which identifier should be used for each nationality. The table in annex II tells you what to use once you know the nationality of your client or trader.

    Six of the countries opted to use the CONCAT approach as their only identifier. Other countries have elected to use national identifiers, passport numbers or tax numbers.

    What is CONCAT?

    As the name suggests CONCAT is a method to generate an identifier for individuals based on the compression or concatenation of four data elements:

    1. Country code (2 characters: ISO 3166-1)
    2. First name (first 5 characters padded with # where required)
    3. Surname (first 5 characters padded with # where required)
    4. Date of birth (YYYY-MM-DD)

    The CONCAT is comprised of these elements in the order shown.

    There is an argument that the four elements lack an important feature of an identifier, that of uniqueness. The cost of clashes, where two individuals are allocated the same CONCAT code, will be dependent on the frequency with which clashes occur.

    The process doesn’t end there. Before creating the CONCAT, the names need to be subject to a transliteration process to convert them into a common Latin alphabet by removing punctuation marks: apostrophes, hyphens, accents, and umlauts. Titles should also be removed as well as prefixes such as “Van” or “De” or “De la”. I am sure there will be questions where individuals treat the prefixes as part of a single surname: or example, where Delarue is used by the individual rather than De La Rue.

    What is the client’s nationality?

    “Firms must ask both new and existing clients whether they have multiple nationalities and to notify their firm if they acquire or lose a nationality.”

    Returning to the philosophical and social question of identity and nationhood: what is your client’s nationality? Rather than getting everyone embroiled in conjectures, ESMA has happily provided a waterfall approach to be used where individuals have multiple nationalities:

    1. For EEA countries use the first country ISO country code when it is sorted alphabetically
    2. Where there are EEA and non-EEA countries, the EEA countries take precedence.
    3. Non-EEA countries use the first country ISO country code when it is sorted alphabetically

    That means firms must ask both new and existing clients whether they have multiple nationalities and to notify their firm if they acquire or lose a nationality.

    Even then, we need to know each client’s list of nationalities which might not be so easy to determine. In my case, which I am sure is not unusual, I was born in Guernsey but have Italian and Irish parents which may complicate things. I am living in the UK but I have never been through any citizenship process. So in all honesty, I’m not sure what my nationality is.

    If I am a UK national, I would be identified using my national insurance number according to the table in RTS 22. But is it so simple?  I think I may have been registered as an Italian citizen and allocated a codice fiscal or Italian tax code.  So perhaps I would be classified as Italian, but I also used to have an Irish passport and I now travel on a Guernsey passport. So what nationalities do I have? I  have been told that anyone who has Irish parentage is eligible for an Irish passport. The problem is I am not actually sure what nationalities I have. As a client completing a form where I am requested to state all my nationalities I would have to do a significant amount of research just to determine how to fill in the form.

    To help address this, it might be an idea to provide industry guidance for the public on how to determine your nationality. ESMA has not, however, provided any guidance regarding what constitutes nationality for transaction reporting purposes. Does citizenship, tax residence, domicile, place of birth, a passport, all qualify? We need to know the answer to be able to arrive at the appropriate identifier to put in the transaction report.

    So taking my example, and assuming I am a national of the respective countries, you would get a table along the lines of something like this:

    Nationality

    Country code (ISO 3166)

    Identifier to use per annex II RTS 22

    Priority

    Basis

    British

    GB

    National Insurance number

    1

    First EU country alphabetically based on country code

    Guernsey

    GY

    Passport

    4

    Not an EU state.  EU states take precedence.

    Irish

    IE

    CONCAT

    2

    Second EU country alphabetically based on country code

    Italian

    IT

    Codice fiscale

    3

    Third EU country alphabetically based on country code


    In a post-Brexit world, the identifier to be used would change because the UK would switch from being an EU state to a non-EU state. Whilst my nationalities haven’t changed, the status of the UK has.  Reapplying the logic to compute the appropriate identifier to use would produce the following:

    Post-Brexit implications
    If there are any EU nationalities, they take precedence over non-EU nationalities. The first EU nationality of the country code when sorted alphabetically is used in that scenario. In this case it would be GB.  Looking at the table in RTS 22 annex II then shows that the UK requires a national insurance number, as its primary identifier.

    Nationality

    Country code (ISO 3166)

    Identifier to use per annex II RTS 22

    Priority

    (post Brexit)

    Basis

    British

    GB

    National Insurance number

    3

    Not an EU state.  EU states take precedence.

    Guernsey

    GY

    Passport

    4

    Not an EU state.  EU states take precedence.

    Irish

    IE

    CONCAT

    1

    First EU country alphabetically based on country code

    Italian

    IT

    Codice fiscale

    2

    Second EU country alphabetically based on country code

     

    The table above shows that this is not going to be a simple process. It however, will go beyond just clients.

    Beyond clients

    Within the MiFID II transaction report there are a number of fields which may require an individual to be identified. Not all of these will be clients.

    Field no.

    Field name

    Type of individual

    7

    Buyer identification code

    Client

    12

    Buyer decision maker code

    Client or representative

    16

    Seller identification code

    Client

    21

    Seller decision maker code

    Client or representative

    57

    Investment decision within firm

    Trader

    59

    Execution within firm

    Trader

     

    Where there is some sort of power of representation in place, that party will also need to be allocated an identifier using the same process if they are to place trades on behalf of the account. Traders within the firm are also caught.

    Identifying businesses under MiFID II

    A much simpler identifier is in place for businesses. MiFID II requires all parties operating a business to be identified with a Legal Entity Identifier (“LEI” code). I say “operating a business” and not “companies” because any party eligible for an LEI under the LEI allocation rules must be identified with an LEI. Under these rules an individual operating a business as a sole trade or as a local is eligible for an LEI.

    “The regulations require firms to have an LEI in their possession before entering into a trade with a client or counterparty or on behalf of their client.”

    No LEI no trade

    This gives rise to the ‘no LEI, no trade’ rule. At present, the regulations require firms to have an LEI in their possession before entering into a trade with a client or counterparty or on behalf of their client. This can be extended to the decision maker fields for representatives under a mandate or power of attorney.

    A legal firm operating for an account will need to register for an LEI. Registration can be made on behalf of a third party or client where they give authority and the information needed to do so. Costs are currently around £100 per LEI and £55 for renewals – required after two years depending on the number of LEIs being registered.

    LEI status

    There are several statuses that an LEI can have. Reporting firms must use an “active” LEI in the executing entity field which are: “Issued”, “Pending transfer” or “Pending archival”. For clients and representatives, they must have registered for an LEI which can be one of the following statuses: “Issued”, “Lapsed”, “Pending transfer” or “Pending archival”.

    Branches

    Branches should be identified with the LEI of their head office, certainly until such time that the proposed branch level LEIs are issued.

    What should firms be doing now?

    Firstly, firms need to test their existing client and counterparty static data (including representatives) to check they have correctly captured LEIs that are already in issue. Then they need to conduct a reach-out exercise encouraging them to obtain an LEI. If you have a lot of clients, you may not want to shoulder the cost of registering an LEI for them. This however could be deemed to be an inducement and may be considered contrary to the inducement rules set out in MiFID II so firms should tread carefully.

    For individuals, a reach-out exercise is needed to collate nationalities and associated identifiers, then the appropriate identifier needs to be determined.

    Mapping client and counterparty accounts to the LEI dataset is a complex activity. At Kaizen, we have been working on LEIs for more than two years, developing solutions that address the challenges associated with mapping identifiers for both individuals and businesses. The LEI dataset itself is not without its problems as it uses multiple alphabets and contains duplicate records and entities with common legal names within its dataset. Building this assessment capability in-house will be an expensive and time-consuming exercise. In addition, this will need to be carried out on a recurring basis as new LEIs are being registered daily.

    As with all regulations, the philosophical and the practical collide, leaving firms with the challenge of accommodating the two.

     
  • The good, the bad and the new: Final MiFID II transaction reporting guidelines

    The good, the bad and the new: Final MiFID II transaction reporting guidelines

    It was a big day in the world of regulatory reporting on Monday (10 October) with the publication of what is expected to be the final version of ESMA Guidelines for MiFID II transaction reporting.

    These guidelines are very important because they establish an obligation on financial market participants who “shall make every effort to comply with those guidelines and recommendations.”[ref]Article 16(3)of Regulation (EU) no 1095/2010 of the European Parliament and of the Council[/ref] Failure to comply with the guidelines will be considered a breach of the transaction reporting requirements.

    The guidelines are extensive so we’ve carried out an initial review of the 280-odd pages and a quick comparison to the previous version focusing on the transaction reporting requirements.

    Our take? Well, the good news is that ESMA has answered a lot of questions. The not-so-good news is that many questions still remain unanswered.  The bad news is that the guidelines have thrown up some new questions.

    Here are our immediate observations (there will be more to come once we’ve had more time to plough through and analyse all the changes).

    Identifying natural persons

    There have been some changes to identifiers for individuals which we think will be welcomed by the industry:

    1. Person identifiers: no longer requires firms to monitor for the expiry of identification documents such as passports.
    2. Clarification of how to determine nationality of individuals with multiple non EEA nationalities is by the first country code when sorted alphabetically.
    3. Introduction of an exhaustive list of name prefixes where these are to be removed when constructing the CONCAT identifier.
    4. Name and surname fields are now to allow the original country spelling so transliteration is not required for these fields.

    Who is the decision maker?

    This is the key question that competent authorities need to answer when undertaking surveillance for market abuse. As such, this is key information in the transaction report and ESMA has provided further clarifications and examples in the scenarios for the various decision maker fields including reporting chains which will prove very useful when mapping out the reporting logic.

    Reporting trades against fund managers has been clarified

    ESMA clarifies that they are looking for the decision maker. Therefore, where there is a transaction on the instruction of the fund manager, the fund manager will be the buyer and the decision maker field is left blank as it is one and the same party.

    Where execution is determined outside of the reporting firm then the “execution within firm” field should be populated with “CLIENT”. Similarly, where executions are filled by an order management system then this should be identified with an Algo identifier.

    Venue identifier

    The original guidance and RTS 22 indicated that all trading that was not directly on venue activity would be reported as XOFF. Unfortunately, the latest guidance suggests a move back to the MiFID I approach where the venue MIC code must be used when a trade is executed under the rules of a venue.

    “The buying and selling interest of two parties is not brought together by the Trading Venue either on a discretionary or non-discretionary basis, but the transaction is nonetheless subject to the rules of that Trading Venue and is executed in compliance with those rules.”

    ESMA confusingly goes on to say,

    “Where an Investment Firm is not the direct market facing entity the Investment Firm is not regarded as executing on the Trading Venue for the purposes of transaction reporting.”

    This seems to contradict the prior statement. The examples provided, however, do make clear that where the parties to a transaction agree that it is executed under the rules of an exchange or trading venue then the venue field should be populated with the MIC code of that exchange or trading venue.

    Short-selling flag

    Only real change here is that aggregated client orders do not require a short-selling flag to be populated as it relates to multiple clients. Transaction reports that show individual client-side activity will need to be populated based on the each client’s overall position in the traded security.

    ESMA has also clarified in the examples that the short-selling flag is only required for uncovered short sales of shares and sovereign debt instruments per articles 12, 13 and 17 of the short selling regulations.

    Cancellation of transaction reports

    ESMA has clarified that only the “key” fields 1, 2, 4 and 6 are to be submitted in the cancellation report. Inclusion of additional field information will result in a rejection of the cancellation report.

    Identification of the underlying instrument

    Surprisingly, ESMA has asked that where there is a derivative on a derivative (an option on a future on an equity, for example) the direct underlying should be identified i.e. the future rather than the equity.

    This raises the question of reportability. Are they suggesting that underlying refers to only one level down and when assessing reportability, there is no longer a look through to the ultimate underlying? For example, an option on an ADR on BT shares would not be reportable because the look through only goes down one level to the ADR? While when assessing the ADR you would look through one level to find BT shares and conclude the ADR itself is reportable? In the case where the immediate underlying is a future on a third country exchange that doesn’t use ISIN to identify its products means that the underlier field cannot be populated again – does this suggest that ESMA now considers such instruments as not reportable?

    Equity swaps and instruments reported with two separate transactions reports

    There has been an amendment to the approach ESMA wants to see for instruments which have multiple legs such as equity swaps. ESMA has compressed the two legs of an equity swap into a single transaction report using + and – to flag the buyer and seller of the legs. Previously in the consultation paper ESMA expected two transaction reports which were to be linked using the complex trade ID field.

    Similarly, for equity swaps the ISIN code for each equity leg is included in underlying instrument field with a + for the buyer (receives the performance) and – for the seller (on the equity leg that where they pay the performance).

    Similarly, where a benchmark is exchanged for equity performance the benchmark is identified in the “Underlying index name” field with a + or -.

    Other things of note:

    • Transfers are further defined in the text.
    • Changes in ownership structure are reportable.
    • Units of funds are not financial instruments and therefore not reportable.
    • Transactions for the creation and redemption of funds are only excluded where they are directly with the fund administrator. This was in the prior version of the guidance but it is now much clearer.
    • Identifying buyer or seller for trusts has been amended to be consistent with the approach taken for firms.

    What’s not addressed
    Outsourcing – do you need to be an ARM?

    There is an open question being debated by lots of different interested parties. The suggestion by ESMA had been that where a firm uses a central reporting hub to generate the transaction reports for all the reporting entities in its group that firm would have to register as an Approved Reporting Mechanism or ARM. Similarly, parties that stood between the reporting firm and the ARM providing reporting services would also be required to become an ARM.

    The guidelines clarify that

    “No requirement for a receiving firm to become an ARM. There was request for confirmation that a receiving firm reporting details transmitted by a transmitting firm did not need to become an ARM. ESMA confirms that that is not an outsourcing arrangement as the receiving firm is making its own report and it is not required to become an ARM. A statement on this has been included in the relevant section of the Guidelines.”

    From this it does imply that any form of outsourcing type arrangement involving your transaction reporting activity may require the supplier of the service seeks ARM status. This is not black and white and my suspicion is that this issue is still under discussion behind the closed doors at ESMA. What they have been able to do is rule out a scenario for receiving firms in the reporting chain to be ARMs.

    My view is that extension of the ARM regime beyond entities seeking to submit transaction reports directly to a competent authority on behalf of third parties will be unworkable.

    To conclude

    The above is by no means an exhaustive list – as always, the devil will be in the detail. Firms should be looking to see if their request for additional scenarios (as requested in the consultation paper) has been appropriately addressed.

    Do share with us here at Kaizen your initial reaction to the guidelines and anything further you’ve discovered so far. As mentioned, we will post a more thorough analysis once we’ve had more time to digest.

    Happy reading!

  • FCA provides timeline for MiFID II testing services

    FCA provides timeline for MiFID II testing services

    The FCA has published details of how interested parties can register to connect to their MiFID II data submission service and has also announced that they will provide testing facilities six months ahead of MiFID II go-live.

    The Market Data Processor (MDP) service replaces the current transaction reporting system Zen and will be operated and supported by a third party, Sopra Steria. The MDP also provides the mechanism for other Data Reporting Service Providers (ARMs, APAs and CTPs), trading venues and systematic internalisers to submit the instrument reference data required under RTS 23 and trade data required by ESMA to calculate the double volume cap as per RTS 3.

    Some parties such as our partner UnaVista are developing services to support MiFID II including an instrument static submission service so parties won’t have to register and pay the connection and annual fees to use the MDP service directly. In addition to a substantial cost saving, it has the benefit of validating the data before submitting it to the FCA.

    The MDP service specifications will be available to registering parties from the end of September and from Q4 for commodity position reports. A test environment will be available from 1 July 2017 allowing connecting entities and those further down the chain a good deal of time to undertake comprehensive testing prior to the MiFID II go-live date of 3 January 2018.

    Sopra Steria will also be managing the data extract service. This is the mechanism by which samples of submitted transaction reports can obtained for testing the veracity and completeness of the submissions. This process is expected to be conducted by all reporting firms as part the controls required to comply with RTS 22 Article 15 paragraph 3.

    Useful link: MiFID II Regulatory Technical Standards.

  • FCA publishes second MiFID II consultation paper

    FCA publishes second MiFID II consultation paper

    The FCA has published its second consultation paper (CP 16/19) on the implementation of MiFID II.

    This consultation paper covers a range of issues including position limits and reporting for commodity derivatives, systems and controls requirements for firms providing MiFID investment services and client asset protections.

    The FCA’s CEO Andrew Bailey, reiterated the importance of firms continuing on with their MiFID II preparations despite the outcome of the EU referendum.

    “MiFID II contains important measures to enhance investor protection and bolster financial stability. It reflects recent themes of UK conduct regulation, such as improved controls on the manufacturing and distribution of financial products, and it implements the international commitments the UK entered into to reform derivatives markets following the financial crisis. As we said in our statement following the EU referendum, firms must continue to abide by their obligations under UK law, including those derived from EU law and continue with implementation plans for legislation that is still to come into effect,” he said in a statement.

    The FCA published its first consultation paper on MiFID II on 15 December 2015 (CP15/43) and there will be a further consultation paper later this year.

    The closing date for responses to consultation paper CP16/19 is 28 October 2016.

    MiFID II comes into effect on 3 January 2018.

  • Will Brexit lead to a TRexit?

    Will Brexit lead to a TRexit?

    I spent some time last weekend catching up on the arguments for and against a Brexit. It got me thinking about the implications for reporting for firms in the UK. Now that the UK has voted to leave, will it have a major impact reporting-wise? Will obligations significantly reduce? I’ve come to the conclusion that in the main, I think Brexit will have very little impact on regulatory reporting. Here’s why:

    A transparent market is the ultimate aim

    Having seen the regulatory process and the development of transaction reporting legislation from inside the (then) FSA, my thinking is this: the UK needs clean markets to attract capital. To that end, the FCA has been at the forefront in establishing the transaction reporting regime in Europe as well as its shape under MiFID II. Clean capital markets will be even more important to the UK under a Brexit scenario so I fully expect that the UK would maintain a near identical transaction reporting regime. This could even include negotiating the ongoing exchange of transaction reports with our European neighbours under the existing MiFID model assuming that MiFID II is not adopted in full as a member of the EEA.

    Passporting

    Where an impact is more likely is for firms passporting into Europe today and they will be anxious about the future of their licence. Dependent on the outcome of negotiations on transaction reporting exchange, passported firms may have to report to their local competent authority (as today under MiFID I) and may lose the benefits of centralised reporting set out under MiFID II.

    Similarly, incoming branches to the UK may end up with a double reporting obligation to the UK and to their home competent authority. This would be more of a challenge were reporting obligations to differ between the UK and Europe but if they remain harmonised it reduces to a routing rather than a reporting problem. These risks I feel, will be addressed with a practical solution. After all, transaction reporting exchange is in place to provide that holistic view of activity on our markets. Without an agreed exchange, the FCA is likely to require market operators to report for members who do not have a UK transaction reporting obligation and similarly from the EU’s perspective.

    What about EMIR?

    For EMIR it is a similar story. EMIR needs to be global, not just European, if the data is to be useful for identifying emergent risks to the financial system: its primary aim. ESMA is currently working with Trade Repositories to standardise how information is made available to the array of regulators that have access rights to this information. Creating a UK specific regime, however well designed, would be an unwelcome complication for firms and Trade Repositories.

    Dual-sided vs single-sided

    Recent EMIR discussions have been around dual-sided vs single-sided reporting. My view is very pro dual-sided between financial counterparties as this goes a long way to promoting reporting quality. That said, for those non-financial counterparties delegating reporting to their broker, there is very little benefit for reporting quality of dual-sided reporting so this could easily be dropped. Similarly, many of the larger firms have created centralised reporting solutions and would not welcome divergence from the EU requirements, creating yet another distinct reporting obligation.

    So all in all, due to the added complications, and the UK having been a chief instigator in tougher reporting measures, I expect that the reporting world will continue very much in the same vein despite the UK voting to leave the EU.

  • Why data quality is key to regulatory reporting compliance

    Why data quality is key to regulatory reporting compliance

    The FCA has used its latest MarketWatch newsletter to remind firms of their transaction reporting obligations, the persistent poor quality of their reporting, and that the FCA have mechanisms in place to detect errors which may result in stringent actions such as fines.

    While this message isn’t new, the FCA has also published a table showing approximately 650,000 data quality breaches across the industry over a one-week period where the FCA’s Transaction Monitoring Unit (TMU) tested only four of the transaction reportable fields. It will be a disappointment to the FCA that in each instance the errors are ones previously made by firms sanctioned for incorrect transaction reporting as well as errors highlighted in previous Market Watch newsletters. These include things such as late reporting of transactions, incorrect MIC codes, wrong execution times, wrong quantity or missing unit price.

    Just the tip of the iceberg

    The one-week snapshot by the FCA does not reveal the true size of the problem.  We took a closer look and analysed in detail the findings of the publicly available fines issued to firms for incorrect transaction reporting since 2009.  Our findings are displayed in the graphic above.

    1. Tip of the iceberg: Maybe not the perfect analogy, but for those firms fined and where information is publicly available, we found only 35% of the firm’s reportable transactions were reported accurately and completely. That is to say, passed ARM validation and the data was correct.
    2. Base of the iceberg: That leaves 65% of the firms’ reportable transactions being reported incorrectly or not at all. In all cases, firms did not have appropriate controls in place to identify and test the correctness of their reports. In short, they were unaware that the majority of their reports were incorrect.

    Only 7% of the transactions were not attempted to be reported or were duplicates.  All of the remainder were breaches where the report passed validation but the data was incorrect. In other words, they were ‘valid but wrong’.

    Transaction reports must be tested at source

    What this tells us is that firms need testing at source not just ARM validation. Even after eight years of MiFID transaction reporting, numerous warnings and increasing fines from the FCA, significant numbers of transactions are being reported incorrectly with firms unaware of their inaccuracies. In addition, firms are deriving false confidence from passing the validations provided by ARMs and the FCA.

    Importance of getting reporting right

    In Market Watch 50, the FCA TMU makes it clear that they see failure to produce current MiFID reports of good quality as an indication on how well a firm can meet its future and more complex obligations under MiFID II/R and in part, compliance with the recently introduced Senior Managers Regime.

    It says: “The ability of firms to submit accurate and complete transaction reports is essential if they are to be in a strong position to meet the more complex requirements of MiFIDII/R.” It also reminds firms: “If we continue to find firms that fail to identify or mitigate risks associated with market abuse then we will take stringent action against those firms. These actions could include penalties such as fines.”

    This echoes the warnings raised by the FCA in all of the public fines for transaction reporting. The obligation to make complete and accurate reporting is also unambiguously clear through the FCA Handbook (SUP 17) and the Transaction Reporting User Pack (TRUP 3.1).

    Detecting market abuse

    In Market Watch 50, the FCA also reminds the industry of how important a tool transaction reporting is to allow them to detect market abuse.  Poor quality data directly affects the ability of the FCA, European competent authorities and other regulatory bodies such as the Bank of England to detect market abuse or carry out their supervisory responsibilities.

    Where to from here?

    The picture illustrated by the fines for transaction reporting is one where a large majority of reported transactions have passed high levels of validation but the data is still inaccurate. Failure by firms to report correctly is a major industry problem. Firms need to change their approach to protect themselves under the current MiFID regime and the upcoming MiFID II/R in 2018.


    Kaizen’s ReportShield™ accuracy testing checks transaction reporting data at source and identifies transactions successfully submitted to ARMs and the FCA but still wrong.  An independent, managed service, ReportShield is already being used by a number of firms to provide reporting assurance and deliver confidence to management and the regulator. The service significantly reduces risk to firms, offers protection to managers who have SMR responsibilities, and is delivered at a significantly lower cost than testing in-house.

  • Collateral transfers are to be explicitly excluded from MiFID II transaction reporting

    Collateral transfers are to be explicitly excluded from MiFID II transaction reporting

    ESMA has published a final report on RTS 22 which seeks to amend the original drafting to explicitly exclude collateral transfers.

    The potential introduction of collateral transfers as reportable transactions was of significant concern to the industry so this development will be warmly welcomed.

  • Updates From The Deutsche Boerse Buy-Side Working Group

    Updates From The Deutsche Boerse Buy-Side Working Group

    Stephen Hanks from the FCA provided some interesting feedback about MIFID II progress at the Deutsche Boerse Buy-Side Working Group (April 21) which we were speaking at and attending. We wanted to share some of the key points we learned at the event.

    Broad points of interest:

    • The finalised delegated acts for MiFID II should be published next week (week commencing 25 April) closely followed the week after with MIFIR delegated acts.
    • The FCA advised that with regards to the waiver volume caps, the debate continues around the appropriate calculation approach. This highlights the ongoing industry concerns regarding these caps being exceeded and all activity in a security being fully lit. As discussed at the working group, it is too early to assess the impact this could potentially have.
    • Questions also remain about principle trading by an institution operating an MTF and what the firm operating the MTF could put through the platform.
    • The FCA also suggested that EU level discussions implied that systematic internalisers would not be able to use matched principal activity as their primary trading model on the SI platform as such activity is considered to fall outside the purpose of the SI regime. The FCA advised that questions also around price improvement under the SI regime should also be dealt with in the delegated acts to be published in the next couple of weeks.

    From a transparency perspective the FCA provided the following comments:

    • Regarding the establishment of a CTP for equity securities, no indications of interest have been received by authorities from potential service providers.
    • For non-equity securities there will now be a phased approach for SSTI.
    • The FCA confirmed that size thresholds for bonds and the present 100k euro threshold was also being looked at by ESMA.
    • As per recent statements, ESMA will also be producing new advice for non-equity transparency.

    From a transaction reporting perspective:

    • ESMA is also reviewing the definition of an ARM and what activities would trigger the requirement to register as an ARM. Debate has been raised as a result of there being unregulated intermediaries conducting key activities between the regulated firm and its ARM. This would mean that regulators would only have locus over a portion of the process and not all of it.
    • The FCA advised that although there are questions around the benefits of including ‘short selling’ flags in the transaction report, this will remain a requirement.

    The main take away here is clearly the timing around the publication of the finalised acts. This will firm up requirements being created under the legislation. Those managing the MiFID II projects have been waiting for the acts to be finalised to progress the work required which is significant for all financial firms. The acts are also bound to raise further discussion points and once published, will provide the platform for progressing with the Level 3 work.

  • Continued uncertainty around future transparency under MiFID II

    Continued uncertainty around future transparency under MiFID II

    The European Commission’s late pushback on MiFID II will cause the industry further headaches and has not surprisingly frustrated ESMA.

    Last week, the Commission rejected three of the 28 MiFID II technical standards asking ESMA to take another look at them.

    ESMA has responded in three open letters, saying it will get to work straight away but has made it clear that the Commission has not followed procedure and should’ve got back to it by the end of December, not nearly three months later.

    One of the issues the Commission has asked for a rethink on are ESMA’s proposals for bringing more transparency to the bond markets – something we here at Kaizen are particularly interested in.

    Damage to liquidity

    The Commission’s concerns around bond market transparency are consistent with the views of the industry. The minutes of the FCA’s recent trade association roundtable highlighted not just worries from a bond market perspective but whether appropriate and equal consideration is being applied to the other asset classes coming into scope for transparency under MiFID II such as derivatives. The new regulation is clearly attempting to remove the opaque nature of these sectors. However arguments continue that the MiFID II RTS as currently drafted would potentially damage liquidity and would in fact be harmful to liquidity providers. The Commission has clearly acknowledged these concerns and ESMA is now revising its approach.

    Further challenges for implementation

    Although a rethink on MiFID II transparency may initially appear positive, for the industry as a whole it creates further problems. Without clarity on these standards, firms will have to make broad assumptions around the current guidance as they progress with MiFID II implementation. It is unclear how long it will take ESMA to review, but the European Parliament has been clear that further delays beyond 3rd Jan 2018 are not an option and the deadline must be met.

    Considerable challenges

    ESMA’s response not surprisingly has highlighted the ongoing frustrations that exist in this extremely delicate and challenging area.

    ESMA’s letter reveals that the Commission views the current transparency proposals on calculating liquidity inappropriate and that more frequent, timely calculations are required. It is understandable given that within the new market sectors liquidity fluctuates dramatically over short periods and a liquid security can rapidly move to being illiquid. ESMA has already faces considerable challenges sourcing the data to calibrate the regime as the MiFID only gives them the power to obtain transparency data post MiFID go-live.  In recognition of this conundrum the draft text proposes all FX derivatives be classified as illiquid for the transparency reporting obligations until such time as ESMA is able to source and assess more meaningful data.

    Developments here will need to be closely monitored as small changes in the regulations have the ability to create a major impact on MiFID II projects.

  • Five things we learned from the FCA’s MiFID II venue roundtable

    Five things we learned from the FCA’s MiFID II venue roundtable

    FCA’s MiFID II trading roundtable have been published. What did we learn?

    • ESMA Level 3 Q&As will not be published until the implementing measures are finalised. Given what now appears to be an inevitable delay of 12 months, the guidance could be significantly delayed as questions remain outstanding in several key areas such as transparency for non-equity securities.
    • The FCA advised that their own second MIFID II consultation paper was likely to be published in the middle of 2016. Again the exact timing of this depends upon the progress with the implementation measures.
    • Venues continue to stress concerns about the new obligations.  For example, where the entity utilising their services is not obliged to report and therefore creates an obligation upon the venue to report the activity executed to meet reporting obligations.  Further clarification is still required here however clearly this creates a significant onus upon the venues that does not exist today. The FCA did confirm as per their guidance that a venue would be expected to report such activity to their home member state.
    • The effective processing of transparency waivers is also a significant concern to venues. The FCA confirmed that interfaces are in place between it and ESMA which allow for batch processing to assist with the timely processing of waiver applications. Waivers will need to be in place for each venue for market participants to utilise the appropriate exemptions and deferrals from publication requirements.
    • Under AOB the FCA was questioned on the approach towards direct market access (DEA) by 3rd country clients (non-EEA). The FCA advised there are a couple of key considerations here. It confirmed questions have been raised with the European Commission about exemptions in Article 2.1 (d)  for those dealing on own account with DEA access based outside EU. With regards to firms based outside the EEA providing DEA access, the FCA confirmed that the consultation paper followed the Treasury implementation legislation which did not permit firms based outside the EEA from providing access to EEA trading venues.
  • MiFID II fee proposals – how will they impact you?

    MiFID II fee proposals – how will they impact you?

    Feedback on the FCA’s fee proposals to recover the costs of submitting data under MiFID II is expected to be released shortly.

    The consultation began in November and finished early last month.  The proposals may have slipped notice however the fees will need to be included in the budgeting process going forward and may significantly impact smaller commodity derivative trading firms and firms that are (or are considering) becoming operators of a trading venue.  The proposals are summarised below and will be of interest for firms that will operate an MTF, OTF or a regulated market under MiFID II as well as firms executing commodity derivatives or acting as a systematic internaliser.

    More transactions, higher fees

    Whilst the costs are not excessive, if firms submit reports directly to the FCA the costs are likely to be prohibitive for smaller firms pointing to the need for intermediaries such as Approved Reporting Mechanisms (ARMs) to aggregate submissions, particularly for commodity position reporting.  The consultation paper doesn’t provide any hint as to the ongoing maintenance and administration costs to run the service but this is likely to be substantial.  The consultation proposes that these costs are raised from the ‘relevant firms that benefit from effective market reporting’.  It is not clear what they mean by this but I suspect they are referring to a per report fee that will be levied on the firms for which the report has been made.  So that means the more transactions, the higher the fees.

    Data Reporting Service Providers

    MiFID II creates a new type of entity called the Data Reporting Service Provider (DRSP).  This category encompasses ARMS, Approved Publication Arrangements (APAs) and Consolidated Tape Providers (CTPs).  Each of these entities require authorisation by a competent authority under the DRSP regulations but in addition, as they have to submit data to the competent authorities, they need to connect to the competent authority’s systems.

    To capture this data the FCA is looking to appoint a Market Data Processor (MDP) who will manage the connectivity and processing of the above data.  The costs of the MDP, authorisations and ongoing supervisory activities have to be recovered.  The FCA’s fee consultation paper sets out their proposals in this regard.

    FCA application fees

    There is a separate fee structure proposed for DRSPs (ARMs, APAs and CTPs) as they are regulated outside of FSMA (The Financial Services and Markets Act).  The DRSP fees will not apply to entities that are “incoming” DRSPs.  Incoming DRSPs are ARMs, APAs and CTPs that are authorised in another EU jurisdiction.  Incoming DRSPs will have to contribute to the costs of connecting to the FCA’s systems but will not face application fees.

    Investment firms providing DRSP services will incur the DRSP fees in addition to their FSMA fees.  Such applications will not be treated as variation of their existing permissions but as full applications as it is under a separate regime.

    FCA periodic fees

    Periodic fees have been proposed as a new G25 fee block for DRSPs.  Rates will be confirmed once the FCA’s costs are better known.  The periodic fees apply for the first quarter pre MiFID go-live as a flat rate fee of £20-30k for each authorised DRSP.  Where the DRSP is authorised for more than one category, e.g. as an ARM and an APA, the proposal is an additional 50% of the periodic fee for each additional DRSP category.

    The tables below set out the proposed fee structure.  If the fees collected fall below the costs incurred overall by the FCA then the difference will be collected via periodic fees.

    FCA DRSP fees

    [supsystic-tables id=’2′]

    FCA data submitter on-boarding fees.

    Only one connectivity/on-boarding fee would be applicable for the MDP.  So if a firm is connected for transaction report submissions they would not have any additional on-boarding fee for other data types.

    [supsystic-tables id=’3′]

    FCA ongoing transactional fees

    It is not clear how the regulator’s ongoing costs of operating the reporting system will be recovered but we anticipate that there will be a fee per transaction report made.  This could be levied directly on the parties submitting to the FCA, principally the ARMs and trading venues and if so, these parties are likely to pass through these costs to their clients, the reporting firms.

    *subject to change

  • MiFID II delay confirmed but there’s no time to waste

    MiFID II delay confirmed but there’s no time to waste

    The European Commission has confirmed the MiFID II implementation deadline has been extended by a year to 3 January 2018.

    While this isn’t in any way surprising, the clarity is welcome news for the industry after ESMA initially proposed a delay in November. The Commission says the delay is to ‘take into account of theexceptional technical implementation challenges faced by regulators and market participants.’

    Twenty-two months is still a very short time for firms to complete all the changes required for MiFID II.  Given the significant size and scope of the new reporting requirements – affecting a much larger group of market participants – those affected should take action now if they haven’t already done so to get themselves ready. 

    A year’s delay may seem like a long time but firms should not take their foot off the pedal.  The reprieve to 2018 means it is likely that regulators will have less tolerance for those who do not meet the new reporting requirements from the get-go.  In addition, those who leave it to the last minute may find themselves with much higher implementation costs.

    We can help firms prepare for the new transaction reporting requirements required under MiFID II from getting your transaction reporting in order through to bespoke training on the new requirements.

    Contact us to find out how we can give you MiFID II peace of mind.

  • ESMA Data Portal Changes

    ESMA Data Portal Changes

    Firms subject to MiFID and other regulatory reporting obligations should be aware that ESMA is migrating its current data register to a new portal.

    These changes will be of particular interest and relevance to compliance and operations teams.

    The existing portal will be removed from 1 April.  The migration impacts the following published data sets which will have a direct impact on validation to ensure compliance with regulatory reporting:

    • Published list of shares admitted to trading on regulated markets
    • List of exempted shares
    • Register of systematic internalisers
    • List of authorised regulated markets
    • List of authorised multilateral trading facilities (MTFs)
    • Central counterparties

    To enable a smooth transition, ESMA is making the data register available on both portals for the rest of February and until the end of March.  As of 1 April 2016 the old portal will be shut down and not accessible.

    Firms that have established automated access to these lists should refer to the updated web service procedure ESMA has published.

    Developers responsible for the automated processes adopted in respect of the datasets should review the information detailed on ESMA’s website.

  • It’s crystal ball time – regulatory reporting in 2016

    It’s crystal ball time – regulatory reporting in 2016

    As the memories of performances of A Christmas Carol fade, the ghosts of Christmas past, present and future are a useful analogy to convey the challenges firms will encounter in meeting their regulatory reporting obligations in 2016.

    From the past, MiFID reporting of the 2007 vintage still provides a real and present risk to firms. The present, in the form of EMIR and DFA reporting, will undergo changes to requirements. Looking to the future there are a number new obligations that are due (REMIT, Money Markets) and significantly, the highly likely delay of MiFIR/MIFID II to 2018. A common theme running through all obligations is the increasing levels of scrutiny from regulators and therefore of firms’ senior management.

    Past

    Despite all the focus and costs expended upon the new reporting obligations globally, still the most material risk to firms in getting their reporting wrong is UK transaction reporting required under MiFID since 2007. Last year we saw fines break new records, reaching GBP£13m and it is not inconceivable that in 2016 firms may receive higher fines. It is crucial that firms do not take their eyes off the ball so that they continue to adhere to legacy reporting requirements.

    Present

    The introduction of EMIR and DFA obligations over last few years is still fresh in the minds of regulators, trade repositories and firms. In 2015 EMIR reporting has seen significant change with ESMA mandating trade repositories to introduce much higher levels of validation on firms’ submissions. In the year ahead we expect to learn of further significant changes to EMIR reporting obligations as a result of both the consultation of 2015 and knock-on effects of EMIR clearing. For those firms who have a DFA reporting obligation, the later part of 2016 will see changes to CFTC Part 45 rules as part of the rewrite. Firms will need to plan for changes to obligations that have only very recently been introduced.

    Future

    Wherever you look, there are new reporting obligations with compliance dates in 2016. In the energy markets, REMIT OTC obligations are due in the second quarter. In the third quarter Switzerland is set to introduce its version of EMIR. Despite the advent of trade repositories, the central banks are requiring their own reports. In the second and third quarters of this year, the Bank of England and the European Central Bank are requiring money market reports. MiFIR/MIFID II is the one omission from the list, due to the highly likely scenario that it will be delayed from January 2017 to January 2018. Despite this delay preparation for the MiFIR requirements for transaction, trade reporting and instrument data reporting will dominate the change agenda for 2016/17.

    Common theme – increased scrutiny

    Regardless of whether the reporting obligation is a legacy requirement, recently introduced, or with a compliance date in 2016/17, the expectations and scrutiny of regulators is only on an increased trajectory. As such, expect increased fines for those more mature reporting regimes (MiFID). For more recent regimes, fines (DFA) have already been issued or greater scrutiny from regulatory bodies is becoming evident (EMIR). Future reporting regimes will be expected to hit the ground running with high quality reports expected from the get-go. The importance of ensuring correct reporting has never been as important to firms and the financial system as a whole.

  • ESMA gets in just before Santa to consult on clocks, data, records and reporting under MIFID II

    ESMA gets in just before Santa to consult on clocks, data, records and reporting under MIFID II

    ESMA’s consultation paper on some MIFIR/MIFID II guidelines were delivered, as promised, before Rudolph had his harness fitted. Well… just about.

    Those still at their desks on 23 December were left scratching the heads on whether they had been naughty or nice as they began to pore over 269 pages of guidelines on transaction reporting, reference data, order keeping and clock synchronization. 

    You may be relieved to hear that we will not be going through all 269 pages in detail in this blog (and there’ll be no more Santa related puns). Instead we look to set this document in context, explore its usefulness, its purpose, and briefly summarise the structure and content.

    Context

    The publication of the consultation paper continues the exercise of adding further granularity to the obligations required under MIFID II/MIFIR and then built upon under ESMA Regulatory Technical Standards (RTS) 22, 23, 24 and 25.  On page 7 of the consultation paper ESMA explains that:

    “…this guidance complements the technical standards and will be essential for the consistent implementation of the new MiFIR rules.”

    Are they useful?

    Considering the already published details under the directive, regulation, and RTS, it is valid to ask whether further granularity and detail is required. It’s worth considering the guidance provided by ESMA to market participants who have to meet EMIR reporting obligations. Under EMIR, guidance was provided in a piecemeal ad-hoc fashion. Guidelines were not drafted and published for consultation, clarifications were instead conveyed via a ‘Question and Answers’ document. For those who have Dodd Frank Reporting (DFA) obligations (under Chapter 17 part 43, 45 and 46) no further guidance other than the regulation was provided. So seen in this light – having well thought out, structured, and consulted upon guidelines should give firms a greater chance of delivering increased quality and consistency of reporting.

    Regulators’ expectations

    The regulators who drafted this consultation document have the experience of reporting under MIFID and as a result, the standards of the RTS and now these guidelines are more informed, detailed, and consistent than compared to EMIR.  Therefore there will be a greater expectation that the quality of MiFIR reporting will be high from the beginning. To increase the likelihood of the guidelines being successful ESMA will consider all comments received by 23 March 2016. Having guidelines that have been written by regulators with previous experience and consulted upon with market participants – combined with a potential year’s delay to MIFID II – gives the best chance of correct reporting than any of the recently introduced reporting obligations such as EMIR and DFA.

    Structure and content

    The guidelines’ length of 269 pages may make it feel impenetrable and inaccessible but on close inspection this is not the case. While there are four issues covered in this document – transaction reporting, reference data, order record keeping and clock synchronization – here we just review the transaction reporting section, which takes up 193 of the 264 pages and is made up of four parts.

    • Part I: General Principles
      Includes guidance on the how, what, when, where to send reports and exclusions.
    • Part II: Blocks (not to be confused with block trades!)
      A block is a collection of fields, which relate to a particular topic and there are 12 blocks in total. For example, block 1 deals with buyer/seller identification, block 4 deals with execution time within the firm and block 10 branches.
    • Part III: Scenarios
      Outlines different trading scenarios that a reporting party may encounter. For example, transmissions of orders, grouped orders, provision of direct electronic access.
    • Part IV: Instruments
      Offers clarity on what instrument data is required to be populated on reports. Focusing primarily on derivatives, this section prescribes when an ISIN is applicable versus when characteristics of the instrument are required.

    In each of the four sections ESMA attempts to provide clear notes on guidance backed up by an example and then an outline of what is expected to be included in the report. It is worth noting that two thirds of the nearly 200 pages on transaction reporting are made up of examples of how the report should be reported.

    Welcome step, but…

    The guidelines and the opportunity for the industry to provide feedback is a very welcome step. Taken together with the MiFID II/R RTS and the now likely year delay, the industry has the materials at its disposal for introducing high quality reporting on go-live. Though I do have a note of caution for firms: ESMA and the competent authorities’ expectations will be high and individuals under the senior managers regime (coming into effect in quarter 1 next year) will be held to account for any failings.

    Over the coming weeks and months we will explore in more detail the effects and implications of guidelines so keep an eye out and feel free to raise questions or comments either to me (dario.crispini@kaizenreporting.com)or via Linkedin or Twitter. Happy New Year from all of us at Kaizen!

  • Is indirect clearing any clearer?

    Is indirect clearing any clearer?

    ESMA has published its latest consultation on Indirect Clearing Arrangements under both EMIR and MIFIR. The consultation paper covers both ETD and OTC derivatives and is designed to ensure consistency between the two regimes.

    The paper looks at “longer chains” and states that:

    “The requirements applicable to a direct client would need to be extended to all the intermediaries between the clearing member and the counterparty at the end of the chain. This means in particular that the provisions related to default management apply throughout the chain, including the requirement to protect through contractual arrangements, to the extent possible, what is owed to the indirect client in relation to the indirect clearing services from the insolvency of any of the intermediary clients providing clearing services.”

    For more information please refer to the Consultation Paper.

  • Finally it’s out, proposed 12 month delay to MiFID II

    Finally it’s out, proposed 12 month delay to MiFID II

    The industry has been mooting a delay to MiFID II for some time now and there were elliptical comments by the FCA and ESMA representatives at the recent FCA conference hinting at an appetite for a delay.  Now, a one year delay was proposed at a hearing of the European Commission’s Committee on Economic and Monetary Affairs yesterday.

    In a statement, MEP Markus Ferber, Rapporteur for MiFID II, blamed ESMA and the European Commission for “dawdling time and again…………responsible for the delays are solely ESMA and the Commission.”

    In a speech by Steve Maijoor to EU institutions published today he raises the need for legislative measures to delay MiFID II principally due to the amount of preparatory work required for building both the rules and IT required for its implementation.

    For a delay, an amendment to the level 1 text will have to be agreed. With today’s announcements that looks extremely likely however it has to be stressed that the European Commission has said only that they are thinking about a delay.

    An additional 12 months would be a boon to firms struggling with implementation.  A delay will mean that there is more time for middleware and service providers to develop their offerings allowing firms to have more clarity on their implementation options.

    A delay may very well result in higher project costs for firms as the projects are extended out but overall they will be better placed to make their preparations.  That said, there will be little appetite for late or poor implementation by firms particularly when it comes to transaction reporting quality.  An extra year would mean that firms now have everything they wanted for the implementation so regulators will expect them to get it right.

  • MiFID II implementation roundtable

    MiFID II implementation roundtable

    For those tracking MiFID implementation activities, the FCA have posted their minutes from the October MiFID II Implementation Roundtable with trade associations.

    The minutes largely cover communication plans including the provision of webinars and other supporting materials to help with the implementation and interpretive challenges that exist.  A couple of areas they covered of interest is the use of endorsed industry guidance which the FCA wants to move away from. However they did say they would be happy to review material produced by the trade associations which is encouraging.  They also cover feedback on its recent MiFID II conference.  See our earlier blog.

  • Good and bad news for transaction reporting under RTS 22

    Good and bad news for transaction reporting under RTS 22

    Fewer reportable fields doesn’t necessarily mean less work.  In this blog, we look at the key changes in RTS 22 from the original  MIFID II consultation proposals and provide some conclusions on the overall impact.

    We carried out a detailed analysis of the reporting fields in the revised draft regulatory technical standards (RTS) released by ESMA.  RTS 22 is the section which sets out the transaction reporting obligations and reportable fields.  The analysis takes the fields in the original consultation paper and compares them to the equivalent versions of the fields in the final report.  In many cases this is a one to one mapping after accounting for some changes in the terminology used.  If you want to take a look or to use the table of fields for your own analysis we have published this as an excel document.

    So what did we find? Taken at face value the number of fields have been reduced from 81 to 65 fields.  A reduction of 16 fields, which is seemingly good news.  However this apparent reduction masks an increase in the information that reporting firms will have to capture and submit – not such good news.

    New fields: Our analysis shows there are 10 new fields which have been added.  The overall reduction in the number of fields results from 13 control fields (code type e.g. LEI vs national identifier) being removed.  We expect that seven of these will be included within the ISO 20022 reporting schema and therefore firms will have to continue to report them.  The remainder are no longer necessary for fields where only one code type is permitted for reporting which again will be enforced through the reporting schema.

    Fully removed fields: Nine fields in total were removed.  “Postcode” and “country of residence” fields have been removed for several identifier fields as has the “consideration” field and the “option exercise” field  is no longer a reportable activity.

    Compressed into another field: Three fields have been compressed into other existing fields, so in essence the information is still to be reported.  The three counterpart fields remain.

    Unchanged: A total of 52 fields remain unchanged in terms of field name.  There are some wording changes embedded which will need further analysis as these will have implications for reporting.

    You can also find our full analysis of the tables below which have the original data fields and revised data fields side by side so you can conduct your own analysis.

    [supsystic-tables id=’6′]

    The 10 new reporting fields:

    Providing these additional fields will in some cases be easy, such as field 5 stating whether you are a MiFID firm or not, whilst others will be very challenging, such as field 40 “complex trade ID” and “instrument full name”.  This latter field is likely to be supported by further guidance given it will be used to identify all derivatives which are not allocated an ISIN code.

    [supsystic-tables id=’5′]

  • Just a second…?

    Just a second…?

    MiFID II introduces the requirement to synchronise the business clocks of trading firms and their customers so that timestamps recorded are standardised across the industry. The idea is that regulators will be able to monitor for market abuse more accurately. Trading systems will need to synchronise themselves to a common source of time. But how will they do this? And what are the implications?

    On the back of the FCA’s MiFID II conference this week we were with the National Physical Laboratory (NPL) to find out. Their workshop, “UTC traceability for the global financial sector, realisation of a unified common clock” attempted to answer some of these questions. Taking the front seat was MiFID II’s RTS 25, which outlines the draft regulatory technical standards on clock synchronisation. The direct impact of this piece of regulation was apparent from the range of professionals from all aspects of the industry including financial firms, exchanges, consultants and scientific organisations.  Most notable was the presence of ESMA and the Bureau International des Poids et Mesures (BIPM) as both have a heavy hand to play in RTS 25. We suggest firms take a look at Table 2 in the Annex of RTS 25 which sets out the level of granularity applicable to their trading activities. It is important that firms are clear on what is expected of them and should be in advanced discussions around the technology to be adopted to meet the new regulatory obligations.

    Here are the key points we took away from the conference:

    1. The industry was concerned about deploying GPS as a means to synchronising their business clocks. It was felt that although it meets the regulators’ authorisation of “satellite systems” as a credited tool, it does not provide traceability back to UTC.  This was further supported by BIPM who claimed that due to the irregular leap second lag incurred through GPS signals, the only credible solution was a direct feed from a National Measurement Institute (NMI). ESMA was clear that both options remain and stood firm, stating that they must be realistic in what they ask from firms and not show any bias to any provider.
    2. The industry feels this needs to be part of the Level 3 discussions but it seems very unlikely that GPSs will be scrapped. We advise all firms to gear up based on the Level 2 RTS 25.
    3. The industry also showed concern around implementing the required technology and sought r advice from the regulator. However, ESMA’s view was very clear in stating it is up to the firm to implement what is required.
    4. ESMA highlighted the importance of firms reviewing their transparency systems on an ongoing basis once deployed. The type of review required is not clarified within the RTS, however we would recommend both internal and third party checks to ensure obligations are met.
    5. FIX is planning to update all versions of its protocol (back to FIX 4.2) to capture the accuracy of seconds in timestamps to 6, 9 or 12 decimal places.
    6. BATS Chi-X Europe is considering providing NPL time source feeds to its clients via a PTP feed if there is considerable demand.

    All in all, the industry is aware of the challenge in implementing this step and the effects it will have on their infrastructures. However, having the same “watch” is very much welcomed by all concerned, agreeing it will lead to better data publication and reporting, thus a more transparent industry as a whole.

    What do you think?  We would welcome feedback or comments about the issues raised in this blog and more broadly, about the MiFID II draft technical standards.

    We’ll be releasing further blogs around the finer details of MiFID II so stay tuned!

    In addition to our testing services, we are offering training courses for firms to help them prepare for the reporting elements of MiFID II. Please contact us to find out more. 

    Read our earlier blog on our reaction to the release of the draft RTSs.

  • 10 things we learned at the FCA’s MiFID II conference

    10 things we learned at the FCA’s MiFID II conference

    Like many of our clients MiFID II is uppermost of our minds at the moment. And on Monday we were discussing all things MiFID II at the FCA’s MiFID II Wholesale Firms Conference in London. Likely to be the first of many conferences about the new regulation, this was probably the earliest event possible given the regulatory technical standards (RTSs) were only released on 28 September.

    Our advice to firms?  Don’t delay: Get your heads around the new rules and get into the detail quickly.

    Here are our key take aways from the conference:

    Regulatory Process

    1. The UK is now working towards transposing the MiFID text into UK law and this must be completed by 3 July 2016 while the European Commission now has three months to consider the published regulatory and technical standards. The FCA’s view is that it is unlikely that the Commission will impose any changes and this position will be affirmed by Q1 2016.  The FCA will publish further consultation papers and these are likely to be split with a consultation paper in December 2015 and an additional one in early 2016.

    2. Regarding the timeline, the FCA acknowledged this is challenging for the industry and regulators alike. However delays to MiFID II are only possible if the Commission considers this is appropriate and it is not within the college of regulators’ powers to impose.  That said, we do think there will be a request for either a partial or full delay given the truncated timetable for what will be a lengthy legislative process.

    3. Organisations not currently within the scope of MiFID I may potentially fall into MiFID II particularly around the commodities space.  These firms will need to quickly plan how they will manage this authorisation process and should submit applications to the FCA by 3 July 2016.   Applications submitted post 3 July will be processed by the FCA on a best efforts basis but there will be no guarantee that applications will be completed before MiFID II goes live in January 2017.  Something that could be very detrimental to business.  A similar story applies to firms that will have to apply for trading venue status OTF or MTF, high frequency trading firms, or as a systematic internaliser.  All activity within firms will need to be assessed to confirm whether authorisation will be required and many platforms are expected to be captured such as broker crossing mechanisms which will come under the new OTF regime.

    Transparency

    4. Following a review by ESMA, the FCA confirmed that agreement had been reached on the approach to be adopted towards the calculation of liquidity and the transparency obligations that would therefore be imposed in respect of non-equity securities.

    5. ESMA, following extensive consultation with industry participants and having reviewed considerable datasets, proposes the liquidity calculation will be applied on an Instrument by Instrument Approach (IBIA).  The FCA believes this will mean real-time transparency reporting obligations for 4% of bonds with a significant portion of these being from sovereign debt.

    6. With regards to deferred publication regime, delays will be possible between two days and up to four weeks from the point of execution.  Venues will also be able to apply for pre-trade transparency ‘waivers’ where the execution is above standard market size. The FCA asked that venues apply for such waivers as soon as possible given that approval is required ahead of trading activity if reliance is to be placed upon any such waivers.

    Commodities

    7. Position limits will be imposed in the commodities sector. The limits will have a cap of between 5-35% of the deliverable supply. Such limits also extend to firms’ open interest positions which imply a potential delivery at such a level. Similarly, the FCA also confirmed that thresholds will be applied to speculative trading in such instruments, and firms exceeding the threshold would require authorisation under MiFID II.

    8. Position limits represent significant challenges for groups with multiple entities trading commodities as the limits are applied both across the group and to each entity so one entity in the group could be within the limits, while across the group the combined total exceeds the position limits. This type of calculation is also to be applied when evaluating whether a firm’s commodity trading activity is ancillary to its main activities or not.  Such calculations look at both the individual entity’s positions and the net positions across a consolidated group.

    9. Position reporting by venues is also a requirement under the new regulations.  The FCA is fully aware of the challenges that the requirements place, not least the need to identify clients down to the ‘end client’.

    10. In transaction reporting, the RTSs are pretty clear but one area we sought clarity on was the new complex trade ID field.  This field seeks to link trades that are part of a wider trading strategy.  Ana Fernandes from the Transaction Monitoring Unit gave a very clear exposition of the aims and drivers behind RTS 22 and confirmed that the aim was to capture true strategies and the intention was not to cover hedging activity or even matched principal activity (riskless principal). However Article 12 wording still points to these transactions being captured.  It is also worth noting that in the RTS ISINs are the only identifier for trading venue instruments.  We expect that was a shock for the likes of Eurex and ICE as the consultation proposal was for Aii codes as well as ISINs.

    What we liked:  In the last session, a panel of regulators including ESMA, BaFin and AMF were quizzed by Nick Bailey of the FCA.  We saw this as very positive in that it shows the regulators are talking to each other; indeed they said that such collusion would be in breach of the competition laws were they operating as firms.

    Once the regulators have had more time to digest the detail of the 900+ pages of RTSs we hope to see more of these events with greater detail and elaboration of the implications for firms and their trading activities.

    In addition to our testing services, we are offering training courses for firms on the reporting elements of MiFID II. If you are interested please contact us. 

     

  • ESMA writes the control section of your transaction reporting BRD…

    ESMA writes the control section of your transaction reporting BRD…

    ESMA has published its eagerly awaited regulatory technical standards (RTS) for MiFID II for consideration by the European Commission.

    Chapter 7, Market Data Reporting (RTS 22) outlines the obligations for transaction reporting. And for those responsible for drafting their firm’s control section of the Business Requirements Document (BRD) Article 15 of RTS 22 makes their job very easy! Recent regulation, whether it be the Dodd Frank Act (DFA) in the US or EMIR in Europe, has become increasingly prescriptive of the controls expected of participating firms. Article 15 takes this prescriptive nature into a different league, placing testing and reconciliations front and centre.

    MiFIR (Article 26(7)) requires firms to verify the completeness, accuracy and timeliness of the transaction reports they submit. RTS 22 expands on this and explains that complete and accurate reporting data is essential to market surveillance and outlines how that is to be achieved.

    Under the first section of Article 15 there are the usual requirements relating to the security and functionality of data and measures to enable timely resumption of reporting when reporting systems go down and measures to identify errors and omissions.  More specifically there is requirement on firms to have mechanisms to avoid duplicate reporting and under reporting.

    Whereas over-reporting is tolerated under current obligations, reporting transactions where there is no obligation is not permitted and Article 15 says firms will need to have mechanisms in place to identify over-reporting.  Over-reporting is the submission of a transaction report where it is not required under the reporting rules.  This can be reporting a trade on an instrument that is not reportable or reporting a transaction on a non-reportable event such as dividend reinvestment.

    When firms become aware of any of these types of errors or omissions they need to be reported to the relevant competent authority. To that end ESMA mandates not only reconciliations but specifies the data sources and fields to be included; reconciliations should be between front office trading records and information contained in transaction reports and checks should be in place to prove the timeliness of reports and the accuracy and completeness of all the individual data fields.

    In tandem with regular reconciliations, Article 15 states that firms are required to put in place a testing methodology and approach for their reporting processes. The multimillion pound fines issued by the Financial Conduct Authority for transaction reporting breaches over the last five years have often been on transactions which have been reported as valid and been through some form of reconciliation process but ultimately have still breached Chapter 17 requirements of the supervisory manual.  It is these breaches that your testing approach must be able to identify.  The often piecemeal, sample-based testing that is common in firms today will not be satisfactory.

    Kaizen Reporting’s testing approaches are setting the industry standard and will enable you to meet your MiFID II requirements efficiently and cost effectively. We combine unrivalled regulatory knowledge with the latest data analytics to provide the highest level of confidence in transaction reporting. 

  • ESMA reveals latest on MiFID II progress

    ESMA reveals latest on MiFID II progress

    On 7th July, Clifford Chance hosted a workshop on MiFID II progress and implementation at which ESMA’s Head of Markets Division Rodrigo Buenaventura provided an update.

    Mr Buenaventura outlined the continuing challenges faced by ESMA. He confirmed that the eagerly awaited final Technical and Regulatory Standards will now be published in September. With regards to timeline and what now appears to be building rumours around delay, Mr Buenaventura confirmed that there is no discussion at this time in this regard and ESMA is moving towards the 3rd Jan 2017 date. Despite recognising this would be challenging, they currently consider this as achievable. Furthermore, he advised that there is no current provision for phasing in particular aspects of the legislation, although acknowledged that over time this could be considered but it was too early for such consideration.

    He highlighted the key issues that require further consideration and these are clearly still a concern to market participants. These include:

    • non-equity transparency
    • commodity reporting
    • liquidity classification

    ESMA is considering the most appropriate approach towards liquidity calculation and whether this should be undertaken against individual securities or whether to adopt a group approach, for example a dependency upon issuance size. Their preference is currently unclear and will require further analysis.

    The liquidity calculation determines what instruments must be trade reported for market transparency. ESMA believes that the number of instruments that will be subject to trade reporting obligations will increase twenty fold.

    ESMA highlighted they will have a different role under MiFID II as consolidator of various important market data for transparency purposes in order to calculate liquidity and establish reporting obligations. They consider a single engine for this is beneficial to the financial community, avoiding reporting obligations to multiple CAs.

    ESMA also recognises there are significant challenges in respect of the establishment of position limits and that the European environment is completely different to the US. In the US some 60 limits exist whereas in Europe this runs into the thousands.

    Particularly interesting to those in the regulatory reporting arena was the fact ESMA confirmed it has significant concerns around the quality of the data reported under both the MiFID and EMIR regimes. Mr Buenaventura stated they are determined to ensure improvements in the quality of reporting and are working with the various colleges in an effort to address this.  ESMA recognises the importance of improving the quality of derivative reporting ahead of MiFID II implementation.

    ESMA advised they have undertaken significant analysis of market data, having reviewed more than two terabytes of EMIR data on top of significant bond market data to consider the appropriate way forward. ESMA recognised they will need to work with market providers in an effort to source the appropriate data for liquidity calculation and establishing appropriate position limits.

    Overall, ESMA stated they consider the implementing legislation should be an improvement for market participants given the harmonisation that regulation creates as opposed to a directive. Supervision convergence should ensure consistent approaches around requirements across the EU.

    With regards to the approach around implementation, questions were raised around adopting a similar approach to the EBA and the implementation of CRD given the issues experienced with EMIR Q&A.  ESMA will consider this and acknowledged the level of queries will be considerably higher and possibly ten times the 2000 or so queries that were raised under EMIR.

    Overall, Mr Buenaventura highlighted the importance placed on reporting and the significant changes that are taking place.  Furthermore, he stated that the focus on the problems with current standards provides a clear indication that regulators are serious about ensuring reporting quality is improved in order to implement the new legislation effectively. ESMA clearly recognise that the poor quality of data today is detrimental to the objectives the reporting obligation are attempting to achieve and so firms should take note of the obligation to have a control framework in place at MiFID II go-live.

  • A review of the key TRUP 3.1 changes for MiFID

    A review of the key TRUP 3.1 changes for MiFID

    The FCA published revised transaction reporting guidance in TRUP 3.1 on 6th February 2015. The key changes come into effect six months after publication on 6 August 2015 whilst other changes which are considered to be for clarification purposes have immediate effect.

    The changes impact the following areas:

    • Trading capacity field
    • Reporting the unit price for bonds
    • Venue field clarifications
    • Strategy trades
    • Self-hitting trades
    • Firms’ systems and controls over transaction reporting activities

    Capturing changes in the firm’s and clients’ positions

    TRUP 3.1 states that “Firms must ensure that the trading capacity field is populated in transaction reports so as to accurately reflect the changes in positions of the firm and its client(s) at the time of the transaction(s).”

    FCA are looking to capture under its rules and guidance what is reportable in terms of changes in position. There are some scenarios where firms’ current use of the trading capacity field results in a change in position of a client or a firm to not be reflected in the transaction reports. This requirement could be interpreted more broadly to require the reporting of all changes in client and firm positions and I don’t think that is the intention. This would introduce full lifecycle event reporting. Lifecycle events are post transaction events which results in changes to existing contracts such as increases in notional or a change of counterparty or beneficiary. Lifecycle event reporting is not being introduced in TRUP 3.1 rather MiFID II sets out the requirements in respect of lifecycle events. The current MiFID II consultation excludes derivative novations, assignments and compressions from reporting which would not enable these changes in position to be captured.

    Trading capacity changes

    Whilst on the surface the change appears straightforward, it masks a great deal of complexity. The cause is the fact that the legal agreements between a firm and its clients and counterparties determines how this field is to be populated.

    In general this can work quite well. Many firms operate in a principal capacity and populate accordingly. Where firms operate in both a principal and an agency capacity, the complexity begins. Where a firm provides a fill from its own book but is acting as agent for its client it is operating in both a principal and agency capacity. The new TRUP guidance requires that both capacities are to be reported. This is achieved by using the “internal” to denote transfers in and out of an internal account. It is expected that positions would always clear from the internal account. The same process will be applied to trades where the firm fills an agency order by trading in a principal capacity against a counterparty or on venue.

    This means firms will have to have reporting processes in place to capture booking scenarios where there is a transfer from a principal book to an agency book/client account. Recoding of systems to put this into effect is likely to be non-trivial exercise particularly where an actual internal account or washbook is not used.

    The TRUP includes brief examples which I would recommend are closely reviewed.

    These changes are to be implemented by 6th August 2015.

    Unit price for bonds and bond futures

    The price to be reported for Bonds has always been the clean percentage price where the percentage is based on the par value of the bond. There has however, been open questions around instruments that are bond like but are traded in a similar way to equities. This would include securitised instruments that pay a coupon. TRUP 3.1 clarifies that such instruments should be reported with the traded price. So if it is traded as based on a percentage of par, the percentage is reported whilst if it has a price in monetary terms that value should be reported (in the major currency).

    As trading conventions for bonds are not uniform, we are still left with the problem of converting prices from the market convention to a percentage. So problematic bond instruments such as French convertibles which are usually traded with a dirty price based on units and Belgian OLOs which are trading with prices agreed in the form of a yield, will now have to be reported in percentage terms. The Belgian OLOs are especially problematic as firms are required to report trading in these instruments to the Belgian FSMA with the price in a yield format which is contradictory to MiFID and FCA requirements.

    Reporting the venue

    Reporting the venue on which a trade is executed remains a problem field for firms and we see many instances where errors have been introduced when capturing the venue identifier. Whilst there are no new obligations emerging from the TRUP changes, the revised text goes some way to clarify how to populate this field however there are still further elements that firms need to consider.

    Sup 17 and TRUP 3.1 require the use of a MIC code when trading under the rules of a “trading venue”. MiFID I provides the applicable definition of trading venue able:

    “(8) ‘trading venue’ means a regulated market, MTF or systematic internaliser acting in its capacity as such, and, where appropriate, a system outside the Community with similar functions to a regulated market or MTF;”

    There are numerous venues within the EU which have been allocated a MIC code. By definition, as they are within the EU they cannot be considered to be a regulated market or MTF (Multilateral Trading Facility). Similarly, there are venues or platforms outside of the Community which have been allocated MIC codes, many of which cannot be considered to be of similar functions to a regulated market or MTF.

    As such it is not sufficient to establish that there is a valid MIC code for the platform upon which the trade was undertaken. An assessment needs to be made as to whether the platform has similar functions to that of a regulated market or MTF.

    MIC segment codes

    MIC codes are now split between an operator code and the segment code. The venue field should reflect the market identifier code (MIC code) of the market segment where the trade is agreed to be under the rules of the trading venue unless the trade is an OTC derivative trade. OTC derivatives are always reported as “XXXX” in the venue field.

    Happily, the FCA has introduced some latitude in those circumstances where the segment traded is unknown or uncertain whereupon the Market Operator MIC code can be reported. This scenario arises when trading on Xetra where exchange fill data does not identify the segment the instrument was traded on and therefore the operating MIC (XFRA) may be utilised.

    Strategy trades

    Strategy trades are trades where a derivative and its associated underlying are traded at the same time. For strategy trades executed on Aii markets, the underlying, which often has an ISIN identifier, cannot be reported using the Aii market’s MIC code as an Aii identifier is expected by the ARMs and FCA’s ZEN system. The guidance clarifies that in such instances “XOFF” should be reported in the venue field and the ISIN of the underlying in the instrument identifier field.

    Self-hitting trades

    Where a firm trades on exchange, particularly if they are trading in significant volumes, they may hit an order on the order-book which has been placed by another desk, algo or DMA client submitting orders for the same firm. The guidance clarifies that such trades are to be considered transactions and are therefore reportable irrespective of subsequent clearing activities which are likely to net out the two trades to zero. Where the trade is immediately cancelled prior to a trade report being published, then an execution is deemed not to have taken place and a transaction report is not required.

    Firms are expected to have implemented reporting in compliance with the above by 6th August 2015.

    Transaction reporting arrangements within firms

    As in previous versions of the TRUP there is guidance on the FCA’s expectations in respect of reporting firms’ controls over the accuracy, completeness and timeliness of their reporting. TRUP 3.1 is more explicit than previously and sets out expectations in respect of the training that those involved in transaction reporting are expected to have (including elements of the training content) and the expectation that firms will conduct front to back reconciliations between front office systems and the reported transactions.

    Whilst many firms will already have controls in place, a review of the controls and whether they satisfy all the areas outlined in the TRUP is recommended.

    Kaizen Reporting Services

    Kaizen offers a suite of services which meet all the requirements of the TRUP 3.1 including execution of front to back reconciliations, reconciliations to FCA data, report testing services as well as comprehensive training on the reporting obligations and reporting health checks.

    If you have concerns or questions about EMIR or Transaction Reporting then please contact us. We would be happy to provide an initial review of your transaction reports at no cost allowing you to try out our report testing service.

  • Obligation to use LEIs picks up pace

    Obligation to use LEIs picks up pace

    LEIs are already required when reporting under EMIR but their use is to be mandatory from 2015 under COREREP and FINREP.

    The EBA published its recommendations on use of LEIs in regulatory reporting and the FCA has adopted the recommended approach. This means that UK firms must have registered both themselves and group companies for an LEI by the end of the year. They are required for COREREP and FINREP submissions for both the reporting firm and any relevant group entities when submitting on a consolidated basis. LEIs are also to be used to identify counterparties when reporting where an LEI has been issued for the counterparty.

    Firms are advised to obtain an LEI from a local operating unit and the FCA expect firms to register their LEIs immediately upon receipt using the FCA survey tool.

    They have become regulators’ entity identifier of choice so we can expect to see it as mandatory for a range of reporting obligations not least under MiFID II and Security Finance Transaction Reporting.

  • NYSE LIFFE MIC changes following migration to ICE Futures Europe

    NYSE LIFFE MIC changes following migration to ICE Futures Europe

    The NYSE LIFFE Market Identifier Code (MIC code) is to change following their migration to ICE Futures Europe including guidance on BClear instruments.

    This change has a direct impact upon firms’ regulatory reporting obligations impacting both EMIR trade repository reporting and MIFID transaction reporting obligations. This note summarises the changes and what action firms should be taking.

    The ICE migration is complicated in that the exchange contracts are being migrated over 5 different dates with the final date of migration being 17th November 2014. Firms should note that fixed income instruments migrated over three different dates therefore the MIC for the respective contract needs to accurately reflect these changes. Further complexity is that close attention is also required in respect of the appropriate MIC being applied for example the MIC code is different for Equity Index Futures (IFLL) and Options (IFLO) contracts and this needs to be identified correctly in firms static data and subsequent reporting.

    What should firms be doing?

    Firms’ static data needs to be amended to reflect the correct MIC code at the time of the changeover for the impacted contracts. Post implementation quality assurance testing should be applied to ensure that EMIR and MiFID transaction reports reflects the MIC changeover and any timing errors are corrected.

    With various LIFFE contracts being migrated to new MIC codes in stages firms will need to take great care to ensure that they use the correct MIC code for the relevant contract at the right time. For quick reference table detailing the precise changes to the appropriate MIC and the respective dates this was applied please refer to the below table which contains the full details.

    LIFEE Contract Migration to ICE Futures Europe

    [supsystic-tables id=’7′]

    BClear

    Firms should also note, that going forward, trading previously undertaken utilising LIFFE BClear for wholesale market activity, will now be undertaken under ICE “block” trading rules. When reporting as per the above table, firms should consider the product sector and contract type and report the appropriate MIC ongoing from it’s respective migration date. Dependent upon the security, this trading activity will be subject to MiFID and/or EMIR reporting requirements. Firms are advised when reporting this activity that they are required to report the appropriate MIC in recognition of the particular security.

    See below for further clarification.

    • “Block” trade on an Equity Index Future the appropriate MIC is IFLL
    • “Block” trade on an Equity Index Option the appropriate MIC is IFLO
    • “BlocK” trade on White Sugar Futures and Options the appropriate MIC is IFLX

    Firms should refer to the “LIFFE to ICE Futures Europe Transition Notice” published September 2014 for further details of the migration impact.