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 compliance infrastructure should be thinking about before the July 10 launch.

What Is ESAP?

ESAP is the EU's centralised repository for public financial and sustainability information. Under Regulation (EU) 2023/2859, Collection Bodies — including national competent authorities and Officially Appointed Mechanisms (OAMs) — must submit standardised financial and sustainability data to ESAP, which then makes it publicly accessible.

Phase 1 (July 10, 2026) begins data collection from Collection Bodies — supervisory and regulatory data submissions. Phase 2 (by July 2027) opens public access, making the full dataset searchable and downloadable by any user. The regulation covers financial statements, prospectuses, fund reports, ESG disclosures, and regulated financial information — from one location, for the first time.

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 customer-permissioned access to personal financial data held by banks, insurers, and other institutions. But they share a fundamental infrastructure premise: financial data should flow more freely, and standardised access infrastructure is the mechanism to achieve this.

Here is where the connection becomes concrete. Financial Data Sharing Schemes (FDSS) operating under FIDA will be regulated entities subject to disclosure obligations. As EU financial infrastructure operators, FDSS may fall within ESAP's Collection Body definitions — meaning their governance data, financial reports, and sustainability disclosures could be subject to ESAP submission requirements. FDSS operators building compliance infrastructure now should assess this question early.

Both ESAP and FIDA are also driving towards standardised data formats. ESAP uses XBRL and iXBRL for financial disclosures; FIDA mandates standardised APIs and data schemas for financial data sharing. For data holders — banks, insurers, investment firms — subject to both frameworks, this means two parallel data standardisation programmes. Organisations that design their data architecture to serve both standards simultaneously will have a significant cost advantage.

The Infrastructure Implications for Data Holders

Banks, investment firms, and insurance companies subject to FIDA must build FDSS-compliant APIs to expose customer financial data. They are also subject to ESAP disclosure requirements for their own regulatory and financial reporting. This creates a practical convergence point for CIOs and CTOs.

On API infrastructure: FIDA requires customer-data APIs; ESAP requires machine-readable submission of regulatory data. Both demand standardised, structured data outputs. Designing these as shared infrastructure — not separate systems — is the efficient approach.

On data quality: both ESAP and FIDA penalise poor data quality. ESAP requires accurate, timely regulatory submissions. FIDA requires accurate, real-time customer data. A shared data governance framework serves both obligations simultaneously.

On vendor selection: when assessing technology vendors for FIDA API infrastructure, data holders should also confirm whether those vendors are aligned with ESAP data format requirements. A vendor that supports FIDA APIs but not ESAP submission formats creates a future integration problem.

Four Things to Do Before July 10

Map your ESAP obligations. Determine whether your organisation qualifies as a Collection Body under ESAP, or whether you have reporting obligations as a regulated financial entity. If yes, identify which data your supervisory authority will require you to submit from July 10.

Audit your data architecture. Assess whether your current data systems can produce both ESAP-compliant regulatory submissions and FIDA-compliant customer data APIs from the same underlying data layer. If not, this gap is worth addressing now — not after FIDA enters into force.

Monitor FDSS disclosure requirements. As FIDA trilogue progresses and FDSS operational standards are developed, watch for any ESAP disclosure requirements that apply to FDSS operators specifically. This is an emerging area where regulatory guidance remains limited.

Use ESAP compliance as a readiness test. Organisations that can meet ESAP disclosure standards — producing machine-readable, standardised financial data on a defined schedule — have demonstrated the underlying data infrastructure that FIDA will also require. If you cannot yet do this, ESAP is an early warning of a FIDA readiness gap.

ESAP launches July 10. FIDA is still in trilogue. But the infrastructure decisions that determine FIDA readiness are being made today. InfraFIDA is tracking both regulatory developments and helping Data Holders and FISPs across the EU prepare. Questions about your ESAP and FIDA infrastructure roadmap? Contact us at info@infrafida.com.