Buy-side urged do more on securities finance regs

Fund managers need to up the ante on their preparations for the Securities Financing Transaction Regulation (SFTR) amid concerns there has been scant attention paid to it.

By Editorial
Fund managers need to up the ante on their preparations for the Securities Financing Transaction Regulation (SFTR) amid concerns there has been scant attention paid to it.

The Regulation, which was published in the Official Journal of the European Union (EU) on December 23, 2015 took effect on January 12, 2016 although the Level 2 technical standards are still being discussed by the European Securities and Markets Authority (ESMA). As such, compliance is some way away, but the impact it will have on financial institutions should not be underestimated.

SFTR forces firms to report information around their securities financing transactions (SFTs), such as repurchase transactions, any securities lending or borrowings, buy-sell backs, sell-buy-backs and collateral swaps such as total return swaps. Firms must report data on their SFTs on a T+1 basis to the six ESMA approved trade repositories. These are the Depository Trust & Clearing Corporation (DTCC), KDPW, Regis-TR, UnaVista, CME Trade Repository and ICE Trade Vault Europe.

“SFTR has not really been on the radars of many fund managers and we have only been fielding inquiries in the last few weeks. However, we anticipate the number of inquiries will increase significantly over time. One of the issues is that ESMA has not finalized all of the details yet, particularly around the reporting template. As such, it is very difficult for fund managers to prepare until they have the granular information around reporting,” said Abigail Bell, partner at Dechert in London.

One regulatory expert, speaking anonymously, said SFT reporting was mirrored on EMIR and likely to fall victim to many of the setbacks faced by EMIR. Perhaps the biggest issue for SFTR surrounds dual-sided reporting whereby both counterparties to a transaction report details of that trade. To enable trade repositories to match these trades, a counterparty must generate a Unique Trade Identifier (UTI), an alphanumeric code designed to enable trade repositories to reconcile reported trades. The generation of UTIs under EMIR has not been straightforward as there was little clarity from regulators in 2014 over which counterparty created the UTI. As such, both counterparties have generated UTIs under EMIR making it difficult for trade repositories to reconcile reported OTCs and ETDs.

“EMIR was introduced in February 2014 and nearly two years later, only a small proportion of OTCs and ETDs are being matched by the trade repositories. The majority are not being matched by trade repositories. This is because ESMA demands dual-sided reporting, which means both counterparties have to report. However, there has yet to be any clarity over which counterparty generates the UTI. As such, we have both counterparties to an OTC trade generating UTIs and these may not be the same code. This is a problem, and yet ESMA is still demanding firms undertake dual-sided reporting under SFTR. I believe the same issues that impacted EMIR will affect SFTR,” said the regulatory expert.

Some have urged ESMA to adopt the stance embraced by the Commodity Futures Trading Commission (CFTC) which allows for single sided reporting of derivatives to swap data repositories (SDRs). The inability to match derivative transactions at an EU trade repository level means that build-ups of systemic risk in the derivatives market are potentially going un-checked by regulators. Daniel Jordan, associate at Dechert, said there was an explicit reference in the regulation that ESMA must report on the appropriateness of single-sided reporting within 24 months of SFTR coming into force. As such, there is a possibility that single-sided reporting could be introduced in due course.

SFTR data reports will include information around SFT counterparties, the principal amount, currency and assets used as collateral and whether that collateral is available for re-use. SFTR also imposes additional disclosure obligations on managers of UCITS and Alternative Investment Funds (AIFs), which the policy expert described as onerous. It is believed service providers who undertook delegated reporting under EMIR will assist with SFTR reporting. “The majority of vendors offering delegated reporting will probably assist with SFTR although there are questions over who will take liability and whether there will be an increase in fees for providing such a service,” commented Bell.

Investors must be notified by AIFMs and UCITS about how SFTs and total return swaps are used in their portfolios in bi-annual and annual reports, as well as prospectuses and pre-contract documentation. This will include information about the absolute amount of assets engaged in SFTs and total return swaps, and how much this makes up of the fund’s total assets.

SFTR also seeks to improve transparency around the re-use of collateral. Again, firms must obtain written consent and agreement from clients permitting the re-use of collateral. Furthermore, clients must be made fully aware of the risks that collateral re-use can entail. The reporting obligations will require firms to build new systems and processes, and this will add to the workloads of asset managers.

However, this might not be too onerous. “When collateral is posted to a counterparty such as a prime broker, it is done so based on the principle of title transfer. In other words, the counterparty has a right of re-use. As long as the re-hypothecation practices are outlined in the hedge fund-investor agreement, then that should be satisfactory,” commented Bell.

There is speculation as to whether this will herald a further EU-wide clampdown on re-hypothecation. Regulators have made it no secret they wish to clamp-down on certain shadow banking activities, and there is speculation the EU could introduce limits around the amount of assets that can be re-hypothecated in line with practices adopted by the Securities and Exchange Commission (SEC).

«