Customs Explorer
⌕

Customs Explorer

Transaction data

CUSTOMS DATA INTELLIGENCE TRANSACTION LAYER

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.

TRANSACTION DATA MODEL
CONCEPTUAL / 01
M
BUSINESS CONTEXT Master Data Products · Parties
R
CONTROLLED VALUES Reference Data Codes · Measures
TX OPERATIONAL RECORD
Customs Transaction

A specific movement, declaration or customs procedure event

GOODS Item details
PARTIES Operator roles
VALUES Amounts & quantities
PROCEDURE Customs context
01 Declarations Submitted data
02 Status Events Process changes
03 Audit Trail Evidence & history
01
Describe the operation

Goods, parties, quantities and values.

02
Support customs processing

Declarations, validation and controls.

03
Preserve the history

Messages, decisions and traceability.

01 / TRANSACTION DATA DOMAINS

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.

CORE INFORMATION DOMAINS

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.

01 / PARTIES

Economic Operators & Roles

Identifies the participants involved in the operation and the roles they perform under the relevant customs procedure.

Importer Exporter Declarant Representative EORI
KEY QUESTION Who is involved, and in which capacity?
02 / GOODS

Goods & Classification

Describes the goods covered by the transaction, including their identity, classification and relevant product characteristics.

Goods description Commodity code Item number Product attributes
KEY QUESTION What goods are being declared?
03 / COMMERCIAL

Values & Commercial Terms

Captures relevant transaction values and commercial information used to determine or support customs valuation.

Invoice value Currency Delivery terms Valuation data
KEY QUESTION What commercial facts support the declared value?
04 / MEASUREMENT

Quantities, Weights & Packaging

Records the physical quantities and measurements relevant to the goods, transport operation and applicable tariff rules.

Net mass Gross mass Packages Supplementary units
KEY QUESTION How much is being moved or declared?
05 / GEOGRAPHY

Origin & Geographical Context

Connects the operation to the relevant countries and territories, including origin and movement information.

Country of origin Dispatch country Destination Preference claim
KEY QUESTION Where do the goods originate and move?
06 / PROCEDURE

Customs Procedure & Routing

Defines the requested customs treatment and the operational context in which the declaration is processed.

Procedure code Previous procedure Customs office Additional procedure
KEY QUESTION What customs treatment is requested?
07 / EVIDENCE

Documents & Authorisations

Links the transaction to supporting commercial documents, certificates, licences and relevant customs authorisations.

Invoice Transport document Certificates Authorisations
KEY QUESTION What evidence supports the operation?
08 / PROCESSING

Identifiers, Status & Events

Records identifiers and events generated during processing, including customs responses and relevant decisions.

MRN Acceptance Control events Release status
KEY QUESTION What happened to the transaction?
DATA RELATIONSHIPS

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.

A REUSABLE BUSINESS INFORMATION

Master Data

Provides maintained information about products, business partners and other recurring business entities.

Product description
Operator identification
Maintained product attributes
B CONTROLLED CODES & VALUES

Reference Data

Supplies applicable classifications, codes and permitted values used to structure transaction information.

Country codes
Customs procedure codes
Document code lists
C OPERATION-SPECIFIC FACTS

Transaction Data

Describes the actual operation, using applicable reusable information alongside transaction-specific details.

Invoice and quantities
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.

PRACTICAL EXAMPLE

One import operation. Multiple data domains.

ILLUSTRATIVE SCENARIO

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.

PARTIES EU importer and non-EU supplier Relevant operator identities and roles
GOODS Industrial components Description and assessed commodity classification
COMMERCIAL VALUE EUR 12,500 invoice amount Illustrative amount; not necessarily the customs value
MEASUREMENTS 250 kg net mass Transaction-specific measurement
ORIGIN Origin to be determined Based on the applicable origin rules and evidence
PROCEDURE Release for free circulation Subject to the applicable procedure requirements
SUPPORTING RECORDS Invoice and transport documentation Other evidence may be required depending on the goods
PROCESSING Declaration and customs responses Identifiers and status events recorded as generated
The transaction is a connected record.

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.

TRANSACTION-LEVEL VALIDATION

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.

Reliable customs transactions depend on relationships between data elements. Accuracy requires more than valid individual fields: the goods, parties, values, procedures and evidence must describe the same underlying operation consistently.

02 / TRANSACTION DATA LIFECYCLE

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.

END-TO-END PROCESS

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.

01
SOURCE INFORMATION PREPARATION

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.

Typical inputs Invoices, orders, transport records, product information
Primary control Identify missing, conflicting or outdated source information
02
DATA ASSEMBLY PREPARATION

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.

Typical inputs Operator details, goods classification, procedure and document codes
Primary control Confirm applicability to the actual goods and operation
03
DATA VALIDATION PRE-SUBMISSION

