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.
Identify where customs-critical information originates.
Define who maintains, verifies and approves the data.
Understand how information changes and reaches customs workflows.
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.
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.
Data ownership
Assign responsibility for important customs data domains, including product information, trading partners, transaction records and supporting evidence.
Data stewardship
Establish who maintains records, investigates inconsistencies, coordinates corrections and applies the agreed operational data-management procedures.
Data definitions
Document field meanings, permitted values, data sources, business rules and the distinction between commercial information and customs-specific determinations.
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.
Lineage and traceability
Track where information originated, how it was transformed, which version was used and where it was transmitted or relied upon.
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.
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.
Business Data Owner
Accountable for a defined data domain, its business purpose, governance requirements and the acceptance of significant data-related risks.
Data Steward
Coordinates day-to-day maintenance, data definitions, issue investigation and correction workflows under the agreed governance policies.
Customs Specialist
Provides customs expertise for relevant data requirements, interpretation, supporting evidence and decisions that require professional assessment.
System Custodian
Manages the technical environment, access mechanisms, integrations, availability and implementation of approved data controls.
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.
| Governance activity | Data Owner | Data Steward | Customs Specialist | System Custodian |
|---|---|---|---|---|
| Define data domain ownership | Accountable | Support | Consulted | Informed |
| Maintain agreed data definitions | Accountable | Responsible | Consulted | Informed |
| Review customs-specific determinations | Accountable* | Support | Specialist review | Informed |
| Investigate data discrepancies | Accountable | Responsible | Consulted | Technical support |
| Implement approved access controls | Approves scope | 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.
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.
Create or acquire
Establish the origin, owner and initial evidence for the information.
SOURCE CONTROLValidate
Apply relevant checks and identify missing or inconsistent values.
VALIDATIONApprove and maintain
Control material changes and preserve approved record versions.
CHANGE AUTHORITYUse and exchange
Transfer information through authorised interfaces and workflows.
LINEAGERetain or dispose
Apply relevant retention, access and lawful disposal requirements.
RECORD GOVERNANCEWho governs the commodity code in a product master record?
Maintains product facts
Supplies accurate descriptions, composition, technical specifications and other relevant product information.
Reviews classification
Assesses the relevant classification information and documents the reasoning supporting the determination.
Maintains the approved record
Coordinates entry of the approved information, version history and resolution of conflicting records.
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.
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.
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.
Trading partner data
Information identifying suppliers, customers, importers, exporters, declarants and representatives, where relevant to the customs process.
Product master data
Technical and commercial characteristics used to identify goods and support customs determinations throughout the product lifecycle.
Customs determinations
Customs-specific information derived from technical facts, commercial circumstances and applicable legal requirements.
Commercial transaction data
Information describing the underlying transaction and the commercial conditions relevant to the movement of goods.
Shipment and movement data
Information describing how goods are packed, transported and moved between locations and customs procedures.
Documents and customs records
Supporting information, declarations, communications and records used to demonstrate how a customs process was performed.
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.
A product changes. Which customs records need attention?
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.
Detect the change
The product team records the revised technical specification and identifies the affected item.
Assess customs impact
The customs specialist determines whether the changed characteristics require a new classification assessment or affect other customs information.
Approve the relevant record
Any revised determination is documented with its supporting reasoning and applicable effective date.
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.
EU customs context
The Union Customs Code establishes obligations concerning the accuracy and completeness of information in customs declarations, the authenticity and validity of supporting documents, and the keeping of relevant records. Internal data governance can support compliance, but does not replace the legal obligations of the relevant customs parties.
Regulation (EU) No 952/2013 — Articles 15, 51 and 162Customs 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.
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.
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.
Data creation standards
Define mandatory fields, accepted formats, reference values and minimum supporting information before a record can be used.
Authoritative source rules
Identify which source is authoritative for each data element and how conflicting information must be investigated.
Approval and modification rights
Establish which roles may propose, review, approve and implement changes to sensitive information.
Version and validity management
Preserve relevant historical values, effective dates and the relationship between a change and affected transactions.
Exception and correction procedures
Define how errors are reported, investigated, corrected and escalated, including the treatment of affected downstream records.
Retention and evidence management
Establish how relevant records, supporting documents and decision histories are retained, protected and made retrievable.
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.
Format and completeness
Verify required fields, permitted formats, data types and structural consistency.
Reference data integrity
Compare values with relevant reference datasets and assess their applicability at the relevant time.
Cross-field consistency
Identify contradictions between product, transaction, shipment and supporting information.
Customs-specific assessment
Refer matters requiring interpretation, judgement or supporting evidence to competent reviewers.
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.
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.
Propose
Record the proposed value, reason and supporting evidence.
Review impact
Identify affected systems, records and customs processes.
Approve or reject
Obtain the appropriate authorised decision.
Publish version
Update the governed record and relevant effective dates.
Reconcile
Confirm intended downstream updates and preserve the history.
The authorised version may be released to the designated downstream systems after the required implementation checks.
The proposed change remains separate from the approved value until the necessary review is completed.
The proposed value is not published. The reason for rejection and any required corrective action are recorded.
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.
Previously approved record
HISTORICALThe classification assessment was based on the product characteristics available when this version was approved.
Change under assessment
REVIEWA revised technical specification triggers an assessment of whether customs information needs to change.
New approved record, if required
CONDITIONALIf the review results in an approved update, the new version records the decision, effective date and downstream implementation.
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.
Identify affected records
Detect changes to critical fields and determine which products, transactions, interfaces or documents may be affected.
Publish approved values
Prevent pending or rejected updates from replacing approved values in systems that rely on them.
Verify downstream consistency
Compare the expected and actual values received by dependent systems and investigate differences.
Contain and correct errors
Define how failed updates are isolated, escalated, corrected and reprocessed without uncontrolled duplication.
An ERP commodity code is changed without customs approval.
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 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.
EU customs legislation and internal governance
The Union Customs Code establishes obligations concerning the accuracy and completeness of customs information, supporting documents and relevant records. The approval workflows, validation layers and versioning methods described here are illustrative internal governance practices, not a single mandatory technical model prescribed by the UCC.
Regulation (EU) No 952/2013 — Articles 15, 51 and 162Governed 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.
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.
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.
Critical field coverage
Monitor the proportion of relevant records containing the information required for their intended use.
Unresolved data issues
Track outstanding discrepancies, their age, assigned ownership and the operational processes potentially affected.
Change approval coverage
Identify sensitive data changes that were released without the required review or recorded authorisation.
Cross-system discrepancies
Detect differences between authoritative records and the values held in dependent operational systems.
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.
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.
Product specification
Technical characteristics supplied by the responsible business function.
Customs assessment
Specialist review of the relevant customs determination.
Approved customs data
Governed value with approval history and applicable validity.
Customs declaration
Information selected and used for a specific declaration.
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.
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.
What information was involved?
Identify the affected data element, product, party, transaction or document.
Where did it come from?
Preserve the relevant source, supporting document and acquisition context.
Who reviewed or approved it?
Record the responsible role, decision outcome and supporting rationale.
When was it valid and used?
Distinguish creation, modification, approval and relevant effective dates.
How was it changed?
Document material changes, mapping logic and relevant system transformations.
Where was it applied?
Connect the approved information to affected systems and customs transactions.
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.
| 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 |
A customs authority questions the classification used in a past declaration.
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.
Locate the transaction
Identify the declaration and the relevant product and supporting records.
Recover the historical version
Retrieve the product characteristics and customs data applicable to the transaction.
Reconstruct the assessment
Identify the reasoning, supporting evidence and relevant decisions.
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.
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.
Integrity
Protect relevant records against unauthorised alteration and preserve the reliability of historical evidence.
Retrievability
Ensure authorised personnel can locate and retrieve information needed for legitimate operational or legal purposes.
Retention rules
Apply the relevant customs record-keeping requirements while considering any other applicable legal obligations.
Access and protection
Restrict access appropriately, especially where records contain commercially sensitive or personal information.
Legal context: records, information and controls
The Union Customs Code provides the legal framework for relevant information obligations, keeping documents and records, and customs controls. In particular, Article 51 addresses the keeping of documents and other information, generally for at least three years, subject to applicable rules and circumstances. Article 48 concerns post-release controls.
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.
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.
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.
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.
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 regulationUCC 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 regulationUCC 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 regulationGeneral 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 regulationRegulatory distinction. The UCC and its supplementary legislation establish legal requirements, but they do not prescribe the complete internal data governance architecture described on this page. Ownership matrices, dashboards, approval workflows and data lineage models are organisational controls whose implementation should reflect actual business and legal requirements. Consult the applicable consolidated legal texts and amendments when assessing a specific case.
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.