ENS Filing Under ICS2: What Maritime Forwarders Have Learned One Year In

ICS2 (Import Control System 2) is the EU's pre-arrival cargo safety and security framework. Release 3 brought maritime, road, and rail traffic into the system, completing the rollout that began with air express in 2021. For maritime, filing went live in mid-2024 for ocean carriers, with NVOCCs and freight forwarders following through a staged deployment window that closed at the end of the same year.

One year into the new regime, the conversation has moved on. Filing a declaration is no longer the question. The question is whether the data inside the declaration is precise enough to avoid a Do Not Load (DNL) decision from EU customs at the foreign port of loading.

Who Files What: The Multi-Filing Model

ICS2 Release 3 changed the filing structure fundamentally. Under the previous ICS regime, a single carrier filing covered everything on board. Release 3 introduced multi-filing:

• The carrier files at master Bill of Lading level for cargo it owns end-to-end.
• The NVOCC or freight forwarder files at house Bill of Lading level for cargo it controls under its own contract.
• Both filings link to the same shipment via the Master Reference Number (MRN).

In practice this means a single container can be the subject of two parallel declarations, filed by two different parties, with both required to be consistent. When they are not, EU customs receives conflicting signals and the cargo gets flagged.

Common Failure Modes One Year In

A year of operational data shows where multi-filing breaks down most often.

Late filing

For deep-sea maritime, the ENS must be filed at least 24 hours before loading at the foreign port of departure. Short-sea and intra-EU routes have shorter windows. The most common compliance gap is forwarders filing late because the underlying booking data arrived late from the shipper. The platform's job here is to flag the deadline against the vessel's loading window, not against the booking creation date.

Generic commodity descriptions

"Auto parts," "machinery," "goods": these descriptions no longer pass. ICS2 Release 3 enforces precise commodity language and a valid HS code at 6 digits minimum. Many DNL decisions through 2025 were triggered by descriptions that customs systems flagged as risk-unverifiable. Operators who moved to HS-code-driven commodity descriptions, where the description is generated from the code rather than free-typed, saw their DNL rate drop sharply.

Inconsistent party identifiers

The expanded dataset requires consignor, consignee, notify party, and seller or buyer when these differ. Each party needs a valid identifier: EORI for EU parties, a recognised foreign identifier otherwise. Forwarders who carry stale or duplicate consignee records in their TMS end up filing different identifiers for the same legal entity, which triggers manual review at the first port of entry.

Master and house data drift

If the carrier files MBL-level data showing one consignee and weight, and the forwarder files HBL-level data showing a different consignee or a weight that does not reconcile, customs sees the mismatch immediately. Reconciliation has to happen before filing, not after.

Container substitution between filing and loading

When containers are swapped at the last minute (a common operational reality), the ENS reference to a specific container number becomes incorrect. An amendment must be filed before loading, not at arrival. The forwarders who handle this cleanly are the ones whose container assignment is tied to the same record as the ENS filing, so the amendment fires automatically when the container changes.

The Expanded Dataset in Practice

Release 3 brought a richer ENS dataset covering parties, commodities, packaging, transport, journey, references, and the security identifier. In a paper-driven workflow, populating seven categories accurately per shipment is impossible at scale. The forwarders who scaled into Release 3 cleanly did three things:

1. Mastered party data once. Consignees, consignors, and notify parties are managed as master records with their valid identifiers, not re-keyed per booking.
2. HS code at booking, not at declaration. The HS code assignment moves upstream into the booking flow, so the ENS pulls a validated code rather than asking the operator to remember one.
3. Single source of truth across MBL and HBL. When the same platform holds both, the consistency check happens automatically before submission.

What "Do Not Load" Actually Costs

A DNL message blocks loading at the foreign port. The container does not sail. The forwarder absorbs storage charges at origin, missed-vessel re-booking fees, and the customer conversation. In the worst cases the freight is re-routed and arrives a week late through a different gateway.

DNL volumes across maritime in 2025 ran in the low single-digit percentages, but the operational cost per incident is high enough that even a 1% DNL rate hits the P&L visibly. Carriers, NVOCCs, and forwarders are now grading their filing accuracy by DNL rate the same way they grade billing accuracy by invoice-dispute rate.

A Practical Compliance Checklist

For maritime forwarders and NVOCCs filing house-level ENS, the checklist is short but operationally heavy.

• Are party master records clean, with valid EORI or foreign identifiers on every consignee and notify party?
• Is the HS code captured at booking and inherited into the ENS, not free-typed at filing time?
• Does the platform reconcile MBL and HBL data automatically before submission?
• Is the filing deadline calculated against the vessel's loading window, not the booking date?
• When containers are swapped at the gate, does an ENS amendment fire automatically?
• Is DNL rate tracked as a KPI, with root-cause coding per incident?

If any of these are still handled by spreadsheets and reminders, the gap is operational, not regulatory.

Closing

The deadlines for ICS2 Release 3 are behind us. The compliance work is not. Multi-filing only delivers cleaner customs outcomes when the parties involved are operating on data that reconciles, with precision that customs systems can verify without manual review. Forwarders and NVOCCs who treat ENS filing as a downstream output of a clean booking, with HS codes, party identifiers, and weights established once and inherited everywhere, are seeing measurably lower DNL rates and faster gate-in at first port. The rest are still firefighting one filing at a time.