Skip to the answer

Disclosure GuidesPillar guides, articles, FAQ and expert notes

Level 2 · Comparison·EU Voluntary Standard 2026 · Disclosure guides

EU Voluntary Standard 2026 vs VSME

What changed - and which version should reporting teams use?

Who this is for A 11-minute read for reporting teams working through Preparing, controlling and releasing the report, and for reviewers testing whether the evidence behind it holds.

Short answer

The answer, before the reasoning

The 2026 EU Voluntary Standard is not a wholly new architecture: it is based on the VSME standard endorsed by Commission Recommendation (EU) 2025/1710 and retains the Basic B1-B11 and Comprehensive C1-C9 modules. The main changes are its proposed legal form and role, the wider intended population up to 1,000 employees, a statutory value-chain cap defined through a separate Annex II, specific reliefs for undertakings with 10 employees or fewer, alignment with the revised ESRS and targeted datapoint changes.

As at 1 August 2026, C(2026) 5011 was Commission-adopted but not yet in force. Teams should therefore keep EFRAG 2024, Recommendation 2025 and the 2026 delegated-act text as distinct controlled source versions.

Why the transition needs careful handling

Organisations that began with VSME may already have templates, data requests, software fields, customer responses and training materials. Because the 2026 text deliberately preserves the modular architecture, the transition can look deceptively simple. The risk is not wholesale redesign; it is hidden version drift. A familiar disclosure number may contain changed wording, a datapoint may move modules, or a customer may continue to request an old field that is no longer part of the statutory cap.

The safest transition separates three questions: which document governed the previous report, which document is current on the next approval date, and which source controls the legal request limit. The answers can differ during the scrutiny and entry-into-force period.

Quick orientation

Applies to
Undertakings, advisers and data users moving from EFRAG VSME or Recommendation 2025/1710 to the Commission-adopted 2026 text.
Primary decision
Which source is current, what changed in architecture and datapoints, and how to transition without losing evidence or overstating legal status.
Key sources
EFRAG VSME December 2024, Recommendation (EU) 2025/1710, C(2026) 5011 and Directive (EU) 2026/470.
Common confusion
“VSME” is often used as a generic label, but the historical technical standard, Recommendation and delegated regulation are not interchangeable.

1. The source timeline: historical, intermediary and Commission-adopted

Figure 1. Version timeline from the EFRAG VSME standard to the Commission-adopted 2026 delegated act.

In practice

Source Status at 1 August 2026 Correct editorial use — Do not treat as
EFRAG VSME, December 2024 Historical technical standard submitted to the Commission. Source for development history, prior templates and detailed practical guidance. — An EU delegated regulation or current legal cap.
Recommendation (EU) 2025/1710 Commission recommendation endorsing VSME; non-binding. Intermediary voluntary basis until the delegated act enters into force. — A mandatory reporting law.
C(2026) 5011, adopted 3 July 2026 Commission-adopted delegated act under scrutiny; not yet in force. Primary forward-looking source for transition design, with visible status caveat. — An already applicable final OJ regulation.
Final OJ regulation Future current legal instrument after scrutiny and publication. Final source for compliance wording, effective dates and cap operation. — Identical by assumption to the pre-OJ text; recheck final numbering and corrections.
Consultation drafts / revised ESRS placeholders Draft or supporting materials. Explain development and resolve comments where relevant. — The final governing source.

2. What stayed the same

A two-module architecture: Basic B1-B11 and Comprehensive C1-C9.

The Basic Module remains the target approach for micro-undertakings and a prerequisite for Comprehensive reporting.

Option A is Basic only; Option B is Basic plus Comprehensive.

The report remains designed principally for business counterparties, banks and investors, with optional public publication.

The Standard still combines impact information and information about how environmental and social issues may affect financial position, performance and cash flows.

The “if applicable” principle, comparative information from the second year, individual or consolidated reporting and links to financial statements remain central preparation features.

EFRAG practical guidance and templates remain relevant as implementation support, subject to version alignment.

This continuity is valuable. A well-designed VSME source register, evidence archive, calculation workbook and owner model can usually be migrated rather than discarded. The transition should therefore preserve stable data lineage and change only the requirement mapping and report outputs that need to change.

