Customs
Transaction Data
The information that describes an individual customs operation — connecting goods, economic operators, declarations, documents and regulatory decisions into a traceable transaction record.
Customs transaction data is created, received and updated as goods move through customs processes. It combines operational facts with information drawn from business master records and applicable reference datasets, supporting declarations, validation, customs controls and subsequent audit trails.
One customs operation may generate multiple messages, decisions and status changes. A reliable data model preserves their relationships rather than treating each message as an isolated record.
A specific movement, declaration or customs procedure event
Goods, parties, quantities and values.
Declarations, validation and controls.
Messages, decisions and traceability.
Every customs operation
has a data structure.
A customs transaction is more than a declaration number or a shipment record. It brings together information about the goods, the parties, the commercial operation and the applicable customs procedure, together with supporting evidence and processing events.
Eight connected dimensions of a customs transaction.
The domains below are a conceptual grouping for understanding customs data. They are not a substitute for the legally applicable declaration data elements or the specifications of an individual customs system.
Economic Operators & Roles
Identifies the participants involved in the operation and the roles they perform under the relevant customs procedure.
Goods & Classification
Describes the goods covered by the transaction, including their identity, classification and relevant product characteristics.
Values & Commercial Terms
Captures relevant transaction values and commercial information used to determine or support customs valuation.
Quantities, Weights & Packaging
Records the physical quantities and measurements relevant to the goods, transport operation and applicable tariff rules.
Origin & Geographical Context
Connects the operation to the relevant countries and territories, including origin and movement information.
Customs Procedure & Routing
Defines the requested customs treatment and the operational context in which the declaration is processed.
Documents & Authorisations
Links the transaction to supporting commercial documents, certificates, licences and relevant customs authorisations.
Identifiers, Status & Events
Records identifiers and events generated during processing, including customs responses and relevant decisions.
Not every field has the same origin.
Some values are reused from existing business records. Others come from official code lists, are specific to the operation or are generated later by customs processing.
Master Data
Provides maintained information about products, business partners and other recurring business entities.
Operator identification
Maintained product attributes
Reference Data
Supplies applicable classifications, codes and permitted values used to structure transaction information.
Customs procedure codes
Document code lists
Transaction Data
Describes the actual operation, using applicable reusable information alongside transaction-specific details.
Declared customs procedure
Shipment and declaration references
Important distinction: a value stored in a product master is not automatically correct for every future transaction. Classification, origin, valuation and other customs information must remain appropriate to the actual goods, facts and applicable rules.
One import operation. Multiple data domains.
An EU company purchases industrial components from a supplier outside the European Union. The goods are presented for import and a declaration for release for free circulation is prepared.
The commercial invoice, product details, customs declaration and subsequent customs messages should be traceable to the same operation, even when they originate in different systems.
Consistency must be checked across domains.
Individual values can appear technically valid while the overall transaction remains incomplete or inconsistent. Cross-domain checks help identify discrepancies before submission.
| Relationship | Example control | Potential issue |
|---|---|---|
| Goods + Classification | Compare product characteristics with the declared classification. | A code is copied from a different product. |
| Goods + Quantities | Check required measurements and consistency with supporting records. | Net mass differs from the available shipment evidence. |
| Value + Commercial Terms | Review invoice details and relevant valuation adjustments. | Invoice value is treated automatically as customs value. |
| Origin + Preference | Check whether the preference claim is supported by applicable rules and evidence. | Preferential treatment is claimed without sufficient support. |
| Procedure + Authorisation | Verify whether the selected procedure requires an applicable authorisation. | A procedure is requested without satisfying its conditions. |
| Documents + Declaration | Compare supporting references with the declared information. | Document references are missing or inconsistent. |
| Status + Processing | Reconcile declaration events with the operational workflow. | Goods are treated internally as released before release is confirmed. |
These are illustrative internal controls, not a universal list of mandatory validation rules. Applicable requirements depend on the declaration, procedure and customs system.
A customs transaction
is a sequence of events.
Customs transaction data evolves throughout an operation. Information is collected, verified, submitted, processed and retained alongside the messages and decisions generated during the customs procedure. Understanding this lifecycle is essential for reliable digital customs operations.
Seven stages of transaction data management.
This model illustrates a common declaration-oriented workflow. Actual stages, messages and legal effects vary by customs procedure, electronic system and applicable requirements.
Collect the Transaction Facts
Information is gathered from commercial, logistics and business systems. The transaction record begins to connect the goods, parties, invoice, shipment and supporting documentation.
Build the Customs Data Record
Transaction-specific facts are combined with appropriate master data and applicable reference values. The information is structured for the intended customs procedure and declaration type.
Validate Before Transmission
Internal controls assess completeness, formatting and consistency. Substantive customs checks may also require reviewing classification, valuation, origin, authorisations and supporting evidence.
Transmit and Record the Response
The declaration or relevant customs message is transmitted through the applicable channel. The receiving system may issue technical responses, validation results or other procedure-specific messages.
Track Acceptance, Controls and Decisions
Depending on the procedure and system, customs processing may generate acceptance information, control notifications, requests, decisions or other status events.
Record Release or Another Applicable Outcome
The transaction record is updated with the relevant official outcome. For a declaration involving release of goods, the business must distinguish a confirmed customs release from an internal assumption that processing has finished.
Retain, Reconcile and Support Later Review
Transaction information, supporting evidence and relevant messages are retained according to applicable obligations. Later corrections, reviews and customs procedures may create additional records linked to the original operation.
One operation. Different kinds of status.
Internal software states and official customs events serve different purposes. Treating them as interchangeable can create operational errors and unreliable reporting.
Business Processing Status
Indicates progress inside the company’s ERP, forwarding platform or customs preparation software.
Message Processing Status
Indicates whether a message was sent, received or processed by a technical interface, according to the relevant system specification.
Customs Procedure Status
Represents an event or decision communicated through the applicable customs system, with its procedure-specific legal meaning.
Critical operational distinction: a declaration marked as “sent” by an internal application is not necessarily accepted by customs. Likewise, an accepted declaration does not automatically mean the goods have been released. Systems should record and display these states separately.
Preserve what happened — and when.
A reliable transaction history records meaningful changes and links them to the corresponding messages, sources and operational decisions.
Import declaration — sample timeline
Commercial and shipment information imported into the preparation system.
Configured data checks passed; transaction approved for submission.
Outbound message and technical transmission reference recorded.
Acceptance information and the applicable official identifier recorded.
Official release event linked to the transaction record.
The timestamps, events and sequence above are illustrative, not actual customs messages or guaranteed processing times. Real event names and message structures depend on the system.
A transaction record should not erase its own history.
Corrections may be necessary before submission or through legally permitted procedures afterwards. Their handling depends on the stage of processing and the applicable customs rules.
Internal Data Correction
Incomplete or inconsistent information is corrected within the preparation workflow.
- Record the changed fields where appropriate.
- Identify the source of the corrected information.
- Repeat relevant validation checks.
Customs Declaration Amendment
An amendment to an accepted declaration is subject to the applicable legal conditions, restrictions and customs procedures.
- Assess whether amendment is legally available.
- Preserve the original submitted information.
- Link the request and resulting customs decision.
Post-Processing Review
Later checks may identify differences requiring a review of the transaction or further action under customs law.
- Retain the original declaration and evidence.
- Document the identified discrepancy.
- Record any subsequent formal action or decision.
Important: editing an internal database does not, by itself, amend a customs declaration already accepted by the customs authorities. The legally applicable amendment, invalidation or other correction process must be followed.
Valid data is not always
correct customs data.
A customs declaration may satisfy technical formatting requirements while containing incorrect commercial facts, inconsistent supporting documents or an inappropriate customs treatment. Reliable transaction processing requires several distinct layers of validation.
From field formatting to regulatory accuracy.
Effective validation combines automated controls with appropriate human review. The objective is to detect problems before submission and maintain data integrity throughout the customs process.
Technical Validation
Confirms that the transaction data follows the required technical structure and interface specifications.
- Required fields are populated.
- Data types and lengths are valid.
- Message structures are supported.
- Mandatory technical relationships are satisfied.
Reference & Code Validation
Checks whether controlled values are recognised and applicable within the relevant customs context.
- Country and territory codes.
- Procedure and document codes.
- Applicable commodity classifications.
- Validity periods and code dependencies.
Cross-Document Consistency
Compares declaration information with commercial, logistics and other supporting records.
- Invoice and declared goods.
- Quantities and transport records.
- Parties and transaction roles.
- Document references and declared details.
Customs Compliance Review
Evaluates whether the declared information and requested treatment are supported by the applicable customs rules and facts.
- Tariff classification assessment.
- Customs valuation requirements.
- Origin and preference conditions.
- Procedure and authorisation requirements.
A successful technical validation does not establish customs compliance. A system can accept a correctly formatted commodity code without independently confirming that it is the correct classification for the goods. The declarant remains subject to the applicable obligations concerning the accuracy and completeness of the information supplied.
Where data inconsistencies commonly appear.
A practical control framework compares transaction fields with their sources, related data elements and applicable business or regulatory rules.
| Data area | Validation objective | Example discrepancy | Suggested response |
|---|---|---|---|
| Operator identity | Confirm the relevant party, role and identification. | Incorrect declarant or outdated operator details. | Verify the source and the actual transaction roles. |
| Goods description | Ensure sufficient and accurate identification of goods. | Generic description inconsistent with the actual product. | Review technical and commercial product information. |
| Classification | Check the declared code against product characteristics and applicable nomenclature. | Previously used code applied to a different product. | Reassess classification and retain supporting reasoning. |
| Customs value | Check the valuation method and relevant adjustments. | Invoice amount automatically treated as customs value. | Review the transaction facts and applicable valuation rules. |
| Origin | Verify origin information and any preference claim. | Supplier country confused with country of origin. | Assess applicable origin rules and supporting evidence. |
| Quantities | Reconcile weights, units and packaging information. | Declared net mass differs from verified goods data. | Identify the authoritative measurement and correct the record. |
| Procedure | Verify the requested treatment and applicable conditions. | Procedure selected without the necessary authorisation. | Review eligibility, authorisation and procedure requirements. |
| Supporting documents | Check references, document types and relevant evidence. | Missing or inconsistent certificate reference. | Obtain or verify the document and assess the declaration impact. |
Illustrative internal control examples. They are not a complete set of EU customs validation rules.
When all the fields are valid — but the declaration is wrong.
An importer prepares a declaration using product information stored in its ERP. The message passes the software’s structural checks. However, the product master contains an outdated commodity classification that does not reflect the goods being imported.
The system retrieves a previously maintained commodity code for the product.
The code is recognised by the configured validation rules and fits the required format.
The actual goods differ from those covered by the classification stored in the ERP.
The appropriate classification is determined using the applicable nomenclature and relevant product information.
The declaration preparation record is corrected, while the master data issue is separately addressed to reduce recurrence.
Validation must assess whether a value is correct for the actual transaction, not merely whether it is present, correctly formatted or included in a recognised code list.
Errors need ownership, evidence and resolution.
Identifying a discrepancy is only the beginning. Reliable workflows define how exceptions are classified, assigned, corrected and documented.
Identify the Exception
Record the failed control, affected fields and relevant transaction reference.
Assess the Impact
Determine whether the issue is technical, operational or potentially relevant to customs compliance.
Establish Responsibility
Direct the issue to the person or function capable of verifying the underlying facts.
Correct and Revalidate
Apply an evidence-based correction and repeat the controls affected by the change.
Preserve the Decision Trail
Record what changed, why it changed, the supporting information and any relevant approval.
Address the Root Cause
Review whether the discrepancy originates in recurring business data, mappings or process controls.
Protect the record throughout its lifecycle.
Transaction integrity requires traceability between original source information, submitted declarations, official responses and subsequent changes.
Source Traceability
Link significant transaction values to their originating documents, systems or verified information.
Version History
Preserve relevant versions of the data, especially where changes affect submitted information.
Access & Responsibility
Define who may prepare, review, approve or modify transaction information.
Official Message Preservation
Retain relevant customs responses and their identifiers without replacing them with internal labels.
Connect the systems.
Preserve the meaning.
Customs transaction data frequently originates outside the customs declaration system. ERP platforms, warehouse applications, transport systems and document repositories each hold part of the operational record. Integration brings these sources together while preserving their meaning, ownership and traceability.
From business systems to customs processing.
The architecture below is conceptual. Actual implementations depend on the customs procedure, national systems, available interfaces and the responsibilities of the parties involved.
ERP System
Orders, invoices, products, partners and commercial values.
Warehouse System
Goods, quantities, packaging and inventory movements.
Transport System
Shipment references, transport information and movements.
Document Repository
Invoices, certificates, authorisations and supporting records.
Customs Transaction Data Preparation
Collects, maps, validates and reconciles information from different business sources before preparing the transaction for the applicable customs workflow.
Declaration Preparation & Submission
Creates and manages declarations or other customs messages through the applicable software and authorised channels.
Customs Authority Systems
Process relevant submissions and generate official messages, decisions and status events according to the applicable procedure.
Official responses and relevant identifiers should be correlated with the originating transaction and communicated to the business systems that need them.
This diagram does not imply that Customs Explorer, an ERP or an integration layer has direct access to customs authority systems. Such access depends on the relevant technical, operational and legal arrangements.
One business field can have several customs implications.
Integration is not simply copying values between databases. Source fields must be interpreted against the applicable customs data requirements and the facts of the operation.
| Business source | Typical source information | Customs data use | Required consideration |
|---|---|---|---|
| Product master | Product code, description and technical attributes | Goods identification and classification support | Classification must reflect the actual goods and applicable nomenclature. |
| Business partner record | Name, address, identification details | Relevant transaction parties and roles | Business relationship does not automatically establish customs role. |
| Sales or purchase invoice | Amounts, currency, quantities, commercial terms | Commercial and valuation-related information | Customs value may require a specific method and adjustments. |
| Warehouse record | Units, weight, packages, goods movements | Physical transaction information | Units and quantities must correspond to the applicable data elements. |
| Transport record | Shipment references, route, transport details | Transport and movement information | Required details depend on the procedure and declaration context. |
| Document repository | Invoices, certificates, licences and references | Supporting documents and authorisation information | Document existence does not establish its legal applicability or validity. |
Illustrative mapping examples, not official EU customs data element specifications.
Automate repetition. Control decisions.
Automation is most useful when the source information is reliable and the relevant rules are sufficiently defined. Uncertain legal assessments and unresolved exceptions should not be silently converted into automated declarations.
Source Data Collection
Retrieve relevant transaction information from structured business records without repeated manual entry.
Data Mapping & Normalisation
Convert source formats and units into the structures required by the destination workflow.
Automated Quality Checks
Detect missing fields, invalid codes, inconsistent values and predefined cross-document discrepancies.
Exception Routing
Direct unresolved issues to the responsible person or team before further processing.
Message & Status Synchronisation
Associate technical and official responses with the relevant business transaction.
Evidence & Audit Trail
Link source documents, submitted data, responses and relevant subsequent changes.
Build reliable flows, not fragile shortcuts.
The quality of a customs integration depends on the handling of changes, failures, duplicate messages and differences between source systems.
Stable Transaction Identifiers
Use reliable internal identifiers to correlate business records, customs submissions and later responses. Official identifiers must be recorded when generated and applicable.
Duplicate Processing Protection
Design retries and message handling to reduce unintended duplicate transactions, while respecting the behaviour of the receiving system.
Versioned Mappings
Track mapping changes and the applicable code or specification versions used for each transaction.
Explicit Error Handling
Distinguish source errors, transformation failures, technical rejections and official customs responses.
Human Review Where Necessary
Route uncertain classifications, valuation questions, origin assessments and other substantive issues to qualified reviewers.
Secure Access & Data Protection
Apply appropriate authentication, authorisation, logging and protection to commercial and customs-related information.
Automating an import declaration preparation workflow.
An EU importer receives several shipments each week. Instead of manually re-entering the same information into its customs preparation application, it implements a controlled integration between its business systems and customs software.
ERP Export
Relevant order, invoice and product information is retrieved from the ERP.
Data Enrichment
Shipment details and required supporting information are associated with the transaction.
Validation
Configured controls identify missing fields, discrepancies and information requiring review.
Authorised Submission
Once ready, the declaration is submitted through the applicable authorised workflow.
Response Correlation
Relevant technical and official messages are linked to the original business transaction.
Record Reconciliation
The business workflow is updated according to the confirmed customs processing outcome.
Less repetitive data entry, more consistent validation and improved traceability. These benefits depend on reliable source information, suitable interfaces and appropriate process controls.
Automation can scale errors as easily as efficiency.
Poor source data and uncontrolled transformations may produce repeated errors across large numbers of transactions.
Incorrect Master Data
An outdated classification or operator record is copied into multiple declarations.
Control: source governance and transaction checks.Incorrect Field Transformation
A business value is mapped to an inappropriate customs data element.
Control: documented mapping and testing.Lost or Misinterpreted Responses
The internal system does not correctly reconcile a customs message with its transaction.
Control: identifiers, monitoring and reconciliation.Unreviewed Regulatory Decisions
Software automatically applies a customs treatment without sufficient supporting facts.
Control: explicit rules and appropriate review.Reliable transaction data starts with controlled processes.
Transaction data connects commercial operations, customs declarations, official responses and supporting evidence. Use this practical framework to identify gaps in data preparation, validation, integration and record management.
A practical transaction data checklist.
These controls can support an internal review of customs transaction data processes. They are illustrative operational recommendations, not an official certification.
Establish reliable information sources
- Identify the system or document supplying each critical data element.
- Confirm that product and operator records are maintained.
- Define how discrepancies between source records are resolved.
- Ensure the information reflects the actual customs operation.
Build a complete transaction record
- Connect commercial, logistics and customs-related information.
- Use applicable reference data and procedure-specific requirements.
- Check that quantities, values, parties and documents are consistent.
- Identify information requiring professional or legal assessment.
Separate technical checks from compliance review
- Validate required fields, formats and applicable codes.
- Compare declaration data with supporting information.
- Review classification, origin, valuation and procedure where relevant.
- Resolve significant exceptions before submission.
Track submissions and official responses
- Preserve the submitted data and relevant transmission details.
- Record official identifiers when issued.
- Distinguish technical delivery, acceptance and release.
- Associate customs responses with the correct transaction.
Control automated data exchanges
- Document ERP-to-customs field mappings.
- Monitor rejected, delayed and duplicate messages.
- Maintain a process for human review of unresolved issues.
- Test changes to interfaces, code lists and mapping rules.
Preserve evidence and transaction history
- Retain relevant supporting documents and customs messages.
- Record significant corrections and subsequent decisions.
- Apply appropriate access and retention controls.
- Ensure the original transaction history remains traceable.
Three stages of transaction data management.
Organisations can improve transaction data reliability progressively, without assuming that every operation requires a fully automated customs platform.
Document-driven processing
Information is gathered and entered manually, with controls dependent on individual procedures and operator experience.
Structured data exchange
Business systems supply transaction information through repeatable mappings, with defined validation and exception handling.
Integrated customs workflows
Suitable transactions move through controlled automated processes, while exceptions and substantive decisions receive appropriate review.
Transaction data — common questions.
Practical answers to recurring questions about customs transaction records, ERP integration and data reliability.
What is customs transaction data?
Is transaction data the same as master data?
Can ERP information be transferred directly into a customs declaration?
Does successful electronic validation mean a declaration is legally correct?
What is the difference between transmission, acceptance and release?
Can an accepted customs declaration be corrected by changing the ERP record?
How long should customs transaction records be retained?
Does customs automation eliminate the need for human review?
Legal foundations and official references.
Transaction data requirements must be interpreted through the applicable customs legislation, procedure and technical specifications.
Union Customs Code
Core provisions on information exchanges, declarations, customs processing and record-related obligations.
View legislation COMMISSION DELEGATED REGULATION (EU) 2015/2446UCC Delegated Regulation
Supplementary rules relevant to customs procedures and the information required in particular contexts.
View legislation COMMISSION IMPLEMENTING REGULATION (EU) 2015/2447UCC Implementing Regulation
Implementing provisions governing aspects of customs procedures, information exchanges and processing.
View legislationConsult the consolidated legislation and relevant amendments for the rules applicable at the time of the operation. Technical requirements may also depend on the specific EU or national customs electronic system.