VIEW THIS AS

Auto mode follows the Route Engine until you choose a viewpoint.

YOU ARE HERE

ROUTE CHECK

CONNECTED TO

WHAT NEXT

Use the canonical route for this room, or HELP if you are unsure.

Top Ways to Translate Correctly | UN/EDIFACT DESADV Segments, Qualifiers and Despatch Advice

UN/EDIFACT DESADV despatch advice messages: this guide answers how to translate DESADV messages, EDIFACT segment codes and despatch advice labels accurately. The safest method is to translate the human-facing explanation of a DESADV despatch advice without altering the machine-readable message, control envelope, qualifier identity or shipment facts. It is written for a logistics translator, warehouse trainer, EDI analyst or receiving clerk, with worked examples and a practical translation quality assurance checklist, not a substitute for a validator or a system owner.

The visible problem is that a seemingly fluent translation can change which business party receives goods, when a dispatch is expected or how many packages a line reports. A translator may understand each ordinary word yet miss the technical relationship between a label, its code and the downstream action. The solution is to separate human explanation from machine identity, preserve what the data actually asserts, and check the result in the document’s real workflow.

For accurate technical translation and localization, begin with the segment and component separators, release character, message version, message-reference identifiers, codes, dates, quantities and party identities. Then identify which natural-language phrases readers genuinely need in their own language. This page explains the first principles, a repeatable twelve-stage method, field-level examples, common errors, practice activities and next reading routes. It deliberately keeps this subject separate from generic advice about translation style, idioms or glossaries.

Quick answer: preserve stable identifiers; translate explanatory wording only when its function is known; verify every important relationship against the primary source; record unresolved ambiguity instead of inventing confidence; and test the final edition with a domain reader. A translated document succeeds when someone can make the same justified decision from it as they could from the original.

  • Canonical job: translate the human-facing explanation of a DESADV despatch advice without altering the machine-readable message, control envelope, qualifier identity or shipment facts.
  • Do not alter: the segment and component separators, release character, message version, message-reference identifiers, codes, dates, quantities and party identities.
  • Best first action: copy the source, identify the version and separate labels from identifiers.
  • Best final action: structural checks, semantic checks and a documented handoff.

The essential distinction: translation is not protocol conversion

Natural language is flexible because speakers can express one purpose in several ways. Structured records are constrained because downstream systems may interpret particular tokens, offsets or relationships literally. The human text around a record may be translated freely within the boundaries of meaning, but its functional identifiers are not prose. This is why the familiar instruction to “translate the meaning rather than the words” requires an extra safeguard in a machine-readable environment: determine exactly where the meaning lives and where the executable structure begins.

A correct target-language phrase is not proof of a correct operational result. Consider a label that appears near a numeric value. Before choosing a synonym, establish whether the number is a count, identifier, date, position, measurement, quality flag or ordering key. If it controls a dependency, a single misplaced relationship can cause a larger mistake than a slightly awkward adjective. An audit must therefore ask two questions: does the reader understand the message, and does the record still mean the same thing to the consuming system?

Document authority also matters. A public specification can define the general model, while an organisation’s implementation profile determines supported values, optional fields or local naming conventions. Translate neither a missing value nor a guessed default into an affirmative fact. If the profile is absent, mark the decision as provisional and identify the field whose interpretation needs confirmation. This is a positive professional outcome: a transparent uncertainty is safer than a polished falsehood.

First principles: what stays fixed and what can change

1. Identity: a principle that can be tested

A string used as an ID, address, reference, or machine key is a locator, not an ordinary word. Preserve it even if it resembles an English noun. Give users a translated description next to it rather than inside it. In UN/EDIFACT DESADV despatch advice messages, a useful illustration is UNA:+.? '. This introduces delimiters, not a prose sentence. This illustrates why a translated label needs more than a plausible dictionary equivalent: changing punctuation breaks parsing. A reviewer should ask the operator to point to the exact source evidence, explain the relationship in ordinary language, and show that the edited human-facing text has not modified the represented fact.

The practical test is to compare the source, the edited copy and the rendered explanation side by side. Record which properties were intentionally localized, which properties were protected and how the result was checked. If a team cannot answer all three, it has not finished quality assurance for this principle. That test generalizes to multilingual training materials, technical help centres and public-facing records.

2. Hierarchy: a principle that can be tested

Parent-child and ordered relationships determine what a value belongs to. A well-written description must not turn a child component into a top-level one, or describe an attached value as applying globally. In UN/EDIFACT DESADV despatch advice messages, a useful illustration is UNH+42+DESADV:D:96A:UN'. This is a DESADV under a specific directory release. This illustrates why a translated label needs more than a plausible dictionary equivalent: calling this an invoice changes the business-document type. A reviewer should ask the operator to point to the exact source evidence, explain the relationship in ordinary language, and show that the edited human-facing text has not modified the represented fact.

The practical test is to compare the source, the edited copy and the rendered explanation side by side. Record which properties were intentionally localized, which properties were protected and how the result was checked. If a team cannot answer all three, it has not finished quality assurance for this principle. That test generalizes to multilingual training materials, technical help centres and public-facing records.

3. Type: a principle that can be tested

A stored value has a type and often a unit or code system. Translation must not coerce integer to text, an identifier to a number, or an encoded role into a familiar but different role. In UN/EDIFACT DESADV despatch advice messages, a useful illustration is DTM+137:20261118:102'. Qualifier and format code govern which date this is. This illustrates why a translated label needs more than a plausible dictionary equivalent: treating 20261118 as local time invents a clock and zone. A reviewer should ask the operator to point to the exact source evidence, explain the relationship in ordinary language, and show that the edited human-facing text has not modified the represented fact.

The practical test is to compare the source, the edited copy and the rendered explanation side by side. Record which properties were intentionally localized, which properties were protected and how the result was checked. If a team cannot answer all three, it has not finished quality assurance for this principle. That test generalizes to multilingual training materials, technical help centres and public-facing records.

4. Scope: a principle that can be tested

Distinguish a property of the complete object from a property of one component. Say explicitly what the rule governs when an abbreviation can apply in several positions. In UN/EDIFACT DESADV despatch advice messages, a useful illustration is NAD+DP+SITE-03::9'. Delivery party may be different from buyer. This illustrates why a translated label needs more than a plausible dictionary equivalent: merging DP with BY routes goods to the wrong address. A reviewer should ask the operator to point to the exact source evidence, explain the relationship in ordinary language, and show that the edited human-facing text has not modified the represented fact.

The practical test is to compare the source, the edited copy and the rendered explanation side by side. Record which properties were intentionally localized, which properties were protected and how the result was checked. If a team cannot answer all three, it has not finished quality assurance for this principle. That test generalizes to multilingual training materials, technical help centres and public-facing records.

5. Time and order: a principle that can be tested

Sequence, timestamps, offset and scheduling information are often operational. A natural-language expansion must preserve event order and avoid inventing a time zone, local date or precision absent from the source. In UN/EDIFACT DESADV despatch advice messages, a useful illustration is CPS+3+1'. Package hierarchy relates a child grouping to its parent. This illustrates why a translated label needs more than a plausible dictionary equivalent: flattening nested packaging makes carton attribution disappear. A reviewer should ask the operator to point to the exact source evidence, explain the relationship in ordinary language, and show that the edited human-facing text has not modified the represented fact.

