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.
Determine which official or applicable dataset governs a particular data element.
Confirm that the value is valid for the relevant context, date and customs procedure.
Monitor updates and prevent outdated values from being reused without appropriate checks.
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.
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.
Country & Territory Codes
Structured geographical identifiers used in customs information, including country or territory references relevant to origin, destination and other declaration data.
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.
Customs Procedure Codes
Coded values identifying customs procedures and relevant procedure combinations within applicable customs declaration data requirements.
Document & Certificate Codes
Reference values used to identify supporting documents, certificates, authorisations and other document-related information in customs declarations and connected systems.
Units & Measurement Codes
Controlled values representing quantities, units and supplementary measurement information where required for customs and tariff purposes.
Regulatory & Status Codes
Additional controlled values used in specific customs processes, including relevant declaration indicators, status values and regulatory classifications where applicable.
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.
Reference Data
Defines recognised codes, values and classifications used to structure information.
Master Data
Describes an enterprise entity, such as a product or business partner, using maintained attributes and assessments.
Transaction Data
Describes the specific goods movement, declaration or operation being performed.
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.
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. |
One product. Several layers of reference data.
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.
Industrial component
Description, composition, technical specifications and supporting documentation.
Applicable coded values
Goods nomenclature, country references, procedure values and document codes, as relevant to the operation.
Specific import
Actual quantity, customs value, parties, movement and requested customs procedure.
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 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.
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.
TARIC
Integrated Tariff of the European Union
TARIC integrates EU tariff measures and relevant trade-policy measures associated with goods codes, including duties, suspensions, quotas and certain restrictions or document requirements where applicable.
TARIC is an operational tariff reference system. Its content must be interpreted with the relevant legal acts and the circumstances of the transaction. National measures, including VAT and excise, may require separate national sources.
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.
The CN and TARIC are related but not identical. CN provides eight-digit subdivisions, while TARIC introduces further subdivisions and integrates applicable EU measures.
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.
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.
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.
Code lists can differ by system, message specification and version. A value accepted by one interface is not necessarily accepted by another.
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.
Country identifiers must not be confused with the legal concepts of customs territory, origin, destination or preferential eligibility.
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.
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.
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.
EU Regulations & Applicable Legal Acts
Establish the legal obligations, conditions and measures governing customs operations.
TARIC, CN & Applicable Code Lists
Organise and expose reference values used for classification, tariff measures and structured customs information.
Customs Systems & Enterprise Applications
Use applicable codes and validation rules within declarations, integrations and business processes.
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.
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.
Identify the data element
Determine whether the information concerns goods nomenclature, procedures, documents, geography or another coded field.
Determine the applicable context
Establish the customs procedure, declaration type, Member State, system and relevant date.
Select the authoritative reference
Use the relevant legal instrument, official dataset or applicable system specification.
Verify applicability
Check validity dates, territorial scope, conditions and relationships with other required data.
Record source and version
Preserve enough information to identify which reference dataset and rules supported the selected value.
Monitor subsequent changes
Reassess affected records and integrations when the relevant nomenclature, code list or system rules change.
One declaration, multiple reference sources.
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.
Establish the appropriate goods code and examine relevant tariff measures.
Identify applicable data elements, formats and coded values.
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.
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.
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.
Publication Date
When a legal act, dataset update or technical specification is published or made available.
Effective Date
The date from which the relevant value, measure or requirement becomes applicable under the governing rules.
System Activation Date
When an organisation activates a new reference version in its ERP, customs software or validation service.
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.
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.
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.
Baseline Reference Version
A controlled reference snapshot is approved for the relevant operational context.
HISTORICALUpdated Reference Version
A new version becomes applicable for the illustrated process. Earlier records retain their previous reference context.
ILLUSTRATIVE ACTIVE VERSIONPending Change Assessment
A proposed change is reviewed, mapped to affected records and tested before controlled activation.
PENDINGThe dates and versions above are fictional examples. They do not represent actual CN, TARIC or customs-system releases.
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.
Code Creation, Deletion or Restructuring
Changes to goods nomenclature may require reassessment of product classifications, mappings and affected master records.
Measure Introduction or Expiry
A tariff measure may change without changing the underlying goods code, affecting duties or applicable regulatory conditions.
Code-List Modification
A declaration value may be introduced, withdrawn or restricted to particular data elements or procedures.
Message Specification Changes
Customs systems may change message structures, validation rules or accepted code-list versions through controlled technical releases.
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.
Detect
Identify changes from relevant official legal publications, datasets or system specifications.
Assess
Determine effective dates, affected codes, business processes and dependent records.
Approve
Obtain the appropriate business, customs and technical approvals for the proposed response.
Deploy
Release the new reference version through controlled integration and activation procedures.
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.
When a tariff code changes between two operations.
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.
Earlier import
The earlier declaration was prepared using the reference values applicable to that operation, subject to the relevant legal rules.
Nomenclature amendment
The company reviews whether the amendment changes the appropriate classification, related measures or product master-data mapping.
Later import
The later operation is assessed using the applicable nomenclature and measures, with an updated, documented determination where necessary.
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.
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.
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.
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 Management
Source tracking, validity rules, version management and controlled distribution.
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.
Batch Synchronisation
Import approved reference files or snapshots at planned intervals, followed by validation and controlled activation.
API-Based Retrieval
Retrieve reference information through an authorised and supported service interface where one is available.
Event-Driven Distribution
Notify connected enterprise systems after a reference-data change has been reviewed and approved internally.
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.
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.
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.
Detect
Identify an invalid, expired, missing or contextually inconsistent value.
Classify
Distinguish technical mapping errors from substantive customs questions.
Resolve
Correct the reference, update the mapping or obtain specialist review.
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.
When the ERP and customs software disagree.
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.
Outdated Mapping
The ERP sends a previously configured value without recognising the newer validation requirements.
Version Mismatch
The validation layer identifies the incompatibility and prevents automatic acceptance of the disputed value.
Controlled Resolution
The responsible team checks the applicable code list, updates the mapping and tests the corrected information.
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.
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.
Inventory
Identify reference datasets, existing copies, system owners and current update procedures.
Govern
Establish source ownership, validity controls, approval responsibilities and exception handling.
Integrate
Implement supported imports, mappings and version-controlled distribution for selected systems.
Monitor
Track failed validations, missed updates, version differences and recurring data-quality problems.
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.
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.
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.
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-LexUCC 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-LexUCC Implementing Regulation
Regulation (EU) 2015/2447
Provides implementing provisions, including relevant data formats and codes in the applicable Annex B framework.
Read on EUR-LexCombined 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-LexUse 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.
Better customs processes
begin with trusted data.
Explore the principles connecting official customs references, reliable business records and controlled digital operations.
Explore Customs Data