Customs Explorer
⌕

Customs Explorer

Multiple filing

EU CUSTOMS / ICS2 / ENTRY SUMMARY DECLARATION

ICS2 Multiple Filing Explained.

How multiple parties contribute Entry Summary Declaration data under the EU Import Control System 2 — and what carriers, freight forwarders and other supply chain participants need to know.

Multiple filing allows different parties to submit the ENS particulars for which they are responsible, where the applicable ICS2 filing arrangements permit this approach. Successful processing depends on accurate data, appropriate filing responsibilities and the correct association of the submitted information.

ICS2 EU advance cargo information system
ENS Entry Summary Declaration
Multiple parties Coordinated data submissions
ICS2 DATA SUBMISSION MODEL CONCEPTUAL
MULTIPLE DATA CONTRIBUTORS
Carrier Transport-related ENS data
Freight Forwarder Relevant shipment particulars
Other Filing Party Additional required information
EU CUSTOMS SYSTEM Import Control System 2 ENS processing & risk analysis

Linked filing information supports the applicable ENS process.

Illustrative architecture — filing combinations, data requirements and responsibilities vary by transport mode and applicable ICS2 specifications.
Shared Data Contribution

Different parties may provide different ENS particulars.

Filing Coordination

Information must be correctly linked and reconciled.

Regulatory Accountability

Each filer must understand its applicable obligations.

02 / HOW MULTIPLE FILING WORKS

How Does ICS2 Multiple Filing Work?

Under the EU Import Control System 2, multiple filing allows ENS particulars to be submitted by more than one economic operator when the applicable filing arrangements permit it. The information must be correctly associated so that customs authorities can process the relevant Entry Summary Declaration data for safety and security risk analysis.

THE OPERATING PRINCIPLE

One ENS Data Requirement. Multiple Contributors.

In a conventional single-filing arrangement, one filing party provides the required ENS particulars through the applicable electronic customs process.

With multiple filing, different parties may submit different portions of the required information. For example, a carrier may hold transport-related data, while a freight forwarder or another supply chain participant holds additional shipment details.

This does not remove the need to establish which party is legally responsible for each submission, whether the information is complete and how the related filings are identified.

FILING ARRANGEMENTS
MODEL 01 Single Filing
Filing party ENS data

One party submits the required information under the applicable filing arrangement.

MODEL 02 Multiple Filing
Carrier Other filer
Linked ENS data

Different parties submit their respective particulars, which must be correctly associated.

Conceptual comparison. The actual number of filings and required data sets depend on the applicable ICS2 scenario.
OPERATIONAL SEQUENCE

From Separate Data Sources to Customs Processing.

The process requires coordination between parties, suitable references and the handling of customs responses throughout the filing lifecycle.

ICS2 MULTIPLE FILING / CONCEPTUAL WORKFLOW DATA ASSOCIATION
01
PREPARATION

Allocate Filing Responsibilities

Identify which party will provide each required set of ENS particulars and confirm the applicable filing arrangement.

02
SUBMISSION

Transmit the Relevant Data

Each filing party submits its required information through the applicable ICS2 connection or authorised service arrangement.

03
ASSOCIATION

Link Related Filings

The system uses the applicable references and identification data to associate related ENS information.

04
PROCESSING

Validate & Analyse

Customs processing may include data validation, completeness checks and safety and security risk analysis.

05
FOLLOW-UP

Handle Responses

Relevant parties monitor acknowledgements, rejections, information requests and other applicable customs messages.

Filing sequences, identifiers, message types and deadlines vary according to the transport mode, filing scenario and applicable ICS2 specifications.

DATA ASSOCIATION

Why Linking the Filings Matters.

Multiple filing is not simply a collection of unrelated submissions. The relevant filing information must be associated using the identifiers and references required for the specific ICS2 filing scenario.

If the information cannot be linked correctly, the ENS process may remain incomplete or require corrective action. Technical acceptance of one submission does not, by itself, prove that all necessary ENS information has been provided.

