Customs Explorer
⌕

Customs Explorer

Reference data

EU CUSTOMS DATA ARCHITECTURE REFERENCE SYSTEMS

Customs
Reference Data.

The controlled codes, classifications and reference values that give structure to EU customs information.

Customs declarations and connected business systems rely on shared reference values to identify countries, goods, procedures, document types and other regulated data elements. Understanding where these values come from, when they apply and how they change is essential for consistent customs information management.

Standardised Shared codes and values
Time-sensitive Effective dates and changes
Context-dependent Applicable rules and datasets
REFERENCE DATA / SYSTEM VIEW
EU CONTEXT
CONTROLLED REFERENCE LAYER 01 / 03
REF / 01 Country Codes Geographical identifiers
REF / 02 Goods Codes Tariff nomenclature
REF / 03 Procedure Codes Customs procedure values
REF / 04 Document Codes Supporting document types
BUSINESS INFORMATION LAYER Customs Master Data Products · partners · approved assessments
OPERATIONAL APPLICATION Customs Transactions Declarations · shipment-specific information
01 / IDENTIFY Use the correct reference

Determine which official or applicable dataset governs a particular data element.

02 / VALIDATE Check meaning and applicability

Confirm that the value is valid for the relevant context, date and customs procedure.

03 / MAINTAIN Manage changes over time

Monitor updates and prevent outdated values from being reused without appropriate checks.

01 / REFERENCE DATA DOMAINS

The codes behind
customs information.

EU customs processes use structured codes and reference values to represent information consistently. These values may come from EU-level datasets, customs legislation, international standards or national implementations. Their correct use depends on the relevant procedure, system, jurisdiction and date.

CORE REFERENCE DOMAINS

Six families of controlled information.

The following categories provide a practical way to understand reference data. They are an explanatory grouping, not an official six-part taxonomy prescribed by EU customs legislation.

01 / GEOGRAPHY

Country & Territory Codes

Structured geographical identifiers used in customs information, including country or territory references relevant to origin, destination and other declaration data.

ILLUSTRATIVE VALUES
DE FR IT
Examples of two-letter country codes; applicable customs code lists must be checked.
KEY CONTROL Correct code list, territory and effective date
02 / GOODS

Commodity & Tariff Codes

Structured goods nomenclatures used to describe product categories for customs and tariff purposes, including the Harmonized System, Combined Nomenclature and TARIC subdivisions.

CODE STRUCTURE
HS · 6 digits CN · 8 digits TARIC · 10 digits
Different levels of nomenclature serve different regulatory purposes.
KEY CONTROL Applicable nomenclature, classification and date
03 / PROCEDURES

Customs Procedure Codes

Coded values identifying customs procedures and relevant procedure combinations within applicable customs declaration data requirements.

REFERENCE CONTEXT
Requested procedure Previous procedure
The meaning and permitted combinations must be assessed against applicable rules.
KEY CONTROL Permitted values, combinations and conditions
04 / DOCUMENTS

Document & Certificate Codes

Reference values used to identify supporting documents, certificates, authorisations and other document-related information in customs declarations and connected systems.

REFERENCE CONTEXT
Document type Certificate type Authorisation reference
A document code does not itself establish that a required document is valid or available.
KEY CONTROL Code applicability and supporting evidence
05 / MEASUREMENT

Units & Measurement Codes

Controlled values representing quantities, units and supplementary measurement information where required for customs and tariff purposes.

REFERENCE CONTEXT
Net mass Supplementary units Quantity codes
Required measurements depend on the data element and applicable goods nomenclature.
KEY CONTROL Correct unit, quantity and conversion
06 / REGULATORY

Regulatory & Status Codes

Additional controlled values used in specific customs processes, including relevant declaration indicators, status values and regulatory classifications where applicable.

REFERENCE CONTEXT
Additional codes Declaration indicators Status values
Code availability and meaning can depend on the procedure or information system.
KEY CONTROL Correct dataset, context and version
DATA ARCHITECTURE

Reference data is not the same as master data.

