DEV Community

Cover image for Debugging Failed TSS Declarations: A Field Guide
Kristi Hampson
Kristi Hampson

Posted on

Debugging Failed TSS Declarations: A Field Guide

Rejected declarations rarely fail for exotic reasons. Five categories cover most of them.

1. Commodity code issues

Wrong digit count, expired codes or codes that do not exist in the current tariff. Fix in the product master, not per declaration.

2. Document code mismatches

The document code claimed does not reconcile with the current Tariff Requirements. This is one of the most valuable validations to catch pre-submission, as covered in this TSS validation guide.

3. Mass and package count disagreement

Gross mass, net mass and package count on the declaration do not match the invoice or packing list. Usually a data extraction fault, not a customs one.

4. Missing or invalid licences

Certificate and licence references that do not match, or scheme authorisation numbers invalid for the movement date.

5. Party data drift

Party details out of sync with authorisations. Fixed once at the party master, not at the submission.

See how iCustoms surfaces and routes these failures. Watch a demo.

Top comments (0)