Important distinction A filing reference, an ENS MRN where assigned, and a transport document reference are not interchangeable identifiers. Their use depends on the applicable message specifications.
ILLUSTRATIVE DATA LINKAGE
This diagram does not represent a fixed message structure or a guaranteed filing sequence.
PRACTICAL EXAMPLE

Carrier and Freight Forwarder: A Multiple Filing Scenario.

Consider a shipment entering the EU where the carrier manages the transport operation but another supply chain participant holds additional information required for ENS purposes.

PARTY A

Carrier

Provides the transport-related particulars assigned to its filing under the applicable multiple filing arrangement.

PARTY B

Freight Forwarder

Provides the additional ENS particulars for which it is responsible, where the relevant filing arrangement permits this.

SYSTEM

ICS2 Processing

Associates the relevant information and performs the applicable processing and safety and security controls.

Operational lesson: The parties must coordinate the necessary references, filing responsibilities and deadlines. Neither party should assume that another participant has completed its required submission without appropriate confirmation.

ESSENTIAL DISTINCTIONS

What Multiple Filing Does — and Does Not — Mean.

01 / DATA CONTRIBUTION

Different Parties Can Supply Different Particulars

Multiple filing distributes the submission of required ENS information across permitted filing participants.

02 / NOT DUPLICATION

It Is Not Simply Multiple Copies of the Same ENS

The purpose is coordinated provision of relevant information, not independent duplicate declarations for the same data.

03 / LEGAL RESPONSIBILITY

Each Filer Must Understand Its Obligations

The distribution of data submission does not automatically transfer or eliminate legal responsibilities.

04 / SYSTEM STATUS

Submission Does Not Equal ENS Completion

Processing status must be assessed using the applicable ICS2 responses and the completeness of the required information.

03 / FILING RESPONSIBILITIES

ICS2 Multiple Filing: Who Files What?

Multiple filing changes how Entry Summary Declaration particulars may be submitted, but it does not eliminate the need to identify the legally responsible parties. Carriers, freight forwarders and other economic operators must understand their respective filing obligations, available information and coordination requirements.

THE LEGAL STARTING POINT

The Carrier Is the Primary ENS Filing Party.

Under Article 127 of Regulation (EU) No 952/2013, the Entry Summary Declaration is generally lodged by the carrier. The Union Customs Code also provides for other persons to lodge an ENS in specified circumstances.

Where multiple filing applies, the allocation of filing obligations and the submission of additional particulars must be assessed against the relevant legal provisions and ICS2 operational specifications.

Read Article 127
THE FILING PARTICIPANTS

Three Roles. Different Responsibilities.

The roles below illustrate common supply chain participants. The actual filing party and the required data depend on the transport mode, contractual arrangements and applicable ICS2 filing scenario.

ROLE 01

Carrier

The party responsible for bringing goods into the customs territory of the Union in the relevant transport context.

Typical information
  • Transport and conveyance particulars
  • Relevant transport document references
  • Routing and arrival-related information
  • Other data required for its filing scenario
Key consideration

The carrier must establish whether its ENS obligations are fulfilled through its own filing and any applicable multiple filing arrangements.

ROLE 02

Freight Forwarder

An intermediary that may hold shipment information not directly available to the carrier.

Typical information
  • House-level transport document data
  • Consignor and consignee particulars
  • Goods descriptions and package details
  • Additional shipment-level information
Key consideration

A freight forwarder is not automatically a separate ICS2 filer. Its role depends on the applicable legal and operational filing arrangements.

ROLE 03

Other Economic Operators

Other supply chain participants may possess required ENS particulars or be involved in permitted filing arrangements.

Possible information
  • Additional commercial particulars
  • Goods-related information
  • Relevant party identification data
  • Information required by the specific scenario
Key consideration

Possession of shipment data does not, by itself, create an independent multiple filing obligation.

DATA OWNERSHIP & FILING

Responsibility Matrix: Who Controls the Information?

This illustrative matrix distinguishes where information is commonly available from who may be responsible for filing it. It is not a prescribed ICS2 allocation of legal responsibilities.