Reference values, enterprise master records and transaction-specific information perform different functions. They often work together within the same customs process.

01 / SHARED VOCABULARY

Reference Data

Defines recognised codes, values and classifications used to structure information.

EXAMPLE An applicable country code or commodity code
MAIN QUESTION Which value is recognised and applicable?
02 / REUSABLE BUSINESS RECORD

Master Data

Describes an enterprise entity, such as a product or business partner, using maintained attributes and assessments.

EXAMPLE A product record with an approved classification
MAIN QUESTION What is known about this business entity?
03 / INDIVIDUAL OPERATION

Transaction Data

Describes the specific goods movement, declaration or operation being performed.

EXAMPLE A declaration with its actual quantity and procedure
MAIN QUESTION What applies to this particular operation?
REFERENCE DATA Recognised codes
MASTER DATA Approved product information
TRANSACTION DATA Actual shipment facts
OPERATIONAL OUTPUT Prepared customs information

This is a conceptual model. A declaration’s legal correctness depends on the applicable requirements and the accuracy of the information supplied, not merely on combining these three data categories.

REFERENCE DATA VALIDATION

A valid code is not always an applicable code.

Reference-data validation should consider more than whether a value exists in a list. A code may be recognised but inappropriate for the procedure, date, territory or specific goods involved.

Control dimension Question to verify Illustrative failure Recommended response
Source Does the value come from the appropriate reference dataset? A code is copied from an unrelated application list. Identify and use the applicable authoritative source.
Existence Is the code recognised in the relevant code list? An obsolete or mistyped value is entered. Validate against the controlled reference list.
Validity period Was the value applicable on the relevant date? A code introduced later is used for an earlier operation. Check effective dates and applicable versions.
Context Is the code permitted for the intended data element and procedure? A recognised value is used in the wrong declaration context. Apply contextual validation rules.
Geographical scope Does the reference apply to the relevant territory or jurisdiction? A territorial distinction is ignored. Verify geographical applicability.
Consistency Does the code agree with related fields and supporting information? Procedure and document information conflict. Investigate the discrepancy before relying on the record.
PRACTICAL EXAMPLE

One product. Several layers of reference data.

ILLUSTRATIVE SCENARIO

A company prepares an import declaration for an industrial component. Its internal product record provides technical information, but the declaration also requires relevant reference values selected under the applicable customs rules.

PRODUCT MASTER

Industrial component

Description, composition, technical specifications and supporting documentation.

REFERENCE DATA

Applicable coded values

Goods nomenclature, country references, procedure values and document codes, as relevant to the operation.

TRANSACTION

Specific import

Actual quantity, customs value, parties, movement and requested customs procedure.

Control objective

Confirm that the relevant reference values are valid and applicable to the specific transaction. Product classification and other customs determinations must also be substantively correct; successful code-list validation alone is insufficient.

Reference data provides a shared vocabulary, not an automatic compliance decision. Reliable customs information depends on using the right values, from the right sources, within the correct legal and operational context.

02 / OFFICIAL SOURCES & DATA AUTHORITY

Reference data begins
with the right source.

Not every customs code comes from the same database. The European Union maintains different legal instruments, reference systems and operational datasets. National customs administrations may also publish values or implementation guidance relevant to their systems.

THE SOURCE LANDSCAPE

Understand the different layers of authority.

A reliable customs information process distinguishes legally binding provisions from the datasets, technical code lists and interfaces used to implement them.

02 / GOODS NOMENCLATURE

Combined Nomenclature

CN — Eight-digit EU classification

The Combined Nomenclature provides the EU goods nomenclature used for customs tariff and external trade statistics purposes. It builds on the international Harmonized System and is updated through EU legislation.

WHAT IT DEFINES
CN codes Product descriptions Legal classification structure Annual updates
Important distinction

The CN and TARIC are related but not identical. CN provides eight-digit subdivisions, while TARIC introduces further subdivisions and integrates applicable EU measures.

Regulation (EEC) No 2658/87
03 / DECLARATION DATA

UCC Annex B

Customs declaration data requirements

