ESMA Securitisation Reporting

The ESMA Reporting Regime

ESMA's securitisation disclosure framework requires originators, sponsors, and SSPEs to submit granular loan-level data to registered repositories. For compliance teams, this means wrestling with detailed templates, strict validation rules, and regular submission deadlines.

The EU Securitisation Regulation (Regulation (EU) 2017/2402) introduced comprehensive disclosure requirements designed to give investors standardised access to underlying asset data. Whether a securitisation qualifies as Simple, Transparent and Standardised (STS) or not, the reporting obligations apply—though STS transactions face additional disclosure requirements.

The operative EU framework is EU 2020/1224 (RTS) and EU 2020/1225 (ITS), binding since 2021. April 2024 was a technical update to validation rules only, not a new framework.

The regime applies to both public and private securitisations, though private transactions have some reporting flexibilities. For ABF practitioners, understanding these requirements matters even for warehouse facilities—as assets eventually moving to public markets need data captured in the required format from origination.

Who Reports What

Article 5 Investor Due Diligence

The EU Securitisation Regulation imposes symmetrical obligations on institutional investors (Article 5) — they must verify access to all required disclosures before investing and perform ongoing monitoring. This investor-side due diligence obligation mirrors the issuer's disclosure duty.

STS Disclosure Requirements

Simple, Transparent and Standardised (STS) securitisations enjoy preferential regulatory capital treatment but face enhanced disclosure requirements. The “STS notification” submitted to ESMA includes detailed confirmations that specific criteria are met.

The STS Framework

STS Notification Content

The STS notification is a detailed document confirming compliance with each criterion. For each requirement, the notification must explainhow the transaction meets it—not merely assert that it does.

Third-Party Verification

While not mandatory, originators may engage an authorised third-party verifier to confirm STS compliance. This provides investors with independent assurance and can support marketing. However, the originator/sponsor remains responsible for STS status—verification does not shift liability.

For STS securitisations, issuers may engage a Third-Party Verifier (TPV) registered with ESMA to independently confirm STS compliance. TPVs include Kroll and STS Verification International. The ESMA Peer Review (March 2025) flagged NCAs for over-reliance on TPV attestations without independent verification.

Synthetic STS notifications are submitted via email to STSnotifications@esma.europa.eu — there is no automated portal for synthetic STS as there is for traditional STS notifications.

Loan-Level Data Templates

ESMA's loan-level templates are the core of securitisation reporting. Each asset class has its own template with hundreds of fields covering borrower information, loan terms, collateral details, and performance data.

Template Categories

The templates are organised by underlying asset type. Each template reflects the specific data points relevant to that asset class, though they share common structural elements.

Field Categories Within Templates

Template Updates

ESMA periodically updates templates to reflect market developments and supervisory experience. Template changes typically have transition periods, but implementing new fields can require significant IT development—especially if the required data wasn't captured at origination.

ESMA's February 2025 consultation proposed a simplified private securitisation template (Annex XVI) for transactions not publicly marketed. As of March 2026, this has not yet been adopted — this remains forthcoming.

XML & CSV Formats

Submissions to securitisation repositories can be made in XML or CSV format. Each has trade-offs, and the choice often depends on originator systems capabilities and volume.

XML Schema Structure

ESMA publishes XML schemas (XSD files) defining the exact structure required. Submissions must validate against these schemas before the repository accepts them. The mandatory XML schema version is v1.3.1 (required since September 1, 2021). Issuers must use this specific schema for all loan-level data submissions.

<SecuritisationData>
  <Header>
    <ReportingEntity>LEI_CODE_HERE</ReportingEntity>
    <SecuritisationIdentifier>ISIN/UTI</SecuritisationIdentifier>
    <ReportingDate>2026-01-15</ReportingDate>
    <DataCutOffDate>2025-12-31</DataCutOffDate>
  </Header>
  <UnderlyingExposures>
    <Exposure>
      <ExposureIdentifier>LOAN001</ExposureIdentifier>
      <OriginalBalance>250000.00</OriginalBalance>
      <CurrentBalance>237500.00</CurrentBalance>
      <InterestRateType>FLOATING</InterestRateType>
      <!-- ... 200+ more fields ... -->
    </Exposure>
    <!-- ... additional exposures ... -->
  </UnderlyingExposures>
</SecuritisationData>

CSV Field Mapping

CSV submissions use a flat file structure with specific column ordering. The repository provides mapping documents showing which column corresponds to which template field.

Common Pain Points

ESMA reporting looks straightforward on paper but creates operational challenges in practice. Teams new to securitisation reporting consistently encounter the same obstacles.

Template Complexity

Validation Errors

Repository validation catches data quality issues before submission is accepted. Common validation failures include:

Data Mapping Challenges

Reporting Timeline & Deadlines

ESMA reporting follows a regular cadence, with different deadlines for initial disclosure and ongoing reporting. Missing deadlines can affect STS status and trigger supervisory scrutiny.

Initial Reporting

Ongoing Reporting

EU, UK & US Reporting Compared

Issuers with cross-border programmes must navigate EU, UK, and US disclosure regimes. While all three aim to provide investors with loan-level data, the approaches differ significantly.

Key Differences

Practical Implications

Building Reporting Capability

ESMA securitisation reporting is a significant operational commitment. Teams that treat it as a compliance checkbox will struggle with each submission. Those that build robust data architecture and automated processes create sustainable advantage.

For related context on securitisation structures, see our Securitisation Fundamentals guide. For understanding the waterfall mechanics that investor reports must explain, explore our Waterfall Structures deep dive.