Here is a sentence I could have lifted from a dozen management commentaries this reporting season. Anonymised, lightly paraphrased, but structurally real: “Unser Compliance-Framework stärkt die Performance und schafft Vertrauen bei allen Stakeholdern.” In German it reads cleanly. A board member signs it off without a second thought. Then it lands, word-for-word, on a London analyst’s desk as “Our compliance framework strengthens performance and builds trust among all stakeholders,” and something is quietly wrong—not ungrammatical, just off by a few degrees in every load-bearing noun.
That gap is the subject of this article. The failure most IR teams worry about is a mistranslation: a number transposed, a term garbled. The failure I want to name is upstream of that. It’s in the source. When the German draft borrows English words—Compliance, Performance, Governance—those words carry subtly German meanings. A translator who is genuinely at home in both languages can see the gap. A translator who isn’t will close it invisibly, in the wrong direction, and produce English that sounds native and means something the German author never intended.
What Denglish in corporate communication is—and what it isn’t
Duden, the standard German reference, defines Denglisch as a pejorative label for German with too many English expressions mixed in; the word was first recorded in German back in 1965, well before the business-anglicism wave of the late 1980s accelerated it. That’s the register we’re in—but the annual-report problem is narrower and more dangerous than “too many English words.”
Some English in a German financial statement is entirely legitimate. IFRS, ESRS, and the ESG acronym stack (GRI, SASB, TCFD, the EU Taxonomy) are technical vocabularies that exist to be used precisely. “Scope 3 emissions” is not Denglish; it’s a defined term. The problem I’m describing is different: the systematic adoption of English-shaped words that have quietly acquired German-inflected meanings. The word looks English, so nobody flags it for translation—and that’s exactly why it survives the round trip intact and wrong.
The scale isn’t hypothetical. Deutsche Bahn—a company whose own name is German—found its internal language so saturated with anglicisms that in June 2013 it issued a directive and glossary of 2,200 English terms to be replaced with German ones. If a state railway needs a 2,200-word counter-directive, the systematic version of this problem is real, and DAX and MDAX management commentaries are where I see it concentrated: strategy sections, governance chapters, and sustainability narratives.
Category one: governance pseudonyms
Start with the governance layer, because it’s where the loan-words look most harmless. “Compliance” in a German IR text usually points at the internal rule-adherence function—the department, the framework, the sign-off process. An English reader hears “compliance” and reaches first for regulatory conformance with external law. Overlapping, not identical. “Stakeholder” in German corporate usage has drifted toward “any interested party we’d like to sound inclusive about”; the English term still carries a sharper claim about who has legitimate standing. Translate each literally and you get a sentence that is grammatically flawless and semantically fuzzy to the one reader who matters.
The clearest case is the calque that sounds English but isn’t used in English at all. The Vier-Augen-Prinzip is bedrock German audit and governance vocabulary. Rendered literally as “four-eyes principle”—a term specialist financial-translation guidance calls “a questionable but widely accepted term in German”—it means nothing to a London auditor. There is no four-eyes principle in English. The idiomatic renderings are “double-checked” or “third-party review.” A translator who has absorbed the German phrase as if it were already English will hand it straight through, and the report now contains a governance term no English-speaking auditor uses.
Category two: the round-trip IFRS problem
The financial notes carry a subtler version. Much IFRS vocabulary was coined in English, absorbed into German accounting practice with slight drift, and then gets re-translated back into English for the annual report. Each leg of that round trip introduces a small error. In an audited financial statement, small errors are not small.
The equivalence problem is documented, not folklore. The Wiley bilingual EU IFRS edition states plainly that the German translation is “in some places inexact or even wrong,” and practitioners surveyed on the point conclude that “exact equivalence cannot be achieved”—translators are forced into interpretation rather than word-for-word conversion. This is the official standard, not a marketing brochure, conceding that the German and English texts don’t fully line up.
A concrete instance: in IAS 32, paragraph AG 19, the English lists “interest rate and currency swaps, interest rate caps, collars and floors.” The German official text lists only “Zins- und Währungsswaps, Collars und Floors”—interest rate caps is gone. A German drafter reading the standard in German never sees the concept. Any commentary written against that German text, then translated back into English, cannot reintroduce a term that was never in the author’s source. The information didn’t get mistranslated; it evaporated one leg earlier and the translation faithfully preserved the hole.
Then there’s the term specialist translators call possibly the hardest in the whole report: Abschreibungen. One German word; three English words depending on the asset. Tangible assets take “depreciation,” intangibles take “amortisation,” and a value decline is an “impairment loss.” German further splits planmäßig from außerplanmäßig where English just changes the verb. A translator who has internalised Abschreibungen as a single lump, without checking asset class each time, will systematically misrender it—and it will read fluently while doing so.
Compounding all of this, IFRS itself is, in the standard-setters’ own words, a work in progress. “Balance sheet” became “statement of financial position”; “income statement” became “statement of comprehensive income.” A German drafter working from an older German-language version, and a translator working from that draft, can faithfully perpetuate English terminology that the standard retired years ago.
Category three: strategy-layer Denglish
The strategy chapter is written by different people—often senior management, not linguists—and it imports consulting English wholesale. “Footprint,” “roadmap,” “full potential,” “rollout”: these settle into German strategy prose and pick up German-inflected readings. In my experience a “Footprint” in a German strategy section usually means operational presence, not the geographical-or-carbon sense an English reader defaults to; a “Roadmap” is invoked as aspiration far more loosely than the fixed-timeline document the English word implies. I flag those as practitioner observation, not documented fact—but the mechanism is the same one that is documented elsewhere.
Because the documented pseudo-anglicisms are unambiguous. In German marketing, a company’s Claim is what English calls a slogan or tagline. In English, “claim” is primarily legal or insurance vocabulary—an assertion you can be held to. Translate a German strategy line about the company’s “Claim” literally and you’ve told an institutional reader the company is making an evidentiary or legal assertion, the exact opposite of the branding register intended. The same source notes Fotoshooting collapsing to “shooting” in English, where the word means gunfire, not photography. These aren’t edge cases; they’re the everyday texture of anglicised German.
Even the ordinary embedded terms—Marketing, headhunter, soft skills, outsourcing, benchmarking, networking—are, as one specialist puts it, “by no means ‘no-brainers’.” Each demands a judgment call about whether to keep the English form or substitute a German-resonant equivalent, precisely because the term’s meaning in German usage has drifted from its source. Annual reports straddle the legal-financial register (where anglicisms are rare and precision is everything) and the strategy register (where they run riot), which is what makes them such high-risk documents.
Why internal review doesn’t catch it
Here’s the structural reason Denglish survives to filing. Your German-speaking editors read straight through it—the anglicised register is their register, so nothing trips the alarm. Your English-only proofreaders can’t catch it either, because they never see the German source; they’re checking whether the English reads well, and calqued English often reads beautifully. Both quality gates are staffed by people who, by design, cannot detect this specific fault.
So the problem surfaces at the worst possible moment: when an English-speaking investor, analyst, or auditor asks what a sentence actually means—usually after the report is filed. ESG translation guidance makes the same point from the other side: a term can be “technically correct,” but if the sentence around it “sounds too promotional, too cautious or too literal,” the report still sends the wrong signal. A native-speaker reviewer who hasn’t read the German can’t tell principled English from calqued English. They look identical on the page. That’s the whole trap.
What this means for your translation brief
The practical takeaway for IR teams and LSP project managers is that “translate, then have a native speaker check it” is not a safety net for Denglish. It fails by construction, because the checker is looking at the output with no access to the input. If you want this caught, it has to be caught by someone reading the German and the English at the same time, holding both meanings in view.
Concretely: mark the Denglish-heavy sections of the German draft—strategy, governance, sustainability—as needing meaning-level review, not just fluency review. Put the entity’s key loan-words in the terminology brief with the intended sense spelled out: what does this company mean by Compliance, by Performance, by its Claim? And keep an approved bilingual glossary. Specialist LSPs store client-preferred terms in a dedicated database precisely so the same concept renders the same way every cycle; ESRS compliance leans on official EU terminology too. Without that glossary, every translator rebuilds the mapping from scratch and the drift resets each year.
It’s worth being honest about scarcity here, because it raises the stakes on the brief. In one specialist LSP’s estimation, of the tens of thousands of freelancers in the German-English pair, those who combine genuine accounting knowledge with translation skill for IFRS reports number “just under 100.” That’s a practitioner estimate, not a census—but it matches what I see. The pool that can catch this fault is small, and machine translation doesn’t fill the gap: the same practitioners describe it as inconsistent in language and unreliable on formatting.
The bilingual advantage: two instincts running at once
This is where I’ll get personal, because the mechanism matters more than any procedure. I grew up with both languages—German father, American mother—and have translated full-time since 2008, across more than 7,000 jobs. The relevant fact isn’t fluency. It’s that neither language is decoded through the other. I don’t read German and convert it to English; I read German as German and English as English, and both instincts are live at the same time.
What that buys you is early warning. A calqued sentence feels wrong before I can articulate why. “Four-eyes principle,” “the company’s Claim,” Compliance-doing-work-it-doesn’t-do-in-English—these register as friction the instant I read them, the way a wrong note registers before you’ve named the interval. That’s not a quality-assurance step I run at the end. It’s the perceptual baseline I read from. It’s also, honestly, the closest thing I have to an explanation for consistency across thousands of reports: not a longer checklist, but two language instincts that won’t let a calque pass unnoticed.
Five signals in the German draft that predict Denglish risk
You can screen for exposure before the German is even finalised. If a section shows several of these, budget for meaning-level bilingual review, not a fluency pass:
- Strategy or governance sections drafted by non-linguist senior management—the register where consulting English enters unfiltered.
- The source uses English-origin words in German inflected forms: “die Stakeholder,” “unser Compliance-Framework,” “gerollt out.” Inflection is the tell that the word has been naturalised—and naturalised words don’t get flagged for translation.
- IFRS note language copied from an earlier English version and re-translated into German—the round trip, with all its documented drift and possibly superseded terminology.
- A sustainability narrative written to a GRI or ESRS template with English section titles, where the whole text environment is saturated with anglicisms.
- No approved bilingual glossary exists for the entity, so every translator rebuilds the term mapping alone and last year’s decisions are lost.
Source-text quality is a project risk—treat it like one
Denglish in the German source belongs on the annual-report risk register alongside missing data and late sign-off. It’s a workflow item, not a stylistic footnote, and it’s one of the few risks you can retire cheaply: it costs almost nothing to flag the high-risk sections and name the loan-words while the German is still editable, and it’s expensive to fix after an analyst has already read the wrong meaning.
So one concrete ask: share the five-signal checklist above with whoever owns the German draft, before it’s locked. If you’d rather have someone read the German and the English together from the start—the only workflow that actually catches this—that’s the work I do. You can see how I price and scope specialist financial translation, or just send me the risky sections and I’ll tell you where the source is going to cost you.