Annex B provisions in the UCC delegated and implementing framework establish data requirements and related formats and codes for customs declarations, notifications and proofs of customs status, as applicable.

WHAT IT SUPPORTS
Data elements Formats Codes Declaration contexts
Important distinction

Requirements depend on the declaration type, procedure and applicable legal provisions. Annex B must be read in its relevant amended form, including applicable transitional rules.

UCC Implementing Regulation
04 / CUSTOMS SYSTEMS

EU Customs System Code Lists

System-specific technical references

Electronic customs systems may publish technical specifications and reference lists governing message structures, accepted values and validation rules for particular processes.

EXAMPLE CONTEXTS
NCTS AES ICS2 Message validation
Important distinction

Code lists can differ by system, message specification and version. A value accepted by one interface is not necessarily accepted by another.

European Commission — Electronic Customs
05 / GEOGRAPHICAL DATA

Country & Territory References

Geographical codes and customs territories

Country and territory identifiers are used in customs datasets and declaration information. Their interpretation may depend on geographical code lists and specific customs or statistical territorial rules.

WHAT TO CHECK
Code-list authority Territorial scope Effective date System compatibility
Important distinction

Country identifiers must not be confused with the legal concepts of customs territory, origin, destination or preferential eligibility.

Union Customs Code
06 / NATIONAL IMPLEMENTATION

National Customs References

Member State systems and instructions

National customs administrations may publish implementation specifications, supplementary national codes and operational guidance for their customs systems, within the applicable EU and national legal framework.

WHAT TO CHECK
Member State National interface Local requirements Release version
Important distinction

National technical requirements should be distinguished from EU-wide legal obligations. A national implementation detail should not automatically be treated as an EU-wide rule.

European Commission — Customs
SOURCE AUTHORITY MODEL

From legal rules to operational values.

Legal provisions, official reference datasets and technical interfaces are connected, but they perform different functions. Each must be evaluated according to its authority and intended purpose.

LAYER 02
OFFICIAL REFERENCE SOURCES

TARIC, CN & Applicable Code Lists

Organise and expose reference values used for classification, tariff measures and structured customs information.

REFERENCE
LAYER 03
TECHNICAL IMPLEMENTATION

Customs Systems & Enterprise Applications

Use applicable codes and validation rules within declarations, integrations and business processes.

APPLICATION

Conceptual model: these layers are not a formal legal hierarchy of databases. Official systems may contain values derived from multiple legal instruments, and technical specifications may impose operational constraints without independently creating substantive customs law.

SOURCE SELECTION

Choose the source before trusting the value.

A practical reference-data process should record not only the code itself but also where it came from, which version applies and the context in which it may be used.

01

Identify the data element

Determine whether the information concerns goods nomenclature, procedures, documents, geography or another coded field.

02

Determine the applicable context

Establish the customs procedure, declaration type, Member State, system and relevant date.

03

Select the authoritative reference

Use the relevant legal instrument, official dataset or applicable system specification.

04

Verify applicability

Check validity dates, territorial scope, conditions and relationships with other required data.

05

Record source and version

Preserve enough information to identify which reference dataset and rules supported the selected value.

06

Monitor subsequent changes

Reassess affected records and integrations when the relevant nomenclature, code list or system rules change.

PRACTICAL SCENARIO

One declaration, multiple reference sources.

ILLUSTRATIVE

A company prepares an EU import declaration for industrial equipment. Different fields may require validation against different sources, even though they appear together in a single declaration.

GOODS CLASSIFICATION CN / TARIC

Establish the appropriate goods code and examine relevant tariff measures.

DECLARATION STRUCTURE UCC Data Requirements

Identify applicable data elements, formats and coded values.

MESSAGE SUBMISSION Customs System Specifications

Check technical requirements for the relevant declaration interface.

Control objective: ensure that each reference value is sourced and validated according to its own rules. A technically accepted message is not, by itself, proof that every customs determination is legally correct.

Reliable reference data requires source awareness. Correct customs information depends on using the appropriate legal framework, official reference values and technical specifications for the relevant operation.

