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.
Customs information
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.
Inside a customs data element
Recognise the relevant data requirement.
Understand the information’s legal and operational meaning.
Determine its relevance to the specific dataset and procedure.
Use the required format, codes and applicable validation rules.
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.
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.
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.
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.
The model describes requirements. The law establishes them.
The common data requirements are established through the UCC legal framework, notably Annexes A and B to Commission Delegated Regulation (EU) 2015/2446, together with relevant implementing provisions. EUCDM provides a technical representation of those requirements; individual customs systems may also impose specific interface and validation rules.
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.
Identify the procedure
Establish the customs operation, filing scenario and applicable legal framework.
Select the dataset
Identify the relevant declaration dataset and the associated legal notes and conditions.
Determine the elements
Apply the data requirements, conditions, formats and codes relevant to that filing.
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.
Information identifying the relevant exporting party.
Classification information for the declared goods.
Destination information under the applicable rules.
Mass information expressed in the prescribed unit.
Procedure information represented using applicable codes.
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.
Declaration type
Standard, simplified and other declaration scenarios may be subject to different data requirements.
Legal conditions
The requirement for particular information may depend on the operation, the goods or other legal circumstances.
Level of information
Data may relate to the declaration, consignment, goods item or another relevant structural level.
System implementation
Electronic systems define message structures and technical validations for their specific filing processes.
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.
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.
Format & Length
Check the permitted data type, length, numerical precision and other prescribed formatting constraints.
STRUCTURAL CONFORMITYPermitted Codes
Where a coded value is required, it must belong to the applicable code list and be appropriate to the operation.
CODE CONFORMITYApplicability
Determine whether the information is required, permitted or inapplicable under the relevant dataset and legal conditions.
LEGAL CONTEXTCross-field Rules
Check dependencies between elements and the additional business rules enforced by the relevant customs system.
SYSTEM VALIDATIONA 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.
Exactly one alphabetic character.
FIXED LENGTHExactly two numeric characters.
FIXED LENGTHUp to six alphanumeric characters.
VARIABLE LENGTHUp 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.
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.
Fictional codes used only to demonstrate the distinction between syntax and code validity.
Where declaration data goes wrong.
Wrong character format
A value exceeds the permitted length or uses characters inconsistent with the specified format.
Unsupported code
The submitted value is absent from the applicable list or is not valid for the relevant context.
Missing conditional data
Information required by the applicable circumstances has not been supplied.
Conflicting information
Two or more data elements are individually well formed but fail an applicable consistency rule.
Two layers of requirements. Both matter.
Annex B to Commission Delegated Regulation (EU) 2015/2446 establishes common data requirements for declarations and notifications. Annex B to Commission Implementing Regulation (EU) 2015/2447 specifies the corresponding formats and codes. Both regulations have been amended, including through Regulations (EU) 2024/249 and 2024/250. Electronic filing must also comply with the applicable system-specific technical specifications.
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 Systems
ERP · WMS · TMS
Mapping Layer
Meaning · Rules · Enrichment
Customs Interface
System-specific filing
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.
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.
Different semantics
An ERP field and a customs element may have similar names but represent different concepts.
Missing information
Some customs particulars may not exist in the source system and require enrichment or review.
Different structures
A business record may need to be separated into declaration, consignment or goods-item information.
Changing requirements
Legal amendments, code-list changes and system releases may require controlled mapping updates.
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.
Record their origin, meaning and ownership.
Identify the applicable dataset and conditions.
Specify enrichment, conversion and validation.
Track changes to rules, codes and specifications.
Include exceptions and conditional requirements.
Retain evidence of how submitted values were derived.
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.
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.
The legal foundation behind customs data.
EUCDM must be read alongside the applicable customs legislation. The legal instruments establish the requirements; the model helps represent them in a structured and technically usable form.
Union Customs Code
Regulation (EU) No 952/2013Establishes the overarching Union customs legal framework, including the principles governing customs declarations and electronic information exchange.
Read regulationUCC Delegated Regulation
Regulation (EU) 2015/2446Its Annexes A and B establish common data requirements for customs applications, decisions, declarations, notifications and related processes, as applicable.
Read regulationUCC Implementing Regulation
Regulation (EU) 2015/2447Provides implementing rules, including relevant formats and codes for common data requirements in its Annexes A and B, as amended.
Read regulationLegal interpretation: Always consult the current consolidated legislation, relevant amendments and applicable system specifications. EUCDM documentation is a technical reference and does not replace binding Union customs law.
EU Customs Data Model documentation
Consult the European Commission’s EUCDM resource for official technical documentation and information about the common customs data model.
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.