Customs Explorer
⌕

Customs Explorer

Customs data governance

CUSTOMSTECH / DATA GOVERNANCE

Customs Data
Governance.

Reliable customs operations begin with data that has clear ownership, defined rules and accountable decision-making.

Explore how organisations govern customs-related information across ERP systems, product records, trade documents and declaration workflows. Understand data ownership, stewardship, access controls, lifecycle management and the evidence needed to support consistent customs processes.

DATA GOVERNANCE MODEL CONTROLLED DATA
GOVERNANCE DATA OWNERSHIP · RULES · CONTROL
01
Data ownership Accountable business roles
OWNER
02
Data standards Definitions and validation rules
RULES
03
Data lineage Source, changes and downstream use
TRACE
04
Access governance Permissions and controlled changes
ACCESS
01 / Know the source

Identify where customs-critical information originates.

02 / Assign responsibility

Define who maintains, verifies and approves the data.

03 / Preserve traceability

Understand how information changes and reaches customs workflows.

01 / THE GOVERNANCE FRAMEWORK

Good customs data needs
more than accurate fields.

Customs data governance defines how trade-related information is owned, maintained, approved, shared and controlled across an organisation. It connects business responsibility with the systems and processes that use the data.

FOUNDATIONAL PRINCIPLES

Five pillars of a controlled data environment.

A practical governance model combines defined responsibilities, consistent standards and traceable decisions. These pillars are an illustrative organisational framework, not a mandatory EU regulatory model.

01 / ACCOUNTABILITY 01

Data ownership

Assign responsibility for important customs data domains, including product information, trading partners, transaction records and supporting evidence.

KEY QUESTION Who is accountable for this information?
02 / MAINTENANCE 02

Data stewardship

Establish who maintains records, investigates inconsistencies, coordinates corrections and applies the agreed operational data-management procedures.

KEY QUESTION Who maintains and resolves data issues?
03 / CONSISTENCY 03

Data definitions

Document field meanings, permitted values, data sources, business rules and the distinction between commercial information and customs-specific determinations.

KEY QUESTION Does everyone interpret the field consistently?
04 / CONTROL 04

Access and change governance

Define who may create, modify, validate or approve data, and establish controls for sensitive or high-impact changes before downstream use.

KEY QUESTION Who may change or approve the record?
05 / EVIDENCE 05

Lineage and traceability

Track where information originated, how it was transformed, which version was used and where it was transmitted or relied upon.

KEY QUESTION Can the information’s history be reconstructed?

Governance is different from data quality. Data quality concerns properties such as accuracy, completeness and consistency. Governance establishes the responsibilities, rules and decision processes used to manage those properties over time.

ROLES & ACCOUNTABILITY

Separate business ownership from technical administration.

A data governance programme works best when responsibilities are explicit. One individual may perform several roles in a smaller organisation, provided conflicts and approval requirements are addressed.

OWNER 01

Business Data Owner

Accountable for a defined data domain, its business purpose, governance requirements and the acceptance of significant data-related risks.

EXAMPLE A product-data owner responsible for the governance of product master information.
STEWARD 02

Data Steward

Coordinates day-to-day maintenance, data definitions, issue investigation and correction workflows under the agreed governance policies.

EXAMPLE A master-data specialist resolving conflicting product descriptions.
SPECIALIST 03

Customs Specialist

Provides customs expertise for relevant data requirements, interpretation, supporting evidence and decisions that require professional assessment.

EXAMPLE Reviewing the basis for a commodity classification or origin determination.
TECHNICAL 04

System Custodian

Manages the technical environment, access mechanisms, integrations, availability and implementation of approved data controls.

EXAMPLE An ERP administrator maintaining controlled data interfaces.
RESPONSIBILITY MODEL

Make decisions and handovers explicit.

A responsibility matrix can clarify who performs an activity, who approves it and which expertise must be consulted. The example below is illustrative.

