Customs
Declaration API.
Connecting customs declaration workflows with business software and authorised electronic submission channels.
Customs declaration integrations can support the preparation, validation, transmission and monitoring of declaration data. The technical connection depends on the relevant customs system, its supported interfaces and applicable access conditions.
Important: A customs declaration API is not a single, universally available EU interface. Integration options and submission requirements must be verified for each relevant customs system.
From Business Data
to Customs Decisions.
A customs declaration integration connects business information with the software and electronic channels used to prepare, submit and monitor customs declarations.
The workflow depends on the customs procedure, the competent customs administration and the technical specifications of the relevant system. The stages below illustrate a common integration pattern, not a universal EU message sequence.
Collect Source Data
Retrieve relevant information from ERP, logistics, inventory and trade records, including goods, parties, values and supporting documents.
BUSINESS SYSTEMSMap Declaration Fields
Transform source information into the data elements, structures and code values required by the applicable declaration system and procedure.
DATA TRANSFORMATIONValidate & Prepare
Check required fields, formats, relationships and known business rules. Resolve detected issues before transmission where possible.
PRE-SUBMISSION CHECKSSubmit Through a Supported Channel
Exchange the declaration message through an interface supported by the relevant system, subject to applicable access conditions.
AUTHORISED EXCHANGEProcess Responses
Interpret acknowledgements, errors, acceptance information, references and subsequent customs decisions as supported by the system.
STATUS & RECONCILIATION
Submission is only
one part of the process.
A declaration integration should be designed for two-way information exchange. Sending a message is not enough: subsequent responses must be interpreted and associated with the correct business transaction.
Depending on the system and procedure, responses may include validation failures, acceptance information, a declaration reference, control-related events, release information or other status changes.
Link system messages to the originating declaration record.
Record meaningful changes without treating every response as final.
Reconcile timeouts and missing responses before attempting resubmission.
Not Every Successful Message
Means Customs Release.
Technical delivery, legal acceptance and release of goods are different events. Integration software must preserve those distinctions.
Message Received
The destination interface may confirm that a message has been received or processed at a technical level.
Does not necessarily mean: Declaration acceptedDeclaration Accepted
Acceptance occurs under the applicable customs rules after the relevant requirements have been satisfied. An MRN may be communicated as part of the system’s processing.
Does not necessarily mean: Goods releasedGoods Released
Release is a separate customs decision allowing the goods to be made available for the purposes of the procedure concerned, subject to the relevant rules.
Integration requirement: Recognise the relevant release outcomeThe Union Customs Code distinguishes acceptance of a customs declaration from release of goods. Relevant provisions include Articles 172 and 194 of Regulation (EU) No 952/2013. The timing, message identifiers and status terminology depend on the applicable system.
Read the Union Customs Code
Accurate Data.
Reliable Declarations.
A customs declaration is built from structured information about the goods, the parties, the customs procedure and the underlying commercial transaction.
Digital integration can collect and transform this information, but it cannot automatically guarantee that the underlying customs determinations are legally correct. Data requirements vary according to the declaration type, procedure, applicable legislation and destination system.
Economic Operators & Parties
Information identifying the relevant parties and their roles in the customs operation.
- Declarant and representative details
- Relevant EORI identifiers
- Consignor and consignee information
- Other required party references
Goods & Classification
Information describing the goods and supporting their identification under the relevant customs nomenclature.
- Goods descriptions
- Commodity classification codes
- Net mass and other required quantities
- Packages and item-level information
Origin & Trade Measures
Information used to determine the applicable origin treatment and relevant trade measures.
- Country of origin
- Preferential origin claims, where relevant
- Supporting origin evidence
- Applicable measure-related references
Value & Commercial Data
Transaction information relevant to customs valuation and other declaration requirements.
- Invoice and currency information
- Relevant valuation elements
- Delivery terms and transport costs
- Adjustments, where applicable
Procedure & Documents
Information connecting the declaration to the intended customs procedure and relevant supporting evidence.
- Requested and previous procedures
- Supporting document references
- Authorisations, where required
- Previous document or movement references
Three Layers.
Different Responsibilities.
Declaration software can apply several types of checks before submission. These checks are valuable, but they address different questions and should not be treated as equivalent.
Does the message meet the expected structure, format and interface specifications?
Are the values, code combinations and relationships consistent with the known rules of the system?
Are the declared classification, origin, value and procedure actually correct under the applicable law?
Key principle: Passing automated validation does not establish that a declaration is legally accurate or immune from subsequent customs controls.
Know Where Every
Data Element Comes From.
Reliable declaration integration requires more than field mapping. Organisations should identify which system owns each data element, who verifies its accuracy and how corrections are managed.
Define the Source of Truth
Establish the authoritative source for each field instead of relying on conflicting copies of data.
Identify Missing Information
Detect data that cannot be obtained from business systems and define how it must be supplied or reviewed.
Preserve Data Lineage
Record relevant source references, transformations, approvals and subsequent corrections.
Manage Changing Requirements
Review mappings when customs specifications, code lists or business processes change.
The applicable data requirements must be checked against the current Union Customs Code framework, its delegated and implementing provisions, and the specifications of the relevant system.
Secure the Connection.
Verify the Authority.
Electronic customs declaration systems require more than a technically valid message. Access, identity, representation and operational permissions must be addressed according to the applicable customs and system-specific requirements.
Authentication proves an identity to a system. Authorisation determines what that identity is permitted to do. Customs law separately governs the roles and responsibilities of the declarant and any customs representative.
Technical Authentication
The integration must use the authentication mechanism supported by the destination interface and comply with its security rules.
- Approved credentials or certificates
- Secure credential storage
- Credential renewal and revocation
- Environment-specific access controls
EORI & Operator Identification
EORI provides an identification reference for economic operators in customs dealings. It must not be confused with technical credentials or access approval.
- Relevant operator identifiers
- Consistency of declared party roles
- Registration requirements
- System-specific onboarding
Representation & Permissions
The declarant’s role and any direct or indirect representation must be established independently of the technical connection.
- Direct or indirect representation
- Evidence of empowerment to act
- Applicable user permissions
- Delegation and access governance
Audit & Message Integrity
Maintain records that support investigation, reconciliation and accountability throughout the declaration lifecycle.
- Submission and response references
- Time-stamped processing events
- Controlled corrections and resubmissions
- Appropriate log access and retention
API Access Is Not
Customs Representation.
A software application may be technically connected to a customs system without being entitled to submit declarations for every economic operator.
The right to act in a customs operation, the representation arrangement and the conditions for using an electronic submission channel must each be verified.
Is the interface available, and has the connection been approved under the relevant technical rules?
Who is the declarant, who is the representative, and what authority supports the representation?
Which persons bear the relevant obligations under customs law, regardless of the software used?
Important: An EORI number does not automatically grant access to every customs system, and possessing API credentials does not itself establish customs representation authority.
Protect the Entire
Declaration Lifecycle.
Security controls should cover preparation, transmission, response handling, corrections and the preservation of relevant records.
Protect Data in Transit
Use the secure transport and cryptographic mechanisms specified for the relevant interface.
Apply Least Privilege
Limit credentials and user permissions to the functions necessary for authorised operations.
Prevent Uncontrolled Duplicates
Reconcile uncertain submissions before retrying. Duplicate handling must follow system-specific rules.
Maintain Reliable Evidence
Preserve appropriate message references, responses, approvals and processing histories under applicable retention rules.
Customs representation and responsibilities
Articles 18 and 19 of Regulation (EU) No 952/2013 address customs representation and empowerment to act. Other UCC provisions govern the obligations and responsibilities associated with customs declarations. Technical integration does not replace those legal requirements.
Read the Union Customs Code
Build for Real Operations.
Not Just Successful Tests.
Reliable declaration integration must handle incomplete data, rejected messages, uncertain transmission outcomes and evolving customs system requirements.
The most difficult problems often appear after the first successful submission. A production integration needs operational controls, exception handling, monitoring and a clear maintenance model.
Incomplete Source Data
ERP and logistics systems may not contain every element required for a customs declaration or may store information in an unsuitable format.
Rejected Declarations
A customs system may reject a declaration because of invalid data, incompatible code combinations or other applicable validation conditions.
Timeouts & Unknown Outcomes
A communication timeout does not prove that the destination system failed to receive or process a submission.
Duplicate Submissions
Automatic retries, user actions or disconnected systems can cause the same business transaction to be submitted more than once.
Changing Message Specifications
Customs systems may introduce updated schemas, code lists, validation rules or technical interface requirements.
Provider & Access Dependencies
Integration may depend on a software provider, national onboarding, authorised access arrangements or services outside the developer’s control.
A Missing Response
Is Not a Rejection.
When a submission produces no visible response, the integration must distinguish between a confirmed failure and an uncertain processing outcome.
Repeated transmission without checking the original transaction can introduce duplicate declarations or inconsistent business records.
Keep a stable internal reference linking requests, responses and the business operation.
Use the reconciliation facilities actually supported by the destination system or provider.
Route uncertain cases for manual review rather than assuming technical failure.
Record acceptance, rejection or other applicable system status.
Investigate using supported reference or status mechanisms.
Select the appropriate action only after establishing the available transaction information.
Verify Feasibility
Before Writing the Integration.
A staged approach helps expose access restrictions, missing data, testing requirements and commercial dependencies before they become expensive development problems.
Verify the Target Interface
Identify the responsible customs system, supported connection method, access eligibility and required onboarding.
Audit the Available Data
Compare business records with required declaration data elements and establish ownership of missing fields.
Design Mapping & State Management
Define message transformation, transaction references, response handling and exception workflows.
Validate Against Real Specifications
Use official or provider test facilities where available and complete any required conformance procedures.
Introduce Production Gradually
Establish monitoring, operational responsibilities, manual fallback and recovery procedures.
Maintain the Integration
Track system updates, credentials, incidents, provider commitments and recurring operational costs.
Before Development,
Answer These Questions.
A technically attractive integration may still be commercially or operationally unviable if access, testing or maintenance requirements cannot be met.
Understand the Rules.
Explore the Connections.
Customs declaration integration operates within a legal and technical framework. The Union Customs Code establishes core customs obligations, while the applicable electronic systems and their specifications determine how messages are exchanged.
Use official sources to verify legal requirements, applicable data elements and implementation conditions. The availability of an electronic customs system does not necessarily mean that an open or publicly accessible API exists.
Official EU Customs Resources
Primary legislation and European Commission information for understanding the customs declaration environment.
Union Customs Code
Regulation (EU) No 952/2013 establishes the core legal framework for customs declarations, representation and customs procedures.
REGULATION (EU) 952/2013UCC Delegated Act
Commission Delegated Regulation (EU) 2015/2446 supplements the UCC, including provisions relevant to customs data requirements.
REGULATION (EU) 2015/2446UCC Implementing Act
Commission Implementing Regulation (EU) 2015/2447 sets detailed rules for implementing provisions of the UCC.
REGULATION (EU) 2015/2447Taxation & Customs Union
European Commission information on customs policy, electronic customs initiatives and related EU systems.
EUROPEAN COMMISSION PORTALElectronic Customs System ≠ Public API
Customs authorities may provide electronic submission through national platforms, approved software channels or other controlled interfaces. Access arrangements, specifications, testing and eligibility must be established for the particular system and use case. There is no universal assumption that every EU customs declaration can be submitted through a single publicly available API.
Connect the Systems.
Understand the Requirements.
Explore the wider Customs APIs section to understand integration models, technical dependencies and the boundaries of automated customs processes.