Customs Explorer
⌕

Customs Explorer

EUCDM data elements

EUCDM / DATA ARCHITECTURE

Every customs declaration starts with data.

Understanding EUCDM Data Elements

Customs declarations are built from structured information. The EU Customs Data Model helps describe and organise the data requirements established under the Union Customs Code framework.

Explore how data elements are identified, defined and used within customs datasets — and why their meaning, conditions and formats matter for accurate electronic declarations.

Defined information Meaning and structure
Applicable datasets Context and conditions
Technical formats Codes and validation
DATA ELEMENT INSPECTOR EUCDM / CONCEPT
ILLUSTRATIVE DATA RECORD

Customs information

01
DATA CONCEPT Exporter
PARTY
02
DATA CONCEPT Commodity code
GOODS
03
DATA CONCEPT Country of origin
ORIGIN
04
DATA CONCEPT Customs value
VALUE
DATA Meaning
EUCDM Structure
SYSTEM Implementation
EU CUSTOMS DATA MODEL / DATA ELEMENTS DISCOVER THE STRUCTURE
01 / UNDERSTANDING THE STRUCTURE

More than a field. A defined piece of customs information.

A customs data element is not simply a box to complete on a declaration. It represents information whose meaning, applicability and permitted representation are determined by the relevant customs requirements.

DATA STRUCTURE / CONCEPTUAL VIEW

Inside a customs data element

EUCDM REFERENCE
ILLUSTRATIVE EXAMPLE DATA CONCEPT / EXPORTER
CUSTOMS DATA CONCEPT Exporter
IDENTIFICATION Element reference Recognisable within the applicable model
SEMANTICS Defined meaning What the information represents
APPLICABILITY Dataset & conditions When the information is required or allowed
REPRESENTATION Format & codes How the information must be expressed
STRUCTURED INFORMATION MODEL → IMPLEMENTATION
FOUR DIMENSIONS
01
Identify

Recognise the relevant data requirement.

02
Interpret

Understand the information’s legal and operational meaning.

03
Apply

Determine its relevance to the specific dataset and procedure.

04
Represent

Use the required format, codes and applicable validation rules.

01 / IDENTIFICATION

Identifiers & References

Data elements can be identified through references used in the relevant customs data requirements. These help distinguish information concepts and support consistent interpretation across documentation.

IDENTIFY THE REQUIREMENT
02 / SEMANTICS

Meaning & Definition

The definition explains what a data element represents. Similar-looking fields may have different meanings depending on the legal context, so matching names alone is not sufficient for reliable data mapping.

UNDERSTAND THE MEANING
03 / APPLICABILITY

Datasets & Conditions

A data element’s relevance depends on the applicable dataset and legal conditions. Information may be mandatory, conditional, optional or not applicable in a particular declaration scenario.

CHECK THE CONTEXT
04 / REPRESENTATION

Formats & Code Lists

The required representation may involve character formats, length constraints, prescribed codes or additional technical rules. A value must satisfy the applicable requirements, not merely look correct.

VALIDATE THE VALUE
02 / DATA ELEMENTS IN PRACTICE

One data model. Different declaration requirements.

Customs procedures do not all require the same information. The applicable legal dataset, the type of declaration and the conditions of the operation determine which data elements must be provided.

HOW REQUIREMENTS ARE DETERMINED CONCEPTUAL PROCESS
STEP 01
CUSTOMS OPERATION

Identify the procedure

Establish the customs operation, filing scenario and applicable legal framework.

EXAMPLE / EXPORT
STEP 02
LEGAL DATA REQUIREMENTS

Select the dataset

Identify the relevant declaration dataset and the associated legal notes and conditions.

ANNEX B / APPLICABLE DATASET
STEP 03
DECLARATION CONTENT

Determine the elements

Apply the data requirements, conditions, formats and codes relevant to that filing.

REQUIRED / CONDITIONAL / PERMITTED
The diagram is simplified. Actual applicability must be assessed using the relevant legislation and system specifications.

Exporting industrial components. What information is involved?

Consider an EU business exporting industrial components to a customer outside the Union. The declaration requires structured information about the parties, goods, procedure and other relevant particulars.

ILLUSTRATIVE EXPORT SCENARIO
SHIPMENT PROFILE EXAMPLE / 001
DISPATCH European Union
DESTINATION Third country
GOODS Industrial components
OPERATION Export
DECLARATION Electronic customs filing
DATA FRAMEWORK Relevant Annex B requirements
FICTIONAL SCENARIO / NO ACTUAL DECLARATION
ILLUSTRATIVE DATA CONCEPTS 05 ITEMS
01
Exporter

Information identifying the relevant exporting party.

PARTY
02
Commodity code

Classification information for the declared goods.

GOODS
03
Country of destination

Destination information under the applicable rules.

COUNTRY
04
Net mass

Mass information expressed in the prescribed unit.

QUANTITY
05
Customs procedure

