Customs Explorer
⌕

Customs Explorer

Electronic customs declarations

EU DIGITAL CUSTOMS / DECLARATION SYSTEMS

Electronic Customs Declarations

How customs declarations are prepared, submitted, processed and monitored through electronic systems in the European Union.

Electronic declarations connect customs information, economic operators and customs authorities. Understanding their data requirements, processing stages and system dependencies is essential for reliable import, export and transit operations.

UCC Legal framework
Electronic Information exchange
EU + National System landscape
DECLARATION WORKFLOW
REFERENCE MODEL
01
Commercial & Customs Data Goods, parties, classification, value and origin
02
Declaration Preparation Procedure, data fields, supporting information
03
Electronic Submission Applicable customs system and authorised channel
04
Customs Processing Validation, controls and procedural decisions
Electronic Responses

Acknowledgements, references, statuses and procedural messages, as applicable.

Digital submission is one part of the customs process. Accurate data, correct procedures and appropriate supporting evidence remain essential.

DECLARATION FUNDAMENTALS

What Is an Electronic Customs Declaration?

An electronic customs declaration is a declaration lodged using electronic data-processing techniques to place goods under a customs procedure or, where applicable, to support other legally defined customs formalities. It communicates structured information required by the relevant customs legislation and system.

A Legal Declaration Expressed Through Structured Data

A customs declaration is not simply an electronic version of a commercial invoice. It identifies the relevant customs procedure and contains information needed for customs supervision, assessment and processing.

Electronic systems organise that information into defined data elements and messages. The exact requirements depend on the procedure, the applicable EU rules and the system through which the declaration is lodged.

Important distinction

Electronic submission does not remove the declarant’s legal responsibilities or guarantee that a declaration will be accepted or goods released.

DECLARATION INFORMATION MODEL Structured Customs Data
Parties Declarant, representative and relevant operators
Goods Description, classification, quantities and packages
Procedure Requested treatment and procedural references
Supporting Data Documents, authorisations and other required references

Import, Export and Transit Are Not the Same Workflow

Each process serves a different customs purpose. Its declaration requirements, message exchanges and processing stages must be considered separately.

01

Import Declarations

Used for placing goods under an applicable import customs procedure, such as release for free circulation.

Typical considerations
  • Tariff classification and customs value
  • Origin and applicable measures
  • Duties, taxes and supporting documents
02

Export Declarations

Used in the relevant circumstances for goods leaving the customs territory of the European Union.

Typical considerations
  • Export procedure and goods information
  • Restrictions and supporting references
  • Export and exit-related messages
03

Transit Declarations

Support the movement of goods under the applicable customs transit arrangements, subject to their specific conditions.

Typical considerations
  • Transit procedure and offices involved
  • Guarantee and movement references
  • Departure, movement and discharge processes

These categories are illustrative. Customs legislation provides additional procedures, special arrangements and declaration forms that require separate analysis.

Who Participates in the Declaration Process?

The legal roles must be distinguished from the software systems or service providers used to transmit information.

01

Declarant

The person lodging the customs declaration in their own name, or the person in whose name it is lodged, as defined by the UCC.

LEGAL ROLE
02

Customs Representative

A person appointed to carry out acts and formalities required under customs legislation in dealings with customs authorities. Representation may be direct or indirect.

LEGAL ROLE
03

Customs Authorities

The competent authorities responsible for applying customs legislation, processing declarations and performing relevant customs controls.

PUBLIC AUTHORITY
04

Software & Integration Providers

Technical service providers may support declaration preparation and electronic communication. Their technical role does not automatically make them the declarant or customs representative.

TECHNICAL ROLE
Electronic customs declarations combine legal responsibilities with structured digital processes.

The technology manages information exchange, but the underlying customs procedure determines what must be declared, by whom and under which conditions.

ELECTRONIC DECLARATION LIFECYCLE

From Declaration Preparation to Customs Release

An electronic customs declaration moves through a sequence of procedural and technical stages. Submission, acceptance, risk analysis, controls and release are distinct events, and their order and associated messages depend on the customs procedure and electronic system.

REFERENCE PROCESS Declaration Lifecycle

A simplified example of the principal stages of an electronic customs declaration.

  1. 01

    Data Preparation

    INTERNAL

    Commercial and logistics information is collected and checked. The appropriate customs procedure, required data elements and supporting references are identified.

    Typical inputs Goods information · Parties · Procedure · Classification · Value · Origin · Documents
  2. 02

    Electronic Submission

    TRANSMISSION

    The declaration is lodged through the applicable electronic customs system, using an authorised submission channel and the required message structure.

    Key distinction Successful technical transmission does not necessarily mean legal acceptance.
  3. 03

    Validation & Acceptance

    CUSTOMS SYSTEM

    The relevant system applies technical and procedural checks. Where the applicable conditions are met, the declaration may be accepted and a customs reference assigned in accordance with the system’s rules.

    Possible outcomes Acceptance · Rejection · Error notification · Request for correction or further action
  4. 04

    Risk Analysis & Customs Controls

    AUTHORITY

    Customs authorities may conduct risk analysis, examine documents, verify information or inspect goods. The extent and timing of controls depend on the relevant procedure and circumstances.

    Operational implication A declaration may require additional information or action before processing can continue.
  5. 05

    Release or Other Procedural Outcome

    DECISION

    When the legal conditions are satisfied, customs authorities may release the goods for the relevant procedure. Other outcomes are possible where the requirements have not been met.

    Important Acceptance and release are separate legal and operational events.
  6. 06

    Follow-up & Record Management

    POST-PROCESSING

    Relevant customs references, status messages, supporting documents and transaction records are retained and reconciled. Depending on the procedure, further steps may remain, including exit confirmation or transit discharge.

    Typical controls Status reconciliation · Evidence retention · Exception follow-up · Record traceability

