Customs Explorer
⌕

Customs Explorer

EUCDM releases

EU CUSTOMS DATA MODEL / VERSION MANAGEMENT

EUCDM Releases. Understand what changes.

Track the evolution of the EU Customs Data Model, understand version updates and assess their implications for customs data requirements, business software and electronic customs systems.

A new EUCDM publication does not automatically establish a common migration deadline for every customs application. Effective legal requirements, system-specific specifications and implementation schedules must be evaluated separately.

REFERENCE MODEL EUCDM Harmonised data requirements
CHANGE ANALYSIS Version Impact Identify affected data and rules
IMPLEMENTATION System-Specific Verify deployment requirements
RELEASE LIFECYCLE CONCEPTUAL WORKFLOW
VERSION CONTROL

From publication to implementation

01
REFERENCE UPDATE EUCDM Publication

Review the published model and release information.

02
CHANGE REVIEW Identify Differences

Examine relevant data elements, codes and conditions.

03
IMPACT ASSESSMENT Evaluate System Dependencies

Determine whether mapping, validation or interfaces are affected.

04
CONTROLLED IMPLEMENTATION Test & Deploy Changes

Follow applicable legal dates and system-specific schedules.

OFFICIAL RELEASE REFERENCE
EUCDM 7.0.11 Published August 2026

Published by the European Commission. This release reference is not a universal customs system migration deadline.

RELEASES ≠ AUTOMATIC SYSTEM DEPLOYMENT
01 / UNDERSTANDING EUCDM VERSIONS

One customs data framework. Several independent change cycles.

The EU Customs Data Model (EUCDM) provides a harmonised reference for customs data requirements and their technical representation. Its documentation evolves as the underlying legal framework and implementation needs develop.

However, an EUCDM version is not the same as a legal amendment or a release of an operational customs IT system. Understanding this distinction is essential for planning reliable customs software updates.

LEVEL 01
01

Legal Framework

Binding customs requirements

EU customs legislation establishes the legal obligations governing declarations, notifications and other customs formalities.

Union Customs Code Delegated and Implementing Acts Applicable amendments and dates
LEVEL 03
03

Customs IT Systems

Operational electronic implementation

Individual customs systems apply their own technical specifications, validation rules, connectivity arrangements and deployment schedules.

AES and NCTS implementations Other EU and national systems System-specific technical releases
VERSION RELATIONSHIP MODEL

Connected, but not interchangeable.

CONCEPTUAL VIEW
LEGAL
EU Customs Legislation Binding rules, requirements and applicable dates
LEGAL BASIS
EUCDM
Published EUCDM Version Harmonised data model and technical reference
DATA MODEL
SYSTEM A AES Implementation Relevant specifications and rollout
SYSTEM B NCTS Implementation Relevant specifications and rollout
SYSTEM C Other Customs Systems System-specific requirements
A published EUCDM version does not automatically establish the production version or migration date of every customs IT system.
02 / VERSION COMPARISON

Three update types. Three different questions.

Before updating software, identify which type of change has occurred and which authoritative source governs the required action.

DIMENSION LEGAL CHANGE EUCDM RELEASE SYSTEM RELEASE
Primary purpose Establish or amend applicable legal requirements Maintain the harmonised data reference Implement or update an operational electronic system
Authoritative source Relevant EU legislation and applicable national provisions European Commission EUCDM documentation Responsible system authority and official technical documentation
Typical impact Legal obligations, required information or procedures Data definitions, representations and reference documentation Messages, validation rules, interfaces or workflows
Relevant date Entry into force and applicability, including transitional provisions Publication or documentation version date Applicable deployment, transition or migration schedule
Developer action Assess legal and business-rule consequences Compare versions and assess affected mappings Verify compatibility and test the target implementation
03 / PRACTICAL INTERPRETATION

A new EUCDM version appears. What should developers do?

The correct response is not to assume that every connected application must immediately migrate to a new message format.

First, examine the published changes. Then determine whether they affect the declarations, data mappings and customs systems used by the organisation.

Implementation principle

EUCDM publication is a trigger for review. The need, scope and timing of a software update must be established from the applicable requirements and system specifications.

RELEASE REVIEW ILLUSTRATIVE DECISION PROCESS
01
Identify the published version Record its source, date and documentation.
02
Compare relevant changes Review affected data elements, codes and conditions.
03
Check the receiving systems Consult current official system specifications.
04
Determine the required action Document whether development, testing or monitoring is needed.
REVIEW BEFORE MIGRATION
OFFICIAL TECHNICAL SOURCE

European Commission — EU Customs Data Model

