DEV Community

Cover image for Integrating TSS Declaration Data With ERP and Freight Systems
John Hall
John Hall

Posted on

Integrating TSS Declaration Data With ERP and Freight Systems

Declarations are only as accurate as your source systems

TSS declarations are only as accurate as the data feeding them. That data usually sits in your ERP, TMS and WMS — long before the customs form is opened.

The data map

ERP owns commodity codes, product master and origin. TMS owns carrier, port, mode and movement date. WMS owns consignment weight, packaging and lot detail. Customs tooling combines all three into ESD, SFD, supplementary, IMMI or Full Frontier records.

The exact field expectations per declaration are covered in this Northern Ireland TSS declarations explainer.

Integration principles

Pull commodity codes from ERP once, not per declaration. Push port and mode from TMS into route selection so inventory-linked ports trigger Full Frontier automatically. Push UKIMS status onto every trader record so IMMI eligibility is calculable at booking. Log every submission event back into ERP for month-end reporting.

Treat the deadline as an SLA

Treat the 10th-of-month supplementary deadline as an SLA between systems, not a manual reminder.

The result

Well-integrated declaration data means the customs system stops being where errors are discovered and becomes where correct data is submitted.

Want to see the integration prebuilt? Watch a demo of iCustoms.

Top comments (0)