Customs Explorer
⌕

Customs Explorer

Trust & Check data access

EU CUSTOMS REFORM / DIGITAL TRUST

Trust & Check Data Access.

Customs transparency starts inside your systems.

Trust & Check changes how authorised businesses demonstrate customs compliance. Instead of relying solely on information submitted at individual stages, the framework requires electronic access to relevant operational and compliance data.

The central requirement: provide or make available data on goods movements and regulatory compliance as close to real time as technically possible.

ARTICLE 31(3)(f)
DATA VISIBILITY MODEL
CONCEPTUAL / NOT A TECHNICAL SPECIFICATION
TRADER ENVIRONMENT Operational data sources
ERP & accounting Commercial and financial records
Logistics & tracking Movements, status and location
Customs & compliance Records, licences and authorisations
RELEVANT DATA MADE AVAILABLE
EU DIGITAL CUSTOMS FRAMEWORK EU Customs Data Hub Relevant data access via the Hub where applicable
COMPETENT AUTHORITIES Customs supervision & verification
CONTROL
THE DATA ACCESS PRINCIPLE Four connected requirements
01 Electronic systems Reliable digital information
02 Timely availability As close to real time as technically possible
03 Compliance evidence Records supporting regulatory verification
04 Customs oversight Access within the applicable legal framework

Legal foundation: Regulation (EU) 2026/2108, Article 31(3)(d) and (f). Technical implementation and applicable dates must be assessed separately.

Official EU regulation
01 / DATA ACCESS REQUIREMENTS

Five data categories. One transparent customs operation.

Article 31(3)(f) identifies five categories of business information that must be made available to customs authorities via the EU Customs Data Hub where relevant. Together, they help customs verify the movement of goods and compliance with applicable requirements.

ARTICLE 31(3)(f)
FIVE LEGALLY IDENTIFIED CATEGORIES
TRADER INFORMATION ENVIRONMENT

Connected evidence, not isolated documents.

Customs must be able to assess whether commercial transactions, goods movements and regulatory records are consistent. The five categories below represent different sources of that evidence.

01
ARTICLE 31(3)(f)(i) CUSTOMS

Customs records

Customs records, including information necessary to check whether the customs debt has been correctly established.

ILLUSTRATIVE RECORDS
Tariff classification Customs value Origin information Duty calculations
02
ARTICLE 31(3)(f)(ii) FINANCIAL

Accounting system

The accounting system used by the trader, providing a basis for examining financial records relevant to customs operations.

ILLUSTRATIVE INFORMATION
Purchase entries Sales entries Supplier invoices Reconciliation records
03
ARTICLE 31(3)(f)(iii) TRANSACTIONAL

Commercial and transport records

Commercial documentation and transport records supporting the identification and verification of the underlying transaction.

ILLUSTRATIVE DOCUMENTS
Commercial invoices Packing lists Transport documents Purchase orders
04
ARTICLE 31(3)(f)(iv) LOGISTICS

Tracking and logistics systems

Systems identifying goods as Union or non-Union goods and indicating their location where appropriate.

ILLUSTRATIVE DATA
Goods status Warehouse movements Shipment tracking Goods location
05
ARTICLE 31(3)(f)(v) REGULATORY

Licences and authorisations

Licences and authorisations granted under other legislation applied by customs authorities, where relevant to the goods and operations.

ILLUSTRATIVE RECORDS
Import licences Export licences Regulatory permits Validity information
WHERE RELEVANT EU Customs Data Hub

Relevant information made available to customs authorities within the applicable legal and technical framework.

PRACTICAL EXAMPLE

One shipment. Five possible sources of evidence.

Consider an imported machine component. Different business records may help customs verify that the transaction, movement and regulatory treatment are consistent.

ILLUSTRATIVE SHIPMENT Imported component Single commercial transaction
01Customs value and tariff data
02Accounting entry
03Invoice and transport document
04Goods status and location
05Applicable licence, if required
Customs verification

Consistency can be assessed across relevant information sources.

Why this matters

A customs record may be accurate in isolation while conflicting with an invoice, warehouse movement or regulatory document. Connected information can make those inconsistencies easier to identify and investigate.

ACCESS IS NOT UNLIMITED

What “where relevant” means for the data-access model.

Relevant information

The requirement concerns information connected with goods movements and compliance with applicable obligations.

Proportionate access