Consult the European Commission’s EUCDM resources for official model documentation and published technical reference material.

View official resource
02 / WHAT CHANGES BETWEEN RELEASES

A version number tells you that something changed. Not what.

EUCDM releases may introduce revisions to the representation, organisation or documentation of customs data requirements. The significance of a change depends on its content, the applicable legal framework and the systems that use the affected information.

A meaningful release comparison therefore looks beyond the version identifier. It examines individual changes, their dependencies and their potential consequences for data mapping, validation and electronic customs processing.

CHANGE TYPE / 01

Data Elements & Structures

Revisions may affect how data elements are described, grouped, identified or represented within the technical model.

WHAT TO EXAMINE
  • New, revised or withdrawn elements
  • Changes to element definitions
  • Groupings and structural relationships
  • Dataset-specific applicability
POTENTIAL IMPACT Data mapping and internal models
CHANGE TYPE / 02

Formats & Representation

Technical descriptions may be updated to clarify or modify how particular information is represented in the reference model.

WHAT TO EXAMINE
  • Data type and format references
  • Length and representation constraints
  • Cardinality or repetition information
  • Dependencies on the applicable dataset
POTENTIAL IMPACT Transformation and format checks
CHANGE TYPE / 03

Code Lists & References

A release may contain updated references to permitted values, classifications or code-list information relevant to customs data.

WHAT TO EXAMINE
  • New or discontinued reference values
  • Changes to code descriptions
  • Contextual restrictions and conditions
  • Effective dates from authoritative sources
POTENTIAL IMPACT Reference-data validation
CHANGE TYPE / 04

Conditions & Applicability

Changes may concern the circumstances in which information is required, permitted or relevant to a particular declaration dataset.

WHAT TO EXAMINE
  • Mandatory and conditional requirements
  • Dependencies between data elements
  • Procedure-specific applicability
  • Relevant legal and technical sources
POTENTIAL IMPACT Business rules and completeness checks
CHANGE TYPE / 05

Documentation & Clarifications

Not every change necessarily introduces a new operational requirement. Updates may improve descriptions, correct inconsistencies or clarify existing technical information.

WHAT TO EXAMINE
  • Editorial corrections and revised explanations
  • Updated cross-references
  • Clarifications of existing model concepts
  • Whether any implemented behaviour is affected
POTENTIAL IMPACT Documentation, interpretation or no code change
01 / CHANGE IMPACT MATRIX

The same change can affect different parts of a customs application.

The following matrix illustrates common dependencies that software teams should investigate. It is a planning aid, not an official EUCDM classification of release impacts.

CHANGE CATEGORY ERP MAPPING VALIDATION INTERFACE DOCUMENTATION
Data elements Review likely Assess Assess Review likely
Formats Assess Review likely Assess Assess
Code references Assess Review likely Assess Assess
Conditions Assess Review likely Assess Review likely
Editorial clarification Case dependent Case dependent Case dependent Review likely

How to read this matrix: “Review likely” identifies an area commonly relevant to the stated change category. “Assess” indicates a possible dependency. Neither label establishes that a software modification is legally or technically required in a particular case.

02 / VERSION COMPARISON EXAMPLE

From a published difference to an actionable change record.

A useful comparison does more than highlight modified text. It identifies the affected requirement, its source and the systems that depend on it.

VERSION DIFFERENCE REVIEW HYPOTHETICAL EXAMPLE
EXAMPLE CHANGE RECORD / DEMONSTRATION ONLY

Conditional Data Requirement

ILLUSTRATIVE
BEFORE / HYPOTHETICAL Reference A
DATA ELEMENT: EXAMPLE_FIELD CONDITION: REQUIRED CONTEXT: EXAMPLE DATASET

In this fictional baseline, the example field is required throughout the illustrated dataset.

AFTER / HYPOTHETICAL Reference B
DATA ELEMENT: EXAMPLE_FIELD CONDITION: CONDITIONAL CONTEXT: EXAMPLE DATASET

In the fictional revised reference, the field is required only when a defined condition is satisfied.

IMPLEMENTATION ASSESSMENT

What would need to be checked?

01 Legal basis

Determine whether the changed condition reflects an applicable legal requirement.

02 Validation logic

Identify which existing rules would incorrectly require the field.

03 System specification

Confirm how the receiving customs system implements the condition.

04 Regression testing

Test scenarios where the field is required and where it is not.

03 / SOURCE VERIFICATION

Not every difference is a new legal obligation.

Changes should be classified by their authoritative source before they are translated into software requirements.

LEGAL SOURCE

Binding Requirement

