SFTR reporting for repos and securities lending

Article 3 names four types. A repurchase transaction, where securities are sold with an agreement to buy them back at a set price and date, including the reverse direction. The lending and borrowing of securities or commodities against a fee. A buy-sell back or sell-buy back, which achieves the same economics through two separate outright trades. And a margin lending transaction, where a firm extends credit to buy or hold securities, the prime brokerage case.

A liquidity swap and a collateral swap fall within the definition. A total return swap stays outside it, as a derivative under EMIR, but SFTR brings it into the fund disclosure duties, which is why a fund using TRS has an SFTR obligation without having an SFTR reporting obligation.

Article 4 puts the duty on both counterparties: each reports the details of an SFT it has concluded, and of any modification or termination, no later than the working day following the event. Where no registered trade repository is available for a type of SFT, the report goes to ESMA instead. Records are kept for at least five years after the transaction ends.

For funds the duty shifts. A UCITS management company reports for the UCITS, and an alternative investment fund manager for the AIF. Where a financial counterparty trades with a small non-financial counterparty, the financial counterparty reports for both and is responsible for doing so, which mirrors the EMIR arrangement on derivative reporting. Central banks, public debt management bodies and the Bank for International Settlements are outside the regime under Article 2.

Commission Implementing Regulation (EU) 2019/363 sets the tables: counterparty data, loan and collateral data, margin data and collateral reuse data, together well over 150 fields. Both counterparties report, so the two submissions have to agree, and the trade repository reconciles roughly 96 of the fields from the loan and collateral set.

The matching breaks in predictable places. Collateral allocated after the trade arrives in a later message than the loan, so the two sides' timing differs. A triparty agent allocating a basket produces collateral detail one counterparty sees and the other receives late. A floating rebate rate reported with a different day count convention produces a mismatch in a field nobody thought was contentious. The ESMA guidelines on SFTR reporting are the reference for how each field should be populated, which is the document a break investigation ends in.

Reuse means a counterparty that received securities as collateral uses them again, by pledging them onward, selling them or lending them. SFTR requires reporting of the collateral available for reuse and of the collateral actually reused, where the securities can be distinguished from the firm's own assets; where cash collateral is involved, the reinvestment details are reported too. Because an exact figure is often impossible when the securities are fungible with others, the regime accepts an estimate calculated from the firm's total reusable collateral.

Article 15 adds the conduct duty behind the data. A counterparty may only reuse financial instruments received as collateral where it has informed the providing counterparty in writing of the risks and consequences, and has obtained that counterparty's prior express consent, evidenced by a signature or a legally equivalent form. The instruments are also transferred to an account in the receiving counterparty's name. That consent requirement is the one firms discover late, because it sits in a conduct article inside a reporting regulation.

Articles 13 and 14 put a disclosure duty on fund managers independent of the reporting. The periodic reports of a UCITS or an AIF set out the use made of SFTs and total return swaps: the aggregate amounts lent or repoed, the ten largest counterparties with their exposures, the collateral by type, quality and currency, the maturity profile, the share of collateral held in custody by the manager, and how the returns are split between the fund and the manager or agent.

The prospectus or pre-contractual document states which SFTs the fund is authorized to use and that it does use them. A fund that lends securities and discloses only a sentence about it has an incomplete prospectus, and the breakdown in the annual report is the one investors and selectors actually compare. Our page on asset management in Germany covers the fund side more broadly.

BaFin, as the competent authority for German counterparties, with ESMA registering and supervising the trade repositories themselves. BaFin receives access to the reported data and can act against a counterparty that reports late, incompletely or not at all; the Wertpapierhandelsgesetz carries the national sanctioning provisions.

The division matters when something goes wrong. A rejection at the repository is a technical matter with the repository; a persistent failure to report is a supervisory matter with BaFin. Firms that treat a growing rejection file as the repository's problem have misread which of the two they are in.

The same transactions drive three different numbers, and only SFTR asks about the chain. A repo funds an asset, so it shows in the liquidity coverage ratio as a secured funding position with an outflow assumption that depends on the collateral quality and the counterparty. It shows on the balance sheet under the accounting treatment for a transfer that does not pass derecognition. And it shows in SFTR with the collateral identified security by security.

That is why an SFTR project usually finds data the treasury and the accountants did not need: the individual security behind a basket, the haircut applied, the reuse status. Our page on liquidity stress testing covers the outflow side, where the rollover assumption on secured funding is one of the hardest scenario inputs.