XBRL & ESEF
Anchoring
Also known as: Wider anchoring · Narrower anchoring
Linking a company-specific extension element back to the closest element in the base taxonomy, by accounting meaning, so the extension stays interpretable.
What it means
Anchoring links a preparer-created extension element to the most closely related element(s) in the base ESEF/IFRS taxonomy, using “wider” and “narrower” accounting-meaning relationships. It is what lets a reader place a company-specific concept inside the standard taxonomy and compare it across filers. ESMA's ESEF Reporting Manual gives anchoring dedicated guidance.
Wider vs narrower anchoring
| Wider anchoring | Narrower anchoring | |
|---|---|---|
| When | Always, for every extension element. | Only when the line item combines two or more base concepts. |
| Links to | The closest base element that fully encompasses the extension's meaning. | The closest base element(s) narrower than the extension. |
| Purpose | Place the custom concept within the standard taxonomy. | Show what the combined figure is built from. |
How it relates to nearby concepts
Anchoring is the safety net for extensions created during tagging. Without it, an extension element would be an island that comparison tools could not interpret.
Common misunderstandings
- Anchoring just means linking to any similar concept: It means the closest wider (and, when combining concepts, closest narrower) element by accounting meaning and scope.
Statera carries anchoring through ESEF preparation and validation. See the framework:
ESEF Digital Filing →Sources
Last reviewed: 19 June 2026
See how Statera handles this in practice
Statera carries structure, controls and filing evidence through every reporting cycle. Request a demo to see it end to end.
Request a demo