Verify the relevant regulation, amendment, applicable date and transitional provisions.

MODEL SOURCE

EUCDM Reference

Review the published technical documentation and identify the exact reference change.

SYSTEM SOURCE

Operational Specification

Confirm whether the relevant customs system requires a corresponding technical update.

03 / RELEASE COMPARISON & IMPACT ASSESSMENT

Detect the difference. Understand the consequence.

Comparing EUCDM releases is not simply a matter of identifying modified fields or changed documentation. The objective is to determine whether a published difference affects the customs processes, data requirements and technical systems used by an organisation.

A structured impact assessment connects each relevant change to its authoritative source, affected datasets, implementation dependencies and required actions. This prevents unnecessary software changes while reducing the risk of overlooking important updates.

STEP 01 01

Establish the Baseline

Identify the currently used EUCDM reference and the newly published version. Preserve the exact documentation and relevant publication information.

OUTPUT Version comparison scope
STEP 02 02

Identify Changes

Review release documentation and compare relevant data elements, representations, code references, conditions and technical explanations.

OUTPUT Documented change inventory
STEP 03 03

Evaluate Dependencies

Determine which customs datasets, ERP mappings, validation rules and electronic systems depend on the changed information.

OUTPUT Impact and dependency register
STEP 04 04

Decide & Document

Verify the applicable legal and system requirements, determine the necessary response and record the rationale for each implementation decision.

OUTPUT Approved action or no-change decision
01 / RELEASE IMPACT FRAMEWORK

Turn release differences into traceable decisions.

The following example demonstrates how a change can be classified and assessed. It uses fictional identifiers and does not represent an actual EUCDM release comparison or a live analysis tool.

EUCDM / RELEASE IMPACT ASSESSMENT ILLUSTRATIVE DATASET
COMPARISON CONTEXT

Reference A → Reference B

Hypothetical comparison showing how different types of changes may require different implementation decisions.

DEMONSTRATION
CHANGE RECORD CHANGE TYPE DEPENDENCY ASSESSMENT POSSIBLE ACTION
EX-001 Field representation revised Format Data transformation REVIEW Check mapping and validation
EX-002 Reference value updated Code reference Reference-data controls REVIEW Verify applicable code source
EX-003 Documentation wording clarified Editorial Internal documentation LOW Update guidance if needed
EX-004 Condition modified Applicability Business-rule engine PRIORITY Verify requirement and test scenarios
04 EXAMPLE RECORDS
03 TECHNICAL REVIEWS
01 EDITORIAL REVIEW
00 CONFIRMED DEPLOYMENTS
Assessment is not deployment approval.

These classifications identify review priorities. They do not establish that a particular software update is mandatory or that the receiving customs system has adopted the hypothetical changes.

Fictional records EX-001 to EX-004 are provided exclusively to demonstrate an impact-assessment methodology.
02 / IMPLEMENTATION DECISIONS

Not every change requires a software release.

The result of an assessment should be a documented decision supported by the relevant evidence. Different outcomes may be appropriate depending on the affected process and system.

OUTCOME 01

No Software Change

The change is irrelevant to the organisation’s datasets, does not affect implemented behaviour or requires documentation only.

OUTCOME 02

Reference-Data Update

Applicable values or reference information must be refreshed without necessarily changing the application architecture.

OUTCOME 03

Application Modification

Mapping, transformation, validation or business-rule logic must be modified to satisfy verified requirements.

OUTCOME 04

System Migration

A receiving system requires an updated interface, technical configuration or migration process according to its applicable implementation arrangements.

03 / EVIDENCE & TRACEABILITY

Every implementation decision should be reproducible.

A release review becomes valuable when another developer, compliance specialist or auditor can understand what changed, why it mattered and how the organisation responded.

Source Evidence

Identify the official document, publication, applicable version and precise requirement supporting the assessment.

Dependency Evidence

Record the affected data mappings, datasets, validation rules, interfaces and business processes.

Decision Evidence

Explain the selected action, responsible owner, approval and rationale, including decisions not to modify software.

Testing Evidence

Preserve relevant test cases, outcomes and deployment records when a technical modification is implemented.

04 / MIGRATION, TESTING & DEPLOYMENT

A release is not complete when the code is deployed.

Once an EUCDM-related change has been assessed and a technical modification is confirmed as necessary, implementation must be planned around the requirements of the affected customs process and receiving electronic system.

Reliable deployment requires more than updating data mappings. Teams must establish the applicable dates, verify technical dependencies, test expected behaviour, prepare operational recovery procedures and monitor the system after release.

