Line4 logoLine4

Search line4.ai

What is ESEF (European Single Electronic Format)?

ESEF is the single electronic format in which issuers with securities on EU regulated markets prepare their annual financial reports. The report is an XHTML document; where it contains IFRS consolidated financial statements, those are tagged with ESMA’s ESEF taxonomy in Inline XBRL. ESMA writes the rules, the taxonomy and the Reporting Manual. Issuers file with their national authority or its officially appointed mechanism, not with ESMA. Outside Europe, the US SEC adopted its Inline XBRL mandate in 2018, and domestic filers now file their 10-K and 10-Q financial statements in the same format.

Guide · 6 min read · Updated 21 November 2026 · By Jess Luper

What ESEF requires

The Transparency Directive requires issuers to publish an annual financial report. Commission Delegated Regulation (EU) 2019/815, the RTS on ESEF, says that report must be prepared in XHTML, so anyone can open it in a browser. Where it contains IFRS consolidated financial statements, those must also be marked up with Inline XBRL.

Not everything is tagged the same way. ESMA sets out two levels.

01Detailed tags on the primary statementsEvery number in the statement of financial position, profit or loss and other comprehensive income, changes in equity and cash flows carries its own tag (ESMA).
02Block tags on the notesSince 1 January 2022, the notes and accounting policies are tagged as larger blocks of text against the elements listed in Annex II of the RTS (ESMA).
03Annex II elements, only if presentIssuers tag the Annex II disclosures their statements contain, and must not add a disclosure just to tag it (Reporting Manual, guidance 1.3.3).
68rules in ESMA’s 2025 ESEF conformance suite: 54 MUST, 14 SHOULD, checked by 215 test packagesESMA, ESEF Conformance Suite 2025 (Line4 count) →
4primary statements tagged in detail; the notes are block tagged since 1 January 2022ESMA →
~23enforcers from EEA countries in ESMA’s ESEF Project Team, which coordinates supervision of the rulesESMA →

An example: anchoring an extension

When an issuer reports a line the ESEF taxonomy has no element for, it creates an extension element. For the primary statements, the RTS says each extension must be anchored to the ESEF taxonomy, so a supervisor’s system still knows roughly what it is. This is ESMA’s own example.

One line from a balance sheet
What the issuer reports
Issued capital and share premium, as one line
What the ESEF taxonomy has
Two separate elements: issued capital, and share premium
What the issuer does
Creates an extension element for the combined line
How it is anchored
To both taxonomy elements, showing the extension is wider than each of them
What a supervisor’s system learns from it

The combined figure can still be compared with peers that report issued capital and share premium separately. The opposite case, a line narrower than a taxonomy element (capital increases in cash, in kind), is anchored to the wider element, here issue of equity (guidance 1.4.1).

The rule, from the Reporting Manual (guidance 1.4.2)ShowWhere an extension taxonomy element combines a number of elements of the ESEF taxonomy, issuers shall anchor that extension taxonomy element to each of the elements in the ESEF taxonomy it combines.

Source: ESMA, ESEF Reporting Manual (14 October 2025). The RTS sets no anchoring requirement for the notes.

How the file travels

ESMA recommends that issuers prepare ESEF submissions as Report Package 1.0 (guidance 2.6.1) and encourages the file name {base}-{date}-{version}-{lang}.xbri, where base is the LEI or a short issuer name of up to 20 characters (guidance 2.6.3). A national authority’s or mechanism’s own naming rules come first, and .zip is still accepted.

Where the law requires the report in two or more languages, each language version is a separate XHTML report in a separate report package, tagged in exactly the same way with the same extension elements (guidance 1.1.2). The ESEF taxonomy package carries labels in all EU languages (ESMA).

An extension that is not anchored is a number nobody can compare.

Who checks ESEF filings

Issuers file their ESEF report with the national competent authority of their home member state, or the officially appointed mechanism it designates for storing regulated information. In Norway, for example, the report goes to Oslo Børs’ NewsWeb, and posting a link to another website is not enough (Finanstilsynet). Romania’s ASF names the same EU regulation for issuers’ annual reports.

ESMA does not collect the files. It writes the RTS, publishes the taxonomy each year (the 2025 taxonomy on 21 April 2026) and the Reporting Manual, and its ESEF Project Team of about 23 enforcers coordinates how national authorities supervise the rules.

What it means for supervisors

