Customs Explorer
⌕

Customs Explorer

EUCDM code lists

EUCDM / STRUCTURED CUSTOMS DATA

Customs data needs a common language.

Understanding EUCDM Code Lists

Customs declarations rely on standardised codes to represent countries, procedures, documents and other regulated information. Code lists help ensure that systems interpret these values consistently.

Explore how coded values work, why the applicable list matters and how customs software validates information against legal and technical requirements.

Controlled Values Defined code sets
Shared Meaning Consistent interpretation
Validation Rules Context-specific checks
CODE LIST EXPLORER DEMO
ILLUSTRATIVE REFERENCE TABLE

Controlled Values

CODE MEANING CHECK
AB Example value A ✓
CD Example value B ✓
EF Example value C ✓
VALIDATION PREVIEW FICTIONAL CODE SET
Input CD ✓ MATCH FOUND

The value matches this illustrative list. Actual acceptance depends on the applicable customs requirements and system rules.

REFERENCE VISUALISATION NOT AN OFFICIAL EUCDM CODE LIST
EU CUSTOMS DATA MODEL / CODE LISTS & CONTROLLED VOCABULARIES
01 / CODE LIST STRUCTURE

A code is more than a short value.

A customs code list connects permitted values to defined meanings. Understanding the code alone is not sufficient: its source, applicability and maintenance rules also matter.

CODE LIST STRUCTURE ILLUSTRATIVE DATA
REFERENCE DATA / CONCEPTUAL EXAMPLE

Controlled Vocabulary

A simplified representation of a coded reference set.

CODE DESCRIPTION STATUS
AB Illustrative meaning A IN LIST
CD Illustrative meaning B IN LIST
EF Illustrative meaning C IN LIST
These codes, labels and list identifiers are fictional. They do not represent official EUCDM values.
01

List identity

Identifies the reference set and the requirements to which it applies.

02

Code value

The encoded representation used to communicate a particular meaning.

03

Meaning & definition

Explains what the value represents, rather than relying on its characters alone.

04

Scope & maintenance

Accounts for applicable contexts, relevant versions and changes to the reference data.

01 / IDENTITY

Which list applies?

The relevant data requirement determines which coded values can be used. A value appearing in one list does not automatically make it acceptable in another.

02 / SEMANTICS

What does it mean?

Codes are compact representations of defined concepts. Their official descriptions and any applicable legal notes are essential for correct interpretation.

03 / CONTEXT

When can it be used?

A code may be recognised but still be inappropriate for a particular declaration, procedure, dataset or combination of information.

04 / LIFECYCLE

Is it still applicable?

Code sets and their implementation may change. Systems must use the relevant legal and technical references for the applicable operation and date.

02 / CODE FAMILIES

Different codes. Different customs functions.

Customs declarations use several categories of coded information. Some identify the procedure or declaration type, others refer to documents, countries, tariff classifications or additional regulatory requirements. Each category has its own legal and technical context.

01 / DECLARATION

Declaration Type Codes

Identify the category of customs declaration or notification being submitted. Their applicability depends on the relevant dataset and filing scenario.

EXAMPLES
EX IM
Declaration type codes; their use depends on the applicable legal provisions.
02 / PROCEDURE

Customs Procedure Codes

Describe the customs treatment requested and, where applicable, the preceding procedure. Additional procedure codes may further specify the operation.

EXAMPLES
10 40 51
Export, release for free circulation and inward processing procedure references.
03 / DOCUMENTATION

Document & Certificate Codes

Identify supporting documents, certificates, authorisations or other references. Their use can depend on the goods, measures and customs procedure.

TYPICAL APPLICATIONS Supporting documents Certificates and authorisations The applicable code must be checked against the relevant customs or regulatory reference.
04 / GEOGRAPHY

Country & Territory Codes

Represent geographic information in a standardised form, including origin, dispatch or destination where the applicable data requirement calls for it.

EXAMPLES
IT DE CH
Italy, Germany and Switzerland. The meaning of the relevant country field must still be assessed.
05 / TARIFF