CONTROLLED RELEASE PIPELINE REFERENCE WORKFLOW
CHANGE DELIVERY MODEL

Six controls between approval and production

A practical implementation sequence for customs applications affected by verified legal, data-model or system-specific changes.

01
PLAN

Confirm Scope

Define affected declarations, data flows, interfaces and responsible owners.

02
VERIFY

Check Dependencies

Confirm specifications, access, credentials, environments and relevant dates.

03
IMPLEMENT

Apply Changes

Update mappings, reference data, validation or interface components as required.

04
TEST

Verify Behaviour

Run relevant unit, integration, negative and regression test scenarios.

05
RELEASE

Deploy Safely

Follow the approved deployment window and documented recovery procedure.

06
MONITOR

Confirm Operations

Track processing outcomes, failures, acknowledgements and unresolved cases.

Release gate: do not treat successful internal testing as proof that a receiving customs system will accept the updated messages. External compatibility must be established using the applicable system documentation and available verification procedures.

CONTROLLED DEPLOYMENT REQUIRES VERIFIED DEPENDENCIES
01 / EFFECTIVE DATES & TRANSITION WINDOWS

One change may involve several different dates.

Release planning must distinguish the publication of technical reference material from the dates on which legal obligations or operational system requirements become applicable.

DATE TYPE / 01

EUCDM Publication

The date on which a version of the technical reference is published or made available.

DOES NOT AUTOMATICALLY MEAN Immediate software migration
DATE TYPE / 02

Legal Applicability

The date from which a particular legal requirement applies, taking account of relevant amendments and transitional provisions.

VERIFY THROUGH Applicable legal instruments
DATE TYPE / 03

System Deployment

The date on which the responsible authority introduces or changes functionality in a particular customs electronic system.

VERIFY THROUGH Official system communications
DATE TYPE / 04

Operator Transition

An applicable period or deadline for economic operators or software providers to adopt a specific operational arrangement.

VERIFY THROUGH Relevant implementation arrangements

Important distinction: not every change has all four dates, and not every system provides a transition period. The applicable arrangements must be confirmed individually. Never infer a migration deadline solely from an EUCDM publication date.

02 / REGRESSION & COMPATIBILITY TESTING

Test what changed. Then test what should not change.

Customs integrations often contain dependencies between data elements, business rules and declaration workflows. A modification that corrects one scenario can unintentionally affect another.

TEST CATEGORY WHAT TO VERIFY EXPECTED EVIDENCE
Data Mapping Source fields are correctly transformed into the required target representation. Mapping test results
Format Validation Length, type, structure and repetition constraints are correctly applied. Positive and negative cases
Conditional Rules Data requirements respond correctly to the applicable declaration context. Rule-specific scenarios
Reference Data Applicable codes and validity periods are interpreted correctly. Code-list test records
Interface Compatibility Messages and exchanges conform to the relevant receiving-system specification. Integration test outcomes
Regression Previously supported declaration scenarios continue to behave as expected. Regression test report
Failure & Recovery Rejections, timeouts, retries and interrupted workflows are handled safely. Recovery test evidence
03 / OPERATIONAL INCIDENT SCENARIO

A message is rejected after a system update. What next?

The following fictional example illustrates how release management and operational troubleshooting should work together.

INCIDENT SIMULATION

Reference-Code Validation Failure

HYPOTHETICAL
01
Detect

A customs message fails validation. The application records the response and identifies the affected submission.

02
Investigate

The team compares the submitted reference value with the applicable system specification and authoritative code source.

03
Correct

If a configuration defect is confirmed, the relevant reference data or mapping is corrected and tested.

04
Recover

The team follows the system’s permitted correction or resubmission procedure, avoiding uncontrolled duplicate submissions.

Operational status matters. A technical acknowledgement, a validation rejection, declaration acceptance and customs release are different events. Their precise meaning and message handling depend on the relevant customs system.

04 / PRODUCTION READINESS

Before deployment, verify the complete operating chain.

A controlled go-live decision should be based on documented evidence, not only on successful development or the publication of a new model version.

01

Requirements Confirmed

Legal, EUCDM and receiving-system requirements have been identified and distinguished.

02

Dates Verified

Relevant applicability, transition and deployment dates have been confirmed.

03

Dependencies Available

Required specifications, access arrangements, credentials and environments have been checked.

04

Tests Documented

Relevant mapping, validation, integration and regression tests have been completed.

05

Recovery Prepared

Rollback or alternative recovery procedures have been assessed for the affected workflow.

06

Monitoring Assigned

Responsible owners can detect failures, investigate responses and manage unresolved declarations.

