A practical guide to financial statement translation and review

A financial report can look complete while its translation brief is missing essential information: which version is final, whether the notes are included, and who can approve a disputed term. Good financial statement translation starts by resolving those questions. The objective is to carry the source document's meaning and relationships into another language without silently changing what the company reported.

This guide explains how to prepare, commission and review financial statement translation. It covers files, terminology, figures, layout and handover, rather than accounting decisions or currency conversion calculations. The examples below are fictional quality checks. They are not client cases, reporting templates or evidence that a particular recipient will accept a translation.

Define the scope of financial statement translation

Before requesting financial statement translation, identify who will read the result and why. A potential investor comparing reports may need different supporting material from an internal team checking a bilingual draft. Ask the recipient about its language, file format and any certification requirements instead of assuming that a polished PDF satisfies every requirement.

Record the entity's exact name, reporting period, source and target languages, deadline and intended use. Explain whether financial statement translation covers a standalone set of statements, selected extracts or an annual report containing other material. Keep that scope visible in the document translation brief so omissions and additional requests can be identified before production begins.

Where certification is requested, ask what the recipient means by that requirement and which documents it covers. A financial statement translation may sit alongside an auditor's report, directors' statements or corporate records, each with a different function. Identify these items individually. Do not merge an auditor's opinion into the company's narrative or remove a qualification because it complicates the wording.

Keep language work separate from currency translation

The phrase financial statement translation can describe language work, but accounting also uses the word translation in connection with currencies. IAS 21 addresses foreign currency transactions, foreign operations and presentation currencies. That accounting scope should not be confused with rendering a report from one human language into another.

State explicitly whether the assignment includes language work only. During financial statement translation, the translator should preserve the source currency and amounts unless a separately agreed, properly instructed task requires something else. An unfamiliar currency label is a question for the document owner, not permission to substitute a currency, select an exchange rate or adjust the company's figures.

Build an inventory before sending the files

Prepare a simple inventory for financial statement translation: filename, version date, page count, language and whether the file is editable. Include appendices and documents referred to elsewhere in the package. A folder containing several files called final can conceal a later revision, so nominate one owner who can identify the authoritative source.

For an IFRS reporting package, the IAS 1 overview is a useful reminder that statements, notes and comparative information belong together. Use the source's contents page to define the actual financial statement translation assignment. Do not assume that receiving a balance sheet means the remaining statements or explanatory notes were intentionally excluded.

Mark each item as included, excluded or awaiting confirmation. This makes financial statement translation easier to quote and review without turning the inventory into a judgment about whether the underlying financial reporting is complete.

Identify the reporting framework and edition

Tell the language team which reporting framework the source identifies and whether an approved bilingual terminology list already exists. For financial statement translation, that information helps distinguish an established reporting label from an ordinary word. It does not authorize the translator to rewrite the statements to match a different framework.

The IFRS Foundation's IFRS 18 overview states that the standard replaces IAS 1 and applies to annual reporting periods beginning on or after 1 January 2027, with earlier application permitted. A financial statement translation project should therefore identify the framework actually applied in its source. Do not automatically relabel a 2026 report merely because a newer standard has been issued.

For financial statement translation involving an earlier report, retain its original reporting date and framework references. Supply an approved previous translation if it is useful, but mark it as a reference rather than automatic authority. A familiar heading from last year's file may no longer match the current source. Differences should be reviewed in context, not copied forward without checking.

Prepare files for financial statement translation

An editable file can reduce rekeying, but it does not replace a reference PDF. Provide both when available for financial statement translation, and explain which controls if they differ. Keep spreadsheets, embedded tables and linked notes together; a PDF may display information that is absent from a separately supplied worksheet.

Scanned pages need a legibility check before financial statement translation begins. Look for clipped margins, faint minus signs, missing pages and stamps covering text. Optical character recognition can assist extraction, but its output needs comparison with the image. Ask for a clearer source when meaning cannot be read reliably, and record unresolved passages rather than guessing.

Agree terminology for financial statement translation

Create a short glossary for financial statement translation containing the source term, proposed target term, context and approval status. Prioritize repeated statement headings, line items, entity names and abbreviations. The goal is consistent use in the particular document, not a universal dictionary detached from the source's reporting context.

A term may appear in a heading, a note and a narrative explanation. During financial statement translation, compare those uses together before approving a replacement. Our guide to translation glossaries and reviewers explains how a shared terminology record supports that process. Keep genuine alternatives as queries until someone with the necessary source knowledge resolves them.

For financial statement translation, a glossary should also record what stays unchanged: legal entity names, approved abbreviations and identifiers. Do not expand an abbreviation merely because a plausible expansion exists elsewhere.

Give context when requesting approval of a financial statement translation term. Words such as interest, capital and provision may have everyday meanings as well as specific uses in a report. Show the surrounding sentence, relevant heading and any previous approved wording. Ask for a decision about that location instead of accepting a broad instruction to use the same equivalent everywhere.

Check figures during financial statement translation

Numeric checking in financial statement translation means comparing the target against the supplied source. Check digits, signs, decimal separators, currency labels and scale headings. A line marked in thousands must not lose that qualification during layout. Do not turn this comparison into an independent calculation or an assurance that the source accounts are correct.