Procedure information represented using applicable codes.

PROCEDURE
These are representative information concepts, not a complete declaration dataset or a determination of mandatory fields.

The same information can have different conditions.

A data element cannot be evaluated independently of the declaration in which it appears. The legal dataset and applicable notes determine its role.

01

Declaration type

Standard, simplified and other declaration scenarios may be subject to different data requirements.

02

Legal conditions

The requirement for particular information may depend on the operation, the goods or other legal circumstances.

03

Level of information

Data may relate to the declaration, consignment, goods item or another relevant structural level.

04

System implementation

Electronic systems define message structures and technical validations for their specific filing processes.

IMPORTANT DISTINCTION

EUCDM is not a universal declaration template.

The model organises customs data requirements, but it does not mean that every EU customs system accepts the same message structure or requires identical fields. For actual filings, consult the applicable legal requirements and the specifications of the relevant customs IT system.

Explore EUCDM
03 / FORMATS, CODES & VALIDATION

Correct data is not enough. It must also be valid.

Every customs data value must be interpreted within its applicable requirements. A value may have the correct character format but still fail because it uses an inappropriate code, appears in the wrong context or conflicts with another declaration element.

01 / SYNTAX

Format & Length

Check the permitted data type, length, numerical precision and other prescribed formatting constraints.

STRUCTURAL CONFORMITY
02 / VOCABULARY

Permitted Codes

Where a coded value is required, it must belong to the applicable code list and be appropriate to the operation.

CODE CONFORMITY
03 / CONTEXT

Applicability

Determine whether the information is required, permitted or inapplicable under the relevant dataset and legal conditions.

LEGAL CONTEXT
04 / LOGIC

Cross-field Rules

Check dependencies between elements and the additional business rules enforced by the relevant customs system.

SYSTEM VALIDATION
01 / READING FORMAT NOTATION

A small notation. A precise constraint.

EU customs legislation uses compact type-and-length notation to describe the permitted representation of data. The following are examples of the notation, not format assignments to particular customs fields.

ALPHABETIC a1

Exactly one alphabetic character.

FIXED LENGTH
NUMERIC n2

Exactly two numeric characters.

FIXED LENGTH
ALPHANUMERIC an..6

Up to six alphanumeric characters.

VARIABLE LENGTH
DECIMAL n..7,2

Up to seven digits in total, with up to two decimal places.

VARIABLE LENGTH

Reading the notation: a means alphabetic, n numeric and an alphanumeric. Two dots indicate a variable length up to the stated maximum. A comma introduces the maximum number of decimal places. Always check the current legal annex for the actual format assigned to an individual data element.

02 / VALIDATION IN PRACTICE

A value can pass one check and fail another.

Consider a fictional coded field that accepts exactly two alphabetic characters and uses a defined list of permitted values. The examples below demonstrate separate validation layers.

DATA VALIDATION INSPECTOR DEMONSTRATION / NOT A LIVE SYSTEM
ILLUSTRATIVE FIELD RULE
Format: a2 Permitted codes: AB, CD

Fictional codes used only to demonstrate the distinction between syntax and code validity.

INPUT 01 AB
✓ FORMAT ✓ CODE LIST
PASSES THESE CHECKS
INPUT 02 XY
✓ FORMAT × CODE LIST
INVALID CODE
INPUT 03 A7
× FORMAT × CODE LIST
INVALID REPRESENTATION
Passing these checks does not establish legal applicability or acceptance by a customs system.
03 / COMMON VALIDATION FAILURES

Where declaration data goes wrong.

01

Wrong character format

A value exceeds the permitted length or uses characters inconsistent with the specified format.

02

Unsupported code

The submitted value is absent from the applicable list or is not valid for the relevant context.

03

Missing conditional data

Information required by the applicable circumstances has not been supplied.

04

Conflicting information

Two or more data elements are individually well formed but fail an applicable consistency rule.

04 / BUSINESS DATA INTEGRATION

Your ERP knows the business. Customs needs the right data.

Enterprise systems hold information about customers, products, invoices and shipments. Customs declarations require legally defined information organised according to the applicable data requirements. Connecting the two involves much more than copying values between fields.

BUSINESS-TO-CUSTOMS DATA FLOW CONCEPTUAL ARCHITECTURE
01 / SOURCE

Business Systems

ERP · WMS · TMS

Products Invoices Parties
02 / TRANSFORMATION

Mapping Layer

Meaning · Rules · Enrichment

EUCDM reference Validation
03 / DESTINATION

Customs Interface

System-specific filing

Message schema Submission
The mapping layer is an architectural concept, not a separate EUCDM service provided by the European Commission.
01 / DATA MAPPING WORKBENCH

From an internal field to a customs data requirement.

Consider a fictional manufacturer exporting industrial components. Its ERP contains useful source information, but the customs mapping must establish whether each value has the correct meaning and whether additional information or validation is necessary.