Information category Carrier Freight forwarder Other party
Conveyance and transport information Typically available May hold details Context dependent
Master transport document references Typically available May hold references Context dependent
House transport document details May receive data Often available May hold details
Consignor and consignee information May receive data Often available May be source
Goods descriptions and package details May receive data Often available May be source
Filing references and submission statuses For own filings For own filings For own filings
CRITICAL DISTINCTION

Data Ownership Is Not the Same as Legal Filing Responsibility.

A freight forwarder may possess detailed commercial information while the carrier holds the principal transport information. This difference in data availability is one reason multiple filing arrangements can be operationally useful.

However, an organisation’s possession of data does not automatically determine its legal filing obligations. The actual allocation must be assessed under the Union Customs Code and the relevant delegated and implementing rules.

DATA OWNERSHIP Who holds the information?

Commercial systems, transport documents, customer records and supply chain data.

≠
OPERATIONAL COORDINATION

Five Questions Every Filing Arrangement Should Resolve.

Before implementing multiple filing, the parties should establish clear responsibilities, technical references and procedures for handling exceptions.

01

Who Is the Filing Party?

Identify each legally relevant filer for the applicable ENS data set.

02

Who Supplies the Data?

Establish the source and responsible owner of each required information element.

03

How Are Filings Linked?

Confirm the required references, identifiers and information exchange.

04

Who Monitors Responses?

Define how filing statuses, rejections and requests for additional information are handled.

05

Who Corrects Errors?

Agree on escalation, amendments and operational ownership of corrective actions.

LEGAL FRAMEWORK

Filing responsibilities should be assessed using the current consolidated EU legislation and the relevant ICS2 technical documentation.

04 / DATA SUBMISSION & MESSAGE FLOW

ICS2 Multiple Filing: Data Submission & Message Flow.

Multiple filing requires more than transmitting separate data sets. Filing parties must use the applicable electronic interfaces, exchange the correct references and monitor customs responses so that the required Entry Summary Declaration information can be processed and associated.

SYSTEM ARCHITECTURE

How Multiple Filers Connect to ICS2.

Filing parties may use their own systems or an appropriate service provider to submit the relevant ENS particulars through the applicable ICS2 interface arrangements.

MULTIPLE FILING / CONCEPTUAL DATA ARCHITECTURE ILLUSTRATIVE MODEL
INDEPENDENT DATA SOURCES
Carrier System Transport information Relevant ENS particulars
Forwarder System Shipment information Relevant ENS particulars
Other Filing Party Additional information Where applicable
SUBMISSION LAYER Applicable ICS2 Filing Interfaces

Electronic messages, technical validation, identifiers and customs responses

EU IMPORT CONTROL SYSTEM ICS2

ENS processing, association of related information and safety and security risk analysis

Customs Responses

Relevant acknowledgements, rejections, information requests and other applicable messages return to the appropriate filing parties.

MESSAGE LIFECYCLE

Six Stages of an ICS2 Filing Process.

The following stages describe a general operational lifecycle. Actual message order and available responses depend on the filing scenario and applicable technical specifications.

01
DATA PREPARATION

Build the Required Filing Data

Each filing party prepares the ENS particulars for which it is responsible, using the relevant source information and data rules.

02
TRANSMISSION

Submit Through the Applicable Interface

The required electronic filing is transmitted using the appropriate ICS2 connection arrangements and message specifications.

03
TECHNICAL PROCESSING

Receive Initial Processing Responses

The filer monitors applicable system responses, including technical or business-rule errors that may require corrective action.

04
DATA ASSOCIATION

Associate Related ENS Particulars

Where multiple filing applies, the required identifiers and references support the association of related filing information.

05
CUSTOMS PROCESSING

Monitor Risk Analysis and Requests

Customs may perform safety and security risk analysis and issue applicable requests or other operational messages.

06
FOLLOW-UP

Resolve Outstanding Actions

Filing parties address relevant errors, amendments and information requests, while maintaining records of their submissions and responses.

REFERENCES & IDENTIFIERS

Correct References Are Essential for Data Association.

Multiple filing depends on the ability to identify related information correctly. The relevant references must be exchanged between filing parties and entered in the appropriate data elements.