The practical test is to compare the source, the edited copy and the rendered explanation side by side. Record which properties were intentionally localized, which properties were protected and how the result was checked. If a team cannot answer all three, it has not finished quality assurance for this principle. That test generalizes to multilingual training materials, technical help centres and public-facing records.

6. Human interface: a principle that can be tested

The translator usually controls captions, tooltips, help text, glossaries and interpretive notes. Those are legitimate spaces for clarity and localization, provided each text is mapped to the correct source key. In UN/EDIFACT DESADV despatch advice messages, a useful illustration is LIN+1++SKU-A47:SA'. Line number and article code identify an item. This illustrates why a translated label needs more than a plausible dictionary equivalent: translating SKU-A47 as a description destroys matching. A reviewer should ask the operator to point to the exact source evidence, explain the relationship in ordinary language, and show that the edited human-facing text has not modified the represented fact.

The practical test is to compare the source, the edited copy and the rendered explanation side by side. Record which properties were intentionally localized, which properties were protected and how the result was checked. If a team cannot answer all three, it has not finished quality assurance for this principle. That test generalizes to multilingual training materials, technical help centres and public-facing records.

7. Evidence: a principle that can be tested

A claim should be traceable to a defined field, official standard or verified implementation. If it cannot be proven, say what remains unverified and do not launder a guess into the published wording. In UN/EDIFACT DESADV despatch advice messages, a useful illustration is MEA+AAE+G+KGM:580'. Measurement category, dimension and unit determine meaning. This illustrates why a translated label needs more than a plausible dictionary equivalent: treating gross mass as net mass affects transport decisions. A reviewer should ask the operator to point to the exact source evidence, explain the relationship in ordinary language, and show that the edited human-facing text has not modified the represented fact.

The practical test is to compare the source, the edited copy and the rendered explanation side by side. Record which properties were intentionally localized, which properties were protected and how the result was checked. If a team cannot answer all three, it has not finished quality assurance for this principle. That test generalizes to multilingual training materials, technical help centres and public-facing records.

8. Reversibility: a principle that can be tested

A reviewer should be able to trace each translated decision to the original field and reconstruct what was preserved. Without source alignment, corrections become guesswork and later revisions risk data loss. In UN/EDIFACT DESADV despatch advice messages, a useful illustration is UNT+47+42'. Trailer counts segments and repeats message reference. This illustrates why a translated label needs more than a plausible dictionary equivalent: translating a label inside the segment corrupts the count. A reviewer should ask the operator to point to the exact source evidence, explain the relationship in ordinary language, and show that the edited human-facing text has not modified the represented fact.

The practical test is to compare the source, the edited copy and the rendered explanation side by side. Record which properties were intentionally localized, which properties were protected and how the result was checked. If a team cannot answer all three, it has not finished quality assurance for this principle. That test generalizes to multilingual training materials, technical help centres and public-facing records.

A repeatable twelve-stage translation workflow

Use this workflow for small one-line notices and larger documentation releases. It is deliberately sequential: verify the assignment and inputs before translating, examine the graph of relationships before approving wording, and leave a small evidence trail that the next editor can reuse. Each step should produce a tangible artifact, not merely an assertion that a check was done.

Step 1: Define the assignment and its exclusions

Before translating a line, state whether the assignment covers viewer labels, human guidance, a source-data object, or actual protocol conversion. A human-readable edition is not authority to rewrite an interoperable file. Ask who will read it, which application will render it, and which elements must remain byte-for-byte unchanged. For UN/EDIFACT DESADV despatch advice messages, place BGM+351+DA2026-884+9' in the working register and ask whether a despatch advice number identifies a particular notice. The immediate quality checkpoint is: keep document identifier immutable and translate descriptive field labels. Do not advance this field simply because a fluent translation has been proposed.

A reusable deliverable for this step is a compact row containing the original value, its operational role, the target-language label, a link to the specification, and the reviewer decision. Such rows are small enough to audit and rich enough to prevent an unresolved assumption from disappearing during editing. In later projects, this record also supports training and regression tests.

Step 2: Freeze the source and record its version

Capture an immutable copy and a reference to the relevant specification or application profile. Note which edition, directory, version and implementation produced the data, because an apparently familiar identifier may be given different restrictions by a project-specific profile. Work in a separate annotation or documentation layer. For UN/EDIFACT DESADV despatch advice messages, place DTM+137:20261118:102' in the working register and ask whether qualifier and format code govern which date this is. The immediate quality checkpoint is: decode qualifier using directory before natural-language rendering. Do not advance this field simply because a fluent translation has been proposed.

A reusable deliverable for this step is a compact row containing the original value, its operational role, the target-language label, a link to the specification, and the reviewer decision. Such rows are small enough to audit and rich enough to prevent an unresolved assumption from disappearing during editing. In later projects, this record also supports training and regression tests.

Step 3: Identify the reader’s question

A newcomer asks what happened, what this label means and what action is safe. A maintainer asks which key, object, value or timestamp it refers to. Draft the answer for the actual decision the reader faces, not as a dictionary dump. Prefer a concise direct label followed by an expanded explanation. For UN/EDIFACT DESADV despatch advice messages, place NAD+BY+BUYER01::9' in the working register and ask whether bY describes the buyer role. The immediate quality checkpoint is: preserve qualifier and look up business-role vocabulary. Do not advance this field simply because a fluent translation has been proposed.

A reusable deliverable for this step is a compact row containing the original value, its operational role, the target-language label, a link to the specification, and the reviewer decision. Such rows are small enough to audit and rich enough to prevent an unresolved assumption from disappearing during editing. In later projects, this record also supports training and regression tests.

Step 4: Build an invariant register

List control characters, field names, machine identifiers, checksums, typed values, references, ordering and other source facts that must survive unchanged. Put every invariant in a table with its purpose and a verification method. The register prevents well-intentioned translators from silently normalising significant bytes. For UN/EDIFACT DESADV despatch advice messages, place NAD+DP+SITE-03::9' in the working register and ask whether delivery party may be different from buyer. The immediate quality checkpoint is: cross-check party-role matrix with the order and receiving site. Do not advance this field simply because a fluent translation has been proposed.

A reusable deliverable for this step is a compact row containing the original value, its operational role, the target-language label, a link to the specification, and the reviewer decision. Such rows are small enough to audit and rich enough to prevent an unresolved assumption from disappearing during editing. In later projects, this record also supports training and regression tests.

Step 5: Draw relationships before choosing words

Trace parent-child relationships, cross-references, message flows, numeric ranges and what each field points at. A translation can be grammatically elegant yet wrong if it attaches a quantity to the wrong object or explains a reference as content. Make a small diagram or two-column map before the first draft. For UN/EDIFACT DESADV despatch advice messages, place RFF+ON:PO-29048' in the working register and ask whether oN identifies order number reference in this directory context. The immediate quality checkpoint is: separate the reference type from the reference value. Do not advance this field simply because a fluent translation has been proposed.

A reusable deliverable for this step is a compact row containing the original value, its operational role, the target-language label, a link to the specification, and the reviewer decision. Such rows are small enough to audit and rich enough to prevent an unresolved assumption from disappearing during editing. In later projects, this record also supports training and regression tests.

Step 6: Classify every text span