Illustrative allocation of customs data governance responsibilities
Governance activity Data Owner Data Steward Customs Specialist System Custodian
Define data domain ownership Support Consulted Informed
Maintain agreed data definitions Responsible Consulted Informed
Review customs-specific determinations Support Specialist review Informed
Investigate data discrepancies Responsible Consulted Technical support
Implement approved access controls Consulted Consulted Responsible

*Business data ownership does not replace the legal responsibilities of the declarant, customs representative or other relevant parties. Customs-specific approval authority must be allocated appropriately within the organisation.

DATA LIFECYCLE GOVERNANCE

Apply governance throughout the life of the data.

Customs-relevant information moves through multiple systems and operational stages. Controls should follow that information, not exist only at the final declaration step.

ILLUSTRATIVE GOVERNED DATA LIFECYCLE END-TO-END CONTROL
01

Create or acquire

Establish the origin, owner and initial evidence for the information.

SOURCE CONTROL
02

Validate

Apply relevant checks and identify missing or inconsistent values.

VALIDATION
03

Approve and maintain

Control material changes and preserve approved record versions.

CHANGE AUTHORITY
04

Use and exchange

Transfer information through authorised interfaces and workflows.

LINEAGE
05

Retain or dispose

Apply relevant retention, access and lawful disposal requirements.

RECORD GOVERNANCE
PRACTICAL EXAMPLE

Who governs the commodity code in a product master record?

ILLUSTRATIVE SCENARIO
PRODUCT TEAM

Maintains product facts

Supplies accurate descriptions, composition, technical specifications and other relevant product information.

CUSTOMS SPECIALIST

Reviews classification

Assesses the relevant classification information and documents the reasoning supporting the determination.

DATA STEWARD

Maintains the approved record

Coordinates entry of the approved information, version history and resolution of conflicting records.

IT / ERP TEAM

Controls downstream distribution

Ensures the approved data is made available through the intended system interfaces and access rules.

Governance outcome: the organisation can identify who supplied the product facts, who reviewed the classification, which record was approved and how that information reached the relevant customs process. The arrangement does not itself guarantee that the classification is legally correct.

Effective customs data governance connects people, processes and systems. The objective is not simply to centralise information, but to ensure that customs-critical data remains controlled, explainable and usable throughout its operational lifecycle.

02 / DATA DOMAINS & INFORMATION FLOW

Know the data.
Know where it comes from.

Customs processes depend on information created by different departments and external parties. Governance begins by identifying each critical data domain, its authoritative source, its responsible owner and the systems that consume it.

CUSTOMS DATA LANDSCAPE

Six domains that require coordinated governance.

These domains are a practical way to organise customs-related information. Their boundaries may differ according to the organisation, customs procedures and IT architecture.

DOMAIN 01 PARTIES

Trading partner data

Information identifying suppliers, customers, importers, exporters, declarants and representatives, where relevant to the customs process.

TYPICAL ELEMENTS Legal name, address, EORI identifier, party role and representation details.
GOVERNANCE FOCUS Identity, role and validity
DOMAIN 02 PRODUCTS

Product master data

Technical and commercial characteristics used to identify goods and support customs determinations throughout the product lifecycle.

TYPICAL ELEMENTS Product description, composition, material, function and technical specifications.
GOVERNANCE FOCUS Technical evidence and change control
DOMAIN 03 CUSTOMS

Customs determinations

Customs-specific information derived from technical facts, commercial circumstances and applicable legal requirements.

TYPICAL ELEMENTS Commodity classification, origin determination, valuation inputs and relevant authorisations.
GOVERNANCE FOCUS Specialist review and supporting evidence
DOMAIN 04 TRADE

Commercial transaction data

Information describing the underlying transaction and the commercial conditions relevant to the movement of goods.

TYPICAL ELEMENTS Invoice values, currency, quantities, delivery terms, freight and insurance data.
GOVERNANCE FOCUS Transaction consistency and valuation relevance
DOMAIN 05 LOGISTICS

