EUCDM 7.0 explained: the data standard behind the Data Hub

What is the EUCDM?

The EU Customs Data Model (EUCDM) is the definitive data model for all EU customs electronic systems. It translates legal data requirements from EU customs legislation into a structured, machine-readable format. Version 7.0, released in April 2025, is the current standard.

The EUCDM serves as a single authoritative source for national customs IT development. Every member state's customs system must conform to it, and the upcoming Customs Data Hub will use it as its native data format.

How the EUCDM is structured

The data model is organised into several annexes, each covering different customs procedures:

• Annex A covers applications and decisions data requirements (authorisations, binding tariff information, etc.)
• Annex B covers declarations and notifications (import, export, transit declarations). This is the most relevant annex for most traders.
• Annex C contains additional data elements used across multiple procedures
• Annex D provides supplementary provisions
• Annex 12-01 defines the EORI dataset for economic operator registration
• SURV datasets cover surveillance and trade flow monitoring data

Key data elements for declarations

Annex B defines the data elements that traders must provide in customs declarations. Key categories include:

• Declaration type and additional declaration type codes
• HS/CN commodity codes (validated against the TARIC3 database)
• INCOTERM codes for trade terms
• Mode of transport at the border
• Container identification (size, type, packed status, supplier type)
• Customs office references
• Guarantee type and method of payment
• Additional procedure codes
• Supply chain actor roles and identifications

Each data element has a precise format specification, validation rules, and cross-references to the legal provisions that require it.

Technical formats

The EUCDM is available in several formats:

• XML datasets that can be downloaded from the official EUCDM website (eucdm.softdev.eu.com). These provide standardised, machine-readable customs data structures.
• GEFEG.FX files for use with the GEFEG data modelling tool, which is the same tooling used by the World Customs Organization.
• Multilingual documentation currently available in English, French, and German.

The model also includes a simulation date function that allows stakeholders to preview future legal data requirement changes before they take effect.

Compatibility with international standards

The EUCDM is fully mapped to the WCO (World Customs Organization) Data Model version 4.1. The architecture works in three layers:

1. WCO Data Model (global standard)
2. EUCDM (EU layer, adding EU-specific requirements)
3. National CDM (member state layer, adding national specifics)

This layered approach means that systems built to EUCDM specifications are inherently compatible with WCO standards, which matters for businesses trading outside the EU as well.

Legal basis

The EUCDM implements data requirements from three main regulations:

• UCC (Regulation (EU) No 952/2013), the Union Customs Code that is being replaced by the reform
• UCC-DA (Commission Delegated Regulation (EU) 2015/2446), the delegated act with detailed provisions
• UCC-IA (Commission Implementing Regulation (EU) 2015/2447), the implementing act with procedural rules

What this means for your systems

If your organisation submits customs declarations, your systems need to produce data that conforms to EUCDM 7.0. The practical steps are:

1. Download the EUCDM XML schemas from the official website and compare them against your current data structures.
2. Identify gaps. Many organisations will find that they collect the right data but store it in formats that do not map cleanly to EUCDM elements.
3. Plan mapping work. Building data transformations between your internal models and EUCDM structures is typically the largest piece of technical work.
4. Test against validation rules. Each data element has specific format and content rules. Automated validation against these rules should be part of your integration pipeline.