3. What changed at framework level

Figure 2. Selective comparison of the 2025 VSME basis and the Commission-adopted 2026 Voluntary Standard.

In practice

Dimension Earlier VSME / Recommendation position 2026 Commission-adopted position — Transition action
Legal vehicle EFRAG technical standard endorsed by non-binding Commission Recommendation. Delegated regulation intended to be binding and directly applicable after scrutiny and OJ publication. — Update legal status, references and basis-of-preparation wording only when the act enters into force.
Application timing Recommendation available as a voluntary basis before the delegated act enters into force. The Regulation enters into force on the third day after OJ publication; Article 3 cap applies for financial years beginning on or after 1 January 2027. — Separate adoption date, entry into force and cap application date in the transition register.
Target population Originally designed for non-listed SMEs and framed through the SME context. Annex I states it is intended for undertakings with no more than 1,000 average employees in the preceding financial year; Article 2 addresses undertakings outside Articles 19a/29a. — Reperform eligibility and intended-user assessment.
Value-chain function Voluntary common data set and policy expectation to limit requests. Formal statutory cap mechanism for protected undertakings, with Annex II listing the cap datapoints. — Separate report mapping from request-cap mapping.
Micro proportionality No dedicated legal table distinguishing undertakings with 10 employees or fewer. Specified datapoints are voluntary for ≤10 employees; Annex II has separate cap columns. — Add employee-band logic to templates and request tools.
Alignment Aligned to 2023 ESRS and EU sustainable-finance needs. Targeted alignment with the revised ESRS; Commission says datapoints were reduced. — Recheck field definitions, source mappings and interoperability claims.
Supersession Recommendation 2025/1710 was the Commission-endorsed voluntary basis. From entry into force, the Recommendation is to be considered no longer producing legal effects. — Set a trigger to archive rather than silently delete historical references.
Assurance VSME did not impose a general assurance obligation. Recital 5 expressly notes that undertakings applying the Standard are not obliged to seek assurance. — Retain voluntary assurance/readiness options without presenting them as a requirement.

4. Selected datapoint and drafting changes

The following list highlights changes that are especially likely to affect existing templates. It is a practitioner transition summary, not a substitute for a paragraph-by-paragraph redline. The final Official Journal version and EFRAG implementation materials should be used to confirm every field before publication.

In practice

Area Earlier VSME pattern 2026 change or emphasis — System impact
B1 basis Module choice, classified/sensitive-information omission, individual or consolidated basis and entity master data. Retains the core entity and subsidiary fields, adds an explicit compliance statement for the selected option, and replaces the narrower omission rule with paragraph 22 categories, disclosure of each omission and annual reassessment. — Update the basis-of-preparation statement and omission register; retain rather than rebuild stable entity master data.
B3 energy and GHG Energy, Scope 1, Scope 2 and an intensity calculation were commonly mapped. Requires total energy and, where available, renewable/non-renewable breakdown; absolute Scope 1 and location-based Scope 2. The prior intensity field is not retained in the same mandatory form. — Retire or relabel old intensity field; keep it only as additional information if useful.
B5 biodiversity Number and area of sites in or near biodiversity-sensitive areas, plus optional land-use metrics. Replaces the number/area and optional land-use fields with an if-applicable disclosure of the sites or locations and the name of the biodiversity-sensitive area. — Retain geospatial evidence, revise the output fields and archive superseded area calculations rather than presenting them as required.
B6 water Withdrawal/consumption and contextual information. Water consumption applies when production processes significantly consume water, with separate consumption at water-stressed sites; specified datapoints are voluntary for ≤10 employees. — Add production-process and water-stress flags.
B7 waste/circularity Waste, recycling/reuse and material flows. Adds an explicit proportion of waste diverted to recycling or preparation for reuse; many fields are voluntary for ≤10 employees. — Update waste denominator and employee-band rules.
B8/C5 workforce Turnover appeared in the Basic workforce area in earlier mapping. Employee turnover is now C5; B8 focuses on employees by contract, gender and country. — Move field to Comprehensive mapping and prevent duplicate disclosure.
B10 remuneration/training Pay gap, bargaining and training with broader data expectations. Gender pay gap is reported if already required by EU or national law; training is average annual hours per employee without the same gender split. — Add legal-applicability flag and update training calculation.
C1 business model Business model, markets and relationships. Specified C1 fields are voluntary for ≤10 employees. — Build micro relief into questionnaire logic.
C3/C4 climate Targets, transition and climate risks. Several climate disclosures are expressly voluntary for ≤10 employees; Scope 3 remains an additional relevant disclosure depending on activities. — Separate essential, conditional, voluntary and micro-voluntary statuses.
C8 activities Certain revenues plus benchmark-exclusion information in prior VSME. Focuses on revenues from prohibited weapons, tobacco, fossil fuels and specified chemicals production. — Review sensitive-activity taxonomy and delete obsolete response fields only after controlled change approval.