The exact identifiers required depend on the applicable ICS2 message and filing scenario. Operators should not assume that a transport document number, filing reference and ENS MRN perform the same function.

Important: An ENS MRN is assigned through the customs process where applicable. It is not a reference independently generated by an ERP, transport management system or commercial software provider.

REFERENCE MANAGEMENT
01
Transport Document References

Identify relevant transport documents according to the applicable data requirements.

02
Filing References

Support identification and tracking of submissions in the relevant process.

03
ENS MRN

A customs-assigned reference used according to the applicable ENS processing arrangements.

04
Party Identification

Identifies relevant economic operators using the identifiers required by the filing specifications.

The list is explanatory and is not a complete ICS2 message data dictionary.
CUSTOMS RESPONSES

What Happens After Submission?

Sending a message does not necessarily mean that the filing has been accepted, linked or fully processed. Filing parties must interpret the actual responses issued for their specific ICS2 scenario.

Acceptance or Acknowledgement

Confirms the applicable stage of message receipt or processing. It does not automatically establish that all related ENS information is complete.

Rejection or Validation Error

Indicates that a submission or its data requires review and potentially correction before processing can continue.

Request for Additional Information

Customs may require further particulars or action as part of the applicable safety and security process.

Amendment or Follow-Up

Changes or additional operational steps may be necessary, subject to the relevant legal and technical conditions.

OPERATIONAL CONTROL

Monitor Each Filing — and the Overall ENS Process.

In a multiple filing environment, different participants may receive different messages relating to their respective submissions. An effective monitoring process should therefore distinguish individual filing status from the wider state of the associated ENS information.

Parties should agree how relevant statuses are communicated, how unresolved issues are escalated and how corrective actions are coordinated before the applicable filing deadlines.

OPERATIONAL MONITORING MODEL CONCEPTUAL
FILING A Carrier submission
Track responses
FILING B Other party submission
Track responses
DATA ASSOCIATION Related filing information
Verify linkage
FOLLOW-UP Outstanding customs actions
Resolve issues
These labels describe monitoring tasks, not official ICS2 status codes.
OFFICIAL EU REFERENCES

Technical implementation should be based on the current ICS2 documentation and applicable EU customs legislation.

05 / ERRORS, COMPLIANCE & PRACTICAL SCENARIOS

ICS2 Multiple Filing: Errors, Compliance & Operational Risks.

Multiple filing can improve the allocation of ENS data submissions between supply chain participants. However, it also creates dependencies between separate filings, information sources and operational responsibilities. Missing data, incorrect references or unresolved customs messages can disrupt the filing process.

THE CENTRAL OPERATIONAL RISK

One Accepted Submission Does Not Necessarily Mean the ENS Information Is Complete.

In a multiple filing arrangement, a party may receive a positive processing response for its own submission while other required information remains outstanding. Operators must distinguish individual filing responses from the overall completion and processing of the relevant ENS data.

OPERATIONAL DIAGNOSTICS

Where Multiple Filing Can Break Down.

The most important failure points are often found between organisations rather than inside a single customs software system.

MULTIPLE FILING / EXCEPTION MONITOR ILLUSTRATIVE
FILING A Carrier submission

Transport-related ENS particulars

Processed
FILING B Additional particulars

Expected from another filing party

Outstanding
DATA ASSOCIATION Related ENS information

References and data must be reconciled

Review required
EXCEPTION DETECTED

Incomplete Filing Coordination

The carrier’s submission may have been processed, but the additional information expected under the filing arrangement has not yet been confirmed.

Required operational response Identify the responsible party, verify references, confirm the applicable deadline and resolve outstanding actions.
All states in this illustration are explanatory labels, not official ICS2 message or status codes. Actual processing must be determined from the applicable customs responses.
COMMON FAILURE POINTS

Six Problems That Require Active Control.

Each issue should be assessed against the applicable ICS2 filing scenario, technical documentation and customs messages.

01 / MISSING FILING

Required Particulars Not Submitted

A participant expected to provide additional ENS information does not submit the relevant particulars within the applicable timeframe.

