Industry domain

Financial Translation

Translate statements, reports, disclosures, and banking documents with figures and accounting terms in view.

Why the subject matters

What changes in this kind of work

A readable financial translation is still wrong if a currency, date, percentage, or reporting term moves. The editor keeps source and target segments together, and QA checks help reviewers locate number and terminology mismatches before delivery.

Financial documents are read by people who compare. Analysts put the translated income statement next to the original, and auditors check that the notes say the same thing in both languages. The errors that matter are usually small: a dropped minus sign, a million that became a billion, “net” where the source says “gross”, or one word for “provision” in the notes and another in the balance sheet.

In DeepReference, a translation model on DeepReference's own servers in the EU writes the first draft. No outside AI company sees the text, and customer content is never used to train the model, which matters for results that are not yet published. A translator or reviewer then works through the draft in the segment editor, with each source sentence next to its translation, and approves it segment by segment.

The quality check compares the figures in each segment and flags a segment where a number in the translation differs from the source. It flags; it does not correct. There is also no automatic conversion of number formats or currencies: whether 1,250.50 appears as 1.250,50 for a German reader depends on the draft, not on a rule. The reviewer checks every separator, currency and scale word.

How it works

A project from upload to delivery

  1. 1

    Prepare terminology and earlier work

    Import the client's approved terms as CSV, XLSX, TMX or TBX (glossary from Starter), and earlier translations as TMX (translation memory on Translator Pro). If there is no glossary yet, terminology extraction can collect candidate terms from last year's report and its translation, for you to approve or dismiss.

    How to do it, step by step: 2.6 Import terms into a glossary · 4.1 Import a TMX file

  2. 2

    Upload the document

    Upload a DOCX, PDF, PPTX or XLSX file of up to 50 MB (75 MB on Business). Tables, headings, numbering, headers and footers and Excel formulas are kept. A PDF needs selectable text; an image-only scan is refused.

    How to do it, step by step: 6. Document translation

  3. 3

    Draft with your terms

    Choose a tone, for example formal for a prospectus or concise for a summary. Approved glossary terms that occur in a sentence are sent to the model with that sentence, and exact matches from translation memory are reused instead of being translated again.

    How to do it, step by step: 5. Text translation, tones and glossary

  4. 4

    Review segment by segment

    In the segment editor, work through the flags for numbers, missing glossary terms, untranslated text and length. Fuzzy matches from memory are shown with a score. Approve each segment, or use “Approve all” once the flags are resolved; every segment keeps a version history.

    How to do it, step by step: 7. Translation Editor

  5. 5

    Handle the next draft

    Annual reports often change several times before publication. Revision comparison (Freelance and up) shows what changed between two DOCX versions: a redline, a DOCX with tracked changes, a redline PDF and a change list. In “With translation” mode (with translation memory on Translator Pro), only the segments the revision affected are retranslated, and nothing is charged until you confirm.

    How to do it, step by step: 9. Revision comparison

  6. 6

    Deliver the file

    Download the translation in the same format and layout. On Translator Pro, the document editor shows the translation in its real layout, which helps when checking that tables and columns still line up.

    How to do it, step by step: 8. Document Editor

Document types

What we translate

  • Annual reportsLong documents in which the same terms recur in the management report, the statements and the notes; a glossary and translation memory help keep them the same throughout.
  • Financial statements and notesEvery figure, sign and total must match the source; the number check flags segments where figures differ, and the reviewer checks negatives shown in brackets.
  • Interim reportsQuarterly and half-year reports repeat much of the previous text, so exact matches from translation memory are reused and the rest is drafted fresh.
  • Investor presentationsShort text in tight PPTX text boxes; the length check flags segments whose length is out of line with the source, and the slide itself should be checked.
  • Earnings releasesOften prepared before publication; the text is processed on DeepReference's servers in the EU and is not sent to an outside AI company.
  • Audit reportsThe opinion and key audit matters use set wording in each language; store the approved wording in translation memory so the same source sentence is reused next year.
  • Banking documentsLoan agreements and account terms use defined terms such as “Borrower” or “Facility”; add them to the glossary so they are sent with each sentence and a missing one is flagged.
  • Risk disclosures and prospectusesHedged wording such as “may” or “could” must keep its strength; a formal tone helps, but the reviewer reads these passages closely.
  • Reporting packs in ExcelLabels are translated and Excel formulas are kept, so totals still calculate; open the file and check the results before delivery.

How to do it, step by step: 6. Document translation

Quality controls

Checks available during review

Domain terminology

A domain glossary or termbase can be applied to keep preferred vocabulary consistent during review.

How to do it, step by step: 3. Terminology extraction

Format and structure checks

Document structure, numbering, tables, and section conventions remain visible for reviewer checks.

How to do it, step by step: 8. Document Editor

Translation memory

Approved translations can be reused when the same or similar text appears again.

How to do it, step by step: 4. Translation memory

Review records

Reviewer actions, translation settings, and approval timestamps are kept where the workflow supports them.

How to do it, step by step: 7.3 Project tools

Glossary filtering

Only glossary terms found in the current text are sent with the translation request.

How to do it, step by step: 2.15 Use a glossary correctly

Recommended settings

How to set up a job in this field

Domain for terminology extraction

Choose Financial when you extract terms from these documents. The domain is used for extraction only.

Step by step in the user guide

Glossary

Add the approved terms for this client and language pair, one translation per term, and select the glossary when you translate.

Step by step in the user guide

