Compliance · Securities financing

SFTR

Applies to counterparties entering into securities financing transactions (repos, securities lending and buy-sell backs), which must be reported to a trade repository.

Key obligations

SFTR brought the reporting logic of EMIR to the market of securities financing transactions: two-sided reporting, collateral data including reuse, and full lifecycle events for every SFT. The population of reporting entities is narrower than under EMIR, but the data model is just as demanding.

  • SFT reporting: repos, securities lending and buy-sell backs reported to a trade repository, at T+1.
  • Full lifecycle: modifications, collateral updates, corrections and terminations: every event reported.
  • Collateral & reuse: collateral composition and reuse data alongside the transactions themselves.
  • Reconciliation & rejections: two-sided matching and repository feedback handled by workflow.
Case study
Investment fund company (TFI) SFTRCesarz_SFTR

SFT reporting delivered in a full-support model

Challenge: A reporting obligation for securities financing transactions: no in-house team or tooling, and a T+1 deadline.

Solution: Cesarz_SFTR with full support: source-data mapping, repository testing and takeover of response monitoring.

Talk about a similar project →
3 mo. implementation
100% reports within T+1
99.8% repository acceptance rate

Client names are protected by confidentiality agreements. Figures verified internally; as of 2025.

Make the obligation
routine.