Four failure modes cover most incidents
Four failure modes cover most TSS declaration incidents. Each has a signature — and each has a fix that lives upstream of the mistake.
1. Supplementary declaration submitted with default commodity codes
Signature: duty corrections, HMRC queries. Root cause: auto-generated fields treated as final. Fix: block submission until commodity code fields carry a review flag.
2. Missed 10th-calendar-day deadline
Signature: late-submission notices, escalations. Root cause: month-end movements get the shortest window and ownership is unclear. Fix: work the calendar backwards from the 10th and assign named owners per lane.
For the exact deadline logic, see this TSS declaration cheat sheet.
3. UKIMS-authorised traders running full supplementary declarations
Signature: heavier monthly workload than peers. Root cause: no quarterly IMMI eligibility review. Fix: automate a UKIMS × Category 1 check per SKU.
4. Wrong route at inventory-linked ports
Signature: Full Frontier requirements discovered post-booking. Root cause: freight teams booking without route-check. Fix: gate booking on the port classification.
Fix upstream, not downstream
Solve the upstream causes and the incident tickets stop showing up.
Want to see the upstream fixes wired in? Watch a demo of iCustoms.