Preserve distinctions between a dash, a zero, a blank cell and a figure shown in parentheses. The financial statement translation reviewer should query an ambiguous convention rather than normalize it silently. When the target language uses different punctuation conventions, agree a consistent presentation rule while retaining the source values and keeping the change traceable.

Check financial statement translation tables after every substantial layout change. Repeat essential column labels when a table continues onto another page, and make sure a heading cannot be mistaken for a separate row. A reader should be able to connect a value with its period and unit without reconstructing the original page. Check the exported PDF, not only the editable layout.

Follow notes and comparisons across the document

Review financial statement translation across pages, not only sentence by sentence. Follow each sampled note reference from the statement to its destination. Check that period headings remain attached to the correct columns and that a comparative figure has not moved into the current-period column when a table was resized.

The same principle applies to financial statement translation of cross-references in running text. If a paragraph refers to a particular note, appendix or page, verify that the target leads to the intended material. A pagination change may require an updated page reference, but it should not silently change the underlying note number.

If financial statement translation covers selected extracts, identify the boundaries clearly. Preserve references to material outside the assignment and tell the recipient which supporting notes were not translated. Do not invent replacement explanations to make an extract appear self-contained. The owner can decide whether to expand the package, provide additional context or obtain the recipient's confirmation of the limited scope.

Use a query log with decisions and owners

A useful query log makes financial statement translation decisions reproducible. Record the source location, the question, its effect on the target, the person responsible and the approved response. A screenshot or short excerpt can help locate an issue, but avoid circulating an entire confidential report when a limited reference is sufficient.

Separate language questions from source-document questions. In financial statement translation, an inconsistent entity name might require confirmation from the document owner, while an awkward target sentence may be resolved by the language reviewer. Give unresolved items a visible status. Silence, an unanswered email or a deadline should not be treated as approval.

Test the checklist with fictional examples

These fictional examples show how financial statement translation checks work without prescribing accounting treatment. In the first, a table heading says “USD thousands” in the source but only “USD” in the target. The reviewer restores the omitted scale label after checking the source; the reviewer does not rescale the amounts.

In the second financial statement translation example, a note reference points to Note 8, but the target points to Note 6. The reviewer traces the reference and corrects the target link. If the source itself contains the conflicting reference, the issue goes to the document owner instead of being silently repaired as a translation decision.

In the third financial statement translation example, two revisions use different company names. The translator pauses that decision, records both locations and asks which version is authoritative. An approved response is then applied consistently to the target, with the affected locations checked again.

Review meaning before the final page check

Use two distinct passes for financial statement translation. First compare meaning and terminology against the source, including qualifications, dates, headings and references. Then inspect the formatted target for clipped text, broken tables, misplaced footnotes and reading order. Running a spelling check alone cannot establish that either pass is complete.

Arrange proofreading and language review with an agreed scope. For financial statement translation, the reviewer needs the authoritative source and the query log, not just the target PDF. If an accountant or another specialist reviews reporting terminology, identify that role accurately; do not describe ordinary language review as an audit or invent professional credentials.

Protect versions while changes are being made

Agree how revisions enter the financial statement translation workflow. Name one source owner, keep a dated change log and distinguish source corrections from target-language edits. If an updated report arrives halfway through production, compare it with the approved source and identify the affected sections before replacing files or restarting work.

Protect confidentiality throughout financial statement translation by limiting access to people involved in the assignment and agreeing how files will be transferred and retained. Confirm the actual arrangements with the provider. Do not assume that an email attachment, a shared link or a generic confidentiality statement establishes the specific controls your organization requires.

Plan the financial statement translation handover

Specify the deliverables for financial statement translation before the deadline: target PDF, editable file if agreed, glossary, resolved queries and any remaining limitations. Include version identifiers that connect the delivery to its source. Keep reviewer comments separate from the clean deliverable so an internal discussion cannot accidentally become part of an externally circulated report.

The quality process should make responsibilities visible. For financial statement translation, ask who checks language, who checks layout, who answers source queries and who approves delivery. Do not infer that an unchanged number has been audited, or that a signed declaration guarantees acceptance by a bank, regulator or other recipient.

Before closing financial statement translation, reopen the delivered files and confirm that the expected pages and attachments are present. Test text selection and search where those functions are required, and check that no tracked changes or internal comments remain in the clean copy. Record the delivery version in the query log so later corrections can be linked to the right file.

A practical request checklist

Before commissioning financial statement translation, confirm the following points in a short written brief. Each answer should point to a file, a decision or a responsible person rather than a general promise of quality.

• Identify the intended reader, target language, reporting period and exact package included.
• Name the authoritative source and supply its reference PDF, editable files and relevant attachments.
• Confirm the reporting framework stated in the source and provide approved terminology where available.
• Agree how figures, scale headings, references and unresolved passages will be checked and recorded.
• Assign the source-query owner, reviewer, deadline and final approval responsibility.
• Specify deliverables, confidentiality arrangements and any recipient requirements that need independent confirmation.

If the package includes company records as well as statements, our business document translation guide can help distinguish those additional materials. Keep the financial statement translation scope explicit so supporting records do not disappear into an assumption about what the original quotation covered.

To prepare a financial statement translation request, send the agreed file inventory with your languages, purpose and required delivery date. Flag missing information at the outset. A clear brief lets the language team explain its scope and raise questions early, while your document owner retains responsibility for the source and the decisions that only they can approve.