An ESEF reviewer at AFM, BaFin, AMF, CONSOB, CNMV, or FSMA opens your filing. Before they read a single sentence of MD&A, the validator has already produced a verdict. ESEF codes are the verdict's vocabulary, and they are organised by where the problem lives.
Three top-level prefixes carry almost all of the traffic. `ESEF.2.x` covers iXBRL and instance-construction issues: contexts, units, transformations, hidden facts, and host XHTML. `ESEF.3.x` covers extension-taxonomy issues: anchoring, labels, link roles, and label-language requirements. `ESEF.4.x` covers filing-process rules: report-package layout, naming, and signing. Once you know which family fires, you know which chapter of the ESEF Reporting Manual (currently ESMA32-60-254, with the 2025 update layered on top) to open.
Two codes earn separate mention because they recur. `ESEF.3.3.1.ExtensionConceptAnchoredToAbstractConcept` fires when an extension is wider-anchored to an abstract IFRS concept. The fix is structural: re-anchor to the closest concrete wider concept, never to an abstract. Reporting Manual rule 1.4.1 is the canonical reference, and abstract-anchoring is one of the first things post-filing peer reviews flag. `ESEF.2.4.1.transformableElementIncludedInHiddenSection` fires when a numeric or transformable fact is parked in `ix:hidden` because the preparer wanted to suppress its visible rendering. `ix:hidden` is for cover-page facts and similar machine-required values that have no natural visible home; it is not a suppression mechanism, and ESEF prohibits using it as one.
The `ESEF.2.5.1` family rounds out the day-to-day list. ESEF expects calculation reconciliation in primary statements within rounding, which means `ESEF.2.5.1` codes intersect with `xbrl.5.2.5.2` and Calc 1.1 considerations.
The codes carry a sub-suffix on purpose. The number narrows the rule book; the suffix narrows to the specific clause. Truncating the code to "ESEF.3.3.1" loses information the agent fixing the file actually needs. The keypoints below tighten this picture.
ESEF codes have prefixes ESEF.2.x for iXBRL/instance issues, ESEF.3.x for extension-taxonomy issues (anchoring, labels, link roles), ESEF.4.x for filing-related rules.
ESEF.3.3.1.ExtensionConceptAnchoredToAbstractConcept fires when an extension is anchored to an abstract IFRS concept. Anchor to a wider concrete concept instead.
ESEF.2.4.1.transformableElementIncludedInHiddenSection fires when a numeric or transformable fact lives in ix:hidden when it could be visible. Hidden is for cover-page facts and similar, not for suppression.
ESEF.2.5.1 family covers calculation-linkbase issues; ESEF expects calc reconciliation in primary statements within rounding.
ESEF rules are defined in ESEF Reporting Manual ESMA32-60-254 (2025 update); the rule numbers in Arelle output trace back to numbered guidance items.
3 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.