Terminology examples

How key terms are handled

Fair value

Translated with the established reporting term of the target language (for example “beizulegender Zeitwert” in German, “juste valeur” in French), not a general phrase for a fair price. Put the client's form in the glossary.

Impairment

A write-down of an asset, not “damage”. Keep it distinct from depreciation and amortisation by giving each its own glossary entry, so a missing one is flagged.

Provision

A liability of uncertain timing or amount, not a reserve in equity. In German it is “Rückstellung”, not “Rücklage”. A typical case for the glossary and for the reviewer.

Securities

In a financial text these are titres, Wertpapiere or titoli, not security in the sense of safety. The model reads the sentence context; short headings and table labels have little context, so check them.

Revenue / turnover

Some British reports say “turnover”, IFRS texts say “revenue”. The client's choice goes in the glossary, so the same term is sent with every sentence that contains it.

Basis point (bp)

One hundredth of a percentage point. “25 bp” must not become “25 %”, and “percentage point” must not become “per cent”. The reviewer checks the unit, not only the figure.

EBITDA and other abbreviations

Many target texts keep EBITDA, EPS or CET1 as they are; some clients prefer a local abbreviation. Record the client's convention in the glossary.

Going concern

A fixed accounting and audit phrase with an established equivalent in each language (for example “continuità aziendale” in Italian). Use that term; do not paraphrase it.

How to do it, step by step: 2.4 Add terms · 2.15 Use a glossary correctly

Who uses this

Industries served

Banks, investment firms, finance teams, auditors, fintech companies, and investor relations teams.

Standards and references

What reviewers can check

Reviewers can check currencies, dates, percentages, ratios, table values, accounting terms, and disclosure wording.

Before delivery

What your reviewer checks

  • Every figure matches the source, including signs, negatives in brackets, subtotals and totals.
  • Decimal and thousands separators follow the target convention (1,250.50 in English, 1.250,50 in German, 1 250,50 in French); DeepReference does not convert them.
  • Currency codes and symbols are unchanged and placed as the target language expects; no amount is converted into another currency.
  • Scale words are right: an English “billion” is a “Milliarde” in German and “mil millones” in Spanish, while a German “Billion” or a Spanish “billón” is a thousand times larger.
  • Dates, financial years and periods (FY2025, Q3, H1, “as at 31 December”) match the source.
  • Accounting terms match the client's glossary and the reporting framework used, such as IFRS or local GAAP.
  • Forward-looking statements and risk wording keep their strength: “may” stays “may”, “expects” stays “expects”.
  • Table labels still sit with the right figures, and Excel formulas give the same results as in the source file.
  • Every quality-check flag is resolved or deliberately accepted before “Approve all”.

How to do it, step by step: 7. Translation Editor

Transparency

What DeepReference does not do

  • DeepReference does not certify translations. Where a regulator, court or stock exchange asks for a certified or sworn translation, a certified or sworn translator provides it.
  • There is no automatic conversion of number formats, currencies, dates or scale words. The reviewer checks them.
  • The quality checks flag; they do not correct. A figure that keeps its digits but changes its scale word (million to billion) or its unit (bp to %) needs a reviewer's eye.
  • DeepReference does not check whether the source figures are correct or whether a report follows IFRS or any other standard. It is not an audit, accounting or investment advice service.
  • There is no model trained specially for finance. The domain setting guides terminology extraction only; it does not change how the model translates.
  • Text inside images, such as charts saved as pictures in a PDF, is not translated, and a scan without a text layer is refused. Upload the original file where possible.

Questions

Frequently asked questions

Does DeepReference convert decimal separators and currencies?

No. The model writes a draft and may or may not adapt the number format to the target language, but no rule converts it, and amounts are never converted into another currency. The number check flags a segment where the figures in the translation differ from the source; the reviewer decides what each flag means and checks every separator.

Can we translate results before they are published?

The text is processed by DeepReference's own model on its servers in the EU. No outside AI company sees it, and it is not used to train the model. Uploads are encrypted in the browser before sending, connections use HTTPS, and stored files are encrypted at rest. Whether unpublished or inside information may leave your company at all is a decision for your own policies.

Will tables and Excel formulas survive?

The file comes back in the same format with its tables, headings, numbering, headers and footers, and Excel formulas. Complex PDF layouts can need a manual check, and some fonts in a PDF are replaced by a similar one. If you have the DOCX or XLSX, upload that rather than the PDF.

Can we use our existing IFRS glossary?

Yes. Glossaries can be imported as CSV, XLSX, TMX or TBX (from Starter). Approved terms that occur in a sentence are sent to the model with that sentence, and the quality check flags a segment where a required term is missing. Missing terms are not corrected automatically; the reviewer fixes them.

Our annual report is largely the same every year. Can we reuse last year's translation?

Yes, with translation memory on Translator Pro. Import last year's translation as TMX, or approve it in DeepReference; an exact match of the same source text is then reused instead of being translated again, and fuzzy matches are shown with a score. For a revised draft of the same report, Revision comparison in “With translation” mode retranslates only the segments the revision affected.

Is the translation accepted for filing with a regulator?

That depends on the regulator, not on the tool. DeepReference does not certify translations, and the issuer remains responsible for what is filed. If a certified or sworn translation is required, a certified or sworn translator has to provide it.

Review framework

Open the platform from the dashboard when you are ready to work on files.

View quality documentation

Begin projects: Financial Translation

Open the platform from the dashboard when you are ready to work on files.