ESAP starts collecting, and your disclosures acquire an index

Nobody should tell a board that ESAP is live. What begins in July 2026 is collection: collection bodies feed entity information, metadata and documents into the central repository so that the platform can be built against real data. Public access is required by 10 July 2027. Between those two dates the material exists centrally without being searchable by the public, which is precisely the window in which a mistake can be corrected quietly.

The route matters as much as the date. An issuer does not acquire a new filing obligation to ESMA. It keeps filing where it files today, and its national mechanism or competent authority forwards the result. The change is in the filing itself: it has to travel. It must carry the metadata the regulation prescribes, including the entity's name and its legal entity identifier, and it must be in a format from which data can be extracted.

A fund platform or a holding group has an issuing entity, a guarantor, a parent, a management company and a series of sub-funds, each with a registered name, a national registration number, a national tax identifier and, in most cases, its own legal entity identifier. Those identifiers were adopted at different times by different teams for different regulatory purposes.

Small differences survive comfortably while each filing sits on its own platform. A trailing legal-form abbreviation, a name recorded before a conversion, a guarantor filed under the parent's identifier, an identifier that has been allowed to lapse. Put those filings side by side under one index and the same entity appears more than once, or its disclosures scatter across several apparent entities. Nobody has done anything wrong. The record simply does not resolve to one company.

So start with what each entity is called and how it is numbered. For every entity that files anything under EU law, record the registered name exactly as the register holds it, the national registration number, the legal entity identifier and its status, the competent authority and mechanism the entity files through, and the person accountable for each filing. Then compare that list against what was actually submitted in the last two reporting cycles. Where they disagree, fix the source and not the spreadsheet: renew a lapsed identifier, correct the name held by the filing agent, retire the identifier that was issued twice. Every entity whose information reaches ESAP needs a current identifier, and it needs to be the identifier of the entity the filing is about. Doing this before July 2027 costs a few hours. Doing it afterwards means correcting filings that are already indexed, already searchable and already downloaded by whoever was watching.

The registered name, the national identifiers and the legal entity identifier are fields on the entity record, held once and used everywhere that entity appears. Ownership and officers hang off the same record, and compliance obligations carry due dates against the entity that owes them, so a reporting cycle is a set of dated obligations and not a recollection of what was sent last year.

Documents attach to the entity that filed them, and the audit trail shows who changed an identifier and when. Alethia submits nothing to ESAP, to a national mechanism or to a competent authority. The obligation stays where it has always been, with the issuer and the people who file in its name; what changes is that they can see, before they file, the name and the identifier the filing will carry.