The Integration Question
Two paths lead into TSS: portal entry and API submission. Either way, the same five data groups need to be assembled and validated first. The integration decision is about where each field is sourced from and how it stays consistent.
What to Pull From Where
From the ERP or product data: commodity code, approved description, material composition, certificate flags. From the order or shipment record: parties, quantities, values, origin, currency. From the transport system: mode, carrier, route. From authorisation records: EORI, UKIMS number, procedure and relief authorisations.
Fields That Should Never Live in Two Places
Commodity codes, EORI numbers, UKIMS authorisation numbers and standing party spellings. One system owns each. The commodity code guidance for TSS covers what breaks when this is not enforced.
Validation as a Contract
Treat the validation layer as an interface contract between the ERP and the customs submission. Failed checks return to source; passed data goes forward. That keeps compliance out of the submission tool and inside the record system where it belongs.
Move validated customs data from your systems to TSS in one path. Watch a demo.
Top comments (0)