Customs Explorer
⌕

Customs Explorer

Customs data quality

CUSTOMS DATA / QUALITY & VALIDATION

Customs Data
Quality.

Reliable customs processes begin with reliable information.

Incomplete product records, inconsistent transaction details and outdated reference data can create errors throughout the customs process. Customs data quality helps organisations identify weaknesses, validate information and improve the reliability of data used in declarations and compliance decisions.

FROM SOURCE DATA TO CUSTOMS-READY INFORMATION
DATA QUALITY ENGINE
CONCEPTUAL MODEL
INPUT LAYER Customs source data ERP · Product · Transaction · Documents
DATA QUALITY CONTROL
01
Completeness Required information is present
02
Accuracy Values reflect supporting facts
03
Consistency Records agree across systems
04
Validity Values meet applicable rules
CONTROLLED OUTPUT Validated data for customs use Subject to relevant specialist and legal review
01
Detect problems early Identify incomplete and inconsistent records
02
Improve data reliability Validate information before operational use
03
Support customs compliance Preserve evidence and resolve exceptions
01 / DATA QUALITY DIMENSIONS

Quality is not
one single check.

Customs data can be complete but inaccurate, consistent but outdated, or technically valid without being legally correct. Effective quality management evaluates several characteristics together and considers how information will actually be used.

SIX CORE DIMENSIONS

What makes customs information reliable?

These dimensions provide a practical assessment framework. They are general data quality concepts, not a mandatory six-part model prescribed by EU customs legislation.

01 PRESENCE

Completeness

All information necessary for a particular customs process is available, including required fields and relevant supporting evidence.

EXAMPLE

A product record contains its description but lacks the technical specifications needed to assess tariff classification.

Is anything important missing?
02 CORRECTNESS

Accuracy

Recorded information reflects the relevant facts and can be supported by appropriate evidence or verification.

EXAMPLE

The declared net mass differs from the actual net mass established from reliable shipment records.

Does the value reflect reality?
03 ALIGNMENT

Consistency

Related records and systems do not contain unexplained contradictions for information that should agree.

EXAMPLE

The approved product master and the customs declaration system hold different commodity codes.

Do related records agree?
04 RULES

Validity

Information satisfies applicable technical, structural and contextual rules, such as accepted formats, code lists and field constraints.

EXAMPLE

A submitted data element contains a code that is not permitted in the relevant declaration context.

Does the value satisfy the relevant rules?
05 TIME

Timeliness

Information is sufficiently current and applicable to the relevant transaction, including changes in commercial facts and time-dependent customs measures.

EXAMPLE

A product master retains an outdated tariff reference after a nomenclature change becomes applicable.

Is the information applicable at the relevant time?
06 IDENTITY

Uniqueness & Identification

Records can be identified unambiguously, and duplicate or incorrectly linked records do not create conflicting customs information.

EXAMPLE

Two product records refer to the same physical item but contain different customs classifications.

Can the correct record be identified?
CUSTOMS-SPECIFIC APPLICATION

Where data quality problems become customs risks.

A single incorrect or unsupported value can affect the information used in a declaration. The consequences depend on the facts, applicable rules and customs procedure.

01 / CLASSIFICATION

Tariff classification data

Product descriptions, composition, function, specifications and approved classification records must be sufficiently reliable for the intended customs assessment.

DATA QUALITY ISSUE

The product description is too generic to establish relevant characteristics.

POTENTIAL IMPACT

The available evidence may be insufficient to support the declared classification.

02 / ORIGIN

Origin information

Origin-related records should distinguish relevant production facts, non-preferential origin, preferential origin determinations and supporting evidence.

DATA QUALITY ISSUE

A supplier’s country is automatically treated as the preferential origin.

POTENTIAL IMPACT

An origin claim may be unsupported by the applicable rules and evidence.

03 / VALUATION

Customs valuation inputs

Transaction information, relevant costs, adjustments and supporting documents must be assessed in accordance with the applicable valuation rules.

DATA QUALITY ISSUE

Relevant freight costs are missing from the information available for valuation assessment.

POTENTIAL IMPACT

The customs value may be calculated incorrectly if applicable adjustments are not considered.

04 / DOCUMENTATION

Supporting documents

Commercial invoices, transport documents, certificates, authorisations and other relevant evidence should be correctly associated with the transaction.

