Category: SFTR Reporting

Securities Financing Transactions Regulation (SFTR) Reporting regulates securities financing activities by setting out reporting requirements, data access, collection, verification, aggregation, comparison and publication of data on securities financing transactions (SFTs) by trade repositories (TRs). TRs centrally collect and maintain the records of SFTs. They play a central role in enhancing the transparency of SFTs markets and reducing risks to financial stability. With the first phase of reporting obligations due to go live in October 2020, check out Kaizen’s insights.

  • SFTR Reporting goes live for the buy-side

    SFTR Reporting goes live for the buy-side

    Our SFTR Reporting Specialist Jonathan Lee on the challenges buy-side firms are facing as the SFTR reporting obligation goes live for them today.  The interview covers the following questions:

    • SFTR reporting seemed to go smoothly for the first and second cohort of firms in July. Is it likely to be the same for the buy-side?
    • How is SFTR reporting different for buy-side firms than sell-side firms?
    • What’s your advice for buy-side firms planning to fully delegate their reporting?
    • Do you expect reporting quality to be better or worse?
    • Any advice for buy-side firms for the next few weeks?

    Jonathan’s also written a blog on the same topic: SFTR Challenges for Buy-Side Firms

    Read Jonathan’s blog

     

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

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

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

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

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

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

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

  • SFTR – the day that wasn’t

    SFTR – the day that wasn’t

    Today was going to be the day…

    For those of us involved in SFTR reporting, Easter was cancelled, last minute testing was to be cast aside and reporting was going into production. The initial report was expected to be small given that it was to cover securities financing transactions trading during the period Easter Saturday to Easter Monday but nevertheless we all waited anxiously in case of the inevitable teething problems that occur.

    Instead, the world was plunged into crisis and an unexpected delay has happened. It will be more than four and a half years from the publication of the regulation to go-live for the now combined first and second phases – Banks, CCPs and CSDs. Crisis or not, this is a great gift for an industry that was not entirely ready for this regulation to become a reality.

    Here are the top three things that banks should be doing to ensure that the additional three months are maximised:

    1. Test, test, test

    Like Covid-19, the key to reporting accuracy is testing, testing and more testing. Once satisfied that SIT and UAT testing are functioning correctly internally, with files passing the trade repository validation rules and ideally independently checked for completeness and accuracy, then it’s time to test with counterparties, market infrastructures, triparty agents, agent lenders and across the industry.

    2. Put the right controls in place

    Controls around reporting should never have been a Day 2 delivery but invariably were destined to be with an April go-live. This excuse has now gone. Therefore, SFTR reporting should have a full set of procedures, reporting policy and decisions made should be fully documented. A testing and reconciliation plan should be put in place internally, with appropriate management information in place to cover reporting completeness, timeliness, trade repository receipts and reconciliation breaks and the closure of those breaks.

    3. Don’t mark your own homework

    Implementing an independent quality assurance layer through periodic regulatory testing will ensure the regulation, technical standards, guidelines and updates have been implemented correctly and remain correctly interpreted as they and the business evolves. It will ensure that the firm is not marking their own homework and losing sight of the less obvious reporting issues they face. It will also reassure key stakeholders and national competent authorities that the regulatory obligations are taken seriously and managed most efficiently.     

    We are helping a number of firms prepare for SFTR reporting including pre go-live accuracy testing of reports as well as providing a full suite of post go-live assurance services to ensure the accuracy and completeness of your reporting.

    Contact us for a conversation with one of our regulatory experts.

    Join our Kaizen community of regulatory reporting professionals for blogs, events and insights from our regulatory subject matter experts.

  • SFTR latest developments: COVID-19 delays, backloading, MiFID II reporting of SFTs, and a new best practice guide…

    SFTR latest developments: COVID-19 delays, backloading, MiFID II reporting of SFTs, and a new best practice guide…

    In amongst the backdrop of this very human and truly global crisis, it has been refreshing to see how innovative and productive our sector of the financial services industry has remained. Efforts continue to ensure that banks and other securities financing transaction counterparties are able to comply with SFTR reporting requirements. Banks will be joined by market infrastructures in going live on 13 July, while the buy-side will follow on 12 October and non-financial counterparties from 11 January 2021.  

    Following the announcement from ESMA on 19 March regarding efforts to delay the first phase of SFTR reporting, there have been further announcements and clarifications to aid the industry during these difficult times. The particular challenge that ESMA has faced has been in how to enact appropriate changes and delays in a suitably technical way to avoid needing executive approval from the EU Parliament, Council and Commission.

    Backloading is no more

    Backloading has become a particular area of concern and confusion. But we can now say with confidence that backloading (the need to report transactions that were opened before go-live date and still open 180 days later) has been removed as a requirement across all phases of reporting.

    ESMA attempted to clarify this as best it could with an update to the initial public statement on 26 March which stated, “ESMA therefore expects competent authorities not to prioritise their supervisory actions towards counterparties, entities responsible for reporting and investment firms in respect of their reporting obligations pursuant to SFTR or MIFIR, regarding SFTs concluded between 13 April 2020 and 13 July 2020, and SFTs subject to backloading under SFTR, and to generally apply their risk-based approach in the exercise of supervisory powers in their day-to-day enforcement of applicable legislation in this area in a proportionate manner.”

    Much more telling have been the conversations that ESMA has had with trade associations such as ICMA and ISLA and in statements from certain national competent authorities (NCAs). The French regulator (AMF) has been most explicit in stating “Concerning the backloading obligations and following ESMA’s update, market participants are expected to focus exclusively on the reporting of SFTs concluded on or after 13 July 2020.” Other NCAs have also provided off the record feedback to the trade associations to the same effect.

    MiFID II reporting of SFTs with ESCB members is also put back until 13 July 2020

    The ESMA statement above also helps clarify that in line with the delay to SFTR reporting, the need to provide MiFID II RTS 22 Transaction Reports in relation to SFTs facing European System of Central Banks (ESCB) counterparties. These reports are also not required from banks, investment firms and credit institutions until 13 July 2020.

    ISLA issues SFTR Best Practice Guide  

    ISLA published its SFTR Best Practice Guide earlier this week to assist securities lending market participants with their SFTR reporting. The online guide explains how to apply the regulatory technical standards across the SFTR counterparty, loan & collateral and collateral re-use data tables and how to populate each respective field. While only available to ISLA members at present, this provides a good complement to the ICMA Guide to Reporting under SFTR which is freely available.

    We are helping a number of firms prepare for SFTR reporting including offering pre go-live accuracy testing of reports as well as a full suite of post go-live assurance services. Contact us for a conversation with one of our regulatory experts.

     

  • ESMA pragmatism allows three-month COVID-19 delay to SFTR implementation

    ESMA pragmatism allows three-month COVID-19 delay to SFTR implementation

    ESMA has stepped up in light of the current COVID-19/Coronavirus crisis.

    Following the joint appeal to ESMA and the European Commission by ICMA and ISLA on Monday 16 March, ESMA has today announced a three-month delay to SFTR implementation. They have created this technical delay in three steps:

    1. Requesting that National Competent Authorities do not prioritise supervisory actions until 13 July 2020
    2. ESMA not registering any Trade Repositories (TRs) ahead of 13 April 2020
    3. Stating that ESMA will also not be available to record details of Securities Financing Transactions (SFTs).

    These three actions ensure “counterparties, entities responsible for reporting and report submitting entities will be unable to report by the reporting start date.”

    “ESMA expects TRs to be registered sufficiently ahead of the next phase of the reporting regime, i.e. 13th July 2020 for credit institutions, investment firms, CCPs and CSDs and relevant third-country entities to start reporting as of this date.”

    The ESMA public statement has the full details.

    Kaizen is offering quality assurance testing as well as core training on the reporting obligations. Get in touch to find out more about how we can get you ready for reporting under SFTR.

  • ESMA and the European Commission clarify treatment of Alternative Investment Funds (AIFs) under SFTR

    ESMA and the European Commission clarify treatment of Alternative Investment Funds (AIFs) under SFTR

    The European Commission and ESMA have both dispelled any concerns that non-EU AIFs were being brought into scope for SFTR reporting if their AIFMs were EU-based.

    A paragraph in the Final Report that accompanied the Level 3 Guidelines on SFTR reporting on 6 January, raised concerns as it appeared to bring non-EU AIFs into scope for SFTR reporting if their Alternative Investment Fund Manager (AIFM) was based in the EU. This statement, while apparently contradicting elements of SFTR Level 1 (the regulation itself), Level 2 (the regulatory and implementation technical standards (RTS & ITS)) and other elements of the guidelines, nevertheless raised fears that extra territoriality was sought by EU regulators.

    In response to trade association concerns, both ESMA and the Commission have responded in letters stating that non-EU AIFs will not come into scope for SFTR reporting regardless of where their AIFM is based.

    Furthermore, ESMA provides further clarification about the nature of the Final Report and how to distinguish it from the Guidelines themselves. The Final Report provides feedback on the consultation responses, a summary of proposals in the consultation paper and an assessment of the feedback. They hasten to add that while some of the feedback resulted in amendments to the guidelines, other elements were discarded. They further emphasise that reporting parties should focus on the Guidelines and not the Final Report as it is the Guidelines that contain all the clarifications and examples to enable reporters to be compliant with the Level 1 SFTR regulation.

    The Commission in its response, re-states that SFTR Article 2(1) limits the application of the regulation to “(a) a counterparty to an SFT that is established (i) in the Union, including all its branches irrespective of where they are located; (ii) in a third country, if the SFT is concluded in the course of the operations of a branch in the Union of that counterparty.” Therefore, an AIF not established in the Union is not subject to the obligations set out in Article 4(1) SFTR.    

    Now we can only hope for such definitive feedback from the Commission and ESMA in relation to settlement finality and the reporting of bilateral variation margins…to be continued!

    You can read the letters here.

    We are helping a number of investment firms prepare to report accurately for SFTR.  Please contact us for a complementary consultation with one of our regulatory experts. 

  • SFTR reporting final guidelines – ready, steady….go!

    SFTR reporting final guidelines – ready, steady….go!

    In this blog, we explain the securities financing transactions reporting final guidelines

    It was good news last week for those of us who’ve been waiting for ESMA to publish the final guidelines for SFTR reporting. The overriding principle of the regulation which these new guidelines reinforce, is that reporting firms are expected to populate the database in as comprehensive, timely and accurate basis as possible. These guidelines, the final report (responding to consultation feedback), updated validation rules and a statement on non-EU issuer LEIs offer some contradictions and will not please all market participants but do provide much of this framework.

    Of course this blog is no substitute for reading the guidelines but here are some of the highlights:

    Timeline

    ESMA confirmed reporting obligations for credit institutions and investment firms (banks) go-live on Monday 13 April (for EU jurisdictions that do not observe Easter Monday as a public holiday) or Tuesday 14 April for those that do. In either case, reporting firms are required to send reports for any SFTs executed on or after Saturday 11 April. Market infrastructures will follow accordingly on 13 July, buy-side on 12 October and non-financial counterparties on 11 January 2021.

    Non-EU issuer LEIs

    ESMA acknowledged that only 30% of non-EU issued securities currently have an issuer LEI and therefore have removed the need to populate these security loan and security collateral issuer LEI fields for non-EU issued securities until 13 April 2021.

    Third party executed reportable trades

    ESMA have provided clarity on which SFTs executed on behalf of the reporting counterparty through powers of attorney are reportable under SFTR. The following are reportable:

    • CSD fails curing transactions in which securities are automatically borrowed. Credit or securities provided to avoid settlement fails are collateralised with the securities account of the borrowing CSD participant
    • Auto-collateralisation transactions where payment banks or their clients are counterparties.
    • CREST client auto-collateralisation trades.

    However, CCP “daylight lending facilities”, auto-collateralisation trades with an ESCB counterparty and intraday credit/overdrafts resulting from fails-curing transactions are all out of scope.

    Third country reporting obligations

    ESMA has advised that in bringing SFTR into line with EMIR, for a transaction to be in-scope for reporting by an EU branch of a 3rd country entity, the term ‘conclusion’ relates only to instances in where they are a counterparty to the trade. i.e. the counterparty where the SFT is booked. References to the EU branch merely supervising trading in a third country entity have been removed.

    Settlement fails reporting

    The guidelines require reporting parties to modify the maturity date (roll it forward to the next day or an expected settlement date) in the reports they send on settlement date +1 if a transaction is failing. It must be modified on this day because going forwards without modification it will be closed and not possible to re-open it. Providing this feedback loop on settlement status is going to be tricky.

    However, the treatment of partial returns is different where “a delayed settlement that does not result in a cancellation of the partial return, should not be reported.” 

    UTI failure

    There is no prescribed approach in the guidelines about what to do if your counterparty – responsible for creating and sharing the UTI – fails to provide it ahead of the COB T+1 reporting deadline. It simply states that “counterparties should ensure a timely solution.” Essentially reporting parties must chase and not report anything until the UTI has been shared, and document all of the steps taken to obtain the UTI.

    Valuation considerations / market values

    Market values should be reported as of close of business each working day. The values used for collateral and exposure management purposes should use most recent market prices or bilaterally agree valuations with counterparties if none are readily available. This requirement to agree values contradicts with a further statement about the unavailability of price information. This relates to some suspended shares and illiquid fixed income securities where counterparties should report the valuation contractually agreed upon conclusion of an SFT. Only then should the market value be updated with a valuation, when new price information becomes available.

    ECB FX rates should be used for valuations or bilaterally agreed rates if none exists. The need to align FX rates is a concern for the industry, given many reporting parties use an enterprise rate, not only for SFTs but across their businesses.

    Re-use reporting with delegated reports

    If reporting has been delegated, the counterparty to which reporting has been delegated is not responsible for the reporting of the estimated re-use of the collateral. NFCs are responsible for calculating the estimated re-use themselves and in providing the estimate to the counterparty in charge of reporting in a timely manner.

    CFI sourcing

    The guidelines state that counterparties should retrieve CFIs from ANNA, National Numbering Agency (NNA) or, if not available, request it at the relevant NNA of the instrument. Unfortunately by acknowledging that it is reconcilable, they contradict themselves by saying that if it doesn’t exist in the official sources then it should be agreed between counterparties. It certainly seems that official sources should be exhausted and CFIs should be requested from the NNA before attempting to derive CFIs.

    Security / collateral quality

    Ratings should be instrument-based and use internal assessments of credit quality rather than mechanistic reliance on credit rating agencies, who use measurements such as local vs foreign currency, short vs long term investment to reflect security specifics. ESMA acknowledge the resultant higher rate of reconciliation breaks. However, they fail to acknowledge sensitivity around sharing any aspect of internal ratings and the fact that many counterparties will not have fully on-boarded many securities that appear on settlement date in collateral baskets. This is likely to require some industry driven solutions.

    Variation margining 

    There is fresh guidance on how to report the collateral given or taken on a net exposure basis through post on-leg, value date, variation margin calls to complement the original trade level collateral. Counterparties should send single collateral update messages to reflect these bilateral variation margin calls. The direction of the collateral should be expressed with a sign against its market value i.e. negative for rows of collateral given and positive for collateral taken.

    Floating rate transactions

    When reporting floating rates, counterparties should indicate the relevant rate and the applicable spread. They should only provide updates when they agree to change the rate or the spread but not on a daily basis.

    Report tracking numbers (RTN) and open offer trades

    In reporting trades executed on venues where execution is contingent on central clearing (open offer basis), including DBV trades, reporting firms are not required to populate the report tracking number (RTN).  It is important to note that the clearing time and execution time would be expected to match.

    In instances in which a trade is bilaterally executed and subsequently subject to clearing (even same day), it requires the prior UTI to be reported as the RTN.

    Our view of the guidelines is that they do provide some clarity and are a step forward from where we were. However they do not provide all the answers and contradict in some places. Because of the diverse scope of the regulation, one size doesn’t fit all and it’s now for the market to interpret as best we can. Good luck and let us know how you’re getting on. 

    Kaizen’s ReportShield™ accuracy testing, advanced regulatory reconcilation and reference data testing services will help ensure your reporting is accurate from day 1 of go-live.  

    Contact us to find out more about how you can make a smooth transition to SFTR reporting.

  • 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

     

     

  • SFTR validation rules and schemas from the ESMA cauldron…

    SFTR validation rules and schemas from the ESMA cauldron…

    Halloween saw some new ghoulish delights appear from the ESMA cauldron with the publication of SFTR validation rules (revised following the summer consultation) and XML schemas for reporting. ESMA has released four documents covering:

    1. SFTR report validation rules
    2. Counterparty and Trade Repository (TR) data exchange XML schema
    3. Intra-TR data exchange XML schema
    4. TR to authority data exchange XML schema.

    We have created a marked changes version of the latest validation rules to highlight the differences.

    Tighter but more logical 

    The validation rules have been tightened up to reflect instances in which fields that business logic dictates should be mandatory or conditional are no longer optional. For example, the loan field ‘security quality’ is now conditional rather than optional for new securities lending transactions. In other instances, fields that were not rationally mandatory (e.g. ‘maturity {date} of the security’ fields for both loan and collateral) are now conditional. The rules generally make more sense, particularly in relation to the two changes noted below.

    Full reporting – not delta reporting

    Modifications and corrections at both trade and position level now require all of the original counterparty table fields to be populated. In most cases, they also require the same fields to be populated in the loan and collateral table as in the original NEWT report in accordance with the same mandatory and conditional rules as the original report. This requirement for full reporting of modifications and corrections should be clarified in the level three guidelines when published by ESMA later this quarter.

    Bilateral Margining Simplified

    The ‘counterparty side’ is no longer required for collateral updates, making bilateral margin reporting simpler. Since stating whether the reporting party is a collateral giver or collateral taker is no longer a pre-requisite of providing a bilateral margining collateral update (COLU) or any other COLU report, it is much more straightforward to report instances of collateral flowing in both directions with the same other counterparty.

    The references to negative values of securities in the ‘counterparty side’ validation field notes on format and content have also been removed (in addition to this field being no longer required for COLU reports). Instead, the ‘collateral quantity or nominal amount’ is now permitted to be negative, enabling you to report collateral moves in either direction – as a margin giver or taker for example. You are also now permitted to use negative values in the ‘price per unit’ field. Again, we hope for further clarification when the reporting guidelines are released.

    The publication of schemas, the cementing of validation rules and a number of key clarifications (as highlighted) puts the industry in a much greater state of readiness for reporting – now only five months away.  Our advice?  Don’t now wait for final reporting guidelines (due later in Q4) but focus full steam ahead on implementation, testing and establishing your controls environment.  And if you’d like to discuss how we can ensure you are compliant with SFTR reporting rules, please don’t hesitate to contact us.

    The new validation rules and schemas are available on the SFTR section of our website.

     

  • The scariest regulatory reporting changes facing you this Halloween

    The scariest regulatory reporting changes facing you this Halloween

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

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

    In Thunder comes Brexit

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

    In Lightning comes SMCR

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

    In Rain comes SFTR

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

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

    Author: Chris Machinbeth

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

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

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

    Register

     

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

  • In the news: Jonathan Lee speaks to Best Execution

    In the news: Jonathan Lee speaks to Best Execution

    The long and winding road of SFTR

    There have been several twists and turns in the Securities Financing Transaction Regulation (SFTR) journey but the finishing line is in sight. There are still kinks to be ironed out but the general view is that the legislation will see the light of the day next year.

    A previous blog by Senior Regulatory Reporting Specialist, Jonathan Lee, has been featured in an article by Lynn Strongin Dodds at Best Execution. Jonathan highlights “there are still a few fundamental questions that need to be clarified in order to support a timely build for SFTR reporting.” He adds that there are also concerns about the availability of data for reporting and some confusion about the reporting of settlement fails. “The general consensus was that perfect settlement would be assumed unless both parties chose to modify a transaction to reflect a default or extended fail”.

    Read the full article here. 

     

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

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

  • Collaborative reporting expected to be in demand for SFTR

    Collaborative reporting expected to be in demand for SFTR

    There is likely to be a high demand for collaborative reporting –  and other forms of delegated reporting – under SFTR, according to the results of our recent webinar with UnaVista. In this blog, we cover the results of the three polling questions asked during the webinar and what they mean for the industry.

    Q: About which of these are you the most concerned with regards to cleared trade reporting?

    1. Timelines of data from the CCP (25%)
    2. Market data availability (20%)
    3. Matching tolerances on collateral valuations (32%)
    4. Accuracy of Margin Reporting (11%)
    5. Correct application of RTNs (11%)

    Cleared trades are by nature significantly more likely to be consistently booked and subsequently reported. The benefits of clearing in counterparty risk reduction and in providing a single data set for many of the reporting fields seems likely to outweigh a number of concerns about the availability of data from CCPs. Nevertheless, pricing anomalies (resulting in concerns by 32% of participants about matching tolerances on collateral valuations) are common among SFT market participants even across different lines of the same business and these differences are likely to promote standardisation, best practices and efficiencies going forward.

    Q: Do you use any form of delegated reporting for other regulatory reporting regimes?

    1. Yes, we use delegated reporting for other regimes (e.g. MiFIR or EMIR) (55%)
    2. No, we have never used delegated reporting (32%)
    3. We have only used assisted reporting (14%)

    Again, interesting to see that 69% of participants use (or claim to use) some form of delegation. It adds weight to the recommendation that these parties focus on the quality of reporting to ensure that they are compliant with the regulation and keeping their reporting counterparty under appropriate scrutiny regarding the service provided.

    Q: How comfortable are you offering optional delegated reporting for SFTR?

    1. Entirely comfortable; this is a mature service for other regimes that we will simply extend to SFTR (37%)
    2. Will reluctantly offer; due to commercial pressures from client dictate we must offer it (23%)
    3. Will offer but not full delegation (7%)
    4. Will not offer any delegated reporting (33%)

    The proportion of participants that stated they were “entirely comfortable” was surprising, particularly given the challenges associated with populating the re-use table for third parties. The “will offer but not full delegation,” option seems more likely where clients use facilities offered by the trade repositories to provide a mirror of the broker dealer’s report to enable ease of reporting but only 7% responded in this way. The 33% stating they will not offer any delegated reporting maybe a little misleading given the mixed nature of participants (both buy-side and sell-side) and the commercial pressures that are likely to fall as reporting deadlines approach.

    In practice, to offer some form of delegated reporting under SFTR is likely to prove a must-do commercially on the sell-side but few operations managers will take it on with much enthusiasm (or resource). We think both parties should be focussed on data quality. The client should ensure that they are meeting their legal obligations (over the completeness, accuracy and timeliness of their reporting – that they cannot delegate). The reporting party should ensure that reports are correct (for both parties) and they do not only meet the trade repository validation, pairing and matching requirements. Two wrongs after all do not make a right! 

    If you’d like support with your SFTR preparation, we can help. Led by our SFTR Reporting Specialist Jonathan Lee, our pre go-live services include programme design and implementation, development of an appropriate controls environment, pre go-live testing of your reporting data and training on the reporting requirements.  Please contact us to find out more or visit our SFTR reporting page for more details.

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

  • ANNA alleviates the SFTR Issuer LEI Conundrum

    SFTR presents firms with many data challenges, including capturing the correct issuer LEI. There are ten unique instances in which reporting parties are required to provide an LEI and one of the most challenging of these is the LEI for an issuer of a security.     

    The Association of National Numbering Agencies (ANNA) and the Global Legal Entity Identifier Foundation (GLEIF) announced the go-live for their new initiative to start linking ISIN codes with LEIs on the 4th April 2019.

    The published ISIN to LEI mapping will be freely available on the GLEIF website and already contains mappings for in excess of 1 million ISINs. While details of the issuer LEI are already available on the FIRDS database for securities admitted to trade in the EEA, coverage is lacking outside this region. Given the global nature of collateral used in SFT transactions and the requirement to populate the issuer LEI for every piece of security collateral, this is a very welcome development to facilitate the reporting requirements.

    We hope in future that such an initiative extends further into other SFTR reference data elements such as the CFI codes, maturity of the security (where applicable), security type and high level security quality. Nevertheless this is a valuable contribution to successful reporting.

    Did you know Kaizen provides training on the SFTR reporting requirements? For further details, please see our SFTR Reporting Core Training page.

     

  • SFTR Regulatory Technical Standards published in the Official Journal

    SFTR Regulatory Technical Standards published in the Official Journal

    Click to enlarge

    We now have legal certainty around the SFTR Article 4 reporting timelines as the ten delegated acts, implementing regulations and annexes have been published in today’s Official Journal of the European Union. Each respective delegated regulation is available here. These requirements appear to be unchanged from those published and adopted by the European Commission on 13th December 2018.

    Timelines

    The SFTR Regulatory Technical Standards (RTS) and Implementing Technical Standards (ITS) come into force 20 days after publication (11th April 2019). This provides the basis behind reporting obligations becoming live on the following dates:

    • Monday 13th April 2020 – Credit Institutions (Banks) & Investment Firms
    • Monday 13th July 2020 – CCPs & CSDs
    • Monday 12th October 2020 – Pension Funds, Insurance/Reinsurance Companies, AIFs & UCITs (Buy-side)
    • Monday 11th January 2021 – Non-Financial Institutions.

    It’s time to get ready…

    Now that we have legal certainty, firms should be fully engaged in SFTR planning, building, testing and controls initiatives in readiness for go-live. We can help to meet your training, scoping, pre-go live testing, vendor selection, controls agenda and post go-live quality assurance to ensure reporting accuracy for this most complex of reporting requirements.  Please contact us for a complementary consultation or find out more in our SFTR section of our website.

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

  • Santa’s SFTR gift extends to EMIR

    Santa’s SFTR gift extends to EMIR

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

    No real change

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

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

    SONIA

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

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

  • SFTR: The final countdown

    SFTR: The final countdown

    UPDATED 18 December with additional links and further details on timelines for trade repository reconciliations for certain fields.

    Now that the ITS and RTS have been released, we have greater clarity on the nature of the European Commission standards for SFTR as well as the timelines. Our SFTR specialist Jonathan Lee highlights the key changes and the timeline for implementation. 

    On Thursday 13 December 2018, the European Commission (EC) adopted Regulatory Technical Standards (RTS) and Implementation Technical Standards (ITS) covering Article 4 ‘Transparency of SFTs’ reporting requirements under Securities Financing Transaction Reporting (SFTR). This critical step puts the wheels in motion for SFTR to become a live reporting obligation and sets an increasingly clear timeframe for the reporting to start from April 2020.

    Official links: EC RTS, RTS Annex 1, and EC ITS and ITS Annex 1 and RTS for Trade Repositories (TR), RTS for TR Annexes and RTS for Access to details of SFTs held in TRs.

    SFTR go-live timeline 

    The RTS and ITS have been subject to some minor revisions since the ESMA publication, therefore we can confirm that it will be subject to a three month scrutiny period by the European Parliament & Council (not the one- month period for an unchanged RTS, nor the six-month period for an RTS subject to significant, material change). Following this scrutiny, it will be published in the Official Journal of the European Union.

    The timeline from here is as follows in the graphic below, although experience tells us to leave approximately one month leeway around these dates:

    SFTR reporting timeline infographic
    Click image to enlarge

    Changes to the RTS

    While this announcement was much more about certainty of timing (after an extended delay), enabling European SFT counterparties to plan and budget for implementation, nonetheless there are some changes of note relative to the 31st March 2017 ESMA text. We can confirm that:

    1. It will be possible to include agent lenders on repo trades.
    2. There is a not-applicable option on termination optionality for repo and securities lending trades.
    3. There is more substantive guidance on the Unique Trade Identifier (UTI) creation waterfall (see Article 3, page 4 of the ITS).
    4. Timelines for Trade Repository reconciliations for certain fields have changed. The following fields in the Transaction Data table Loan section: Security quality, Maturity of the security, Jurisdiction of the issuer, LEI of the issuer and Security type  – have been brought forward to Day 1. They were previously Day 1 +24 months in the 2017 ESMA text. This will present a more pressing data quality challenge. As a small concession in Transaction Data Collateral section: Collateral unit of measure, Price currency, Price per unit and Collateral market value have been pushed back from Day 1 to Day 1 +24 months. This brings the importance of independent reference data testing to the fore. 
    5. Finally and perhaps most significantly, any bad blood between the EC and ESMA over the adoption of UTIs and branch LEIs appears to have ended. The EC has stated that that once standards are finalised and considered suitable for the purposes of reporting SFTs, the regulation will be amended accordingly. In the interim, ISO codes should be used to identify branches and bilaterally agreed UTIs should be used to identify SFTs.    

    We can help you put the right controls in place

    As we look forward to the festive season and find time to step away from all this talk of SFTR, we would encourage you to ensure that projects are now underway. Now is the time to start SFTR budgeting, hiring, planning, building and thinking about testing, controls and governance if your project has not already begun. 

    Need some help with your SFTR reporting implementation? Contact us for a consultation to find out how you can put the right controls in place to ensure accurate and effective reporting from day one. We are also rolling out an SFTR training course early in 2019 so again, please get in touch to register your interest or find out more.

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

    Another year of significant growth, success and development for Kaizen

    FOR IMMEDIATE RELEASE

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

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

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

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

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

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

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

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

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

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

    (ends)

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

  • SFTR – the countdown to compliance begins

    SFTR – the countdown to compliance begins

    Commenting on the adoption of the Regulatory Technical Standards for SFTR, our Senior Regulatory Reporting Specialist, Jonathan Lee said,

    “The European Commission’s decision to adopt the Regulatory Technical Standards (RTS) and Implementation Technical Standards (ITS) for Securities Financing Transaction Reporting (SFTR) on 13th December 2018 presents the final piece in the puzzle of certainty around the Article 4 regulatory reporting obligation go-live. It also dictates the timeline to implementation. The European Parliament and Council of Ministers now have a three-month scrutiny period, followed by publication in the Official Journal of the European Union, a further 20 days will pass and the regulation comes into force. Once in force, Credit Institutions (Banks) and Investment Firms have 12 months to implement reporting, Central Counterparties (CCPs) and Central Securities Depositories (CSDs) have 15 months, Pension Funds, Insurance/Reinsurance Companies, AIFs and UCITs have 18 months and Non-Financial Counterparties have 21 months. On that basis, reporting will start in earnest in April (possibly May) 2020 for Banks with the others to follow in three month increments.     

    “At present, the actual content of the RTS and ITS have only been released to a select few (it is not yet public) but we understand that few changes have been made from the ESMA 31st March 2017 and EC July 2018 versions. Now is the time to start SFTR budgeting, hiring, planning, building and thinking about testing, controls and governance if your project has not already kicked off.”

    Need some help with your SFTR reporting implementation? Contact us for a consultation to find out how you can put the right controls in place to ensure accurate and effective reporting. 

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

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

  • 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
  • SFTR: ESMA dismissive of proposed amendments from European Commission

    SFTR: ESMA dismissive of proposed amendments from European Commission

    ESMA have now published their opinion on proposed amendments to SFTR technical standards. This mirrors the letter that they published, sent to the commission on 4 September.

    ESMA dismiss outright the proposed changes made by the European Commission, citing the importance of the original text and the limitations of the Commission’s proposed alternatives. ESMA are adamant that they must continue to include LEIs, ISINs and UTIs in order to be consistent with EMIR and international developments in global standards (Branch LEIs and UTIs). They also state the desire to “Future Proof” SFTR.

    It is fair comment to suggest that some of the EC proposals did water down some of the ESMA proposed data standards for SFTR and that ESMA have made a number of valid points. If ESMA had decided to carry through these proposals then it was likely to introduce some confusion over the timely adoption of UTIs (without which trade repository pairing and matching would have become an even greater challenge). It was also likely to slow the international adoption of branch LEIs. 

    All in all, this would appear to be much ado about nothing. The changes (or lack of changes) from the original “Final RTS” published by ESMA on 31st March 2017 will not have any material impact on the SFTR delivery. It is just unfortunate that the pragmatic steps that the EC proposed to incorporate the option of including agent lenders on repo trades and in providing a not-applicable option for termination optionality on repo and securities lending trades will also be omitted.

    In practical terms, there is likely to be a few additional weeks of delay to the publication of the SFTR RTS into the official journal of the European Union as negotiations between ESMA and the EC continue. The EC could potentially overrule ESMA on some of these matters. This delay is likely to push out the go-live for SFTR reporting further into Q1 2020, starting with the banks & investment firms.

    For a consultation on your SFTR reporting preparation, please contact us.

  • In the news: Jonathan Lee speaks to Inside Data Management

    In the news: Jonathan Lee speaks to Inside Data Management

    Our SFTR reporting specialist Jonathan Lee recently spoke with Amelia Axelsen at Waters Technology about the challenges of SFTR implementation.

    “Implementing the necessary controls around accuracy and completeness is going to be arduous,” he says.

    Read the full article: Illuminated data – SFTR may reach too far

    Read Jonathan’s blog on the challenges of SFTR implementation. 

    Contact us for an initial conversation about getting ready for SFTR reporting. 

  • SFTR: Challenges of implementation

    SFTR: Challenges of implementation

    In Part 2 of our introduction to SFTR, Jonathan Lee looks ahead at the implementation of the regulation and some of the data quality challenges firms need to be thinking about now.

    STOP PRESS! The European Commission broke with protocol in publishing a letter sent to ESMA on 2 August (generally they do not publish in August), stating that they planned to endorse with amendments, the draft Regulatory Technical Standards (RTS) and Implementing Technical Standards (ITS). This gives ESMA a further six weeks to submit revised drafts that reflect these changes.

    The changes whilst minor, are extensive. There are a large number of changes in semantics, providing further clarity through simpler language. The material changes relate to concerns that LEIs for branches and standards around UTIs may not be ready in time for go-live. Furthermore, they have incorporated industry feedback that agent lenders may be used on repo trades and that there needs to be a not-applicable option for termination optionality on repo and securities lending trades.

    These amendments and the six weeks for ESMA to respond will introduce some additional delay to SFTR Article 4 reporting go-live. Nevertheless, we anticipate that the RTS will be published in the official journal of the European Union at the end of 2018 or early 2019 and that reporting will go-live for banks & investment firms in Q1 2020 with market infrastructures, fund managers and non-financial counterparties to follow at three month subsequent intervals.

    A herculean task

    Under SFTR, participants in the European securities financing markets will be required to provide daily reporting to a trade repository (TR) of not only every new trade, amendment, correction, error and cancelation but also the majority of lifecycle events, collateral valuations and legal entity wide collateral re-use statistics. This herculean reporting task will hand a legal obligation to all but the smallest non-financial counterparties to report between 61-128 fields (product dependent) across four reporting tables. Furthermore, reporting parties will be tasked with ensuring that between 36-48 of these fields can be matched between reporting parties (intra and inter trade repository) for ESMA to be able to interpret the data and the ESCB Datastore to be able to create the Europe wide data aggregations. We envisage that handling trade repository reconciliation queries on SFTR is set to become a significant and complex operational task post go-live.

    Bringing together securities financing markets

    Securities financing markets are currently more fragmented and disparate than many other markets currently subject to significant regulatory reporting regimes. There is generally less precedent, less market convention and less infrastructure in place than for many other markets. The regulation seeks implicitly to set about changing this. To put forward the repo market as an example, there are still many instances in which the functioning of the market is very settlements driven, there are many manual processes and any pre-settlement matching is limited in scope or subscription. SFTR will encourage many OTC telephone or messaging based trades to move onto venues. This would certainly help overcome many booking discrepancies, contractual and lifecycle handling differences between counterparties. It will also help in the creation of a common dataset to in turn be reported to the TRs.

    Data sourcing will be painful

    SFTR requires that reporting firms not only provide the common reporting standards (ISINs for collateral, LEIs for counterparties and collateral issuers, MIC codes for venues, CFI codes for collateral classification and unique trade identifiers (UTIs)) – with mandatory use of UTIs and branch LEIs potentially to be introduced later – but also much additional classification and derivation too. Many of the required fields are largely unfamiliar within this industry and will present data sourcing difficulties. Indeed, in many cases, firms will need to look beyond risk management, trading and settlement systems in order to source the data. Siloed securities financing businesses will also need to look beyond their own businesses to capture data across entire legal entities in order to meet requirements such as re-use reporting.

    Less risk, greater transparency

    ESMA and the European regulators have made it very clear that they require SFTR reports to be a true reflection of a firm’s books and records. They have provided very little sympathy for proposed pragmatic reporting solutions that ensure higher degrees of trade repository matching rates if this deviates from original trade bookings or fails to reflect fundamental business practice or booking discrepancies that the securities financing industry is experiencing. The regulators expect firms to be able to prove that they are continuing to evolve and improve both their booking and reporting practices to create an environment of less risk, greater efficiency and the greater transparency that comes from strengthening regulatory reporting compliance. The reporting deadline itself may prove something of a ‘Big Bang’ but ensuring that the controls and quality assurance framework continue to make evolutionary and iterative progress is not.

    Data quality assurance should be part of SFTR plan

    At Kaizen Reporting, we support trade association industry initiatives that encourage securities financing businesses to shape up in advance of SFTR go-live.  We also support bilateral reconciliations to better understand firms’ and industry reporting issues and the creation of industry-wide best practice documents to encourage enhanced booking practices and behaviours. In addition, we would urge reporting parties to embark on the incorporation of trade level and reference data quality assurance within their project plans. Firms should look to perform both internal and external reconciliations to ensure reporting data is complete, accurate and uncorrupted by systems. Furthermore, applying Kaizen’s ReportShield™ to your post go-live plans will help tremendously in ensuring Senior Managers are kept abreast of reporting quality and reassuring the regulatory authorities of the firm’s level of diligence. Contact us for an initial conversation about getting ready for SFTR reporting. 

    Read Part 1: SFTR – if you can’t beat em, join em which focuses on the background and context of SFTR.

  • SFTR: If you can’t beat ’em, join ’em…

    SFTR: If you can’t beat ’em, join ’em…

    In the first of a two-part blog, our newly appointed SFTR reporting expert Jonathan Lee looks at the background and context of the Securities Financing and Transactions Regulation. 

    The author of this blog is about to take an “If you can’t beat ‘em, join ‘em” approach in following our European regulators into their summer recess. The European Commission publication freeze will shortly kick in and the probable timeline for publication of the final Regulatory Technical Standards (RTS) for Securities Financing Transaction Reporting will be held back until September this year at the earliest. This in turn will result in SFTR Article 4 Reporting delayed until Q1 2020 for banks and investment firms, with market infrastructures, fund managers and large non-financial counterparties to follow at subsequent three month intervals.

    Waiting a little longer…

    Many of us working closely on the new Securities Financing Transaction Reporting European regulatory regime have been on tenterhooks ever since the publication of ESMA’s Final Report on Technical Standards under SFTR in March 2017. Indeed, the initial guidance was that the European Commission would decide whether to endorse the technical standards within three months of that date and for reporting for banks and investment firms to follow approximately 15 months later (September/October 2018). We have now slipped approximately 15 months from this original target date. Nevertheless, as September approaches, we are likely to finally have some report timing finality.  

    Securities financing influence is high 

    The premise for SFTR reporting has always been a little different from the mainstream reporting regimes exemplified by MiFIR, EMIR, Dodd Frank and so forth. Securities Financing markets are less widely understood and often seen as a market utility or service offering rather than a mainstream ‘risk’ market. Nevertheless, of the four markets covered by SFTR (Repo, Buy-sellback, Securities Lending and Margin Lending); EUR 7.25 trillion contracts were recorded as outstanding within the scope of the highly respected ICMA ERCC Semi-Annual European Repo market survey (for Repo markets alone) in December 2017. The ability of securities financing markets to influence leverage, liquidity and overall global systemic market function is high.

    Financial crisis

    SFTR Regulation (November 2015) stems from the financial crisis. Repo and other securities financing markets were seen at the centre of aspects of the crisis, perhaps most notably in the collapse of Lehman Brothers (September 2008). Concerns over shadow banking, the lack of transparency, build-up of leverage, interconnectedness and pro-cyclicality inspired much debate and discussion among G20 members from 2011. This culminated in FSB reports on Shadow Banking in October 2011 and further FSB reports specific to Securities Lending and Repo from April 2012 onwards. SFTR itself sets out to enact the FSB 2015 report “Standards and Processes for Global Securities Financing Data Collection and Aggregation.”

    The greatest challenge of SFTR is the extent to which European regulators seek to ‘gold plate’ the global guidelines. The Financial Stability Board (FSB) stipulates the need for retrospective, periodic, single sided, settled position level reporting that can readily be aggregated regionally and globally. The European regulation sets out the need for very granular, daily, two-sided, trade and lifecycle event level reporting. Invariably, this is going to be very challenging to implement, manage and control by reporting parties and perhaps equally tricky for regulators to interpret, comprehend and aggregate.

    Implementation of SFTR and data quality implications will be covered in a second blog from Jonathan early next week.

  • In the news: Jonathan Lee speaks to the International Financial Law Review

    In the news: Jonathan Lee speaks to the International Financial Law Review

    Our SFTR reporting specialist Jonathan Lee spoke to reporter Sharon Kimathi at the International Financial Law Review (IFLR) about the challenges firms are facing with the implementation of SFTR.

    Here’s an extract from the article:

    Securities lending desks and trade repositories feel that the new regulation’s 153 data fields are cumbersome, with significant potential for errors and duplication. The UTI requirement is a particular headache.

    “There are a large number of fields to complete, not only in terms of the initial transaction but also covering lifecycle events that take place during the course of the transaction,” says Jonathan. 

    Read the full article. 

  • Media release: Kaizen hires industry expert to consolidate SFTR offering

    Media release: Kaizen hires industry expert to consolidate SFTR offering

    We’re delighted to announce that Jonathan Lee is to head up our recently-formed SFTR-related operation. The former Fixed Income Regulatory Reporting Manager at JP Morgan Chase is a leading voice on regulation and specifically on SFTR. Lee was previously head of the International Capital Markets Association (ICMA)’s SFTR taskforce and has spearheaded industry responses and discussions related to the challenges it brings. With more than 10 years of regulatory reporting experience and 9 years as an Interest Rate Strategist at Barclays Capital under his belt, he will be tasked with working with Kaizen’s clients to ensure we offer the same high level of service for SFTR as we do for regulations such as MiFID II and EMIR.

    SFTR is a new reporting obligation aimed to bring transparency to the securities financing industry and shadow banking sector.  Kaizen’s existing client base of tier 1 and 2 banks, fund managers and brokers increasingly consider SFTR a top priority.  Lee joins Kaizen in the middle of an exciting period of expansion for us and the new SFTR section further bolsters its team of regulatory reporting experts and data scientists.  

    Holding an MSc in International Securities, Investment and Banking from the ICMA centre, Reading University, Jonathan’s role of Chair of ICMA’s European Repo & Collateral Council (ERCC) taskforce on SFTR has meant working closely with industry participants, ESMA, ECB and FSB on implementation, giving him a truly unique perspective on the intricacies of the regulation and making him an invaluable asset to financial institutions. Endorsement of the final draft Regulatory Technical Standards by the European Commission is expected imminently and the estimated go-live of SFTR transaction reporting is expected up to 15 months after that.

    Dario Crispini, CEO of Kaizen, commented: “We are delighted to bring someone of Jonathan’s calibre on board.  We want to ensure that our clients are prepared well in advance for SFTR transaction reporting go-live.  Jonathan will work with our clients on their SFTR preparedness and internally with our data scientists to develop testing and reconciliations so that our clients have the same confidence and assurance for SFTR as they currently enjoy with MiFID II, EMIR and other G20 regulations. I am incredibly pleased to welcome him to the team.”

    Ian Rennie, Managing Director, added: “SFTR is the next big challenge in the reporting space and anything that is of primary concern to our clients is of course of equal concern to us. I’m excited to have enlisted Jonathan, whom I see as the best person for the job. He clearly has extensive and specialised knowledge of SFTR as well as wide-ranging influence and experience in the industry.”

    Jonathan Lee said: “Kaizen is growing rapidly and is working with a wide range of clients for whom SFTR is becoming increasingly important. I’m looking forward to joining such a knowledgeable team, and I am very much looking forward to working with our clients.”

    For an initial consultation with Jonathan on preparing for SFTR reporting, please contact him directly on jonathan.lee@kaizenreporting.com

    Editorial contacts

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

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

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

    For immediate release – Thursday 14 December 2017

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

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

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

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

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

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

    ***ends***

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

  • Obligation to use LEIs picks up pace

    Obligation to use LEIs picks up pace

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

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

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

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