Shipment and movement data

Information describing how goods are packed, transported and moved between locations and customs procedures.

TYPICAL ELEMENTS Packages, gross mass, transport references, routing and shipment identifiers.
GOVERNANCE FOCUS Shipment identity and data reconciliation
DOMAIN 06 EVIDENCE

Documents and customs records

Supporting information, declarations, communications and records used to demonstrate how a customs process was performed.

TYPICAL ELEMENTS Commercial invoices, origin evidence, transport documents, declarations and customs responses.
GOVERNANCE FOCUS Integrity, accessibility and retention
SYSTEM ARCHITECTURE

Follow information across system boundaries.

A data field may originate in one system, be transformed in another and eventually support a customs declaration. Governance must cover the handovers between them.

ILLUSTRATIVE CUSTOMS DATA FLOW GOVERNED EXCHANGE
01 / SOURCES
ERP / Product Master Products, parties and transactions
Logistics Systems Shipment and movement information
External Evidence Supplier documents and supporting data
02 / CONTROLLED PROCESSING
GOVERNANCE LAYER Validation & Mapping Field definitions and consistency checks
Review & Approval Customs determinations and exceptions
Lineage & Audit Source references, versions and decisions
03 / DOWNSTREAM USE
Customs Software Declaration preparation and validation
Electronic Interfaces Authorised exchanges with relevant systems
Records & Reporting Evidence, monitoring and reconciliation
SOURCE OF TRUTH

One data element can have several sources, but not several uncontrolled authorities.

The authoritative source should be defined for each data element and business context. It is not always the system where the information is first entered.

01 / ORIGIN

Source of the fact

Identify who originally supplied the information and what evidence supports its reliability.

Example: a manufacturer’s technical specification
02 / DECISION

Authority to determine

Establish who may evaluate the information and approve a customs-relevant determination.

Example: an authorised internal classification reviewer
03 / RECORD

Authoritative record

Specify where the approved information is maintained, including its version, validity and supporting references.

Example: a governed product classification record
04 / DISTRIBUTION

Controlled downstream use

Define how approved information reaches dependent systems and how discrepancies are identified.

Example: a version-controlled ERP-to-customs interface
PRACTICAL GOVERNANCE SCENARIO

A product changes. Which customs records need attention?

ILLUSTRATIVE CASE

A manufacturer updates the material composition of a product. The product identifier remains unchanged, but the technical characteristics used in a previous customs classification assessment may no longer be the same.

01

Detect the change

The product team records the revised technical specification and identifies the affected item.

02

Assess customs impact

The customs specialist determines whether the changed characteristics require a new classification assessment or affect other customs information.

03

Approve the relevant record

Any revised determination is documented with its supporting reasoning and applicable effective date.

04

Update dependent systems

The approved information is distributed to affected workflows, while relevant historical records remain traceable.

Governance outcome: a technical product change triggers a controlled review rather than silently propagating potentially outdated customs information. Whether classification or other customs treatment actually changes requires a substantive assessment.

Customs data governance must extend beyond the declaration. When ownership, source authority and information flows are clearly defined, organisations can detect problems earlier and preserve the context needed to understand how customs information was produced and used.

03 / POLICIES, VALIDATION & CHANGE CONTROL

Define the rules.
Control every change.

Customs data governance becomes operational when policies are translated into validation rules, approval requirements and controlled updates. A reliable framework prevents unverified information from silently reaching downstream customs processes.

GOVERNANCE POLICIES

Six policy areas that protect customs-critical information.

Policies establish how information should be managed across its lifecycle. Their precise implementation depends on business risk, applicable customs obligations and the organisation’s technical environment.

POLICY 01 01

Data creation standards

Define mandatory fields, accepted formats, reference values and minimum supporting information before a record can be used.

EXAMPLE A new product requires a meaningful technical description before customs review.
POLICY 02 02

Authoritative source rules

Identify which source is authoritative for each data element and how conflicting information must be investigated.