An ESEF filing is both a document and a dataset. The checks worth running on arrival are the technical ones: is it a valid report package, does the XHTML pass, is every number in the primary statements tagged, is every extension there anchored. ESMA’s conformance suite gives 68 rules to start from, each marked MUST or SHOULD.

The harder questions are about meaning. Does an extension duplicate a core element, which ESMA says issuers should not do because it hurts comparability? Is it anchored to an element of the same data type? Those need a person who reads accounts, helped by a system that points to where to look.

Where AI fits, and where people decide

AI can read the block-tagged notes next to the detailed numbers and point out where they disagree, suggest a closer core element for an extension, and explain a failed check to the issuer in plain words.

Whether a file conforms is still a fixed check against the RTS and the conformance suite, and whether a tag is wrong is still an enforcer’s judgement. AI shortens the queue. It does not decide the case.

Put it to workBefore the next ESEF season
  1. 1Run ESMA’s conformance rules on arrival, and send failures back in plain words.
  2. 2Count extensions per filer, and how many are anchored to a same-type element.
  3. 3Check language versions use the same extension elements.
  4. 4Publish your naming rule, or point issuers to ESMA’s .xbri pattern.
  5. 5Plan how analysts will use the tagged numbers, not just store the file.

Where Line4 fits

Line4 is SupTech software for financial regulators. It collects returns in XBRL, Excel and CSV by portal, API or MCP, validates them against your taxonomies and rules at the point of submission (see XBRL software for regulators), and puts AI to work reading them, with supervisors making every decision. If you work with a standard we have not yet run in production, we will say so plainly and show you how we would approach it.

In the returns library

One page per return: who files it, how often and by when, the format and the validation rules, with links to the official documents.

Browse every return in the library.

Questions

What is ESEF?

The European Single Electronic Format: the format, set by Commission Delegated Regulation (EU) 2019/815, in which issuers with securities on EU regulated markets prepare their annual financial reports. The report is XHTML, and IFRS consolidated financial statements in it are tagged with the ESEF taxonomy in Inline XBRL.

Is ESEF the same as Inline XBRL?

No. Inline XBRL is the XBRL International standard for putting tags inside a readable document. ESEF is the EU rule that uses it, together with ESMA’s ESEF taxonomy, for listed issuers’ annual financial reports.

What has to be tagged under ESEF?

Every number in the four primary statements (financial position, profit or loss and OCI, changes in equity, cash flows) is tagged in detail. Since 1 January 2022 the notes and accounting policies are block tagged against the elements listed in Annex II of the RTS, where those disclosures are present.

What is anchoring in ESEF?

When an issuer creates an extension element for a line in the primary statements, it must link it to the ESEF taxonomy: to a wider element if the extension is a breakdown, and to each element it combines if it is a combination. ESMA also says extensions should be anchored to elements of the same data type. There is no anchoring requirement for the notes.

Who do issuers file ESEF reports with?

With the national competent authority of their home member state, or the officially appointed mechanism it designates, not with ESMA. ESMA writes the rules, taxonomy and Reporting Manual, and coordinates supervision through its ESEF Project Team.

How should an ESEF file be named and packaged?

ESMA recommends Report Package 1.0 and the name {base}-{date}-{version}-{lang}.xbri, with the LEI or a short issuer name as base. National naming rules take precedence, and .zip is still accepted.

What if the annual report is published in two languages?

Where the law requires more than one language, each version is a separate XHTML report in its own report package, tagged in exactly the same way with the same extension elements (Reporting Manual, guidance 1.1.2).

How many ESEF validation rules are there?

ESMA’s 2025 ESEF conformance suite lists 68 rules, 54 MUST and 14 SHOULD, checked by 215 test packages. The suite is for testing software; the Reporting Manual explains common errors and how to fix them.

Is there an ESEF outside Europe?

Yes, in other forms. In the US, the SEC adopted its Inline XBRL mandate on 28 June 2018, and domestic filers now file the cover page and financial statements of their 10-K and 10-Q reports in Inline XBRL, the same format ESEF uses. South Africa’s CIPC mandated XBRL reporting for all qualifying companies from 1 July 2018. The idea is the same everywhere: one report that people can read and machines can check. Line4 validates Inline XBRL as well as XBRL-XML, so a regulator can check annual reports and supervisory returns on one platform.

Share this guideShare on LinkedIn
Was this useful?

For supervisors

New guides and Insights, by email

One short email when we publish something worth your time, from Jess Luper. No spam, unsubscribe any time.