What Happens When the Normal Flow Is Interrupted?

Electronic customs processing is not always linear. Errors, requests and controls can interrupt or redirect the process.

01

Technical Rejection

The submitted message fails an applicable technical validation or formatting requirement.

Operational response Investigate the error and follow the system’s permitted correction or resubmission procedure.
02

Missing or Inconsistent Information

Required information is incomplete, contradictory or otherwise unsuitable for the intended process.

Operational response Verify the underlying records and apply the relevant amendment, correction or follow-up procedure.
03

Customs Control or Additional Request

The authorities require further verification, documents or examination before the procedure can continue.

Operational response Coordinate the requested action, monitor the declaration and retain relevant supporting evidence.
DATA REQUIREMENTS & VALIDATION

Reliable Declarations Begin With Reliable Data

Electronic customs systems process structured information, but the quality of a declaration depends on the accuracy, consistency and legal relevance of its underlying data. Effective validation begins before the declaration is transmitted.

DECLARATION DATA

Six Areas That Require Particular Attention

The data elements required for a declaration depend on the customs procedure and applicable legal rules. The following groups illustrate information commonly relevant to electronic customs processing.

01 / PARTIES

Economic Operators

Declarant, representative, importer, exporter and other relevant parties, as required.

CHECK Identity, EORI and representation
02 / GOODS

Goods Identification

Commercial descriptions, commodity codes, quantities, net mass and packaging information.

CHECK Classification and item consistency
03 / VALUE

Customs Valuation

Value information and relevant adjustments according to the applicable customs valuation rules.

CHECK Currency, value basis and adjustments
04 / ORIGIN

Origin Information

Non-preferential origin and, where relevant, preferential origin claims and their supporting evidence.

CHECK Origin basis and documentary support
05 / PROCEDURE

Customs Procedure

Requested procedure, previous procedure and references to relevant authorisations or preceding customs operations.

CHECK Procedure eligibility and references
06 / EVIDENCE

Supporting Information

Required document references, certificates, licences, transport information and other procedure-specific supporting data.

CHECK Validity, availability and traceability
PRE-SUBMISSION CONTROLS

A Layered Validation Approach

A reliable declaration workflow should distinguish structural validation from substantive customs checks. Passing one type of validation does not establish compliance with every applicable requirement.

INPUT Prepared Declaration Dataset

Data collected from commercial documents, enterprise systems and customs records.

ERP Trade Data Documents
01

Structural Validation

Required fields, data types, message structure and applicable formatting rules.

TECHNICAL
02

Cross-Field Consistency

Relationships between quantities, values, parties, procedures and document references.

LOGICAL
03

Customs Rule Checks

Relevant procedural conditions, applicable measures and known declaration requirements.

REGULATORY
04

Document & Evidence Review

Availability and consistency of supporting evidence, including manual review where needed.

EVIDENCE
Ready for Submission

Defined pre-submission checks have passed. Transmission may proceed through the applicable channel.

Review Required

Missing, inconsistent or uncertain information must be investigated before proceeding.

This diagram illustrates internal quality controls, not a universal EU customs validation engine. Official system validation and customs authority decisions remain separate processes.

DATA QUALITY PRINCIPLES

What Makes Customs Data Operationally Reliable?

Technical correctness is only one dimension. Reliable customs data also needs a defensible source, clear ownership and a process for resolving inconsistencies.

01
Accuracy

Information reflects the actual goods, transaction and applicable customs facts.

02
Completeness

Required information is available for the intended procedure and declaration type.

03
Consistency

Data remains coherent across invoices, transport records, ERP systems and declarations.

04
Traceability

Key information can be linked to its source and relevant supporting evidence.

05
Accountability

Responsibilities for data creation, approval and correction are clearly assigned.

COMMON VALIDATION FAILURES

Errors That Software Alone Cannot Always Resolve

01 Incorrect Classification

A commodity code may be technically valid but inappropriate for the actual goods.

02 Unsupported Origin Claims

An origin statement may be present without sufficient evidence for the treatment being claimed.

03 Valuation Inconsistencies

Invoice amounts, adjustments and declared customs values may not be correctly reconciled.

04 Procedure Mismatch

The selected procedure may not match the transaction or the conditions applicable to the goods.

EU Legal Framework for Declaration Data

