ESAP Phase 1 Launches July 10: What It Means for FIDA Infrastructure Teams

On July 10, 2026, the European Single Access Point (ESAP) launches its Phase 1 — the EU’s new centralised platform for financial and sustainability data. For most observers, ESAP is primarily a transparency tool. For FIDA compliance infrastructure teams, it is something more: the first operational proof that the EU can build shared financial data access infrastructure at scale.

This article explains what ESAP is, how it connects to FIDA, and what financial institutions building FIDA infrastructure should take from Phase 1 of ESAP going live.

What Is ESAP?

ESAP is the EU’s centralised repository for public financial and sustainability data. It will allow investors, regulators, civil society, and the public to access standardised financial disclosures from companies across the EU in one place.

Phase 1 (July 10, 2026) begins data collection from Collection Bodies — supervisory authorities and other designated bodies — that will feed structured financial data into the central ESAP platform. The platform is built on the principle of machine-readability and structured data formats, not PDFs.

Why ESAP Matters for FIDA Infrastructure

At first glance, ESAP and FIDA look like separate regulatory projects. ESAP governs public disclosure of financial data. FIDA governs private access to personal financial data. But the infrastructure logic is the same: standardised formats, API-based delivery, machine-readable outputs, and a regulatory expectation that financial data should be accessible, not siloed.

Here is where the connection becomes concrete. Financial Data Sharing Schemes (FDSS) under FIDA will need to define data formats and API standards. ESAP uses XBRL and other structured formats. Institutions building FDSS-compliant infrastructure now will be working on very similar technical problems to those building ESAP-compliant reporting pipelines.

Both ESAP and FIDA are also driving towards standardised data formats. ESAP uses XBRL-based structured formats for financial disclosures. FIDA will require standardised APIs and data schemas across financial product categories. Institutions that invest in structured data infrastructure for ESAP are building capability that will transfer directly to FIDA.

The Infrastructure Implications for Data Holders

Banks, investment firms, and insurance companies subject to FIDA must build FDSS-compliant data infrastructure. Many of these same institutions are also subject to ESAP reporting requirements as public-interest entities. The infrastructure overlap is real.

On API infrastructure: FIDA requires customer-data APIs; ESAP requires machine-readable public disclosures. Different data, same architectural pattern: structured, accessible, standardised.

On data quality: both ESAP and FIDA penalise poor data quality. ESAP requires accurate, timely, structured disclosures. FIDA requires accurate, standardised customer data. Institutions that build data quality governance for one will find it transfers to the other.

On vendor selection: when assessing technology vendors for FIDA API infrastructure, data holders should also confirm whether those vendors are building for ESAP compatibility. The intersection is not coincidental — it is architectural.

FIDA infrastructure operators also need to account for the EU's Corporate Data Act on Cloud Infrastructure (CADA), adopted by the Commission on June 3, 2026. CADA introduces binding cloud sovereignty requirements — covering data residency, portability, and provider switching — that apply directly to FDSS and FISP providers. Where ESAP shapes the data-sharing architecture, CADA constrains the infrastructure layer on which that architecture runs. Operators building for FIDA compliance cannot treat these as separate workstreams.

Four Things to Do Before July 10

Map your ESAP obligations. Determine whether your organisation qualifies as a Collection Body, a Reporting Entity under ESAP Phase 1, or both. If you are subject to ESAP, begin assessing your data quality and format readiness now.

Audit your data architecture. Assess whether your current data systems can produce the structured, machine-readable outputs that both ESAP and FIDA will require. Identify gaps in data quality governance, format standardisation, and API readiness.

Monitor FDSS disclosure requirements. As FIDA trilogue progresses and FDSS operators begin forming schemes, watch for alignment between ESAP-style structured data requirements and emerging FDSS technical standards.

Use ESAP compliance as a readiness test. Organisations that can meet ESAP disclosure requirements on time and at quality are demonstrating exactly the kind of data infrastructure maturity that FIDA will demand. Treat ESAP as a live rehearsal.

ESAP launches July 10. FIDA is still in trilogue. But the infrastructure decisions you make now — on data architecture, vendor selection, and compliance programme design — will determine how ready your organisation is when FIDA’s obligations begin to bite.