Category: MiFID II Trade Reporting

MiFID II trade reporting is an obligation under the second Directive of the Markets in Financial Instruments Directive (MiFID) / Markets in Financial Instruments Regulation (MiFIR). Sometimes referred to as Post-trade transparency (PPT), it is an extension of the current regime for shares to a wider range of instruments including: ETF’s, depositary receipts, non-equity instruments, emission allowances and derivatives. It involves the publication of data on the trades once these are executed for investment firms and trading venues. Check out Kaizen’s insights on MiFID II trade reporting.

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

  • One year to go:  RTS 2 non-equities reporting to reduce to five minutes

    One year to go: RTS 2 non-equities reporting to reduce to five minutes

    The countdown has now started! From this month it is now less than a year to go until investment firms’ RTS 2 non-equities post-trade transparency reporting needs to reduce from 15 minutes to five minutes. This new implementation comes in three years after the original MiFID II go-live.

    RTS 2, Article 7 states: “…for the first three years of application of Regulation No 600/2014, within 15 minutes after the execution of the relevant transaction; thereafter, within 5 minutes after the execution of the relevant transaction.”

    Whereas RTS 1 transparency has been relatively straightforward due to the electronic nature of equities trading (hence the one minute limit), the non-automated nature of voice trading, as an example, still causes problems for firms in terms of meeting the current close-to-real-time 15-minute deadline imposed by the regulation. It is commonly recognised that firms still struggle to meet publication after 15 minutes, whether that’s changing a trader’s habit, automating trading or even introducing FIX messaging protocol which  – believe it or not  – still isn’t used by all firms. So the reduction to five minutes may really impact firms and may alert the national competent authorities to focus more on these transparency deadlines.

    MiFID II’s transparency objective meant that it was bringing the non-equities trading world into the 21st century and electronifying the practice, creating a level playing field and enabling investors to make an informed decision with the knowledge of how the price was formed.

    With under a year to go, firms need to incorporate this change into their book of work technologically, procedurally and in some cases, culturally. At Kaizen, we provide accuracy testing on MiFID II post-trade transparency reporting (PTT) data to check that you are meeting these close-to-real-time requirements and that your data is correct. This includes checking whether you are reporting within the required timescales and alerting firms where they consistently do not meet the deadline after execution. 

    Contact us if you’d like some help in ensuring your PTT reporting is accurate as this will help with your preparation for the change to reporting within five minutes. 

     

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

  • 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

     

     

  • ESMA postpones review of MiFID II RTS 2

    ESMA has written to the European Commission to postpone the review of MiFID II Regulatory Technical Standards (RTS) 2, which was due in July 2019, as outlined in Article 17 of the RTS regulatory text.

    The review is key to understanding bond transparency thresholds and liquidity assessments. Given the uncertainties around Brexit, it was felt that the analysis should be completed after the UK has left the European Union. This will now be due by 30 July 2020 and recent regulatory commentary suggests it will begin around March 2020.

    This is another rescheduling to RTS 2, as data quality already delayed the SI regime for bonds until eight months after MiFID II go-live. The SI regime for derivatives is still not due to go live (for the same reason) until ‘at some point in 2020’. This Brexit-related delay to the review will almost certainly push the derivatives SI regime to the latter end of 2020, which in turn may delay the transparency reporting requirement under RTS 2 which looks at decreasing it from 15 minutes to five minutes in January 2021.

    For regulatory reporting purposes, this brings further complexities to investment firms. Understanding of trading where the primary market liquidity is sitting, and its subsequent size and liquidity thresholds for deferral eligibility, is key. Ensuring you are reporting to the correct APA in Europe or UK brings transparency challenges too. 

    To discuss any of the issues above or to find out how our ReportShield™ services could help with your Post Trade Transparency reporting, please get in touch. 

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

  • The effects of Brexit on MiFID II post-trade transparency reporting

    The effects of Brexit on MiFID II post-trade transparency reporting

    “There are known knowns. These are things we know that we know. There are known unknowns. That is to say, there are things that we know we don’t know. But there are also unknown unknowns. There are things we don’t know we don’t know.” – Donald Rumsfeld (Feb, 2002).

    Brexit…the ‘known unknown’ of everyone’s lives (at least for those of us in the UK) and not just in financial services but across all sectors of life.

    MiFID II has not escaped Brexit either.  Let’s call it BRiFID!  My colleague David Nowell has covered in detail the effects of Brexit on EMIR trade reporting & MiFIR transaction reporting but in this blog, I want to delve into the effects on post-trade transparency reporting. 

    Kaizen announced at the beginning of December 2018 that we were to offer post-trade transparency reporting testing following on from our established MiFID II transaction reporting testing service. The need and demand for MiFIR completeness and accuracy across regimes has become very relevant, highlighted even further by the recent penalty announcements from the UK regulator, the FCA:

    The FCA’s Final Notice on 19 March for the first of this year’s transaction reporting fines, stated:

    “Firms must take reasonable steps to ensure the accuracy and completeness of the transaction reports that they submit to the Authority. One way that firms can help to achieve this is by having controls in place to reconcile the completeness and accuracy of their transaction reporting process.”

    The most recent fines were admittedly for transaction reporting inaccuracies under MiFID I, and MiFID II sanctions are not yet known or been broadcast. But it is only a matter of time before the next firm is penalised and this could well be for post-trade reporting inaccuracies (known unknowns). Stephen Hanks, Head of Markets Policy at the FCA, mentioned at an conference on 16th April that, “poor data quality is still being sent to APAs and that the FCA will continue to work with investment firms to improve quality as a priority”.

    What Now?

    MiFID II transaction reporting has clearly taken a regulatory priority since go-live but post-trade transparency reporting, its just-as-important sibling, is just as key. The past year’s Level 3 Q&As have brought clarity to previous ambiguous regulatory text so firms should now have a greater understanding of their reporting obligation but do they have the testing and controls in place?

    Stephen Hanks stated; “There are still issues we see in reports and we are particularly disappointed to still be seeing errors in reports which would have been errors under MiFID I, never mind MiFID II.”

    Really! Why? When??

    Yes, in amongst the turmoil of BRiFID, investment firms and regulated markets have a near to real-time responsibility to make sure their RTS 1 equity-like and RTS 2 non-equity trades are reported within one minute and 15 minutes respectively (reducing to five minutes by 2021). The responsibility wording is key. Firms may think they do not have a reporting responsibility or they may have asked their brokers to report on their behalf but have firms put in place the correct control framework to prove this if the regulators come calling?  Could this highlight a firm’s unknown unknowns?

    MiFID II has now been live for almost 15 months. With Brexit there is the very real situation that post-trade transparency reporting will need to be directed to either the EU or UK APA as well as liquidity shifting away from the main markets and the impact of ESMA’s Trading Obligation views.  This is a good time to make sure you’re also compliant with post-trade transparency reporting as well as transaction reporting. 

    What next?

    If you have any doubts about whether your post-trade transparency reporting and controls are up to the required standard, we can help. We have a proven track record in helping firms tackle their regulatory reporting issues and risks head on – and helping them to avoid censure. Our ReportShield™ quality assurance services provide everything you need for reporting assurance including a bespoke control framework, quality assurance testing of all fields on all reports, reference data testing, reconciliation and completeness checks and training. Contact us to find out more. 

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

  • MiFIR offering from Kaizen to include APA trade reporting

    MiFIR offering from Kaizen to include APA trade reporting

    FOR IMMEDIATE RELEASE

    3 December 2018, London: Kaizen Reporting, the specialist regulatory reporting firm, has announced it is extending its award-winning assurance service, ReportShield™, to cover MiFIR trade reporting*.

    Kaizen has hired Chris Machin, who was instrumental in the development of the MiFIR real-time reporting solution TRADEcho, to help develop its new testing service. With a background in global banking (including at UBS and Credit Suisse), operations and client services, Machin brings significant subject-matter expertise on major regulatory regimes including MiFIR, CSDR, SFTR, MAR, EMIR and Dodd-Frank. He was most recently Head of Client Support at Simplitium, where he partnered with the London Stock Exchange to help build the APA TRADEcho.

    Ian Rennie, Managing Director of Kaizen, said: “With both the buy- and sell-side financial firms now turning their attention to the quality of the data published in the real-time reports through APAs, trade reporting is an important focus for our clients and exactly where Kaizen’s strengths of quality, accuracy and transparency will pay dividends.”

    He added: “We are delighted to have Chris leading the development of our testing service for MiFIR trade reporting. Chris previously played a prominent role in the planning, development and go-live at one of the main APAs. His expertise will enable us to quickly meet the increasing demand from clients and regulators for accurate and complete MiFIR trade reports.”

    Machin’s move to Kaizen adds to the company’s growing list of regulatory experts. Earlier this year the regulatory technology firm hired former regulator and EMIR and MiFIR expert David Nowell, and the former head of the ICMA Taskforce on SFTR, Jonathan Lee.  Already providing peace of mind to clients with its market-leading assurance services for EMIR, MIFID II transaction reporting, Dodd Frank and SFTR, the new MiFID II trade reporting testing service will provide additional confidence to clients that they are meeting their reporting obligations.

    Chris Machin commented: “Kaizen are pioneers in their approach to regulatory reporting assurance and I’m delighted to be joining such a forward-thinking company dedicated to giving clients peace of mind in their reporting data quality.  Trade reporting is a key part of MiFID II’s aims to improve price transparency in the financial markets and I am confident that clients will quickly benefit from the new service.”

    Kaizen’s ReportShield assurance service is a set of four controls that test for the accuracy and completeness of regulatory reports, something mandated under MiFIR.  Kaizen’s testing services are unique in their comprehensiveness, delivering full visibility of reporting quality.

    *Under MiFID II, investment firms are required to both trade and transaction report. Trade reporting improves the near to real-time trade transparency information published to potential investors. Financial details of trades are reported to an Approved Publication Arrangement (APA) for dissemination to the market. In transaction reporting trade details must be reported in T+1 to an Approved Reporting Mechanism (ARM) which validates the data before sending the reports to regulators. 

    (ends)

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

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

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

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

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

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

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

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

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