DEV Community: Kristi Hampson

CHED and TRACES NT: Getting Field Level Consistency Right

Kristi Hampson — Tue, 11 Aug 2026 07:35:41 +0000

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.

Troubleshooting a Stopped Consignment Under EUDR

Kristi Hampson — Mon, 10 Aug 2026 08:47:24 +0000

If goods stop at the border under EUDR, start with the reference number. A missing or mismatched DDS reference on the declaration halts a consignment as surely as a missing health certificate, and it is the most common self-inflicted failure.

The first four checks

Is there a reference at all? Confirm the statement was submitted in the EUDR Information System and that the number was captured. Does it match the goods? A reference tied to different products, quantities or suppliers will not satisfy verification. Is the product actually in scope? Re-run the HS code against Annex I. Scope errors present as filing errors. Is the deadline live for your category? Large and medium operators are in from 30 December 2026, micro and small from 30 June 2027, with the earlier date applying to those already under EUTR.

The check people forget

If the issue is not the reference, ask which system raised it. Health certificate and establishment code problems come from Regulation (EU) 2017/625 controls, not EUDR. The two run side by side, and a single consignment such as leather can be held by either. Diagnosing the wrong system wastes hours, so keep the comparison to hand along with this DDS reference number guidance.

Prevent the repeat

Log the root cause by stage: collection, assessment, submission or declaration. Patterns appear quickly and they usually point at one upstream data gap.

FAQs

Can we file a statement retrospectively to release goods? Filing must precede the declaration that quotes the reference, so plan the sequence rather than repairing it.

Does a valid establishment code help an EUDR hold? No. They prove different things under different regulations.

Watch a demo and get a guided demo

Debugging a Flagged TRACES Establishment Code: A Decision Tree

Kristi Hampson — Fri, 07 Aug 2026 10:40:05 +0000

A flagged TRACES establishment code has one of two root causes: your data is wrong, or the approval is wrong. Diagnosing which one first saves the supplier call you did not need to make.

Start with your own data

Check these before contacting anyone:

Whitespace. Codes pasted from PDFs and emails carry invisible characters.
Transposition. Two swapped digits produce an unrecognised number that looks correct at a glance.
Column alignment. Merged cells shift values into the wrong fields, so a valid country lands in the activity column.
Age. Codes reused from a previous order may have been correct then and not now.

If the raw source document and your file disagree, the problem is yours. Fix and re-run.

Then read the flag type

Different flags mean different things, and the fix follows the type. An unrecognised number points at data or a delisting. A country mismatch usually points at a supplier operating from a different site than assumed. An activity category mismatch means the establishment is approved, but not for what you are importing. The published guidance on flagged TRACES establishment codes separates these cases clearly.

Resolution paths

Confirm the correct approval number with the supplier.
Correct the typo in your own records.
Source from an approved establishment where the current one no longer covers the product.

Then re-validate. A fix that has not been re-checked is an assumption.

The rule that matters

Never ship with an unresolved flag. Overriding a flag does not clear the goods; it just moves the discovery to the border, where it costs more and takes longer to fix.

Watch a demo

The Off-By-One Error in Establishment Code Validation

Kristi Hampson — Wed, 05 Aug 2026 08:45:58 +0000

The naive check

if (code in tracesList) return PASS;
This is the bug almost every homegrown validation contains. It answers "does this number appear somewhere on a list" when the actual requirement is "is this facility currently approved for the activity that matches the goods I am importing".

Why the difference bites

TRACES NT publishes establishments by country and by activity type. Meat products, fish and seafood, dairy, eggs, animal fats and oils, animal by-products. A facility approved for dairy is not approved for meat products. A cold store listing does not imply processing approval.

So a code can be genuinely present, genuinely current, and still wrong for your consignment. The explanation of approved establishment requirements covers how those activity sections are organised.

The corrected check

match = tracesList.find(e =>
  e.code === code &&
  e.country === exportCountry &&
  e.activity === requiredActivity &&
  e.status === 'listed'
);
nameMatches(match, supplier) ? PASS : FLAG;

Four conditions plus a name and address match, not one.

Mapping goods to activity

Rough guide by HS chapter: meat in 2 and 16, fish in 3 and 16, dairy and eggs in 4, animal fats and oils in 15, animal by-products in 5 and 23. Composite products containing processed animal ingredients still need approval evidence, which is the case teams most often miss.

Fail loudly

A validation that returns PASS on partial matches is worse than no validation, because it manufactures confidence. Flag, do not assume.

Watch a demo

The Document Types Behind EU TRACES: CHED, INTRA, PHYTO and Export Certificates

