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
The value matches this illustrative list. Actual acceptance depends on the applicable customs requirements and system rules.
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.
Controlled Vocabulary
A simplified representation of a coded reference set.
AB
Illustrative meaning A
IN LIST
CD
Illustrative meaning B
IN LIST
EF
Illustrative meaning C
IN LIST
List identity
Identifies the reference set and the requirements to which it applies.
Code value
The encoded representation used to communicate a particular meaning.
Meaning & definition
Explains what the value represents, rather than relying on its characters alone.
Scope & maintenance
Accounts for applicable contexts, relevant versions and changes to the reference data.
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.
What does it mean?
Codes are compact representations of defined concepts. Their official descriptions and any applicable legal notes are essential for correct interpretation.
When can it be used?
A code may be recognised but still be inappropriate for a particular declaration, procedure, dataset or combination of information.
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.
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.
Declaration Type Codes
Identify the category of customs declaration or notification being submitted. Their applicability depends on the relevant dataset and filing scenario.
EX
IM
Customs Procedure Codes
Describe the customs treatment requested and, where applicable, the preceding procedure. Additional procedure codes may further specify the operation.
10
40
51
Document & Certificate Codes
Identify supporting documents, certificates, authorisations or other references. Their use can depend on the goods, measures and customs procedure.
Country & Territory Codes
Represent geographic information in a standardised form, including origin, dispatch or destination where the applicable data requirement calls for it.
IT
DE
CH
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.
Preference & Additional Codes
Represent additional customs or tariff information, including preference-related particulars and supplementary codes required in defined circumstances.
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.
Standardised coded information for customs data requirements.
LEGAL DATA REQUIREMENTSCommodity classification, tariff subdivisions and measure-related information.
DATE & MEASURE CONTEXTNationally defined values where permitted under the relevant Union framework.
MEMBER STATE SCOPETechnical values and constraints used by the applicable customs IT implementation.
SYSTEM SPECIFICATIONSOne 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.
Which declaration category applies?
Which customs procedure is requested?
Which country is the destination?
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.
Formats and codes under the UCC framework
Annex B to Commission Implementing Regulation (EU) 2015/2447, as amended, specifies formats and codes for the corresponding common data requirements. Commission Implementing Regulation (EU) 2024/250 introduced significant updates to these provisions.
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.
Format
Does the value match the required character type, length and representation?
STRUCTURAL CHECKList membership
Is the value present in the reference set applicable to the data requirement?
REFERENCE CHECKApplicability
Is the code permitted for the declaration type, procedure and relevant circumstances?
CONTEXTUAL CHECKSystem rules
Does the complete message meet the applicable technical and cross-field validation rules?
SUBMISSION CHECKSame format. Three different outcomes.
The following simulation uses fictional codes to demonstrate how list membership and contextual rules can produce different results.
a2
Two alphabetic characters
AB · CD · EF
Three fictional permitted values
Valid and applicable
The value has the expected format, exists in the fictional list and is permitted under Scenario A.
Unknown reference value
The format is correct, but XY does not appear in the fictional reference list.
Recognised but not permitted
EF exists in the fictional list, but Scenario A permits only AB and CD. Membership alone is not sufficient.
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.
Incorrect representation
The code has an unexpected length, character type or structure for the relevant data element.
Unrecognised code
The value is absent from the reference set applicable to the field and system.
Invalid combination
A recognised value conflicts with the declaration type, procedure or another required data element.
Outdated reference data
The implementation relies on values or rules that are no longer applicable to the operation.
Build validation around the applicable context.
Reliable customs software should not rely on a single generic list of values.
Determine the relevant declaration or notification requirements.
Use the applicable Union, tariff, national or system reference data.
Check dependencies between codes and other declaration information.
Maintain version and applicability information for changing values.
Distinguish missing data, invalid codes and contextual incompatibilities.
Verify the final message using the applicable customs system requirements.
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.
From official sources to validated customs data.
Authoritative references
Union legislation, tariff data, national references and applicable technical specifications.
SOURCE IDENTIFICATIONReference data layer
Controlled records containing codes, meanings, source versions and relevant applicability metadata.
VERSION MANAGEMENTRules & mappings
Format checks, contextual restrictions, ERP transformations and cross-field dependencies.
BUSINESS RULESCustoms system interface
Declaration data prepared according to the specifications of the receiving customs system.
SYSTEM-SPECIFIC MESSAGEAn 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.
New reference data published
A revised code set becomes available from the relevant authoritative source.
Changes compared and assessed
Added, modified and removed values are reviewed against existing mappings and declarations.
New rules become applicable
The relevant version is applied according to its actual effective date and scope.
Historical decisions remain explainable
The software retains the reference version and rules used for earlier validations.
What should be recorded?
Reference source and publication identifier
Version or revision information, where available
Effective date and relevant applicability conditions
Added, modified, withdrawn or replaced values
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.
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.
destination_country
Switzerland
Resolve the relevant country code.
CH
Subject to field context
product_sku
VALVE-1048
Retrieve a verified commodity classification.
transaction_type
Export Sale
Determine the customs treatment from the full facts.
Customs Data Mapping
Explore how business data can be transformed, enriched and validated for customs processes.
Reference data needs clear ownership.
A maintainable implementation separates reference-data updates from business decisions and provides a controlled process for exceptions.
Assign responsibility
Define who monitors sources, approves changes and resolves questions about code applicability.
Detect relevant changes
Track legal amendments, reference-data revisions and updates to receiving-system specifications.
Check downstream effects
Test modified lists against mappings, validation logic and representative declaration scenarios.
Preserve evidence
Record which rules and source versions were used, when changes were deployed and how exceptions were resolved.
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.
EUCDM Code Lists FAQ
Practical answers for customs professionals, software developers and businesses integrating customs data into their systems.
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.
The regulatory foundation behind customs data codes.
The following instruments provide the core Union customs framework. Always consult the applicable amended text and the requirements relevant to the customs operation.
Regulation (EU) No 952/2013
Union Customs Code
Establishes the overarching legal framework for customs procedures and customs information requirements within the Union.
Read regulationRegulation (EU) 2015/2446
UCC Delegated Regulation
Supplements the UCC. Annex B contains common data requirements for relevant declarations, notifications and proofs of customs status.
Read regulationRegulation (EU) 2015/2447
UCC Implementing Regulation
Establishes implementing rules. Annex B specifies relevant formats and codes corresponding to the common data requirements, as subsequently amended.
Read regulationOfficial EU Customs Data Model resource
Consult the European Commission’s EUCDM resources for the data-model documentation and available technical reference materials.
Better customs data starts with reliable references.
Understand the model, identify the applicable code requirements and connect structured customs information to your business systems.