Integration Concepts Behind Automated TSS Declaration Submission

Three Categories of Integration

An automated TSS declaration workflow sits between three broad categories of system:

1. Source systems and documents — invoices, packing lists, transport documents and ERP records that hold the raw shipment facts.
2. Reference sources — approved lookups for commodity codes, authorisation numbers and party identifiers used to enrich the record.
3. The submission channel — TSS itself, which receives the completed declaration through an API and returns a status. ### Where the Interfaces Sit

Extraction lives closest to the source systems. Enrichment reads from reference sources. Submission speaks to TSS. Each interface has its own reliability, security and error-handling considerations. For a wider view of how these pieces sit together, read Streamlining the TSS Declaration Process.

Design Considerations

• Keep source-of-truth clear for every field.
• Prefer read from reference sources over free text entry for enrichment fields.
• Log every submission and every response for traceability.
• Handle rejection responses as workflow events, not as silent failures. ### What Integration Does Not Do on Its Own

Integration moves data. It does not decide what the data means. Classification of new products, risk judgement and final accountability still belong to the trader and the people supporting them.

See these integration concepts working end-to-end in a live TSS setup and Watch a demo of iCustoms.