Q3 peak week: how German interim reports get translated into English on time

Every autumn brings the same squeeze: the German Q3 text is only final late in the day, and the English version still has to appear at the same moment. The pattern that survives it is parallel—translate the approved narrative while the figures are still moving, then reconcile every changed number and its surrounding wording before release.

Why Q3 leaves no slack

For calendar-year issuers, the nine-month reporting date sits fixed on September 30, and nothing else in the chain is. Controlling consolidates, legal and audit review follow, the board signs off, and layout gets whatever days are left over. By the time the German text is stable enough to translate well, the release date penciled in during the summer is standing right there. In most projects I see, the English version inherits every delay upstream of it, because translation is scheduled last.

The second squeeze is seasonal. Late-October weeks can run into school holidays and compressed calendars, and the people who own approvals are the same people who own the webcast. Small team, fixed timestamp, document that grew: that combination is what makes the window tight. I won’t dress it up as a statistical claim about the busiest week of the German reporting year—it doesn’t need to be. One hard calendar is pressure enough.

The useful fact points the other way: translation is the single step in the chain that can safely start before the numbers exist, because narrative and figures can be separated. Consolidation needs real figures; review needs real figures; translation needs stable wording and placeholders. That separation is the entire premise of the workflow below—everything else is about protecting it.

Know exactly which document you’re translating

German interim reporting is four different documents under similar names, and Zwischenbericht—interim report—is the umbrella over all of them. Which one you’re translating decides its length, its tone, how much approved English text already exists, and where the figures live. Pin it down before planning a single hour of the week.

• A Prime Standard quarterly statement. Under section 53 BörsO FWB, Deutsche Börse’s follow-up obligations for Prime Standard issuers include a statement on the first and third quarters, in German and English, to be transmitted “no later than two months after the end of the respective reporting period.” Some foreign issuers may be allowed to report in English only.
• An optional quarterly financial report. Where an issuer wants fuller disclosure than a statement requires, it can publish one—but substance, structure and length are its own choice, which makes the English version a moving target until the content plan is fixed.
• An IAS 34 interim financial report. The standard’s own definition: “An interim financial report is a complete or condensed set of financial statements for a period shorter than a financial year.” IAS 34 specifies minimum content and recognition and measurement rules—it does not decide which entities must publish an interim report.
• A half-yearly financial report under section 115 WpHG. That section covers the first six months of the financial year, with a three-month publication deadline, subject to its own statutory scope and exemptions. It is not a Q3 obligation—but its approved English text is the best reference material in the building in October.

The four overlap in the wild: one issuer’s “quarterly report” is another’s statement plus an IAS 34 appendix, and the actual obligations depend on listing segment, domicile and the document itself. Nothing here says every German company must publish every language simultaneously—that assumption is exactly what to check with your own counsel or with the exchange, not with a translation blog.

Plan the parallel delivery before the German is final

Parallel delivery is a set of agreements, not a hope. Before the peak week starts, the IR team and I put five things in writing: which German sections count as approved narrative—stable enough to translate—which figures are provisional, who owns each section, the release timestamp with its time zone, and what depends on what: layout, CMS, wire distribution, the IR site.

For a statement-sized document, a schedule I often propose looks like this. Every timing in it is an example to be negotiated in advance, never a promised turnaround. The only deadline that counts is one I confirm after I’ve seen the files.

1. 72 hours before release: the near-final German narrative is handed over, version ID attached, every figure flagged as provisional.
2. 48 hours before release: the complete English draft is delivered, with placeholders wherever final numbers belong.
3. 24 hours before release: figures are reconciled against the final German; the change log is closed; layout re-flow is checked.
4. 12 hours before release: final QA—numbers, signs, dates, cross-references, names—and sign-off on the release version.
5. Release: both language versions go out at the agreed timestamp.

Dependencies deserve as much attention as durations. If the English layout starts before the figures are final, somebody must own the re-flow after reconciliation—and that somebody should be named in the plan. If the wire copy deadline is three hours before site publication, you don’t have one English deadline; you have two. Schedules survive contact with release week only when the dependencies are written down.

