Tag: Securities Financing Transaction Regulation

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