ESRS-40a consultation: how non-EU groups can plan their feedback

Practical guide · Educational reading

EFRAG’s ESRS-40a cost-benefit survey and technical consultation have different deadlines. Here is how potentially affected non-EU groups can organise their review.

Audience / jurisdiction: European Union reporting context; sustainability, finance and compliance teams at potentially affected non-EU undertakings

Keep the two feedback deadlines separate

For non-EU groups assessing EFRAG’s proposed sustainability reporting standards, two feedback routes need to be kept separate: the cost-benefit survey and the technical consultation on the exposure draft. EFRAG’s opened news index lists a 9 October 2026 announcement extending the ESRS-40a cost-benefit survey deadline to 18 October 2026. Its project page gives 31 October 2026 as the closing date for the broader technical consultation.

The distinction matters when allocating internal review time. A team preparing evidence about likely reporting costs should not assume it has until the end of October to complete the survey. Equally, the survey extension should not be read as a new deadline for every part of the consultation. This guide explains how potentially affected teams can organise their review without treating consultation dates as reporting obligations.

Sources: [2], [1]

Understand the proposal’s status

The project concerns the Exposure Draft ESRS for Certain Non-EU Undertakings, referred to as ESRS-40a. EFRAG’s project information places it in the context of Article 40a of the Accounting Directive and describes a technical consultation running from 23 July to 31 October 2026. EFRAG develops technical advice for the European Commission; the material under consultation remains a proposal.

For practitioners, that status is an important boundary. The consultation is an opportunity to examine proposed reporting requirements, not evidence that a final standard has been adopted. Neither the survey deadline nor the technical consultation closing date should be entered in a compliance register as a legal effective date. The opened evidence does not establish a change to mandatory reporting commencement or a transition timetable.

Sources: [1]

Prepare a coordinated internal assessment

EFRAG’s project page distinguishes the cost-benefit exercise from the technical consultation. Teams can mirror that separation in their internal work: one review can consider anticipated implementation effort and benefits, while another examines the proposed reporting content. These are suggested ways to organise a response, not additional requirements imposed on organisations.

For example, sustainability staff could identify where proposed disclosures would draw on existing information. Finance colleagues could help distinguish recurring work from one-off preparation. Compliance colleagues could record questions that require a separate legal scope assessment. Where teams develop estimates, a useful approach is to state assumptions and distinguish measured experience from forecasts. This avoids presenting a preliminary judgement as a settled implementation cost.

Sources: [1]

Check the current deadline before submitting

There is a visible deadline inconsistency in the supplied opened evidence: the project page retains 11 October 2026 for the cost-benefit survey, while the news index lists the newer extension announcement specifying 18 October. The later dated announcement is the basis for the extended date reported here. The technical consultation remains a separate entry closing on 31 October.

Before scheduling a submission, teams should check EFRAG’s current information and the survey itself. Do not assume a closing time or time zone for 18 October from an earlier notice. It would also be sensible to allow time for internal approval rather than planning around an unverified final-hour cutoff. These are practical precautions, not issuer instructions.

Sources: [2], [1]

Separate participation from compliance planning

The intended audience is teams evaluating the proposals for certain non-EU undertakings in an EU reporting context. This is not a blanket statement that every non-EU business must comply. An organisation’s legal applicability assessment should remain separate from its decision to review the draft or contribute feedback.

A proportionate next step is to assign an owner, confirm which feedback route is relevant and record unresolved questions. Keep consultation activity distinct from implementation commitments until the applicable legal position and final reporting requirements have been checked.

Sources: [1]

Sources

1. ESRS for Certain Non-EU Undertakings in Accordance with Article 40a of the Accounting Directive | EFRAG
2. News | EFRAG

Your experience

How is your team separating implementation-cost estimates from technical feedback on the proposed reporting requirements?