CDS: What Changed When CHIEF Retired, and Why It Still Bites

Migration to the Customs Declaration Service finished on 30 March 2024, and since then every UK import and export declaration has gone through it. Most businesses experienced that as a software change their broker dealt with, which is why the more interesting consequence tends to go unnoticed: CDS asks considerably more of the data behind a declaration than CHIEF ever did.

Elements rather than boxes

CHIEF was built around fixed boxes, and CDS is built on the Union Customs Code data model, which uses structured data elements grouped into eight sections. In practical terms that took the declaration from roughly 60 fields to more than a hundred.

The point of the change was validation. A structured model lets the system check that what you have entered is internally consistent, so errors that once sat undetected in a free-text box now tend to surface as a rejection instead.

Procedure codes split in two

The change that causes the most confusion is what happened to Customs Procedure Codes. Under CHIEF a goods item carried a single fixed seven-digit CPC, whereas CDS splits that into a four-digit Procedure Code and up to 99 three-digit Additional Procedure Codes for the same item.

That is more expressive, because a movement can now carry several additional codes describing different aspects of the treatment claimed. It is also less forgiving, since the combination has to be coherent, and a code that was habitually copied from the last similar shipment is exactly the kind of thing that no longer passes unexamined.

What this means in practice

The constraint has quietly moved from one place to another. Under CHIEF the limiting factor for many businesses was whether somebody knew how to complete the form, whereas under CDS it is whether the underlying data is good enough to survive validation.

That surfaces in entirely familiar places, because commodity codes now have to be right and consistently applied, valuation has to rest on a basis you can explain, and origin claims need evidence sitting behind them. None of those are new obligations, but the system has become considerably better at noticing when they are not met.

If a broker prepares your declarations, it is worth asking where their data actually comes from. They can only submit what you give them, which leaves them reliant on your product master, your classifications and your commercial documents being accurate.

Why this leads towards AEO

An AEO application examines records, systems and declaration accuracy, which is very close to the list of things CDS validates against. A business that has adapted well to CDS has usually done most of the underlying work already, even if nobody framed it that way at the time.

The relationship also runs the other way, since the simplified procedures that make customs cheaper to operate are administered through CDS and generally depend on an authorisation you have to qualify for. Getting the data right is the precondition for both.

CDS requirements and procedure code combinations change. Check current HMRC guidance before relying on this for a live declaration.