- Binding amendment applying from 1 January 2026 that simplifies Article 8 templates, deletes Annex XII, and permits use of the rules in force on 31 December 2025 for financial years beginning during 2025.
"Annex XII is deleted"
A practical checklist for preparing ESRS and Article 8 disclosures for XHTML and Inline XBRL review.
Use it to structure the sustainability statement, map taxonomy elements, run ESEF-style controls, and keep unsupported final-rule claims out of the filing plan.
Structured answer sets in this page tree.
Cited legal and guidance references.
Use this checklist for readiness work, not as proof that sustainability markup is already mandatory. links the management reports of undertakings reporting under Articles 19a and 29a to the electronic format and future markup of ESRS and . Directive (EU) 2026/470 replaces Article 29d, states that undertakings need not mark up sustainability reporting until the marking rules are adopted through Delegated Regulation (EU) 2019/815, and must be transposed by Member States by 19 March 2027. EFRAG's 2024 ESRS Set 1 and Article 8 XBRL taxonomies support mapping and testing; ESMA's draft technical standards and the Commission's delegated act will establish the authoritative marking-up rules.
Start with the human-readable sustainability statement, not the tagging tool. For readiness testing, the XHTML layer should remain readable in a browser while the layer identifies machine-readable facts. Assign a report owner for XHTML rendering, a disclosure owner for each ESRS and Article 8 section, and a technical owner for iXBRL generation. These are readiness roles, not roles prescribed by .
Check that every tagged disclosure can be traced back to visible report text, a table cell, or a controlled hidden value where the XBRL mechanics require it. Avoid relying on a separate PDF, web page, or spreadsheet as the place where tagged sustainability disclosures actually live.
This checklist helps connect ESRS and Article 8 disclosure mapping, XHTML/iXBRL controls, validation evidence, and final-rule caveats before the filing workflow hardens.
Treat the as a digital model of the ESRS disclosures, not as a replacement for the ESRS reporting analysis. The mapping work should begin from the materiality assessment, ESRS 2 general disclosures, topical disclosure requirements, minimum disclosure requirements, and any entity-specific disclosures that the undertaking has concluded are needed.
The checklist should force a reviewer to see the difference between a disclosed item, a taxonomy element, and an . The same disclosure can create multiple facts when it is repeated for different periods, dimensions, policies, actions, targets, metrics, geographies, entities, or sustainability matters.
Do not blend ESRS narrative tagging and Article 8 EU Taxonomy tagging into one generic task. EFRAG describes the Article 8 XBRL taxonomy as a separate digital transposition of the Disclosures Delegated Act templates and related qualitative disclosures.
The Article 8 review should therefore look like a template-control exercise: identify the undertaking type, reporting period, applicable version of Delegated Regulation (EU) 2021/2178, relevant annexes and templates, KPI rows and columns, contextual disclosures, dimensional breakdowns, restatements or corrections, and whether values are monetary, percentage, Boolean, integer, enumeration, or text block.
Do not treat the 2024 EFRAG taxonomy as a current copy of the binding templates. Commission Delegated Regulation (EU) 2026/73 applies from 1 January 2026, simplified the Article 8 templates, and deleted the separate Annex XII nuclear and fossil gas templates. Undertakings may instead use the rules in force on 31 December 2025 for a financial year that began during 2025. Record that choice and run a gap analysis between the applicable legal templates and the available taxonomy.
Validation software can catch technical errors, but it cannot prove that the selected tag is the right disclosure concept. For readiness work, add reviewer gates before the file reaches final validation: one disclosure reviewer, one technical XBRL reviewer, and one assurance or internal-control reviewer should each have a distinct sign-off.
Use a traceable fact table. Every should show where it appears in the XHTML, what source requirement it answers, what taxonomy element and dimensions were selected, what transformation was used, and what evidence supports the disclosed amount or narrative.
Apply the Reporting Manual and conformance-suite tests as readiness controls only where they fit. They govern the established financial-reporting format and software tests; they do not settle the final sustainability taxonomy, mandatory element list, phasing, extensions, or filing rules.
Close the checklist with validation evidence, not a generic statement that the report is tagged. Save the validator output, unresolved warnings, reviewer decisions, taxonomy files used, conformance-suite result where applicable, and the version of the XHTML or package that was reviewed.
Record the limit of the current materials: EFRAG taxonomy files and illustrations support readiness work, but ESMA drafts the technical standards and the European Commission adopts the authoritative marking-up rules. As of 26 July 2026, ESMA's electronic-reporting overview still says sustainability-reporting digitalisation is under development and markup is not required until the delegated marking-up rules are adopted. Do not promise final tagging obligations, national filing mechanics, or penalty outcomes without the applicable final rule and national implementation.
"Annex XII is deleted"
"Single electronic reporting format"
"undertakings shall not be required to mark up their sustainability reporting"
"not to be considered as tagging rules"
"validation rules"
"defining marking up rules"
"ESEF Conformance Suite"
"harmonised and consistent approach"
"European sustainability reporting standards"