Validate Before Transmission

Internal controls assess completeness, formatting and consistency. Substantive customs checks may also require reviewing classification, valuation, origin, authorisations and supporting evidence.

Typical checks Required fields, code validity, cross-field consistency
Primary control Resolve exceptions rather than silently replacing data
04
OFFICIAL INTERACTION SUBMISSION

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.

Typical records Submitted message, transmission time, response identifiers
Primary control Distinguish successful transmission from legal acceptance
05
CUSTOMS PROCESSING OFFICIAL EVENTS

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.

Typical records Official identifiers, customs messages, control outcomes
Primary control Preserve the original meaning and timing of official events
06
PROCEDURE OUTCOME OUTCOME

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.

Typical records Release notification or other procedure-specific outcome
Primary control Do not infer customs release from transmission or acceptance alone
07
RECORD MANAGEMENT POST-PROCESSING

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.

Typical records Final data, supporting documents, event history, later amendments
Primary control Maintain traceability without overwriting the original history
STATUS & LEGAL MEANING

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.

A INTERNAL WORKFLOW

Business Processing Status

Indicates progress inside the company’s ERP, forwarding platform or customs preparation software.

Examples Draft · Ready for review · Approved internally
Does not establish a customs authority decision.
B TECHNICAL COMMUNICATION

Message Processing Status

Indicates whether a message was sent, received or processed by a technical interface, according to the relevant system specification.

Examples Sent · Delivery acknowledged · Technical rejection
A technical acknowledgement is not necessarily legal acceptance.
C OFFICIAL CUSTOMS EVENT

Customs Procedure Status

Represents an event or decision communicated through the applicable customs system, with its procedure-specific legal meaning.

Examples Acceptance · Control notification · Release
Must be interpreted under the relevant procedure and rules.

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.

EVENT HISTORY & TRACEABILITY

Preserve what happened — and when.

A reliable transaction history records meaningful changes and links them to the corresponding messages, sources and operational decisions.

ILLUSTRATIVE EVENT LOG

Import declaration — sample timeline

EXAMPLE ONLY
09:05
Transaction record created

Commercial and shipment information imported into the preparation system.

ERP
09:18
Internal validation completed

Configured data checks passed; transaction approved for submission.

INTERNAL
09:22
Declaration transmitted

Outbound message and technical transmission reference recorded.

GATEWAY
09:24
Official acceptance received

Acceptance information and the applicable official identifier recorded.

CUSTOMS
10:10
Release notification received

Official release event linked to the transaction record.

CUSTOMS

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.

CHANGES & CORRECTIONS

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.

01 / BEFORE SUBMISSION

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.
02 / AFTER ACCEPTANCE

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.
03 / AFTER PROCESSING

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.

Transaction data is not static. Its reliability depends on preserving the connection between original business facts, submitted information, official customs responses and subsequent changes. The objective is a traceable history, not merely the latest status displayed by an application.

03 / DATA VALIDATION & INTEGRITY

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.

FOUR VALIDATION LAYERS

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.

01 STRUCTURAL

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.
02 SEMANTIC

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.
03 OPERATIONAL

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.
04 REGULATORY

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.

TRANSACTION CONTROL MATRIX

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.

PRACTICAL SCENARIO

When all the fields are valid — but the declaration is wrong.

ILLUSTRATIVE CASE

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.

01
ERP record retrieved

The system retrieves a previously maintained commodity code for the product.

DATA SOURCE
02
Technical validation passed

The code is recognised by the configured validation rules and fits the required format.

TECHNICALLY VALID
03
Product characteristics reviewed

The actual goods differ from those covered by the classification stored in the ERP.

DISCREPANCY
04
Classification reassessed

The appropriate classification is determined using the applicable nomenclature and relevant product information.

REVIEW
05
Transaction and source records updated

The declaration preparation record is corrected, while the master data issue is separately addressed to reduce recurrence.

RESOLVED
The important lesson

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.

EXCEPTION MANAGEMENT

Errors need ownership, evidence and resolution.

Identifying a discrepancy is only the beginning. Reliable workflows define how exceptions are classified, assigned, corrected and documented.

01 / DETECT

Identify the Exception

Record the failed control, affected fields and relevant transaction reference.

Example Declared quantity does not match the verified source record.
02 / CLASSIFY

Assess the Impact

Determine whether the issue is technical, operational or potentially relevant to customs compliance.

Example A formatting error differs from an unsupported preference claim.
03 / ASSIGN

Establish Responsibility

Direct the issue to the person or function capable of verifying the underlying facts.

Example Product engineering confirms technical characteristics.
04 / RESOLVE

Correct and Revalidate

Apply an evidence-based correction and repeat the controls affected by the change.