Commodity & Tariff Codes

Identify goods under the applicable nomenclature. These classifications are governed by tariff rules and should not be confused with a simple EUCDM reference-value list.

RELATED CLASSIFICATIONS Combined Nomenclature (CN) TARIC subdivisions Classification and applicable measures must be checked for the relevant date and operation.
06 / REGULATORY

Preference & Additional Codes

Represent additional customs or tariff information, including preference-related particulars and supplementary codes required in defined circumstances.

TYPICAL APPLICATIONS Preference information Additional procedure / TARIC codes These are distinct coding families with different legal sources and conditions.
01 / REFERENCE LAYERS

Not every code comes from the same source.

A customs system may combine Union-level legal code requirements, tariff reference data and technical rules specific to a particular electronic system. These layers must remain distinguishable.

CUSTOMS CODE REFERENCE MATRIX CONCEPTUAL OVERVIEW
REFERENCE LAYER PRIMARY FUNCTION IMPLEMENTATION CONSIDERATION
01 UCC data codes

Standardised coded information for customs data requirements.

LEGAL DATA REQUIREMENTS
02 Tariff reference data

Commodity classification, tariff subdivisions and measure-related information.

DATE & MEASURE CONTEXT
03 National codes

Nationally defined values where permitted under the relevant Union framework.

MEMBER STATE SCOPE
04 System reference data

Technical values and constraints used by the applicable customs IT implementation.

SYSTEM SPECIFICATIONS
These categories describe overlapping reference layers, not four mutually exclusive or official EUCDM classifications.
02 / PRACTICAL APPLICATION

One declaration. Several coding systems.

Consider a company exporting industrial components from Italy to Switzerland. The declaration may involve different categories of codes, each answering a separate customs question.

DECLARATION EX

Which declaration category applies?

PROCEDURE 10

Which customs procedure is requested?

DESTINATION CH

Which country is the destination?

GOODS CN / TARIC

How are the goods classified?

Illustrative scenario: the values shown are examples of genuine coding concepts, not a complete export declaration. Their use must be checked against the applicable dataset, customs procedure and current rules.

03 / CODE VALIDATION

A valid code is not always an acceptable code.

Customs code validation goes beyond checking whether a value exists in a reference list. The value must also satisfy the applicable data requirement, declaration context, effective rules and technical specifications of the customs system receiving it.

CHECK 01 01

Format

Does the value match the required character type, length and representation?

STRUCTURAL CHECK
CHECK 02 02

List membership

Is the value present in the reference set applicable to the data requirement?

REFERENCE CHECK
CHECK 03 03

Applicability

Is the code permitted for the declaration type, procedure and relevant circumstances?

CONTEXTUAL CHECK
CHECK 04 04

System rules

Does the complete message meet the applicable technical and cross-field validation rules?

SUBMISSION CHECK
01 / VALIDATION WORKBENCH

Same format. Three different outcomes.

The following simulation uses fictional codes to demonstrate how list membership and contextual rules can produce different results.

CODE VALIDATION CONSOLE STATIC EDUCATIONAL DEMO
ILLUSTRATIVE VALIDATION PROFILE FICTIONAL RULES
VALUE FORMAT a2 Two alphabetic characters
REFERENCE LIST AB · CD · EF Three fictional permitted values
SELECTED CONTEXT Scenario A Only AB and CD are applicable
INPUT VALUE VALIDATION RESULT
TEST CASE 01 AB Format: a2
ACCEPTED IN DEMO

Valid and applicable

The value has the expected format, exists in the fictional list and is permitted under Scenario A.

TEST CASE 02 XY Format: a2
REJECTED IN DEMO

Unknown reference value

The format is correct, but XY does not appear in the fictional reference list.

TEST CASE 03 EF Format: a2
NOT APPLICABLE

Recognised but not permitted

EF exists in the fictional list, but Scenario A permits only AB and CD. Membership alone is not sufficient.

