Two systems, one consignment
Health controls and customs are separate processes with separate records. The Common Health Entry Document is filed in TRACES NT and closed by the border control post in Part 2. The customs declaration is a different submission entirely. The join between them is the CHED reference, and it is easy to drop.
The failure this causes
A consignment can pass the documentary, identity and physical checks, be recorded as accepted in Part 2, and still not be released, because the customs declaration does not carry the CHED reference. Nothing is wrong with the goods. The two records simply have not been linked. Reading through the CHED and customs declaration integration step makes clear that this is treated as part of the same job, not a separate one.
Designing the handoff
- treat the CHED reference as a required field on the customs declaration for any regulated consignment, not an optional one
- pull the reference from the CHED record rather than re-keying it, since transcription is where digits get lost
- validate the CHED type against the goods classification at the same point, so CHED-P and CHED-D confusion is caught once
- keep both records under one consignment identifier internally, so the link is queryable after the fact ### Classification as the shared dependency
The CHED type follows the product, and so does the customs classification. iClassification determines HS codes across 32 or more countries, which lets the same classification decision drive both the CHED type and the declaration rather than being made twice by two teams.
Bring both submissions into one audited flow, and watch a demo to see the reference carried through automatically.
Top comments (0)