Customs Explorer
⌕

Customs Explorer

EU Customs Data Model explained

EUROPEAN CUSTOMS DATA STANDARD

One data model. A common language for EU customs.

The EU Customs Data Model (EUCDM) brings together the legal data requirements behind European customs declarations, notifications and digital customs systems.

Discover how customs data elements, datasets, formats and code lists fit together — and why they matter for traders, customs professionals, software developers and authorities.

LEGAL FOUNDATION Union Customs Code
DATA STRUCTURE Elements · Datasets · Codes
SYSTEM COVERAGE EU & National Systems
DATA ARCHITECTURE CONCEPTUAL VIEW
EU CUSTOMS EUCDM DATA MODEL
01 DATA ELEMENTS
02 DATASETS
03 CODE LISTS
04 EU SYSTEMS
THE FOUNDATION OF DIGITAL CUSTOMS DATA SCROLL TO DISCOVER
01 / UNDERSTANDING THE ARCHITECTURE

Behind every customs declaration, there is a data architecture.

A customs declaration is more than a collection of fields. Each piece of information belongs to a defined legal and technical structure. The EU Customs Data Model makes those requirements easier to identify, compare and implement across EU and national customs systems.

EUCDM / DATA ARCHITECTURE
CONCEPTUAL MODEL · NOT A SYSTEM SCHEMA
FROM LEGAL REQUIREMENTS TO STRUCTURED DATA

How the pieces fit together.

EU customs legislation establishes the requirements. EUCDM organises them into datasets, data elements and associated formats and codes that support the design of customs IT systems.

01
LEGAL FOUNDATION

Union Customs Code framework

UCC legislation defines the customs obligations and the underlying legal data requirements. Its delegated and implementing acts contain the relevant annexes.

UCC · DA · IA
02
DECLARATION STRUCTURE

Datasets

Datasets define the information structure for particular declarations, notifications, applications or decisions. Different procedures can require different combinations of data.

ANNEX A · B
03
INDIVIDUAL INFORMATION

Data elements

Data elements describe the information required within a dataset, such as the declarant, commodity classification, origin, goods description or transport particulars, where applicable.

FIELDS · GROUPS
04
DATA VALIDATION

Formats & code lists

Formats specify how information is represented. Code lists define permitted values where prescribed. Together, they support consistent interpretation and automated validation.

FORMAT · VALUES
IMPLEMENTATION IN CUSTOMS SYSTEMS

These harmonised requirements inform the technical specifications of trans-European systems and national customs applications. System-specific rules and permitted national requirements may also apply.

02 / THE FOUR BUILDING BLOCKS

Four concepts. One coherent model.

Understanding these components is the starting point for interpreting EUCDM documentation and translating legal data requirements into operational processes.

01 / LEGAL BASIS §

Legal requirements

Identify the legal source of each requirement, including the applicable UCC annex and the distinction between mandatory, conditional and procedure-specific information.

START WITH THE LAW
02 / STRUCTURE ▤

Datasets

Find the dataset relevant to a declaration, notification or customs decision. A dataset determines which information is expected for a particular legal context.

SELECT THE RIGHT DATASET
03 / CONTENT ⌗

Data elements

Examine individual data requirements, their structure, usage conditions and the information they represent within a customs declaration or other prescribed dataset.

04 / VALIDATION { }

Code lists & formats

Understand how accepted values, prescribed codes, character formats and technical constraints help systems validate the information submitted by operators.

03 / FROM THEORY TO PRACTICE

What does this look like in a real declaration?

Consider an export declaration. The applicable dataset identifies the required information. Individual data elements represent specific particulars, while formats and codes govern how those particulars must be expressed.

The simplified example illustrates the relationship between the components. It is not a complete export declaration or a technical message specification.

DECLARATION DATA / ILLUSTRATIVE EXPORT
LEGAL CONTEXT UCC / ANNEX B
DATASET APPLICABLE EXPORT DATASET
SELECTED DATA ELEMENTS
DECLARANT Economic operator identification
IDENTIFIER
COMMODITY CODE Goods classification information
CODE
COUNTRY OF DESTINATION Destination country information
COUNTRY CODE
STRUCTURED INFORMATION FOR SYSTEM PROCESSING
A data model is not a substitute for legislation.

