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.
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.
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.
Electronic submission does not remove the declarant’s legal responsibilities or guarantee that a declaration will be accepted or goods released.
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.
Import Declarations
Used for placing goods under an applicable import customs procedure, such as release for free circulation.
- Tariff classification and customs value
- Origin and applicable measures
- Duties, taxes and supporting documents
Export Declarations
Used in the relevant circumstances for goods leaving the customs territory of the European Union.
- Export procedure and goods information
- Restrictions and supporting references
- Export and exit-related messages
Transit Declarations
Support the movement of goods under the applicable customs transit arrangements, subject to their specific conditions.
- 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.
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.
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.
Customs Authorities
The competent authorities responsible for applying customs legislation, processing declarations and performing relevant customs controls.
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.
The technology manages information exchange, but the underlying customs procedure determines what must be declared, by whom and under which conditions.
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.
A simplified example of the principal stages of an electronic customs declaration.
-
01
Data Preparation
INTERNALCommercial 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 -
02
Electronic Submission
TRANSMISSIONThe 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. -
03
Validation & Acceptance
CUSTOMS SYSTEMThe 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 -
04
Risk Analysis & Customs Controls
AUTHORITYCustoms 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. -
05
Release or Other Procedural Outcome
DECISIONWhen 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. -
06
Follow-up & Record Management
POST-PROCESSINGRelevant 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.
Technical Rejection
The submitted message fails an applicable technical validation or formatting requirement.
Missing or Inconsistent Information
Required information is incomplete, contradictory or otherwise unsuitable for the intended process.
Customs Control or Additional Request
The authorities require further verification, documents or examination before the procedure can continue.
The UCC addresses acceptance of customs declarations in Article 172, verification in Articles 188–194 and release of goods in Articles 194–195. The applicable conditions and procedural rules must be considered in each case.
Union Customs Code — Regulation (EU) No 952/2013Reliable 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.
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.
Economic Operators
Declarant, representative, importer, exporter and other relevant parties, as required.
Goods Identification
Commercial descriptions, commodity codes, quantities, net mass and packaging information.
Customs Valuation
Value information and relevant adjustments according to the applicable customs valuation rules.
Origin Information
Non-preferential origin and, where relevant, preferential origin claims and their supporting evidence.
Customs Procedure
Requested procedure, previous procedure and references to relevant authorisations or preceding customs operations.
Supporting Information
Required document references, certificates, licences, transport information and other procedure-specific supporting data.
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.
Data collected from commercial documents, enterprise systems and customs records.
Structural Validation
Required fields, data types, message structure and applicable formatting rules.
Cross-Field Consistency
Relationships between quantities, values, parties, procedures and document references.
Customs Rule Checks
Relevant procedural conditions, applicable measures and known declaration requirements.
Document & Evidence Review
Availability and consistency of supporting evidence, including manual review where needed.
Defined pre-submission checks have passed. Transmission may proceed through the applicable channel.
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.
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.
Information reflects the actual goods, transaction and applicable customs facts.
Required information is available for the intended procedure and declaration type.
Data remains coherent across invoices, transport records, ERP systems and declarations.
Key information can be linked to its source and relevant supporting evidence.
Responsibilities for data creation, approval and correction are clearly assigned.
Errors That Software Alone Cannot Always Resolve
A commodity code may be technically valid but inappropriate for the actual goods.
An origin statement may be present without sufficient evidence for the treatment being claimed.
Invoice amounts, adjustments and declared customs values may not be correctly reconciled.
The selected procedure may not match the transaction or the conditions applicable to the goods.
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.
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.
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.
Enterprise Data Sources
Business systems and operational records
Customs Application Layer
Declaration preparation and workflow management
Customs Electronic Interface
Applicable national or EU electronic system
Customs Authority Processing
Declaration assessment and procedural decisions
System acknowledgements, declaration references, status messages and procedural outcomes must be linked back to the original business transaction.
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.
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.
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.Customs Software Integration
A dedicated customs application manages declaration preparation, validation, electronic messages and response monitoring.
Typical fit Recurring declaration volumes and requirements for structured workflows or ERP integration.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.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.
System Access
Confirm who may connect, which identities and registrations are required, and whether direct machine-to-machine access is available.
Technical Specifications
Obtain the applicable message formats, interface documentation, validation rules and supported communication protocols.
Testing & Onboarding
Verify the existence and conditions of test environments, conformity testing, certification or other onboarding requirements.
Legal & Operational Roles
Define who acts as declarant or representative, who controls credentials, and who is responsible for corrections, monitoring and records.
Ongoing Maintenance
Plan for changing message specifications, regulatory requirements, system versions and operational support.
Successful integration requires reliable source data, legally appropriate declaration logic, permitted system access and continuous reconciliation of customs responses.
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.
Three Core EU Regulations
These regulations provide the principal legal foundation for EU customs declarations. The consolidated texts and subsequent amendments should be consulted for current requirements.
Union Customs Code
Establishes the core customs rules, including electronic information exchange, customs declarations, acceptance, verification and release of goods.
UCC Delegated Regulation
Supplements the UCC with detailed provisions covering customs procedures, declaration requirements and relevant data elements.
UCC Implementing Regulation
Establishes implementing rules for the application of the UCC, including procedural and data-related requirements.
Four Principles Worth Remembering
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.
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.
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.
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.
Where to Verify Customs Requirements
Use official EU and national sources to confirm legislation, system documentation and implementation arrangements.
EU customs policy, legislation, procedures and information on electronic customs systems.
Official access to EU legal acts, amendments and consolidated regulatory texts.
European Commission information on customs digitalisation, programmes and EU initiatives.
For national declaration interfaces, credentials, software connectivity and test environments, consult the customs administration of the Member State responsible for the relevant operation.
Return to the Key Topics
Navigate directly to the main sections of this guide for a closer examination of electronic customs declarations.
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