Recital 18 frames access to electronic systems as proportionate and strictly necessary for customs transparency.

Technical implementation

The regulation establishes the legal requirement; it does not prescribe a universal ERP product, API architecture or database configuration.

02 / TIMELINESS & DATA RELIABILITY

Near-real-time access. Reliable information.

The value of digital customs transparency depends on information being available when it is relevant, reflecting the actual movement and regulatory status of goods.

THE LEGAL STANDARD As close to real time as technically possible REGULATION (EU) 2026/2108 · ARTICLE 31(3)(f)
OPERATIONAL DATA FLOW
ILLUSTRATIVE SYSTEM MODEL
FROM BUSINESS EVENT TO CUSTOMS VISIBILITY

Data must remain useful as operations change.

The sequence below illustrates a possible information-management process. It is not a legally prescribed workflow or a technical specification for the EU Customs Data Hub.

01 / EVENT

Goods movement

A relevant event occurs: goods arrive, move, change location or enter a different operational stage.

PHYSICAL OPERATION
02 / RECORD

System update

Relevant business records reflect the event, including goods identity, status and location where applicable.

TRADER SYSTEM
03 / AVAILABILITY

Data made available

The relevant information is provided or made available to customs as close to real time as technically possible.

LEGAL TIMELINESS STANDARD
04 / SUPERVISION

Customs verification

Customs authorities can use relevant information to support supervision and compliance checks.

AUTHORITY FUNCTION
Timeliness is a capability requirement.

Article 31(3)(f) does not impose one identical technical delay on every operator, system or category of information.

THREE DISTINCT DIMENSIONS

Timeliness, accuracy and accessibility are not interchangeable.

A system may deliver information quickly while still containing incorrect records. Conversely, accurate records may lose operational value if they become available too late for a relevant customs check.

01

Timeliness

Relevant data should be provided or made available as close to real time as technically possible.

EXPRESS LEGAL CRITERION ARTICLE 31(3)(f)
02

Data quality

Records need to be sufficiently accurate, consistent and traceable to support meaningful compliance verification.

OPERATIONAL CONTROL OBJECTIVE SUPPORTS VERIFIABILITY
03

Accessibility

The relevant information must be capable of being provided or made available to customs within the applicable legal and technical arrangements.

EXPRESS LEGAL CRITERION ARTICLE 31(3)(f)
PRACTICAL DISTINCTION

What the regulation says — and what it does not specify.

✓ EXPRESSLY PROVIDED
Electronic system

The applicant must have a system providing or making available relevant data to customs.

Near-real-time standard

Data availability must be as close to real time as technically possible.

Relevant data categories

Article 31(3)(f) identifies customs, accounting, commercial, logistics and authorisation information.

— NOT FIXED BY ARTICLE 31(3)(f)
A universal latency in seconds

The provision does not establish a fixed number of seconds or minutes for every data update.

A mandatory software vendor

It does not require businesses to purchase one named ERP, tracking or compliance platform.

One prescribed integration architecture

It does not itself specify a universal API endpoint, data schema or synchronisation method.

Further technical requirements may be established through applicable implementing measures, specifications and authorisation arrangements. The absence of a detail in Article 31(3)(f) should not be interpreted as proof that no additional requirement can apply.

PRACTICAL READINESS

Four questions to test your data environment.

These are suggested internal assessment questions, not a statutory checklist or a substitute for an authorisation assessment.

01 / EVENT CAPTURE

When does the system learn that goods have moved?

Identify whether physical events are recorded promptly or only during later manual reconciliation.

02 / RECORD CONSISTENCY

Can customs and commercial records be reconciled?

Examine whether goods references, quantities and relevant transactions can be linked across systems.

03 / DATA AVAILABILITY

Can relevant information be retrieved reliably?

Consider how records remain available during ordinary operations, interruptions and system changes.

04 / ERROR HANDLING

Can missing or incorrect data be identified and corrected?

Evaluate practical procedures for detecting discrepancies, correcting records and retaining an understandable audit trail.

03 / BUSINESS SYSTEM INTEGRATION

Your business systems. One verifiable data environment.

Trust & Check data access is not simply a matter of installing new software. Businesses need to understand where relevant information originates, how it moves between systems and how it can be made available for customs supervision.

