EU Voluntary Standard vs ESRS: Key Differences for Companies Outside CSRD Scope

The frameworks share sustainability subject matter but serve different legal and reporting architectures.

Companies outside CSRD scope often receive ESRS-shaped questionnaires and assume that completing the Voluntary Standard produces an “ESRS-aligned” report. That can overstate the reporting basis and hide gaps in materiality, value-chain coverage, governance and disclosure architecture.

The more useful model is reuse without equivalence: preserve controlled datasets, methods and evidence, then identify the additional decisions and disclosures required if the undertaking later enters CSRD scope or voluntarily prepares an ESRS-based statement.

Data overlap can support efficiency, but the reporting basis and claims remain framework-specific.

The Voluntary Standard is intended to support undertakings not subject to mandatory sustainability reporting. Its objectives include responding to data needs from reporting undertakings, banks and investors, improving sustainability management and limiting disproportionate value-chain requests through the value-chain cap for protected undertakings. It is therefore a practical reporting and data architecture, not a substitute legal regime for CSRD.

ESRS, by contrast, specify information for undertakings required to report under the Accounting Directive as amended. Whether a company is in scope is a legal question involving size, listing, group, jurisdiction, transition and national implementation. A framework comparison cannot determine scope without those facts.

SCOPE CONTROL / A company outside CSRD today should record why it is outside scope, who approved that conclusion and what events could change it: growth, listing, acquisition, group restructuring, non-EU parent rules, national transposition or another legal change.

The Voluntary Standard uses modules. A reporting route is chosen and the applicable module is tested in its entirety, while individual datapoints may be conditional, voluntary or subject to a micro relief. This is different from an ESRS process that first identifies material impacts, risks and opportunities and then determines which topical and entity-specific information is material to report.

The Voluntary Standard contains selected value-chain content, including C7 awareness of confirmed incidents, Scope 3 considerations and business-relationship information. Its Annex II datapoints also function as the upper limit for certain sustainability information requests to protected undertakings. This helps an SME maintain one controlled dataset for counterparties.

ESRS require material upstream and downstream value-chain information according to the double materiality assessment and specific topical requirements. They do not require data on every actor, and estimates can be used when direct information is not practicable or reliable. However, the scope is driven by material IROs, not simply by whether a datapoint appears in the Voluntary Standard.

The Voluntary Standard does not create a general duty to obtain external assurance or to publish a universal annual report. An undertaking can prepare a public report, a controlled counterparty response pack, or a reusable dataset and evidence room, provided its basis and claims are transparent.

An undertaking subject to CSRD reports a sustainability statement in a dedicated section of the management report and enters the statutory assurance, filing and governance environment applicable in its jurisdiction. Cross-referenced information must meet strict conditions, including availability and assurance treatment. The exact legal obligations should be confirmed against the final delegated act, Accounting Directive and national law.

NON-EQUIVALENCE RULE / A common data field is not a common reporting requirement. Energy, emissions, workforce and policy data may be reused, but the reporting entity, materiality logic, definitions, boundaries, comparatives, disclosure selection and claim must still be tested separately.

Migration preserves evidence but adds framework-specific decisions and reporting controls.

Confirm legal scope and timeline. Document the reporting entity, group, exemptions, transition and national filing requirements.

Reconcile the reporting perimeter. Map subsidiaries, associates, joint ventures, sites and value-chain relationships to ESRS boundaries.

Perform double materiality. Identify actual and potential impacts, dependencies, risks and opportunities across short-, medium- and long-term horizons.

Build the IRO register. Record location, value-chain position, affected stakeholders, financial channels, assessment criteria and approvals.

Select material information. Apply ESRS topical requirements and add entity-specific information where necessary.

Expand governance and strategy. Connect material IROs to governance oversight, strategy, business model, financial effects and resilience.

Map policies, actions, metrics and targets. Convert Voluntary Standard practices and datapoints into ESRS-controlled disclosures, including “not in place” statements where required.

Strengthen value-chain methods. Add material upstream/downstream data, estimates, proxies and cap documentation.

Build the sustainability statement. Apply structure, cross-reference, comparatives, digital and publication controls.

Prepare for assurance. Formalise evidence, ownership, reconciliations, estimates, review, governance approval and remediation of control findings.

ILLUSTRATIVE SCENARIO / A 700-employee manufacturer has used Option B for two years and is acquired by a group that will report under ESRS. Its energy, GHG, workforce, policy and site data are reusable. However, the prior report did not identify material IROs, assess financial materiality, map upstream and downstream value-chain information by topic, connect policies and actions to material IROs, disclose governance information flows or prepare a sustainability statement. The group imports the controlled dataset into an ESRS gap register rather than relabelling the Option B report as ESRS compliant.

MYTH / REALITY / Myth: “A company outside CSRD should prepare ESRS anyway because the Voluntary Standard will soon be obsolete.” Reality: the appropriate architecture depends on users, resources, group plans and expected scope. A controlled Voluntary Standard dataset can deliver immediate value and support migration, provided it is not represented as full ESRS reporting.