Translate EORI, MRN & Customs References | Preserve Trader and Movement Identity

To translate EORI numbers, MRNs and customs declaration references accurately, a translator must separate trader identity from shipment or declaration identity and from commodity classification. Customs forms, transit documents, export records, freight instructions and compliance files can contain company names, EORI numbers, Movement Reference Numbers, declaration types, office codes and commodity codes in the same record. The human-language descriptions may need translation; the official customs identifiers generally must remain exact. A single changed character can attach the target document to the wrong trader or customs movement.

This guide explains how to translate EU customs and trade documents without changing EORI numbers, Movement Reference Numbers or customs declaration references. It solves one distinct high-intent search problem: what does EORI identify, what does an MRN identify, how are customs reference numbers different from HS or tariff codes, which parts can be localized, and how can multilingual trade documentation preserve the same economic operator and movement after translation?

The working rule is translate the customs prose, preserve official identifiers, identify the system and event behind each reference, and verify every relationship after export. The European Commission states that an EORI number uniquely identifies an economic operator or other person for EU customs purposes and consists of a two-letter issuing-country code plus a national unique identifier of up to 15 alphanumeric characters. The Commission’s MRN follow-up service describes the Movement Reference Number as a unique customs identifier used to track customs movements and declarations. This specialist branch connects to Master Art of Translation, the protected Vocabulary Learning Hub, and How English Works without replacing the existing HS-code or broad shipping/customs owners.

Three customs layers must stay separate

A trade record can contain trader identity, movement identity and goods classification at the same time. Calling every code a customs number makes the document ambiguous. Map EORI, MRN and commodity-code fields separately. Treat the party or goods description as translatable, the official customs identifier as protected, and the role or procedure relationship as something to verify after export. This prevents a correct-looking EORI or MRN from being attached to the wrong trader or movement.

Before release, ask what the field identifies: person, declaration, customs office, procedure, commodity or commercial document. The target should make that scope visible instead of relying on the code’s appearance.

EORI identifies the economic operator

The EU EORI system uniquely identifies economic operators and certain other persons for customs interactions. It does not identify a shipment or commodity. Preserve the EORI as trader identity. The practical test is system traceability. A reviewer using only the target should be able to validate the same economic operator or follow the same customs movement without guessing which reference was intended.

EORI is mandatory in many EU customs operations

The European Commission requires EORI use for import, export, transit and related customs activities where applicable. Replacing it with a company tax number can break customs identification. Use the assigned EORI. For files and declarations, store EORI and MRN as text with explicit field names and exclude them from locale formatting, automatic numbering and generative rewriting. Translation can then change the language around stable customs data.

One valid EORI per person at a time

The Commission states that a person can have only one valid EORI number at a point in time. Creating localized variants of one EORI undermines uniqueness. Preserve one authoritative value. A strong reviewer checks both directions: from the target party or movement to the official identifier, and from the identifier back to the same trader, procedure and date. This catches row-shift errors that character comparison alone misses.

EORI begins with issuing-country code

The EORI format starts with the two-letter code of the EU country that assigned it. Translating that prefix into a local abbreviation changes the identifier. Keep the official two-letter code. Treat the party or goods description as translatable, the official customs identifier as protected, and the role or procedure relationship as something to verify after export. This prevents a correct-looking EORI or MRN from being attached to the wrong trader or movement.

EORI national part can be up to 15 alphanumeric characters

The second part is an identifier unique within the issuing Member State. Spacing or punctuation changes can make validation fail. Copy the complete EORI as assigned. The practical test is system traceability. A reviewer using only the target should be able to validate the same economic operator or follow the same customs movement without guessing which reference was intended.

EORI is not simply a VAT number

Some national implementations can use existing tax or statistical identifiers as a basis, but EORI is an EU customs identifier with its own full format. Dropping the country prefix or relabeling the number as VAT can misstate the record. Keep EORI and VAT fields separate. For files and declarations, store EORI and MRN as text with explicit field names and exclude them from locale formatting, automatic numbering and generative rewriting. Translation can then change the language around stable customs data.