DATA QUALITY ISSUE

A transaction is linked to an outdated or unrelated supporting document.

POTENTIAL IMPACT

The organisation may be unable to substantiate the relevant declaration information.

QUALITY ASSESSMENT MATRIX

Translate quality dimensions into practical checks.

Different problems require different detection methods. Some can be identified with deterministic rules; others need source verification or specialist assessment.

ILLUSTRATIVE CONTROL DESIGN NOT A LEGAL CHECKLIST
Examples of data quality dimensions, checks and appropriate review methods
Dimension Example check Typical method Limitation
Completeness Identify missing required data elements Automated A populated field may still be insufficient
Accuracy Compare declared quantity with verified records Combined Source records may themselves be incorrect
Consistency Compare product codes across connected systems Automated Matching values do not prove correctness
Validity Check accepted formats and applicable code lists Automated Technical validity is not legal correctness
Timeliness Check reference validity against transaction dates Combined Changes may require legal interpretation
Uniqueness Detect duplicate product or party identifiers Combined Similar records may represent different entities
THE VALIDATION BOUNDARY

What software can check — and what it cannot establish alone.

Data quality systems can improve the reliability of inputs and highlight exceptions. Customs determinations may still require interpretation of law and factual evidence.

AUTOMATED CONTROL

Structured, testable conditions

  • Missing mandatory fields
  • Invalid formats and prohibited values
  • Duplicate or inconsistent identifiers
  • Differences between defined source records
  • Expired reference values where validity is known
  • Missing approval or evidence references

Best suited to clearly defined rules and verifiable data relationships.

SPECIALIST ASSESSMENT

Judgement, evidence and legal interpretation

  • Tariff classification in complex cases
  • Assessment of applicable origin rules
  • Evaluation of customs valuation adjustments
  • Interpretation of relevant customs provisions
  • Assessment of incomplete or conflicting evidence
  • Decisions on material discrepancies and corrections

Requires appropriate expertise and consideration of the individual circumstances.

A green validation result is not a customs ruling. Passing technical and business-rule checks indicates that the tested conditions were satisfied. It does not automatically demonstrate that a declaration is legally correct or that a customs authority will accept it.

PRACTICAL EXAMPLE

One product. Three different quality problems.

ILLUSTRATIVE CASE

A company prepares an import declaration for an industrial component. Its ERP record contains a commodity code, a country of origin and a product description. All three fields are populated, but further review reveals different weaknesses.

01 COMPLETENESS

Insufficient description

The product description does not include technical characteristics needed to assess classification.

Response Obtain reliable technical information.
02 ACCURACY

Unsupported origin

The origin field was copied from the supplier’s address without a relevant origin assessment.

Response Verify production facts and applicable rules.
03 TIMELINESS

Outdated tariff reference

The stored nomenclature reference has not been reviewed against the applicable version.

Response Review the code and relevant measures for the date.

The lesson: a record can be technically complete while remaining unsuitable for reliable customs use. Quality management must evaluate the substance, context and applicability of the information, not merely whether fields contain values.

Data quality is contextual. A reliable customs record is not simply a record that passes technical validation. It contains information that is sufficiently complete, accurate, consistent, valid and current for its intended customs purpose, with appropriate supporting evidence.

02 / VALIDATION & QUALITY CONTROLS

Detect errors before
they travel downstream.

Customs information moves through product masters, ERP platforms, logistics applications and declaration systems. Quality controls help identify missing, inconsistent or questionable data before it is reused, while directing matters requiring customs judgement to the appropriate reviewer.

CONTROL ARCHITECTURE

Five layers of data validation.

A layered approach separates technical checks from contextual verification and expert decisions. The model below is illustrative, not a prescribed EU customs system architecture.

01

Field controls

Presence, structure, data type and format.

STRUCTURAL
02

Reference controls

Permitted codes, valid dates and relevant lists.

REFERENCE
03

Cross-record checks

Defined relationships between connected records.

CONSISTENCY
04

Evidence review

Supporting documents, sources and discrepancies.

SUBSTANTIVE
05

Release decision

Resolve exceptions and authorise the intended use.

CONTROLLED

Important distinction: a technically valid commodity code may still be incorrect for the product. A successful automated check confirms only the conditions actually tested.

RULE LIBRARY

Turn quality expectations into testable controls.

