The terrain
Legal translation is not about finding equivalent words. It is about representing a concept from one legal system in another legal system that may not have a direct equivalent for that concept.
Common law and civil law are different structures of reasoning. A “trust” in English law has no precise equivalent in most civil law systems. An “Auflassungsvormerkung” in German property law describes a legal instrument that does not exist in that form in English law. The translator is not looking up a word; they are making a professional judgment about how to represent a legal concept across a jurisdictional boundary, and that judgment will be reviewed by lawyers who know exactly what they are looking at.
Financial documentation adds quantitative precision requirements. An annual report contains numbers. Those numbers must be formatted correctly for each locale (period vs. comma as decimal separator; thousands separator conventions; currency placement). A misplaced decimal separator in a financial statement is not a translation error. It is a compliance failure and potentially a securities law issue.
Regulatory filings have their own vocabulary: submissions to EMA, FDA, FCA, BaFin, AMF, or CNMV are each reviewed by regulators who expect the standard terminology of their own documentation, not a translation of what the other regulator calls it.
What we have learned
The most important decision in a legal translation project is not which terminology to use but who has authority to make terminology decisions when the legal systems differ.
In an M&A transaction, the terminology committee needs representation from both the translation team and the legal teams on each side of the deal. A term that the translators resolve by choosing the closest civil-law equivalent may be unacceptable to the acquiring party’s lawyers, who need the term to carry a specific legal weight in the target system. These conversations have to happen before the translation, not during the review.
Financial translators need to understand the accounting standards of both the source and target markets. A company reporting under US GAAP and producing translations for European investors needs translators who understand the differences in how specific line items are treated and labeled under IFRS. “Revenue” and “turnover” are not interchangeable; neither are “provisions” in US and UK accounting conventions.
Speed is a real constraint in legal and financial work because of deal timelines and regulatory deadlines. A prospectus that must be filed by Monday does not benefit from a six-day translation cycle. We have built workflows (with dual-linguist review and client legal review) that deliver on 48-hour timelines when the project is scoped and staffed in advance.
A typical engagement
For contract and legal document projects, we begin with a terminology alignment session: identifying the key concepts that require cross-jurisdictional judgment before translation begins. This session includes a subject-matter specialist in the relevant area of law, not just a legal translator.
Translation follows a dual-linguist workflow: primary translation, full revision by a second linguist with equivalent legal subject-matter expertise, and a structured QA pass before client review. For regulatory submissions, we add a compliance review pass against the specific agency’s style and terminology standards.
Client-side legal review is built into the workflow, not added at the end. We provide translation notes for every concept that required a cross-jurisdictional judgment, so the reviewing lawyer can assess the decision rather than the wording.