EORI is not a company registration number

A legal entity can have corporate registration, tax and customs identifiers simultaneously. Using the company number as EORI because the digits resemble one another is unsafe. Preserve each namespace. A strong reviewer checks both directions: from the target party or movement to the official identifier, and from the identifier back to the same trader, procedure and date. This catches row-shift errors that character comparison alone misses.

EORI can be validated independently

EU services allow checking whether an EORI is valid. A plausible-looking string should not be accepted only because the company name matches. Use official validation where appropriate. Treat the party or goods description as translatable, the official customs identifier as protected, and the role or procedure relationship as something to verify after export. This prevents a correct-looking EORI or MRN from being attached to the wrong trader or movement.

Company name can be translated or transliterated separately

The economic operator’s legal or trading name is human-readable identity. Changing the name does not authorize changing the EORI. Keep corporate naming and customs identity distinct. The practical test is system traceability. A reviewer using only the target should be able to validate the same economic operator or follow the same customs movement without guessing which reference was intended.

Address can change while EORI identity persists

Business addresses may be updated in registration data. An old customs document should not be silently rewritten with a new address. Preserve source-period data. For files and declarations, store EORI and MRN as text with explicit field names and exclude them from locale formatting, automatic numbering and generative rewriting. Translation can then change the language around stable customs data.

Invalidation is not expiration

EORI numbers do not have an ordinary expiry date, though they can be invalidated in defined circumstances. Translating invalidated as expired can misstate status. Use precise status terminology. A strong reviewer checks both directions: from the target party or movement to the official identifier, and from the identifier back to the same trader, procedure and date. This catches row-shift errors that character comparison alone misses.

MRN identifies a customs movement or declaration context

The Movement Reference Number is used to track customs processing and movements. It is not the trader’s identity. Keep EORI and MRN labels separate. Treat the party or goods description as translatable, the official customs identifier as protected, and the role or procedure relationship as something to verify after export. This prevents a correct-looking EORI or MRN from being attached to the wrong trader or movement.

MRN is generated by the customs system

An MRN is created for a customs operation or declaration rather than chosen by the trader. Translating or reformatting it destroys the system reference. Treat it as protected data. The practical test is system traceability. A reviewer using only the target should be able to validate the same economic operator or follow the same customs movement without guessing which reference was intended.

MRN uses an 18-character structure in EU systems

EU customs documentation uses an 18-character MRN with structured year, country, unique-operation and check elements. Removing letters because a page calls it an 18-digit number can corrupt the actual alphanumeric structure. Preserve all characters exactly. For files and declarations, store EORI and MRN as text with explicit field names and exclude them from locale formatting, automatic numbering and generative rewriting. Translation can then change the language around stable customs data.

MRN year component carries chronology

The leading portion can encode the year of acceptance in relevant MRN structures. Changing the year to match invoice or shipment date can create another reference. Do not harmonize dates inside identifiers. A strong reviewer checks both directions: from the target party or movement to the official identifier, and from the identifier back to the same trader, procedure and date. This catches row-shift errors that character comparison alone misses.

MRN country code belongs to the identifier

The customs country element forms part of the MRN structure. Translating the country code into another abbreviation breaks the reference. Preserve the official code. Treat the party or goods description as translatable, the official customs identifier as protected, and the role or procedure relationship as something to verify after export. This prevents a correct-looking EORI or MRN from being attached to the wrong trader or movement.

MRN unique-operation component is not translatable

The central alphanumeric sequence identifies the customs operation within the system. Readable letters inside it are not words. Lock the string. The practical test is system traceability. A reviewer using only the target should be able to validate the same economic operator or follow the same customs movement without guessing which reference was intended.

MRN check character helps validation