Mark fields as stable machine code, translatable human description, potentially translatable free text, identifier, numeric data, controlled vocabulary or uncertain. Do not infer that a value is translatable merely because it contains English-looking letters. Request authority for the uncertain class. For UN/EDIFACT DESADV despatch advice messages, place CPS+3+1' in the working register and ask whether package hierarchy relates a child grouping to its parent. The immediate quality checkpoint is: draw the package tree before translating handling instructions. Do not advance this field simply because a fluent translation has been proposed.

A reusable deliverable for this step is a compact row containing the original value, its operational role, the target-language label, a link to the specification, and the reviewer decision. Such rows are small enough to audit and rich enough to prevent an unresolved assumption from disappearing during editing. In later projects, this record also supports training and regression tests.

Step 7: Translate the operational meaning

Write a natural explanation of who does what, to which object, under which condition and at which stage. Keep quantities, polarity, role and scope explicit. If two target-language terms seem possible, choose the one that preserves the process distinction and document why. For UN/EDIFACT DESADV despatch advice messages, place PAC+12' in the working register and ask whether package count belongs to its segment-level context. The immediate quality checkpoint is: read placement and unit relations around PAC. Do not advance this field simply because a fluent translation has been proposed.

A reusable deliverable for this step is a compact row containing the original value, its operational role, the target-language label, a link to the specification, and the reviewer decision. Such rows are small enough to audit and rich enough to prevent an unresolved assumption from disappearing during editing. In later projects, this record also supports training and regression tests.

Step 8: Make an aligned bilingual mapping

Use source key, proposed label, context, justification, owner and status fields. This separates the immutable source value from the display phrase. For each name, link back to a unique identifier so reviewers can discuss meaning without corrupting the original data. For UN/EDIFACT DESADV despatch advice messages, place LIN+1++SKU-A47:SA' in the working register and ask whether line number and article code identify an item. The immediate quality checkpoint is: translate the accompanying description but not the item key. Do not advance this field simply because a fluent translation has been proposed.

A reusable deliverable for this step is a compact row containing the original value, its operational role, the target-language label, a link to the specification, and the reviewer decision. Such rows are small enough to audit and rich enough to prevent an unresolved assumption from disappearing during editing. In later projects, this record also supports training and regression tests.

Step 9: Run structural and semantic checks separately

Structural review asks whether identifiers, paths, order and machine types still match. Semantic review asks whether the translated words preserve meaning, roles, distinctions and expected actions. Neither test replaces the other. A file can parse and still mislead; a phrase can read well and still break the workflow. For UN/EDIFACT DESADV despatch advice messages, place QTY+12:240:PCE' in the working register and ask whether quantity qualifier and unit contextualise the value. The immediate quality checkpoint is: check qualifier, unit code, line scope and received evidence. Do not advance this field simply because a fluent translation has been proposed.

A reusable deliverable for this step is a compact row containing the original value, its operational role, the target-language label, a link to the specification, and the reviewer decision. Such rows are small enough to audit and rich enough to prevent an unresolved assumption from disappearing during editing. In later projects, this record also supports training and regression tests.

Step 10: Exercise realistic edge cases

Test missing values, duplicates, nested objects, unusual language directions, empty fields and out-of-order observations. Include a case where the value looks ordinary but is a control token. Record what a renderer, reader or downstream operator actually does rather than assuming it from the translated prose. For UN/EDIFACT DESADV despatch advice messages, place MEA+AAE+G+KGM:580' in the working register and ask whether measurement category, dimension and unit determine meaning. The immediate quality checkpoint is: preserve KGM as data and label ‘gross weight’ only after decode. Do not advance this field simply because a fluent translation has been proposed.

A reusable deliverable for this step is a compact row containing the original value, its operational role, the target-language label, a link to the specification, and the reviewer decision. Such rows are small enough to audit and rich enough to prevent an unresolved assumption from disappearing during editing. In later projects, this record also supports training and regression tests.

Step 11: Review with a second discipline

Ask one language reviewer to focus on clarity and one domain reviewer to focus on technical identity. Present each reviewer with source, translation, invariants and evidence. An expert who sees only the translated paragraph may miss a link that was silently severed. For UN/EDIFACT DESADV despatch advice messages, place CNT+2:14' in the working register and ask whether summary counters can support reconciliation. The immediate quality checkpoint is: check control total meaning against line and package detail. Do not advance this field simply because a fluent translation has been proposed.

A reusable deliverable for this step is a compact row containing the original value, its operational role, the target-language label, a link to the specification, and the reviewer decision. Such rows are small enough to audit and rich enough to prevent an unresolved assumption from disappearing during editing. In later projects, this record also supports training and regression tests.

Step 12: Release a traceable edition and transfer learning

Publish the display translation or explanatory guide with version, source reference, unresolved questions and test outcomes. Keep a glossary limited to this domain and a regression suite of representative cases. When a source revision arrives, compare changed fields rather than blindly rewriting every surviving label. For UN/EDIFACT DESADV despatch advice messages, place UNT+47+42' in the working register and ask whether trailer counts segments and repeats message reference. The immediate quality checkpoint is: never modify the wire payload in a translation-only job. Do not advance this field simply because a fluent translation has been proposed.

A reusable deliverable for this step is a compact row containing the original value, its operational role, the target-language label, a link to the specification, and the reviewer decision. Such rows are small enough to audit and rich enough to prevent an unresolved assumption from disappearing during editing. In later projects, this record also supports training and regression tests.

Worked examples: interpret, translate, verify

The following scenarios are constructed teaching examples. They show how to read a source field, identify what may be translated and detect a mistaken interpretation. They are not authenticated shipping transactions, archive records, production image files or live control messages. Always check the precise standard edition and local implementation for a real submission.

Worked example 1: UNA service-string advice

Source specimen: UNA:+.? '. What it establishes: This introduces delimiters, not a prose sentence. Start by identifying the object’s scope and the authority for interpreting this field. Describe what a new reader should learn from it before deciding where to put the translated words. The target text should explain the function of the value, not silently convert the value into a different kind of evidence.

Tempting but wrong interpretation: Changing punctuation breaks parsing. The error may look harmless in a glossary because the surrounding words remain natural. In an actual workflow, however, the affected party could sort, route, render, approve or reject something based on the wrong assumption. Keep the source specimen as a frozen reference; if an example is hypothetical, make that status visible to the reader rather than implying it comes from a verified transaction.

Correct translation decision: Read exact delimiters before extracting translatable free text. The editor should preserve the technical key in the data and provide a separate human-readable explanation naming the field’s role. A domain reviewer then confirms the explanation from the relevant standard and the local producer’s implementation. If the specification alone does not settle the question, the correct output is a qualified note and a request for the missing profile, not an invented rule.

Quality check and transfer: ask a second reader to locate the same record with only the identifiers available; ask a language reviewer to paraphrase the human explanation without seeing the first draft; and ask a technical reviewer to state one realistic failure that the translation must prevent. If the two reviewers disagree, reopen this example and document the specific claim under dispute. The lesson transfers to any multilingual structured record whose labels are easier to change than its underlying relationships.

Worked example 2: UNB interchange header

Source specimen: UNB+UNOC:3+SENDER+RECEIVER+261118:0800+ABC19'. What it establishes: Header communicates interchange parties and control reference. Start by identifying the object’s scope and the authority for interpreting this field. Describe what a new reader should learn from it before deciding where to put the translated words. The target text should explain the function of the value, not silently convert the value into a different kind of evidence.