Article 162 of the Union Customs Code addresses the particulars required in a standard customs declaration. The detailed data requirements are established through the applicable UCC framework, including the relevant annexes and amendments to the Delegated and Implementing Acts.

SYSTEMS & INTEROPERABILITY

Connecting Business Data to Customs Systems

Electronic customs declarations depend on more than a submission interface. A reliable operational architecture connects business information, declaration preparation, authorised communication channels and customs system responses.

REFERENCE ARCHITECTURE

From Enterprise Systems to Customs Authorities

A conceptual architecture for an economic operator using electronic customs declaration services. Actual implementations vary by Member State, procedure and system.

CONCEPTUAL MODEL
LAYER 01

Enterprise Data Sources

Business systems and operational records

ERP Invoices Inventory Transport Data
LAYER 02

Customs Application Layer

Declaration preparation and workflow management

Data Validation Procedure Rules Message Generation Audit Records
LAYER 03

Customs Electronic Interface

Applicable national or EU electronic system

Authentication Message Exchange System Validation Response Handling
LAYER 04

Customs Authority Processing

Declaration assessment and procedural decisions

Acceptance Risk Analysis Controls Release / Outcome
EU CUSTOMS SYSTEM LANDSCAPE

Different Procedures Use Different Electronic Systems

EU customs digitalisation includes interconnected national and trans-European systems. Their functions are not interchangeable, and access arrangements depend on the relevant implementation.

System Primary Function Operational Consideration
National Import Systems Processing import declarations under applicable procedures National technical specifications and access requirements
AESAutomated Export System Electronic export processes and related exchanges National implementation and relevant export/exit messages
NCTSNew Computerised Transit System Electronic management of applicable transit operations Transit-specific rules, guarantees and movement messages
ICS2Import Control System 2 Entry summary declaration data and pre-arrival safety and security risk analysis Separate obligations from the customs declaration for release for free circulation
CDSCustoms Decisions System Management of applications and decisions for covered customs authorisations Authorisation workflow, not a general goods declaration channel

System availability, versions, national interfaces and technical specifications should be checked with the competent customs administration before implementation.

INTEGRATION APPROACHES

Three Practical Operating Models

Companies can organise electronic customs processes in different ways. The appropriate model depends on declaration volumes, internal expertise, system access and operational responsibilities.

MODEL 01

Manual Portal Submission

An authorised user prepares and lodges declarations through an available customs portal or supported user interface.

Typical fit Lower volumes, limited integration needs or procedures supported by an accessible portal.
MODEL 03

Representative-Managed Process

A customs representative handles relevant declaration formalities, while the company supplies the required information and supporting records.

Typical fit Outsourced declaration operations with defined responsibilities, data exchanges and reporting.
IMPLEMENTATION FEASIBILITY

Verify External Dependencies Before Building

A functioning declaration application requires more than generating a technically valid message. Several external conditions must be verified before software development is committed.

01

System Access

Confirm who may connect, which identities and registrations are required, and whether direct machine-to-machine access is available.

02

Technical Specifications

Obtain the applicable message formats, interface documentation, validation rules and supported communication protocols.

03

Testing & Onboarding

Verify the existence and conditions of test environments, conformity testing, certification or other onboarding requirements.

04

Legal & Operational Roles

Define who acts as declarant or representative, who controls credentials, and who is responsible for corrections, monitoring and records.

05

Ongoing Maintenance

Plan for changing message specifications, regulatory requirements, system versions and operational support.

Interoperability is an operational capability, not merely a technical connection.

Successful integration requires reliable source data, legally appropriate declaration logic, permitted system access and continuous reconciliation of customs responses.

EU FRAMEWORK & OFFICIAL RESOURCES

The Legal Framework Behind Electronic Customs Declarations

Electronic customs declarations operate within the Union Customs Code framework. EU legislation establishes the underlying customs obligations, while the applicable electronic systems implement procedure-specific data, communication and processing requirements.

LEGAL & OPERATIONAL DISTINCTIONS

Four Principles Worth Remembering

01

Electronic Communication Is the General Rule

Article 6 UCC establishes the general use of electronic data-processing techniques for exchanges and storage of information required under customs legislation, subject to the exceptions and arrangements provided by law.

02

Data Requirements Depend on the Procedure

Import, export, transit and special procedures do not necessarily require identical data elements or electronic messages. The applicable legal and technical specifications determine the relevant dataset.

03

Acceptance Is Not the Same as Release

A declaration may be accepted before the authorities complete verification or decide whether the conditions for release are met. These events must be tracked separately.

04

Technical Access Must Be Confirmed

EU legal harmonisation does not mean that every customs system offers a single public API or identical access conditions. National implementation and onboarding requirements remain relevant.

OFFICIAL INFORMATION

Where to Verify Customs Requirements

Use official EU and national sources to confirm legislation, system documentation and implementation arrangements.

For national declaration interfaces, credentials, software connectivity and test environments, consult the customs administration of the Member State responsible for the relevant operation.

CONTINUE EXPLORING

Understand the Wider Digital Customs Landscape

Explore how electronic declarations connect with customs data management, digital workflows, interoperability and the broader transformation of EU customs operations.

Explore Digital Customs Explained