The European Union’s Import Control System 2 (ICS2) represents a transformative shift in customs security, designed to enhance the safety of goods entering or transiting through the EU, Northern Ireland, Norway, and Switzerland. As of March 31, 2025, this advanced cargo information system is fully operational for various transport modes, with rail and road carriers joining the compliance framework from April 1, 2025. At its core, ICS2 mandates the submission of an Entry Summary Declaration (ENS) before goods arrive, enabling customs authorities to conduct risk assessments and ensure a secure supply chain. For businesses importing to the EU, understanding the documents and procedures required for ICS2 ENS compliance is essential to avoid delays, penalties, or shipment rejections.
ICS2 is a phased initiative replacing the previous Import Control System (ICS1), focusing on pre-arrival data submission to identify high-risk consignments. The ENS is the cornerstone document, a detailed declaration of cargo information submitted electronically to the ICS2 system. It applies to all economic operators (EOs)—carriers, freight forwarders, consignees, and logistics providers—involved in shipping goods to or through the EU. The system’s rollout began in 2021, with Release 3 now extending requirements to maritime, inland waterways, road, and rail transport, completing the transition by September 1, 2025, when ICS1 fully phases out.
What is ICS2 ENS Compliance?
Key Documents for Compliance
To comply with ICS2 ENS requirements, several documents and data elements are critical:
- Economic Operators Registration and Identification (EORI) Number: Every EO involved in the supply chain must have an EORI number, a unique identifier issued by an EU Member State. This is mandatory for the consignee and, in multiple filing scenarios, the supplementary declarant (e.g., freight forwarder submitting house-level data). Businesses new to EU trade must register for an EORI well in advance.
- Entry Summary Declaration (ENS): The ENS requires detailed shipment data, including:
- A complete commercial description of goods (e.g., “men’s leather shoes, size 10,” not just “shoes”).
- Six-digit Harmonized System (HS) codes for each commodity.
- Shipper and consignee details (names, addresses, and EORI numbers).
- Number of packages, weight, and transport mode specifics.
- For chemicals, a CUS code may be required if listed in the European Customs Inventory of Chemical Substances (ECICS).
- House and Master Bill of Lading: Ocean carriers submit the Master Bill of Lading (MBL) with high-level cargo details, while freight forwarders file the House Bill of Lading (HBL) for individual shipments. Both must align for a complete ENS.
- Supporting Commercial Documents: Invoices or packing lists may be needed to verify ENS data accuracy if customs requests further clarification.
Procedures to Ensure Compliance
Compliance begins with preparation. Businesses must update IT systems to interface with ICS2, either through in-house solutions or third-party IT service providers. The Shared Trader Portal (STP) facilitates ENS submissions, requiring registration in the Unified User Management and Digital Signatures (UUM&DS) system. A mandatory self-conformance test ensures system compatibility before going live.
Timing is critical: for maritime shipments, ENS must be filed 24 hours before loading (as of December 4, 2024, for house filers); for road and rail, prior to arrival starting April 1, 2025. EOs unprepared by these deadlines can request a deployment window from their National Customs Authority at least one month in advance (e.g., by March 1, 2025, for road/rail).
Collaboration is key—carriers and forwarders must coordinate to ensure data accuracy. Non-compliance risks shipment holds, customs rejection, or sanctions, disrupting supply chains. Training staff on ICS2 requirements and leveraging compliance software can streamline the process, ensuring legitimate trade flows smoothly while safeguarding EU borders.
UPDATE on ICS2 Compliance
To ensure smooth processing and compliance with EU Customs, we have identified errors that cause issues and delays:
Missing or invalid EORI numbers
- Issue: Missing/incorrect EORI numbers cause customs rejections.
- Solution: Verify EORI number accuracy via the EU’s validation tool.
Incorrect phone number format
- Issue: Non-standard phone numbers with symbols or letters cause processing errors.
- Solution: Use only digits and follow the required format.
Unacceptable cargo HS codes and descriptions
- Issue: Non-compliant cargo descriptions or HS codes delay customs clearance.
- Solution: Verify them against the latest EU Customs guidelines to prevent rejections.
