Energy invoices, purchasing records, workforce information and supplier evidence already support decisions across your business. When reporting standards change, the immediate cost is often reorganising those records: teams revise templates, repeat requests and rebuild explanations for figures they have already collected. The ESRS transition should reduce that work, rather than create another disconnected reporting project.
This article originally examined an April 2026 forecast of a possible Q4 delay. That forecast has been superseded. The European Commission adopted the revised ESRS on 3 July 2026, and the published regulation now provides a confirmed timetable. Planning should use that final text rather than commentary about a draft.
The practical issue is how to close FY2026 while preparing for FY2027. Teams need to choose the appropriate reporting route, retain a clear record of that decision and adapt their disclosure mapping without losing useful source data. Reporting, cost analysis and operational decisions can continue to draw on the same underlying information.
Below, we distinguish the legal milestones, explain the FY2026 choices and set out a working approach for finance, reporting, operations and review teams. The dates concern the standards; whether a company must report still requires a separate assessment of its applicable CSRD scope and national rules.
Update, 3 November 2026: The revised ESRS have been adopted and published. Entry into force is set for 10 November 2026, followed by application to financial years beginning on or after 1 January 2027. FY2026 options must be assessed under the published transitional provisions, not the earlier draft.
The confirmed ESRS timetable
Adoption, publication, entry into force and application are different milestones. The Commission’s 3 July announcement confirms adoption. ESMA’s implementation information records publication and entry into force. The distinction matters because a draft, an adopted act and an applicable reporting requirement do not have the same status.
| Milestone | Confirmed date | Planning consequence |
|---|---|---|
| Commission adoption | 3 July 2026 | The adopted text replaced the earlier drafting forecast. |
| Official Journal publication | 21 September 2026 | Teams can reference the published regulation and annexes. |
| Entry into force | 10 November 2026 | The regulation becomes operative under its entry-into-force provision. |
| FY2026 transition | Financial years beginning in 2026 | Assess the reporting choices permitted by Article 2. |
| General application of revised ESRS | Financial years beginning on or after 1 January 2027 | Prepare the reporting process for the revised standards. |
EFRAG’s publication notice distinguishes FY2027 application from the permitted FY2026 early-adoption route. For a calendar-year company, collecting FY2027 information and publishing a statement about that year are separate stages. Build the internal timetable around the actual financial year and applicable filing requirements.
A change in the standards does not automatically determine whether a particular company is in scope. Keep the eligibility assessment separate from the decision about which ESRS version to apply. Our CSRD transposition analysis explains why the national position also matters.
3 reporting routes to assess for FY2026
Article 2 of Delegated Regulation (EU) 2026/1563 provides the FY2026 transition choices. These include the existing standards as amended by the quick fix, the revised standards, and the existing standards with specified provisions from the revised text. The sustainability statement must identify the version applied.
1. Retain the existing ESRS with the quick fix
For a team with an established close process, continuity may reduce the immediate configuration work. Assess the applicable reliefs against the published provisions and the company’s circumstances. Do not treat the quick fix as a blanket exemption from every disclosure on a topic.
Document the version, reliefs and decisions in the reporting file. Maintain the disclosure checklist and explain any changes from the previous period. This route still needs a transition plan for FY2027; retaining an existing process for one close does not remove the need to prepare the next one.
2. Use the existing standards with the specifically permitted provisions
The regulation allows particular revised provisions to be used alongside the existing standards. This is a defined legal option, rather than permission to assemble a preferred set of requirements from different versions.
Prepare a decision log identifying the provisions selected, their conditions and the affected disclosures. Discuss the approach with the responsible accounting and review teams before changing templates. The implementation task is to keep the reporting basis understandable to everyone who prepares, approves or examines the statement.
3. Apply the revised ESRS for FY2026
Early adoption can align the current close with the next reporting cycle, but only if the organisation can implement the revised approach properly. Compare the remaining work on materiality, mappings, methodologies, narrative disclosures and controls before choosing this route.
A practical readiness test is to prepare a representative disclosure using the proposed configuration. Ask a reviewer to reconstruct its figures and decisions without relying on an undocumented explanation. If that test reveals gaps, include their resolution in the timetable rather than assuming that fewer datapoints make the transition automatic.
Fewer datapoints still require reliable evidence
Update the disclosure map before changing collection
The Commission describes a reduction of more than 60% in mandatory datapoints and more than 70% in the total number of datapoints. These are changes to the standards, not a guaranteed reduction of the same size in every company’s workload.
Map the existing disclosures to the final requirements and record what is retained, changed or no longer required for that output. Apply the relevant materiality decisions and transitional conditions. A draft comparison can help locate changes, but the final mapping should reference the adopted text and its applicable provisions.
Separate disclosure changes from business data needs
An electricity record may no longer feed one particular reporting field yet remain useful for emissions calculations, energy-cost analysis or a customer request. Deleting the source because a disclosure changes can create another collection exercise later.
Record both the reporting purpose and the wider business uses of each dataset. Review retention, access and quality requirements accordingly. The useful saving comes from removing duplicated preparation and unnecessary transformations while preserving information that still supports a legitimate operational or reporting need.
Keep one data foundation as reporting rules change
Dcycle is an environmental data platform for structuring information the company already generates. Instead of rebuilding energy, fuel, materials and supplier records for each request, teams can organise a shared foundation for reporting, savings analysis and operational decisions.
The distinction between source data and reporting configuration is important during the ESRS transition. A platform assessment should test how records retain their evidence, how calculations are documented and how a reporting mapping can change without silently overwriting a previously approved result. These controls matter more than a generic promise that a product is ready for every standard.
For example, follow an energy invoice through its consumption record, emissions calculation and cost view. Then test a correction and compare the affected outputs. Dcycle’s automated data collection and CSRD resources provide a starting point for discussing that workflow with your own data and requirements.
Reviewing your ESRS transition? Bring an energy, fuel or supplier dataset and see how Dcycle connects source records, evidence and reusable outputs.
Review your data workflow5 practical steps for FY2026 and FY2027 planning
1. Confirm the reporting perimeter and financial year
Identify the legal entities, consolidation boundary and financial year covered by the statement. Record the eligibility assessment and the people responsible for confirming it. Do not use the date of a new standard as a substitute for that analysis.
Include acquisitions, disposals and changes in reporting responsibility in the review. Finance, legal and the reporting team should work from the same documented perimeter before operational teams receive revised data requests.
2. Approve the FY2026 reporting basis
Prepare a short decision paper comparing the available route with the organisation’s readiness. Explain the work required, the reasons for the choice and the implications for the next reporting cycle.
Assign an owner for keeping the decision, supporting references and approvals together. The configuration used in the reporting process should match that record. Changes after approval need a visible review process rather than an informal adjustment to a spreadsheet.
3. Map disclosures to sources, methods and owners
For each relevant disclosure, identify the source system or document, period, unit, calculation method, evidence and responsible person. Distinguish raw activity data from derived metrics and narrative explanations.
Use this map to identify missing information and duplicated requests. Where a source feeds several outputs, document the adjustments needed for each. Reuse should preserve differences in boundaries and definitions, not hide them behind a common field name.
4. Test representative disclosures before scaling
Choose examples that cover a calculation, a narrative explanation and information from another entity or supplier. Trace each example from the source to the proposed statement and back again.
Include an incomplete record and a correction. Record who resolves the issue, how the change is approved and what happens to related outputs. A successful test should demonstrate a repeatable process, not simply produce a plausible final number.
5. Set the FY2027 transition and review calendar
Plan when mappings, templates, responsibilities and controls will be updated for the next financial year. Include time for training, questions from contributing teams and resolution of findings from the pilot.
Retain an approved reference for the previous reporting configuration. That helps explain why figures or disclosures differ between periods and prevents later changes from making the earlier statement impossible to reconstruct.
Practical tip: Use the same source record to test both the current and proposed reporting configuration. Compare the evidence, transformations and approvals, then record why any output differs. This separates an operational change from a change in reporting treatment.
3 mistakes to avoid during the transition
1. Treating the smaller disclosure set as permission to delete records
A reporting field and its underlying source have different purposes and retention needs. Before removing a collection step, identify who else uses that information and whether another obligation, contract or operational process depends on it.
Document the decision and the affected outputs. The aim is to remove unnecessary work without creating a blind spot for finance, operations, procurement or later review.
2. Mixing versions without a documented reporting basis
Using an old checklist, a new template and draft guidance together can make the final statement difficult to assess. The problem is not simply inconsistent labels: teams may be applying different conditions without recognising the difference.
Maintain one approved reporting basis and reference the specific options used. Keep draft working documents clearly separated from the approved configuration and explain which version each reviewer is examining.
3. Confusing reporting preparation with independent assurance
Organised records and automated checks can support a review, but they do not replace the practitioner’s work or guarantee an assurance outcome. Agree the engagement scope and evidence expectations with the relevant professionals.
Rehearse the evidence trail before the formal review. Our ESRS implementation resources can help frame the platform questions, while the company remains responsible for its methods, source quality and approvals.
Conclusion: make the transition a controlled data project
The planning question has moved beyond whether the delegated act might be delayed. The published timetable gives teams a basis for choosing their FY2026 route and preparing the FY2027 process. The remaining work is to turn that decision into mappings, responsibilities, evidence and a realistic review calendar.
Start with the perimeter and reporting basis, then test representative disclosures before scaling. Preserve useful source records and distinguish changes in business activity from changes in reporting treatment. That makes the process easier to maintain and the results easier to explain.
A shared environmental data foundation can continue to support consumption analysis, savings opportunities and operational decisions throughout the transition. The reporting statement becomes one output of that work, rather than the reason to rebuild the same information every year.
Make your next reporting change easier to manage with source data, responsibilities and evidence connected in one workflow.
Talk to the Dcycle teamFrequently asked questions (FAQs)
Was adoption of the revised ESRS delayed until Q4 2026?
No. The Commission confirmed adoption on 3 July 2026. The later milestones are publication and entry into force. The earlier April forecast should not be used as the current adoption timetable. Use the published regulation and distinguish these milestones when planning the reporting cycle.
When do the revised ESRS enter into force and apply?
Entry into force is set for 10 November 2026, with application to financial years beginning on or after 1 January 2027. As of this article’s 3 November update, the entry-into-force date is still ahead. Applicability of CSRD to a particular company remains a separate assessment.
Can a company use the revised ESRS for FY2026?
The published transition provisions permit FY2026 choices, including the revised standards. Assess eligibility, the permitted reporting basis and the required statement identifying the version used. The decision should be supported by a readiness review and consistent configuration, rather than a selective combination of draft and final requirements.
Does the quick fix make every topical disclosure optional?
No. Reliefs have specified conditions and scope. Review the provisions applicable to the company and reporting period, and retain the reasons for using them. A general reference to the quick fix does not explain which requirements were deferred or how the rest of the statement was prepared.
Should we stop collecting a metric that disappears from a reporting template?
First check whether the source is still needed for another disclosure, customer request, legal requirement or operational decision. A change to one output does not determine every use of the underlying record. Document the purpose, retention decision and affected processes before removing a collection step.
What should a platform demonstration prove during the transition?
Ask it to trace a record from its source through the calculation, evidence and reporting output, then show a correction. Check methods, permissions, approvals, history and the effects on other outputs. The demonstration should help you assess the continuing workload and ability to explain results, not only the presentation of a completed report.
