The Common Health Entry Document is submitted through TRACES NT and acts as the entry authorisation for a regulated consignment. At the border, its fields are compared against the health certificate and the commercial documents. Any disagreement between those sources is a hold, so integration work should target one thing: a single authoritative value per field.
The integration problem in one line
Three documents, produced by three parties, in three systems, must agree exactly. The certificate comes from the exporting authority. The invoice comes from the supplier. The CHED comes from you. Nobody owns the whole chain, which is why these disagreements surface so quietly and so often.
Fields worth treating as critical
- Establishment code, matched exactly and checked for current listing and activity scope
- Seal numbers, which must match the health certificate record
- Quantities and weights across certificate, invoice and CHED
- Product description and category, since the category drives the CHED type
- Consignment origin and destination details Every one of these is a comparison point, which is why CHED and TRACES NT data matching deserves explicit integration work.
Practical integration patterns
Extract rather than re-key. Intelligent document processing pulls values from source documents, which removes the transcription layer entirely. Validate on write, not on submit, so an operator sees a mismatch while they can still act. Keep an audit trail of what was checked and when, because that record is what turns a repeat refusal argument into a factual one.
Submit early
Pre-arrival CHED submission gives the integration a correction window. Filing on arrival means any mismatch is discovered when the goods are already at the ramp.
FAQ
Which CHED type applies?
It depends on the consignment category. Selecting the wrong type is itself a documentary refusal reason.
Watch a demo to see field level matching across certificate, invoice and CHED in a single view.
Top comments (0)