Example A corrected value triggers renewed consistency checks.
05 / DOCUMENT

Preserve the Decision Trail

Record what changed, why it changed, the supporting information and any relevant approval.

Example A classification review is linked to its supporting analysis.
06 / PREVENT

Address the Root Cause

Review whether the discrepancy originates in recurring business data, mappings or process controls.

Example An incorrect ERP mapping is corrected for future operations.
DATA INTEGRITY

Protect the record throughout its lifecycle.

Transaction integrity requires traceability between original source information, submitted declarations, official responses and subsequent changes.

01

Source Traceability

Link significant transaction values to their originating documents, systems or verified information.

02

Version History

Preserve relevant versions of the data, especially where changes affect submitted information.

03

Access & Responsibility

Define who may prepare, review, approve or modify transaction information.

04

Official Message Preservation

Retain relevant customs responses and their identifiers without replacing them with internal labels.

Customs data quality is not simply the absence of software errors. It depends on accurate underlying facts, appropriate regulatory treatment, consistent supporting records and a traceable process for resolving discrepancies.

04 / SYSTEM INTEGRATION & AUTOMATION

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.

INTEGRATION ARCHITECTURE

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.

CONCEPTUAL TRANSACTION DATA FLOW SYSTEM-NEUTRAL MODEL
01 / BUSINESS
ERP

ERP System

Orders, invoices, products, partners and commercial values.

02 / LOGISTICS
WMS

Warehouse System

Goods, quantities, packaging and inventory movements.

03 / TRANSPORT
TMS

Transport System

Shipment references, transport information and movements.

04 / EVIDENCE
DOC

Document Repository

Invoices, certificates, authorisations and supporting records.

DATA INTEGRATION & CONTROL LAYER CONTROLLED PROCESSING

Customs Transaction Data Preparation

Collects, maps, validates and reconciles information from different business sources before preparing the transaction for the applicable customs workflow.

Data mapping Reference validation Consistency checks Exception handling Version tracking Message correlation
A
CUSTOMS APPLICATION

Declaration Preparation & Submission

Creates and manages declarations or other customs messages through the applicable software and authorised channels.

B
OFFICIAL PROCESSING

Customs Authority Systems

Process relevant submissions and generate official messages, decisions and status events according to the applicable procedure.

↺
Return information matters as much as submission.

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.

DATA MAPPING

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.

AUTOMATION OPPORTUNITIES

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.

01 / EXTRACTION ↗

Source Data Collection

Retrieve relevant transaction information from structured business records without repeated manual entry.

CONTROL Verify source identity, completeness and freshness.
02 / TRANSFORMATION ⇄

Data Mapping & Normalisation

Convert source formats and units into the structures required by the destination workflow.

CONTROL Document transformations and avoid unsupported assumptions.
03 / VALIDATION ✓

Automated Quality Checks

Detect missing fields, invalid codes, inconsistent values and predefined cross-document discrepancies.

CONTROL Separate technical validation from substantive compliance.
04 / EXCEPTIONS !

Exception Routing

Direct unresolved issues to the responsible person or team before further processing.

CONTROL Preserve the exception, supporting evidence and resolution.
05 / COMMUNICATION ↔

Message & Status Synchronisation

Associate technical and official responses with the relevant business transaction.

CONTROL Do not confuse internal status with official customs events.
06 / RECORDS ▤

Evidence & Audit Trail

Link source documents, submitted data, responses and relevant subsequent changes.

CONTROL Apply appropriate access, retention and integrity safeguards.
INTEGRATION DESIGN PRINCIPLES

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.

01

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.

02

Duplicate Processing Protection

Design retries and message handling to reduce unintended duplicate transactions, while respecting the behaviour of the receiving system.

03

Versioned Mappings

Track mapping changes and the applicable code or specification versions used for each transaction.

04

Explicit Error Handling

Distinguish source errors, transformation failures, technical rejections and official customs responses.

05

Human Review Where Necessary

Route uncertain classifications, valuation questions, origin assessments and other substantive issues to qualified reviewers.

06

Secure Access & Data Protection

Apply appropriate authentication, authorisation, logging and protection to commercial and customs-related information.

PRACTICAL EXAMPLE

Automating an import declaration preparation workflow.

ILLUSTRATIVE SCENARIO

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.

STEP 01

ERP Export

Relevant order, invoice and product information is retrieved from the ERP.

STEP 02

Data Enrichment

Shipment details and required supporting information are associated with the transaction.

STEP 03

Validation

Configured controls identify missing fields, discrepancies and information requiring review.

STEP 04

Authorised Submission

Once ready, the declaration is submitted through the applicable authorised workflow.

STEP 05

Response Correlation

Relevant technical and official messages are linked to the original business transaction.

STEP 06