EXAMPLE A customs classification record is not overwritten by an unrelated sales-system update.
POLICY 03 03

Approval and modification rights

Establish which roles may propose, review, approve and implement changes to sensitive information.

EXAMPLE A material change to classification information requires designated review.
POLICY 04 04

Version and validity management

Preserve relevant historical values, effective dates and the relationship between a change and affected transactions.

EXAMPLE A product record retains the classification used for an earlier declaration.
POLICY 05 05

Exception and correction procedures

Define how errors are reported, investigated, corrected and escalated, including the treatment of affected downstream records.

EXAMPLE Conflicting country-of-origin information triggers review before further use.
POLICY 06 06

Retention and evidence management

Establish how relevant records, supporting documents and decision histories are retained, protected and made retrievable.

EXAMPLE The supporting evidence for a customs determination remains linked to its record.
VALIDATION ARCHITECTURE

Not every data check answers the same question.

Effective validation combines technical checks, business consistency rules and customs-specific assessments. Passing one layer does not guarantee that the information is legally or substantively correct.

MULTI-LAYER VALIDATION MODEL ILLUSTRATIVE DESIGN
01
STRUCTURAL

Format and completeness

Verify required fields, permitted formats, data types and structural consistency.

CHECK Is the required value present and formatted as expected?
02
REFERENTIAL

Reference data integrity

Compare values with relevant reference datasets and assess their applicability at the relevant time.

CHECK Is the reference value valid for this context and date?
03
BUSINESS

Cross-field consistency

Identify contradictions between product, transaction, shipment and supporting information.

CHECK Are related values consistent across source records?
04
SPECIALIST

Customs-specific assessment

Refer matters requiring interpretation, judgement or supporting evidence to competent reviewers.

CHECK Is the customs determination appropriately supported?

Important distinction: a commodity code can pass a format check and exist in a reference dataset while still being unsuitable for the goods concerned. Technical validation must not be presented as proof of correct tariff classification.

CONTROLLED CHANGE MANAGEMENT

From proposed change to approved downstream use.

Sensitive data changes should follow a documented sequence. The appropriate review and approval steps depend on the impact of the information being changed.

01
REQUEST

Propose

Record the proposed value, reason and supporting evidence.

02
ASSESS

Review impact

Identify affected systems, records and customs processes.

03
DECIDE

Approve or reject

Obtain the appropriate authorised decision.

04
IMPLEMENT

Publish version

Update the governed record and relevant effective dates.

05
VERIFY

Reconcile

Confirm intended downstream updates and preserve the history.

APPROVED CHANGE

The authorised version may be released to the designated downstream systems after the required implementation checks.

PENDING REVIEW

The proposed change remains separate from the approved value until the necessary review is completed.

REJECTED CHANGE

The proposed value is not published. The reason for rejection and any required corrective action are recorded.

VERSION CONTROL & TEMPORAL CONTEXT

Preserve what was known, approved and used at the relevant time.

Overwriting a record without preserving its history can make it difficult to reconstruct the information used for previous customs transactions.

ILLUSTRATIVE PRODUCT CUSTOMS RECORD PRODUCT REF: ITEM-2048
V1

Previously approved record

HISTORICAL

The classification assessment was based on the product characteristics available when this version was approved.

Technical specification: Revision A Decision reference: CLASS-001
V2

Change under assessment

REVIEW

A revised technical specification triggers an assessment of whether customs information needs to change.

Technical specification: Revision B Review reference: REV-002
V3

New approved record, if required

CONDITIONAL

If the review results in an approved update, the new version records the decision, effective date and downstream implementation.

Effective date: To be established Approval reference: Required
DOWNSTREAM PROTECTION

Prevent an unverified change from spreading across systems.

A controlled interface should distinguish an approved master-data update from a proposed or disputed value. Publication and synchronisation should follow the applicable release rules.

01 / CHANGE DETECTION ↻

Identify affected records

Detect changes to critical fields and determine which products, transactions, interfaces or documents may be affected.

