ENS Workflow Design for Northern Ireland Freight Teams

The workflow problem

Teams that treat ENS as customs work miss the deadline. ENS binds to the transport booking, not the customs paperwork window.

Recommended workflow

1. Booking created in the TMS.
2. Consignment data pulled into the ENS builder.
3. XI EORI validated at booking, not at submission.
4. Description matched against the approved product library.
5. ENS submitted through ICS2.
6. Movement Reference stored against the booking.
7. Customs route selected (simplified, internal market, full).
8. Supplementary declarations auto-generated where simplified. The full workflow is walked through in the Windsor Framework ENS reference.

Split of responsibility

• Trader: master data, descriptions, EORI check.
• Carrier: legal ownership of ENS.
• Forwarder: submission and ICS2 response handling.

Corrections

Corrections applied only to downstream customs declarations create mismatch flags. Apply at the ENS source and cascade forward.

Design ENS workflows that hold up under audit — Watch a demo.