Record Reconciliation

The business workflow is updated according to the confirmed customs processing outcome.

Expected operational benefit

Less repetitive data entry, more consistent validation and improved traceability. These benefits depend on reliable source information, suitable interfaces and appropriate process controls.

IMPLEMENTATION RISKS

Automation can scale errors as easily as efficiency.

Poor source data and uncontrolled transformations may produce repeated errors across large numbers of transactions.

01 / SOURCE QUALITY

Incorrect Master Data

An outdated classification or operator record is copied into multiple declarations.

Control: source governance and transaction checks.
02 / MAPPING

Incorrect Field Transformation

A business value is mapped to an inappropriate customs data element.

Control: documented mapping and testing.
03 / COMMUNICATION

Lost or Misinterpreted Responses

The internal system does not correctly reconcile a customs message with its transaction.

Control: identifiers, monitoring and reconciliation.
04 / COMPLIANCE

Unreviewed Regulatory Decisions

Software automatically applies a customs treatment without sufficient supporting facts.

Control: explicit rules and appropriate review.

The objective of customs integration is not merely faster submission. It is to move reliable information between systems, maintain the relationship between business and customs records, and ensure that automated processing remains controlled, traceable and appropriate to the operation.

05 / PRACTICAL GUIDANCE & RESOURCES

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.

OPERATIONAL READINESS

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.

01
SOURCE DATA

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.
02
DATA PREPARATION

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.
03
VALIDATION

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.
04
CUSTOMS COMMUNICATION

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.
05
INTEGRATION & AUTOMATION

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.
06
TRACEABILITY & RECORDS

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.
PROCESS MATURITY

Three stages of transaction data management.

Organisations can improve transaction data reliability progressively, without assuming that every operation requires a fully automated customs platform.

LEVEL 01 / MANUAL

Document-driven processing

Information is gathered and entered manually, with controls dependent on individual procedures and operator experience.

Priority Standardise source records and review controls.
LEVEL 02 / CONNECTED

Structured data exchange

Business systems supply transaction information through repeatable mappings, with defined validation and exception handling.

Priority Improve data consistency and message traceability.
LEVEL 03 / CONTROLLED AUTOMATION

Integrated customs workflows

Suitable transactions move through controlled automated processes, while exceptions and substantive decisions receive appropriate review.

Priority Monitor outcomes, changes and regulatory dependencies.
FREQUENTLY ASKED QUESTIONS

Transaction data — common questions.

Practical answers to recurring questions about customs transaction records, ERP integration and data reliability.

What is customs transaction data?
Customs transaction data is information relating to a specific customs operation, such as the goods, parties, quantities, values, procedure, supporting documents and relevant customs messages. It differs from reusable master data and general reference data because it describes a particular transaction.
Is transaction data the same as master data?
No. Master data generally describes reusable business entities, such as products and trading partners. Transaction data describes a specific operation. A transaction may use master data, but the information must still be checked against the actual goods and circumstances.
Can ERP information be transferred directly into a customs declaration?
Some ERP information can be reused through appropriate integration. However, customs data requirements may differ from ordinary commercial fields. Mapping, enrichment, validation and additional customs-specific assessments may be necessary before submission.
Does successful electronic validation mean a declaration is legally correct?
No. Technical validation may confirm that a message satisfies configured structural or code requirements. It does not necessarily establish that classification, origin, customs value or the selected procedure is correct for the goods and transaction.
What is the difference between transmission, acceptance and release?
Transmission concerns sending information through a technical channel. Acceptance is an official customs event under the applicable declaration rules. Release is a separate customs decision allowing goods to be used for the purposes specified by the customs procedure. These events must not be treated as interchangeable.
Can an accepted customs declaration be corrected by changing the ERP record?
No. Changing internal business information does not itself amend an accepted customs declaration. Any amendment, invalidation or other formal correction must follow the applicable customs rules and procedures.
How long should customs transaction records be retained?
Article 51 of the Union Customs Code generally provides for a minimum three-year period for keeping documents and information required for customs controls, subject to the rules governing when that period begins and circumstances requiring longer retention. Other legal obligations may also apply. The applicable period should be assessed for the specific operation and records.
Does customs automation eliminate the need for human review?
No. Automation can reduce repetitive entry and support predefined controls, but uncertain facts, exceptions and substantive customs assessments may still require qualified human review. Automation does not remove the applicable legal responsibilities.
FINAL TAKEAWAY

Reliable customs operations depend on reliable transaction data.

Effective transaction data management combines accurate source information, appropriate customs assessments, controlled system integration and a traceable history of official interactions. Automation can improve efficiency, but data quality and legal responsibility remain fundamental.

CUSTOMS EXPLORER / DIGITAL CUSTOMS KNOWLEDGE