DATA MAPPING WORKBENCH ILLUSTRATIVE / NON-OPERATIONAL
BUSINESS SOURCE MAPPING ASSESSMENT CUSTOMS INFORMATION
ERP / PRODUCT MASTER Product classification Internal commodity reference
CHECK Classification validity
GOODS INFORMATION Commodity code Applicable nomenclature and format
ERP / CUSTOMER MASTER Delivery destination Customer and address information
INTERPRET Destination rules
COUNTRY INFORMATION Country of destination Determine the legally relevant country
ERP / SALES INVOICE Invoice amount Commercial transaction value
ASSESS Value requirements
VALUE INFORMATION Relevant value particulars Not necessarily a direct copy of invoice total
WMS / SHIPPING DATA Measured net weight Warehouse measurement
VALIDATE Units and item level
QUANTITY INFORMATION Net mass Correct unit and declaration structure
ERP / BUSINESS WORKFLOW Transaction type Internal order or shipment category
DETERMINE Customs treatment
PROCEDURE INFORMATION Customs procedure Legal assessment and applicable codes
Conceptual mapping examples only. The actual legal data elements, formats and required information depend on the filing scenario.
02 / INTEGRATION CHALLENGES

The difficult part is understanding the meaning.

Internal business terminology rarely matches customs requirements perfectly. Reliable mapping needs controlled definitions, legal interpretation and traceable transformation rules.

01

Different semantics

An ERP field and a customs element may have similar names but represent different concepts.

02

Missing information

Some customs particulars may not exist in the source system and require enrichment or review.

03

Different structures

A business record may need to be separated into declaration, consignment or goods-item information.

04

Changing requirements

Legal amendments, code-list changes and system releases may require controlled mapping updates.

03 / IMPLEMENTATION CONTROLS

A reliable mapping needs governance.

The objective is not simply to generate a message, but to maintain a defensible connection between source information and customs requirements.

01 Document source fields

Record their origin, meaning and ownership.

02 Reference legal requirements

Identify the applicable dataset and conditions.

03 Define transformation rules

Specify enrichment, conversion and validation.

04 Version the mapping

Track changes to rules, codes and specifications.

05 Test realistic scenarios

Include exceptions and conditional requirements.

06 Maintain an audit trail

Retain evidence of how submitted values were derived.

05 / KNOWLEDGE & REFERENCES

Understand the elements. Understand the requirements.

Explore the most common questions about EUCDM data elements, their legal foundations and their practical application in customs declarations and business systems.

01 / FREQUENTLY ASKED QUESTIONS

EUCDM Data Elements FAQ

Key distinctions for customs professionals, software developers and businesses working with structured customs information.

01 What is an EUCDM data element?

A data element represents a defined piece of customs information within the applicable data requirements. It has an identified meaning and may be subject to particular conditions, formats, codes and structural rules. Its use depends on the relevant customs dataset.

02 Are all data elements mandatory?

No. Requirements vary according to the applicable dataset, declaration type, customs procedure and relevant legal conditions. An element may be required in one situation and not applicable in another.

03 Where are EU customs data requirements legally defined?

The Union Customs Code provides the overarching legal framework. Common data requirements are established in particular through Annexes A and B to Commission Delegated Regulation (EU) 2015/2446, while related formats and codes are specified through the implementing provisions, notably Annexes A and B to Commission Implementing Regulation (EU) 2015/2447, as amended.

04 What is the difference between a data element and a dataset?

A data element describes a particular information requirement. A dataset defines the collection of requirements applicable to a particular type of declaration, notification or other customs process, subject to the relevant legal notes and conditions.

05 Does EUCDM define the electronic message sent to customs?

EUCDM provides a common reference for customs data requirements. It should not be treated as a single universal submission message or API. The actual message structures and validation rules depend on the customs system and its technical specifications.

06 Can ERP fields be mapped directly to EUCDM elements?

Sometimes a source value can be reused, but direct field-to-field copying is not always reliable. Businesses must verify meaning, legal relevance, required transformations, data quality and the technical requirements of the destination system.

07 Why can a correctly formatted value still be rejected?

Format validation is only one layer. A value may also need to belong to an applicable code list, satisfy conditional requirements or remain consistent with other declaration data. System-specific validation rules may apply as well.

08 Do EUCDM data requirements change over time?

Yes. Legislative amendments, updates to technical documentation and changes to customs systems may affect implementation. Organisations should track the relevant legal versions, EUCDM documentation, code lists and system-specific specifications.

OFFICIAL EUROPEAN COMMISSION RESOURCE

EU Customs Data Model documentation

Consult the European Commission’s EUCDM resource for official technical documentation and information about the common customs data model.

Official EUCDM resource
CUSTOMS EXPLORER / EUCDM KNOWLEDGE HUB

Every declaration starts with structured information.

Return to the EU Customs Data Model hub to understand how datasets, data elements, formats and implementation requirements fit into the wider customs architecture.