Freeze terminology from approved material

The first hour of a Q3 project goes to gathering approved material: the prior year’s annual report in English, the half-yearly report in English, the client termbase, and the current wording of any guidance. In the CAT tools I use—Trados Studio in most projects—a translation memory stores bilingual source-target units and distinguishes exact matches from fuzzy ones. Approved translations from prior files then feed the new project, which is the point of keeping them.

For interim reporting, the termbase is short and load-bearing: segment and division names, KPI labels, product names, currency and unit conventions, the issuer’s preferred rendering of recurring boilerplate, and the exact verbs of the outlook. Guidance wording deserves near-literal status: “we expect” stays “we expect,” not “we anticipate,” because the subtle verbs carry weight in the English as much as in the German.

How much text carries over varies by document and by how much the business changed, so I don’t quote a reuse percentage before seeing the files. What reuse is worth is consistency: the same segment names, the same KPI labels, the same phrasing as the half-yearly report. Readers notice drift, and analysts keep receipts.

Then the part people skip: matches get contextual review. An exact match is a sentence-level match, not a meaning-level guarantee. If the German sentence now sits in a new paragraph, or the number inside it has changed, a 100% match can still be wrong. Every CAT match is read in its new home, checked against the termbase, and checked against the figure.

Translate the approved narrative, not the moving figures

The mechanic that makes the schedule work: translate the wording, not the numbers. The approved draft’s narrative is stable enough to translate on day one; its figures are not. So every number becomes a placeholder—a tagged field or a highlighted span—and the English text is built around the placeholders.

Two controls keep that safe: a version ID on every file, and a change log with one authoritative source. The authoritative source is the file the issuer declares final—the reporting-tool export or the layout file—and nothing else. A spreadsheet someone made “with the latest numbers” is not a source; it is a comment waiting to become a restatement.

change log -- Q3 statement, v0.7 -> v0.8
table 12, revenue 9M: 1,234.5 -> 1,241.2
revenue commentary, sentence 3: reworded in German
outlook: unchanged
reflected in English: yes

Then the step nobody budgets for: re-checking grammar and meaning after the numbers land. A sentence built around “rose” may need “fell.” “Compared with the prior-year quarter” may need to become “compared with the first nine months.” A figure that crosses a billion boundary changes how you would round it in prose. Numbers never change alone—they change the words around them.

Where MTPE fits—and where it doesn’t

MTPE—machine translation with post-editing—sits on my services page, but in interim reporting it is a case-by-case decision made with the client, never a default. My own published line on it: “I check the MT output first and tell you honestly whether MTPE is worth it.” In Q3 files, that check comes after two gates.

The first gate is client approval. The second is permitted data handling, and the distinction there is contractual rather than technological: client-approved AI tools, used within agreed terms, are a different thing from uploading an unpublished draft to a public service nobody approved. One is processing under an agreement; the other is a disclosure decision nobody made. There is no blanket ban on cloud services—there is a question of permission, of data location and retention, and of the issuer’s own policy.

Human review is the part that isn’t negotiable either way. ISO 18587:2017 describes the discipline: it “provides requirements for the process of full, human post-editing of machine translation output” and for post-editors’ competences. That is a description of a controlled workflow—not evidence that all MT output is suitable, and not permission to route confidential drafts through an unapproved service. In interim documents, MT is weakest exactly where the stakes are highest: first-time disclosures, restructured segments, guidance wording, and condensed note sentences that pack three facts into one clause. Those get full human attention whatever produced the first draft.

What counts as sensitive—and what doesn’t

An unpublished interim report can contain information the market has not seen. It does not follow that every unpublished draft automatically qualifies as inside information. The regulatory definitions are precise: Austria’s FMA glossary, for example, describes insider information as information that is not publicly known, precise, relating to the issuer or a financial instrument, and price-sensitive. Whether a specific draft at a specific moment meets those criteria is the issuer’s legal assessment. Compliance owns that call; a translator does not, and neither does a blog post.