The console illustrates validation principles only. It does not execute checks or reproduce an official EUCDM code list, rule or customs system.
02 / COMMON FAILURE MODES

Why coded customs data can fail validation.

An apparently small reference-data error can prevent a message from passing technical checks or require correction before the customs process can continue.

01 / FORMAT

Incorrect representation

The code has an unexpected length, character type or structure for the relevant data element.

02 / REFERENCE

Unrecognised code

The value is absent from the reference set applicable to the field and system.

03 / CONTEXT

Invalid combination

A recognised value conflicts with the declaration type, procedure or another required data element.

04 / VERSION

Outdated reference data

The implementation relies on values or rules that are no longer applicable to the operation.

03 / IMPLEMENTATION PRACTICE

Build validation around the applicable context.

Reliable customs software should not rely on a single generic list of values.

01Identify the dataset

Determine the relevant declaration or notification requirements.

02Resolve the reference source

Use the applicable Union, tariff, national or system reference data.

03Apply conditional rules

Check dependencies between codes and other declaration information.

04Control effective dates

Maintain version and applicability information for changing values.

05Handle exceptions

Distinguish missing data, invalid codes and contextual incompatibilities.

06Test against specifications

Verify the final message using the applicable customs system requirements.

04 / SOFTWARE IMPLEMENTATION

Code lists change. Your systems must keep up.

In customs software, reference data is not simply a collection of values stored in a database. Codes must be associated with their authoritative sources, applicable contexts, effective dates and validation rules.

A controlled update process helps prevent outdated values, incorrect ERP mappings and inconsistent declarations across different customs systems.

REFERENCE DATA ARCHITECTURE

From official sources to validated customs data.

CONCEPTUAL WORKFLOW
01 / SOURCE

Authoritative references

Union legislation, tariff data, national references and applicable technical specifications.

SOURCE IDENTIFICATION
02 / CONTROL

Reference data layer

Controlled records containing codes, meanings, source versions and relevant applicability metadata.

VERSION MANAGEMENT
03 / VALIDATE

Rules & mappings

Format checks, contextual restrictions, ERP transformations and cross-field dependencies.

BUSINESS RULES
04 / OUTPUT

Customs system interface

Declaration data prepared according to the specifications of the receiving customs system.

SYSTEM-SPECIFIC MESSAGE
EUCDM is a reference data model, not a universal submission API. Actual electronic messages and their validation requirements depend on the relevant customs system.
01 / VERSION & EFFECTIVE DATE CONTROL

An updated list is not enough. Applicability matters.

A new reference-data release may add values, remove values or change their conditions of use. Systems should distinguish the date a change was published from the date on which it becomes applicable.

ILLUSTRATIVE CHANGE RECORD NOT AN OFFICIAL EUCDM RELEASE
EVENT 01 / PUBLICATION

New reference data published

A revised code set becomes available from the relevant authoritative source.

EVENT 02 / IMPACT ANALYSIS

Changes compared and assessed

Added, modified and removed values are reviewed against existing mappings and declarations.

EVENT 03 / EFFECTIVE DATE

New rules become applicable

The relevant version is applied according to its actual effective date and scope.

EVENT 04 / TRACEABILITY

Historical decisions remain explainable

The software retains the reference version and rules used for earlier validations.

VERSION CONTROL

What should be recorded?

01

Reference source and publication identifier

02

Version or revision information, where available

03

Effective date and relevant applicability conditions

04

Added, modified, withdrawn or replaced values

05

Related validation and mapping changes

Publication date ≠ effective date

A reference update may be published before its rules apply. Conversely, different customs systems may follow distinct implementation schedules. These dates must not be treated as interchangeable.

02 / ERP & CUSTOMS INTEGRATION

Internal business values are not customs codes.

ERP systems often use internal identifiers for products, locations, transactions or business processes. These values must be mapped to the appropriate customs concepts before they can support a declaration.

ILLUSTRATIVE ERP-TO-CUSTOMS MAPPING EXAMPLE ONLY
ERP SOURCE TRANSFORMATION CUSTOMS OUTPUT
ERP FIELD destination_country Switzerland
REFERENCE LOOKUP