Control Confirm filing ownership, deadlines and evidence of actual submission.
02 / REFERENCE MISMATCH

Related Information Cannot Be Associated

Incorrect or inconsistent references prevent the relevant submissions from being associated as intended.

Control Validate required identifiers and reference exchanges before submission.
03 / DATA INCONSISTENCY

Conflicting Shipment Information

Related parties hold different values for relevant shipment, transport or commercial data elements.

Control Reconcile source documents and establish a defined process for resolving discrepancies.
04 / REJECTED MESSAGE

Technical or Business-Rule Rejection

A filing fails an applicable validation requirement and needs correction or further action.

Control Read the actual response, identify the rejected data and follow the permitted correction procedure.
05 / UNANSWERED REQUEST

Customs Follow-Up Is Not Handled

A relevant customs request is received, but the responsible participant does not respond or escalate it appropriately.

Control Assign message monitoring and escalation responsibilities to named operational roles.
06 / OWNERSHIP GAP

Each Party Assumes Another Will Act

The filing arrangement lacks a clear division of responsibilities for submission, correction or monitoring.

Control Establish an agreed responsibility matrix and operational escalation process.
PRACTICAL SCENARIOS

Three Situations Supply Chain Operators Should Prepare For.

These examples illustrate operational dependencies. They are not fixed ICS2 message sequences or universal rules for every transport mode.

01
MISSING ADDITIONAL INFORMATION

The Carrier Files, but Another Party Has Not.

The carrier submits the transport-related ENS particulars. Under the agreed and applicable multiple filing arrangement, another participant is expected to provide additional information, but the submission has not been confirmed.

Operational risk

The required ENS information may remain incomplete, notwithstanding the processing of the carrier’s own filing.

Recommended response

Contact the responsible filer, verify the applicable deadlines and confirm the actual customs processing responses.

02
INCONSISTENT REFERENCES

Both Parties Submit, but the Data Does Not Match.

Two participants transmit information relating to the same transport operation, but one or more required references are inconsistent or incorrectly entered.

Operational risk

Related filing information may not be associated correctly, requiring investigation or corrective action.

Recommended response

Compare the relevant references against source records and apply the correction procedure permitted by the actual customs processing status.

03
CUSTOMS INFORMATION REQUEST

Customs Requests Additional Details.

During the applicable ENS processing and risk analysis, customs issues a request that requires a response or further operational action.

Operational risk

The relevant request may remain unresolved if the parties have not agreed who monitors and handles customs messages.

Recommended response

Identify the message recipient, determine the required action and coordinate the response with the party holding the necessary data.

COMPLIANCE BY DESIGN

Build Controls Around the Entire Filing Process.

A reliable multiple filing process requires both technical validation and organisational coordination. It is not enough to verify that individual electronic messages have been transmitted.

Operators should document the applicable filing arrangement, maintain appropriate submission records and establish clear procedures for errors, amendments and customs requests.

Regulatory reminder

The precise obligations, deadlines and available corrective procedures depend on the current EU customs legislation and applicable ICS2 specifications. Internal controls do not replace compliance with those requirements.

OPERATIONAL CONTROL CHECKLIST
  • Document Filing Responsibilities

    Identify the parties and their relevant ENS obligations.

  • Validate Source Information

    Check required data before electronic submission.

  • Verify Reference Consistency

    Use the identifiers required by the applicable scenario.

  • Monitor Customs Responses

    Track actual acknowledgements, rejections and requests.

  • Escalate Outstanding Actions

    Assign ownership and procedures for unresolved issues.

  • Maintain Appropriate Records

    Retain relevant evidence in accordance with applicable requirements.

Internal control framework — not an official European Commission checklist.
IMPLEMENTATION PRIORITIES

What to Verify Before Using Multiple Filing.

01

Legal Eligibility

Confirm that the proposed multiple filing arrangement is permitted for the relevant circumstances.

02

Technical Readiness

Verify access to the appropriate ICS2 interfaces, message specifications and testing arrangements.

03

Data Availability

Establish whether each participant holds the required particulars at the necessary time.