03 / VALIDITY & VERSION CONTROL

A code can exist.
And still be wrong.

Customs reference data is not static. Goods nomenclatures, tariff measures and technical code lists evolve over time. Reliable systems must evaluate not only whether a value exists, but whether it is applicable to the relevant transaction, date and regulatory context.

TEMPORAL VALIDITY

Four dates. Different meanings.

A reference-data update may have several important dates. Treating them as interchangeable can produce incorrect validations and unnecessary changes to historical records.

01 / PUBLICATION

Publication Date

When a legal act, dataset update or technical specification is published or made available.

CONTROL QUESTION When did the organisation become able to identify the change?
02 / APPLICABILITY

Effective Date

The date from which the relevant value, measure or requirement becomes applicable under the governing rules.

CONTROL QUESTION From which date should the new reference be used?
03 / INTERNAL RELEASE

System Activation Date

When an organisation activates a new reference version in its ERP, customs software or validation service.

CONTROL QUESTION Was the correct version available when operations needed it?
04 / TRANSACTION

Relevant Customs Date

The legally relevant date used to assess a particular requirement or measure. It is not necessarily the invoice, shipment or system-processing date.

CONTROL QUESTION Which date governs this specific customs determination?
Important legal distinction

Different customs provisions may use different legally relevant dates. For example, the rules governing customs debt and applicable duty rates must be assessed under the relevant UCC provisions. There is no universal date that automatically determines the validity of every customs code or regulatory measure.

VERSION HISTORY

Keep the past intact while the rules evolve.

Historical customs records should retain enough information to reconstruct the references used at the time. New versions should not silently overwrite the basis of earlier decisions.

REFERENCE DATASET Illustrative version history
EXAMPLE ONLY
V1
01 JAN 2026

Baseline Reference Version

A controlled reference snapshot is approved for the relevant operational context.

HISTORICAL
V2
01 JUL 2026

Updated Reference Version

A new version becomes applicable for the illustrated process. Earlier records retain their previous reference context.

ILLUSTRATIVE ACTIVE VERSION
V3
FUTURE RELEASE

Pending Change Assessment

A proposed change is reviewed, mapped to affected records and tested before controlled activation.

PENDING

The dates and versions above are fictional examples. They do not represent actual CN, TARIC or customs-system releases.

CHANGE CLASSIFICATION

Not every update has the same impact.

The required response depends on whether a change affects a code, its meaning, a tariff measure, its validity period or the technical rules of a customs interface.

01 / NOMENCLATURE

Code Creation, Deletion or Restructuring

Changes to goods nomenclature may require reassessment of product classifications, mappings and affected master records.

RESPONSE Identify affected products and review classification decisions.
02 / TARIFF MEASURES

Measure Introduction or Expiry

A tariff measure may change without changing the underlying goods code, affecting duties or applicable regulatory conditions.

RESPONSE Recheck measures by goods code, origin, date and conditions.
03 / DECLARATION CODES

Code-List Modification

A declaration value may be introduced, withdrawn or restricted to particular data elements or procedures.

RESPONSE Update controlled lists and validate affected business rules.
04 / TECHNICAL INTERFACES

Message Specification Changes

Customs systems may change message structures, validation rules or accepted code-list versions through controlled technical releases.

RESPONSE Test interfaces and coordinate deployment with system requirements.
CONTROLLED CHANGE MANAGEMENT

From an official update to a controlled release.

A reference-data change should follow a repeatable process that connects source monitoring, impact analysis, approval, implementation and verification.

01

Detect

Identify changes from relevant official legal publications, datasets or system specifications.

02

Assess

Determine effective dates, affected codes, business processes and dependent records.

03

Approve

Obtain the appropriate business, customs and technical approvals for the proposed response.

04

Deploy

Release the new reference version through controlled integration and activation procedures.

05

Verify

Confirm correct behaviour, monitor rejected values and retain evidence of the change.

Release principle: a technical deployment should not be treated as approval of the underlying legal interpretation. Substantive customs determinations require appropriate specialist review.