Kristi Hampson — Fri, 31 Jul 2026 11:56:21 +0000

If you are mapping out a compliance workflow that touches EU TRACES, you need to know which document type applies before you can validate anything against it.

The core document types

TRACES issues several certificate types depending on what is moving and where. The Common Health Entry Document (CHED) has been required for animals and goods entering the EU since December 2019. INTRA, also called ITAHC, is the Intra-Trade Animal Health Certificate used for live animal movements between member states and Northern Ireland. Export certificates cover goods leaving the EU, and PHYTO certificates apply to plants and plant products.

How the certification flow connects them

The process itself follows a fixed sequence: an operator or authority creates the certificate, a competent authority validates it, the consignment travels with it, and border officials check it against the CHED at an EU border control post before recording a decision. Our guide to how EU TRACES works sets out each step alongside the document types involved.

Establishment lists as a fifth data type

Alongside certificates sits a separate but connected dataset: establishment lists, the registers of non-EU facilities approved to export animal-origin products. A certificate can be perfectly valid while the establishment behind it has been delisted, which is a distinct failure mode worth checking separately.

Building a validation layer

Any workflow processing these documents benefits from checking establishment codes independently of certificate validity, since the two can diverge without warning.

Watch a demo

Invalid EORI: The Basic Field That Stops an Entry Cold

Kristi Hampson — Thu, 30 Jul 2026 07:02:27 +0000

The check that feels too simple to make

EORI and party details look like the safest part of a declaration, which is why they get skipped. An invalid or expired EORI, or a wrong party detail, can stop an entry before the technical fields even matter. It is a basic check with an outsized effect.

Where the basic error fits

An invalid EORI belongs to the same list of repeat mistakes as a wrong commodity code, incorrect valuation, and a wrong procedure code. Treating the basics with the same care as the technical fields keeps entries moving, and this guide to the common UK customs declaration errors and how to avoid them covers party details alongside the rest.

A ten-second verification

Before submitting, confirm the EORI is active and correctly formatted and that importer and representative details match the records. A validation step flags an invalid EORI immediately, well before HMRC does.

Want to see party-detail validation catch a problem early? Watch a demo to see it run.

Automating the Frontier-to-Supplementary Handoff

Kristi Hampson — Tue, 28 Jul 2026 07:18:47 +0000

The weakest point in an SDP workflow is the handoff. Data collected at the frontier has to reappear, complete and accurate, in the supplementary declaration.

Do it by hand and you rekey. Rekeying introduces errors, and because the supplementary entry drives the duty calculation, those errors cost money and compliance standing.

Automation fixes this. Good software carries frontier data forward to the supplementary entry, which reduces rekeying and error. The Simplified Customs Declaration Process shows why the handoff is where accuracy matters most.

A sensible monthly routine looks like this. Reconcile the month's frontier entries. Complete each supplementary declaration from the carried-forward data. Check duty totals against the deferment statement before the deadline, usually the fourth working day of the next month.

Keep evidence for each release too. HMRC officers can ask how a frontier entry links to its supplementary declaration, so a clear audit trail is not optional. Automate the link, and the audit trail builds itself.

Watch a demo

GVMS, GMR and PBN: Untangling CDS Pre-Lodgement

Kristi Hampson — Fri, 24 Jul 2026 07:11:54 +0000

Three acronyms cause more confusion in CDS pre-lodgement than almost anything else: GVMS, GMR and PBN. Each belongs to a different part of the process, and mixing them up is a common source of delay.

GVMS: the port system

The Goods Vehicle Movement Service is how many UK RoRo ports operate instead of an inventory system. At these ports, pre-lodgement is not optional, it is simply how the process works.

GMR: what the MRN becomes

Once a pre-lodged declaration is submitted at a GVMS port, its MRN needs to be combined into a Goods Movement Reference before the vehicle boards. Without a valid GMR, the driver cannot check in.

PBN: the Ireland equivalent

If the goods travel by RoRo into Ireland, GVMS does not apply. Irish Revenue instead uses a Pre-Boarding Notification, which links declarations before the ferry departs. This CDS pre-lodgement at UK RoRo ports breakdown sets out how the GB and Ireland routes differ in full.

Keeping the three apart

The simplest way to avoid errors is to treat GVMS and GMR as the GB pairing, and PBN as its own separate process for Ireland, rather than variations of the same thing.

Watch a demo

Why HMRC Rejects UK Customs Declarations (and How to Fix It)

Kristi Hampson — Wed, 22 Jul 2026 07:20:28 +0000