EUCDM is a technical representation of customs data requirements. The legally binding provisions remain those published in the Official Journal of the European Union. Always consult the applicable legislation, consolidated amendments and relevant system specifications when implementing customs software.

EUCDM SOURCE ↗
02 / THE EUROPEAN CUSTOMS ECOSYSTEM

One common foundation. Many customs systems.

The EU Customs Data Model provides a common reference for legal data requirements across trans-European customs systems and national customs applications. It helps authorities, traders and software developers interpret the information required for different customs procedures.

EU CUSTOMS / DATA LANDSCAPE
ILLUSTRATIVE RELATIONSHIPS
COMMON DATA REQUIREMENTS

The reference layer behind digital customs.

The diagram illustrates how different customs systems rely on harmonised legal data requirements. It does not represent direct system-to-system connections or live data exchange.

EU CUSTOMS EUCDM COMMON DATA REFERENCE
EXPORT AES Automated Export System
TRANSIT NCTS New Computerised Transit System
SAFETY & SECURITY ICS2 Import Control System 2
IMPORT & CLEARANCE NATIONAL Member State customs systems
03 / SYSTEMS & USE CASES

Different procedures. Shared data principles.

EUCDM provides a horizontal view of customs data requirements, while each operational system implements the rules applicable to its own procedures, messages and business processes.

01 / EXPORT

AES

Automated Export System

AES supports electronic export and exit processes. Its declaration data requirements draw on the UCC framework, including the relevant Annex B datasets, while its technical specifications define the actual messages and validations.

EXAMPLE DATA Exporter · Goods · Procedure · Exit
Explore EU systems
02 / TRANSIT

NCTS

New Computerised Transit System

NCTS manages electronic transit declarations and associated movements. Its data structures reflect the applicable UCC requirements, supplemented by transit-specific functional and technical specifications.

EXAMPLE DATA Transit · Guarantee · Routing · Goods
Explore EU systems
03 / ENTRY SECURITY

ICS2

Import Control System 2

ICS2 processes advance cargo information for safety and security risk analysis. ENS data requirements depend on the transport mode and filing scenario, with specific technical specifications for submission and processing.

EXAMPLE DATA ENS · Transport · Consignment · Parties
Explore ICS2
04 / NATIONAL CLEARANCE

National systems

Member State customs applications

National customs systems implement EU customs requirements for import, clearance and related procedures. Member States may apply permitted national requirements and their own technical interfaces.

EXAMPLE DATA Import · Customs value · Duties · Goods
Understand customs data
04 / FROM MODEL TO IMPLEMENTATION

Harmonised requirements. Different technical realities.

EUCDM is the reference for understanding legally defined data requirements. It is not itself a production messaging interface, a customs declaration portal or a substitute for system-specific implementation documents.

A software provider integrating with AES, NCTS or ICS2 must also follow the applicable message specifications, business rules, validation rules, interface requirements and national implementation instructions.

Explore Customs Data Mapping
IMPLEMENTATION LAYERS REFERENCE → EXECUTION
01
LEGAL REQUIREMENTS UCC and applicable annexes

Identify the legal data obligations relevant to the customs procedure.

02
COMMON DATA MODEL EUCDM

Consult the structured requirements, data elements, formats and code lists.

03
TECHNICAL SPECIFICATIONS System messages & business rules

Apply the specifications and validation rules of the relevant customs system.

04
OPERATIONAL IMPLEMENTATION Software, interfaces & filing

Configure and test the actual connection and procedures authorised for the system.

EUCDM ALONE DOES NOT ESTABLISH CONNECTIVITY
BEYOND THE FOUR EXAMPLES

EUCDM has a wider scope.

The model also covers data requirements relating to customs applications and decisions, economic operator registration, surveillance and other prescribed customs datasets. Its scope is broader than import, export and transit declarations alone.

Official EUCDM documentation
03 / PRACTICAL APPLICATION

From business data to customs-ready information.

Commercial systems store products, customers, invoices and shipments. Customs systems require legally defined information arranged in specific datasets and message structures. Data mapping connects these two worlds.