The final position can support integrity checking under the relevant specification. Dropping it because it looks separate makes the MRN incomplete. Preserve the complete reference. For files and declarations, store EORI and MRN as text with explicit field names and exclude them from locale formatting, automatic numbering and generative rewriting. Translation can then change the language around stable customs data.

MRN can be used for status follow-up

EU services allow traders and officers to follow movements using the MRN. A target document with an altered MRN cannot retrieve the same movement. Test lookup where appropriate. A strong reviewer checks both directions: from the target party or movement to the official identifier, and from the identifier back to the same trader, procedure and date. This catches row-shift errors that character comparison alone misses.

Import, export and transit contexts can all use customs references

Different EU customs systems and procedures can generate MRNs or related references. Calling every MRN an export number can be misleading. Translate the procedure label as well as preserving the reference. Treat the party or goods description as translatable, the official customs identifier as protected, and the role or procedure relationship as something to verify after export. This prevents a correct-looking EORI or MRN from being attached to the wrong trader or movement.

Transit MRN is not trader identity

NCTS movements can have MRNs while traders carry EORIs. The same trader can have many movements. Do not merge movement and operator records. The practical test is system traceability. A reviewer using only the target should be able to validate the same economic operator or follow the same customs movement without guessing which reference was intended.

Export MRN can follow one declaration event

Export systems can assign an MRN to accepted declarations. A later document may cite the same reference. Preserve cross-document continuity. For files and declarations, store EORI and MRN as text with explicit field names and exclude them from locale formatting, automatic numbering and generative rewriting. Translation can then change the language around stable customs data.

Declaration reference and MRN can differ by workflow

Some documents contain internal declaration IDs, local reference numbers and the official MRN. A translator can mistake the first visible number for the official movement reference. Keep field names and namespaces explicit. A strong reviewer checks both directions: from the target party or movement to the official identifier, and from the identifier back to the same trader, procedure and date. This catches row-shift errors that character comparison alone misses.

Local Reference Number can be another layer

Traders or systems can use local reference numbers before or alongside official customs references. LRN-like fields are not automatically MRNs. Preserve the source label and purpose. Treat the party or goods description as translatable, the official customs identifier as protected, and the role or procedure relationship as something to verify after export. This prevents a correct-looking EORI or MRN from being attached to the wrong trader or movement.

Customs office identifiers are separate codes

Declarations can contain office-of-export, office-of-destination or other customs-office codes. Those identify offices, not traders or movements. Keep office code and MRN separate. The practical test is system traceability. A reviewer using only the target should be able to validate the same economic operator or follow the same customs movement without guessing which reference was intended.

Declaration type is structured customs data

Import, export, transit and procedure types can use controlled codes. Translating a procedure code as ordinary text can break machine processing. Translate descriptions, preserve codes. For files and declarations, store EORI and MRN as text with explicit field names and exclude them from locale formatting, automatic numbering and generative rewriting. Translation can then change the language around stable customs data.

Procedure codes are not commodity codes

Customs procedure codes describe the treatment requested or previous procedure. HS or commodity codes classify goods. Do not merge procedure and tariff fields. A strong reviewer checks both directions: from the target party or movement to the official identifier, and from the identifier back to the same trader, procedure and date. This catches row-shift errors that character comparison alone misses.

HS code remains a separate classification layer

The existing eduKateSG HS-code owner covers trade classification. EORI and MRN answer who and which movement rather than what commodity. Link conceptually without duplicating the classification guide. Treat the party or goods description as translatable, the official customs identifier as protected, and the role or procedure relationship as something to verify after export. This prevents a correct-looking EORI or MRN from being attached to the wrong trader or movement.

Commodity description is human-language content

A declaration pairs tariff classification with a natural-language goods description. The description can be translated while identifiers stay fixed. Keep classification and prose aligned. The practical test is system traceability. A reviewer using only the target should be able to validate the same economic operator or follow the same customs movement without guessing which reference was intended.

