DEV Community

Cover image for Troubleshooting T1 and T2 Transit Declaration Errors
Kristi Hampson
Kristi Hampson

Posted on

Troubleshooting T1 and T2 Transit Declaration Errors

Rejections at lodgement

The most common lodgement issues fall into a short list. Wrong office of departure code. Guarantee reference not authorised for the movement type. Commodity codes that do not match the previous customs entry. Consignor or consignee EORI mismatch.

Fixes are usually quick if the root data is clean.

Post arrival issues

Post arrival problems are the ones that hurt. A T2 movement can be reassessed as T1 at destination if the Union status evidence is missing or thin. That triggers a duty demand months after the move. The T1 and T2 transit document overview sets out exactly which evidence keeps this from happening.

Preventive checks

Run three checks before lodgement every time. Does the customs history support the declared status. Is the guarantee reference valid for the declaration type. Is the Union status evidence attached where T2 is used.

For a live view of these checks in action, watch a demo.

Top comments (0)