CSRD in English: translation risk, audit liability, and the workflow IR teams need

If your company files a CSRD sustainability statement in German and also publishes an English version, you now own two legal documents, not one document and a translation. Most IR teams I work with haven’t been told that. Here’s what it means for compliance, for your auditor, and for the workflow you need before the next reporting season.

1 · The 2026 mid-cap wave—and why English suddenly matters

The Omnibus I Directive, approved by the Council on February 24, 2026, cut the CSRD population hard. The European Commission now estimates that around 5,000 companies in the EU will remain directly obligated—instead of the original 50,000. Listed SMEs are fully exempt. The new gate is a dual threshold: only large undertakings with more than 1,000 employees and net annual turnover above €450 million must report.

That sounds like relief, and for the smallest filers it is. But the companies that stay in scope are precisely the ones for whom English was never optional in practice. They hold ADR programs, they carry Euronext or dual listings, and their register of institutional shareholders reads in three or four languages. For an issuer like that, a German-only disclosure is legally conceivable and functionally impossible—the analysts covering the stock read the English version, and so does the machine layer. The official ESRS XBRL taxonomy uses English element names, which means the digitally tagged skeleton of every CSRD report already has an English reference point baked in, whatever language the prose is written in.

2 · Is an English translation legally required?

There is no blanket EU mandate for English. The CSRD delegates language to national law. As one practitioner FAQ drawing on the Commission’s own guidance puts it, the sustainability statement “must be drafted and published in a language specified by the laws of the relevant Member State.” In Germany, the management report—which now carries the sustainability statement—may be published in German or English. So a stand-alone English statement is a permitted choice for many German filers, not a mere add-on.

Capital-market issuers face a second layer. The Transparency Directive (Article 20) requires that where securities trade on a regulated market only in the home Member State, regulated information be disclosed “in a language accepted by the competent authority in the home Member State.” Where securities are also admitted elsewhere, the issuer must additionally use a host-state language or “a language customary in the sphere of international finance”—which in EU supervisory practice means English. The annual financial report, and therefore the sustainability statement inside it, is regulated information.

3 · What publishing an English version actually triggers

CSRD assurance has a defined perimeter. The CEAOB’s September 2024 interim guidelines state that the limited assurance report addresses “(i) the sustainability statement with regards to the relevant legal requirements, i.e. the ESRS…; (ii) the information provided to address Article 8 of the Taxonomy Regulation; and (iii) a mark-up of the sustainability statements with regards to EU digitalisation requirements.” Read that carefully: the auditor opines on the filed statement. A voluntarily published English translation sits outside that perimeter unless it is itself the filed document.

This is where parallel disclosure bites. Once you circulate an English version to capital markets, you have made a public representation. The auditor’s limited assurance did not test it. If the English wording differs materially from the assured German original—on a forward-looking commitment, an ESRS classification, or a number—an investor relying on the English text has no auditor-backed accuracy guarantee, and the discrepancy is yours to explain. This is a structural inference, not settled doctrine; regulators are only beginning to address it. But the logic is not complicated, and it leads to the one sentence your board should hear:

In a regulated CSRD disclosure, the English version is not a courtesy translation—it is a parallel representation of a legal document. A material discrepancy between language versions is a disclosure risk, regardless of which version the auditor examined.

4 · What counts as a material translation error

Not typos. Reviewers catch typos. The errors that create disclosure exposure are the ones that read fluently and shift meaning. Four patterns come up repeatedly in sustainability statements:

• A figure that moves on rounding convention. German uses the comma decimal and often rounds to a different place. A Scope 1 emissions total that reads 1.234 in one version and 1,234 in the other is not a translation—it’s a three-order-of-magnitude discrepancy waiting for a footnote.
• A forward-looking statement hedged differently. German “wir werden” is a commitment; rendered as “we aim to,” it becomes an aspiration. The reverse is worse—turning an aspiration into “we will” manufactures a promise the board never approved.
• A regulated ESRS term rendered with a looser equivalent. ESRS vocabulary is defined vocabulary. Translating Wesentlichkeitsbewertung as “importance assessment” instead of the approved “materiality assessment” quietly detaches your text from the standard.
• A Scope 3 commitment softened by idiomatic English. Value-chain language is where the most careful drafting lives; an idiomatic smoothing that drops a qualifier can widen or narrow a stated boundary.

That the standards themselves are vulnerable here is not speculation. The German version of ESRS Set 1 needed a full corrigendum, published in the Official Journal on August 9, 2024, and several changes were substantive: “potenzielle finanzielle Auswirkungen” became “erwartete finanzielle Auswirkungen” (potential → expected), and ESRS G1 was renamed from Unternehmenspolitik to Unternehmensführung. If the official reference text can drift that far, so can yours.