DATA TRANSFORMATION / CONCEPTUAL WORKFLOW ERP → REQUIREMENTS → VALIDATION → FILING
01 SOURCE LAYER

Business data

Information originates in ERP, warehouse, invoicing and transport systems.

ERPWMSTMS
02 REFERENCE LAYER

EUCDM mapping

Source fields are matched to applicable legal datasets and data elements.

ANNEX BELEMENTS
03 CONTROL LAYER

Rules & validation

Check completeness, codes, formats, dependencies and system-specific rules.

FORMATSCODES
04 EXECUTION LAYER

Customs filing

Approved software prepares and submits the required system-specific message.

AESNCTSIMPORT
This is an illustrative software integration workflow, not a native EUCDM processing service or an automatic declaration submission process.
04 / A PRACTICAL EXPORT EXAMPLE

One shipment. Several data requirements.

Imagine a company exporting industrial components. Its ERP contains the sales invoice and product master data, but not necessarily every item required by the customs declaration. A mapping exercise identifies what can be reused, what must be validated and what needs to be collected separately.

SCENARIO EU export of industrial components Illustrative example — not a complete declaration dataset
FIELD MAPPING / ILLUSTRATIVE EXPORT DATA
BUSINESS SOURCE CUSTOMS INFORMATION REQUIRED ACTION
Customer master Buyer / delivery information Destination country Applicable declaration field Verify destination
Product master Internal product code Commodity classification Applicable customs commodity code Map & validate
Sales invoice Commercial price and currency Invoice / value particulars As required by the relevant dataset Check valuation context
Warehouse system Quantity and packaging Mass and package information Applicable units and structure Convert & reconcile
Customs master data Procedure and authorisations Procedure / authorisation data Subject to the filing scenario Confirm applicability
EXAMPLE ONLY · NO OFFICIAL DATA ELEMENT NUMBERS ASSIGNED 5 MAPPING SCENARIOS
05 / WHAT CAN GO WRONG

A field can be populated. And still be wrong.

Successful data mapping is not just about moving information between databases. Customs data must also be legally correct, semantically accurate and valid for the selected procedure.

01 / SEMANTICS

Wrong meaning

An ERP field labelled “origin” may represent the supplier’s location rather than the non-preferential origin of the goods.

02 / COMPLETENESS

Missing information

Commercial records may not contain transport, customs procedure, authorisation or other particulars needed for the filing.

03 / VALIDATION

Invalid codes

A familiar internal value may not match the prescribed customs code list, format or a system-specific validation rule.

04 / CHANGE CONTROL

Outdated mapping

Legal amendments, updated EUCDM releases and changes to customs system specifications can require a mapping review.

06 / IMPLEMENTATION DISCIPLINE

Build the mapping once. Maintain it deliberately.

A robust integration documents where each customs value comes from, why it is required, how it is transformed and which rules govern its use.

Explore Customs Data Mapping
MAPPING CONTROL FRAMEWORK 5 CHECKS
01
Identify the declaration scenario

Determine the relevant procedure, dataset and applicable rules.

02
Document every source field

Record the ERP field, its meaning and its data owner.

03
Apply legal and technical rules

Check required values, conditionality, codes and formats.

04
Test against the target system

Use the relevant interface specifications and test environment.

05
Monitor regulatory and system changes

Review mappings when requirements or specifications change.

EUCDM IS A REFERENCE MODEL — NOT A FILING ENGINE
THE KEY PRINCIPLE Good customs automation starts with good data governance.

EUCDM helps explain what customs information means. Accurate sourcing, interpretation, validation and system integration remain essential.

Official EUCDM reference
04 / EXPLORE THE FRAMEWORK

Go deeper into the EU Customs Data Model.

Understand the building blocks of EUCDM, from individual data requirements to complete datasets, prescribed values and changes between model versions.

GUIDE 01 / DATA STRUCTURE 01

EUCDM Data Elements

Discover how individual customs data requirements are identified, described and organised. Learn why the meaning and usage conditions of a data element matter as much as its technical format.

IDENTIFIERS DEFINITIONS CONDITIONS
Explore this topic
GUIDE 02 / DECLARATIONS 02

EUCDM Datasets

Explore the relationship between customs procedures, declarations, notifications and their applicable datasets. Understand why different filing scenarios require different combinations of information.

