Rejection messages arrive at consignment level. TSS raises a case identifying affected items. The temptation is to fix the record and resubmit. The better move is to trace the error back to the step that produced it.
Trace Path
Read the error code first. TSS publishes two error-code guides: one for entry summary and simplified frontier declarations, another for supplementary and full frontier declarations. Match the code to the field. Then ask: was that field entered from a source document? Copied from a previous declaration? Filled in by memory? Where the field came from tells you which control was missing.
If the description was pulled from a supplier invoice with no library check, the missing control is a standard description library. If a commodity code was reused from last quarter, the missing control is a Tariff Requirements review at code changes. The TSS rejection troubleshooting reference maps causes to controls.
Log It or Repeat It
A rejection not logged is a rejection scheduled to repeat next month. Rejection logging with monthly pattern review is the difference between improving and firefighting. It is the least glamorous control and the highest return.
See TSS troubleshooting inside iCustoms. Watch a demo.
