is a reporting obligation built around the management report and sustainability statement. The compliance file should first show why the undertaking remains in the current scope after Directive (EU) 2026/470, which applies the amended main threshold from financial years beginning in 2027, then document ESRS disclosures, double materiality, value-chain judgments, evidence, assurance, and electronic reporting.
1
Section 1
Start with CSRD scope and reporting perimeter
The original CSRD expanded sustainability reporting beyond the earlier non-financial reporting population. Directive (EU) 2026/470 later narrowed the main Articles 19a and 29a scope from financial years beginning in 2027 to undertakings or parent groups exceeding EUR 450 million net turnover and 1,000 average employees. For financial years beginning in 2025 or 2026, check whether the Member State used the optional exemption for an undertaking below either new threshold. Preserve earlier category and wave evidence, but use the amended thresholds, exemptions, sector or issuer rules, and national law for the current conclusion.
The reporting perimeter cannot be copied from a policy template. 1 says the sustainability statement is for the same reporting undertaking as the financial statements, and then extends the information to material impacts, risks, and opportunities (IROs) connected through direct and indirect business relationships in the upstream and downstream .
Record the reporting undertaking, group boundary, consolidation basis, and any parent-reporting exemption relied on.
Separate CSRD legal scope from voluntary sustainability reporting, supplier questionnaires, and internal due-diligence program design.
Check whether Article 8 Taxonomy disclosures are also required because CSRD brings the undertaking within Articles 19a or 29a of the Accounting Directive.
Keep the scope memo linked to the management report owner, financial reporting calendar, and national transposition requirements.
Build the ESRS sustainability statement around double materiality
compliance begins with double materiality, not with a fixed list of sustainability topics. The undertaking must identify impacts, risks, and opportunities, assess impact materiality and financial materiality, and then disclose the ESRS information that is material or otherwise required irrespective of the materiality outcome.
Control the standards edition as part of the compliance file. The Commission adopted revised on 3 July 2026, but they remain subject to Parliament and Council scrutiny and do not apply until that process ends. A report still governed by Delegated Regulation (EU) 2023/2772 should not silently use requirements, reliefs, or datapoint references from the pending revised text.
A defensible assessment should preserve the criteria used, the stakeholder and source inputs considered, the thresholds applied, and the link from each material impact, risk, or opportunity to the relevant disclosure requirements. Climate change needs particular care because ESRS requires a detailed explanation if the undertaking concludes that climate change is not material and omits all ESRS E1 disclosures.
Maintain an IRO register with impact, risk, opportunity, value-chain location, affected stakeholder, financial effect, time horizon, and disclosure mapping.
Distinguish mandatory 2 general disclosures from topical disclosures that depend on the materiality assessment.
When policies, actions, or targets do not exist for a material matter, disclose that fact instead of inventing a control narrative.
Use the EFRAG datapoint list as a gap-analysis and evidence-organising tool, while keeping itself as the controlling standard.
Control value-chain information and estimation limits
value-chain reporting is not a request to document every supplier or customer. The sustainability statement must include material upstream and downstream value-chain information where needed to understand material impacts, risks, and opportunities. Different matters can be material in different parts of the .
Where value-chain data is incomplete, the Accounting Directive requires the undertaking, during its first three years of being subject to sustainability reporting, to explain the efforts made to obtain the information, why it could not be obtained, and the plans to obtain it in the future. That explanation should be tied to a real data-collection log rather than a boilerplate disclaimer.
List the value-chain segments that are material for each topic, including upstream suppliers, downstream users, products, services, business relationships, and affected stakeholders where relevant.
Document which figures are measured, estimated, supplier-provided, proxy-based, or unavailable, and why the method is appropriate for the disclosure.
Retain evidence of supplier outreach, data-quality checks, estimation methodology, management review, and unresolved limitations.
Avoid treating value-chain reporting as proof of broader conduct compliance unless the page or report separately supports that claim from appropriate sources.
includes assurance over sustainability reporting. The amended audit rules require an assurance opinion on a limited-assurance basis, covering compliance with the Directive, the standards, the process used to identify reported information, Article 8 Taxonomy reporting where applicable, and the electronic markup requirement once the marking rules apply.
The evidence pack should be designed for review before the sustainability statement is drafted. Assurance will be difficult if materiality judgments, value-chain estimates, source systems, controls, and management approvals are kept in separate tools with no stable version history.
Create an assurance index that maps each material disclosure to source system, data owner, preparer, reviewer, approval date, and evidence location.
Preserve the double-materiality methodology, meeting records, thresholds, stakeholder input, IRO register, and climate non-materiality explanation if used.
For each quantitative datapoint, retain calculation logic, data lineage, estimation basis, reconciliation checks, and management sign-off.
Include digital-tagging readiness in the assurance timetable, then add formal markup testing when the ESEF marking rules apply.
Connect CSRD scope, ESRS materiality judgments, value-chain data, assurance evidence, and tagging controls before the sustainability statement is drafted.
CSRD links the management report to the ESEF electronic format and future sustainability markup, including Article 8 Taxonomy disclosures. Directive (EU) 2026/470 now states expressly that undertakings are not required to mark up sustainability reporting until the marking rules are adopted through Delegated Regulation (EU) 2019/815.
EFRAG's Set 1 XBRL taxonomy material is a readiness resource, not the final tagging rule. Preparers can structure the human-readable statement around separable datapoints, preserve fact-level evidence, and test mappings, but should not describe that work as a required or completed statutory sustainability-tagging filing.
Assign owners for human-readable disclosure drafting, XBRL taxonomy mapping, extension decisions, validation errors, and final filing evidence.
Align the datapoint inventory with the sustainability statement outline before drafting long narrative sections.
Keep each tagged fact traceable to the reported sentence, table cell, source datapoint, reporting period, unit, and review evidence.
Use ESMA ESEF guidance for technical controls such as Inline XBRL consistency, extension anchoring, readability of block tags, and unique identifiers for tagged facts.
A file should remain usable after the annual report is published. It should explain what changed since the prior report, which materiality judgments or value-chain estimates are likely to be challenged, which data controls failed or required manual adjustment, and which disclosures need earlier collection in the next cycle.
Do not include EU-wide penalty amounts or enforcement guarantees unless the source material for the relevant Member State supports them. is implemented through national law and assurance, publication, and filing controls; unsupported penalty figures or generic statements can make the page less accurate.
Retain a final sustainability statement copy, assurance report, management approvals, ESEF validation output, XBRL mapping file, and filing receipt where available.
Track post-filing changes as correction, restatement, methodology improvement, source-system change, or future-period action.
Review whether new EU acts, national transposition measures, EFRAG guidance, ESMA technical materials, or company structure changes affect the next reporting cycle.
Use the published report as the baseline for next-year data ownership, not as a one-time communications document.
Before each reporting year, rerun the scope test, confirm the applicable edition and phase-ins, reopen changed IRO and value-chain judgments, and assign owners for new or restated datapoints.
Supports the ESRS rule that value-chain information is included for material upstream and downstream impacts, risks, and opportunities, not for every actor automatically.
"does not require information on each and every actor in the value chain"
Supports the current rule for explaining unavailable value-chain information, efforts made to obtain it, reasons it could not be obtained, and future plans.
"For the first three years of being subject to sustainability reporting requirements"
Current Article 29d source stating that sustainability markup is not required until the marking rules are adopted through the ESEF Delegated Regulation.
"undertakings shall not be required to mark up their sustainability reporting"
Supports the practical ESEF control focus for Inline XBRL preparation, including extension anchoring, block-tag readability, and unique identifiers for tagged facts.
"supporting a harmonised approach for the preparation of annual financial reports"