Integrating ENS Filing With TMS and Customs Systems

The integration case

ENS data lives in three systems: the TMS (transport), the customs stack (declarations), and ICS2 (safety and security). Without integration, each is rekeyed and each is a mismatch risk.

TMS side

Pull booking, mode, vehicle, and routing data from the TMS into the ENS builder. Store the returned Movement Reference against the booking so it is available for port check-in. The ENS submission requirements guide covers the full field set.

Customs side

Under the simplified customs route, supplementary declarations auto-generate from ENS data. That means the ENS is the upstream source of truth. Bad ENS = bad supplementary.

ICS2 side

Handle acknowledgements, Movement References, and rejections through structured message handling, not manual email flows. This matters most for volume lanes.

Sync rules

• One source of truth per consignment.
• Corrections applied upstream, cascaded down.
• XI EORI resolved at booking, not submission.
• Description library shared across TMS and customs. ### What to test

Test rejection handling, mismatch scenarios, and correction flows before go-live, not after.

Integrate ENS with the rest of your customs stack — Watch a demo.