Tag: transparency

  • Video series: Dario Crispini on issues and risks of poor data quality in regulatory reporting

    Video series: Dario Crispini on issues and risks of poor data quality in regulatory reporting

    In this video, Dario Crispini covers the following data quality in Regulatory Reporting topics:

    • What are the main regulatory reporting issues that firms should currently be looking out for?
    • What should firms have in place and what preparations should they be making for new regulations?
    • What is the status of firms’ regulatory reporting capabilities?
    • What are the main risks of a poor regulatory reporting practice?

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

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

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

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

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

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

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

    In this video, David Nowell answers the below questions:

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

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

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

     

  • Cappitech and Kaizen Reporting publish findings of SFTR implementation survey

    Cappitech and Kaizen Reporting publish findings of SFTR implementation survey

    FOR IMMEDIATE RELEASE

    17 September 2019, London and Tel Aviv: Cappitech and Kaizen Reporting today published the findings of the SFTR implementation survey conducted by Cappitech, a leading provider of regulatory reporting and intelligence solutions for the financial services industry, and analysed by Kaizen Reporting, global leaders in quality and accuracy for regulatory reporting, in which securities financing market participants were asked to help establish the industry’s state of readiness.

    While there is a greater state of readiness among the banks (due to go live in the first phase, April 2020) of reporting, the survey shows that 56% of banks are still only in the pre-implementation planning stages. The survey concluded that overall only 37% of the securities lending industry has started or completed SFTR implementation and expect to be ready in time when the regulation comes into force in phase one. 11.5% have not even begun to plan. While some allowance can be made for the fact that a number of respondents have later go-live dates, this is somewhat concerning.

    The current lack of readiness across the industry for this new and complex regulation is highlighted by the survey. Both Cappitech and Kaizen Reporting believe industry participants need to prioritise planning, implementation and testing of robust processes for SFTR, to ensure timely implementation.

    Jonathan Lee, Senior Regulatory Reporting Specialist (SFTR) at Kaizen Reporting said, “The findings from the SFTR survey make it clear that many companies are not as prepared as they should be at this stage. In order for firms to be ready by April 2020 there is a need to accelerate their plans and make sure that they allow enough time for testing and implementation.”

    Ronen Kertis, Founder and CEO of Cappitech comments, “Reporting firms who aren’t ready, especially those that haven’t started planning, will need to prioritise this in the coming months. Where possible, an extension of their existing technology may provide an easier and more seamless transition.”

    Reporting firms highlighted a number of additional concerns with SFTR including, most significantly, the issue of UTI matching; 54% of respondents felt they will need to implement UTI matching, with another 33% still considering it.

    40% of survey respondents are also still undecided regarding which trade repository (TR) they are intending to use, bringing additional readiness to test. While tier 1 firms often decide based on board seats and shareholdings, for the rest of the market pricing will be key and most TRs have not yet published detailed pricing data.

    Additional findings from the report include:

    Vendor Selection: This is an ongoing process, with 58% of respondents planning to implement extensions of their current reporting tools.  

    Delegated reporting: 51% of the banks surveyed are committed to providing delegated reporting. “Delegated reporting brings real challenges, not least of which is the need for clients to have control of and access to their reporting data to meet their regulatory requirements. Specific delegated reporting solutions  solve this challenge for banks when they offer delegated or assisted reporting to their clients,” says Mr. Kertis.

    UAT testing: The report also shows that despite its importance, UAT testing has not been fully embraced by the industry. Approximately 54% plan to test in the three months prior to go-live but Kaizen and Cappitech experience proves that many regulatory programme deliveries are delayed, leaving minimal time for testing. This has a knock on negative impact on data quality and regulatory compliance. For the 11% who are planning not to do any testing, and the 7% whose planning only incorporates testing one month before, these risks are greater with Mr. Lee stating, “We would caution that three months will not necessarily prove sufficient to launch such a large and complex reporting regime.”

    For a full copy of the report and to access further findings, please download it here.

    (ends)

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

  • In the news: David Nowell speaks to Practice Insight

    In the news: David Nowell speaks to Practice Insight

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

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

    Read the full report.         

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

  • 10 Lessons from industry responses to the ESMA Guidelines Consultation

    While not an exhaustive list, here are our key takeaways from reading the ESMA SFTR Guidelines consultation responses. The overall level of engagement in relation to the consultation was substantial, with 49 files published by ESMA following the consultation period.

    1. Reporting certainty

    A few fundamental questions are key to providing clarity to support a timely build for SFTR reporting. Banks and credit institutions (due to report from April 2020) need answers to some of the these questions well in advance of the self-imposed Q4 2019 deadline set by ESMA.

    In particular, question 25, whether to provide full reports or the delta of changes for modifications and corrections – respondents overwhelming voted for full reporting.

    2. Reportability of intraday market infrastructures executed SFTs

    Which intraday transactions executed on behalf of firms by CSDs and CCPs remain in-scope for reporting? While T2S Auto-collateralisation transactions are explicitly excluded from reporting, does this also cover UK Crest Auto-collateralised repos? Extracting and reporting this data presents unique challenges.

    3. Scope and third country considerations

    The approach to determining the ‘conclusion’ of a transaction by a branch is far reaching and strays from the EMIR definition. It appears to focus on the activities of individuals rather than risk held in the EU. The practical challenges of reporting SFT activities of non-EU entities where traders are supervised by EU branches are immense and likely to lead to significant confusion in relation to areas such as bilateral margining and reuse.

    Concerns were raised where SFTR does not require non-EU AIFs managed by EU AIFMs to be reported (unlike EMIR), while EU AIFs must be reported regardless of whether the AIFM is based in the EU (again unlike EMIR).

    4. Why are buy-sell backs still treated differently?

    ESMA have specified that documented buy-sell backs should be reported as buy-sell backs listing the master agreement, but it is still unclear why the reporting requirements differ from repo. The inability to apply a repo rate, forward breakeven yield or forward price on a buy-sell back is a particular issue.

    5. Is fails reporting really required?

    There has been some confusion about the reporting of settlement fails (general consensus was that perfect settlement would be assumed unless both parties chose to modify a transaction to reflect a default or extended fail).

    6. How to report bilateral variation margining

    Concerns continue to surround the reporting of bilateral variation margins for repo. Given these margin calls at the counterparty portfolio level are entirely separate from the trade level collateral, there should be a separate end of day collateral update report to reflect bilateral margining. They cannot, as ESMA examples suggest, be incorporated with trade level collateral updates.

    7. Failure to transmit Unique Trade Identifiers (UTI)

    The issue of what to do if a counterparty is responsible for providing the UTI fails to provide it in a timely manner for reporting, remains an open question. The real question is how the party subject to late notification of the UTI by their counterparty can be excused from their obligation to submit timely reports.

    8. Availability & consistency of reportable data

    There are many concerns about the availability of data for reporting. The FSB themselves highlighted in their May 2019 document Thematic Review on Implementation of the Legal Entity Identifier that on aggregate only 55% of all financial instruments in scope have an LEI code (representing 78% of outstanding amounts) and that only 11% of all firms that are issuing securities have so far obtained an LEI. Mandating usage of issuer LEIs when firms that use securities as collateral have no contractual relationship with the issuer of the securities, appears a step too far. Solutions are to make the field conditional or apply a standard dummy issuer LEI.

    Other concerns persist around missing official CFI codes, ISIN codes, differences in credit rating assessments between firms and the collateral type field.

    9. The removal of ESCB transactions from the calculation

    Trade associations reiterated that removing ESCB transactions from both sides of estimated re-use calculations will be both difficult and misleading. Nonetheless, this is understood to be an FSB requirement rather than ESMA specific.

    10. Uncertainly around in-scope commodities financing transactions

    A number of trade associations and other respondents commented on the significant uncertainty felt by the commodities trading industry around the SFTR reporting scope of any of their transactions. Concerns were raised that while commodities financing transactions share attributes with SFTs, they are not executed for financing purposes. Disagreement exists as to which transactions constitute repos and which buy-sell backs, in general they were deemed hard to define under existing SFT definitions. There are also concerns that certain commodity transactions, believed to best fit the repo definition use pledge arrangements and not title transfer. Some power and gas contracts may also be reportable under SFTR as well as REMIT. While exclusions are in place for EMIR, they are not in place for REMIT.

    Did you know Jonathan provides CPD-accredited, CISI-endorsed training on the SFTR reporting requirements? Book your place on one of our upcoming courses here or get in touch for bespoke, in-house training.   

  • ESMA fines trade repository for data delivery breaches

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

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

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

  • Sunny ESMA provides some SFTR relief

    Sunny ESMA provides some SFTR relief

    ESMA published a Consultation paper “Guidelines for reporting under Articles 4 and 12 SFTR,” together with the latest consolidated SFTR validation rules. The deadline for responses is 29 July 2019. ESMA plan to consider feedback during Q3 2019 and the final report is scheduled to be published in Q4 2019. This does not give a lot of time, particularly for the 1st phase of reporting counterparties (Banks), due to go-live in April 2020.

    Nevertheless, ESMA provided clarity on many issues and gave reason to be cheerful as many SFTs executed on behalf of financial institutions through powers of attorney during the course of daily clearing, custody and settlement activities at CCPs, CSDs and ICSDs were ruled out of scope. This has undoubtedly removed a major operational headache from the SFTR reporting requirements and will assist regulatory authorities in gaining a better understanding of the data (as they will be significantly less overwhelmed with noise).

    • In particular, Chapter 5 (General Principles), paragraphs 25-27 rule out any reporting of short term credit lines for custody or CCP clearing.
    • Paragraphs 36-41 rule out reporting of any transactions relating to “fails-curing” services offered by CSDs.
    • Paragraph 43 rules out the need to report any transactions associated with Target 2 Securities Auto-Collateralisation.

    The guidelines also clarify the exclusion of the need to report under SFTR in relation to: Retail client lending (except when it is against an irrevocable trust), private banking & Lombard loans, syndicated lending and other corporate lending for commercial purposes, intermediate give-ups and take-ups (in the execution & clearing chain) and transactions involving emission allowances.

    In further points of clarification:

    • Buy-sellbacks and Sell-buybacks should be reported as such with the appropriate master agreement detail where applicable (overruling the original SFTR regulation) (paragraph 61).
    • Margin Loan reporting only applies to Prime Brokerage business (paragraph 11).
    • Modifications that are agreed but have not taken place should not be reported until the actual modification takes place (paragraph 117).
    • Margin loans – where the value of an existing margin loan hits zero, the transaction should be modified (MODI action type) rather than terminated (ETRM action type) (paragraph 83).
    • Securities lending and borrowing transactions can only involve a single ISIN being transferred between a given pair of counterparties (paragraph 65).
    • Backloading: ESMA advises that they like the idea of reporting all open and term transactions executed prior to the date of application whether they meet the requirements for backloading or not. This approach is seen as operationally simpler for many reporting parties and provides authorities with greater information in relation to variation margining (paragraphs 167-170).
    • When trading with sub-funds, each sub-fund should be treated as a counterparty if they have their own LEI (paragraph 52)
    • For cleared SFTs, each SFT between the CCP, its clearing members and the clients of those clearing members should be treated as separate SFTs with different UTIs (paragraph 53).
    • In relation to Repos, collateralised loans in more than one currency constitute separate SFTs. This doesn’t preclude a single SFT having collateral denominated in multiple currencies though
    • Small & medium sized non-financial counterparties trading with a non EU third country entity must either trade with an entity that has been granted equivalence (in which case there is no reporting obligation under SFTR), else they will need to delegate or self-report the transaction/s (paragraph 93).
    • Execution by a branch was clarified to cover the following: a) for a client in accordance with a discretionary mandate given to it by the client; b) where the branch has supervisory responsibility for the person responsible for the investment decision concerned; c) where the branch has supervisory responsibility for the person responsible for execution of the transaction; d) where the transaction was executed on a trading venue or an organised trading platform located outside the Union using the branch’s membership of that trading venue or an organised trading platform (paragraph 102).
    • Counterparties should not report the LEI of the CSD in which they are either a direct or indirect participant (paragraph 122) in the CSD participant field.
    • ESMA acknowledged that updating valuations of securities on loan or used as collateral may not be possible where pricing becomes stale. This can affect suspended shares and some illiquid fixed income securities. In these instances, reporting parties should use contractually agreed values and only update them if new price information becomes available (paragraph 155).
    • ESMA advises counterparties should always use official sources for CFI codes. Those who felt that it would be sufficient to just populate the first 2 characters are likely to be disappointed as ESMA states that X should only be used when a character is not applicable (paragraph 163).
    • Non-bank entities are permitted to start reporting earlier than their date of application if they find it easier (paragraph 188).   

    The consultation also contains an extensive set of sample reports for many different scenarios, detailing how each of the 4 reporting tables should be populated. Once we’ve had the opportunity to review these samples and the latest trade repository validation rules, we will produce a follow-up blog.

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

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

     

  • In the news: Jonathan Lee speaks to BobsGuide

    In the news: Jonathan Lee speaks to BobsGuide

    Our Securities Financing Transaction Regulation (SFTR) reporting specialist Jonathan Lee recently spoke with Rebekah Tunstead at Bobs Guide to highlight the pressure that tier one banks are putting on trading venues to provide a much more compliant SFTR confirmation file from the beginning. 

    “Pretty much everyone in the chain is looking for ways in which to cut costs and to some extent pass on the onus and responsibility to others. Even among the tier one banks, they are looking to trading venues that will provide more of the reportable field in the appropriate format such that they don’t need to collate and process that data themselves,”  Lee says.

    Read the full interview.

  • Alpha FMC and Kaizen to provide transaction reporting compliance assurance service

    Alpha FMC and Kaizen to provide transaction reporting compliance assurance service

    Combined proposition will assess governance and control frameworks and identify any gaps in MiFID II transaction reporting obligations.

     

    FOR IMMEDIATE RELEASE

    5 February 2019, London: Alpha FMC the global leader in asset and wealth management consultancy, has teamed up with multi-award-winning Kaizen Reporting, the specialist regulatory reporting firm. The collaboration will comprise a “health check” for specialist wealth managers and smaller asset managers by providing independent transaction reporting assessments. 

    The new proposition will see Kaizen’s proprietary testing technology combine with Alpha’s wide-ranging global asset and wealth management expertise to provide independent and expert assurance to wealth and asset managers that their transaction reporting arrangements meet the standards required by MiFID II.

    The combined proposition will check the accuracy of all of an institution’s reported data, assess the effectiveness of firms’ governance and control frameworks, and identify any gaps they might have in meeting the regulator’s transaction reporting obligations.

    “The proposition is an ideal solution for asset and wealth managers with lower trading volumes who require peace of mind that they are reporting accurately and correctly.” 

    The key benefits of the proposition include:

    • Full visibility of the quality of data reported to the regulator, including accuracy testing of all instruments, scenarios and data fields
    • Review of existing transaction reporting governance and oversight framework
    • Independent assessment and recommendations for regulatory compliance
    • Fast execution and outcomes

    The proposition comprises a discovery phase, using a detailed questionnaire to cover transaction reporting compliance and the process involved. This is followed by an evaluation phase involving a thorough assessment of the regulatory reporting control and governance framework.

    Reporting quality will be checked by Kaizen’s accuracy testing service which assesses all data fields on all reported transactions to provide a complete picture of reporting integrity. Recommendations will then made on whether transaction reporting controls are robust and whether the required level of testing is in place.

    Andrew Glessing, Head of Regulation, Compliance and Risk at Alpha FMC said:

    “We are delighted to work alongside Kaizen, who are the standard-setters when it comes to reporting assurance. With MiFID II requirements now a year old, this is the perfect time for specialist wealth and asset managers to take stock of their reporting quality and processes. We think this proposition fills a gap in the market by providing firms with market leading assurance tools and expert advice on their transaction reporting arrangements.”

    Dario Crispini, CEO of Kaizen, said:

    “This is an important milestone in Kaizen’s timeline. By joining forces with Alpha, we are able to offer the wealth and asset management sector a vital snapshot of the quality of its transaction reporting through an all-important health check. I am delighted we are working together.”

    “The proposition is an ideal solution for asset and wealth managers with lower trading volumes who require peace of mind that they are reporting accurately and correctly.  We recommend health checks take place periodically for ongoing visibility of reporting quality or in some circumstances, more regular testing may be required

    (ends)

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

  • SFTR RTS endorsement is still wait and see

    SFTR RTS endorsement is still wait and see

    Wednesday’s Trade & Transaction Reporting Northern Europe conference delivered updates from the European Commission (EC) and ESMA on the state of play for SFTR. It was a useful refresher course but did not deliver anything more tangible on reporting go-live timescales.

    European Commission Policy Officer Gerd Heinen said the delay in the EC’s adoption of the SFTR Regulatory Technical Standards (RTS) is the result of relatively minor technical legal concerns. He said they were highly motivated to endorse the RTS before year end but the EC did not agree with ESMA’s assertion that it was sufficient for them to endorse common standards for UTIs and branch LEIs for these fields to come into force, rather than amending the RTS itself. Once the RTS is endorsed by the EC, there is a three-month period for the European Parliament and the Council to adopt, followed by publication into the Official Journal. A further 20 days later, the RTS will come into force, consistent with a late Q1 2020 reporting go live for banks and investment firms. Market infrastructures (including CCPs), funds and large non-financial counterparties will follow at subsequent three-month intervals.

    ESMA Senior Policy Officer Nikolay Arnaudov reiterated that there were seven technical standards under SFTR (*). He highlighted that this was an EU transparency regime aimed at enhancing financial stability and contributing to the global securities financing transactions data collection exercise. He revisited the EMIR foundations of the report and the four data tables as building blocks (counterparty, loans & collateral, margin, and re-use). However, he would not be drawn any further on go-live dates beyond saying that the RTS amendments by the EC and the subsequent rejection of those amendments by ESMA, were in line with standard procedures.

    We continue to believe that an RTS (likely to be little different in substance from the March 2017 ESMA RTS) will be endorsed by the EC during November or December 2018. This would mean the reporting requirement goes live for banks and investment firms during the latter stages of Q1 2020, with an outside chance that it falls into April 2020.

    (*) The seven technical standards are:

    • RTS and ITS on SFT reporting
    • RTS and ITS on registration and extension of registration of trade repositories
    • RTS on data collection
    • RTS on data availability and access levels
    • ITS on exchange of data between authorities
  • EMIR trade reporting: lifting the lid on pairing and matching

    EMIR trade reporting: lifting the lid on pairing and matching

    EMIR trade reporting is part of the regulatory response to the financial crisis of 2007/2008.  It requires complete and accurate reporting of derivatives to trade repositories (TRs) to enable regulators to monitor for any build-up of systemic risk. Unlike Dodd Frank, EMIR is a dual reporting regime – both counterparties have a reporting obligation (if they are captured by EMIR). This has caused consternation among some parts of the industry as they believe the inherent duplication is wasteful and just increases costs for the industry. The other side of the argument is that dual-sided reporting reinforces the quality of the data by highlighting errors if the two sides of the report don’t “pair” or “match”. The TRs inform the reporting firms where the trade reports have not matched or even paired with the versions supplied by their counterparty.

    How do the TRs pair and match the trade reports?

    The first stage is to find out if both counterparties to the trade have a reporting obligation. This is done by examining the values in the ‘ID of the other counterparty’ field (1.4) and the ‘Country of the other Counterparty’ field (1.5). If these indicate that the ‘other counterparty’ has a reporting obligation, then the TR will set out to find the other side of the trade report – ie. to ‘pair’ it with the report submitted by the ‘other counterparty’.

    This ‘pairing’ is achieved by using the ‘Unique Trade Identifier’ (UTI) in each report and the LEIs in the ‘Reporting Counterparty ID’ field (1.2) and ‘ID of the Other Counterparty’ field (1.4). If the receiving TR does not have both sides of the report, it will request the data from the other TRs. If the two reporting counterparties have failed to use the same UTI, or if they have entered the wrong LEI in either counterparty field, then the TRs will not be able to ‘pair’ the trade.

    If the TRs are able to pair both ‘sides’ of the trade report, they will then check a subset of the fields to ensure that they ‘match’ (as each counterparty is reporting the same trade, the trade details should match). The current set of fields subject to this matching process are as follows:

    • Counterparty side
      (aka buy/sell indicator)
      if one counterparty
      has said ‘B’ the other
      must be ‘S’ and vice versa.
    • Contract Type
    • Asset Class
    • Product Classification Type
    • Product Classification
    • Product Identification Type
    • Product Identification
    • Underlying ID Type
    • Underlying ID
    • Notional Currency 1
    • Notional Currency 2
    • Trade ID
    • Venue of Execution
    • Compression
    • Price/Rate
    • Price Notation
    • Currency of Price
    • Notional
    • Price Multiplier
    • Quantity
    • Delivery Type
    • Execution Timestamp
    • Effective Date
    • Maturity Date
    • Termination Date
    • Confirmation Timestamp
    • Confirmation Means
    • Clearing Obligation
    • Cleared
    • Clearing Timestamp
    • CCP
    • Intragroup
    • Fixed Rate Leg 1
    • Fixed Rate Leg 2
    • Exchange Rate 1
    • Forward Exchange Rate
    • Exchange Rate Basis
    • Commodity Base
    • Commodity Details
    • Option Type
    • Option Exercise Style
    • Strike Price
    • Strike Price Notation
    • Maturity Date of the Underlying
    • Seniority
    • Reference Entity
    • Frequency of Payment
    • Series
    • Version
    • Index Factor
    • Tranche
    • Attachment Point
    • Detachment Point

    Many of these fields must match exactly, whilst others have to match within a tolerance. The matching on a few of these fields is conditional – for example, the Underlying ID must match where the Underlying ID Type is ‘I’ (for ISIN), but does not need to match where the Underlying ID Type is ‘X’ (for index) and free text has been used.

    What happens if the report fails to pair or all the fields do not match?

    The TRs will still accept the report, but they will inform the reporting counterparty if the report does not pair and it will also identify all the fields that have not matched if a pair has been found. The reporting counterparties are then expected to resolve the issues with their counterparty.

    How good are the pairing and matching rates?

    The pairing rates are a little disappointing and the matching rates are extremely low. Whilst the pairing rates have increased since the implementation of the revised reporting technical standards last year (probably due to the guidance on the UTI generating party being formally added to the regulation), the matching rates have not.

    Does this matter?

    Yes. Remember, one of the drivers behind dual-sided reporting is to reinforce the quality of the data and the disappointing rates indicate that there are issues with data quality. While firms may not have seen much action from the NCAs on EMIR data quality aspects (although the £35m fine levied by the UK FCA may have come as a shock), ESMA clearly flagged that it will focus on data quality in its annual report and work plan:

    “ESMA continued to closely engage with NCAs and exchange data to identify counterparties where reporting causes large amounts of breaks in the reconciliation process. ESMA plans to further intensify its engagement with the NCAs as part of the NCA cooperation process related to data quality.”

    Firms most definitely need to be aware that NCAs are monitoring the pairing and matching rates and could target those firms seen as outliers. Whilst the reason for unpaired or unmatched reports could lay with the ‘other counterparty’, those firms with comparatively low pairing and matching rates overall will be in the sights of the NCAs.

    What can firms do to improve matching rates?

    Low matching rates are a very good indication of poor quality EMIR trade reports. Sadly, there’s no short cut on this one; to improve the matching rates, firms need to improve the quality of the data they submit. This is where Kaizen can help. We can offer a reconciliation from the front office trading data to the data submitted in your name to the trade repository. We can also run an accuracy test on all your trade and position reports, including a check that your outstanding positions are an accurate reflection of your trade reports. We also offer training on the EMIR reporting standards. For further information please contact us.

  • Measure for measure: ESMA’s assessment of EU-wide supervisory measures for EMIR

    Measure for measure: ESMA’s assessment of EU-wide supervisory measures for EMIR

    Measure for Measure is classed as a comedy yet it is also considered one of Shakespeare’s problem plays as it has aspects of a tragedy. Dealing with the concepts of justice and virtue, the play sprang to mind when reading ESMA’s recently published report on EMIR supervisory measures.

    This is because the report, which runs to some 40 pages, highlights some significant differences in approach by the national competent authorities (NCAs) on supervision and enforcement of EMIR requirements, as well as the fines and other supervisory actions that have been undertaken to date. The report has both good and bad news for financial firms.

    Let’s start with the good: There have only been three fines raised for EMIR breaches to date across Europe. Two of these fines were levied by COVIP (Italy), one for €105k and the other for €60k both in relation to article 9 reporting breaches and article 11 breaches in respect of clearing activities. Within each jurisdiction, the maximum fines that can be levied are almost consistently low.

    And the bad news: the third fine in our list is the eye-watering £35m fine raised by the FCA for the non-reporting of 68 million exchange-traded derivative contracts.  The per-record penalty applied by the FCA was increased because of prior breaches under the MiFID I transaction reporting regime. That points to the FCA treating reporting failures as a single type of breach irrespective of the reporting obligation concerned. In its final notice, the FCA also took the time to highlight that insufficient testing was carried out to ensure the accuracy and completeness of reports as well as weaknesses in oversight arrangements. And in another piece of bad news, the largest potential fine for those countries that have a cap is France’s €100m. 

    Few investigations across Europe

    Perhaps it’s unsurprising, but not all authorities have been active in conducting investigations since the inception of EMIR.  What is surprising is how few investigations have been carried out across Europe when the number of entities, both financial and non-financial, falling within the scope of EMIR is so vast.  We can’t tell the true number of investigations conducted as the “more than 20” category (as shown below) could hold a great many but we would expect ESMA to have stopped there because it was closer to 20 than 40. 

    In terms of investigations carried out, Belgium is the standout performer with more than 20 investigations being run across reporting, clearing obligation, reporting, risk mitigation techniques and Article 11 in respect of Non-Financial counterparties. On the other end of the scale, we have a number of countries that haven’t undertaken any investigations at all including Ireland, Finland, Norway and the Netherlands.

    Number of investigations carried out on the reporting obligation by country in 2017:

    None

    BU

    CZ

    FI

    HR

    IE

    LV

    MT

    NL

    NO

    SI

    1 to 5

    FR

    EL

    SK

    UK

     

     

     

     

     

     

    6 to10

    AT

    DK

    PL

    SE

     

     

     

     

     

     

    11 to 20

    CY

    ES

    PT

     

     

     

     

     

     

     

    >20

    BE

    DE

    LU

    IT

     

     

     

     

     

     

     

    Another piece of bad news (at least for firms) is that we can expect ESMA to push for more harmonisation and more investigative activity.  ESMA and other competent authorities have been concerned with the quality of reporting under EMIR and MiFID. This, combined with the EMIR regime being in its 4th  year and matching rates across repositories remaining challenging, pressure to improve reporting will continue.  Pressure to ensure compliance with the clearing obligation and risk mitigation techniques can also be expected in the coming year.  

    The report also drew attention to the fact that no work seems to have been carried out in terms of the anti-evasion provisions of EMIR.  This would be a complex area to assess but firms should be prepared for questions on this which means having a handle on what guarantees are in place between EU group entities and non-EU entities.

    Penalties across the EU

    The report highlights the approach to penalties as an area where there is a low level of harmonisation. We’ve created the table below which shows the divergence in percentage terms of the maximum caps (France at €100m) and minimum penalties (Bulgaria €40k) across the EU. 

    In the UK and Spain, there is no stated penalty cap. In the case of the UK, a per record penalty is applied which means that the penalty regime scales to the level of reportable activity and degree of non-compliance for the firm concerned. 

    Country

    Percentage of maximum

    Max € (000)

    Notes

    Spain

    n/a

    –

    Variable no stated maximum

    France

    100.00%

    100,000

    Capped at less than 10x gain made or loss avoided

    United Kingdom

    n/a

    –

    Variable no stated maximum

    Finland (articles 4 & 10)

    10.00%

    10,000

    Capped at less than 10% turnover

    Sweden

    5.00%

    5,000

    Now capped at 10% of turnover but figures relate to a decision when the old rules applied.

    Belgium (National Bank)

    5.00%

    5,000

    Capped at less than 10% turnover

    Italy

    5.00%

    5,000

    Capped at less than 10% turnover

    Greece

    3.00%

    3,000

     

    Ireland

    2.50%

    2,500

     

    Poland

    2.50%

    2,500

    < 10% of turnover

    Belgium (FSMA)

    2.50%

    2,500

    Capped at 3x gain made or loss avoided

    Luxembourg

    1.50%

    1,500

    Capped at 5x gain made or loss avoided

    Netherlands

    1.00%

    1,000

     

    Cyprus

    0.70%

    700

    Capped at 2x gain made or loss avoided

    Germany

    0.50%

    500

     

    Czech Republic

    0.40%

    400

     

    Austria

    0.15%

    150

     

    Malta

    0.15%

    150

     

    Latvia (legal persons)

    0.14%

    142

     

    Finland (articles 9 & 11)

    0.10%

    100

     

    Slovenia

    0.10%

    100

     

    Croatia

    0.07%

    67

     

    Latvia (natural persons)

    0.06%

    57

     

    Bulgaria

    0.04%

    40

     

     

    NCA powers across the EU

    NCA powers are relatively consistent allowing them to: summon and interview personnel, conduct on-site investigations and inspect documents. They also all have the power to issue fines, issue binding and non-binding letters whilst some NCAs have the power to issue criminal sanctions against individuals. 

    Actions firms should be taking for EMIR reporting

    Firms should be reviewing their EMIR control environment. This means assessing the more difficult activities of regular accuracy testing, reference data testing and front to back reconciliations as well as ensuring the governance process is robust and up-to-date. 

    Governance arrangements need to be looking at the operation of the reporting process itself, the assurance process around accuracy and completeness of reporting but also the remediation process, ensuring that known issues are being appropriately escalated, prioritised and remediated which includes replaying records to correct historic errors. 

    While we are known for providing accuracy testing and reconciliation services, we also help our clients mature their broader reporting controls with our Control Framework – all are key components of our ReportShield™ quality assurance service. We also, in conjunction with our consultancy partner Elixirr, run remediation programmes to bring firms’ trade repository records into line.  If you would like to discuss your reporting controls please contact us.

    A variation of this article was published by Thomson Reuters Accelus (subscription only) on 20 July 2018. 

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

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

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

  • Kaizen officially presented with Queen’s Award for innovation

    Kaizen officially presented with Queen’s Award for innovation

    Kaizen Reporting has been formally presented with the prestigious Queen’s Award for Enterprise in innovation by the Lord Mayor of London, Andrew Parmley at a ceremony at Mansion House.

    The celebration followed an audience with the Queen at Buckingham Palace attended by our CEO and Founder Dario Crispini and Lead Data Scientist, Tamer Onder in July this year.

    The Queen’s Award was awarded to Kaizen in April this year for outstanding achievement in innovation for our ReportShield™ accuracy testing service that provides financial firms with full visibility of the quality of their regulatory reporting.

    The Lord Mayor said Kaizen was one of only very few firms in the City to receive the award, and that the work we were doing to improve data standards in the industry was pioneering:

    “What you are doing is incredibly important for the future of the city, for regulation and for the country,” he said.

    Kaizen CEO Dario Crispini said, “It’s an incredible honour to receive the award from the Lord Mayor of London at Mansion House, just down the road from our offices.  Winning the Queen’s Award is testament to our fantastic team who has developed and delivered this unique solution for firms with reporting obligations.”

    Read our press release from earlier in the year or find out more about ReportShield™ accuracy testing.

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

  • New rules = new tools: DTCC simplifies technology ahead of EMIR rewrite

    New rules = new tools: DTCC simplifies technology ahead of EMIR rewrite

    This week we attended the DTCC’s Partners Forum in London to get a taste of what the future holds for firms reporting data to the global trade repository (GTR).  As reporting rules become more complex across all global jurisdictions, the DTCC is aiming to simplify the functionality of the GTR.  Of course anything that makes reporting more straightforward is something we welcome here at Kaizen but there is a lot of work to do to prepare and resource appropriately to make sure you comply with the both changes in obligations and at DTCC. 

    The next phase of the GTR Re-architecture is going to be aligned with the go-live weekend for EMIR RTS on October 28th and is scheduled to be rolled out globally in 2018.

    If you have access to DTCC’s learning center you can see all of the latest updates here.

    Straightforward ingestion

    The new harmonized template is a ‘one size fits all’ solution to understanding how to format and upload data to the repository.  It acts as a one-stop-shop for finding the required information across all five asset classes and also enables filtering on specific products within asset classes, giving greater clarity on what fields are required to be reported.

    Practical processing

    DTCC have also adopted a new ‘latest is greatest’ approach in trade state calculation.  This removes the complexities of multiple submissions being interdependent on each other. UTI locks will also become a thing of the past which will make successful submission to the GTR easier.  However, this puts more responsibility on data submitters to ensure that counterparties are correct and to remove any incorrect submissions.  Delegated submissions will also be split into two parts and allow for separate processing per counterparty.

    Error messages are also being redesigned and will give greater insight into exactly where the error lies and what needs to be corrected.

    Upgraded reports and portal

    What we view as the greatest benefit of the Re-Architecture is the new way in which counterparties and third parties will have access and visibility to data.  Participants will have absolute transparency on what has been reported to the regulator and who it has been reported for.  Historic data will also be retrievable with the new search tool.  Eventually recurring queries can be scheduled to allow bespoke reports to be generated for every user on a timeline that will suit them.

    Changes in context

    The DTCC Re-Architecture is a big step in the right direction in terms of simplifying the way data is submitted and viewed but there is a lot of work to do to get to a place where you can truly take advantage of its benefits – and the clock is ticking.

    We are helping a number of firms understand and get the correct controls in place for the new EMIR RTS obligations due to come into force on I November, please get in contact if you would like to have a conversation about this or any other upcoming changes to reporting obligations. 

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

  • Significant changes proposed for EMIR reporting

    Significant changes proposed for EMIR reporting

    The European Commission has published its legislative proposals to amend European Market Infrastructure Regulation (EMIR).

    If implemented, they will result in significant changes to the current reporting obligations.

    Here is a quick rundown of the key changes being proposed:

    • Good news if you have not reported your historic trades – they are no longer needed
    • ETD reporting is going single sided, with the central counterparties (CCPs) picking up the burden.  The question remains for non-EU CCPs though.
    • Similarly, small non-financial counterparties (NFCs) will be able to rely upon financial counterparties (FCs) to take up the reporting burden.
    • Finally, trade repositories are going to be asked to ensure the quality of the data.

    The proposals follow on from a public consultation on EMIR and the Call for Evidence on financial regulation.  They also form part of the 2016 Commission’s Regulatory Fitness and Performance programme (REFIT).

    Yesterday the Commission also said it intended to present further proposed changes to EMIR on derivatives clearing as its scale and importance grows.

    We’ll be writing a more in-depth analysis of the proposals in the coming weeks.

    More information can be found on the European Commission’s EMIR webpage.

  • Kaizen Reporting’s ReportShield™ testing wins Queen’s Award for innovation!

    Kaizen Reporting’s ReportShield™ testing wins Queen’s Award for innovation!

    Regulatory technology firm, Kaizen Reporting is delighted to announce that it has won a Queen’s Award for Enterprise, the highest accolade in UK business.

    Kaizen’s award comes in the innovation category for the prestigious business awards which are announced today by the Business Secretary Greg Clark.

    Kaizen won the award for its ReportShield quality assurance service which tests 100% of regulatory reports. This is in contrast to traditional methods which only test small data samples.  The in-depth testing gives Kaizen’s clients full sight of any errors within their reporting data so they can be corrected.

    Changing the way reporting is done

    Kaizen CEO and Founder, Dario Crispini, said, “Winning a Queen’s Award for innovation is a huge honour and recognition of the way Kaizen’s ReportShield testing is changing the way reporting is delivered throughout the industry.”

    Regulatory trade and transaction reporting has become absolutely vital since the financial crisis in 2007. Regulators rely on regulatory reporting to detect insider dealing, rogue trading and the build-up of systemic risk (one of the primary causes of the crisis).

    However regulatory reporting is becoming increasingly complex and financial firms have struggled to get it right.  This has resulted, in some cases, in regulatory fines running into millions of pounds and costly bills to retrospectively fix the errors.

    Improving the quality of regulatory reporting

    In response to this, Dario, a former regulator, and Ian Rennie, industry expert, set up Kaizen Reporting in 2013 to help improve the quality of firms’ regulatory reporting.   

    By combining their regulatory knowledge with data science, Kaizen developed ReportShield, an automated testing service that fully assesses the quality of regulatory reporting data.

    Dario continues, “Incorrect regulatory reporting is a major industry problem that Kaizen wants to help solve. ReportShield is helping both sides of the industry – firms can be confident of their reporting integrity and avoid fines, and the regulator receives good quality transaction reports, ensuring market transparency.”

    Dario added, “I’d like to personally thank the Kaizen team for their dedication and expertise in developing ReportShield, and also our clients and partners for their support over the past three years.” 

    Winners of the Queen’s Award are invited to attend a reception at Buckingham Palace later in the year.

    ends

    About the Queen’s Awards

    Established in 1965, the Queen’s Awards for Enterprise are for outstanding achievement by UK businesses in the categories of innovation, international trade and sustainable development. Awards for innovation are given to businesses that can demonstrate that their innovative products or services are commercially successful.

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

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