05 / FREQUENTLY ASKED QUESTIONS

EUCDM Releases. Questions answered.

Understanding EUCDM version management requires distinguishing technical documentation from binding legal requirements and operational customs system specifications. These answers address common questions about releases, migration and compliance.

01 What is an EUCDM release?

An EUCDM release is a published version of the European Commission’s EU Customs Data Model. The model brings together structured information about customs data requirements derived from EU legislation and supports the development and maintenance of customs IT systems.

A release may incorporate legal amendments, updated data representations, code references, corrections or usability improvements. The actual changes should be checked against the official release documentation.

02 What is the latest published EUCDM version?

As reported by the European Commission in August 2026, EUCDM version 7.0.11 was published with updates relating to low-value consignments, corrections to legal-text alignment and improvements to the presentation of requirements.

Version information is time-sensitive. Consult the official European Commission EUCDM portal to establish the most recent publication before starting a new project or release assessment.

Check the official EUCDM portal ↗
03 Does a new EUCDM version create an immediate legal obligation?

Not by itself. EUCDM is a technical reference representing customs data requirements. Binding obligations arise from the applicable legal instruments, including relevant amendments, applicability dates and transitional provisions.

A new model publication should prompt a review, but its publication date must not automatically be treated as a universal compliance or software migration deadline.

04 Do AES and NCTS automatically adopt every EUCDM release?

No automatic one-to-one adoption should be assumed. AES, NCTS and other customs electronic systems operate according to their applicable functional and technical specifications, implementation arrangements and deployment schedules.

A software provider must verify the requirements of the actual receiving system, including relevant national implementation details, rather than relying exclusively on an EUCDM version identifier.

05 How can developers identify changes between EUCDM versions?

Developers should review the official documentation and available release information, then compare the relevant data elements, structures, formats, code references and applicability conditions.

Each significant difference should be linked to its authoritative source and assessed against the datasets, mappings, validation rules and interfaces actually used by the organisation.

06 Are EUCDM code lists always sufficient for customs validation?

Not necessarily. EUCDM provides relevant harmonised references, but operational validation may also depend on the applicable legal context, system-specific rules, reference-data validity and national implementation requirements.

A value appearing in a reference list does not establish that it is valid for every procedure, declaration type, date or receiving customs system.

07 Does EUCDM provide a universal customs submission API?

No. EUCDM is a harmonised data reference, not a universal electronic submission interface through which every customs declaration can be transmitted.

Connectivity depends on the relevant customs electronic system, its technical specifications and the access arrangements established by the responsible authority. API availability, certification and testing conditions must be verified for each intended integration.

08 What should an organisation retain after a release assessment?

Good release governance includes retaining the reviewed documentation versions, identified differences, affected requirements, dependency assessments and implementation decisions.

Where changes are implemented, relevant testing results, approvals, deployment records and operational incident information should also be preserved according to the organisation’s applicable recordkeeping and governance arrangements.

06 / LEGAL & OFFICIAL REFERENCES

The legal foundation. The official technical source.

EUCDM draws on the Union Customs Code framework and related legal data requirements. The following sources should be consulted in their applicable, amended versions when evaluating a release.

PRIMARY LEGISLATION §

Union Customs Code

Regulation (EU) No 952/2013

Establishes the Union Customs Code, including the legal framework for customs formalities, electronic information exchange and data requirements.

Read on EUR-Lex
DELEGATED ACT A

UCC Delegated Regulation

Commission Delegated Regulation (EU) 2015/2446

Contains detailed customs rules. Annex B establishes common data requirements for declarations, notifications and proof of customs status. Other annexes cover additional datasets.

Read on EUR-Lex
IMPLEMENTING ACT B

UCC Implementing Regulation

Commission Implementing Regulation (EU) 2015/2447

Establishes implementing provisions, including formats and codes associated with common customs data requirements in Annex B and other relevant annexes.

Read on EUR-Lex
OFFICIAL TECHNICAL RESOURCE ↻

European Commission EUCDM

Directorate-General for Taxation and Customs Union

Official information about the EU Customs Data Model, published versions, technical reference material and access to EUCDM resources.

Open EUCDM resource
EUCDM / FINAL PERSPECTIVE

A published version is information. A verified impact is a decision.

Effective EUCDM release management connects harmonised customs data references to applicable legislation, system-specific technical requirements and controlled implementation processes.

The objective is not to update software whenever a version number changes. It is to maintain accurate, compliant and reliable customs data processing as requirements evolve.

VERIFY Authoritative sources
ASSESS Actual dependencies
IMPLEMENT Controlled changes
MONITOR Operational reliability