Annual report translation: when to brief your specialist translator, and what they need from you

Every year the same email lands in mid-February: final report attached, we go live April 30, how fast can you turn it? By then the calendar has already decided most of the answer. This post gives you the timeline and the checklist that keep you out of that email.

Why the annual report translator always arrives ‘too late’—and who’s really to blame

I’ve worked full time through 17 annual-report seasons, and the crisis is always the same shape. The financials slip. Legal review runs long. The board wants one more pass at the CEO letter. Every one of those delays eats into the same fixed window—because the publication date almost never moves. So the translation, which sits at the very end of the chain, absorbs slack that got spent three departments upstream.

Nobody’s negligent here. The report genuinely isn’t finished. But ‘the report isn’t finished’ and ‘there’s nothing to translate yet’ are two different statements, and confusing them is what costs you money in February. Roughly 80% of an annual report—the narrative, governance disclosures, methodology notes, the risk section—is stable weeks before the audited figures land. A specialist agency I follow puts it plainly: the majority of your content is available long before the key figures are finalized, and as a rule about 80% can be processed at a very early stage.

So the honest answer to ‘when do I brief my translator?’ is: earlier than feels natural, and with less than you think you need. Here’s how that breaks down across the season.

The reporting calendar: publication deadlines and what they mean for lead time

Every translation deadline is a backward calculation from a legal one. Three constraints drive the German season:

• HGB preparation deadline (§ 264 HGB). Legal representatives of a capital company must prepare the annual accounts within the first three months of the new fiscal year. For a December 31 balance-sheet date, that’s March 31. Small capital companies get six months, to June 30.
• Listed-company disclosure (§ 114 WpHG). Domestic issuers on a regulated market must make the annual financial report publicly available no later than four months after year-end—April 30 for a calendar-year filer. This is the hard outer wall.
• General HGB disclosure (§ 325 HGB). Non-listed companies have twelve months to file. That window is misleading for planning: the pressure point is the audited-accounts date, not the disclosure date.

The industry-standard translation timeline runs about ten weeks backward from the filing date, aiming for a complete multilingual draft roughly one month before release. Map that onto an April 30 WpHG wall and the arithmetic is unforgiving:

• April 30 — publication (hard).
• ~ April 1 — complete translated draft, one month out, for final proofing and DTP.
• Mid-January to mid-February — rolling translation of the stable 80%.
• October–December — pre-season prep: terminology, style guide, prior-year memory.
• Mid-February — the last realistic date to hand over the last stable draft without paying for speed.

October to December: the prep that pays off in season

This is the quiet window, and it’s where the real savings live. You don’t need a single new sentence of this year’s report to start. You need last year’s.

The single highest-leverage thing you can hand me is the prior year’s approved translated report. Loaded into the translation memory before the season opens, it does two things at once: it fixes your corporate language so this year reads like last year, and it turns every recurring passage into a match rather than a fresh translation. Annual reports are full of year-over-year boilerplate—note templates, accounting-policy language, standing risk factors—and that boilerplate is exactly what a warmed-up memory recognizes.

That recognition is what your invoice reflects. My no-match base rate is €0.85 per standard line (a standard line is 55 characters including spaces—a German-market convention worth defining once). Against a well-fed memory, that same content is priced down the match scale: repetitions and 100% matches at €0.17 per line, high fuzzy matches (85–99%) at €0.51, context matches from the TM at €0.00. Industry estimates put total savings on repeat or revised content at 30–70%; on a report with stable note templates, you’re at the upper end of that band. The warm-up costs you an email in November. It saves you real money in February.

While you’re at it, send four more things before the first draft exists: an updated in-house terminology list, your style guide, a note on any known structural changes to this year’s report, and a heads-up on the audit timeline so I know when the figures realistically arrive. Sharing volume and schedule this early is also what lets me reserve capacity for you—which matters more than most clients realize, for the reason in the next section.

January to mid-February: how do you work with texts that aren’t final?

You work with them by treating ‘not final’ as a workflow, not an excuse to wait. The narrative is stable; the numbers aren’t. So we translate the narrative and quarantine the numbers.

The discipline that makes this safe is single-source-of-truth version control. One canonical file per language, one owner, and every change logged with what changed, why, and where it cascades across the other language files. When a paragraph moves in the German, I need to know so the English moves with it—not discover it three versions later.

A few practical rules from the production side:

• Send clean Word, not InDesign exports, for the translation stage. I translate from the editable source. IDML round-trips belong to the DTP stage at the end, not the rolling-translation stage in the middle.
• Use track changes for updates, and leave them visible. A silent overwrite of a ‘final’ file is how a corrected sentence quietly reverts. If you accept all changes before sending, tell me what they were.
• ‘Final except the financials’ is a green light, not a hold. It means the 80% is ready. Send it. We lock the narrative and leave clearly marked gaps for the figures.
• Name your versions like you mean it. Report_v7_2026-02-10_legal-review beats Report_final_FINAL_v2 every season.

The briefing checklist: what your translator actually needs from you

Here’s the concrete handover. Get these in front of your translator and the avoidable back-and-forth—the thing that actually eats turnaround—mostly disappears.

1. Reference documents. Last year’s approved bilingual report, plus any interim or quarterly translations from this year.
2. In-house terminology. Your current glossary. If you don’t have one, a list of the 30 or 40 terms you’re fussy about beats nothing.
3. Style guide. Corporate voice, capitalization conventions, whether you write ‘Group’ or ‘group’, US or UK English.
4. Publication format and DTP hand-off. Tell me the final format and who does layout. If it’s InDesign, agree the IDML hand-off point up front.
5. XBRL / iXBRL implications, if you’re tagging. Flag it early; tagged financial statements change how the number-bearing sections are handled downstream.
6. NDA and data-residency confirmation. A pre-publication draft is material non-public information. A signed NDA, encrypted transfer, and a clear data-retention window aren’t optional extras—they’re due diligence. I sign yours or provide mine.
7. A named contact for questions. One person who can answer ‘is this term intentional?’ within a day. Not a shared inbox.
8. Hard publication date vs. soft target. Tell me which is which. I plan backward from the hard wall and treat the soft target as the goal.

The final sprint: managing last-minute changes cleanly

Late changes are inevitable. The question is whether they’re managed or chaotic. The classic scenario: the whole report’s done and approved, and now ‘only pages 12 to 17’ are left because the segment figures moved. That’s fine—if you submit the update as a marked delta against the version I already have, not as a fresh full file with untracked edits buried inside. A fresh file forces me to re-diff the entire document to find your six changes, which is slower and riskier than the changes themselves.

On overnight delivery: sometimes realistic, sometimes not, and the honest line matters. A handful of revised pages against a memory that already holds the rest? Often doable overnight. A first draft of a section I’ve never seen, at midnight, before an 8 a.m. board sign-off? That’s not speed, that’s a quality gamble, and I’ll tell you so.

When a rush is real, the surcharge is a capacity decision, not a penalty. From my side it buys the evening and weekend hours that displace other work: +30% for firm 24-hour delivery, +50% for same-day, weekend, or holiday turnaround. The point of the whole timeline above is to make sure you’re paying my base rate in February instead of the surcharge in April.

When several frameworks run at once: HGB, IFRS consolidated, and ESRS in one season

Larger groups increasingly translate three things in parallel: the HGB single-entity accounts, the IFRS consolidated statements, and—new pressure for the current cohort—an ESRS sustainability statement. The CSRD’s second wave brings large companies not previously caught by the old NFRD (250-plus employees, turnover above €40 million) into scope, with their first sustainability statement covering fiscal year 2025 and published in 2026. That chapter lands in the same season as the financials.

HGB and IFRS share most of their terminology discipline; the memory and termbase carry across cleanly. ESRS does not. Its vocabulary—‘materiality’, ‘dual materiality’, ‘taxonomy’, ‘risks and opportunities’—carries legally defined meanings set by the standards themselves, not by financial-reporting habit, and an inaccurate rendering creates regulatory risk rather than just an awkward sentence. That’s why the ESRS section gets its own mini-briefing and its own termbase, kept separate from the financial-statement glossary. If you want the deeper treatment of ESRS terminology and of how the CAT workflow handles all of this, I’ve written those up separately on the blog—no need to repeat them here.

Five sentences to save your next reporting season

1. Send your translator last year’s approved bilingual report before December—it warms up the memory and cuts your per-line cost before the season even starts.
2. Brief in October or November, not February; specialists allocate January capacity in the prior autumn.
3. Release the stable 80%—narrative, governance, methodology—as soon as it’s clean, and quarantine the number-dependent paragraphs for the sprint.
4. Get the last stable draft over by mid-February, or plan to pay a rush surcharge that a warmer timeline would have avoided.
5. Give the ESRS chapter its own briefing and termbase; its terms are legally defined and don’t inherit from your financial glossary.

If you’d rather sort this out before the season lands on top of you, that’s exactly what the quiet autumn window is for. Send me your calendar and last year’s report and we’ll map the backward timeline together—see services and pricing, or just get in touch.