Tempting but wrong interpretation: Translating SENDER or changing ABC19 breaks routing and acknowledgements. The error may look harmless in a glossary because the surrounding words remain natural. In an actual workflow, however, the affected party could sort, route, render, approve or reject something based on the wrong assumption. Keep the source specimen as a frozen reference; if an example is hypothetical, make that status visible to the reader rather than implying it comes from a verified transaction.

Correct translation decision: Keep identifier bytes; add human explanation outside payload. The editor should preserve the technical key in the data and provide a separate human-readable explanation naming the field’s role. A domain reviewer then confirms the explanation from the relevant standard and the local producer’s implementation. If the specification alone does not settle the question, the correct output is a qualified note and a request for the missing profile, not an invented rule.

Quality check and transfer: ask a second reader to locate the same record with only the identifiers available; ask a language reviewer to paraphrase the human explanation without seeing the first draft; and ask a technical reviewer to state one realistic failure that the translation must prevent. If the two reviewers disagree, reopen this example and document the specific claim under dispute. The lesson transfers to any multilingual structured record whose labels are easier to change than its underlying relationships.

Worked example 3: UNH message identification

Source specimen: UNH+42+DESADV:D:96A:UN'. What it establishes: This is a DESADV under a specific directory release. Start by identifying the object’s scope and the authority for interpreting this field. Describe what a new reader should learn from it before deciding where to put the translated words. The target text should explain the function of the value, not silently convert the value into a different kind of evidence.

Tempting but wrong interpretation: Calling this an invoice changes the business-document type. The error may look harmless in a glossary because the surrounding words remain natural. In an actual workflow, however, the affected party could sort, route, render, approve or reject something based on the wrong assumption. Keep the source specimen as a frozen reference; if an example is hypothetical, make that status visible to the reader rather than implying it comes from a verified transaction.

Correct translation decision: Record version and message reference separately. The editor should preserve the technical key in the data and provide a separate human-readable explanation naming the field’s role. A domain reviewer then confirms the explanation from the relevant standard and the local producer’s implementation. If the specification alone does not settle the question, the correct output is a qualified note and a request for the missing profile, not an invented rule.

Quality check and transfer: ask a second reader to locate the same record with only the identifiers available; ask a language reviewer to paraphrase the human explanation without seeing the first draft; and ask a technical reviewer to state one realistic failure that the translation must prevent. If the two reviewers disagree, reopen this example and document the specific claim under dispute. The lesson transfers to any multilingual structured record whose labels are easier to change than its underlying relationships.

Worked example 4: BGM document identity

Source specimen: BGM+351+DA2026-884+9'. What it establishes: A despatch advice number identifies a particular notice. Start by identifying the object’s scope and the authority for interpreting this field. Describe what a new reader should learn from it before deciding where to put the translated words. The target text should explain the function of the value, not silently convert the value into a different kind of evidence.

Tempting but wrong interpretation: Treating the number as a purchase order misstates evidence. The error may look harmless in a glossary because the surrounding words remain natural. In an actual workflow, however, the affected party could sort, route, render, approve or reject something based on the wrong assumption. Keep the source specimen as a frozen reference; if an example is hypothetical, make that status visible to the reader rather than implying it comes from a verified transaction.

Correct translation decision: Keep document identifier immutable and translate descriptive field labels. The editor should preserve the technical key in the data and provide a separate human-readable explanation naming the field’s role. A domain reviewer then confirms the explanation from the relevant standard and the local producer’s implementation. If the specification alone does not settle the question, the correct output is a qualified note and a request for the missing profile, not an invented rule.

Quality check and transfer: ask a second reader to locate the same record with only the identifiers available; ask a language reviewer to paraphrase the human explanation without seeing the first draft; and ask a technical reviewer to state one realistic failure that the translation must prevent. If the two reviewers disagree, reopen this example and document the specific claim under dispute. The lesson transfers to any multilingual structured record whose labels are easier to change than its underlying relationships.

Worked example 5: DTM qualifier and format

Source specimen: DTM+137:20261118:102'. What it establishes: Qualifier and format code govern which date this is. Start by identifying the object’s scope and the authority for interpreting this field. Describe what a new reader should learn from it before deciding where to put the translated words. The target text should explain the function of the value, not silently convert the value into a different kind of evidence.

Tempting but wrong interpretation: Treating 20261118 as local time invents a clock and zone. The error may look harmless in a glossary because the surrounding words remain natural. In an actual workflow, however, the affected party could sort, route, render, approve or reject something based on the wrong assumption. Keep the source specimen as a frozen reference; if an example is hypothetical, make that status visible to the reader rather than implying it comes from a verified transaction.

Correct translation decision: Decode qualifier using directory before natural-language rendering. The editor should preserve the technical key in the data and provide a separate human-readable explanation naming the field’s role. A domain reviewer then confirms the explanation from the relevant standard and the local producer’s implementation. If the specification alone does not settle the question, the correct output is a qualified note and a request for the missing profile, not an invented rule.

Quality check and transfer: ask a second reader to locate the same record with only the identifiers available; ask a language reviewer to paraphrase the human explanation without seeing the first draft; and ask a technical reviewer to state one realistic failure that the translation must prevent. If the two reviewers disagree, reopen this example and document the specific claim under dispute. The lesson transfers to any multilingual structured record whose labels are easier to change than its underlying relationships.

Worked example 6: NAD party-role qualifiers

Source specimen: NAD+BY+BUYER01::9'. What it establishes: BY describes the buyer role. Start by identifying the object’s scope and the authority for interpreting this field. Describe what a new reader should learn from it before deciding where to put the translated words. The target text should explain the function of the value, not silently convert the value into a different kind of evidence.

Tempting but wrong interpretation: Replacing buyer with consignee confuses commercial and physical responsibility. The error may look harmless in a glossary because the surrounding words remain natural. In an actual workflow, however, the affected party could sort, route, render, approve or reject something based on the wrong assumption. Keep the source specimen as a frozen reference; if an example is hypothetical, make that status visible to the reader rather than implying it comes from a verified transaction.

Correct translation decision: Preserve qualifier and look up business-role vocabulary. The editor should preserve the technical key in the data and provide a separate human-readable explanation naming the field’s role. A domain reviewer then confirms the explanation from the relevant standard and the local producer’s implementation. If the specification alone does not settle the question, the correct output is a qualified note and a request for the missing profile, not an invented rule.

Quality check and transfer: ask a second reader to locate the same record with only the identifiers available; ask a language reviewer to paraphrase the human explanation without seeing the first draft; and ask a technical reviewer to state one realistic failure that the translation must prevent. If the two reviewers disagree, reopen this example and document the specific claim under dispute. The lesson transfers to any multilingual structured record whose labels are easier to change than its underlying relationships.

Worked example 7: NAD delivery destination

Source specimen: NAD+DP+SITE-03::9'. What it establishes: Delivery party may be different from buyer. Start by identifying the object’s scope and the authority for interpreting this field. Describe what a new reader should learn from it before deciding where to put the translated words. The target text should explain the function of the value, not silently convert the value into a different kind of evidence.

Tempting but wrong interpretation: Merging DP with BY routes goods to the wrong address. The error may look harmless in a glossary because the surrounding words remain natural. In an actual workflow, however, the affected party could sort, route, render, approve or reject something based on the wrong assumption. Keep the source specimen as a frozen reference; if an example is hypothetical, make that status visible to the reader rather than implying it comes from a verified transaction.

