ICS2 Compliance for AU/NZ Freight Forwarders

The EU's Import Control System 2 (ICS2) is reshaping how cargo bound for European ports and airports gets declared, and it doesn't only affect operators based in Europe. Any Australian or New Zealand freight forwarder handling shipments destined for the EU, or transiting through it, sits inside ICS2's compliance perimeter the moment that cargo is booked. Getting the filing wrong doesn't just risk a fine; it can mean a shipment stuck at customs while the rest of the supply chain waits on it.

This guide covers what ICS2 actually requires, why it matters specifically for AU/NZ operators, and what to look for in a freight forwarding platform that keeps you compliant without turning every booking into a compliance project.

What Is ICS2?

ICS2 is the European Union's pre-arrival security and safety programme, introduced under the Union Customs Code. It replaces the original Import Control System (now often referred to as ICS1) with a system built for much finer-grained risk analysis: EU customs authorities want visibility into what's moving toward their borders, and who's involved in moving it, before it ever arrives.

The mechanism is the Entry Summary Declaration (ENS): a structured dataset that carriers, freight forwarders, and in some cases postal and express operators must lodge before goods are loaded or arrive, depending on the mode of transport. Customs authorities use the ENS to run a safety and security risk assessment ahead of arrival, rather than discovering an issue once cargo is already on EU soil.

This isn't a one-off filing requirement bolted onto existing paperwork - it changes who submits what, how early, and how much detail is required, compared to the pre-ICS2 regime.

Why This Matters for AU/NZ Freight Forwarders Specifically

It's easy to read "EU customs system" and assume it's someone else's problem. It isn't, for two reasons.

First, geography doesn't exempt you. If your business books air, sea, or multimodal freight that terminates in, or transits through, an EU member state, your booking is inside ICS2's scope regardless of where your business is headquartered. An Australian forwarder consolidating freight for a European import customer is just as exposed to ICS2's filing obligations as a forwarder based in Rotterdam.

Second, ICS2 spreads responsibility across the chain rather than parking it entirely with the carrier. Depending on how a shipment is structured, freight forwarders can be responsible for house-level ENS data even when a carrier has already filed at the master level. If your booking and documentation workflow wasn't built with that split-filing reality in mind, it's easy to have a gap nobody notices until a shipment gets flagged.

For AU/NZ operators specifically, this also tends to be new territory in a way that AU and NZ's own customs regimes aren't - most forwarders here have well-worn processes for customs clearance at home, but far less muscle memory for a foreign safety-and-security filing regime with its own deadlines and data requirements.

The Phased Rollout: Release 1, 2, and 3

ICS2 hasn't landed all at once - the EU rolled it out in phases, each covering a different transport mode:

• Release 1 covered postal operators and express carriers moving cargo by air.
• Release 2 extended the requirement to general air cargo across all operators, not just postal and express services, bringing house-level and master-level ENS filing into scope for air freight broadly.
• Release 3 extends ICS2 to maritime, inland waterway, road, and rail transport - the modes most relevant to multimodal freight forwarders who combine ocean legs with inland transport.

The practical implication for AU/NZ forwarders: if you've only dealt with ICS2 in the context of air freight so far, don't assume your sea freight bookings into Europe are unaffected - the same underlying filing obligation extends to those modes under Release 3. Rollout phases and exact compliance deadlines are set and periodically adjusted by the European Commission - the European Commission's own ICS2 Release 3 page is the source to check for the current timeline, rather than treating any single guide, including this one, as the final word on specific dates.

What Data ICS2 Actually Requires

The data burden under ICS2 is genuinely heavier than the pre-ICS2 system, not just earlier. Where the previous regime asked for a relatively thin dataset, ICS2's ENS wants:

• A more complete picture of the parties involved - not just shipper and consignee, but additional roles such as buyer, seller, and notify party where applicable.
• Detailed goods descriptions, including harmonised system (HS) codes precise enough to support meaningful risk screening, rather than generic cargo descriptions.
• Routing and conveyance detail sufficient for customs authorities to model the physical movement of the shipment, not just its commercial terms.

For a forwarder managing this manually, or through a patchwork of spreadsheets and carrier portals, that's a meaningful jump in data-entry burden per shipment, and a meaningful jump in the number of places a data-entry mistake can hide.

What Happens When ICS2 Filing Goes Wrong

The consequences aren't abstract. An incomplete or late ENS can result in:

• Cargo held at the border while customs authorities wait on the missing data, with knock-on delays for the receiving customer and anyone downstream in the supply chain.
• Denied loading in some circumstances - carriers can refuse to load cargo that lacks a valid, accepted ENS, since they carry their own compliance exposure.
• Penalties for the responsible party, which, depending on the filing structure, may be the freight forwarder rather than the carrier.

None of this is unique to ICS2, and none of it is theoretical. DHL Express's own published account of its ICS2 rollout, written up by the World Customs Organization, describes real data-collection and coordination difficulties even for a global carrier with substantial compliance resources - a useful reminder that "we'll figure it out when it comes up" isn't much of a plan for an operator with far less dedicated compliance headcount.

How the Right Freight Forwarding Platform Helps

This is fundamentally a data and workflow problem, which is why it's a software problem as much as a compliance one. A freight forwarding platform that treats EDI integration and structured customs data capture as core, rather than bolted-on, gives forwarders a real advantage here: the same underlying data model that supports day-to-day customs clearance can be extended as new international requirements like ICS2 phase in, instead of requiring a separate manual process built from scratch for each new regulatory regime.

Concretely, that means:

• Capturing the fuller set of party and goods data ICS2 requires once, at booking, rather than re-keying it into a separate compliance step later.
• Structured EDI connections to the carriers and customs systems that need this data, reducing the number of manual handoffs where a filing can go missing or go stale.
• The flexibility to adapt data mappings as rollout phases (and their exact requirements) continue to evolve, rather than treating the current phase as the final state.

Expedient's forwarding and customs modules are built around exactly this kind of structured, EDI-driven data capture - the same discipline that supports day-to-day AU and NZ customs clearance extends naturally to adapting for evolving international requirements like ICS2, rather than requiring a bolt-on process per regulation.

Practical Steps to Prepare

If you haven't formally audited your ICS2 exposure yet, four steps cover the practical ground:

1. Map which of your lanes actually touch the EU - direct EU-bound freight is the obvious case, but transit shipments through EU ports can also trigger ICS2 obligations.
2. Confirm who's filing what - for each lane, know whether your business, your carrier, or a customs broker is responsible for house-level ENS data, and don't assume it's covered just because a carrier is filing at the master level.
3. Check your data capture, not just your process - do your existing systems capture the fuller party and goods detail ICS2 requires, or does someone currently re-key it manually before filing?
4. Confirm current deadlines directly - rollout phases and specific compliance dates are set by the European Commission and can shift; verify against the current official timeline for your specific transport mode rather than relying on a fixed date from any single guide.

Next Steps

ICS2 is one regulatory requirement among many that AU/NZ freight forwarders now have to track well beyond their home market. The forwarders who handle it best aren't the ones treating it as a one-time scramble - they're the ones running it through a platform already built for structured EDI and customs data. Contact us to talk through what ICS2 readiness looks like for your specific lanes.

Frequently Asked Questions