Back to blog
Regulations··4 min read

CDS vs CHIEF: what the migration actually changed for hauliers

HMRC finished migrating UK customs declarations from CHIEF to the Customs Declaration Service. Here's what it means in practice if you just want your trucks to keep moving.

For anyone who has worked with UK customs for more than five years, CHIEF — HMRC's Customs Handling of Import and Export Freight — was the system. It's the one trade clerks learned on, the one every freight forwarder in the country had integration with, and the one that quietly held the UK's cross-border flow together for decades. It was also, by the end, seriously old.

Its replacement, the Customs Declaration Service (CDS), has now fully taken over. CHIEF has been retired for both imports and exports. If you've been on CDS for a while this is old news. If you're still catching up, here's the short version of what changed and what didn't, from a haulier's perspective.

What stayed the same

Despite the headline, a lot of the operational reality for hauliers has not changed.

  • Your goods still need a declaration before they can move.
  • Your EORI is still how HMRC identifies you across every system.
  • Your commodity codes still matter, and wrong ones still cause queries.
  • GVMS sits on top of both systems and cared only that a valid MRN existed.
  • The ferry operators still don't wait for late paperwork.

If you're a haulier and your customs work is done by a broker, the move from CHIEF to CDS was largely invisible. Your paperwork and timings are the same.

What genuinely changed

CDS reshaped a few things that you notice once you look closely:

More data fields. CDS declarations require more data elements than CHIEF ever did, especially around valuation, parties and procedure codes. The upshot for traders is that commercial invoices and packing lists need to contain more detail, and incomplete paperwork that used to squeeze through on CHIEF now often triggers a query on CDS.

Postponed VAT Accounting is the default behaviour. Under CHIEF, import VAT was generally paid at the border and recovered later. CDS is natively built around Postponed VAT Accounting (PVA), which means VAT-registered importers can declare and recover import VAT on their return rather than paying it upfront. It's a cash-flow advantage that many businesses still don't take full advantage of.

The procedure-code model is different. CHIEF's "CPC" (Customs Procedure Codes) system has been replaced by CDS "Procedure Codes" and "Additional Procedure Codes". It reads differently, and a common mistake during migration was mechanically re-using old CPCs without understanding the mapping.

The audit trail is tighter. Every edit, every query, every resubmission is logged more visibly on CDS than it was on CHIEF. For compliance, that's a good thing. For bad habits, it's a problem.

HMRC's correspondence has moved online. Queries and amendments come through CDS itself rather than through older portals. If your customs inbox relies on scraping email, make sure that's actually pointing at CDS-era mailboxes.

Where the migration went wrong most often

From what we've seen, three failure patterns repeat:

  1. Under-specified commercial invoices. Goods descriptions that were "acceptable" on CHIEF are now frequently insufficient on CDS, leading to classification queries on shipments that used to glide through.

  2. Wrong valuation method. CHIEF was quite forgiving about valuation shortcuts; CDS is not. Using "method 1" (transaction value) where the facts don't actually support it — related parties, royalties, unusual payment structures — now tends to generate a query where it once didn't.

  3. PVA eligibility confusion. Importers who could have used PVA sometimes reverted to paying import VAT at the border because the PVA selection wasn't flagged on the declaration. Cash was paid that could have flowed through the VAT return.

What to do if you're still unsure you're in a good place

Three quick self-checks:

  • Pull a sample of your last 10 import declarations and look at how many had queries. If more than a quarter did, the cause is almost certainly upstream data quality, not CDS itself.
  • Ask your broker whether they've been using PVA as the default where you're VAT-registered. If the answer is anything other than "yes, always unless there's a specific reason not to", you may be missing out.
  • Check whether your commercial invoice template includes fields for: HS code (at least 8-digit), country of origin, Incoterms, value broken out by line, and party EORIs. If any of those are missing, add them now.

The quiet good news

CDS is, on the whole, a better system than CHIEF. It's built for a post-Brexit volume of declarations, it integrates properly with GVMS, it supports Postponed VAT Accounting natively, and it keeps a proper audit trail. The migration wasn't painless, and anyone telling you it was wasn't watching closely. But the worst of the churn is behind us, and the work now is mostly about making sure the upstream data — invoices, packing lists, commodity codes — is good enough for CDS to process cleanly.

For hauliers specifically: if your broker is competent and your paperwork is clean, the transition is already done. For hauliers whose broker is still "working on it" in 2026, the transition is an urgent conversation to have, not a background task.