A useful validation rule identifies the data being tested, its source, the condition to verify and the action required when the condition is not satisfied.

CUSTOMS DATA CONTROL MATRIX
ILLUSTRATIVE RULES
Examples of configurable customs data quality checks and their limitations
Control Example rule Failure response Control boundary
Required informationDQ-01 Check whether a required data element is present for the selected process. Hold / complete Presence does not establish accuracy.
Identifier formatDQ-02 Validate identifier structure against the applicable specification. Reject invalid format Format alone does not establish entitlement or status.
Code validityDQ-03 Compare a reference code with the relevant permitted values and dates. Review reference A permitted code may still be inappropriate.
Cross-system consistencyDQ-04 Identify unexplained differences between approved source data and downstream records. Investigate mismatch Both systems may contain the same incorrect value.
Document linkageDQ-05 Verify that the expected document reference is linked to the relevant transaction. Verify evidence Attachment does not prove authenticity or sufficiency.
Temporal applicabilityDQ-06 Check known effective dates against the relevant transaction date. Hold / reassess Legal applicability may require further analysis.
EXCEPTION MANAGEMENT

From detection to controlled resolution.

An exception should not disappear merely because a user edits a field. Its cause, correction, supporting evidence and disposition should remain understandable.

01
DETECT

Identify the anomaly

Record the failed rule, affected data and relevant transaction or product identifier.

02
ASSESS

Determine its significance

Establish whether the issue is technical, factual or potentially customs-relevant.

03
CORRECT

Resolve the source problem

Correct the authoritative record or obtain the missing information and evidence.

04
APPROVE

Review the proposed resolution

Apply the appropriate approval or specialist review for material changes.

05
RELEASE

Update and reconcile

Publish approved data, verify downstream updates and retain the resolution history.

!
Material exception

Potentially affects a customs determination, declaration or required evidence. Escalate for appropriate review.

~
Data discrepancy

Conflicting information requires reconciliation before the relevant record can be relied upon.

i
Quality observation

A non-blocking issue may be tracked for improvement when continued use is appropriately justified.

ILLUSTRATIVE OPERATIONAL CASE

When a product code changes in one system but not another.

CROSS-SYSTEM MISMATCH

A company’s approved product master contains an updated commodity code following a documented review. Its declaration application still contains the previous code. A consistency control identifies the mismatch before the affected record is used for a new declaration.

APPROVED PRODUCT MASTER Current reviewed classification Recorded with approval and effective date SOURCE RECORD
DECLARATION APPLICATION Previous stored classification Not reconciled with the approved update REVIEW REQUIRED

Appropriate resolution

Confirm the applicable classification and effective date, investigate the failed synchronisation, update the relevant downstream record and verify the result. Preserve historical values for transactions to which they applied. If declarations have already been lodged using questionable information, assess whether further action is required under the applicable customs rules.

CONTROL EVIDENCE

Make every significant correction traceable.

An audit trail should help reconstruct what happened, why a change was made and which records were affected. The appropriate level of detail depends on the significance of the information and the control.

01

What changed?

Previous value, new value and the relevant data element.

02

Why did it change?

Reason, exception reference and supporting information.

03

Who reviewed it?

Responsible person or function and applicable approval.

04

Where was it used?

Effective dates, impacted systems and relevant transactions.

Effective quality control is more than error detection. It connects the identified problem to a responsible reviewer, a justified resolution, an authorised update and a traceable record of what was changed.

03 / MONITORING & CONTINUOUS IMPROVEMENT

Measure quality.
Find the real cause.

Data validation identifies individual problems. Data quality monitoring reveals whether those problems are isolated, recurring or spreading across systems. Meaningful indicators help customs teams prioritise corrective action and evaluate whether improvements are actually working.

QUALITY OBSERVABILITY

From individual errors to measurable performance.

A monitoring dashboard should combine data quality measures with information about unresolved exceptions, affected processes and the time required to correct identified problems.

CUSTOMS DATA QUALITY / MONITORING OVERVIEW
ILLUSTRATIVE DATA ONLY
Required-field completeness
96.8%

Records meeting the defined completeness rule

Cross-system consistency
93.4%

Compared records without defined mismatches

Open quality exceptions
28
6 awaiting specialist review

Unresolved issues in the illustrative queue

Median resolution time
2.4days
Closed exceptions in selected period