CONCEPTUAL INTEGRATION ARCHITECTURE
ILLUSTRATIVE — NOT AN EU TECHNICAL SPECIFICATION
DATA ORIGINATION → VALIDATION → AVAILABILITY

Connecting operational reality to customs visibility.

A trader may use several internal platforms. The objective is to make relevant data identifiable, consistent and accessible through arrangements meeting the applicable legal and technical requirements.

01 BUSINESS SYSTEMS
ERP
Enterprise systems Transactions, invoices, accounting
WMS
Warehouse management Stock, locations, goods movements
TMS
Transport management Shipments, tracking, transport events
GRC
Compliance records Authorisations, licences, controls
02 INTEGRATION & CONTROL
POSSIBLE TECHNICAL LAYER

Data integration

Connect, organise and prepare relevant business information for lawful availability.

01 Data mapping
02 Consistency checks
03 Access controls
04 Error handling
This layer may be implemented in different ways or partly within existing systems.
03 CUSTOMS DATA ACCESS
EU CUSTOMS FRAMEWORK

EU Customs Data Hub

Relevant information made available via the Hub where applicable, under the governing legal and technical arrangements.

◎
COMPETENT AUTHORITIES Customs supervision
ACCESS SCOPE DEPENDS ON APPLICABLE REQUIREMENTS
i

Important: the diagram illustrates a possible architecture. Article 31(3)(f) does not require a particular ERP, WMS, TMS, middleware product, API protocol or direct connection design. Actual implementation must follow applicable technical specifications and authorisation conditions.

SYSTEM DESIGN PRINCIPLES

Five building blocks of a dependable integration.

These are recommended technical design considerations. They are not five additional statutory criteria under Article 31(3)(f).

01 / IDENTIFICATION ⌗

Data mapping

Identify which system contains each relevant item of information and how records relate to the same goods, shipment or transaction.

02 / CONSISTENCY ≡

Data validation

Compare relevant fields across systems. Differences in quantities, goods status or transaction references may require investigation before information is relied upon.

RECONCILIATION & ACCURACY
03 / AVAILABILITY ◷

Timely updates

Assess how quickly relevant operational changes become available and whether the system can meet the legal standard as close to real time as technically possible.

TIMELINESS & TECHNICAL FEASIBILITY
04 / PROTECTION ◇

Controlled access

Design appropriate authentication, permissions and security measures so that access to relevant records remains controlled and traceable.

SECURITY & ACCOUNTABILITY
05 / RESILIENCE ↻

Exception management

Prepare for missing records, inconsistent information, connection failures and correction procedures without losing the ability to explain what happened.

ERRORS & RECOVERY
IMPLEMENTATION OPTIONS

Different companies may need different solutions.

The appropriate design depends on the trader’s existing systems, business model, transaction volumes and applicable technical requirements.

A

Existing ERP capabilities

Relevant data may already be available through built-in reporting, integration or data-management functions.

ASSESS EXISTING CAPABILITIES FIRST
B

Integration middleware

A separate integration layer may help connect multiple applications and manage transformations, controls and availability.

USEFUL FOR MULTI-SYSTEM ENVIRONMENTS
C

Custom technical development

Bespoke interfaces may be considered where standard capabilities do not meet operational or applicable technical requirements.

REQUIRES ONGOING MAINTENANCE
!
Do not design against assumptions.

A conceptual integration model is not sufficient to establish EU Customs Data Hub compatibility. Before investing in development, verify the available technical specifications, connection arrangements, implementation dates and applicable authorisation requirements.

INTERNAL SYSTEM ASSESSMENT

Where could integration fail?

Four practical questions can reveal significant weaknesses before a technical project begins.

01 Fragmented records

Can a single goods movement be traced across purchasing, warehouse, transport and customs records?

02 Manual dependencies

Which relevant updates depend on spreadsheets, emails or manual re-entry into another system?

03 Unavailable information

What happens when a source system, interface or external service becomes temporarily unavailable?

04 Unclear responsibility

Who identifies, investigates and corrects a discrepancy between operational and customs data?

04 / SECURITY, CONFIDENTIALITY & ACCOUNTABILITY

Transparent to customs. Protected by design.

The Trust & Check model depends on access to relevant business information. That access must operate within the applicable legal framework, while businesses continue to protect the integrity and confidentiality of their systems.

THE CENTRAL DISTINCTION Data visibility is not unrestricted access.

