ESRS 2.0: Should You Early-Adopt for FY2026?

For two years, CSRD preparers have built data pipelines, mapped value chains, and wrestled with more than a thousand ESRS datapoints. That groundwork is about to shift. The European Commission is expected to adopt a simplified set of European Sustainability Reporting Standards — informally “ESRS 2.0” — by delegated act in late June or early July 2026, following a public consultation that closed on 3 June. EFRAG’s advice cuts mandatory datapoints by roughly 61% and removes voluntary datapoints altogether.

Crucially, the revised standards allow voluntary early adoption from financial year 2026, becoming mandatory only for financial years beginning on or after 1 January 2027. That leaves teams with a genuine decision to make now: keep building to the old standard, or pivot to the lighter regime a year early? This guide walks through what is changing and how to weigh the choice with clarity rather than guesswork.

What ESRS 2.0 actually changes

The revision is a simplification exercise, not a rewrite of the directive. Three changes matter most for reporting teams:

• A ~61% cut in mandatory datapoints, with all voluntary datapoints removed. The aim is to concentrate disclosure on what is decision-useful and drop the long tail of marginal metrics.
• A “top-down” approach to materiality. Rather than testing each datapoint from the bottom up, teams start from the sustainability matters that are material to the business and work down to the disclosures that follow — reducing the assessment burden that has dominated first-cycle projects.
• Fair presentation applied to the statement as a whole, rather than to each individual datapoint. This is a meaningful audit and governance shift: the question becomes whether the report as a whole gives a true and fair view, not whether every line item is independently perfect.

The companion Voluntary SME standard (VSME) is on the same adoption track. It underpins the “value-chain cap,” which limits what CSRD reporters can demand from counterparties with 1,000 or fewer employees — directly relevant if your Scope 3 and supply-chain data depend on smaller suppliers.

The timeline you are actually working against

Two dates frame the decision. After the Commission adopts the delegated act, a scrutiny period of up to four months by the European Parliament and Council must conclude before the standards are published in the Official Journal. So while the substance is effectively settled, formal finality arrives later in 2026. Early adoption applies from FY2026; mandatory application begins for financial years starting on or after 1 January 2027.

This sits on top of the February 2026 Omnibus changes, which narrowed mandatory scope to companies with more than 1,000 employees and more than €450m turnover. Many mid-caps that were preparing to report are now outside mandatory scope entirely — yet still face value-chain data requests from larger customers. If that is you, the early-adoption question is less “must we?” and more “what is the most efficient basis to respond on?” For the fuller picture, see our CSRD timeline for 2025–2028.

The case for early-adopting ESRS 2.0 for FY2026

• You report on the lighter regime sooner. If your first mandatory report is FY2027 anyway, early adoption lets your FY2026 disclosure — voluntary or value-chain-driven — use the reduced datapoint set rather than the legacy one.
• You avoid building data flows you are about to retire. Continuing to engineer collection for datapoints that the revision deletes is sunk cost. Pausing those builds now protects budget and analyst time.
• Top-down materiality is cheaper to run. Re-scoping your materiality assessment around the new model can shrink the single most expensive part of a first cycle.
• You signal maturity. A clean, focused report aligned to the final standards reads better to investors and assurance providers than an over-stuffed one built to a superseded draft.

The case for waiting

• The act is not yet final. Until the scrutiny period concludes and the text is published in the Official Journal, detail can still move. Building to a near-final draft carries some rework risk.
• Mid-cycle re-scoping has its own cost. If you are deep into an old-ESRS data build with assurance lined up, switching frameworks mid-stream can create more disruption than it saves.
• Comparability gaps. Reporting on a different basis from peers for one year can complicate year-on-year and benchmark comparisons until everyone converges in FY2027.
• Internal readiness. Top-down materiality is conceptually simpler but demands confident judgement about what is material. Teams that built bottom-up muscle memory may need time to adjust.

How to decide: a practical filter

Work through four questions in order:

1. When is your first mandatory report? If FY2027, early adoption mainly affects voluntary or value-chain disclosure in FY2026 — lower stakes, easier to trial. If you are still in mandatory scope for FY2026, the calculus is sharper.
2. How far is your data build? Early-stage projects can pivot to the reduced set cheaply. Near-complete builds with assurance booked may be better finished as planned.
3. How exposed are you to value-chain requests? If larger customers are asking for data, aligning early to the final standards — and the VSME value-chain cap — can simplify what you owe them.
4. Can your assurance provider support it? Confirm they are comfortable giving assurance on an early-adopted basis before you commit. The new statement-level fair-presentation model is worth discussing with them directly.

Whichever way you lean, the foundational work does not change: a defensible double materiality assessment still anchors the report, and your underlying data still needs to be traceable and audit-ready. For a fuller walkthrough of the standards themselves, see our complete ESRS reporting guide.

The bottom line

ESRS 2.0 is the most consequential operational change for CSRD preparers since the directive itself. For most teams whose first mandatory report is FY2027 — and especially those early in their data build or responding to value-chain requests — early adoption is the more efficient path, provided your assurance provider is on board. Teams deep into a near-complete old-ESRS cycle have a stronger case to finish as planned and converge in FY2027. Either way, decide deliberately now rather than drifting into the deadline.

Horizon ESG helps reporting teams navigate ESG complexity with clarity — including scoping and collecting against the right datapoint set the first time. If you are weighing your ESRS 2.0 options, see how our CSRD reporting software keeps your data audit-ready whichever basis you report on.