Median elapsed time from detection to closure

QUALITY TREND

Completeness over six periods

Illustrative %

Period labels are illustrative. Comparable trends require consistent definitions, populations and measurement methods.

EXCEPTION DISTRIBUTION

Issues by category

Missing information40%
System mismatches30%
Reference issues20%
Evidence discrepancies10%

Example distribution of classified exceptions; not an industry benchmark.

MEASUREMENT FRAMEWORK

Choose indicators that lead to action.

Every KPI needs a defined population, calculation, reporting period, owner and response threshold. A percentage without those definitions can be misleading.

01 / COMPLETENESS

Required-field completeness rate

Measures the share of assessed records that contain all data elements required by a defined control.

FORMULA Complete records ÷ assessed records × 100
Define what counts as complete for each process.
02 / CONSISTENCY

Cross-system consistency rate

Measures agreement between selected comparable values across connected systems.

FORMULA Matching comparisons ÷ valid comparisons × 100
Exclude comparisons that are not genuinely equivalent.
03 / EXCEPTIONS

Exception incidence rate

Measures how frequently the defined population produces one or more quality exceptions.

FORMULA Records with exceptions ÷ assessed records × 100
Distinguish affected records from total error events.
04 / RESOLUTION

Median exception resolution time

Measures the typical elapsed time between exception detection and documented closure.

MEASUREMENT Median duration across closed exceptions
Report open-item age separately to avoid hiding backlogs.

Measurement discipline: a KPI should never be interpreted without its denominator, scope and limitations. For example, a high completeness rate does not prove that tariff classification, origin or customs valuation is legally correct.

ROOT CAUSE ANALYSIS

Correct the source, not just the symptom.

Repeated manual corrections may hide a structural weakness in the process. Root cause analysis examines why an error was created, why it was not prevented and why it reached a downstream system.

ILLUSTRATIVE CAUSAL CHAIN
OBSERVED PROBLEM Incorrect product data reaches the declaration application
PROCESS WEAKNESS Changes are copied without a defined customs review
UNDERLYING CAUSE Ownership and approval rules are missing from the update workflow
STRUCTURAL RESPONSE Introduce controlled approval and downstream reconciliation
INVESTIGATION QUESTIONS

Four questions worth asking.

01
Where did the error originate?

Identify the earliest record or process in which the incorrect information appeared.

02
Why was it accepted?

Examine missing checks, ambiguous rules, weak evidence or unclear responsibilities.

03
How far did it propagate?

Identify affected products, transactions, interfaces and potentially relevant declarations.

04
What prevents recurrence?

Choose a control improvement and verify its effectiveness through subsequent monitoring.

CONTINUOUS IMPROVEMENT

Build a feedback loop between data and process owners.

Sustainable improvement requires more than closing exceptions. Teams should periodically review recurring patterns, control effectiveness and changes in business or customs requirements.

01

Measure

Collect comparable quality indicators.

02

Prioritise

Identify material and recurring weaknesses.

03

Improve

Change source processes and preventive controls.

04

Verify

Check whether the intervention reduced the problem.

Close the loop: if the same exception continues to appear, the corrective action may have addressed individual records without eliminating the underlying cause.

RISK-BASED PRIORITISATION

Not every data problem has the same significance.

Priorities should reflect potential customs consequences, the scale of affected data, the likelihood of recurrence and the ability to detect problems before use.

HIGH PRIORITY

Potentially material customs impact

A questionable origin determination or classification affecting declarations may require prompt specialist assessment and appropriate containment.

PROCESS PRIORITY

Recurring systemic discrepancy

Repeated mismatches between product and declaration systems may indicate a failed interface or an ineffective change-management process.

MONITOR & IMPROVE

Limited operational inconvenience

A non-material formatting issue may be addressed through routine maintenance where it does not affect required data or the intended customs use.

These categories illustrate internal prioritisation. They do not replace applicable legal obligations, deadlines or the assessment of individual circumstances.

Better data quality is a measurable process improvement. Monitoring becomes valuable when it helps an organisation discover recurring weaknesses, correct their causes and demonstrate that the resulting controls work.

04 / OWNERSHIP & OPERATIONAL INTEGRATION

Make quality
an operational responsibility.

Reliable customs data depends on clear ownership, controlled corrections and coordination between business teams, customs specialists and IT. The objective is not simply to repair individual records, but to ensure that approved information reaches the right systems at the right time.

