An acronym in a translated document should be handled by a rule you set once per acronym, not by whatever the engine decides in each paragraph. For each entry decide whether it stays as the source acronym, is expanded in full at first mention, or is replaced by an established target-language equivalent, and record that decision in the glossary so every document in a matter follows it. Without the rule, the same abbreviation can appear three different ways in one contract.
Acronyms are where glossary enforcement most often fails quietly. "SPA", "EBITDA", "KYC" or "ESG" look like single tokens, so teams assume they are safe, yet each one forces a choice that a plain term does not. Bluente is built for the lawyers, bankers and consultants who send a translated agreement or board pack straight to a counterparty, and the acronym rules below are the ones that keep those files consistent without a manual proofread of every abbreviation.
Three Decisions Hide Inside One Acronym
Every acronym entry in a glossary answers three separate questions, and most glossaries only record one of them. The first is the surface form: does the target document show the source letters (SPA), a localized set of letters (a different acronym built from the target-language words), or the full expansion with no acronym at all? The second is first-mention behaviour: is the full name spelled out once, with the short form in brackets, and then used alone? The third is scope: does the rule apply to the whole document estate or only to one client or one matter?
Skipping any of the three produces the failure reviewers recognize on sight. A glossary that says only "SPA = SPA" leaves the expansion undefined, so the reader of the translated contract never learns what the letters stand for. A glossary that records an expansion but not the surface form lets the engine alternate between the two. Record all three per entry.
Keep, Expand or Localize: Choosing Per Acronym
Keep the source acronym when it names something specific to the source jurisdiction or the client: a tax form, a regulator, an internal programme. A translator in a practitioner thread on ProZ describes a French client who wanted French tax and billing acronyms left unchanged because they refer to French systems, and that instinct is correct for anything a local reader would search for under the original letters.
Localize when a recognized target-language equivalent exists and the reader would expect it. The same thread cites the familiar case of a United Nations acronym that is routinely swapped for the local-language version. Expand in full when the audience is mixed or the acronym is ambiguous, because "CA" can mean a condition precedent, a confidentiality agreement or a credit agreement depending on the deal.
When none of the three clearly wins, the thread's consensus is the safe default: spell it out once, give the short form, and be consistent afterward.
Why Machine Translation Drifts on Acronyms
A translation engine reads text segment by segment, so it has no memory that "the Purchaser" was introduced on page two with a bracketed abbreviation. When an acronym appears again forty pages later, the engine sees a short string with little context and may leave it, expand it or substitute a near-match from its training data. In a contract this matters because defined terms carry legal weight, a point covered in how AI translation handles defined terms in contracts.
Ambiguity compounds the problem. Short uppercase strings collide across domains, and an engine that has learned one expansion from financial text will apply it inside a clinical or regulatory document. Closely related are inflected languages, where a localized acronym must also take a grammatical ending. Because the engine resolves these cases independently each time, the only dependable control is a glossary entry that fixes the surface form and is applied on every occurrence, not a hope that the model stays consistent.
Modelling Acronyms in a Term Base
The cleanest way to store the decision is as relationships between entries, not as a single flat pair. The term-exchange standard ISO 30042 (TBX) lets one concept carry several terms, and its commonly used TBX-Basic profile distinguishes the type of each term, with values for full forms and acronyms among them. That means "Share Purchase Agreement" and "SPA" are two terms attached to one concept, rather than two unrelated rows that can drift apart.
Modelled this way, you can enforce a preference per concept: the full form on first mention, the acronym thereafter, and a flag for the cases where the acronym must never be translated. If your vendor imports TBX, check that the term type survives the import, a step worth adding to the checks you run for any new custom glossary. A flat two-column spreadsheet can still work, but it needs separate rows for the long and short forms and a column for the rule.
Do-Not-Translate Is Not the Same as Keep
Teams often put acronyms on a do-not-translate list and consider the job finished. That list protects the letters from being altered, but it does nothing about the expansion. A document that keeps "KYC" untouched and never explains it is perfectly consistent and still unhelpful to a reader who does not work in compliance.
Separate the two lists. Do-not-translate answers "do these characters change?" The acronym rule answers "what does the reader see on first mention, and what do they see after?" For a cross-border contract set, the second question is the one counterparties actually ask. The same applies to financial filings, where an abbreviation that is standard in one reporting regime may be unfamiliar in another, a distinction treated in the guide to translating contracts without legal terminology errors.
Checking Acronyms After Translation
Verification is mostly mechanical, which makes it a good candidate for a quick script or a reviewer's search. Pull every uppercase token of two to six letters from the source, list its translated counterpart, and flag any acronym that maps to more than one rendering across the document set. Then confirm that each acronym is expanded exactly once, at first mention, and that no acronym is used before it is defined.
Grade the findings by severity rather than treating them all alike. The MQM framework classes terminology errors by impact, so an inconsistent house-style abbreviation is minor while a mistranslated defined term in an operative clause is critical. Spend reviewer time on the second kind. For segment-level traceability, XLIFF 2.1 can carry notes alongside each unit, which is a practical place to record that an acronym was deliberately kept.
A Short Rule Set to Adopt This Week
Start with the twenty acronyms that appear most often in your contracts and reports, and give each one a recorded decision. Default to expand-then-abbreviate for anything a counterparty might not know, keep the source form for jurisdiction-specific names, and localize only where a recognized equivalent exists. Write the decision, the reason and the date next to the entry.
Then make the rule travel with the file. A glossary that lives in one person's spreadsheet will not be applied by the vendor, the freelancer who reviews the output or the colleague who translates the next document in the matter. If you version your entries, a changed acronym rule follows the same discipline as any other term, as covered in our look at glossary enforcement platforms. The outcome is a document set where an acronym means the same thing on page one and page ninety, in every language.
Related Reading
Sources and Further Reading
ISO 30042 (TBX) — terminology exchange standard, the term-entry model that attaches full forms and acronyms to a single concept
XLIFF 2.1 — OASIS localization interchange standard, the segment-level format that can carry notes on deliberately kept acronyms
MQM — the open framework for analytic translation quality evaluation, on grading terminology errors by severity
ProZ.com — "Should I use the source acronym or convert it to align with the target?", a practitioner thread showing translators weighing keep, expand and localize for the same acronym
Last reviewed 13 October 2026. Written by the Bluente document engineering team, who build and test the format-preservation pipeline described above. We update these guides when the underlying standards, regulations or file formats change.
Acronym rules that survive the whole matter. Upload a contract with your glossary attached to BluTranslate and see the same abbreviation rendered one way from the first page to the last, with the layout untouched. Teams setting up shared term bases can talk to us.