Consignor and consignee are roles, not codes

Customs documents contain parties with names, addresses and identifiers. Translating role labels loosely can swap who sends and receives. Use precise trade terminology. For files and declarations, store EORI and MRN as text with explicit field names and exclude them from locale formatting, automatic numbering and generative rewriting. Translation can then change the language around stable customs data.

Declarant is not always the importer

A customs representative may lodge a declaration for another economic operator. Replacing declarant with importer can misstate legal responsibility. Preserve role relationships. A strong reviewer checks both directions: from the target party or movement to the official identifier, and from the identifier back to the same trader, procedure and date. This catches row-shift errors that character comparison alone misses.

Representative can have its own EORI

Customs representatives can be identified separately from clients. A form may legitimately show more than one EORI. Keep each EORI beside the correct party. Treat the party or goods description as translatable, the official customs identifier as protected, and the role or procedure relationship as something to verify after export. This prevents a correct-looking EORI or MRN from being attached to the wrong trader or movement.

Carrier identity is another role

Carriers can require EORI in relevant customs activities. A carrier’s identifier should not be copied into consignor or declarant fields. Use role-aware translation. The practical test is system traceability. A reviewer using only the target should be able to validate the same economic operator or follow the same customs movement without guessing which reference was intended.

Authorised Economic Operator status is separate from EORI

AEO status and references concern customs authorization and facilitation, while EORI is the core operator identity. Calling EORI an AEO number confuses status with identity. Keep authorization data separate. For files and declarations, store EORI and MRN as text with explicit field names and exclude them from locale formatting, automatic numbering and generative rewriting. Translation can then change the language around stable customs data.

TIR-related structures can have special EORI patterns

EU guidance includes recommended structures for certain non-EU TIR carnet holders. An unusual EORI should not be corrected into the common pattern by intuition. Verify the issuing authority. A strong reviewer checks both directions: from the target party or movement to the official identifier, and from the identifier back to the same trader, procedure and date. This catches row-shift errors that character comparison alone misses.

Customs decision numbers are another layer

Authorizations and decisions can have their own references. Those identify permissions or rulings, not movements. Keep decision identity distinct. Treat the party or goods description as translatable, the official customs identifier as protected, and the role or procedure relationship as something to verify after export. This prevents a correct-looking EORI or MRN from being attached to the wrong trader or movement.

Guarantee references are separate

Transit and customs guarantees can have guarantee reference numbers. They should not be labeled MRN simply because both are long alphanumeric strings. Preserve field context. The practical test is system traceability. A reviewer using only the target should be able to validate the same economic operator or follow the same customs movement without guessing which reference was intended.

Invoice number is commercial, not customs movement identity

Commercial invoices can appear alongside MRN and EORI. An invoice number belongs to seller records, not the customs system. Keep commercial and customs references separate. For files and declarations, store EORI and MRN as text with explicit field names and exclude them from locale formatting, automatic numbering and generative rewriting. Translation can then change the language around stable customs data.

Bill of lading number is transport identity

Shipping documents carry B/L or airway-bill references. Those identify transport documents, not EU customs movements. Keep shipment-document and customs identity separate. A strong reviewer checks both directions: from the target party or movement to the official identifier, and from the identifier back to the same trader, procedure and date. This catches row-shift errors that character comparison alone misses.

Container number is equipment identity

Container identifiers may sit beside MRNs in freight records. The existing container-number owner covers that layer. Do not substitute equipment ID for movement ID. Treat the party or goods description as translatable, the official customs identifier as protected, and the role or procedure relationship as something to verify after export. This prevents a correct-looking EORI or MRN from being attached to the wrong trader or movement.

Package marks are another logistics layer

Cartons and pallets can carry shipping marks and SSCC-type identifiers. These do not replace EORI or MRN. Keep logistics-unit identity separate. The practical test is system traceability. A reviewer using only the target should be able to validate the same economic operator or follow the same customs movement without guessing which reference was intended.