ACCOUNTABILITY MODEL

Define who owns each decision.

Responsibilities should be assigned by data domain and process. The same person may perform several roles in a smaller organisation, provided that appropriate review and control arrangements remain in place.

01

Data owner

Defines accountability for a data domain, approves its intended use and ensures that quality expectations are established.

02

Data steward

Coordinates routine quality checks, investigates exceptions and maintains agreed definitions and data standards.

03

Customs specialist

Reviews customs-relevant questions, including classification, origin, valuation and procedural implications.

04

IT / integration team

Maintains interfaces, access controls, technical validation, synchronisation and system-level change records.

Governance distinction: internal role assignments do not transfer or replace legal responsibilities established under customs law. The applicable declarant, representative and other relevant parties must still be identified according to the circumstances.

CONTROLLED REMEDIATION

Correct information at its authoritative source.

Updating a downstream field may solve an immediate discrepancy without resolving the underlying problem. A sustainable remediation process identifies the source record, confirms the correction and verifies the affected downstream systems.

01
IDENTIFY

Locate the authoritative record

Determine which system or approved process controls the relevant data element.

02
SUBSTANTIATE

Verify the proposed correction

Obtain supporting information and specialist review where customs determinations are involved.

03
AUTHORISE

Approve and version the change

Record the decision, effective date, relevant approval and previous value.

04
PROPAGATE

Update dependent systems

Apply the approved change through controlled interfaces or documented manual procedures.

05
RECONCILE

Verify the operational result

Confirm that the correct version is available for the intended use and assess any historical impact.

SYSTEM INTEGRATION

Keep customs information consistent across applications.

ERP, product information, logistics and declaration platforms may each hold different portions of the customs data landscape. Integration controls should make those relationships explicit and testable.

ILLUSTRATIVE CONTROLLED DATA FLOW CONCEPTUAL MODEL
PRODUCT DATA Product master / PIM

Specifications, product identifiers and maintained attributes

BUSINESS DATA ERP / commercial records

Parties, invoices, transactions and relevant financial information

SUPPORTING DATA Documents / evidence

Supplier information, supporting records and approval history

CONTROLLED INTEGRATION LAYER Mapping · Validation · Versioning · Exception handling

Applies defined transformations, checks source references and routes unresolved issues for review.

01 / CUSTOMS OPERATIONS Declaration preparation

Relevant validated information for the intended process

02 / BUSINESS OPERATIONS Logistics & reporting

Consistent operational references and controlled updates

The diagram describes a possible internal architecture. Actual integrations, data requirements and submission channels depend on the systems and customs procedures used.
01

Mapping integrity

Verify that fields retain their intended meaning, units and context when transferred between systems.

02

Change propagation

Identify failed synchronisations, outdated records and updates requiring downstream reconciliation.

03

Interface observability

Record failed transfers, processing outcomes and exceptions requiring investigation.

04

Historical consistency

Preserve information needed to understand which data version applied to a particular transaction.

OPERATIONAL RELEASE

Introduce a pre-use quality gate.

Before data is relied upon for a customs process, a defined control should establish whether the required checks have been completed and whether unresolved exceptions need further assessment.

PRE-USE DATA QUALITY CHECKLIST
ILLUSTRATIVE INTERNAL CONTROL
Required data is available

Completeness has been assessed against the relevant process requirements.

CHECK
Reference values are applicable

Codes, dates and reference data have been checked within the defined scope.

CHECK
Material discrepancies are resolved

Open issues affecting intended use have been reviewed and appropriately addressed.

CHECK
Supporting information is traceable

Relevant sources, evidence and approvals can be identified when required.

CHECK
Correct data version is selected

The intended transaction uses information applicable to its circumstances and date.

CHECK
READY FOR INTENDED USE

Defined checks completed; no unresolved issue prevents the relevant internal release.

HOLD / REVIEW REQUIRED

A material exception remains unresolved or the necessary review is incomplete.

Passing an internal quality gate does not constitute customs authority approval or establish legal compliance. Actual release conditions must reflect the applicable process and obligations.

PRACTICAL SCENARIO

A supplier changes a product specification.

PRODUCT DATA CHANGE

A supplier provides an updated technical specification showing a change in product composition. The purchasing team updates the product record, but the change may also be relevant to tariff classification or origin analysis. The data quality process must distinguish a routine attribute update from a change requiring customs review.