So the working practice is caution regardless of the legal answer: need-to-know distribution, secure transfer channels, no forwarding “just for a quick look,” and agreed clean-up after release. The realistic need-to-know list for a bilingual release is short—translator, layout or web staff, the wire service, the IR team itself. Everyone else can wait for the timestamp.

The errors a reconciliation exists to catch

No war stories here—just the list I work through on every reconciliation, because these are the mistakes that survive a tired Thursday night.

• German changes that never reach English. The “small wording fix” made in layout after handover, forwarded to everyone except the translator.
• Quarter versus nine months. A Q3 statement can headline the three-month quarter, the nine-month cumulative, or both; one wrong label turns growth into a decline.
• Reversed signs. Minus signs lost in re-keying, or a negative restated as parentheses where the English convention expects them.
• Swapped separators. German 1.234,56 against English 1,234.56—swap them blindly and a strong quarter becomes a rounding error.
• Unit slips. Mio. and Mrd. against million and billion: a factor of a thousand in the wrong place.
• Inconsistent dates and comparatives. German 30.09.2026 against the issuer’s English date convention, and comparative columns labeled prior-year quarter where the text says H1.

German: Umsatz 1.234,5 Mio. EUR (30.09.2026)
English: revenue of EUR 1,234.5 million (September 30, 2026)

The separator point gets its own check because it is the one error that looks plausible at a glance: 1.234,5 reads naturally to a German eye and wrong to everyone else. I verify figures number by number and table by table against the authoritative source—then again in layout, after the file has been through somebody else’s hands.

What the IR team should agree with its translator

Most Q3 pain I see is contractual before it is linguistic—things that were never agreed, or agreed once in a hallway. Put these five in writing before the window opens.

• Realistic capacity, booked in advance. What fits—full translation, MTPE, or a narrower scope—is confirmed before the week starts, not discovered during it.
• Terminology approval. Who signs off, when a deviation from the termbase is acceptable, and who arbitrates when memory and termbase disagree.
• Changes after approval. A cutoff, a change-log format, and an honest statement of what late changes cost in hours.
• Final QA ownership. One named person reconciles the English against the final German and signs off the release version.
• An emergency contact on release day. A person with a phone number, not a shared inbox.

I’ve been translating German financial reporting full-time since 2008, and I still won’t improvise a delivery promise in a hallway. What I can do is look at the document type, the page count and the release date early, and give a straight answer about what’s possible. That conversation is much cheaper in September than in release week: the contact page is the right door, and the services overview says what I do and don’t take on.

A readiness checklist, and what carries into the annual report

Condensed to a single page, a parallel German and English Q3 week that holds together looks like this.

• Document type confirmed: Prime Standard statement, optional quarterly report, IAS 34 set, or half-yearly report.
• Obligations checked with the issuer’s own counsel or the exchange—not inherited from another issuer’s practice.
• Release timestamp agreed, time zone named, both language versions included.
• Near-final German narrative handed over, version ID attached, figures flagged provisional.
• One authoritative source named, and a change log running from the first handover.
• Termbase, prior English reports and current guidance wording attached to the project.
• Reconciliation pass scheduled before release, with a named QA owner.
• Sensitive-file handling agreed: channels, retention, clean-up after release.

The payoff doesn’t stop at the timestamp. Everything the process approves in October—the updated termbase, the reconciled guidance wording, the change-log habit—walks straight into annual-report preparation, because the next big German document in the cycle is the Geschäftsbericht, and it reuses every one of those assets. Teams that run Q3 this way start the annual report with terminology that has already survived a live release. That is the compounding interest of controlled translation: every document makes the next one faster to get right.

So take the citable sentence with its caveat attached. Translate the approved narrative while the figures are finalized; reconcile every changed number and its surrounding wording before release; and call it what it is—a recommended workflow, not a rule somebody quoted at you. The issuer owns the obligations, the IR team owns the calendar, and the translator’s job is to make both languages land at the same moment saying the same thing, down to the last decimal separator.