Status logic at the core
Every transit declaration resolves to one of two states. T1 for non-Union goods that have not been released into free circulation in the EU. T2 for Union goods that need to cross non-EU territory on their way back to the EU.
The decision is deterministic. It depends on the customs history stored against the goods, not on user selection.
Inputs the workflow needs
A reliable transit workflow needs four inputs. The origin of the goods. Any prior customs procedures such as warehousing or inward processing. The routing across CTC and non-CTC territories. The commercial evidence attached to the shipment record.
If you want the wider context, this guide to T1 and T2 transit declarations walks through each factor.
Outputs and downstream systems
The declaration type feeds the NCTS message set, the guarantee reference and the office of departure or destination logic. For T2 moves, the workflow also needs to attach or reference Union status proof so the arrival office does not raise an assessment.
Want to see this modelled inside a live system? Watch a demo.
Top comments (0)