Customs supervision, information security and commercial confidentiality are separate considerations that must be addressed together.

CONTROLLED DATA ACCESS
CONCEPTUAL SECURITY MODEL
LEGAL ACCESS / TECHNICAL PROTECTION

Access should be governed, not improvised.

The diagram illustrates how relevant information may be made available while retaining technical safeguards. It is not a prescribed EU Customs Data Hub architecture.

TRADER ENVIRONMENT
▦ Commercial records
▤ Customs information
⌖ Logistics data
◇ Regulatory evidence

Relevant business information originates from operational systems.

CONTROL LAYER

Governed availability

01 Defined access scope
02 Identity & permissions
03 Data integrity checks
04 Access traceability
Illustrative safeguards, subject to applicable technical and legal requirements
CUSTOMS FRAMEWORK

EU Customs Data Hub

Relevant information made available via the Hub where applicable.

◎
COMPETENT AUTHORITIES Lawful customs supervision
i

Interpretation: the access-control layer is a conceptual security measure. The regulation does not prescribe this particular technical arrangement, nor does it grant traders a unilateral right to restrict information that they are legally required to provide or make available.

THREE CONNECTED RESPONSIBILITIES

Access, protection and accountability.

A credible data-access model must distinguish what the law requires from the measures a company adopts to manage technical and organisational risks.

01 / CUSTOMS ACCESS
◎

Lawful availability

Article 31(3)(f) requires the trader’s electronic system to provide or make available relevant data to customs, as close to real time as technically possible.

EXPRESS TRUST & CHECK CRITERION ARTICLE 31(3)(f)
02 / INFORMATION PROTECTION
◇

Confidentiality & security

Customs-related information may include commercially sensitive records and, in some circumstances, personal data. Applicable confidentiality and data-protection rules remain relevant.

APPLICABLE LEGAL FRAMEWORK DATA PROTECTION & CONFIDENTIALITY
03 / BUSINESS GOVERNANCE
▣

Operational accountability

Internal ownership of data, correction processes and security responsibilities helps the trader maintain reliable records and respond to discrepancies.

RECOMMENDED MANAGEMENT PRACTICE INTERNAL CONTROL DESIGN
CONFIDENTIAL INFORMATION

Business transparency does not make information public.

Data made available for customs supervision can contain information that a company would not ordinarily disclose to competitors, customers or the general public.

01
Commercial terms

Prices, supplier arrangements, purchasing conditions and transaction information.

02
Supply-chain information

Suppliers, logistics routes, warehouse locations and movement records.

03
Financial records

Accounting information and records relevant to the verification of customs operations.

04
Personal information

Identifiable individuals may appear in some commercial, transport or administrative records.

RECOMMENDED TECHNICAL SAFEGUARDS

Six controls worth evaluating.

The following measures are examples of good system governance. Their precise necessity and configuration depend on the applicable requirements and the trader’s risk environment.

01

Identity management

Establish how users and connected services are authenticated.

02

Access permissions

Define and review appropriate permissions for internal users and integrations.

03

Transmission protection

Assess appropriate technical safeguards for information exchanged between systems.

04

Audit logging

Maintain suitable records of relevant system activity and data changes.

05

Incident procedures

Prepare responses to unauthorised access, data corruption and system outages.

06

Supplier governance

Assess the responsibilities of external software providers and integration partners.

!

Not a mandatory technical checklist. These safeguards are suggested design considerations. They should not be presented as six individually prescribed conditions of Trust & Check authorisation under Article 31(3)(f).

ORGANISATIONAL RESPONSIBILITY

Who is responsible when the data is wrong?

Technology can expose inconsistencies, but it cannot independently determine every legal consequence or correct every underlying commercial record.

DATA OWNERSHIP

Know who maintains each record.

Identify the business function responsible for the accuracy of customs, accounting, logistics and regulatory information.

DISCREPANCY HANDLING

Define a correction process.

Establish how conflicting, incomplete or outdated information is investigated and corrected.

CONTINUOUS OVERSIGHT

Monitor the control environment.

Review significant system changes, recurring errors and access arrangements as the business evolves.

05 / QUESTIONS, LAW & NEXT STEPS

Trust & Check data access. The questions that matter.

Understand the practical meaning of electronic data availability, the limits of technical assumptions and the legal framework behind the Trust & Check model.

LEGAL FOUNDATION Article 31(3)(f) Regulation (EU) 2026/2108

