A reporting deadline moves, the scope narrows and the sustainability team receives a reasonable question from finance: which parts of the programme still need funding?
The answer depends on the work. A disclosure that is no longer required may justify stopping a collection exercise. A reliable record of energy use, supplier information or material business exposure may still support a decision. Keeping every project running under the old budget can be expensive. Closing everything can leave useful work unfinished.
The Corporate Sustainability Reporting Directive, or CSRD, establishes sustainability reporting obligations for companies within its scope. For a finance leader, the practical starting point is to establish the company’s obligation and connect the remaining reporting work to people who can deliver it.
Who Does the CSRD Apply To?
The 2026 amendments substantially narrowed the main EU reporting scope. The amended framework uses both net turnover above EUR 450 million and an average of more than 1,000 employees, assessed at the relevant company or group level. The revised application framework covers financial years starting in 2027; earlier reporting periods and available exemptions require separate assessment. These changes are set out in Directive EU 2026/470.
A group should therefore record its conclusion by legal entity, reporting period and applicable rule. Consolidated reporting, national implementation and exemptions can affect the answer. A non-EU parent also needs an assessment of the provisions relevant to its circumstances. A slide containing two thresholds cannot settle every entity’s position.
Keep customer questionnaires distinguishable from statutory reporting. A company outside mandatory scope may still receive a commercial information request. Someone should assess its purpose, proportionate coverage and applicable limits before distributing it throughout the business.
This distinction has a direct budget consequence. The person requesting a voluntary exercise should be able to explain who will use the result and which decision depends on it.
Turn materiality into an operating decision
CSRD and the European Sustainability Reporting Standards perform related functions. CSRD sets the reporting framework; ESRS specify the reporting requirements. The Commission adopted revised ESRS in July 2026 and described the subsequent scrutiny process. Teams need to establish the version applicable to their reporting period before changing their collection design. The Commission announcement distinguishes adoption from the process before application.
Double materiality considers the company’s impacts on people and the environment and the financial effects of sustainability matters on the business. A matter can be material from either perspective. EFRAG’s implementation guidance explains the assessment approach, while remaining non-authoritative guidance to be read alongside the applicable standards.
Consider an illustrative manufacturer with several production sites. Flood exposure at one location may affect continuity and investment decisions. The assessment also needs to consider the company’s relevant impacts; financial exposure alone does not complete it.
The useful output explains the conclusion, supporting facts and resulting disclosure work. A list of topics selected in a workshop leaves the collection team with too much interpretation to do later.
Follow one disclosure from source to approval
Suppose the manufacturer needs to describe measures taken at the exposed site. Operations knows what was installed. Finance holds the expenditure records. The site manager knows whether the work is complete. The sustainability team prepares the disclosure.
Each source answers a different question. An approved budget establishes authorisation. An invoice supports expenditure. Neither necessarily establishes that the measure is operating across the area described in the report.
The collection request should identify the claim being made and ask for the evidence that supports it. If the measure is complete in one building and planned for another, the final wording should preserve that difference.
Give the disclosure a responsible owner and a reviewer who can examine the underlying facts. Record the source version and the reason for any adjustment. When the completion date changes, the team should know which sentence requires reconsideration.
This is where a shared compliance workspace becomes useful. It can connect the disclosure to its supporting records and unresolved questions, so reviewers spend their time assessing the claim rather than locating attachments. Its value depends on those working connections.
Rework the budget around deliverable results
A revised programme should distinguish work that can stop, work required for the remaining obligation and work retained for an identified business use. The categories should describe actual tasks, contracts and ownership.
For example, closing a redundant questionnaire may remove recurring effort. Preserving a site register may support both reporting and operational analysis. Completing a source connection may still be worthwhile if it replaces a repeated reconciliation that finance needs every month.
Include internal effort in these decisions. A low software subscription can still require substantial manual preparation. A source correction may cost more initially while removing work from several later reporting cycles.
Avoid presenting expected savings as achieved results. Record the current effort, identify what should change and revisit the comparison after the new process has operated. If time is released, explain how the team will use it; reduced preparation hours do not automatically reduce expenditure.
Make the next review easier to perform
Reporting readiness should show what remains unresolved and why it matters. A dashboard with most fields complete can conceal a missing assumption that prevents approval of a significant disclosure.
Show the specific question, its owner and the consequence of delay. A missing document belongs with someone who can obtain it. A disagreement about scope needs someone authorised to decide it. Additional reminders will not solve either problem if the request reaches the wrong person.
Bring assurance considerations into preparation where reporting requires assurance. Ask whether a qualified reviewer can trace a selected disclosure back to its basis and reproduce a significant calculation. Preserve earlier versions when standards or business boundaries change, so a later review can still explain the original report.
The first funding decision under the revised programme should name a result that management can inspect. For the manufacturer, that might be a supported scope conclusion and one completed disclosure whose claims agree with the site’s records. The ESRS collection process can then expand from a working example, with the remaining requests tied to a clear obligation and an accountable owner.