ANNEX A ANNEX B REQUIREMENTS
Explore this topic
GUIDE 03 / VALIDATION 03

EUCDM Code Lists

Learn how prescribed codes and formats support consistent customs data. See why a valid-looking value may still be rejected when it does not satisfy the applicable legal or system-specific rules.

CODE VALUES FORMATS VALIDATION
Explore this topic
GUIDE 04 / CHANGE MANAGEMENT 04

EUCDM Versions & Updates

Understand why model versions, legal amendments and technical releases must be tracked separately. Explore the implications for mapping tables, customs software and operational maintenance.

RELEASES CHANGES IMPACT
Explore this topic
05 / YOUR LEARNING PATH

A clearer way to understand customs data.

Begin with the meaning of individual data elements. Then study how they are combined into datasets, how values are constrained and how the framework evolves over time.

This sequence is a suggested learning path, not a mandatory order for technical implementation.

EUCDM / LEARNING SEQUENCE 4 MODULES
01
Understand data elements

What information does each element represent?

02
Identify the correct dataset

Which requirements apply to the selected scenario?

03
Interpret formats and codes

How must the required information be expressed?

04
Manage versions and changes

What needs to be reviewed when requirements evolve?

LEARN THE MODEL · APPLY THE SYSTEM RULES
OFFICIAL DOCUMENTATION

Always check the authoritative sources.

EUCDM documentation supports the interpretation of harmonised data requirements. The applicable EU legislation and the relevant customs system specifications must also be consulted.

05 / QUESTIONS & LEGAL FOUNDATIONS

EUCDM explained. The essential answers.

Understand what the EU Customs Data Model does, where its requirements come from, and what businesses and software developers must consider when working with customs data.

Questions that matter in practice.

These answers explain the relationship between harmonised customs requirements, technical implementation and national customs systems.

REFERENCE PRINCIPLE

EUCDM helps interpret customs data requirements. The applicable legislation and system-specific specifications remain essential.

01 What is the EU Customs Data Model?

The EU Customs Data Model (EUCDM) is a technical reference that organises customs data requirements established by EU legislation. It supports the understanding and implementation of data requirements for trans-European and national customs IT systems.

02 Is EUCDM itself a legally binding regulation?

No. EUCDM is a technical instrument that represents requirements established by EU customs legislation. The binding obligations arise from the applicable legal acts, including the Union Customs Code and its delegated and implementing provisions.

03 What is the difference between Annex A and Annex B?

Annex A concerns common data requirements for customs applications and decisions. Annex B concerns requirements for customs declarations, notifications and proof of the customs status of Union goods. The applicable annex and dataset depend on the relevant customs process.

04 Does EUCDM apply to every customs declaration?

EUCDM covers a broad range of customs data requirements, but not every data element applies to every declaration. The relevant dataset, procedure, filing scenario and applicable legal conditions determine which information must be provided.

05 Can national customs authorities require additional data?

National requirements may supplement the common EU framework where permitted by EU customs rules. Economic operators must therefore check the applicable national implementation and the requirements of the customs system they use.

06 Does EUCDM provide an API for submitting declarations?

EUCDM is not itself a declaration-submission API. Actual electronic filing depends on the relevant customs system, its authorised interfaces, message specifications, validation rules and access arrangements.

07 How does EUCDM relate to the WCO Data Model?

EUCDM is designed for compatibility with the World Customs Organization Data Model. Mappings between corresponding data elements support international interoperability, but compatibility does not mean that every dataset or national implementation is identical.

08 Why should businesses monitor EUCDM versions?

Updates may reflect legal amendments, revised data requirements, code changes or corrections. Businesses and software providers should assess their impact on data mapping, validations and technical integrations rather than assuming that every release requires the same action.

03 / PRIMARY TECHNICAL REFERENCE

European Commission — EUCDM

Access the official model, its available releases, supporting documentation and guidance on interpreting the data requirements.

Open official EUCDM
CUSTOMS EXPLORER / DIGITAL CUSTOMS KNOWLEDGE

Better customs data. Better customs decisions.

Understanding data requirements is the starting point for reliable declarations, effective compliance controls and future-ready customs technology.