Anchoring is what keeps the IFRS-with-extensions taxonomy from becoming a thousand parallel taxonomies. ESMA's design choice was elegant: every primary-statement extension carries a definition-linkbase relationship pointing back to the closest base concept that still describes it fairly. A consumer who only understands IFRS can still follow the report, because each unfamiliar concept comes with a translation arc. The mechanism is the wider-narrower arcrole at http://www.esma.europa.eu/xbrl/esef/arcrole/wider-narrower.
There are two rules to remember and one trap. Rule one, Reporting Manual 1.4.1: every extension used in a primary statement must anchor to its closest wider IFRS or ESEF base concept. The arc runs from the wider concept to the narrower extension. Rule two, RTS Annex IV section 9(b): when an extension combines two or more base concepts, the filer must additionally anchor narrower to each component. So an extension Salary plus EmployeeBenefits plus TerminationBenefits cannot just point to ifrs-full:EmployeeBenefitsExpense and call it done; it must point to each of the three component base concepts as well. The trap is anchoring to an abstract concept. Abstracts are placeholders for presentation hierarchy, not real reporting lines. Arelle catches this with its own dedicated code, ESEF.3.3.1.ExtensionConceptAnchoredToAbstractConcept, and post-filing NCA reviews flag it consistently.
Two refinements come up almost every review. First, anchoring lives in the definition linkbase, not the presentation linkbase. Reviewers who look for it in presentation will not find it. Second, anchoring is exempt for extensions used only in narrative notes and accounting policies; the obligation only attaches to extensions that surface in the four primary statements.
Pure subtotals get their own treatment under paragraph 10 of Reporting Manual 1.4.1. They are aggregations of base concepts and do not need a wider anchor, but they must still appear in the calculation linkbase so that the arithmetic remains verifiable. Skip the calc participation and the report-package validator will tell you about it before any human reviewer does.
ESEF Reporting Manual 1.4.1 requires every primary-statement extension to be anchored to its closest WIDER concept in the ESEF or IFRS taxonomy via the wider-narrower arc.
RTS Annex IV section 9(b) adds: when an extension combines two or more base concepts, anchor to EACH narrower base concept as well.
Pure subtotals (extensions that aggregate base concepts only) are exempt from wider anchoring (Reporting Manual paragraph 10). They must still appear in the calc linkbase.
Never anchor to an abstract concept. ESEF.3.3.1.ExtensionConceptAnchoredToAbstractConcept is the dedicated code.
Anchoring lives in the definition linkbase. The arcrole is the wider-narrower URI: http://www.esma.europa.eu/xbrl/esef/arcrole/wider-narrower.
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.