PRACTICAL SCENARIO

When a tariff code changes between two operations.

ILLUSTRATIVE

A company imports the same industrial component in two different periods. Between the operations, the applicable goods nomenclature is amended. The business must determine how the change affects classification and declaration preparation.

BEFORE THE CHANGE

Earlier import

REFERENCE VERSION A

The earlier declaration was prepared using the reference values applicable to that operation, subject to the relevant legal rules.

CHANGE EVENT

Nomenclature amendment

REASSESSMENT REQUIRED

The company reviews whether the amendment changes the appropriate classification, related measures or product master-data mapping.

AFTER THE CHANGE

Later import

REFERENCE VERSION B

The later operation is assessed using the applicable nomenclature and measures, with an updated, documented determination where necessary.

Do not automatically rewrite historical declarations.

A later reference-data change does not, by itself, establish that an earlier declaration was incorrect. Historical correctness must be assessed under the rules applicable to that operation. Any correction or amendment follows the relevant customs procedures.

AUDIT & TRACEABILITY

Know which version supported each decision.

Version traceability helps businesses investigate discrepancies, reproduce historical decisions and explain how reference values were selected.

Reference dataset and source identifier

Published or recorded dataset version

Relevant effective date or validity interval

Applicable customs and business context

Change assessment and approval record

Deployment, validation and exception history

These are recommended internal governance controls, not a prescribed six-field EU legal record format. Statutory recordkeeping obligations must be assessed separately under the applicable rules.

Reference-data governance is also time governance. A reliable customs system must distinguish historical validity, current applicability, future changes and the version used for each relevant operational decision.

04 / ERP INTEGRATION & VALIDATION

One reference layer.
Connected customs systems.

Reference data becomes operationally valuable when business applications use the correct codes, versions and validation rules. ERP integration should reduce inconsistent values without replacing the specialist decisions required for customs compliance.

INTEGRATION ARCHITECTURE

From official sources to operational use.

A controlled reference-data service can distribute applicable values to multiple systems. The architecture below is illustrative: EU legislation does not prescribe this particular software arrangement.

REFERENCE DATA DISTRIBUTION MODEL
CONCEPTUAL ARCHITECTURE
EU REFERENCE CN & TARIC Nomenclature and tariff measures
DECLARATION DATA UCC Code Lists Applicable formats and codes
TECHNICAL SOURCES System Specifications Message and interface rules
NATIONAL CONTEXT Member State Sources Applicable national references
CONTROLLED REFERENCE DATA LAYER

Reference Data Management

Source tracking, validity rules, version management and controlled distribution.

Source verification Effective-date checks Version history Change approval Mapping controls Exception logging
BUSINESS SYSTEM ERP / Product Master Reusable business records
CUSTOMS APPLICATION Declaration Preparation Applicable customs values
CONTROL SYSTEM Compliance Validation Rules and exceptions
SOURCE TRACEABILITY · VALIDITY CONTROL · CONSISTENT DISTRIBUTION
SYNCHRONISATION PATTERNS

Different update methods. Different risks.

The appropriate integration method depends on source availability, update frequency, data volume, system capabilities and operational requirements. Not every official dataset provides a public API.

01 / SCHEDULED

Batch Synchronisation

Import approved reference files or snapshots at planned intervals, followed by validation and controlled activation.

SUITABLE WHEN Periodic updates and supported file-based distribution
MAIN RISK Changes may occur between scheduled imports
02 / SERVICE-BASED

API-Based Retrieval

Retrieve reference information through an authorised and supported service interface where one is available.

SUITABLE WHEN A documented service supports the required data and access
MAIN RISK Availability, licensing, authentication and version dependencies
03 / CHANGE-DRIVEN

Event-Driven Distribution

Notify connected enterprise systems after a reference-data change has been reviewed and approved internally.

SUITABLE WHEN Multiple internal applications need coordinated updates
MAIN RISK Missed events or inconsistent deployment across systems