02 / RELEASE CONTROL ✓

Publish approved values

Prevent pending or rejected updates from replacing approved values in systems that rely on them.

03 / RECONCILIATION ≡

Verify downstream consistency

Compare the expected and actual values received by dependent systems and investigate differences.

04 / EXCEPTION RESPONSE !

Contain and correct errors

Define how failed updates are isolated, escalated, corrected and reprocessed without uncontrolled duplication.

PRACTICAL EXAMPLE

An ERP commodity code is changed without customs approval.

ILLUSTRATIVE SCENARIO
THE RISK

A user updates a commodity code in the ERP. The change is automatically transmitted to customs software, where it may be used for subsequent declaration preparation. The change has not been reviewed by the designated customs specialist.

THE GOVERNANCE RESPONSE

The proposed value enters a controlled review state. The approved value remains available where appropriate, the reviewer assesses the evidence and the system records the decision before releasing an authorised update.

Expected outcome: the organisation reduces the risk of an unreviewed master-data change affecting future customs declarations. If incorrect information has already been used, a separate assessment of affected transactions and any necessary corrective action is required.

Governed data changes must be deliberate, authorised and traceable. Policies define expectations, validation identifies potential problems, approval establishes decision authority and version control preserves the information needed to reconstruct past operations.

04 / MONITORING, LINEAGE & EVIDENCE

Governance must be
visible and verifiable.

A customs data governance framework cannot rely exclusively on written policies. Organisations need ways to monitor whether controls operate as intended, identify recurring weaknesses and reconstruct the information behind customs-related decisions.

CONTINUOUS GOVERNANCE MONITORING

Measure the effectiveness of the controls, not just the volume of data.

Monitoring should focus on indicators that reveal potential weaknesses in data quality, approval processes, change management and downstream consistency.

01 / COMPLETENESS

Critical field coverage

Monitor the proportion of relevant records containing the information required for their intended use.

ILLUSTRATIVE INDICATOR Complete records / Relevant records
02 / EXCEPTIONS

Unresolved data issues

Track outstanding discrepancies, their age, assigned ownership and the operational processes potentially affected.

ILLUSTRATIVE INDICATOR Open issues by severity and age
03 / APPROVAL

Change approval coverage

Identify sensitive data changes that were released without the required review or recorded authorisation.

ILLUSTRATIVE INDICATOR Approved changes / Controlled changes
04 / CONSISTENCY

Cross-system discrepancies

Detect differences between authoritative records and the values held in dependent operational systems.

ILLUSTRATIVE INDICATOR Discrepant records / Compared records

Metrics require context. A low exception count does not necessarily indicate effective governance: controls may be incomplete, incorrectly configured or failing to detect relevant problems. Monitoring should consider both control coverage and detected outcomes.

DATA LINEAGE

Reconstruct the journey from source information to customs use.

Data lineage describes how information originates, changes and moves between systems. For customs purposes, it can help establish which source values supported a particular transaction.

ILLUSTRATIVE CUSTOMS DATA LINEAGE SOURCE → DECISION → USE
01 SOURCE

Product specification

Technical characteristics supplied by the responsible business function.

Document reference SPEC-EXAMPLE-A
02 REVIEW

Customs assessment

Specialist review of the relevant customs determination.

Decision reference REV-EXAMPLE-01
03 MASTER RECORD

Approved customs data

Governed value with approval history and applicable validity.

Record reference MASTER-EXAMPLE-02
04 TRANSACTION

Customs declaration

Information selected and used for a specific declaration.

Transaction reference DECL-EXAMPLE-03

Lineage is more than a list of systems. A useful record should preserve relevant source references, transformations, approval decisions, versions and the values actually used. The identifiers above are fictional examples, not real customs transaction references.

AUDITABILITY & EVIDENCE

What should a governance audit trail explain?

An audit trail should make important data decisions understandable after the event, including when the original users or system configurations have changed.

