How Information Moves Through a TSS Declaration Workflow

Tracing a Single Record

A useful way to understand a TSS declaration workflow is to follow one shipment record through it.

1. It arrives as a commercial invoice, a packing list and a transport document.
2. Extraction reads the fields it needs and puts them into a structured record.
3. Validation compares fields across documents, checks formats and looks for missing values.
4. Enrichment adds commodity codes and authorisations from approved lookups.
5. Submission sends the completed record to TSS.
6. Response handling records the outcome and, if rejected, routes the case to a person. ### What Changes at Each Step

The information does not change identity as it moves. What changes is how structured, checked and complete it is. See the movement visualised in From Trade Documents to TSS Submission.

Where Time Disappears in a Manual Workflow

• Waiting for a missing packing list.
• Retyping the same weight into a second system.
• Re-checking commodity codes typed differently each time.

• Chasing rejection reasons after submission rather than before.

  Where an Automated Workflow Puts Time Back

• Documents are read once.

• Fields are compared automatically.

• Rejections are surfaced with the context needed to fix them.

• Known products flow through without re-work.

Ready to see the same journey inside a live TSS declaration system? Watch a demo of iCustoms.