Technical feasibility must be verified first. Before designing an automated connector, confirm that the specific dataset can be lawfully obtained, in the required format and frequency, under acceptable access, licensing and operational conditions.

AUTOMATED CONTROLS

Validate the value, the version and the context.

Reference-data automation is most effective when it distinguishes basic technical checks from legal and business determinations that require additional evidence or specialist review.

Control System verification Failure example Expected handling
Source integrity Verify the imported dataset and its provenance. An incomplete or unexpected file is received. Reject or quarantine the update pending investigation.
Code existence Check that a value exists in the relevant code list. An obsolete document code remains in the ERP. Flag the record and prevent inappropriate reuse.
Temporal validity Compare the code validity interval with the relevant date. A future code is selected for an earlier operation. Apply the appropriate version or refer for review.
Contextual applicability Check available rules for procedure, data element and territory. A recognised code is not permitted in the selected context. Return a contextual validation error.
Cross-field consistency Compare related codes and relevant business attributes. A document code conflicts with the declared procedure. Escalate the discrepancy for correction or assessment.
Version alignment Compare reference versions used by connected applications. ERP and customs software use incompatible code-list releases. Hold affected processing and coordinate the update.
Auditability Record the reference source, version and validation outcome. A historical decision cannot be reconstructed. Preserve traceable validation and change records.

The matrix describes recommended internal controls. The exact checks depend on the relevant system and applicable legal requirements.

EXCEPTION MANAGEMENT

Automation needs a controlled failure path.

Invalid or uncertain reference values should not be silently substituted. The system should make the problem visible and route it to the appropriate operational or customs specialist.

01

Detect

Identify an invalid, expired, missing or contextually inconsistent value.

02

Classify

Distinguish technical mapping errors from substantive customs questions.

03

Resolve

Correct the reference, update the mapping or obtain specialist review.

04

Verify

Revalidate the affected information and record the resolution.

Do not guess replacement codes. An automated system should not replace an unrecognised customs value with a plausible alternative unless an authorised, validated mapping rule supports that substitution.

PRACTICAL SCENARIO

When the ERP and customs software disagree.

ILLUSTRATIVE

A company updates its customs application to a new reference-data version. Its ERP continues to supply a document code from an older internal mapping table.

ERP SYSTEM

Outdated Mapping

REFERENCE VERSION A

The ERP sends a previously configured value without recognising the newer validation requirements.

INTEGRATION CONTROL

Version Mismatch

EXCEPTION DETECTED

The validation layer identifies the incompatibility and prevents automatic acceptance of the disputed value.

CUSTOMS APPLICATION

Controlled Resolution

REVIEW & REVALIDATE

The responsible team checks the applicable code list, updates the mapping and tests the corrected information.

Desired outcome

The systems return to a consistent, documented reference-data state. The resolution is based on the applicable rules rather than on whichever application happens to contain the newest value.

IMPLEMENTATION ROADMAP

Start with control. Then automate distribution.

An effective implementation does not require an enterprise-wide platform from day one. A limited, well-governed reference domain can provide a practical starting point.

PHASE 01

Inventory

Identify reference datasets, existing copies, system owners and current update procedures.

PHASE 02

Govern

Establish source ownership, validity controls, approval responsibilities and exception handling.

PHASE 03

Integrate

Implement supported imports, mappings and version-controlled distribution for selected systems.

PHASE 04

Monitor

Track failed validations, missed updates, version differences and recurring data-quality problems.

Reference-data integration is a control process, not simply a data transfer. Reliable customs systems need appropriate sources, consistent versions, contextual validation and accountable exception handling.

05 / QUESTIONS, REGULATIONS & NEXT STEPS

Better reference data.
More reliable decisions.

Customs reference data connects legal requirements, official datasets and operational systems. Understanding its sources, validity and limitations helps organisations reduce avoidable errors and maintain more consistent customs processes.

FREQUENTLY ASKED QUESTIONS

Common questions about customs reference data.

Practical answers to the questions that arise when businesses manage customs codes, integrate reference datasets or introduce automated validation.

01 What is customs reference data?