04

Operational Ownership

Define responsibilities for submission, monitoring, corrections and customs follow-up.

OFFICIAL LEGAL REFERENCES

Use current consolidated legislation and official ICS2 technical documentation when assessing specific filing obligations.

06 / FAQ & OFFICIAL RESOURCES

ICS2 Multiple Filing: Frequently Asked Questions.

Explore the most common questions about ICS2 multiple filing, Entry Summary Declaration responsibilities, data association, customs responses and the applicable EU legal framework.

ESSENTIAL QUESTIONS

Understanding Multiple Filing in Practice.

Select a question to explore the practical requirements and responsibilities involved in ICS2 multiple filing.

What is multiple filing in ICS2?

Multiple filing is an arrangement under which more than one party may submit different particulars required for an Entry Summary Declaration, where permitted by the applicable EU customs rules and ICS2 specifications. Related information must be correctly associated for customs processing.

Who is responsible for filing the ENS?

Under Article 127 of the Union Customs Code, the carrier is generally responsible for lodging the Entry Summary Declaration. Other persons may lodge the declaration in the circumstances provided by that article. Specific multiple filing responsibilities must be assessed under the applicable legal provisions.

Must every freight forwarder submit a separate filing?

No. Being a freight forwarder does not automatically create a separate multiple filing obligation. The applicable requirements depend on the transport mode, legal provisions and relevant filing arrangements.

How are multiple filings linked in ICS2?

Related filing information is associated using the references and identifiers prescribed by the applicable ICS2 data and message specifications. Filing parties must coordinate the relevant information accurately.

Does an accepted filing mean the ENS is complete?

Not necessarily. Acceptance or processing of an individual submission does not automatically confirm that all required ENS particulars have been provided and associated. The relevant customs processing responses must be monitored.

What happens when filing references do not match?

Incorrect or inconsistent references may prevent related filing information from being associated as intended. The responsible parties should examine the actual customs messages, verify source data and follow the applicable correction procedures.

Is an ENS MRN the same as a transport document number?

No. An ENS MRN is a customs-assigned reference, while transport document numbers identify relevant transport documents. Their respective functions and use depend on the applicable filing and message specifications.

Who must correct errors in a multiple filing arrangement?

Corrective responsibilities depend on the affected filing, the legally responsible party and the applicable customs procedure. Participants should establish clear operational responsibilities for monitoring, escalation and correction.

Can multiple filing be implemented through a service provider?

Filing parties may use appropriate technical or service arrangements where permitted. However, outsourcing electronic transmission does not automatically remove the obligations imposed by customs legislation.

Which EU legislation governs ICS2 multiple filing?

The legal framework includes Regulation (EU) No 952/2013, particularly Article 127, together with the relevant provisions of Delegated Regulation (EU) 2015/2446 and Implementing Regulation (EU) 2015/2447. Current ICS2 specifications establish the technical requirements for applicable filing scenarios.

KEY TAKEAWAYS

Four Principles to Remember.

Multiple filing depends on coordinated data submission, clearly identified responsibilities and reliable customs processing.

01 Identify the Filing Parties

Determine who must submit the relevant ENS particulars under the applicable legal framework.

02 Coordinate References

Ensure the identifiers required for associating related filing information are accurate.

03 Monitor Customs Responses

Distinguish individual filing responses from the overall processing of ENS information.

04 Resolve Outstanding Actions

Establish clear responsibilities for errors, information requests and permitted corrections.

CUSTOMS EXPLORER / EDITORIAL CONCLUSION

Multiple Filing Requires Coordination, Not Just Connectivity.

Successful ICS2 multiple filing depends on identifying the relevant filing responsibilities, ensuring the availability and accuracy of required ENS data, associating related submissions and responding appropriately to customs messages.

Technical connectivity is only one part of compliance. Effective operational arrangements between supply chain participants remain essential.

EU Customs ICS2 ENS Multiple Filing

This guide is provided for general educational purposes and does not constitute legal advice. Filing obligations, technical specifications and operational requirements should be verified against current official EU sources and the circumstances of the relevant transaction.