Correct translation decision: Cross-check party-role matrix with the order and receiving site. The editor should preserve the technical key in the data and provide a separate human-readable explanation naming the field’s role. A domain reviewer then confirms the explanation from the relevant standard and the local producer’s implementation. If the specification alone does not settle the question, the correct output is a qualified note and a request for the missing profile, not an invented rule.

Quality check and transfer: ask a second reader to locate the same record with only the identifiers available; ask a language reviewer to paraphrase the human explanation without seeing the first draft; and ask a technical reviewer to state one realistic failure that the translation must prevent. If the two reviewers disagree, reopen this example and document the specific claim under dispute. The lesson transfers to any multilingual structured record whose labels are easier to change than its underlying relationships.

Worked example 8: RFF document reference

Source specimen: RFF+ON:PO-29048'. What it establishes: ON identifies order number reference in this directory context. Start by identifying the object’s scope and the authority for interpreting this field. Describe what a new reader should learn from it before deciding where to put the translated words. The target text should explain the function of the value, not silently convert the value into a different kind of evidence.

Tempting but wrong interpretation: Recasting it as a shipment reference damages reconciliation. The error may look harmless in a glossary because the surrounding words remain natural. In an actual workflow, however, the affected party could sort, route, render, approve or reject something based on the wrong assumption. Keep the source specimen as a frozen reference; if an example is hypothetical, make that status visible to the reader rather than implying it comes from a verified transaction.

Correct translation decision: Separate the reference type from the reference value. The editor should preserve the technical key in the data and provide a separate human-readable explanation naming the field’s role. A domain reviewer then confirms the explanation from the relevant standard and the local producer’s implementation. If the specification alone does not settle the question, the correct output is a qualified note and a request for the missing profile, not an invented rule.

Quality check and transfer: ask a second reader to locate the same record with only the identifiers available; ask a language reviewer to paraphrase the human explanation without seeing the first draft; and ask a technical reviewer to state one realistic failure that the translation must prevent. If the two reviewers disagree, reopen this example and document the specific claim under dispute. The lesson transfers to any multilingual structured record whose labels are easier to change than its underlying relationships.

Worked example 9: CPS package hierarchy

Source specimen: CPS+3+1'. What it establishes: Package hierarchy relates a child grouping to its parent. Start by identifying the object’s scope and the authority for interpreting this field. Describe what a new reader should learn from it before deciding where to put the translated words. The target text should explain the function of the value, not silently convert the value into a different kind of evidence.

Tempting but wrong interpretation: Flattening nested packaging makes carton attribution disappear. The error may look harmless in a glossary because the surrounding words remain natural. In an actual workflow, however, the affected party could sort, route, render, approve or reject something based on the wrong assumption. Keep the source specimen as a frozen reference; if an example is hypothetical, make that status visible to the reader rather than implying it comes from a verified transaction.

Correct translation decision: Draw the package tree before translating handling instructions. The editor should preserve the technical key in the data and provide a separate human-readable explanation naming the field’s role. A domain reviewer then confirms the explanation from the relevant standard and the local producer’s implementation. If the specification alone does not settle the question, the correct output is a qualified note and a request for the missing profile, not an invented rule.

Quality check and transfer: ask a second reader to locate the same record with only the identifiers available; ask a language reviewer to paraphrase the human explanation without seeing the first draft; and ask a technical reviewer to state one realistic failure that the translation must prevent. If the two reviewers disagree, reopen this example and document the specific claim under dispute. The lesson transfers to any multilingual structured record whose labels are easier to change than its underlying relationships.

Worked example 10: PAC package count

Source specimen: PAC+12'. What it establishes: Package count belongs to its segment-level context. Start by identifying the object’s scope and the authority for interpreting this field. Describe what a new reader should learn from it before deciding where to put the translated words. The target text should explain the function of the value, not silently convert the value into a different kind of evidence.

Tempting but wrong interpretation: Reporting 12 individual units instead of 12 packages misleads receiving. The error may look harmless in a glossary because the surrounding words remain natural. In an actual workflow, however, the affected party could sort, route, render, approve or reject something based on the wrong assumption. Keep the source specimen as a frozen reference; if an example is hypothetical, make that status visible to the reader rather than implying it comes from a verified transaction.

Correct translation decision: Read placement and unit relations around PAC. The editor should preserve the technical key in the data and provide a separate human-readable explanation naming the field’s role. A domain reviewer then confirms the explanation from the relevant standard and the local producer’s implementation. If the specification alone does not settle the question, the correct output is a qualified note and a request for the missing profile, not an invented rule.

Quality check and transfer: ask a second reader to locate the same record with only the identifiers available; ask a language reviewer to paraphrase the human explanation without seeing the first draft; and ask a technical reviewer to state one realistic failure that the translation must prevent. If the two reviewers disagree, reopen this example and document the specific claim under dispute. The lesson transfers to any multilingual structured record whose labels are easier to change than its underlying relationships.

Worked example 11: LIN line identifier

Source specimen: LIN+1++SKU-A47:SA'. What it establishes: Line number and article code identify an item. Start by identifying the object’s scope and the authority for interpreting this field. Describe what a new reader should learn from it before deciding where to put the translated words. The target text should explain the function of the value, not silently convert the value into a different kind of evidence.

Tempting but wrong interpretation: Translating SKU-A47 as a description destroys matching. The error may look harmless in a glossary because the surrounding words remain natural. In an actual workflow, however, the affected party could sort, route, render, approve or reject something based on the wrong assumption. Keep the source specimen as a frozen reference; if an example is hypothetical, make that status visible to the reader rather than implying it comes from a verified transaction.

Correct translation decision: Translate the accompanying description but not the item key. The editor should preserve the technical key in the data and provide a separate human-readable explanation naming the field’s role. A domain reviewer then confirms the explanation from the relevant standard and the local producer’s implementation. If the specification alone does not settle the question, the correct output is a qualified note and a request for the missing profile, not an invented rule.

Quality check and transfer: ask a second reader to locate the same record with only the identifiers available; ask a language reviewer to paraphrase the human explanation without seeing the first draft; and ask a technical reviewer to state one realistic failure that the translation must prevent. If the two reviewers disagree, reopen this example and document the specific claim under dispute. The lesson transfers to any multilingual structured record whose labels are easier to change than its underlying relationships.

Worked example 12: QTY qualifier

Source specimen: QTY+12:240:PCE'. What it establishes: Quantity qualifier and unit contextualise the value. Start by identifying the object’s scope and the authority for interpreting this field. Describe what a new reader should learn from it before deciding where to put the translated words. The target text should explain the function of the value, not silently convert the value into a different kind of evidence.

Tempting but wrong interpretation: A count of ordered items is not automatically a shipped count. The error may look harmless in a glossary because the surrounding words remain natural. In an actual workflow, however, the affected party could sort, route, render, approve or reject something based on the wrong assumption. Keep the source specimen as a frozen reference; if an example is hypothetical, make that status visible to the reader rather than implying it comes from a verified transaction.

Correct translation decision: Check qualifier, unit code, line scope and received evidence. The editor should preserve the technical key in the data and provide a separate human-readable explanation naming the field’s role. A domain reviewer then confirms the explanation from the relevant standard and the local producer’s implementation. If the specification alone does not settle the question, the correct output is a qualified note and a request for the missing profile, not an invented rule.