Customs reference data consists of structured values, codes and classifications used to support customs processes. Examples include goods nomenclature codes, customs procedure codes, document codes and geographical references.

These values help applications represent information consistently, but their legal meaning and permitted use depend on the applicable rules and context.

02 What is the difference between TARIC and the Combined Nomenclature?

The Combined Nomenclature provides the eight-digit EU goods classification structure. TARIC builds on that structure with further subdivisions and integrates relevant EU tariff and trade-policy measures.

A goods code alone does not necessarily establish every applicable duty, restriction or documentary requirement. The relevant measures and transaction conditions must also be considered.

03 Are all customs reference codes valid throughout the European Union?

No. Many reference values are defined within EU-wide frameworks, but their applicability may depend on the customs procedure, declaration type, territory, date or electronic system.

Member State customs systems may also use supplementary national values or technical specifications. These must not automatically be treated as universally applicable EU codes.

04 How often does EU customs reference data change?

There is no single update frequency for all customs reference datasets. The Combined Nomenclature is updated annually, while TARIC measures and technical code lists may change on different schedules.

Businesses should monitor the relevant official sources and assess changes according to their effective dates and operational impact.

05 Can customs reference data be integrated automatically into an ERP?

Yes, where the necessary data and technical access are available. Integration may use approved file imports, supported service interfaces or internal distribution mechanisms.

The feasibility of each integration depends on the specific source, its access conditions, data format, update arrangements and the capabilities of the receiving system.

06 Does a technically valid code guarantee customs compliance?

No. Technical validation can establish that a code exists, follows a required format or satisfies a defined system rule.

It cannot, by itself, establish that the underlying tariff classification, origin determination, procedure selection or other substantive customs decision is correct. Those decisions require the appropriate facts, evidence and legal assessment.

07 Should historical customs records be updated when a code list changes?

Not automatically. A later reference-data update does not necessarily make an earlier declaration incorrect.

Historical records should retain sufficient information to identify the rules and references applicable to the original operation. Any amendment or correction must be assessed under the relevant customs provisions.

08 Does EU customs legislation require a dedicated reference-data management platform?

The Union Customs Code establishes legal obligations concerning customs information, declarations, supporting records and related procedures. It does not generally prescribe the particular internal software architecture illustrated on this page.

A central reference-data service is therefore a possible governance and technology choice, not a universally mandated EU customs software product.

EU LEGAL FRAMEWORK

Official sources behind customs reference data.

Customs reference values must be understood within their governing legal framework. The following official EU instruments provide essential starting points.

CORE CUSTOMS LEGISLATION

Union Customs Code

Regulation (EU) No 952/2013

Establishes the central EU customs legal framework, including obligations concerning customs information, declarations, records and customs procedures.

Read on EUR-Lex
SUPPLEMENTARY RULES

UCC Delegated Regulation

Regulation (EU) 2015/2446

Supplements the UCC with detailed provisions. Its Annex B framework is relevant to customs declaration data requirements, subject to applicable amendments and rules.

Read on EUR-Lex
IMPLEMENTATION RULES

UCC Implementing Regulation

Regulation (EU) 2015/2447

Provides implementing provisions, including relevant data formats and codes in the applicable Annex B framework.

Read on EUR-Lex
GOODS NOMENCLATURE

Combined Nomenclature Framework

Regulation (EEC) No 2658/87

Establishes the tariff and statistical nomenclature framework and the Common Customs Tariff. The CN is maintained through subsequent amending legislation.

Read on EUR-Lex

Use current legal texts. The links identify the underlying instruments. For operational decisions, consult their applicable consolidated versions, subsequent amendments and relevant implementing measures. A consolidated text is a documentation aid; the legally authoritative acts remain those published in the Official Journal.

CUSTOMS EXPLORER / DATA INTELLIGENCE

Better customs processes
begin with trusted data.

Explore the principles connecting official customs references, reliable business records and controlled digital operations.

Explore Customs Data

Customs Explorer provides general educational information. It does not replace the applicable legislation, official customs guidance or transaction-specific professional assessment.