ESMA SFTR

Understand, validate and oversee EU SFTR reporting with confidence

EU SFTR reporting is designed to improve transparency in securities financing markets and support monitoring of systemic and counterparty risk. ESMA describes SFTR as creating a Union framework under which details of securities financing transactions can be efficiently reported to trade repositories and information disclosed to investors where required.

For firms in scope, the challenge is not just submitting SFT data, but demonstrating that reportable transactions are identified correctly, and that collateral, reuse and lifecycle data is complete, accurate, and the control framework around reporting can withstand regulatory scrutiny.

What is EU SFTR Reporting?

EU SFTR reporting refers to the obligation to report the details of securities financing transactions to a trade repository under the Securities Financing Transactions Regulation. The framework covers repo, securities lending, buy-sell back / sell-buy back and margin lending activity, together with lifecycle and collateral-related reporting.

ESMA supports the regime through guidelines on reporting under SFTR and related technical standards. These guidelines are key to interpreting how the reporting framework should be applied in practice.

Who is required to report under EU SFTR reporting?

EU SFTR reporting obligations apply broadly to financial counterparties and non-financial counterparties in scope under the Regulation. The regime is generally dual-sided, although financial counterparties may be responsible for reporting both sides of the transaction on behalf of EU-established NFC- counterparties in relevant cases.

That means firms need to understand not only whether an SFT is reportable, but also how reporting responsibility is allocated and how delegated or representative reporting models should be controlled in practice.

Scope and EU nexus

EU SFTR scope analysis turns on whether the transaction is an SFT in scope, the status of the counterparties and, in some cases, whether the transaction is conducted through branches. ESMA’s guidance addresses the application of SFTR reporting obligations to SFTs concluded by branches and by non-EU entities with EU branches.

For cross-border firms, that makes branch mapping, entity classification, collateral model and lifecycle ownership especially important. In practice, firms need to be confident they can apply the perimeter consistently across legal entities, desks and reporting workflows.

What must be reported?

EU SFTR requires reporting of the details of securities financing transactions and associated lifecycle and collateral information to a trade repository. The reporting model includes both sides of the transaction, lifecycle updates and key data fields relevant to reuse and collateral.

In practice, that means firms need to control:

• Product classification

• Counterparty identifiers

• Collateral data

• Reuse indicators

• Lifecycle events

• Reconciliation of breaks

• Pairing and matching

Reporting deadlines

EU SFTR reporting is generally subject to a T+1 reporting timeline. Firms must report no later than the next working day following the conclusion, modification or termination of an SFT.

For firms in scope, that means reporting timeliness depends on timely event capture, accurate collateral and lifecycle data, and a process capable of identifying and correcting errors before counterparty-side mismatches become embedded in the repository data.

Is EU SFTR reporting single-sided, dual-sided or delegated?

EU SFTR is best understood as a generally dual-sided reporting regime, with the financial-counterparty-on-behalf-of-NFC- model in relevant cases. That means counterparties still need to understand the data and control environment, even where operational reporting is being done for them.

Operationally, firms may rely on delegated reporting or internal reporting hubs, but that does not remove the need for oversight of what reaches the trade repository and how it reconciles against the other side.

SFTR also imposes a regulatory requirement for pairing and matching of reports between both counterparties at the trade repository level, meaning firms need to ensure that submitted data aligns accurately with their counterparty’s report and any breaks are identified, investigated and resolved in a timely manner.

Are there EU SFTR reporting exemptions or reliefs?

EU SFTR includes responsibility reallocations and detailed perimeter rules, but the practical challenge is usually less about broad exemptions and more about correct classification, branch treatment and allocation of reporting responsibility. ESMA’s guidance is the key source for applying these points operationally. The practical point is that firms should not assume delegated or counterparty reporting removes the need for active control. The repository record still needs to be complete, timely and defensible.

Certain entities and transactions are exempt from EU SFTR reporting. These include transactions entered into by the Bank for International Settlements (BIS), the Bank of England, foreign central banks, and other public bodies responsible for managing public debt, as well as members of the European System of Central Banks (ESCB).

Consequences of non-compliance

EU SFTR reporting failures create regulatory, operational and reputational risk, particularly where firms cannot evidence control over collateral, reuse, lifecycle reporting and counterparty reconciliation. SFTR is specifically aimed at improving transparency in securities financing markets, which means weak reporting quality undermines a core supervisory objective.

Firms are expected to identify and address misreporting issues in a timely manner, including investigating root causes, implementing remediation and, where required, notifying the regulator via an Errors and Omissions notification. This includes ensuring that reported data is complete, accurate and consistent with counterparty submissions, with appropriate controls in place to prevent recurrence.

For firms in scope, the expectation is clear: SFTR reporting must be accurate, complete, timely and supported by a defensible control framework.

How En:ACT helps with EU SFTR reporting oversight

En:ACT helps firms strengthen control over their EU SFTR reporting obligations by ingesting raw transaction data from any source system, performing books and records reconciliation, and assessing 100% of transactions and fields against the applicable EU SFTR rules.

Using transparent, regulator-linked logic, the platform identifies:

• Product classification issues

• Field-level errors

• Cross-field inconsistencies

• Collateral mismatches

• Reuse errors

• Lifecycle reporting gaps

• Counterparty-side inconsistencies

Each identified issue is linked directly to the specific EU SFTR rule breached, giving firms a clear view of what is wrong, why it matters and where remediation is required.

En:ACT also ensures rules are kept up to date to reflect developments across:

• Regulatory text

• Regulator guidance

• Consultation papers

• Relevant industry papers

For EU SFTR specifically, that means firms benefit from rule coverage maintained in line with the SFTR legal framework and ESMA reporting guidance.

Specialist EU SFTR expertise from the Novatus Intelligence team

Our EU SFTR capability is supported by specialists within the Novatus Intelligence team, including SMEs with backgrounds across banking, asset management, product and regulation.

For EU SFTR specifically, that means access to specialists who understand SFT reporting, collateral data, branch treatment and trade repository control challenges.

‍

Common EU SFTR reporting challenges

Some of the most common EU SFTR reporting issues include:

• Collateral and reuse mismatches

• Weak lifecycle processing

• Branch-treatment errors

• Poor source-to-report reconciliation

• Inconsistent counterparty-side reporting

• Delegated reporting oversight gaps

In many cases, issues arise not from a single incorrect field, but from inconsistencies between the booked transaction, the collateral position and the final reported record.

‍

Why firms choose En:ACT for EU SFTR oversight

Firms use En:ACT because it gives them more than a validation tool. It provides a control framework around EU SFTR reporting.

With En:ACT, firms can:

• Test reporting quality against transparent rule logic

• Reconcile source data to reported data

• Identify issues before they become regulatory problems

• Evidence oversight of delegated reporting

• Benchmark reporting quality over time

• Prepare for regulatory change ahead of go-live

The result is stronger reporting assurance, better governance and a clearer line of sight from raw transaction data to trade repository submission quality.

‍