Quality check and transfer: ask a second reader to locate the same record with only the identifiers available; ask a language reviewer to paraphrase the human explanation without seeing the first draft; and ask a technical reviewer to state one realistic failure that the translation must prevent. If the two reviewers disagree, reopen this example and document the specific claim under dispute. The lesson transfers to any multilingual structured record whose labels are easier to change than its underlying relationships.

Worked example 13: MEA consignment measurement

Source specimen: MEA+AAE+G+KGM:580'. What it establishes: Measurement category, dimension and unit determine meaning. Start by identifying the object’s scope and the authority for interpreting this field. Describe what a new reader should learn from it before deciding where to put the translated words. The target text should explain the function of the value, not silently convert the value into a different kind of evidence.

Tempting but wrong interpretation: Treating gross mass as net mass affects transport decisions. The error may look harmless in a glossary because the surrounding words remain natural. In an actual workflow, however, the affected party could sort, route, render, approve or reject something based on the wrong assumption. Keep the source specimen as a frozen reference; if an example is hypothetical, make that status visible to the reader rather than implying it comes from a verified transaction.

Correct translation decision: Preserve KGM as data and label ‘gross weight’ only after decode. The editor should preserve the technical key in the data and provide a separate human-readable explanation naming the field’s role. A domain reviewer then confirms the explanation from the relevant standard and the local producer’s implementation. If the specification alone does not settle the question, the correct output is a qualified note and a request for the missing profile, not an invented rule.

Quality check and transfer: ask a second reader to locate the same record with only the identifiers available; ask a language reviewer to paraphrase the human explanation without seeing the first draft; and ask a technical reviewer to state one realistic failure that the translation must prevent. If the two reviewers disagree, reopen this example and document the specific claim under dispute. The lesson transfers to any multilingual structured record whose labels are easier to change than its underlying relationships.

Worked example 14: CNT control total

Source specimen: CNT+2:14'. What it establishes: Summary counters can support reconciliation. Start by identifying the object’s scope and the authority for interpreting this field. Describe what a new reader should learn from it before deciding where to put the translated words. The target text should explain the function of the value, not silently convert the value into a different kind of evidence.

Tempting but wrong interpretation: Replacing total line count with total pieces violates the summary. The error may look harmless in a glossary because the surrounding words remain natural. In an actual workflow, however, the affected party could sort, route, render, approve or reject something based on the wrong assumption. Keep the source specimen as a frozen reference; if an example is hypothetical, make that status visible to the reader rather than implying it comes from a verified transaction.

Correct translation decision: Check control total meaning against line and package detail. The editor should preserve the technical key in the data and provide a separate human-readable explanation naming the field’s role. A domain reviewer then confirms the explanation from the relevant standard and the local producer’s implementation. If the specification alone does not settle the question, the correct output is a qualified note and a request for the missing profile, not an invented rule.

Quality check and transfer: ask a second reader to locate the same record with only the identifiers available; ask a language reviewer to paraphrase the human explanation without seeing the first draft; and ask a technical reviewer to state one realistic failure that the translation must prevent. If the two reviewers disagree, reopen this example and document the specific claim under dispute. The lesson transfers to any multilingual structured record whose labels are easier to change than its underlying relationships.

Worked example 15: UNT trailer control

Source specimen: UNT+47+42'. What it establishes: Trailer counts segments and repeats message reference. Start by identifying the object’s scope and the authority for interpreting this field. Describe what a new reader should learn from it before deciding where to put the translated words. The target text should explain the function of the value, not silently convert the value into a different kind of evidence.

Tempting but wrong interpretation: Translating a label inside the segment corrupts the count. The error may look harmless in a glossary because the surrounding words remain natural. In an actual workflow, however, the affected party could sort, route, render, approve or reject something based on the wrong assumption. Keep the source specimen as a frozen reference; if an example is hypothetical, make that status visible to the reader rather than implying it comes from a verified transaction.

Correct translation decision: Never modify the wire payload in a translation-only job. The editor should preserve the technical key in the data and provide a separate human-readable explanation naming the field’s role. A domain reviewer then confirms the explanation from the relevant standard and the local producer’s implementation. If the specification alone does not settle the question, the correct output is a qualified note and a request for the missing profile, not an invented rule.

Quality check and transfer: ask a second reader to locate the same record with only the identifiers available; ask a language reviewer to paraphrase the human explanation without seeing the first draft; and ask a technical reviewer to state one realistic failure that the translation must prevent. If the two reviewers disagree, reopen this example and document the specific claim under dispute. The lesson transfers to any multilingual structured record whose labels are easier to change than its underlying relationships.

Common failure modes and their repairs

Failure 1: nad party-role qualifiers is misread

A characteristic failure begins with NAD+BY+BUYER01::9': replacing buyer with consignee confuses commercial and physical responsibility. A surface review may not catch it because the rewritten English still reads smoothly. Repair the problem by returning to field scope and the source version, then apply the discipline: preserve qualifier and look up business-role vocabulary. Keep a before-and-after snapshot of the label and evidence that the protected data did not change.

The prevention test is concrete: give a reviewer the source object and ask which decision would differ if the flawed wording were trusted. Record that answer as a regression condition. A useful quality checklist tracks severity separately from fluency; an incorrect routing, order, unit, link or execution condition must remain a blocker even when the phrasing seems natural.

Failure 2: nad delivery destination is misread

A characteristic failure begins with NAD+DP+SITE-03::9': merging DP with BY routes goods to the wrong address. A surface review may not catch it because the rewritten English still reads smoothly. Repair the problem by returning to field scope and the source version, then apply the discipline: cross-check party-role matrix with the order and receiving site. Keep a before-and-after snapshot of the label and evidence that the protected data did not change.

The prevention test is concrete: give a reviewer the source object and ask which decision would differ if the flawed wording were trusted. Record that answer as a regression condition. A useful quality checklist tracks severity separately from fluency; an incorrect routing, order, unit, link or execution condition must remain a blocker even when the phrasing seems natural.

Failure 3: rff document reference is misread

A characteristic failure begins with RFF+ON:PO-29048': recasting it as a shipment reference damages reconciliation. A surface review may not catch it because the rewritten English still reads smoothly. Repair the problem by returning to field scope and the source version, then apply the discipline: separate the reference type from the reference value. Keep a before-and-after snapshot of the label and evidence that the protected data did not change.

The prevention test is concrete: give a reviewer the source object and ask which decision would differ if the flawed wording were trusted. Record that answer as a regression condition. A useful quality checklist tracks severity separately from fluency; an incorrect routing, order, unit, link or execution condition must remain a blocker even when the phrasing seems natural.

Failure 4: cps package hierarchy is misread

A characteristic failure begins with CPS+3+1': flattening nested packaging makes carton attribution disappear. A surface review may not catch it because the rewritten English still reads smoothly. Repair the problem by returning to field scope and the source version, then apply the discipline: draw the package tree before translating handling instructions. Keep a before-and-after snapshot of the label and evidence that the protected data did not change.

The prevention test is concrete: give a reviewer the source object and ask which decision would differ if the flawed wording were trusted. Record that answer as a regression condition. A useful quality checklist tracks severity separately from fluency; an incorrect routing, order, unit, link or execution condition must remain a blocker even when the phrasing seems natural.