Import-control systems can use additional references

Entry summary declarations and safety/security systems generate their own records and statuses. A target table should retain exact field names rather than calling everything customs reference. Use system-specific terminology. For files and declarations, store EORI and MRN as text with explicit field names and exclude them from locale formatting, automatic numbering and generative rewriting. Translation can then change the language around stable customs data.

Exit summary declarations have their own context

EXS records concern exit safety/security processes. An EORI can identify the operator while another reference identifies the declaration. Keep person and event identity distinct. A strong reviewer checks both directions: from the target party or movement to the official identifier, and from the identifier back to the same trader, procedure and date. This catches row-shift errors that character comparison alone misses.

Temporary storage declarations are another procedure

Customs systems can require EORI and declaration data before release to a later procedure. A translation should not collapse temporary storage into import clearance. Preserve procedure chronology. Treat the party or goods description as translatable, the official customs identifier as protected, and the role or procedure relationship as something to verify after export. This prevents a correct-looking EORI or MRN from being attached to the wrong trader or movement.

Status messages need controlled terminology

Released, accepted, rejected, discharged and closed can have specific customs meanings. Loose translation can imply a different processing state. Use official target-language terminology where available. The practical test is system traceability. A reviewer using only the target should be able to validate the same economic operator or follow the same customs movement without guessing which reference was intended.

Historical documents need historical status

A movement that was pending at the source date may be closed today. Updating the translated text with today’s status changes the record. Keep source-period status and add current lookup separately if needed. For files and declarations, store EORI and MRN as text with explicit field names and exclude them from locale formatting, automatic numbering and generative rewriting. Translation can then change the language around stable customs data.

EORI prefixes should not be localized

The two-letter issuing-country code is structured identifier data. Target-language country abbreviations can differ. Translate the country name outside the EORI. A strong reviewer checks both directions: from the target party or movement to the official identifier, and from the identifier back to the same trader, procedure and date. This catches row-shift errors that character comparison alone misses.

Spaces and special characters can invalidate entry

Commission guidance warns against spaces and unexpected special characters in EORI entry contexts. Desktop formatting can introduce invisible spaces. Protect exact strings. Treat the party or goods description as translatable, the official customs identifier as protected, and the role or procedure relationship as something to verify after export. This prevents a correct-looking EORI or MRN from being attached to the wrong trader or movement.

O and zero can be confused

Alphanumeric EORI and MRN fields can contain characters that look alike. OCR or manual entry can substitute 0 and O. Verify with official systems. The practical test is system traceability. A reviewer using only the target should be able to validate the same economic operator or follow the same customs movement without guessing which reference was intended.

Spreadsheets can corrupt MRNs

A long customs reference can be converted to scientific notation or stripped of leading characters. The damage may be invisible until export. Store MRN as text. For files and declarations, store EORI and MRN as text with explicit field names and exclude them from locale formatting, automatic numbering and generative rewriting. Translation can then change the language around stable customs data.

CSV needs explicit namespaces

A bare column named ID can contain EORI, MRN, office code or invoice number. Without field type, translators can mislabel values. Define the customs namespace. A strong reviewer checks both directions: from the target party or movement to the official identifier, and from the identifier back to the same trader, procedure and date. This catches row-shift errors that character comparison alone misses.

OCR can detach field labels

Scanned customs forms use dense boxed layouts. Text extraction can place an MRN under the wrong heading. Inspect the page image when structure is unclear. Treat the party or goods description as translatable, the official customs identifier as protected, and the role or procedure relationship as something to verify after export. This prevents a correct-looking EORI or MRN from being attached to the wrong trader or movement.

Machine translation should lock identifiers

MT can translate country prefixes, insert spaces or normalize punctuation. A fluent target can become operationally unusable. Protect EORI and MRN fields before MT. The practical test is system traceability. A reviewer using only the target should be able to validate the same economic operator or follow the same customs movement without guessing which reference was intended.