Resolve the relevant country code.

COUNTRY CODE CH Subject to field context
ERP FIELD product_sku VALVE-1048
MASTER DATA LOOKUP

Retrieve a verified commodity classification.

COMMODITY CLASSIFICATION Applicable CN / TARIC code Not derived from the SKU alone
ERP FIELD transaction_type Export Sale
PROCEDURE ASSESSMENT

Determine the customs treatment from the full facts.

CUSTOMS PROCEDURE Applicable procedure data Requires operational assessment
These transformations are conceptual. An ERP label does not independently establish customs classification, procedure eligibility or legal compliance.
03 / DATA GOVERNANCE

Reference data needs clear ownership.

A maintainable implementation separates reference-data updates from business decisions and provides a controlled process for exceptions.

01 / OWNERSHIP

Assign responsibility

Define who monitors sources, approves changes and resolves questions about code applicability.

02 / MONITORING

Detect relevant changes

Track legal amendments, reference-data revisions and updates to receiving-system specifications.

03 / TESTING

Check downstream effects

Test modified lists against mappings, validation logic and representative declaration scenarios.

04 / AUDITABILITY

Preserve evidence

Record which rules and source versions were used, when changes were deployed and how exceptions were resolved.

05 / REFERENCE & FURTHER READING

Understand the codes. Apply the right rules.

Code lists are essential to consistent customs data, but their correct use depends on the relevant legal requirements, declaration context and customs system. These frequently asked questions clarify the main distinctions.

FREQUENTLY ASKED QUESTIONS

EUCDM Code Lists FAQ

Practical answers for customs professionals, software developers and businesses integrating customs data into their systems.

Important distinction

A code being listed does not automatically establish that it is permitted in every declaration or system.

What is an EUCDM code list?

In the EUCDM context, code lists describe or reference controlled values associated with customs data requirements. They support consistent representation and interpretation of coded data. Their legal or technical authority depends on the underlying source.

Are all customs codes defined directly by EUCDM?

No. Customs systems use codes from several sources, including Union customs legislation, tariff nomenclatures, regulatory reference data and national or system-specific specifications. EUCDM helps describe harmonised data requirements; it is not the sole authority for every coded value.

Where are legally prescribed customs codes found?

Relevant formats and codes for common customs data requirements are established in Annex B to Commission Implementing Regulation (EU) 2015/2447, as amended. Other coded information may be governed by separate legislation, tariff references or applicable technical specifications.

Can a code exist in a list but still be rejected?

Yes. A recognised code may be inappropriate for a particular dataset, procedure, declaration type or combination of information. The receiving system may also apply additional technical validation rules.

Are EUCDM code lists the same as TARIC codes?

No. TARIC integrates EU tariff and trade measures and includes tariff subdivisions and related regulatory coding. EUCDM concerns harmonised customs data requirements. Tariff information may be used in declarations, but the two frameworks serve different functions.

Do all EU Member States use identical codes?

Union-level requirements establish harmonised elements, but national codes and implementation details may exist where the applicable framework permits them. The relevant Member State and electronic customs system must therefore be considered.

How often do customs code lists change?

There is no single update frequency covering every customs code list. Changes depend on the legal instrument, reference-data source, tariff measures and system release schedule. Publication dates and effective dates should be monitored separately.

Can an ERP system use its own internal codes?

Yes, for internal business processes. However, internal values must be mapped or transformed into the information required by the applicable customs declaration. An ERP transaction label or product identifier does not independently determine the correct customs treatment.

Does EUCDM provide a universal customs submission API?

No. EUCDM is a data-model reference, not a universal electronic filing interface. Declarations and notifications must be submitted through the relevant customs systems using their applicable message specifications and access arrangements.

EUCDM / CUSTOMS DATA ARCHITECTURE

Better customs data starts with reliable references.

Understand the model, identify the applicable code requirements and connect structured customs information to your business systems.

Explore EUCDM Overview