The Cost of Sustainability Reporting After the Omnibus: What Actually Got Cheaper

On 3 July 2026 the European Commission adopted the revised ESRS. Its own summary of the effect is specific: the standards “reduce the number of mandatory datapoints by over 60% and the total number of datapoints by more than 70%”, and together those changes “are expected to lower reporting costs by over 30% per company” (European Commission).

That is a real number from a credible source, and it has been read in a way the Commission did not say. Cutting seven datapoints in ten does not cut seven euros in ten. The Commission knows that, which is why its own estimate is thirty per cent and not seventy.

The gap between those two figures is the whole subject of this article. It is also where most 2027 reporting budgets are currently wrong.

What the Commission actually promised, and to whom

Two separate numbers get quoted together and should not be.

The headline for the whole Omnibus I package, announced in February 2025, was “over €6 billion in administrative relief”. That figure covers sustainability reporting, due diligence, the Taxonomy, CBAM and InvestEU together. It is an economy-wide relief estimate. It is not a per-company saving, and no single filer should expect to find a slice of it in their own budget.

The “over 30% per company” figure is narrower and more useful. It refers to the revised ESRS specifically. It is the one to plan against.

There is a third saving that dwarfs both, and it only applies to some readers. Directive (EU) 2026/470 reset who is in scope at all: more than 1,000 employees and more than €450 million in turnover. The Commission describes Omnibus I as having “reduced the number of companies within the scope of the Corporate Sustainability Reporting Directive”. For a company that falls out entirely, the saving is not thirty per cent. It is the whole line. We covered the mechanics of that reset in The EU Omnibus Is Now Law.

If you are still in scope, read on. The thirty per cent is yours, and it will not land where you expect.

Why a 70% datapoint cut is not a 70% cost cut

Reporting cost is not paid per datapoint. It is paid per system, per boundary, per supplier and per hour of reconciliation.

Consider what does not change when a datapoint is removed from a standard. You still need the source system that would have fed it. You still need one consolidated reporting boundary that matches your financial statements. You still need someone who can explain, eighteen months later, which emission factor was used and why. Removing the disclosure obligation removes the last step, the writing. It leaves the plumbing exactly where it was.

Workiva’s 2024 survey of more than 2,200 professionals found 83% saying that collecting accurate data to meet CSRD requirements would be the challenge. Collection is the expensive half, and collection cost tracks the number of sources you touch, not the number of boxes you fill.

A concrete version. Suppose Scope 2 previously fed four required datapoints and now feeds one. You have not stopped needing meter readings from every site. You have not stopped needing a market-based and a location-based figure. You have removed one output of an unchanged process. The saving is real. It is a fraction of the reduction the headline percentage suggests, because the percentage measures outputs and the invoice measures inputs.

Three costs the revision does not reach

Assurance. Sustainability disclosures still require independent assurance, and an assurance fee is driven by the evidence the provider has to test, not by the length of the standard. If your emission factors live in a spreadsheet with no record of who chose them, the provider does the same work on a shorter report. Our guide to limited and reasonable assurance sets out what that testing involves.

Value-chain requests. The revision introduced the value chain cap, so companies in scope “cannot require companies in their value chains to provide more information than is covered by the voluntary standard” (European Commission). That protects your suppliers. It does not remove your need to ask, chase and reconcile what comes back. We wrote about what a supplier may now refuse in The Value Chain Cap.

Everyone else who asks. Falling out of CSRD scope does not make the questions stop. Your bank will want financed-emissions inputs regardless of whether IFRS S2 applies to you, which we covered in IFRS S2 Does Not Apply to Your Company. CBAM, EUDR and the CSDDD run on overlapping supplier data on their own calendars, as set out in One Supplier Dataset, Four EU Filings. A company out of scope and unprepared answers the same questions with less structure and no assurance to point at.

Nothing has applied yet

One timing point that budgets keep missing. The revised ESRS and the voluntary standard “will now be submitted to the European Parliament and the Council for scrutiny”, and “will apply once the two-month scrutiny period, which can be extended by a further two months, has ended” (European Commission).

Adopted is not in force. Any plan that assumes the reduced datapoint set is already binding is planning against a document that is still in a scrutiny window.

In Japan, none of this saving travels

This is the part that catches Japanese groups with EU operations, and it is simple.

SSBJ is not derived from the ESRS. It comes from Japan’s own process, given legal effect through a Cabinet Office Ordinance, and it phases in on its own timetable: annual reporting periods ending March 2027 for Prime-listed entities with market capitalisation of ¥3 trillion or more, March 2028 at ¥1 trillion, March 2029 at ¥500 billion (IFRS Foundation).

Nothing the Commission adopted in July changes any of that. A Japanese group in the first SSBJ cohort with EU subsidiaries now has a European obligation that got lighter and a Japanese obligation that did not, arriving first. The reduction applies to one of the two reports it files, and to the later one.

That asymmetry is the practical case for building the dataset once rather than per framework. The operational detail is in our dual-reporting guide and the SSBJ roadmap.

What actually moves the bill

Three things, in order of how much they move it.

Collect once. The cost is in the sources, so touch each one a single time and let every framework draw from the same set. Two collection exercises for CSRD and SSBJ is the expensive mistake, and it is the common one.

Record the method beside the number. Factor, source, publication year, boundary, and the reason for the judgement, written when the judgement is made. This is what an assurance provider tests. Reconstructing it from invoices a year later is where the fee goes.

Fix the boundary once. One consolidated boundary answers your lender, your largest customer, your CSRD statement and your SSBJ report. Reconciling three boundaries is a cost no simplification package will ever reach.

The Omnibus made the report shorter. It did not make the data easier to get, and the data was always the bill.

If you want to see where your own gaps sit, our free CSRD readiness check and SSBJ readiness check each take a few minutes and return a specific list rather than a score. Socious Report is for the part after that: one dataset that produces CSRD, SSBJ and ISSB reports, with an independent Socious Verify credential attached to the result.