5. The value-chain cap is the biggest legal change

Under the 2026 framework, the Standard is not only a reporting option. It also sets the reference level for protected-undertaking requests. Yet the cap is deliberately narrower than the complete Standard. Only essential datapoints listed in Annex II form the upper limit, with different columns for undertakings with more than 10 employees and those with 10 or fewer. Voluntary, conditional and sector-specific fields may therefore sit outside the cap even when they remain available in Annex I for a voluntary report.

In practice

Transition test Why it matters
Does the old supplier questionnaire contain fields not in Annex II? Those fields may be above the statutory cap for qualifying Accounting Directive reporting requests.
Does the requester need every Annex II field? The delegated act says requesters should ask less where they do not need the full list.
Is the request for Accounting Directive reporting or another purpose? The cap only applies to the specified reporting purpose; due diligence, credit and other purposes need separate analysis.
Is the supplier ≤10 employees? Use the narrower Annex II column and the related micro reliefs.
Has the supplier self-declared its size? The requester may rely on the declaration unless it is manifestly incorrect.

In practice

6. A controlled transition workflow

Step Action Evidence retained
1 Freeze the source set used for the last report and label it EFRAG 2024, Recommendation 2025 or another controlled version. Prior report, source list, template version and approval date.
2 Build a change register at paragraph and datapoint level; do not compare titles only. Old/new reference, change type, owner, impact and decision.
3 Reperform eligibility, group boundary and employee-band assessment. Scope memo, headcount calculation and group chart.
4 Split reporting requirements from Annex II cap datapoints. Two mappings with different purposes and statuses.
5 Update data requests, calculations, evidence and controls. Revised source register, calculation methods and test scripts.
6 Review report wording, module statement, omission wording and status notice. Redlined draft and legal/technical review comments.
7 Update customer and bank response packs, software fields and AI retrieval records. Versioned outputs and deprecation log.
8 Release only after the legal status and final OJ text are confirmed. Final sign-off, publication note and supersession record.

7. Hypothetical transition case

The team retains its reliable energy, emissions, workforce and governance data but remaps the report to the 2026 adopted text. GHG intensity becomes optional additional information rather than a required B3 field. Employee turnover moves to C5. The bank questionnaire is split into Annex II cap fields, other voluntary-standard fields and bank-specific credit fields. The company does not claim that the delegated regulation is already in force; it states that the report is prepared using the Commission-adopted text as a transition basis and will be revalidated after Official Journal publication.

The transition succeeds because it preserves data lineage while changing the requirement layer. It also avoids the common error of treating the full Annex I report, or an old bank questionnaire, as the statutory cap.

In practice

8. Weak versus stronger transition wording

Weak wording Why weak Stronger pattern
“We report under the new mandatory VSME 2026 standard.” It incorrectly describes a voluntary, not-yet-in-force delegated act as mandatory. “This report uses the Commission-adopted 2026 Voluntary Standard as a transition basis. The act was pending scrutiny and OJ publication at the approval date.”
“Nothing changed except the legal name.” It hides changed scope, cap operation, micro relief and datapoints. “The modular architecture is retained, but the entity has revalidated eligibility, datapoint mappings, micro reliefs and Annex II request controls.”
“All old VSME fields remain required.” It converts legacy template content into current obligations. “Legacy fields are retained only where required by the 2026 text or useful as clearly labelled additional information.”
“The customer cannot request more than the report.” The cap is Annex II, purpose-specific and not the whole report. “For qualifying Accounting Directive requests, above-cap items are assessed against Annex II and the protected-undertaking rules.”

