Revised ESRS (2026): What the July 3 Adoption Changed — and Why ‘Simpler’ Means Remapping Your Data

Somewhere in Europe there is a sustainability team that finished its ESRS datapoint mapping in June.

Months of work. Every disclosure requirement traced back to a system of record, an owner, a refresh cadence. Spreadsheets reconciled against subsidiary ledgers. The whole apparatus finally standing up on its own.

On 3 July 2026, the European Commission adopted the revised standards that mapping was built against.

The headline is relief: mandatory datapoints cut by more than 60%. The operational reality is less comfortable. A standard that shrinks is still a standard that changed, and every datapoint already wired to the 2023 set now has to be re-checked against the 2026 one. “Simpler” and “less work this year” are not the same sentence.

Here is what actually changed, what quietly got stricter, and what to do with the runway you have.

What happened on 3 July

The Commission adopted the final delegated act containing the simplified European Sustainability Reporting Standards — ESRS (2026) — one of the closing steps of the Omnibus simplification package first proposed in February 2025. The Commission published its accompanying staff working document the same day (SWD(2026) 500 final).

The procedural path from here is short and largely one-way. The texts went to the European Parliament and the Council, which have two months to scrutinise them. Neither institution can amend the act — it can only be rejected in full, which practitioners generally consider unlikely (Cooley). On publication in the Official Journal, the revised ESRS enter into force on 20 November 2026 and apply to financial years beginning on or after 1 January 2027.

So the calendar is fixed: you report your FY2027 year against ESRS (2026), and you have the remainder of 2026 to be ready for it.

What got cut

The reductions are real and they are large. Mandatory datapoints are down by more than 60% — a 61% reduction against the 2023 standards — and the total number of datapoints is down by more than 70% (PwC; Deloitte). The Commission’s projection is roughly a 30% reduction in reporting cost per organisation — a projection, not an observed outcome, and one that assumes you are not paying to rebuild your mapping by hand.

What did not change is the architecture. The revised set keeps the same shape: ESRS 1 and 2 for general requirements and general disclosures, five environmental standards, four social standards, one governance standard. If you invested in understanding the topical structure, that investment holds. It is the datapoint layer underneath that moved.

That distinction matters for how you plan the next six months. This is not a re-education project. It is a data-lineage project.

What got stricter

The simplification narrative has buried the part of this act that raises the bar, and it is the part most likely to cause pain during assurance.

A new fair-presentation requirement. Disclosed information must be comparable, verifiable and understandable — and companies must be able to justify their conclusions to assurance providers more rigorously than before. Fewer numbers, held to a higher evidentiary standard. If a figure cannot be traced to its source and its transformation, the reduced datapoint count will not save you.

A prohibition on padding. Companies generally may not report non-material information unless it is required by other legislation, stems from a recognised reporting framework, or meets a specific user demand. The familiar defensive move — disclose everything, let the reader decide — is now largely closed off. That raises the stakes on the materiality assessment itself, because you can no longer hedge a borderline call by disclosing anyway.

Materiality becomes an annual question. The revised standards permit a top-down approach to double materiality, starting from an analysis of the business model to identify evidently material topics, while still allowing bottom-up methods or a combination. In exchange, companies must evaluate annually whether significant changes warrant revisiting their materiality conclusions.

The treatment of mitigation also got more precise. For actual impacts, remediation carried out during the period cannot reduce the assessed severity. For potential impacts, prevention measures can be taken into account where they are reasonably effective. Positive impacts cannot be netted against negative ones, and cannot consist merely of legal compliance.

Where the relief is real

Two areas give genuine breathing room, and both are worth planning around.

Value chain. Under the Omnibus I amendments, a company subject to CSRD cannot require companies in its value chain with 1,000 employees or fewer to provide more sustainability information than the voluntary standard requires — with an important carve-out: gross Scope 1, 2 and 3 greenhouse gas metrics are excluded from that cap. Companies may also rely on proxies and estimates for value-chain data, and the previous obligation to make reasonable efforts to obtain information from suppliers has been removed.

Read that carefully before you stand down your supplier programme. The relief covers the long tail of questionnaires. It does not cover your emissions inventory, which is exactly the dataset most companies find hardest.

Transitional reliefs. Companies beginning to report for FY2027 may omit information on anticipated financial effects for their first two reporting years, and quantitative data on those effects for four years. A new “undue cost or effort” proportionality mechanism allows a company to forgo gathering information where doing so would be unreasonably burdensome, reassessed annually. Subsidiaries acquired during a reporting period can be deferred into the following period’s materiality assessment.

The Japan collision

For Japanese multinationals, none of this arrives in isolation.

Japan’s own standards are on a parallel track. The SSBJ finalised its standards on 5 March 2025, with mandatory application beginning for fiscal years ending March 2027 for Prime-listed companies above ¥3 trillion in market capitalisation, extending to ¥1 trillion in 2028 and ¥500 billion in 2029. Globally, IFRS S1 and S2 continue to spread — the IFRS Foundation counts jurisdictions representing more than half of global GDP moving to adopt.

A Japanese company with material EU operations is therefore standing up an SSBJ disclosure for FYE March 2027 and an ESRS (2026) disclosure for FY2027 in the same window, from what is largely the same underlying data, on two different timetables and in two different languages. Meanwhile CSRD’s post-Omnibus scope gate — more than 1,000 employees and more than €450M turnover — has cut roughly 80% of the companies originally in scope, taking the population from around 49,000 to an estimated 8,000–10,000. Being out of direct scope does not mean being out of the data flow: those companies still sit in someone else’s value chain.

The teams that struggle here are the ones treating each framework as a separate reporting project. The teams that cope are the ones treating all of them as views onto one governed dataset.

What to do before 20 November

1. Inventory what you mapped, and to which version. Every datapoint reference should carry a standard-version tag. If your mapping does not record which ESRS release it was built against, that is the first gap to close — and the reason the next revision will hurt as much as this one.
2. Re-run the materiality assessment with the top-down option in mind. You now have a permitted route that starts from the business model. Document the reasoning, because you will need to defend it and revisit it annually.
3. Separate the datapoints you lost from the ones that moved. A removed disclosure is a saving. A relocated or reworded one is a remap. Conflating them is how teams discover in month eleven that they are short.
4. Do not decommission your emissions data pipeline. The value-chain relief explicitly excludes gross Scope 1, 2 and 3 metrics.
5. Build for the fair-presentation bar, not the datapoint count. Every figure should have a traceable path from source system to disclosure, surviving the departure of the analyst who built it.

Where Socious fits

Point 5 is the whole thesis behind what we build. Socious Report takes your data in once, normalises it, and maps it to CSRD, SSBJ and ISSB from that single dataset — so a standard revision is a remapping inside the platform rather than a rebuild across your spreadsheets. Each disclosure keeps its lineage back to the source, and finished reports can carry an independent Socious Verify credential for the assurance conversation.

If you want a read on where you actually stand before committing to a programme, our free CSRD readiness check and SSBJ readiness check take a few minutes and produce a gap view you can take to your steering committee.

Further reading: the full CSRD timeline and wave deadlines, our ESRS datapoint mapping guide, the SSBJ roadmap for Japanese companies, and the wider Asia-Pacific reporting requirements for 2026.