Block tagging is what happens when XBRL stops trying to atomise narrative disclosures and admits that some notes are most usefully reported as the entire structured paragraph. ESEF Article 6 made block tagging mandatory from the FY2022 reporting onward for the disclosures listed in the RTS Annex II Table 2: revenue, segments, financial instruments, leases, and so on. The mechanism is one of the cleaner inventions in iXBRL. Wrap the whole note's XHTML in an ix:nonNumeric element with escape="true" and the inner XHTML becomes the fact value. Tables, headings, ordered lists, paragraph structure: all preserved.
The escape attribute is the load-bearing piece. With escape="true", parsers keep the inner markup as part of the canonical fact value so that downstream consumers see the same structure the reader saw. With escape="false" the parser collapses everything to plain text, dropping the table cells, the bullets, and the headings. ESEF Reporting Manual section 2.2.6 requires that block-tagged values remain machine-readable after extraction, which is impossible to achieve with escape="false" on anything more than a single paragraph.
Two pathologies recur in production filings. The first is the empty block tag. An ix:nonNumeric escape="true" element wrapping no content is syntactically valid and operationally meaningless. It happens when a block tag is applied to the wrong region (a heading rather than the surrounding section) or when the disclosure is missing entirely and the tag is left as a placeholder. Empty blocks pass syntax validation and trip downstream formula assertions that test whether a required disclosure exists.
The second is the broken continuation chain. ix:continuation extends a fact's value across DOM regions that are not adjacent, often because the human-facing layout splits a note across pages or columns. The fact carries continuedAt pointing at the id of an ix:continuation, which itself can carry a further continuedAt, daisy-chained until the value is complete. A broken IDREF in the middle of that chain produces a silently truncated fact value: the portion before the break is preserved, everything after is lost. Validators rarely highlight this clearly. Pre-flight scripts that walk the chain explicitly are the cheapest way to catch it before submission.
Block tagging wraps a whole note in ix:nonNumeric escape='true'. The escaped XHTML is the fact value. ESEF Article 6 requires this for Annex II Table 2 disclosures (mandatory from FY2022).
Block tags must be machine-readable after extraction (ESEF Reporting Manual 2.2.6). Preserve tables, lists, headings, ordering. A pretty rendering with mangled HTML inside is a defect.
ix:continuation chains let one fact's value span non-contiguous DOM regions. The chain follows continuedAt IDREFs from the fact through ix:continuation elements (or ix:footnote elements for footnote text).
A broken continuation chain (continuedAt pointing at an element that does not exist or that is itself broken) produces a value that is silently truncated or empty.
Empty block tags are syntactically valid and operationally useless. They often trip downstream formula assertions and indicate the block tag was applied to the wrong region.
<ix:nonNumeric name="ifrs-full:DisclosureOfRevenueExplanatory"
contextRef="c-Group-2025"
escape="true"
continuedAt="rev-cont-1">
<h3>Note 4. Revenue</h3>
<p>Revenue is recognised when control of the goods or services transfers to the customer.</p>
</ix:nonNumeric>
<!-- ... pages later ... -->
<ix:continuation id="rev-cont-1">
<p>Disaggregated revenue by geography is shown below.</p>
</ix:continuation>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.