A rejection is different from a query. It means HMRC has refused the entry outright, and it needs to be corrected before it can go anywhere.

The common rejection triggers

The wrong procedure code for the movement, data that does not match the supporting documents, an invalid or expired EORI number, and format errors in mandatory data elements are the usual causes. When this happens, correct the flagged field and resubmit. Good CDS software catches most of these before submission, which keeps the process moving rather than bouncing back and forth. This customs declaration process UK guide sets out the filing steps that reduce this risk from the start.

Turning a rejection into a quick fix

Treat a rejection as a specific, fixable error rather than a full restart. Most only need one field corrected before the entry can be resubmitted successfully.

FAQs

How fast can I resubmit after a rejection? As soon as the flagged field is corrected, generally within minutes.

Does an expired EORI cause an outright rejection? Yes, an invalid or expired EORI is one of the most common triggers.

Software that validates data before submission is the simplest way to avoid this stage altogether.
Watch a demo

The Benefits CDS Brings to UK Customs Filing

Kristi Hampson — Mon, 20 Jul 2026 08:23:00 +0000

Replacing a legacy system only pays off if the new one is genuinely better. Here is what CDS actually improves on over CHIEF.

Validation precision

CDS validates declarations against structured data elements rather than loose box entries, catching mismatches with more precision than CHIEF's model allowed. The full explainer on how this works is in this Customs Declaration Service guide.

Automated calculation

Duty and VAT are calculated directly from the declared data, reducing manual computation and the errors that come with it.

Financial visibility

The integrated Financial Dashboard replaces CHIEF's limited account visibility, bringing payments, statements, and balances into one view.

Scalability

Built on the Union Customs Code model and hosted in the cloud, CDS is designed to scale with UK trade volumes rather than strain under them, as CHIEF eventually did.

FAQs

What is the clearest improvement over CHIEF? More precise, structured validation and automatic duty calculation.

Does CDS scale better than CHIEF did? Yes, it was built specifically for post-Brexit trade volumes.

See these improvements in a live declaration. Watch a demo

Decommissioning CHIEF: Lessons from a Legacy Migration

Kristi Hampson — Thu, 16 Jul 2026 06:31:57 +0000

A Legacy System Finally Switched Off

CHIEF processed UK customs entries for decades, which in government technology terms makes it ancient infrastructure. HMRC decommissioned it in two phases: imports moved to the Customs Declaration Service on 30 September 2022, and exports followed on 4 June 2024. Since then, CDS has been the single production system for all UK declarations.

Phased Cutover, Real Consequences

Phased migrations sound gentle, but the end state is absolute. There is no fallback route, no legacy endpoint, no filing outside CDS. Any business that trades through the UK must complete registration before it can submit anything, and that onboarding takes real calendar time. The complete onboarding sequence appears in this guide to CDS registration for freight agents.

What Changed for Users

One digital platform for imports and exports alike
Identity anchored to the GB EORI rather than any CDS-specific number
Payment methods integrated into the platform: duty deferment, cash account, or immediate payment

The Takeaway for Teams

Every migration transfers work to the users. Here, that work is registration done in the correct order, with most teams completing it inside two weeks. Plan for it the way you would plan any dependency with a lead time.

Modern platform, modern tooling: iCDS files UK import declarations in around three minutes with 99% accuracy. Watch a demo

Debugging UK Customs Delays: Four Root Causes

Kristi Hampson — Tue, 14 Jul 2026 08:41:39 +0000

Treat Delays Like Incidents

When a shipment is held at the UK border, there is always a root cause, and it is nearly always one of four: a wrong commodity code, an incorrect customs value, a mismatched procedure code, or a missing document reference. Each triggers an HMRC query, a delay, or a penalty. Postmortems across clearance desks keep finding the same short list.

Root Causes and Their Guards

The fix for a recurring failure is a guard at input. Commodity codes get checked against the current tariff rather than copied from a previous entry. Values get reconciled with the commercial invoice. Procedure code pairs get matched to the actual goods movement. Document references get confirmed before submission. All four checks sit inside the wider process described in this guide to the UK customs process for freight forwarders.

Why Timing Makes It Worse

At many RoRo ports the declaration must be pre-lodged before the goods arrive. An error discovered at the border means a vehicle waiting while queries resolve. Clearance is almost instant when the data is clean, so the entire cost lives in the error path.

Shift the Check Left

Pre-submission validation is the shift-left move: software flags the four failure types before the entry reaches HMRC. The human review becomes a final confirmation instead of a bug hunt.

Fewer incidents, faster clearance. Watch a demo