01 / CHANGE DETECTED

Updated technical information

The new specification is linked to the product record and compared with the previous version.

02 / IMPACT ASSESSED

Customs relevance reviewed

A competent reviewer determines whether classification or origin assumptions require reassessment.

03 / APPROVED UPDATE

Controlled data propagation

Approved changes are applied to the relevant source records and downstream systems.

04 / HISTORICAL REVIEW

Previous use considered

The organisation assesses whether past records or declarations may be affected, rather than automatically overwriting historical information.

Operational lesson: a change in product data does not automatically establish a change in customs classification or origin. It creates a reason to assess whether the previous determination remains appropriate.

Data quality becomes reliable when it is embedded in the operating process. Clear responsibilities, controlled source corrections, reconciled integrations and documented release decisions help prevent the same errors from recurring across systems.

05 / KNOWLEDGE & REFERENCE

Practical answers.
Reliable references.

Customs data quality connects technical validation, operational processes and legal responsibilities. The following questions clarify what internal controls can achieve, where specialist assessment remains necessary and how to build a more reliable data environment.

FREQUENTLY ASKED QUESTIONS

Customs Data Quality — FAQ

Eight practical questions about validation, ownership, accuracy, automation and the treatment of data quality exceptions.

01 What is customs data quality?

Customs data quality describes the extent to which information is accurate, complete, consistent, current and suitable for its intended customs use. Relevant information may include product descriptions, commodity codes, origin data, values, parties, supporting documents and transaction references.

Quality must be assessed in context. A field can be correctly formatted and still contain information that is unsuitable for a particular declaration or customs determination.

02 How does data quality differ from data governance?

Data governance establishes responsibilities, definitions, policies and decision-making arrangements. Data quality focuses on whether the actual information meets defined requirements.

Governance provides the framework for assigning ownership and resolving disagreements. Quality controls measure and improve the information managed within that framework.

03 Can software automatically verify the correctness of a commodity code?

Software can check code structure, applicable reference data, effective dates and consistency between systems. It can also flag changes or discrepancies that require further investigation.

However, determining the appropriate tariff classification may require technical product information, interpretation of classification rules and relevant legal materials. Passing an automated validation does not establish that the classification is legally correct.

04 Who should be responsible for customs data quality?

Responsibility is usually distributed across functions. Product teams may maintain technical specifications, finance teams may manage commercial records, customs specialists may review customs determinations and IT teams may control system integrations.

The organisation should identify accountable data owners, operational stewards and appropriate approval arrangements. These internal roles do not replace responsibilities established by customs legislation.

05 What happens when customs data is inconsistent across different systems?

The discrepancy should be investigated to identify the authoritative source, the reason for the difference and any affected transactions. The appropriate value should be established before a controlled correction is applied.

Updating every system with the newest available value is not always appropriate. Historical transactions may need to retain the information applicable at the relevant time.

06 Which KPIs are useful for monitoring customs data quality?

Useful indicators may include required-field completeness, cross-system consistency, exception incidence, unresolved issue age, resolution time and recurrence rates.

Each indicator needs a clearly defined population, calculation and reporting period. High quality scores do not, by themselves, demonstrate customs compliance.

07 Does the EU Customs Data Model guarantee that submitted data is accurate?

No. The EU Customs Data Model supports the harmonised definition and organisation of customs data requirements. It does not independently verify the factual accuracy of product information, commercial values or supporting evidence.

Organisations still need appropriate controls over data collection, maintenance, validation and use. Applicable requirements also depend on the relevant procedure and system implementation.

08 Can an internal data quality check replace customs compliance review?

No. Internal data quality checks support the reliability of information used in customs processes, but they cannot replace legal analysis, procedural requirements, specialist judgement or decisions of customs authorities.

Where an error may affect an existing customs declaration, the organisation should assess the applicable legal consequences and any necessary corrective action separately.

CUSTOMS EXPLORER / DATA INTELLIGENCE

Better customs decisions
begin with better data.

Reliable information does not happen automatically. It requires clear definitions, appropriate verification, accountable decisions and controls that remain effective as products, regulations and systems change.

Customs Explorer — Educational information on EU customs processes, data and technology. This guide does not constitute a binding customs determination or individual legal advice.