Customs Data
Mapping
Connecting enterprise information with the data requirements of EU customs processes.
ERP systems organise information around business operations. Customs systems require data structured according to specific procedures, definitions, codes and technical specifications. Customs data mapping establishes the controlled relationship between these two environments.
Enterprise Data
Commercial and operational information
Data Mapping Layer
Translate source information into the appropriate destination structure using documented mapping rules.
Customs Data Structure
Procedure-specific information requirements
The same information.
Different data structures.
Enterprise applications and customs systems are designed for different purposes. A business field may supply part of a customs data element, require transformation or need additional information before it can be used in a declaration. Source-to-target mapping defines these relationships explicitly.
Mapping connects meaning, not just field names.
A reliable mapping specification identifies the originating information, its intended customs use, the necessary transformations and the controls required before the destination value is accepted.
Identify the Source
Determine which system, document or responsible function provides the original business information.
Define the Meaning
Establish what the source value represents and whether it corresponds to the intended customs concept.
Apply Mapping Rules
Convert formats, combine information or enrich records where the destination requires it.
Validate the Output
Check the resulting value against the applicable customs data requirements, business facts and validation rules.
One transaction. Multiple data relationships.
Consider a purchase transaction recorded in an ERP. The commercial record contains useful information, but not every field can be transferred directly into a customs declaration.
Mapping does not create legal equivalence. Supplier country is not automatically origin, invoice amount is not automatically customs value, and an internal product identifier is not a tariff classification.
What a reliable mapping document should contain.
A documented specification allows developers, customs specialists and business owners to understand how each destination value is produced.
| Specification element | Purpose | Example |
|---|---|---|
| Source system | Identify the origin of the data. | ERP invoice module |
| Source field | Identify the exact business field. | invoice.currency |
| Business definition | Explain what the source value represents. | Currency used on the commercial invoice |
| Target element | Identify the relevant destination data concept. | Applicable invoice currency data element |
| Transformation | Document required formatting or conversion. | Map internal currency representation to the required code |
| Cardinality | Define the number of values or records permitted. | One invoice may contain multiple goods lines |
| Validation | Define technical and contextual checks. | Verify code validity and relevant field relationships |
| Missing-data rule | Specify what happens when the source is unavailable. | Raise an exception instead of inventing a value |
| Ownership | Identify who maintains or approves the rule. | Business data owner and customs process owner |
| Version | Track changes to the mapping specification. | Mapping version and effective date |
The examples above illustrate internal documentation practices. They are not official EU customs data element identifiers.
Not every field has a one-to-one relationship.
Customs mapping often requires combining, splitting or interpreting information from different sources.
One-to-One
A source value corresponds to a destination concept without substantive transformation.
Example: a verified currency code.One-to-Many
A source record supplies information used in multiple destination data elements.
Example: a structured party record.Many-to-One
Several source values are combined to establish a destination value.
Example: constructing a required address representation.Derived or Enriched
The destination requires a rule, assessment or additional information not directly present in the source.
Example: customs value assessment.Missing information must be handled explicitly.
A reliable integration distinguishes unavailable information from information that is genuinely not required for the operation.
Required and Available
The source contains the necessary information and the applicable checks can be performed.
VALIDATE & CONTINUERequired but Missing
The information is necessary for the relevant transaction but is not available.
REQUEST INFORMATIONConditionally Required
The data element is necessary only when specified conditions or procedures apply.
EVALUATE CONDITIONSNot Applicable
The element is not required for the relevant declaration context or procedure.
DOCUMENT THE RULENever substitute an arbitrary default for an unknown customs fact. A technically acceptable placeholder can create an inaccurate declaration. Where information is required, the process should obtain, verify or appropriately resolve it before submission.
Every mapping rule needs an owner.
Mapping quality depends on cooperation between business operations, customs expertise and technical implementation.
Source Data Accuracy
Confirms the meaning, origin and reliability of commercial or operational information.
Regulatory Interpretation
Determines the appropriate customs concepts, conditions and required assessments.
Mapping Implementation
Implements, tests and maintains the transformations and integration controls.
Understand the model.
Map the requirements.
EU customs data mapping requires more than matching ERP fields with similarly named customs fields. The applicable declaration dataset, data element definitions, conditions, code lists and electronic system specifications determine what information must be prepared and how it must be represented.
From legislation to a valid electronic message.
A customs data model helps organise information. It does not replace the underlying legal provisions or the technical rules of the system receiving the message.
Legal Requirements
The Union Customs Code and its supplementary provisions establish customs obligations, declaration requirements and the conditions applying to particular procedures.
EUCDM & Data Definitions
The EU Customs Data Model provides a structured representation of customs data requirements, including elements, relationships and relevant definitions used in EU customs processes.
System Specifications
Applicable electronic systems define the message structure, technical validation, communication mechanisms and processing requirements used in practice.
What the EU Customs Data Model contributes.
EUCDM supports a common understanding of customs information across different procedures and electronic environments. Its application must still be considered in the context of the relevant dataset.
Data Elements
Defined customs information concepts that can be associated with the applicable declaration or message.
Data Groups
Related information organised into logical structures, such as parties, goods or documents.
Datasets & Conditions
Requirements vary according to the relevant customs process, declaration type and applicable rules.
Formats & Code Lists
Information may require prescribed formats, identifiers, controlled codes or specific value structures.
There is no single universal customs dataset.
Before mapping fields, the implementation must identify the applicable customs operation and the corresponding data requirements. A field required in one context may be conditional or irrelevant in another.
Determine the customs context
These decisions establish the scope of the mapping exercise. They must not be inferred solely from the presence of fields in the ERP.
Required
The element must be supplied for the applicable context.
Conditional
The element is required when the relevant conditions apply.
Permitted or Optional
The element may be supplied where allowed and relevant.
Not Applicable
The element is not used in the particular data context.
R, C, P and N are explanatory labels used in this diagram, not a reproduction of official EUCDM status codes.
Code validity depends on context and time.
A value may be correctly formatted but inappropriate for the goods, procedure, date or customs system. Reliable mapping therefore requires more than checking whether a code exists.
| Code or identifier | Typical mapping issue | Required control |
|---|---|---|
| Country codes | Different country concepts may be stored in the ERP. | Identify the relevant country concept and accepted representation. |
| Commodity codes | Internal product categories do not establish tariff classification. | Verify the classification, code length, applicable date and intended use. |
| Procedure codes | Business transaction types do not automatically identify customs procedures. | Confirm the intended customs treatment and applicable conditions. |
| Document codes | An attached file does not necessarily correspond to a valid document reference. | Verify the required document type, reference and applicability. |
| Units of measurement | Commercial units may differ from required customs measurement units. | Check conversion logic, precision and the relevant data requirement. |
| Operator identifiers | Internal customer or supplier numbers are not official customs identifiers. | Verify the required identifier, relevant party role and validity. |
Technical acceptance confirms only the checks performed by the relevant system. The substantive correctness of a customs classification, procedure or other declaration detail requires assessment against the actual operation and applicable law.
EU harmonisation does not eliminate system differences.
The legal framework is shared, but the technical implementation of customs exchanges depends on the relevant EU or national electronic system.
Common Customs Requirements
Legal provisions and harmonised data definitions establish the common foundation for customs information.
- Relevant customs data concepts
- Applicable legal datasets
- Defined conditions and code requirements
- Union-wide customs rules
Technical Message Requirements
The receiving system may prescribe specific structures, interfaces, validation rules and exchange processes.
- Message structures and versions
- System-specific validation
- Communication and authentication
- Technical responses and error handling
Practical consequence: an EUCDM-based mapping can provide a common semantic foundation, but an operational integration still needs to conform to the exact requirements of its destination system.
Mapping rules must follow regulatory and technical changes.
Customs datasets, code lists and electronic system specifications can change. Integrations need a documented mechanism for assessing their impact.
Monitor
Identify relevant changes to legislation, datasets and system specifications.
Assess
Determine which mappings, controls and business processes are affected.
Update
Revise documented rules, reference values and technical transformations.
Test
Verify the revised mapping before deploying it to the relevant workflow.
Transform the data.
Preserve its meaning.
A technically successful transformation can still produce incorrect customs information. Reliable data mapping must preserve the underlying business facts, apply documented conversion rules and identify discrepancies before the resulting data enters a customs declaration workflow.
Six transformation types that require control.
Some transformations are purely technical. Others require additional information, business interpretation or customs expertise. The mapping specification must distinguish between them.
Format Conversion
Convert dates, decimal representations, character formats and other technical structures into the required format.
27/10/2026
→
2026-10-27
Code Translation
Translate internal ERP values into accepted codes using controlled and versioned mapping tables.
ERP: ITALY
→
IT
Unit Conversion
Convert measurements only when the source unit, conversion factor, required destination unit and rounding rules are established.
1,250 g
→
1.25 kg
Record Restructuring
Split, group or combine source records according to the target message structure without losing their underlying relationships.
ERP lines
→
Goods items
Data Enrichment
Add verified information from product master data, approved reference tables or other authoritative business sources.
Item ID
+
Verified classification
Customs Determination
Obtain a substantive determination where the destination value depends on customs rules rather than a simple technical conversion.
Invoice facts
→
Valuation assessment
Build controls around every transformation.
Validation should occur before and after transformation. This separates source-data defects from mapping errors and destination-rule failures.
Source Validation
Verify availability, source integrity and essential business relationships.
INPUT CONTROLSTransformation
Apply approved conversion, lookup and restructuring rules to the source values.
VERSIONED RULESOutput Validation
Check formats, permitted values, relationships and applicable target requirements.
OUTPUT CONTROLSRelease Gate
Authorise the mapped data to proceed only when required checks and approvals are satisfied.
CONTROLLED HANDOFFThe release gate is an internal workflow control. It is not equivalent to acceptance or release by a customs authority.
When the numbers match but the data is wrong.
Consider an illustrative import transaction in which the ERP, invoice and packing list contain apparently compatible values. Several checks are still needed.
Import shipment — three source records
Packaging conversion does not reconcile.
The invoice and ERP both indicate 2,400 pieces, but 200 cartons multiplied by the stored conversion factor of 10 pieces per carton produces only 2,000 pieces.
The records contain a discrepancy that cannot be resolved through arithmetic alone.
The actual packing configuration, the accuracy and applicability of the product-master conversion factor and the supporting documents.
Flag the discrepancy, assign it for review and use verified information before completing any dependent mapping.
This example illustrates an internal consistency check. It does not establish that the shipment is incorrectly declared; the underlying facts must first be verified.
What should a mapping engine verify?
Different controls answer different questions. A robust integration combines technical, business and customs-specific validation.
Completeness
Are all data elements required for the applicable context available or appropriately resolved?
Format & Type
Does each value conform to the expected structure, length, precision and format?
Reference Validity
Are codes and identifiers valid for the relevant system, context and date?
Cross-Field Consistency
Do quantities, weights, parties, procedures and related values remain coherent?
Document Reconciliation
Are mapped values supported by the relevant commercial, transport and customs evidence?
Rule Provenance
Can the organisation identify which source, mapping version and approval produced each value?
Not every mapping issue should stop the same workflow.
Internal severity categories help teams prioritise exceptions. Their meaning should be documented and aligned with the organisation’s approval and submission controls.
| Internal category | Illustrative condition | Workflow response |
|---|---|---|
| BLOCKING | A required value is absent, a mandatory transformation fails or a critical inconsistency remains unresolved. | Prevent the affected workflow from proceeding until the issue is resolved. |
| REVIEW REQUIRED | Source documents conflict or a customs determination requires qualified assessment. | Assign an owner, obtain supporting evidence and record an approval before proceeding. |
| ADVISORY | A non-critical data-quality observation is detected without preventing required checks. | Record the observation and address it under the applicable internal policy. |
These are illustrative internal workflow categories, not official classifications of customs authority errors.
Preserve the original source values, record the reason for the correction and retain the mapping version used to generate the revised output.
Five shortcuts that create unreliable customs data.
Most mapping failures are not caused by complicated algorithms. They arise when assumptions are treated as verified facts.
Supplier location and the origin of goods are different concepts.
Customs valuation depends on the applicable method and any relevant adjustments.
Classification records and applicable tariff codes require appropriate maintenance.
Technical completeness does not justify inventing an unknown customs fact.
Passing a software validation rule does not establish that the underlying declaration is accurate.
Connect the systems.
Control the information.
A customs mapping architecture must coordinate data from commercial, logistics and product systems while preserving traceability. The objective is not simply to transfer fields, but to create a controlled path from verified business information to customs-ready data.
How an ERP-to-customs integration can be organised.
The following model illustrates a possible architecture. Actual interfaces depend on the software products, customs procedures, access arrangements and technical specifications involved.
Orders, invoices, partners and commercial values
Descriptions, product attributes and approved classifications
Goods quantities, packaging and movement records
Invoices, certificates and supporting evidence
Customs Data Mapping Layer
A controlled integration layer interprets source information, applies approved mappings and prepares data for the appropriate customs application.
Declaration Preparation & Processing
The mapped information is transferred to the appropriate customs application or authorised integration channel, where further preparation, checks and processing may occur.
Architecture boundary: this diagram does not imply that an ERP, middleware product or Customs Explorer has direct access to customs authority APIs. Connectivity, authorisations and technical onboarding must be established separately.
Each system should have a clearly defined role.
Unclear ownership creates duplicate records, conflicting values and corrections that cannot be traced to their source.
Maintain Source Facts
Store and maintain the underlying commercial and operational information used in the customs process.
Examples: invoice, purchase order, shipment.Transform & Reconcile
Apply approved mappings, validate relationships and preserve the origin of derived information.
Examples: unit conversion, code mapping, exception log.Manage Customs Workflow
Support the preparation and processing of customs information according to the relevant procedure.
Examples: declaration draft, review, submission workflow.Provide Official Responses
Return the official messages and outcomes associated with customs processing.
Examples: acknowledgements, references, decisions.From a purchase transaction to customs-ready data.
This simplified example shows how an import transaction may draw information from multiple business records and require additional customs determinations.
Industrial components — third-country supplier
| Business source | Available information | Customs mapping requirement | Control |
|---|---|---|---|
| ERP invoice | Supplier, buyer, invoice number, currency and amount | Relevant parties, commercial references and valuation inputs | Verify roles, source documents and valuation basis |
| Product master | Three internal product identifiers and descriptions | Goods descriptions and applicable commodity classifications | Confirm product identity and classification validity |
| Purchase records | Supplier and procurement information | Potential inputs to origin and transaction assessment | Do not infer origin from supplier location |
| Warehouse records | 600 pieces, packaging and recorded weights | Goods quantities, packages and required mass data | Reconcile units, packaging and measurement sources |
| Transport documents | Shipment references and movement information | Relevant transport and routing particulars | Check consistency with the actual movement |
| Customs process records | Intended operation, authorisations and available evidence | Procedure, supporting references and applicable conditions | Confirm eligibility and required documentation |
€12,500 is the illustrative invoice amount, not automatically the customs value. The appropriate customs valuation method and any applicable adjustments must be assessed. Similarly, the three ERP product lines do not necessarily establish the final structure of customs goods items.
Six steps from business records to a controlled handoff.
The integration should create a repeatable process in which incomplete or inconsistent data is detected before it moves further downstream.
Identify the Transaction
Select the relevant business transaction and establish its unique internal reference.
Collect Source Records
Retrieve invoices, product information, logistics records and available supporting documents.
Apply Mapping Rules
Convert formats, resolve relationships and enrich data using verified information.
Validate & Resolve
Run required checks and route unresolved customs questions to the responsible owner.
Approve the Output
Record the relevant checks, decisions and internal authorisations.
Transfer & Reconcile
Pass the approved data to the designated application and reconcile subsequent identifiers and responses.
Never lose the link between the source and the declaration.
Integration design should preserve relationships between internal records, mapped data versions and official customs references when available.
Design principle: an internal job ID, declaration draft reference and official customs reference are not interchangeable. Store their relationships explicitly and retain the status and timing of each event.
Build for reliability before adding automation.
A successful pilot must demonstrate more than a working data transfer. It must handle duplicate messages, failures, revisions and changes to the underlying source records.
Duplicate Prevention
Avoid unintended duplicate processing when the same transaction or message is retried.
Mapping Version Control
Record which transformation rules and reference data were applied to each output.
Failure Handling
Distinguish temporary technical failures from substantive data-quality exceptions.
Response Correlation
Associate acknowledgements, errors and official references with the correct transaction.
Access & Data Protection
Limit access to authorised users and protect commercial and customs information in transit and at rest.
Human Review
Require appropriate approval for customs determinations that cannot safely be inferred from source data.
Make the mapping reliable.
Keep it under control.
Customs data mapping is not complete when the first electronic message is generated. A dependable implementation needs documented field definitions, verified business rules, exception management, controlled changes and evidence that the resulting information remains consistent with the underlying transaction.
Ten checks before putting a mapping into production.
Use these questions during design, testing and approval. The precise controls depend on the customs procedure, destination system and organisation’s responsibilities.
Define the customs operation
Identify the procedure, declaration or message type, applicable dataset and receiving system before selecting the fields to map.
Identify every data source
Document which ERP, product, warehouse, transport or document records supply each required information concept.
Assign responsibility for values
Establish who maintains source data, approves customs determinations, resolves exceptions and authorises changes to mapping rules.
Confirm the meaning of each field
Verify that a source value represents the same information concept as its destination field. Similar field names do not establish equivalence.
Document conversion rules
Define permitted code translations, unit conversions, calculations, rounding rules and data enrichment using verified information.
Test technical and business consistency
Check formats, mandatory values, code validity, quantities, document relationships and relevant customs-specific conditions.
Define how failures are resolved
Prevent unresolved critical issues from being silently converted into default values. Establish review, correction and escalation procedures.
Preserve source-to-output relationships
Connect source records, mapping jobs, output versions and relevant customs references without confusing internal and official identifiers.
Test retries and corrections
Verify that interrupted processing, duplicate requests, changed source records and rejected messages do not produce uncontrolled outcomes.
Plan ongoing maintenance
Assign responsibility for monitoring changes to legislation, customs datasets, reference values and technical specifications after deployment.
This is an implementation checklist, not an exhaustive statement of legal requirements or a substitute for procedure-specific customs guidance.
What should be demonstrated before deployment?
A working demonstration is not sufficient evidence of reliability. Testing should cover normal operations, exceptional conditions and the integrity of the information produced.
Correct Mapping
Representative transactions produce outputs consistent with approved field definitions and transformation rules.
Controlled Exceptions
Missing, conflicting or invalid information is identified and handled through the appropriate review process.
Recoverable Processing
Interrupted workflows and retries can be reconciled without unintended duplication or loss of processing history.
Documented Approval
Relevant business and customs owners have reviewed the applicable mapping, controls and remaining limitations.
Important distinction: internal go-live approval does not establish that a customs authority will accept a declaration, nor does technical acceptance prove the substantive correctness of its data.
Keep mappings accurate after the first release.
Changes in business processes, product information, customs requirements or system interfaces can make previously valid mappings unreliable.
Detect Change
Identify a revised dataset, code list, business process or technical specification.
Assess Impact
Determine affected fields, transactions, controls and integrations.
Update & Test
Revise the mapping and run regression tests against relevant scenarios.
Release & Monitor
Deploy the approved version and monitor exceptions, responses and reconciliation.
Customs data mapping — essential questions.
These answers explain the boundaries between data mapping, customs interpretation and electronic declaration processing.
01 What is customs data mapping?
Customs data mapping is the process of relating information from business systems to the data elements required by a customs process or electronic message. It includes identifying source fields, defining their meaning, applying permitted transformations and validating the resulting information.
02 Can ERP data be transferred directly into a customs declaration?
Some ERP values may be suitable for direct transfer after validation. Others require conversion, enrichment or customs-specific assessment. For example, an invoice amount is a relevant valuation input but does not automatically establish the customs value. Direct transmission also depends on the available software interfaces and authorised communication arrangements.
03 Does EUCDM provide a ready-to-use API for every customs system?
No. The EU Customs Data Model describes and organises customs data requirements. It is not itself a universal operational API. Actual connectivity requires the applicable system specifications, technical interfaces, access arrangements and any necessary authorisations.
04 What is the difference between mapping and validation?
Mapping defines how information moves from a source concept to a destination concept. Validation checks whether the source information, transformation and output satisfy the relevant rules. Both are necessary: a correctly executed mapping can still transfer incorrect business information.
05 Can software determine commodity codes, origin and customs value automatically?
Software can retrieve approved determinations, apply defined rules and flag inconsistencies. However, commodity classification, origin and customs valuation depend on the facts and applicable legal provisions. Automation must not treat incomplete source information or unsupported assumptions as verified customs determinations.
06 How should mapping errors be handled?
Errors should be classified according to their effect on the relevant workflow, assigned to a responsible owner and resolved using verified information. The system should preserve the original data, the correction history and the mapping version used for the revised output. Technical failures should be distinguished from substantive customs-data issues.
07 When should customs mapping rules be reviewed?
Review rules whenever relevant legal requirements, customs datasets, code lists, electronic system specifications or business source structures change. Periodic review and monitoring of production exceptions are also useful controls. The review frequency should reflect the risks and change rate of the implementation.
Start with the legal and technical source.
Always consult the applicable consolidated legal texts and current technical documentation for the relevant customs system.
Union Customs Code
Regulation (EU) No 952/2013. Legal framework for customs procedures, information and declarations.
View on EUR-Lex DELEGATED REGULATIONUCC Delegated Act
Regulation (EU) 2015/2446, including the applicable declaration data requirements and Annex B provisions.
View on EUR-Lex IMPLEMENTING REGULATIONUCC Implementing Act
Regulation (EU) 2015/2447. Implementing provisions relevant to customs processes and information requirements.
View on EUR-Lex EUROPEAN COMMISSIONDG TAXUD
European Commission customs information, electronic systems, data-model resources and implementation guidance.
Explore official resourcesReferences are provided for orientation. The applicable legal provisions, amendments, system versions and national implementation arrangements must be verified for the particular customs operation.
A successful mapping does not simply move data. It preserves trust in the information.
The most reliable customs integrations combine clear data definitions, controlled transformations, substantive validation, documented responsibilities and traceability across the entire transaction lifecycle.
Back to Customs Data Explained