Open a report package filed under the European Single Electronic Format (ESEF), look at the `schemaRef`, and you will find two URLs in the import chain. One points to the IFRS Accounting Taxonomy, the vocabulary the IFRS Foundation issues for the International Financial Reporting Standards (IFRS). The other points to the ESEF taxonomy, the layer the European Securities and Markets Authority (ESMA) builds on top of it. They relate the way a base coat and a top coat relate: the IFRS taxonomy supplies the IFRS concept set, and ESEF adds European Union (EU) specific dimensions, entry points, and label translations into all 24 EU official languages.
The legal instrument behind that package is Commission Delegated Regulation (EU) 2019/815, adopted under the Transparency Directive and known in practice as the ESEF Regulatory Technical Standard, the "ESEF RTS." It requires the entire annual financial report (AFR) of issuers whose securities are admitted to trading on an EU regulated market to be filed as Extensible HyperText Markup Language (XHTML), with the consolidated IFRS statements additionally marked up in Inline XBRL (iXBRL, where XBRL is the eXtensible Business Reporting Language). The RTS is amended yearly to swap in the current taxonomy annexes, which is the detail that trips up filers who assume last year's package still applies.
Version pinning is where that yearly amendment bites. The IFRS Foundation's 2025 edition of the IFRS Accounting Taxonomy, issued 27 March 2025, reflects IFRS 18, IFRS 19, and amendments through 1 January 2025. Delegated Regulation (EU) 2025/19 carries the 2024 IFRS taxonomy and applies to financial years beginning on or after 1 January 2025; Delegated Regulation (EU) 2026/283 carries the 2025 taxonomy edition and applies mandatorily to financial years beginning on or after 1 January 2026. The rule to hold onto is: pin the taxonomy version to the reporting period, never to today's date. A filer who reaches for whatever ESMA published this month, instead of whatever applied when the financial year started, produces a package whose schema imports resolve fine and whose disclosure-system checks still fail.
The entry point decides what actually lands in the report's Discoverable Taxonomy Set (DTS), the complete graph of schemas and linkbases a validator pulls in. The report's `schemaRef` points at the issuer's own extension entry-point schema; that extension imports `esef_cor.xsd`, the ESEF core schema, which in turn discovers the IFRS Accounting Taxonomy version applicable to the period transitively. Entity-specific extension concepts live in that small extension taxonomy packaged beside the report, and RTS Annex IV, points 9 to 11, requires each of those extensions to be anchored, linked in the definition linkbase, to the closest wider concrete IFRS concept, and to each narrower component when the extension aggregates several. Same-statement subtotals are exempt from that wider-anchoring duty, though they still have to appear correctly in the calculation linkbase.
The filing rules sit in the ESEF Reporting Manual (ESMA32-60-254, updated annually), the preparer's rulebook, and surface as `ESEF.*` validator codes when something is wrong. Filing itself runs through each home member state's designated arrangements, national portals and Officially Appointed Mechanisms, with national enforcers such as the Dutch Autoriteit Financiële Markten (AFM) and Germany's Federal Financial Supervisory Authority (BaFin) handling supervision. Block-tagging targets, whole notes wrapped as a single non-numeric fact, are listed in RTS Annex II Table 2; detailed-tagging targets, individual facts, sit in Annex II Table 1. One provision worth remembering because it looks like an exception but is not: Reporting Manual section 1.2.2 permits replicating an IFRS concept as an extension when that concept exists in the current-year IFRS taxonomy but has not yet been incorporated into the ESEF taxonomy actually in force for the filing.
For a reviewer, the practical sequence follows the same three lenses in order. Confirm the DTS resolves to the ESEF and IFRS taxonomy versions that match the financial year, not the filing date. Confirm every extension concept is anchored per Annex IV, with subtotals correctly exempted rather than merely omitted. And confirm the block-tagged notes and detail-tagged facts line up with Annex II's two tables. Get the version and the anchoring right, and most of what `ESEF.*` complains about tends to disappear before you ever open the validator log.
The legal instrument: the European Single Electronic Format (ESEF) is mandated by Commission Delegated Regulation (EU) 2019/815, the 'ESEF RTS' (Regulatory Technical Standard), under the Transparency Directive. It requires the annual financial report (AFR) of issuers whose securities are admitted to trading on a European Union (EU) regulated market to be Extensible HyperText Markup Language (XHTML), with consolidated International Financial Reporting Standards (IFRS) statements marked up in Inline XBRL (iXBRL, where XBRL is the eXtensible Business Reporting Language). The RTS is amended yearly to swap in new taxonomy annexes: Delegated Regulation (EU) 2025/19 carries the 2024 taxonomy for financial years from 1 January 2025, and Delegated Regulation (EU) 2026/283 carries the 2025 taxonomy, mandatory for financial years from 1 January 2026.
The IFRS Foundation publishes the IFRS Accounting Taxonomy. The 2025 edition (27 March 2025) reflects IFRS 18, IFRS 19, and amendments through 1 January 2025.
The European Securities and Markets Authority (ESMA) publishes the ESEF taxonomy, which extends the IFRS taxonomy with EU-specific dimensions, entry points, and labels in all 24 EU official languages.
ESEF 2024 and ESEF 2025 differ; the 2025 taxonomy applies to AFRs covering financial years starting on or after 1 January 2026. Pin the taxonomy version to the reporting period, never to today's date.
The entry point decides the Discoverable Taxonomy Set (DTS): the report's schemaRef references the issuer's own extension entry-point schema; that extension imports esef_cor.xsd (the ESEF core entry point), which in turn discovers the relevant IFRS Accounting Taxonomy transitively. Extension concepts are anchored to base concepts in the definition linkbase (RTS Annex IV).
The filing rules: the ESEF Reporting Manual (ESMA32-60-254, updated annually) is the preparer rulebook from the European Securities and Markets Authority (ESMA); validators speak the ESEF.* code family; filing runs through each home member state's designated arrangements (national portals and Officially Appointed Mechanisms), with national enforcers handling supervision.
Block-tagging targets are listed in ESEF RTS Annex II Table 2; detailed-tagging targets are in Annex II Table 1.
XBRL world Knowledge-graph / ontology world
--------------------------------------------------------------------------
concept (ifrs-full:Revenue) a class / type (part of the ontology)
the concept's QName an IRI: a globally unique identifier
the taxonomy (schema + linkbases) the ontology / TBox: the types + rules
periodType, balance, item type axioms constraining that type
presentation / calc / def arcs labeled, directed edges (predicates)
arcrole URI (parent-child, ...) the relationship type on the edge
dimension (an Axis) a property an entity can be sliced by
member (a domain value) an individual / allowed value
a reported fact (concept+context) an assertion / triple (the ABox)
the whole instance over its DTS a knowledge graph about one filer3 questions. Druk op 1 tot 4 om te kiezen, Enter om te bevestigen.
Door deze quiz af te ronden, markeer je deze sectie als voltooid.
Tip: kies met 1 tot en met 4 en bevestig met Enter.