Translation memory can carry stale movements

Customs declarations share repetitive templates. A high TM match can reuse another shipment’s MRN or party EORI. Populate identifiers from the current document. For files and declarations, store EORI and MRN as text with explicit field names and exclude them from locale formatting, automatic numbering and generative rewriting. Translation can then change the language around stable customs data.

Redaction is separate from translation

Public examples may need trader identifiers masked. A translator should not redact official-use documents without authorization. Follow the document’s privacy and disclosure purpose. A strong reviewer checks both directions: from the target party or movement to the official identifier, and from the identifier back to the same trader, procedure and date. This catches row-shift errors that character comparison alone misses.

Worked example: one trader, many movements

A fictional exporter has one EORI but files dozens of export declarations with different MRNs. The target preserves the EORI across records and each movement’s unique MRN. This demonstrates operator versus event identity. Treat the party or goods description as translatable, the official customs identifier as protected, and the role or procedure relationship as something to verify after export. This prevents a correct-looking EORI or MRN from being attached to the wrong trader or movement.

Worked example: declarant and exporter differ

A fictional customs broker lodges a declaration for an exporter and both have EORIs. The target must keep each EORI beside the correct role. Do not let a translated party label swap identities. The practical test is system traceability. A reviewer using only the target should be able to validate the same economic operator or follow the same customs movement without guessing which reference was intended.

Worked example: MRN and HS code together

A fictional declaration has one MRN and several item-level commodity codes. The MRN identifies the declaration or movement while HS codes classify goods lines. Keep movement and classification levels separate. For files and declarations, store EORI and MRN as text with explicit field names and exclude them from locale formatting, automatic numbering and generative rewriting. Translation can then change the language around stable customs data.

Error clinic

Common failures include removing the EORI country prefix, treating MRN as trader identity, scientific notation, O/0 confusion, procedure-code translation and row shifts. These errors can survive fluent trade prose review. Run dedicated customs-identity QA. A strong reviewer checks both directions: from the target party or movement to the official identifier, and from the identifier back to the same trader, procedure and date. This catches row-shift errors that character comparison alone misses.

Release checklist

EORI, party role, MRN, procedure, office code, local reference, dates and commodity-code relationships all need verification. Checking only translated goods descriptions is insufficient. Validate tokens and customs relationships. Treat the party or goods description as translatable, the official customs identifier as protected, and the role or procedure relationship as something to verify after export. This prevents a correct-looking EORI or MRN from being attached to the wrong trader or movement.

Frequently asked questions

EORI and MRN values should not be translated. Users often ask whether EORI is a VAT number or whether MRN is an HS code. Explain trader identity, movement identity and goods classification separately. The practical test is system traceability. A reviewer using only the target should be able to validate the same economic operator or follow the same customs movement without guessing which reference was intended.

Connection to eduKateSG architecture

This specialist owner protects customs operator and movement identity. A new general customs or HS hub would cannibalize existing owners. Use this page for EORI/MRN and the existing HS page for tariff classification. For files and declarations, store EORI and MRN as text with explicit field names and exclude them from locale formatting, automatic numbering and generative rewriting. Translation can then change the language around stable customs data.

Authoritative sources

The European Commission maintains EORI guidance, validation services and MRN follow-up systems. National customs authorities can add operational details. Verify identifiers against the responsible official system. A strong reviewer checks both directions: from the target party or movement to the official identifier, and from the identifier back to the same trader, procedure and date. This catches row-shift errors that character comparison alone misses.

Reference verification route

For trader identity and current format guidance, use the European Commission’s EORI guidance. For customs movement lookup, use the Commission’s MRN Follow-up service and applicable national customs systems. Commodity classification belongs to the separate Harmonized System and tariff-classification layer.

Translate | EORI Numbers, MRNs and Customs Declaration References — Preserve Trader and Movement Identity Across Languages