01 / IDENTITY

What information was involved?

Identify the affected data element, product, party, transaction or document.

Record ID · Field · Related entity
02 / ORIGIN

Where did it come from?

Preserve the relevant source, supporting document and acquisition context.

Source system · Evidence reference
03 / DECISION

Who reviewed or approved it?

Record the responsible role, decision outcome and supporting rationale.

Reviewer · Approval · Reason
04 / TIME

When was it valid and used?

Distinguish creation, modification, approval and relevant effective dates.

Timestamp · Version · Validity
05 / TRANSFORMATION

How was it changed?

Document material changes, mapping logic and relevant system transformations.

Previous value · New value · Rule
06 / DOWNSTREAM USE

Where was it applied?

Connect the approved information to affected systems and customs transactions.

Interface · Transaction · Outcome
ISSUE MANAGEMENT

Turn recurring data problems into corrective action.

Monitoring becomes valuable when identified weaknesses are assigned, investigated and resolved. Repeated issues may indicate a problem with the underlying process.

ILLUSTRATIVE DATA ISSUE REGISTER NO LIVE DATA
Fictional examples of customs data governance issues
Issue Affected domain Control response Status
Conflicting product composition Product master Request updated technical evidence Review
Unapproved commodity code change Customs determination Hold proposed update for specialist review On hold
ERP / customs software mismatch System integration Reconcile approved source and target values In progress
Missing origin evidence Supporting documents Investigate evidence requirements and availability Review
PRACTICAL AUDIT SCENARIO

A customs authority questions the classification used in a past declaration.

ILLUSTRATIVE CASE

A customs authority examines a declaration and requests relevant information concerning the tariff classification of the goods. The company must establish what product information and classification reasoning were available and used at the time.

01

Locate the transaction

Identify the declaration and the relevant product and supporting records.

02

Recover the historical version

Retrieve the product characteristics and customs data applicable to the transaction.

03

Reconstruct the assessment

Identify the reasoning, supporting evidence and relevant decisions.

04

Provide relevant records

Retrieve the documentation required for the examination and assess any identified issues.

Governance outcome: the company can reconstruct the information behind the declaration and support an informed response to the authority. A complete audit trail does not establish that the original classification was necessarily correct.

RECORD INTEGRITY & RETENTION

Evidence must remain reliable and retrievable.

Governance should consider the preservation, accessibility and protection of records throughout the applicable retention period, including after system migrations or organisational changes.

01

Integrity

Protect relevant records against unauthorised alteration and preserve the reliability of historical evidence.

02

Retrievability

Ensure authorised personnel can locate and retrieve information needed for legitimate operational or legal purposes.

03

Retention rules

Apply the relevant customs record-keeping requirements while considering any other applicable legal obligations.

04

Access and protection

Restrict access appropriately, especially where records contain commercially sensitive or personal information.

Effective governance leaves evidence of how information was managed. Monitoring identifies weaknesses, lineage connects source data to operational use, and reliable records support investigation, correction and accountability over time.

05 / KNOWLEDGE, REGULATION & NEXT STEPS

Governance questions.
Practical answers.

Customs data governance brings together business responsibilities, information management and customs compliance. These frequently asked questions clarify how governance operates and where its legal and practical limits lie.

FREQUENTLY ASKED QUESTIONS

Understanding customs data governance.

The answers describe general governance principles in an EU customs context. Specific obligations depend on the transaction, customs procedure and applicable legislation.

01 What is customs data governance?

Customs data governance is the organisational framework used to define ownership, responsibilities, standards and controls for information supporting customs activities.

It covers data creation, validation, approval, modification, exchange, retention and traceability. Its purpose is to help organisations manage customs-relevant information consistently and accountably.

02 How is customs data governance different from data quality?

Data quality describes characteristics of information, such as accuracy, completeness, consistency and suitability for its intended use.

Data governance defines who is responsible for managing those characteristics, which standards apply, how problems are resolved and how changes are controlled.