5 · The ESRS terminology governance problem

The translation specifics—which English equivalent maps to which ESRS term—I’ve covered elsewhere. The harder problem is governance: who owns the mapping, and what happens when the standard moves under you. And it does move. After the August 2024 corrigendum, Germany’s DRSC and Austria’s AFRAC conducted a further systematic review and submitted a list of terms that “could be translated more precisely or that have not been translated consistently throughout the ESRS.” The authoritative German standard-setters are telling you the German reference text is not stable across cycles.

On top of that, Omnibus I brings a 61% cut in mandatory datapoints—from roughly 1,100 to about 430—with revised standards expected to apply from financial year 2027. Any English termbase built against the full original set is about to be partly obsolete. So the governance question is not academic. It is: which version of which term did we approve, and can we prove it?

In three of my last eight sustainability report commissions, the client had no record of which English equivalent was approved for Wesentlichkeitsbewertung in the prior year. Nobody had signed off on it; it had simply carried over. That’s the gap that turns a routine update into a three-week revision round—and the one an auditor’s question exposes fastest.

6 · Four governance checkpoints for a dual-language disclosure

Each of these prevents a specific, recurring failure. None is expensive. All are skipped under deadline pressure.

1. Source lock. No edits to the German source after translation begins. Prevents the most common defect I see—a CFO’s last-minute change that lands in the German file and never reaches the English one, so the two versions diverge at the finish line.
2. Subject-matter review. The reviewer must understand IFRS and ESRS, not just English. Prevents a fluent, wrong rendering of a defined term surviving because the only checker read for grammar.
3. Parallel sign-off. Both language versions approved simultaneously, not sequentially. Prevents the German version being finalized and filed while the English is still in draft, which guarantees a gap no one is accountable for.
4. Dual-version archiving. Both stored with identical metadata for the audit trail. Prevents the English version existing only as an emailed PDF—untraceable, unversioned, and impossible to reconcile when a regulator asks which text was public on which date.

7 · Briefing a specialist translator—the package that prevents revision rounds

Most revision rounds are caused before the translation starts, by an incomplete brief. Send me these five things up front and you remove the usual failure points:

• The prior year’s approved English version—so continuity of wording is deliberate, not accidental.
• The approved termbase export (Trados .sdltb or Across)—the actual mappings, not a memory of them.
• The current ESRS reference glossary—post-corrigendum, so we’re not building on obsolete source terms.
• The name of a single internal reviewer with ESRS knowledge—one accountable person, not a distribution list.
• A realistic timeline that ring-fences review time separately from translation time—review is not a rounding error at the end.

For scale: a typical CSRD sustainability statement runs roughly 5,000 to 18,000 words depending on company size and the breadth of the materiality scope. Priced at my standard specialist rate of €0.85 per standard line (a standard line is 55 characters including spaces—the German-market unit many English readers won’t know), repetitions and 100% matches from a well-maintained termbase fall to €0.17 per line (high-fuzzy matches, €0.51), which is exactly why the termbase export in the brief pays for itself. The math rewards governance.

8 · From 17 years of reporting seasons—what actually goes wrong

I’ve been translating full-time since 2008, across more reporting seasons than I care to count, much of it for DAX- and MDAX-adjacent clients I can’t name. The failures are boringly consistent. They are almost never linguistic.

• The source document arrives after internal approval—carrying last-minute CFO edits that were never flagged, so the English is faithful to a version that no longer exists.
• No internal reviewer is assigned until three days before filing, at which point review becomes a formality performed by whoever is free.
• The English version is treated as a “nice to have” PDF—not filed, not archived as a document version, so there’s no record of what was public.
• The previous year’s English text is used as the working source instead of the current German—quietly reintroducing last year’s language into this year’s disclosure.

None of these is a translation problem. Every one of them is a workflow problem that lands on the translation, because that’s the last station before the document goes out.

9 · The one claim to take to the board

For context on the stakes: Member State penalties for CSRD non-compliance can reach €10 million or 5% of annual turnover, alongside public naming and exclusion from public tenders. Translation quality is not itself the filing offence—but a materially incorrect English version circulating in the capital market while the compliant German version sits in the register is a disclosure-parity exposure that securities regulators and auditors are only starting to examine.

So here is the sentence your legal, IR, and sustainability teams can align on: the English version of a regulated CSRD disclosure is a parallel legal document, and any material discrepancy between the language versions is a disclosure risk in its own right—no matter which version the auditor read.

The practical response isn’t to buy more translation. It’s to treat the two versions as one governed disclosure: lock the source, assign one ESRS-literate reviewer, sign both off together, and archive both with matching metadata. If you want a translator inside that workflow rather than bolted onto the end of it, that’s the conversation to have—the services page lays out how I price it, and you can send me the brief before the season starts, not during it.