Customs Data Explained.
Every digital customs process begins with data. From product descriptions and tariff codes to origin, value and shipment details, reliable information is the foundation of customs compliance.
Understand how commercial information becomes structured customs data, why data quality matters, and how different systems exchange and use information throughout international trade.
A customs system may accept a field’s format without establishing that its content is legally accurate. Data validation, regulatory assessment and customs acceptance are distinct processes.
The Information Behind Every Customs Declaration.
Customs declarations are built from multiple categories of information. Some originate in commercial documents, others come from logistics systems, product master data or assessments required by customs legislation.
The exact data requirements depend on the customs procedure, declaration type and applicable legal and technical specifications. Understanding the underlying information categories is the first step towards reliable digital customs processes.
Product & Classification Data
Information identifying the goods and their classification within the applicable customs tariff.
- Goods descriptions
- Commodity codes
- Quantities and units
- Net and gross mass, where required
Parties & Identification
Data identifying the businesses and other parties involved in the customs operation, according to their relevant roles.
- Importer and exporter information
- Declarant details
- Customs representative information
- EORI numbers, where applicable
Value & Transaction Data
Commercial and financial information relevant to determining customs value and other declaration amounts.
- Invoice amounts and currency
- Transaction information
- Delivery terms
- Relevant valuation adjustments
Country of Origin & Evidence
Information used to establish and support the origin of goods under the relevant preferential or non-preferential rules.
- Country of origin
- Applicable origin rules
- Supplier declarations, where relevant
- Supporting origin evidence
Transport & Shipment Data
Information connecting the goods to their movement, transport arrangements and accompanying documents.
- Transport references
- Packages and packaging details
- Transport modes, where required
- Relevant transport documents
Procedure & Regulatory Data
Information defining how goods are placed under a customs procedure and which requirements apply to the operation.
- Requested customs procedure
- Previous procedure, where relevant
- Supporting documents and references
- Authorisations, where required
Customs Data Is Not Just a Collection of Fields.
Individual data elements must be interpreted in context. A commodity code relates to specific goods. Origin information may affect the applicable tariff treatment. Customs value depends on the relevant transaction and valuation rules.
A reliable data model preserves these relationships rather than treating every field as an independent value copied from a document.
A shipment can contain several goods items, each potentially requiring its own classification, origin and valuation information.
Simplified illustration. Actual declaration structures and data requirements vary by procedure and system.
Commercial Data vs. Customs Data
Commercial records provide essential inputs, but they do not necessarily contain every element needed for a legally correct customs declaration.
Commercial Information
Information created to document business transactions and support operational activities.
Customs Information
Information prepared and assessed according to the requirements of the applicable customs procedure and legislation.
How Customs Data Becomes Structured Information.
Electronic customs systems need information in defined structures. Data elements must have clear meanings, expected formats and relationships so that information can be processed consistently.
In the European Union, harmonised customs data requirements provide a common foundation for electronic declarations and notifications. Technical message specifications then determine how those requirements are implemented in particular systems.
The EU Customs Data Model.
The EU Customs Data Model (EUCDM) provides a harmonised representation of customs data requirements used across EU customs processes.
It helps organise data elements, their definitions and their relationships in the context of customs declarations and other relevant customs formalities.
Consistent descriptions of customs information requirements.
Organisation of data elements and their relevant relationships.
A framework connected to EU customs data requirements.
Three Layers of Electronic Customs Data.
A data requirement, an electronic message and a software interface are related concepts, but they are not interchangeable.
Data Elements
Define what information means and which data is required in a particular context.
Electronic Messages
Organise data into a technical structure that can be exchanged and validated by the relevant systems.
System Interfaces
Define how information is transmitted, authenticated, received and processed between software applications.
Standardisation Does Not Automatically Mean Interoperability.
Two applications may understand the same customs data concepts while still requiring different message formats, communication methods or access arrangements.
Data Standardisation
Establishes common definitions and structured information requirements.
System Interoperability
Requires compatible technical interfaces, exchange rules, access permissions and operational arrangements.
Practical implication: adopting a harmonised data model does not automatically provide access to customs authority systems or eliminate the need for national and system-specific technical specifications.
Explore how the European customs IT environment supports electronic customs formalities.
Good Customs Data Requires More Than Valid Fields.
Customs data quality is not simply a question of whether information is present. Data must also be accurate, consistent, relevant and supported by appropriate evidence.
Electronic systems can detect many technical inconsistencies. They cannot, by themselves, establish that every declared fact or legal assessment is correct.
What Makes Customs Data Reliable?
Accuracy
Information reflects the actual goods, transaction and customs circumstances.
Completeness
Required information is available for the relevant declaration or procedure.
Consistency
Related records and data elements do not contain unexplained contradictions.
Timeliness
Information and reference data are current for the relevant transaction and regulatory context.
Not Every Validation Answers the Same Question.
A robust customs data workflow separates technical checks from business consistency checks and substantive customs assessments.
Technical Validation
Checks whether data follows expected formats, structures and field constraints.
Is the data technically acceptable?Business Rule Validation
Checks relationships between fields, transaction records and defined operational rules.
Is the information internally consistent?Customs Compliance Assessment
Evaluates whether the relevant classification, origin, valuation and procedural requirements are met.
Is the customs treatment legally justified?Passing one stage does not establish that all subsequent requirements are satisfied.
What Happens When Data Does Not Match?
A reliable process should not silently overwrite, ignore or automatically approve unresolved discrepancies. Exceptions need a defined route to investigation and correction.
Detect
Identify missing, conflicting or unexpected information.
Classify
Determine the issue type, relevance and potential operational impact.
Resolve
Obtain corrected data, supporting evidence or an authorised decision.
Record
Preserve the resolution and relevant actions for traceability.
Example: an ERP record contains a commodity code that differs from the classification currently approved for the product. The discrepancy should trigger review rather than an automatic replacement based solely on the latest available value.
Reliable Data Needs Clear Ownership.
Data governance defines who maintains information, who can approve changes and how corrections are documented throughout the customs workflow.
Data Ownership
Assign responsibility for maintaining product, supplier, transaction and customs-related records.
Change Control
Review changes to classifications, mappings, reference data and validation rules before deployment.
Auditability
Retain relevant source records, decisions, modifications and supporting evidence.
Periodic Review
Reassess data quality and controls as products, business operations and regulatory requirements evolve.
From Commercial Records to Customs-Ready Information.
A commercial invoice may contain many of the details needed for a customs declaration. However, information must be interpreted, reconciled and supplemented before it can support a reliable customs process.
The following simplified example illustrates how commercial data, product master records and customs assessments come together during declaration preparation.
One Shipment. Multiple Data Sources.
Commercial Invoice
ERP Product Records
Transport Documents
What Happens Between Input and Output?
The process combines automated data handling with defined checks and customs-specific review.
Collect
Retrieve relevant information from commercial and operational records.
Match
Connect invoice lines with the corresponding product and shipment records.
Validate
Check formats, completeness and consistency across sources.
Assess
Review classification, origin, valuation and procedure requirements.
Prepare
Organise verified information for the applicable declaration workflow.
Not All Data Is Ready at the Same Time.
The following table illustrates why data extraction alone is not sufficient to complete a customs declaration.
| Data Element | Primary Source | Example Status | Required Action |
|---|---|---|---|
| Invoice amount | Commercial invoice | Available | Reconcile with invoice lines |
| Product description | Invoice + ERP | Check | Confirm goods identification |
| Commodity code | ERP classification record | Review | Verify classification and applicable tariff |
| Country of origin | Supplier / product records | Review | Determine origin and verify supporting evidence |
| Gross mass | Transport documents | Available | Reconcile shipment totals |
| Customs value | Invoice + additional records | Review | Assess valuation method and relevant adjustments |
| Customs procedure | Import instructions | Check | Confirm intended procedure and conditions |
Illustrative statuses only. Actual requirements depend on the customs procedure, transaction and applicable system specifications.
Data Availability Is Not Customs Readiness.
Having a value in an ERP field does not prove that it is correct for the current customs operation. A reliable workflow distinguishes retrieved data, verified data and information that still requires a customs assessment.
Customs Data Frequently Asked Questions.
Understanding customs data means understanding more than electronic formats. It also requires distinguishing data availability, technical validation, legal assessment and system connectivity.
01 What is customs data?
Customs data is the information used to support customs declarations, notifications, procedures and related compliance activities.
It can include goods descriptions, commodity codes, values, origin, quantities, parties, transport details, supporting documents and procedure-specific information.
The required data depends on the relevant customs formalities and applicable rules.
02 What is the EU Customs Data Model (EUCDM)?
The EU Customs Data Model is a harmonised representation of customs data requirements used within the European Union.
It helps organise data elements, definitions and relationships relevant to customs declarations and other formalities.
The EUCDM should not be confused with a universal communication interface. Actual electronic exchanges depend on the technical specifications of the relevant customs systems.
03 Can customs declarations be generated directly from commercial invoices?
Invoice data can support automated declaration preparation, but commercial invoices do not necessarily contain all the information required for a customs declaration.
Additional information or assessment may be needed for tariff classification, customs value, origin, procedure codes, authorisations and supporting documents.
An automatically generated declaration draft should therefore be subject to appropriate validation and review before submission.
04 Does passing electronic validation mean a declaration is legally correct?
No. Electronic validation can establish that a message satisfies certain technical formats, field requirements and business rules.
It does not necessarily establish that the goods have been classified correctly, that origin has been properly determined or that customs value has been calculated in accordance with the applicable rules.
Technical acceptance and substantive customs compliance are different matters.
05 Can ERP systems exchange data directly with customs authorities?
Direct integration may be possible in particular technical and regulatory contexts, but it is not guaranteed by the presence of customs-related fields in an ERP.
Actual connectivity depends on the relevant customs system, available interfaces, technical requirements, authentication, access arrangements and applicable authorisations.
These dependencies should be verified before developing a customs integration.
06 Why is customs data governance important?
Customs data governance establishes responsibilities for maintaining, reviewing and updating information.
It supports traceability, change control, evidence management and consistent treatment of recurring transactions.
This becomes particularly important when incorrect master data or automated mappings could affect many declarations.
Five Principles to Remember.
Customs information comes from multiple operational sources.
Data standards and technical interfaces are not the same thing.
A valid electronic field does not prove legal correctness.
Exceptions and changes require defined review procedures.
Reliable automation begins with reliable data governance.
Better Customs Processes Start with Better Data.
Explore practical customs knowledge, digital transformation concepts and tools designed to make complex trade requirements easier to understand.