Level 2 · Comparison·ESRS · Disclosure guides
ESRS 2023 vs Revised ESRS 2026: Which Version Should Your Company Use?
A version decision guide for FY2026 and FY2027, covering the current legal basis, 2025 Quick Fix, early-application routes, comparatives, local-law references and disclosure of the version used.
Published passport
Current as at 10 August 2026
Reviewed by
Dr Ross KurinkoLinkedIn
Strategic ESG Advisor · IFRS S1 & S2 / GRI / ESRS expert
GRI Certified Global Trainer · PhD, University of Cambridge · ESG-AI expert
15+ years on FTSE 100 & Fortune Global 500 disclosures
Canary Wharf, London
LRA educational guidance · Not issued or endorsed by European Commission
Edition written against
—
Published
10 Aug 2026
Knowledge Hub guide
Last reviewed
10 Aug 2026
Short answer
The answer, before the reasoning
For a financial year beginning in 2026, a company should not choose an ESRS version by preference alone. It must first confirm that the revised delegated regulation has entered into force and that the chosen route is valid for its reporting period and legal context.
The adopted act then permits three practical FY2026 routes: use the 2023 ESRS with the 2025 Quick Fix; use the full revised 2026 ESRS; or use the 2023 ESRS with Quick Fix plus only the specified revised reliefs. The company must clearly state the version used. For financial years beginning on or after 1 January 2027, the final revised ESRS are designed to apply.
Version selection affects more than wording. It determines materiality instructions, disclosure inventory, metric definitions, phase-ins, statement structure, comparative treatment, data systems, assurance evidence and how the basis of preparation is described. A route that appears easier for the current year may create a larger redesign one year later; a route that aligns early with FY2027 may require more system change and comparative analysis now.
Technical status
EDITORIAL STATUS
<p>Publication and legal-status control At 2 August 2026, the 2023 ESRS as amended by the 2025 Quick Fix remain the legally current EU standards. The revised ESRS adopted on 3 July 2026 are not yet in force. The adopted act provides FY2026 choices once in force and is designed to apply for FY2027 onward. Reconfirm the final Official Journal text, reporting period and national-law references before release.</p>
Quick orientation
Figure 1. FY2026 ESRS version decision matrix and FY2027 direction. London Reporting Academy learning visual.
Quick orientation
- Applies to
- Companies reporting for FY2026, and teams designing FY2027 systems before the revised regulation becomes mandatory.
- Primary decision
- Select a legally valid version route and document the data, comparative, control and disclosure consequences.
- Key source
- C(2026) 5010 Article 2 transitional provisions, Article 3 application, current 2023 ESRS and 2025 Quick Fix.
- Common confusion
- Assuming “adopted” means “already in force”, or mixing paragraphs from different versions without using the authorised hybrid route.
1. Current legal basis at 2 August 2026
Commission Delegated Regulation (EU) 2023/2772 remains the first set of ESRS in force. Commission Delegated Regulation (EU) 2025/1416, the Quick Fix, amended selected phase-in provisions for undertakings that had already begun reporting. The Commission adopted a replacement Annex I through C(2026) 5010 on 3 July 2026, but the Commission’s official page states that it is not in force until publication in the Official Journal. Therefore, a report authorised before entry into force cannot simply cite “revised ESRS 2026” as its legal basis.
Rule
Version-control principle
<p>A reporting team should preserve the full source set used for the statement: regulation number, annex version, publication date, reporting period, national-law basis, interpretation notes and the approved version decision. File names such as “final_ESRS_v9.xlsx” are not sufficient evidence.</p>
2. The three FY2026 routes in the adopted act
The eight Route C relief areas are: ESRS 1 paragraph 27 on top-down double materiality; paragraphs 32-33 on undue cost or effort and value-chain limitations in the assessment; paragraphs 74-75 on acquisitions and disposals; paragraph 90 on metrics for non-significant activities; paragraph 91 on partial value-chain reporting scope; paragraph 92 on joint operations; paragraph 106 on a separate EU Taxonomy appendix; and paragraph 110 on an executive summary. Other revised requirements and definitions do not become available under Route C merely because they appear helpful.
In practice
| Route | Permitted basis for FYs starting in 2026 | Main advantage — Main risk |
|---|---|---|
| A · Current | 2023 ESRS as last amended by the 2025 Quick Fix. | Lowest immediate redesign for an established wave-one process. — A full transition to revised ESRS is still needed for FY2027. |
| B · Revised | Full revised 2026 ESRS. | Earlier alignment with the FY2027 target architecture and reduced datapoint set. — Requires complete change mapping, new judgement controls, changed metrics and comparative analysis. |
| C · Hybrid reliefs | 2023 ESRS + 2025 Quick Fix, with only the eight relief areas listed in Article 2. | Targeted process and presentation relief without a full revised-metric transition. — High risk of accidental mixing beyond the authorised reliefs. |
3. The version used must be stated
Article 2 requires an undertaking using either the current/revised choice or the current-plus-reliefs route to state clearly in the sustainability statement which version it applies for the FY2026 reporting period. This is a core comparability and assurance control. The statement should identify the delegated regulation, the 2025 Quick Fix, whether the full revised standards are used and, for Route C, the specific reliefs applied.
Hypothetical scenario
Illustrative version statement - adapt to the final legal text
<p>“For the financial year beginning 1 January 2026, the group has prepared its sustainability statement using [Route A: Commission Delegated Regulation (EU) 2023/2772 as amended by Delegated Regulation (EU) 2025/1416 / Route B: the revised ESRS introduced by the delegated regulation of 3 July 2026, as published and in force / Route C: the 2023 ESRS as amended by the Quick Fix, together with the reliefs in Article 2(1)(b) relating to …]. The effects of the selected version on methods, boundaries and comparative information are described below.”</p>
Illustrative only. It shows how the decision is made, not wording that can be copied or relied on.
In practice
4. Decision criteria for FY2026
| Criterion | Route A may fit when… | Route B may fit when… — Route C may fit when… |
|---|---|---|
| Legal timing | The revised act is not yet in force for the report or early use is not valid. | The revised act is in force and full early application is legally available. — The revised act is in force and the listed relief route is available. |
| System readiness | Current definitions and controls are stable; redesign time is limited. | Systems can implement revised definitions, boundaries and disclosure inventory. — Systems remain mostly current but can support selected relief decisions. |
| Comparatives | Continuity with prior 2023-ESRS metrics is a priority. | The company can analyse changed metrics and apply transition relief correctly. — The reliefs do not create unmanaged comparative or presentation inconsistency. |
| Assurance | Assurance provider is prepared for the current basis and Quick Fix. | Assurance provider has reviewed the full transition and evidence. — Assurance provider can verify that only authorised reliefs were used. |
| FY2027 strategy | The company accepts a larger transition after FY2026. | The company prefers one earlier change to the future-state model. — The company wants targeted FY2026 relief while planning full FY2027 transition. |
5. What the 2025 Quick Fix changes
The Quick Fix was designed for undertakings already reporting from FY2024. It extends selected phase-in reliefs for FY2025 and FY2026 so that those undertakings do not have to add information that companies entering later waves would not yet have been required to report. It does not replace the 2023 ESRS, change the main double materiality model or authorise general use of the revised 2026 wording. Route A and Route C therefore need a controlled 2023-ESRS source set with the Quick Fix incorporated.
A practical mistake is to use a clean copy of Delegated Regulation (EU) 2023/2772 and overlook the Quick Fix, or to apply the Quick Fix to an undertaking that does not meet its conditions. The disclosure applicability matrix should identify every phase-in, the eligibility basis, the year used and the supporting source.
6. Comparatives and changed definitions
A Route B transition can change quantitative metrics, amounts, calculation methods or boundaries. Revised ESRS 1 generally requires prior-period comparatives for quantitative metrics and amounts and, where relevant, narrative disclosures. It also provides a transition relief: wave-one undertakings do not need comparative information in their first year under the revised regulation for metrics and amounts that are not the same as those required by the 2023 ESRS. Other undertakings are not required to provide comparatives in their first ESRS reporting year.
The relief is not a reason to erase trend information that remains comparable and useful. The reporting team should classify each metric as unchanged, changed but restatable, changed and impracticable to restate, new, or no longer required. Where a comparative is revised, the company should explain the reason and the difference. Where it is unavailable under a valid relief, the basis and effect should be clear.
In practice
| Metric status | Comparative treatment | Evidence |
|---|---|---|
| Unchanged definition and boundary | Continue the prior-period amount and consistency checks. | Current and prior calculation files, reconciliation and sign-off. |
| Changed but restatable | Restate the comparative and explain the change where significant. | Mapping, recalculation and approval. |
| Changed and impracticable to restate | Disclose impracticability and explain the break. | Impracticability assessment and reviewer challenge. |
| New under the selected version | Use the applicable first-year or transition relief if eligible. | Version source, eligibility and start-year record. |
| Removed from mandatory list | Assess whether it remains material or entity-specific before deletion. | Information-materiality conclusion. |
7. Local-law and reporting-period references
The delegated regulation is directly applicable once in force, but the duty to report and the reporting level arise through the Accounting Directive as transposed. The version memorandum should therefore include the national legal basis, the financial year start date, whether the undertaking is reporting under an individual or consolidated duty, and any regulator or filing guidance. A calendar-year group and an entity with a 1 July year start may reach different practical conclusions on availability, board approval and the first application period.
Where a group operates across Member States, the parent’s consolidated statement version does not automatically resolve every subsidiary’s local obligation, exemption citation or filing requirement. Legal and company-secretariat teams should confirm that the version statement, management report and assurance opinion use compatible legal references.
In practice
8. A controlled version-selection workflow
| Step | Action | Output / approval |
|---|---|---|
| 1 | Confirm the reporting-period start date and the revised regulation’s final entry-into-force and application provisions. | Legal-status note signed by legal/company secretariat. |
| 2 | Confirm national-law scope, reporting level, exemption position and any regulator guidance. | Scope memorandum. |
| 3 | Create a paragraph-level mapping of 2023 ESRS, Quick Fix and revised ESRS. | Version change register. |
| 4 | Assess Route A, B and C against system readiness, comparatives, assurance and FY2027 transition cost. | Decision paper with recommended route. |
| 5 | Approve the route and the exact basis-of-preparation wording. | CFO/management/board approval. |
| 6 | Freeze the disclosure inventory, data dictionary and relief register for the selected version. | Controlled reporting manual and system configuration. |
| 7 | Dry-run comparative, assurance and statement-structure impacts. | Mock statement and findings log. |
| 8 | Revalidate immediately before authorisation and release. | Final version sign-off and source archive. |
Hypothetical scenario
Illustrative scenario - two possible decisions
<p>Group A has stable 2023-ESRS systems, limited change capacity and a late FY2026 reporting close. It selects Route A, uses the Quick Fix, documents the larger FY2027 transition and avoids mixing revised definitions into current metrics. Group B has already rebuilt its materiality workflow, data dictionary and GHG boundary controls around the revised standards. After entry into force and legal review, it selects Route B, applies the comparative transition relief only where eligible and explains changed methods. Neither group describes its choice as “better compliance”; each demonstrates that its route is legally valid, consistently implemented and transparent.</p>
Illustrative only. It shows how the decision is made, not wording that can be copied or relied on.
In practice
FY2026 and FY2027 decision matrix
| Reporting period | Default legal focus | Version decision |
|---|---|---|
| FY beginning before revised act is in force | Current 2023 ESRS + applicable Quick Fix. | Do not cite the revised regulation as the preparation basis. Use it only for planning unless another valid legal basis exists. |
| FY beginning in 2026 after the act is in force | Article 2 transitional provisions. | Select Route A, B or C; document and clearly state the version used. |
| FY beginning on/after 1 January 2027 | Final revised ESRS under Article 3. | Use the revised standards, subject to the final published regulation and applicable law. |
Quick orientation
Common version-control mistakes
- Mistake
- Risk
- Using the July 2026 annex before entry into force
- The statement may cite a non-operative legal basis.
- Mixing preferred paragraphs from both versions
- Creates an unauthorised hybrid and inconsistent definitions.
- Failing to state the FY2026 version
- Reduces transparency and breaches the adopted transition provision.
- Using the same metric code for changed definitions
- Comparatives and assurance evidence become unreliable.
- Assuming Quick Fix applies to everyone
- Phase-ins may be used by an ineligible undertaking.
- Selecting a route without assurance input
- Late evidence or comparative findings can force rework.
Readiness
Version decision checklist
- The reporting-period start date and final entry-into-force date are confirmed.
- The national legal basis and reporting level are cited.
- The undertaking’s Quick Fix eligibility is documented.
- Route A, B and C impacts have been compared across data, controls, comparatives, assurance and FY2027 cost.
- The selected route has formal management or board approval.
- The disclosure inventory and data dictionary are locked to one version.
- Every Route C relief is separately identified; no other revised paragraph is mixed in.
- Comparative metrics are classified and transition relief eligibility is recorded.
- The basis-of-preparation wording clearly states the version used.
- The final source set and version memorandum are retained for assurance and future updates.
In practice
Source register
| ID | Official source | Role in article — Status |
|---|---|---|
| S1 | Commission Delegated Regulation (EU) 2023/2772 | Current 2023 ESRS — In force |
| S2 | Commission Delegated Regulation (EU) 2025/1416 | Quick Fix amendment and phase-ins — In force |
| S3 | Commission Delegated Regulation C(2026) 5010 final, Article 2 | FY2026 version choices and listed reliefs — Adopted; not yet in force at review date |
| S4 | C(2026) 5010, Article 3 | Entry into force and FY2027 application — Final OJ text pending |
| S5 | Annex I revised ESRS 1, paragraphs 83-87 and 124 | Comparatives and transition relief — Adopted text |
| S6 | National implementing law and regulator guidance | Scope, reporting level, filing and local references — Jurisdiction-specific |
Take it with you
The checklists as a working spreadsheet
Every checklist and table on this page, with empty status, owner and evidence columns for your team to fill in and keep.
✓ LRA AI Assistant · Human-in-the-loop
Ask about this guide
It answers from this page, and reaches into the linked disclosure cards when your question is about the standard itself. Your first two answers are free without signing in.
Go deeper · ESRS
ESRS and CSRD training
Double materiality, datapoints and the sustainability statement, with a mentor on your own report.
Available as Guided Flex, Live Cohort, 1:1 Expert Mentorship or Corporate Programme.