Failure 5: pac package count is misread

A characteristic failure begins with PAC+12': reporting 12 individual units instead of 12 packages misleads receiving. A surface review may not catch it because the rewritten English still reads smoothly. Repair the problem by returning to field scope and the source version, then apply the discipline: read placement and unit relations around PAC. Keep a before-and-after snapshot of the label and evidence that the protected data did not change.

The prevention test is concrete: give a reviewer the source object and ask which decision would differ if the flawed wording were trusted. Record that answer as a regression condition. A useful quality checklist tracks severity separately from fluency; an incorrect routing, order, unit, link or execution condition must remain a blocker even when the phrasing seems natural.

Failure 6: lin line identifier is misread

A characteristic failure begins with LIN+1++SKU-A47:SA': translating SKU-A47 as a description destroys matching. A surface review may not catch it because the rewritten English still reads smoothly. Repair the problem by returning to field scope and the source version, then apply the discipline: translate the accompanying description but not the item key. Keep a before-and-after snapshot of the label and evidence that the protected data did not change.

The prevention test is concrete: give a reviewer the source object and ask which decision would differ if the flawed wording were trusted. Record that answer as a regression condition. A useful quality checklist tracks severity separately from fluency; an incorrect routing, order, unit, link or execution condition must remain a blocker even when the phrasing seems natural.

Failure 7: qty qualifier is misread

A characteristic failure begins with QTY+12:240:PCE': a count of ordered items is not automatically a shipped count. A surface review may not catch it because the rewritten English still reads smoothly. Repair the problem by returning to field scope and the source version, then apply the discipline: check qualifier, unit code, line scope and received evidence. Keep a before-and-after snapshot of the label and evidence that the protected data did not change.

The prevention test is concrete: give a reviewer the source object and ask which decision would differ if the flawed wording were trusted. Record that answer as a regression condition. A useful quality checklist tracks severity separately from fluency; an incorrect routing, order, unit, link or execution condition must remain a blocker even when the phrasing seems natural.

Failure 8: mea consignment measurement is misread

A characteristic failure begins with MEA+AAE+G+KGM:580': treating gross mass as net mass affects transport decisions. A surface review may not catch it because the rewritten English still reads smoothly. Repair the problem by returning to field scope and the source version, then apply the discipline: preserve KGM as data and label ‘gross weight’ only after decode. Keep a before-and-after snapshot of the label and evidence that the protected data did not change.

The prevention test is concrete: give a reviewer the source object and ask which decision would differ if the flawed wording were trusted. Record that answer as a regression condition. A useful quality checklist tracks severity separately from fluency; an incorrect routing, order, unit, link or execution condition must remain a blocker even when the phrasing seems natural.

Failure 9: cnt control total is misread

A characteristic failure begins with CNT+2:14': replacing total line count with total pieces violates the summary. A surface review may not catch it because the rewritten English still reads smoothly. Repair the problem by returning to field scope and the source version, then apply the discipline: check control total meaning against line and package detail. Keep a before-and-after snapshot of the label and evidence that the protected data did not change.

The prevention test is concrete: give a reviewer the source object and ask which decision would differ if the flawed wording were trusted. Record that answer as a regression condition. A useful quality checklist tracks severity separately from fluency; an incorrect routing, order, unit, link or execution condition must remain a blocker even when the phrasing seems natural.

Failure 10: unt trailer control is misread

A characteristic failure begins with UNT+47+42': translating a label inside the segment corrupts the count. A surface review may not catch it because the rewritten English still reads smoothly. Repair the problem by returning to field scope and the source version, then apply the discipline: never modify the wire payload in a translation-only job. Keep a before-and-after snapshot of the label and evidence that the protected data did not change.

The prevention test is concrete: give a reviewer the source object and ask which decision would differ if the flawed wording were trusted. Record that answer as a regression condition. A useful quality checklist tracks severity separately from fluency; an incorrect routing, order, unit, link or execution condition must remain a blocker even when the phrasing seems natural.

Practice workshop: independent decisions and explained answers

Try each problem without looking at its solution. Make a two-column note: what is stable source data, and what may be changed for clarity? Then describe the test you would use to prove that the answer is right. The exercise is not to produce the prettiest sentence; it is to preserve an actionable meaning while showing your work.

Exercise 1: UNB interchange header

Task: Your colleague proposes to translate or normalize UNB+UNOC:3+SENDER+RECEIVER+261118:0800+ABC19' in a training guide. Identify one protected element, draft an accurate explanation for an unfamiliar reader, and specify the minimum evidence needed before publication. Imagine that the recipient will act on the guide tomorrow without access to the original editor.

Model reasoning: Header communicates interchange parties and control reference. Therefore keep identifier bytes; add human explanation outside payload. An unacceptable shortcut would be translating SENDER or changing ABC19 breaks routing and acknowledgements. The evidence must include the source occurrence, a verified field definition, the selected target-language wording and a test showing unchanged relationships. If a required assumption remains unverified, label it as unresolved and block that particular assertion from a definitive release.

Exercise 2: BGM document identity

Task: Your colleague proposes to translate or normalize BGM+351+DA2026-884+9' in a training guide. Identify one protected element, draft an accurate explanation for an unfamiliar reader, and specify the minimum evidence needed before publication. Imagine that the recipient will act on the guide tomorrow without access to the original editor.

Model reasoning: A despatch advice number identifies a particular notice. Therefore keep document identifier immutable and translate descriptive field labels. An unacceptable shortcut would be treating the number as a purchase order misstates evidence. The evidence must include the source occurrence, a verified field definition, the selected target-language wording and a test showing unchanged relationships. If a required assumption remains unverified, label it as unresolved and block that particular assertion from a definitive release.

Exercise 3: NAD party-role qualifiers

Task: Your colleague proposes to translate or normalize NAD+BY+BUYER01::9' in a training guide. Identify one protected element, draft an accurate explanation for an unfamiliar reader, and specify the minimum evidence needed before publication. Imagine that the recipient will act on the guide tomorrow without access to the original editor.

Model reasoning: BY describes the buyer role. Therefore preserve qualifier and look up business-role vocabulary. An unacceptable shortcut would be replacing buyer with consignee confuses commercial and physical responsibility. The evidence must include the source occurrence, a verified field definition, the selected target-language wording and a test showing unchanged relationships. If a required assumption remains unverified, label it as unresolved and block that particular assertion from a definitive release.

Exercise 4: RFF document reference

Task: Your colleague proposes to translate or normalize RFF+ON:PO-29048' in a training guide. Identify one protected element, draft an accurate explanation for an unfamiliar reader, and specify the minimum evidence needed before publication. Imagine that the recipient will act on the guide tomorrow without access to the original editor.

Model reasoning: ON identifies order number reference in this directory context. Therefore separate the reference type from the reference value. An unacceptable shortcut would be recasting it as a shipment reference damages reconciliation. The evidence must include the source occurrence, a verified field definition, the selected target-language wording and a test showing unchanged relationships. If a required assumption remains unverified, label it as unresolved and block that particular assertion from a definitive release.

Exercise 5: PAC package count

Task: Your colleague proposes to translate or normalize PAC+12' in a training guide. Identify one protected element, draft an accurate explanation for an unfamiliar reader, and specify the minimum evidence needed before publication. Imagine that the recipient will act on the guide tomorrow without access to the original editor.