A governance framework can support data quality, but it cannot guarantee that every customs determination is legally correct.

03 Who should own customs data within an organisation?

Ownership should be allocated according to the nature of the information and the organisation’s operating model.

Product teams may be responsible for technical product facts, finance for relevant commercial information, logistics for shipment information and customs specialists for reviewing customs-specific determinations.

Clear internal ownership does not alter the legal responsibilities established by customs legislation.

04 Can an ERP system be the single source of truth for customs data?

An ERP may serve as the authoritative repository for selected data elements, but it is not automatically authoritative for every customs-related determination.

Some information originates from suppliers, technical documentation, specialist assessments, customs decisions or other systems. Governance should establish the appropriate authoritative source for each element and control its downstream distribution.

05 Why is version control important for customs records?

Customs information can change over time because products, transactions, legal measures and business circumstances change.

Version control helps distinguish current information from the values and supporting evidence used in earlier transactions. It also helps reconstruct decisions during investigations and post-release controls.

Organisations should distinguish the date a record was changed from the date on which a particular value became applicable.

06 Does automated data validation guarantee customs compliance?

No. Automated validation can identify missing fields, incorrect formats, inconsistent values and other detectable issues.

It cannot, by itself, establish the correct classification, origin or customs value in every case. These matters may require legal interpretation, supporting evidence and professional assessment.

A successful internal validation is not equivalent to acceptance or approval by a customs authority.

07 How long must customs documents and information be retained in the EU?

Article 51 of the Union Customs Code generally requires persons concerned to keep documents and other information for at least three years, by means accessible to and acceptable to customs authorities.

The applicable period and its starting point depend on the circumstances. Extensions and other legal retention requirements may also apply. Organisations should assess the relevant obligations rather than adopting a universal three-year deletion rule.

08 What should a company be able to demonstrate during a customs audit?

Depending on the subject of the examination, a company may need to provide relevant transaction records, supporting documents, product information and explanations of customs determinations.

Effective governance can make it easier to identify the source of information, recover historical versions and explain how records were reviewed and used. The precise documents required depend on the applicable legal obligations and the authority’s request.

OFFICIAL EU LEGAL FRAMEWORK

The legislation behind customs information obligations.

Data governance is an organisational discipline. The regulations below provide important legal context for customs information, declarations, supporting records and related obligations.

PRIMARY CUSTOMS LEGISLATION EU

Union Customs Code

Regulation (EU) No 952/2013

Establishes the core EU customs framework. Particularly relevant provisions include Article 15 on information and document responsibilities, Article 48 on post-release controls, Article 51 on keeping documents and information, and Article 162 on the content of standard customs declarations.

View official regulation
DELEGATED CUSTOMS RULES EU

UCC Delegated Act

Commission Delegated Regulation (EU) 2015/2446

Supplements the Union Customs Code with detailed provisions relating to customs procedures and requirements. Relevant data obligations must be assessed in conjunction with the UCC, implementing legislation and applicable amendments.

View official regulation
IMPLEMENTING CUSTOMS RULES EU

UCC Implementing Act

Commission Implementing Regulation (EU) 2015/2447

Sets out implementing rules for provisions of the Union Customs Code. Its requirements form part of the wider legal and procedural environment in which customs data is prepared, exchanged and used.

View official regulation
PERSONAL DATA PROTECTION EU

General Data Protection Regulation

Regulation (EU) 2016/679

Relevant where customs-related systems process personal data. Governance should consider applicable principles such as purpose limitation, data minimisation, accuracy, storage limitation and appropriate security.

View official regulation
CUSTOMS EXPLORER / DATA GOVERNANCE

Reliable customs processes
start with governed information.

Clear ownership, controlled changes, traceable decisions and reliable evidence create a stronger foundation for customs operations, digital integration and future automation.

Customs Explorer provides general educational information about EU customs processes and digital customs practices. Content does not replace the applicable legislation, official customs guidance or case-specific professional assessment.