Electronic access is an authorisation criterion, not a prescribed software product.

FREQUENTLY ASKED QUESTIONS

Eight essential answers.

Based on the adopted legal framework. Technical examples are identified as implementation considerations, not statutory specifications.

01 Must customs have direct access to our ERP?

Article 31(3)(f) requires an electronic system that provides or makes available relevant data to customs. It does not name a particular ERP or prescribe one direct-connection architecture.

The actual arrangements must satisfy applicable technical rules and authorisation conditions. Businesses should not assume that an ordinary ERP export function is automatically sufficient.

02 Does the regulation require real-time data?

The legal standard is availability as close to real time as technically possible. This wording is important: it is not a universal requirement for an instantaneous update of every record in every business system.

The trader must nevertheless be able to demonstrate that its electronic arrangements meet the applicable standard. Technical limitations should not be treated as an automatic exemption.

03 Which categories of data are identified?

Article 31(3)(f) identifies, where relevant, five categories of information to be made available via the EU Customs Data Hub:

  1. Customs records, including information needed to check the customs debt.
  2. The accounting system used.
  3. Commercial and transport records.
  4. Tracking and logistics systems identifying the customs status and, where appropriate, location of goods.
  5. Licences and authorisations granted under other legislation applied by customs.

These categories are part of a wider criterion covering goods movements and compliance with requirements applicable to the goods.

04 Does customs access make business data public?

No. Making relevant information available to competent authorities is different from publishing that information.

Article 23 of Regulation (EU) 2026/2108 addresses confidentiality. Applicable data-protection rules also remain relevant where personal data are processed. Confidentiality is not, however, an absolute bar to disclosures authorised or required by law.

05 Is an API or middleware platform mandatory?

Article 31(3)(f) does not prescribe a specific API product, middleware vendor or integration architecture.

Such technologies may be useful for connecting ERP, warehouse, transport and compliance systems. Any proposed solution must be assessed against the technical arrangements actually applicable to the EU Customs Data Hub.

06 Why are three years of historical data relevant?

Article 31(2) provides for customs authorities to have access to the applicant’s relevant data for the preceding three years when assessing compliance with the authorisation criteria.

This assessment requirement should not be confused with the separate electronic-system criterion under Article 31(3)(f), or interpreted as a standalone technical data-retention specification.

07 Can a company use several separate systems?

The provision does not require every relevant business record to originate in a single software application.

An organisation may need to connect or coordinate information held in several systems. What matters for authorisation is whether its overall arrangements satisfy the applicable legal and technical requirements.

08 Can an existing AEO automatically meet these requirements?

Existing AEO experience may provide a useful foundation in record management, internal controls and customs compliance.

It should not be treated as automatic proof that the distinct Trust & Check data-access criterion has been satisfied. The relevant authorisation requirements still need to be assessed.

Explore the transition from AEO
PRIMARY LEGAL FRAMEWORK

Read the rules behind the model.

These references distinguish the authorisation criterion, the confidentiality framework and personal-data protection.

PRIMARY SOURCE 01

Regulation (EU) 2026/2108

Article 31 — Trust & Check authorisation

Paragraph 3(f) establishes the electronic data-access criterion. Paragraph 2 addresses the examination of historical data during authorisation. Other parts of Article 31 govern monitoring and the status itself.

Read the official regulation
CONFIDENTIALITY 02

Article 23

Regulation (EU) 2026/2108

Addresses the treatment of confidential information within the customs framework, including relevant rules and exceptions concerning disclosure and protection.

View legal text
PERSONAL DATA 03

EU data-protection rules

Regulations (EU) 2016/679 and 2018/1725

Relevant where personal information is processed. The applicable regime depends on the processing activity and the organisation responsible for it.

THE PRACTICAL CONCLUSION

Three things to establish before investing in integration.

01

Know your data

Identify relevant records, source systems, data owners and gaps in information quality.

02

Know the legal scope

Distinguish the data-access criterion from broader authorisation and monitoring obligations.

03

Verify technical requirements

Check applicable specifications and implementation arrangements before committing to a software architecture.

END OF GUIDE / TRUST & CHECK DATA ACCESS

This guide explains the regulatory framework and possible implementation considerations. Illustrative technical arrangements do not replace official specifications or individual authorisation requirements.

Return to Trust & Check overview