CDS versus CHIEF and UK Customs Declarations

A shipment can be packed, booked and waiting at the port, yet still be delayed by one missing data element in its customs declaration. That is why CDS versus CHIEF is not simply a technology change for UK traders. It changes how declaration data is structured, checked and submitted – with direct implications for release times, duty payments and audit readiness.

For businesses that still refer to “CHIEF entries”, the practical position is clear: CHIEF has been replaced by the Customs Declaration Service (CDS). Import declarations moved to CDS in September 2022 and export declarations followed in March 2024. The focus now is not choosing between two live systems, but ensuring that your people, processes and software are set up to use CDS accurately.

CDS versus CHIEF: the practical difference

CHIEF, short for Customs Handling of Import and Export Freight, was the UK’s long-standing customs declaration system. It was familiar to customs agents, freight forwarders and experienced declarants because much of the process was built around a box-based declaration format.

CDS is HMRC’s replacement platform. It is designed around the Union Customs Code data model and uses a more detailed set of data elements, codes and rules. For traders, that often means the commercial facts behind a declaration need to be captured more consistently before goods arrive or depart.

The shift can feel more demanding, especially where teams previously relied on an agent to interpret incomplete paperwork. However, CDS also gives businesses a more structured basis for customs compliance. When the underlying data is right, declarations can be submitted with greater consistency and fewer last-minute corrections.

This is not a matter of copying a CHIEF declaration into a new screen. CDS requires a review of the information, codes and authorisations used for each movement. A declaration that was accepted under an established CHIEF process may need different or additional information in CDS.

What changed when declarations moved to CDS?

The most noticeable change is the way data is presented. CHIEF used numbered boxes. CDS uses data elements, each relating to a specific piece of information about the goods, parties, procedure, transport or financial arrangements.

For a logistics or customs team, this means operational staff need to understand what sits behind the declaration rather than relying only on familiar box numbers. The commodity code, customs procedure code, country of origin, customs value, Incoterms, supporting document references and authorisation details must all align.

More detailed customs data

CDS may require information that was not routinely requested in the same way under CHIEF. This can include additional party details, valuation information, document codes, additional information codes and procedure-specific data.

The exact requirements depend on the goods and the customs procedure. A straightforward free circulation import is different from an entry using inward processing, customs warehousing, returned goods relief or postponed VAT accounting. The point is not to add data for its own sake. It is to evidence why the goods are being declared in a particular way and how any duty or VAT treatment has been applied.

This makes good source documents essential. Purchase orders, commercial invoices, packing lists, transport documents and supplier statements should be available early enough for the declarant to check them. If the information arrives only after the lorry has reached the border, there is less time to resolve a classification, value or origin query.

Different codes and procedure combinations

CDS uses more granular code combinations than CHIEF. Customs procedure codes still define the broad treatment of the goods, but they are supported by additional procedure codes, document codes and other declaration data.

This is especially relevant where a business claims a relief, uses a customs special procedure or imports goods under a specific commercial arrangement. Teams should not assume that a code which worked historically is still the correct CDS approach. The declaration needs to reflect the current rules and the trader’s actual authorisations.

Duty and VAT payment controls

CDS also changed aspects of how traders manage financial accounts and payment instructions. Businesses using a duty deferment account, cash account or postponed VAT accounting should confirm that their accounts, authorities and declarations are correctly aligned.

A declaration can be technically complete but still create problems if the payment method is wrong or the available guarantee is insufficient. Finance, customs and operations teams therefore need a shared view of who is authorised to use each account, how duties are reconciled and how postponed import VAT is reported.

Why the change matters beyond the customs team

The most effective CDS process begins before a declaration is created. Procurement needs to obtain accurate supplier information. Warehouse and transport teams need the correct consignment and movement references. Finance needs visibility of customs value, freight and insurance costs where relevant. The customs declarant brings those details together and applies the customs rules.

This is where businesses can see the real benefit of treating customs as an operational process rather than a final administrative step. Better data at source reduces declaration amendments, clearance delays and repeated requests to suppliers or hauliers.

It also improves management visibility. When declarations are processed in-house through suitable customs software, traders can retain access to their declaration records and see how commodity codes, values, origins and procedures are being used. That control can be valuable during an HMRC review, an internal audit or a tender process with a major customer.

Outsourcing still has an important place. A smaller importer with occasional shipments may prefer an agency to complete declarations, while a high-volume 3PL may need an experienced internal team using direct software connectivity. Many businesses take a hybrid approach: routine declarations are processed internally, while complex movements, special procedures or overflow volumes are handled with expert support.

Preparing your business for reliable CDS declarations

The right preparation depends on shipment volume, goods complexity and internal experience. A business importing one standard product line from a regular supplier has a different requirement from a freight forwarder handling hundreds of consignments for multiple customers.

Start by mapping the data required for your regular movements. Check who provides the commodity code, origin, valuation details and commercial terms, then decide who validates them. If a supplier gives incomplete information, create a process for resolving that before the goods are dispatched.

Next, review the customs procedures your business uses. Make sure any relevant authorisations are current and that staff understand the evidence required to support reliefs or special procedures. A lower duty bill is only sustainable when the claim is properly evidenced.

Training matters just as much as software. Staff do not need to become customs lawyers, but they should understand the difference between a transport reference and a customs declaration reference, when a movement needs safety and security data, and when an issue must be escalated. Clear responsibilities prevent routine questions becoming a border delay.

Finally, test the full operational journey. A declaration is only one part of a movement. Depending on the route and goods, your process may also involve GVMS, safety and security declarations, NCTS5 transit activity, port systems or, for Ireland, Revenue’s ROS and PBN requirements. The systems must work together at the point goods move, not just in a training environment.

Choosing software, agency support or both

A CDS solution should make the required data easier to manage without hiding the compliance decisions behind it. Look for direct connectivity, clear validation messages, accessible declaration history and workflows that match how your team actually operates. Ease of use is particularly important where operational staff have limited customs experience but need to act quickly.

Support should be part of the decision, not an afterthought. Customs rules, commodity classifications and border processes can change. A provider that can offer training, practical advice and agency cover gives your business options when a declaration is unusual or your internal resource is stretched. Custran combines this support with software designed to help businesses process customs declarations in-house when that is the right model.

The move from CHIEF is complete, but improving a CDS process is ongoing. Treat every recurring declaration issue as a signal to improve the source data, ownership or training behind it. That is how customs becomes a controlled part of your supply chain, rather than the point at which it stops moving.