9. Common mistakes

Replacing every occurrence of “VSME” with “EU Voluntary Standard” without reviewing the underlying paragraph.

Using a consultation draft or an EFRAG presentation as if it were the Commission-adopted legal text.

Deleting legacy datapoints without considering whether a bank, customer or internal manager still needs them as additional information.

Treating the full Basic or Comprehensive Module as the statutory value-chain cap.

Applying the >10 employee Annex II column to an undertaking with 10 employees or fewer.

Claiming that Recommendation 2025/1710 ceased to matter before the delegated regulation entered into force.

Updating the report PDF but leaving old fields in customer portals, AI Assistant knowledge, spreadsheets or training materials.

Readiness

10. Transition checklist

  • The last report's source version and approval date are identified.
  • A paragraph-level change register exists.
  • Current legal status and OJ publication have been checked.
  • Eligibility and intended-user tests have been rerun.
  • The Basic/Comprehensive module statement is still accurate.
  • Fields for undertakings with 10 employees or fewer are correctly classified.
  • Annex I reporting fields and Annex II cap fields are stored separately.
  • Moved, removed and modified datapoints have controlled migration rules.
  • Legacy additional information is clearly labelled rather than presented as required.
  • All templates, portals, mappings, visuals, FAQs and AI records use the same current source set.
  • Recommendation 2025/1710 is retained as historical evidence and superseded only at the correct trigger.
  • A final technical reviewer has approved the transition statement.

Recommendation (EU) 2025/1710 is not simply obsolete: it remains an Official Journal recommendation and has not been expressly repealed. The 2026 delegated regulation creates a distinct, newer source and timetable, so teams should identify which text and reporting period they are using rather than merge the two versions.

Questions

Questions people ask

Did the 2026 Standard replace the VSME architecture?

The 2026 EU Voluntary Standard is not a wholly new architecture: it is based on the VSME standard endorsed by Commission Recommendation (EU) 2025/1710 and retains the Basic B1-B11 and Comprehensive C1-C9 modules. The main changes are its proposed legal form and role, the wider intended population up to 1,000 employees, a statutory value-chain cap defined through a separate Annex II, specific reliefs for undertakings with 10 employees or fewer, alignment with the revised ESRS and targeted datapoint changes.

Is Recommendation (EU) 2025/1710 already obsolete?

Recommendation (EU) 2025/1710 is not simply obsolete: it remains an Official Journal recommendation and has not been expressly repealed. The 2026 delegated regulation creates a distinct, newer source and timetable, so teams should identify which text and reporting period they are using rather than merge the two versions.

Do companies need to rebuild all VSME data?

A well-designed VSME source register, evidence archive, calculation workbook and owner model can usually be migrated rather than discarded. The transition should therefore preserve stable data lineage and change only the requirement mapping and report outputs that need to change.

Is this article a complete legal redline?

The following list highlights changes that are especially likely to affect existing templates. It is a practitioner transition summary, not a substitute for a paragraph-by-paragraph redline.

Sources

Primary sources

Take it with you

The checklists as a working spreadsheet

Every checklist and table on this page, with empty status, owner and evidence columns for your team to fill in and keep.

Download .xlsx

✓ LRA AI Assistant · Human-in-the-loop

Ask about this guide

It answers from this page, and reaches into the linked disclosure cards when your question is about the standard itself. Your first two answers are free without signing in.

Try
2 free answers Automated · the LRA team is one click away

Go deeper · EU Voluntary Standard 2026

Available as Guided Flex, Live Cohort, 1:1 Expert Mentorship or Corporate Programme.

See course formats
/en/knowledge-hub/disclosure-guides/eu-voluntary/eu-voluntary-preparing-the-report/eu-voluntary-standard-2026-vs-vsme/