Model reasoning: Package count belongs to its segment-level context. Therefore read placement and unit relations around PAC. An unacceptable shortcut would be reporting 12 individual units instead of 12 packages misleads receiving. The evidence must include the source occurrence, a verified field definition, the selected target-language wording and a test showing unchanged relationships. If a required assumption remains unverified, label it as unresolved and block that particular assertion from a definitive release.

Exercise 6: QTY qualifier

Task: Your colleague proposes to translate or normalize QTY+12:240:PCE' in a training guide. Identify one protected element, draft an accurate explanation for an unfamiliar reader, and specify the minimum evidence needed before publication. Imagine that the recipient will act on the guide tomorrow without access to the original editor.

Model reasoning: Quantity qualifier and unit contextualise the value. Therefore check qualifier, unit code, line scope and received evidence. An unacceptable shortcut would be a count of ordered items is not automatically a shipped count. The evidence must include the source occurrence, a verified field definition, the selected target-language wording and a test showing unchanged relationships. If a required assumption remains unverified, label it as unresolved and block that particular assertion from a definitive release.

Exercise 7: CNT control total

Task: Your colleague proposes to translate or normalize CNT+2:14' in a training guide. Identify one protected element, draft an accurate explanation for an unfamiliar reader, and specify the minimum evidence needed before publication. Imagine that the recipient will act on the guide tomorrow without access to the original editor.

Model reasoning: Summary counters can support reconciliation. Therefore check control total meaning against line and package detail. An unacceptable shortcut would be replacing total line count with total pieces violates the summary. The evidence must include the source occurrence, a verified field definition, the selected target-language wording and a test showing unchanged relationships. If a required assumption remains unverified, label it as unresolved and block that particular assertion from a definitive release.

Exercise 8: UNA service-string advice

Task: Your colleague proposes to translate or normalize UNA:+.? ' in a training guide. Identify one protected element, draft an accurate explanation for an unfamiliar reader, and specify the minimum evidence needed before publication. Imagine that the recipient will act on the guide tomorrow without access to the original editor.

Model reasoning: This introduces delimiters, not a prose sentence. Therefore read exact delimiters before extracting translatable free text. An unacceptable shortcut would be changing punctuation breaks parsing. The evidence must include the source occurrence, a verified field definition, the selected target-language wording and a test showing unchanged relationships. If a required assumption remains unverified, label it as unresolved and block that particular assertion from a definitive release.

Frequently asked questions

Should I translate the codes themselves?

Usually not when they are defined as machine identifiers, syntax tokens or references. First check the schema and local implementation. Translate the associated explanation instead. Even an English-looking key may be used by software as an exact-match string, so a good translator treats the code as evidence to preserve rather than prose to improve. For a concrete check here, consider UNA:+.? ': read exact delimiters before extracting translatable free text.

Can a translation be linguistically correct but technically wrong?

Yes. An elegant sentence can associate a value with the wrong party, stage or file. The practical distinction is between grammatical acceptability and operational equivalence. Both require review. For technical records the latter also means stable identifiers, cross-references, units, scope, ordering and conditions, not just reasonable wording. For a concrete check here, consider BGM+351+DA2026-884+9': keep document identifier immutable and translate descriptive field labels.

What if the source is missing a local implementation profile?

Do not pretend the public standard defines every local convention. Preserve raw values, translate clearly identified general terms and mark profile-dependent explanations as provisional. Ask the owning team to supply the profile or a validated example. Do not let an unresolved uncertainty turn into a positive factual assertion through stylistic editing. For a concrete check here, consider NAD+DP+SITE-03::9': cross-check party-role matrix with the order and receiving site.

How do I handle terms with no short target-language equivalent?

Use a concise natural description at first mention, followed by the stable source term or code when helpful. In dense tables, prefer a short approved label with a nearby glossary entry. The goal is stable comprehension; inventing a terse but false synonym harms both learners and experts. For a concrete check here, consider PAC+12': read placement and unit relations around PAC.

Can AI translation tools process this format directly?

They can assist with explanatory prose, but a generative output is not a structural validator. Extract permitted text spans, keep machine keys protected, compare source and target fields and conduct domain review. Never infer a safe production change solely from a plausible generated paraphrase. For a concrete check here, consider MEA+AAE+G+KGM:580': preserve KGM as data and label ‘gross weight’ only after decode.

How should a glossary be organised?

Make it key-aware. Record the concept, its source identifier, exact target phrase, prohibited near-synonyms, scope, edition and reviewer. A generic alphabetical glossary without source keys can accidentally merge two different concepts that merely share a similar English word. For a concrete check here, consider UNA:+.? ': read exact delimiters before extracting translatable free text.

What counts as final quality assurance?

A credible release contains a source-to-target map, a no-change report for protected fields, a semantic review of material decisions, representative edge-case tests and a named owner for unresolved questions. It should tell a new reviewer where a translation came from and which assumptions were checked. For a concrete check here, consider BGM+351+DA2026-884+9': keep document identifier immutable and translate descriptive field labels.

How should beginners practise without production access?

Use constructed sample records, mark them as educational and compare every field against official public documentation. Practice naming the actor, object, action, time, qualification and evidence limit. Do not fabricate realistic-looking production credentials or assert that an untested example is valid for every implementation. For a concrete check here, consider NAD+DP+SITE-03::9': cross-check party-role matrix with the order and receiving site.

Which other translation articles should I read?

Start with the linked series owners for the nearest adjacent skill, then use the Vocabulary hub for precision of meaning and How English Works for sentence-level clarity. The present guide owns only this particular structured-record problem; those routes teach related concepts without repeating the same canonical job. For a concrete check here, consider PAC+12': read placement and unit relations around PAC.

A practical release checklist

  1. Source and implementation edition recorded.
  2. Protected keys, structural fields, numeric values and links inventoried.
  3. Translatable text spans extracted rather than edited blindly in the source object.
  4. Role, time, scope, unit and hierarchy understood from the correct context.
  5. Terminology reviewed for false synonyms and unapproved expansions.
  6. Translated labels mapped back to stable source identifiers.
  7. Structural checks passed without unintended changes.
  8. Semantic checks performed by a language reviewer and domain reviewer.
  9. Ambiguities and local-profile dependencies recorded visibly.
  10. Final guide published with evidence, version and a transfer plan.

Further reading: authoritative references and next routes

For the technical definitions and version-specific restrictions, use UNECE DESADV D.96A segment definitions and UNECE DESADV message overview. These are the primary references for the present canonical job. Treat vendor examples and local policy as supplementary evidence, not substitutes for a documented implementation profile. Standards and recommendations can evolve; re-check them when a new software or content version is deployed.

To continue learning without confusing adjacent topics, read Financial Statements and Accounting Disclosures and Markdown Documentation and Link Targets. For general word meaning, morphology and retrieval, visit the eduKateSG Vocabulary Learning Hub. For broader English sentence structure and readable explanation, see How English Works. These routes support the translator’s language judgement while this article retains the separate job of preserving structured technical meaning.

The durable lesson is straightforward. Keep the source object and every protected reference intact, place translated words in the correct human-facing location, and make every important interpretation defensible. The work is complete when a reader can understand the same relevant facts, a downstream system can still interpret the same structure, and a future editor can audit how both outcomes were achieved.