On the day an AI agent first authors a wider-narrower arc on your behalf, the temptation is to anchor at a comfortably high concept and move on. Resist it. ESMA's Reporting Manual examples consistently favour faithful narrowness, and post-filing NCA reviews from AMF and others flag inappropriate anchoring as one of the highest-frequency substantive findings. The closest wider concept is the one whose meaning fairly subsumes your extension, and finding it takes time the agent will only spend if you ask.
A practical workflow for agent-authored extensions covers four moves. First, you have the agent declare the concept with the right substitution group, item type, periodType, and balance. Get any of those wrong and the rest of the filing inherits the defect. Second, you wire the concept into the presentation linkbase under the appropriate extended link role, calculation linkbase with the right weight, and definition linkbase. Third, the agent adds the wider-narrower arc in the definition linkbase pointing at the closest concrete IFRS or ESEF base concept. Fourth, the agent supplies the Standard Label in the reporting language and an English label.
Anchoring arcs do not affect arithmetic. They are dimensional and structural information that analytical consumers use to align the filing with the base taxonomy. A consumer running peer comparisons uses the wider anchor to project your extension onto an IFRS-only schema; an industry analyst uses the narrower anchors on combination extensions to decompose the reported amount. Underplaying anchoring quality penalises your own report's analytical value.
After the agent finishes, you verify. The cheapest check is to run the validate/ESEF Arelle plugin and confirm no ESEF.3.3.1 (abstract anchor) or related codes are emitted. The next check is a manual sample: open the definition linkbase, find the wider-narrower arc, follow the locator to the wider concept's schema, and confirm the concept is concrete (abstract="false") and a fair description of the extension. If you can read the wider concept's name aloud and answer "yes, this is what we mean", the anchor is right. If you have to defend the choice, the anchor is too high or pointing in the wrong direction, and a surgical re-prompt is the next move.
An extension's wider anchor must be the closest base concept that still fairly describes the extension (RTS Annex IV; Reporting Manual 1.4.1). Anchoring too high in the hierarchy is not a style choice: it fails the closest-wider requirement and destroys analytical value, even where a validator does not mechanically catch it.
When in doubt about the wider anchor, prefer one level above. ESMA Reporting Manual examples favour faithful narrowness.
Anchoring arcs do not affect arithmetic. They are dimensional/structural information for analytical consumers.
When AI agents author extensions, ask them to (a) declare the concept with correct type, periodType, balance, (b) wire presentation, calculation, definition linkbases, (c) add anchoring arcs in the definition linkbase, (d) supply Standard Label plus English label.
After agent authoring, verify in the validator output that ESEF.3.3.1 and ESEF.3.3.2 codes are absent.
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.