A document translation service supports industry-specific legal terminology when it lets you supply the term base, enforces it during translation, reports every place it deviated, and scopes it to the matter and jurisdiction you are working in. "Our translators specialize in law" is a staffing claim, not a terminology capability: you cannot audit it, and it does not survive the moment any part of the work is automated. The distinction is load-bearing because legal terminology is fixed by legal system and practice area rather than by language — so a vendor treating "legal Spanish" as one vocabulary will be wrong in Mexico City or wrong in Madrid, and often both.
Bluente is a document translation platform for legal and finance teams. Files go in and come back in 120+ languages with the original layout intact and terminology governed by a glossary the team controls rather than by whatever the model happened to prefer that day.
"Legal" is not a vocabulary — the practice area is
Ask a vendor whether they handle legal terminology and the answer is always yes. Ask whether they handle reinsurance terminology and the question becomes answerable. A bordereau, a cut-through clause and a loss-occurring policy belong to a vocabulary that a competent commercial-contracts translator has never used. Shipping has laytime, demurrage and general average. Construction has retention, snagging lists and liquidated damages that a US project team calls a punch list. Patent prosecution has inventive step, prior art and the specific claim language that survives a national-phase filing.
These vocabularies barely overlap. A term base built for one is close to useless for another, which is why "we support custom glossaries" is only meaningful alongside an answer to whose glossary, scoped to which matters. Terminology is the part of legal translation that quality scores do not measure — a sentence can read perfectly and still name the wrong instrument.
The same target language, three different correct terms
Legal terms attach to jurisdictions. Translate "articles of association" into Chinese and the defensible rendering depends on whether the company is registered in Hong Kong, mainland China or Taiwan — three systems, one written language, three different statutory terms. French splits the same way between France, Quebec and Belgium; Spanish between Spain and each Latin American system; Arabic between the Gulf jurisdictions and the North African civil-law codes.
This is the failure a language-level glossary cannot catch. The term base says "translate X as Y", the engine complies, and the output is fluent, consistent and filed in the wrong legal system. Any service that claims terminology support for legal work should be able to hold more than one correct answer per language and let you pick which one governs a given matter. If the glossary is a flat two-column list with no jurisdiction field, it will eventually be right in one country and wrong in the next.
Where an authoritative bilingual term actually comes from
The question every agency page skips: if you do not already have a term base, where do the terms come from? The honest answer is that a small number of jurisdictions publish their own law bilingually, and those are the only unimpeachable sources.
Hong Kong e-Legislation publishes verified English and Chinese versions of the same ordinances — both carry legal status, so the pairing is authoritative rather than someone's best guess. IATE, the EU institutions' terminology database, covers 24 official languages across law, IP, finance and more, and the European Commission's translation service publishes the resources behind it. Canada legislates in English and French in parallel. WIPO's PCT system sets the translation requirements that national-phase patent filings are judged against.
Terms drawn from these sources can be defended to a regulator or a court. Terms drawn from a generic model's training data cannot, because you cannot say where they came from.
What glossary support has to mean mechanically
There is a large gap between a vendor that stores your term list and one that enforces it. The mechanical questions are short and they separate the field quickly.
Can you import a real term base — ISO 30042 (TBX) or a structured CSV — rather than retyping terms into a web form? Is there a do-not-translate list, so party names, defined terms and product marks come through untouched? What happens when two glossary entries conflict, and is the resolution rule documented or silent? Can the service produce a deviation report showing where it did not apply an entry and why?
That last one is the tell. A vendor confident in enforcement will show you the exceptions; a vendor relying on the model's goodwill will offer a screenshot instead. If you work in an interchange format like XLIFF 2.1, ask whether term annotations survive the round trip — plenty of pipelines drop them silently.
Three places terminology control quietly fails
Inflection. A term base entry for Gesellschafter will not match Gesellschaftern or Gesellschafters unless the matching is lemma-aware. German, Polish, Finnish, Russian and Turkish all break naive string matching, and the failure is invisible: the term simply is not enforced, and nothing is flagged.
Structure. Terms living inside a table cell, a footnote, a header, a cross-reference field or a numbered definition clause are often processed by a different path than body text. A glossary that works on paragraphs and not on defined-term numbering will be inconsistent exactly where a contract is most load-bearing.
Images. A term inside a scanned exhibit, a stamp or a chart label only reaches the glossary if the document was OCR'd first. Ask which file objects the terminology layer can actually see. This is where practitioners report the most frustration — the r/sysadmin thread on document translation services is a useful read on how differently vendors behave once real business files, rather than clean text, hit the pipeline.
The eight-point test you can run in an afternoon
Skip the demo. Take twenty terms from your own live matters — including three you know are jurisdiction-specific and two proper nouns that must not be translated — and two real documents, one clean DOCX and one scanned PDF. Then check:
Did the term base import without manual retyping?
Was every one of the twenty terms rendered as specified, in both files?
Did the do-not-translate entries survive untouched?
Was the same term translated identically on page 2 and page 40?
Were terms inside tables, footnotes and headers enforced?
Did the scanned file get terminology treatment at all?
Did the layout survive — tables, numbering and cross-references intact?
Can you get a written answer on retention: how long the file is stored, and whether it is used for model training?
Any vendor that passes eight of eight supports your terminology. Any vendor that talks about linguist credentials instead of answering the eight is selling a service, not a capability — which may still be what you want, but you should know which one you bought.
Where automation ends and sign-off begins
An even-handed note, because the compliance answer is not "automate everything". ISO 17100 is the standard for human translation services and explicitly excludes machine-translation post-editing; ISO 18587 is the applicable standard when machine output is edited by a person. A vendor advertising "ISO 17100-certified AI translation" has told you something useful about how carefully they read.
The practical split most legal teams settle on: automate the reading layer — the incoming foreign-language contracts, the Chinese-language filings, the diligence room — with terminology enforced and logged, and route the executing instruments and anything filed with an authority through named human sign-off on top of the machine draft. The term base is what makes those two tracks agree with each other.
Related Reading
Sources and Further Reading
ISO 30042:2019 — TermBase eXchange (TBX), the terminology interchange standard
XLIFF 2.1 — OASIS specification for localization interchange, including term annotation
ISO 17100:2015 — requirements for human translation services (excludes MTPE)
ISO 18587:2017 — requirements for post-editing of machine translation output
IATE — the EU institutions' multilingual terminology database, 24 official languages
Directorate-General for Translation, European Commission — EU translation resources
Hong Kong e-Legislation — the official bilingual database of Hong Kong law
WIPO — PCT system FAQs, including national-phase translation requirements
Last reviewed 14 September 2026. Written by the Bluente document engineering team, who build and test the format-preservation and terminology-enforcement pipeline described above. We update these guides when the underlying standards, regulations or file formats change.
Bring your own terminology. Import your term base, lock your defined terms, and see whether the output holds up across a clean DOCX and a scanned exhibit. Start with BluTranslate, or talk to our team about per-matter glossary scoping.