- Supports XHTML, XBRL, Inline XBRL, extension taxonomy, and common markup-rule evidence checks for ESEF filings.
"prepare their entire annual financial reports in XHTML"
Build an evidence file that lets assurance reviewers trace each sustainability statement disclosure from ESRS requirement to source data, control, sign-off, and planned digital tag.
This page focuses on assurance readiness, ESRS datapoint inventories, and ESEF/XBRL preparation where the official and technical sources support the work.
Structured answer sets in this page tree.
Cited legal and guidance references.
CSRD evidence work should connect three layers: the sustainability statement prepared under ESRS, the assurance conclusion over that reporting, and the digital reporting layer that makes ESRS information machine-readable. Treat the evidence file as a traceability pack for reported information, not as a generic compliance memo.
The CSRD requires assurance over sustainability reporting and links that assurance to compliance with Union sustainability reporting requirements. The assurance opinion starts from limited assurance, while the CSRD describes a possible later move to reasonable assurance if the Commission adopts assurance standards after assessing feasibility.
The same evidence pack should also support digital reporting preparation. CSRD recitals require management reports to use the electronic reporting format specified in Delegated Regulation (EU) 2019/815 and to mark up sustainability reporting once the format is determined. ESMA's current sustainability-markup material is still a consultation/draft source, so teams should treat detailed tagging levels as readiness work unless final rules apply to their filing.
Use this evidence checklist to connect ESRS disclosures, source data, assurance requests, and digital-tagging workpapers before the sustainability statement is finalized.
Assurance evidence is strongest when it follows the ESRS reporting architecture. ESRS 2 general disclosures apply across CSRD-scope companies, while most topical standards and their datapoints depend on materiality. The Commission Q&A also states that materiality is not the same as voluntary reporting: information subject to materiality must be disclosed if it is material.
For datapoints linked to SFDR, Benchmark Regulation, or Capital Requirements Regulation reporting needs, the Commission Q&A says companies should state not material where applicable and provide a table identifying those datapoints and where they appear in the sustainability statement.
A useful datapoint inventory is more than a list of disclosure names. It should identify whether a datapoint is numerical, narrative, boolean, enumeration, table-based, conditional, alternative, voluntary, phased in, or linked to minimum disclosure requirements. That classification helps assurance reviewers choose evidence and helps tagging teams understand the likely digital representation.
EFRAG's IG 3 explains that the human-readable list of ESRS datapoints and the digital ESRS XBRL taxonomy are consistent, but not identical in technical implementation. The XBRL taxonomy may reuse elements and use dimensions where the human-readable datapoint list has one item per standard.
Digital tagging evidence should be built from the published sustainability statement, not separately drafted reporting text. The ESEF framework uses XHTML and Inline XBRL so one annual report can be both human-readable and machine-readable.
Before final filing, the tagging workpaper should show how report sections, narrative disclosures, numerical values, entity identifiers, extension taxonomy elements, and validation rules were reviewed. Where ESMA material is still draft or phased, record the assumption and the version of the taxonomy or consultation text used.
The assurance file should let a reviewer move from a sustainability statement assertion to the ESRS requirement, the source record, the control that produced or reviewed it, and the final tagged disclosure. Keep estimates and value-chain information especially visible because they often require judgment and explanation.
ISSA 5000 is useful as assurance-readiness context because IAASB describes it as a general sustainability-assurance standard compatible with suitable reporting frameworks. It should not be presented as the binding EU assurance rule on this page unless a specific engagement or jurisdiction has adopted it.
"prepare their entire annual financial reports in XHTML"
"sustainability reporting standards"
"ESRS 2 is mandatory"
"limited assurance engagement"
"support implementation"
"single report which is human- and machine-readable"
"ESRS Set 1 XBRL Taxonomy"
"European sustainability reporting standards"
"Compatible with Any Suitable Reporting Framework"