Three jobs, one week, three different flavors of English. That’s a normal reporting season. The German words repeat—Bilanz, Gewinn- und Verlustrechnung, Eigenkapital—but the correct English changes depending on one thing the file itself rarely states: which accounting standard produced it.
Three jobs, one week, three answers
Here is what actually landed on my desk during one recent season, anonymized past recovery. Monday: an HGB-Einzelabschluss for a mid-sized GmbH, needed in English for a foreign parent’s files. Wednesday: the IFRS-Konzernabschluss of a listed group, the glossy investor-relations version. Friday: a chunk of a US-GAAP reporting package from a German subsidiary feeding into an American parent’s SEC filing. Same translator, same language pair, three different sets of terminology—and if I’d rendered all three the same way, at least two of them would have been wrong.
The reason isn’t stylistic taste. Each of those documents was built under a different accounting framework, and each framework carries its own English vocabulary—one prescribed by a standard-setter, one inherited from British market convention, one American. So the practical question I ask before I translate a single line is not “how should this sound?” It’s “which rulebook produced this?” Get that wrong and the terminology follows you into an audited document, where it’s read by exactly the people trained to notice.
HGB in English: the standard with no official glossary
Start with the hardest case, because it’s the one people underestimate. The Handelsgesetzbuch—the German Commercial Code—prescribes bookkeeping, financial-reporting, and statutory-audit requirements for German companies. Every Kapitalgesellschaft must prepare a Jahresabschluss under §242 HGB. What the HGB does not have is an official English translation issued by a recognized standard-setter. No single authoritative body—not the IDW, not the DRSC, not the IASB—has published a binding English glossary for German GAAP the way the IASB publishes IFRS in English.
So what fills the gap? Market convention, practitioner guides, and the terminology auditors have used for decades. And that convention leans on pre-IASB British English. The established renderings are older and plainer than most people expect:
- Bilanz → balance sheet
- Gewinn- und Verlustrechnung → profit and loss account (not “income statement,” not “statement of profit or loss”)
- Anhang → notes (the disclosures required under §§284–288 HGB)
- Lagebericht → management report (required for medium and large corporations)
- Jahresüberschuss → net income for the year / profit for the year
- Eigenkapital → equity / shareholders’ equity
The trap in HGB work is IFRS bleed. A translator who spends most of the year in group reporting reaches reflexively for statement of financial position—and drops it into a document that, by law, isn’t IFRS. It reads as a small thing. To an auditor reviewing the English version of a German statutory account, it reads as a category error. The HGB set of accounts is a balance sheet and a profit and loss account, full stop. Reaching for the wrong drawer signals that the translator can’t tell the frameworks apart.
IFRS English: the IASB’s own text is the source of truth
IFRS is the easy case, because the authority is explicit. The standards are developed and first published in English by the International Accounting Standards Board; every other language version is a translation of that English original. Which means the English text isn’t a rendering I produce—it’s a source I cite. When a German IFRS report says Bilanz, I don’t reach for market convention. I reach for what IAS 1 prescribes.
And IAS 1 Presentation of Financial Statements prescribes specific names. The balance-sheet equivalent is a statement of financial position. The income component is a statement of profit or loss and other comprehensive income. These are the labels in the standard’s own list of the components of a complete set of financial statements. There’s a nuance worth knowing: IAS 1 also permits entities to use everyday alternatives—it explicitly allows names such as “balance sheet” and “income statement.” So an IFRS entity that titles its primary statement “balance sheet” isn’t breaking the rules. But other comprehensive income and profit or loss are IFRS terms of art, and they aren’t negotiable in the way a title heading is.
For the German-to-English direction, the DRSC’s role is a useful bridge to understand. The Deutsches Rechnungslegungs Standards Committee does the serious work of standardizing German-language renderings of international reporting terms—its recent submission of systematically reviewed German ESRS terminology to the EU Commission is one example of that machinery in action. That effort runs the opposite way to mine, but it tells you something structural: there is an institutional apparatus keeping IFRS-family terminology aligned across German and English. For HGB, that apparatus doesn’t exist. That asymmetry is exactly why the two jobs feel so different to translate.
US-GAAP in English: when a German subsidiary feeds an SEC filing
Now the American case, which trips up translators who’ve internalized IFRS as “the international default.” Under US-GAAP, balance sheet is correct. It’s the term of art in FASB-governed reporting, the everyday label in the United States. So the very phrase I’d flag as wrong in an IFRS group report is the right one in a US-GAAP context. Same German Bilanz, opposite verdict, and the deciding factor is purely which framework governs the document.
There’s a wrinkle that catches people out at the filing level. Since a 2007 SEC rule change, a foreign private issuer filing on Form 20-F may present financial statements under IFRS as issued by the IASB without reconciliation to US GAAP. So “it’s a US filing” does not automatically mean “use US-GAAP English.” A German group filing a 20-F on IFRS keeps IASB terminology—statement of financial position—even though the document is going to Washington. The governing standard, not the destination country, sets the vocabulary.
Register matters too. A 20-F is a legal filing: dense, conservative, close to the source structure, US spelling throughout. The US-GAAP equivalent of the German Lagebericht lands as MD&A—Management’s Discussion and Analysis—which is a genuinely different genre from the HGB management report, not just a different label. An investor presentation drawn from the same numbers reads looser and more persuasive. Knowing which document you’re in changes sentence rhythm, not only nouns.
Dual reporting: when HGB and IFRS land in the same job
Here’s where it gets genuinely tricky, and it’s more common than you’d think—because German law builds the collision in. Listed companies must apply IFRS in their consolidated financial statements. But the separate, individual accounts—the Einzelabschluss—must follow HGB; IFRS isn’t even available as an option there. So a single company routinely produces an HGB Einzelabschluss and an IFRS Konzernabschluss, and both can end up in the same translation package.
When that happens, the same German word needs two different English equivalents inside one deliverable. Bilanz is a “balance sheet” in the HGB section and a “statement of financial position” in the IFRS section. Gewinn- und Verlustrechnung is a “profit and loss account” in one and a “statement of profit or loss” in the other. That is not inconsistency—it’s precision. Flattening both to one term to look tidy is the actual error.
How I structure these: two termbases, one per standard, kept deliberately separate, then a single consistency pass at the end whose only job is to confirm each section used its own framework’s vocabulary—not to homogenize them. The check is looking for cross-contamination in both directions: IFRS terms that wandered into the HGB pages, HGB terms that wandered into the IFRS pages.
And the most common briefing failure? The client often doesn’t know which standard governs which part of their own document package. That’s not a criticism—an IR coordinator assembling files under deadline isn’t necessarily the person who prepared them. But it means I can’t outsource the question. Either the briefing tells me, or I ask before I start, because guessing wrong is the one mistake this whole article exists to prevent.
What your briefing has to settle
There is one question that determines everything downstream: which accounting standard was this document prepared under? The answer tells me which dictionary to open. Everything else—tone, spelling, house-style preferences—is negotiable. That isn’t. So when an IR team or project manager first hands me a financial-reporting job, here’s what I actually need to know:
- Which standard governs each document—HGB, IFRS, or US-GAAP? If a package mixes them (a common Einzelabschluss-plus-Konzernabschluss situation), say so explicitly and mark which section is which.
- Where is it going? An SEC 20-F, an EU statutory filing, and an investor presentation carry different register expectations even when the underlying standard is the same.
- US or British spelling for the house style? Separate from the standard question, and worth fixing up front.
- Is there an existing English glossary or prior-year translation to match? Consistency with last year’s report usually outranks my personal preference.
- One named contact who can answer a terminology question mid-project—because in dual-reporting jobs, one will come up.
If a client can’t answer question one, that’s fine—it’s often the honest starting point—but we resolve it before I translate, not after.
The bottom line: this is a technical question, not a style question
So here’s the claim worth quoting: an HGB set of accounts has no “statement of comprehensive income.” That’s an IFRS term. A translator who uses it anyway in an HGB document signals to auditors and institutional investors that they can’t keep the accounting standards apart—and in an audited statement, that kind of slip quietly erodes confidence in the whole report. Terminology is how a reader gauges whether the person who produced the English actually understood the numbers.
None of this is about eloquence. It’s about knowing that balance sheet is right under HGB and US-GAAP but wrong as the IFRS term of art, that IFRS is authored in English so the IASB text is the source rather than a target, and that German law routinely puts two standards in one company’s reporting. Settle the standard before the project starts. Build the termbase standard by standard. And choose a translator who reads financial statements for a living, not one who treats every Bilanz the same.
I’ve been doing German-English financial translation full-time since 2008, across thousands of jobs and plenty of reporting seasons like the one that opened this piece. If you’ve got a package where you’re not certain which standard governs which part, that’s exactly the conversation to have before we begin—see what I do and what it costs, or just send me the files and the question.