A Declaration Is a Structured Data Problem
The Customs Declaration Service, HMRC's platform for all UK import and export entries, follows the UK Trade Tariff data model. Instead of the box layout used under the old CHIEF system, every declaration is built from structured data elements. For anyone who thinks in schemas, a CDS entry is essentially a validated record set that HMRC either accepts or rejects.
The Sections of an Entry
Data elements are grouped into sections that cover the parties involved, the goods and their commodity codes, transport details, valuation, and the customs procedure. Each element has to be present and consistent with the others. A procedure code that contradicts the goods description, or a value that does not match the invoice, fails validation on HMRC's side and the shipment waits. The full structure, and how agents work through it in practice, is set out in this Freight Forwarder's Guide to UK Customs.
Where Errors Concentrate
Four fields cause most failures:
- Commodity code
- Customs value
- Procedure code pair (four digits plus three)
- Document references
Validate Before You Submit
The pattern is familiar from software: catch errors at input, not in production. Filing software with built-in validation flags inconsistencies before submission, so clearance can be almost instant instead of held for queries. Clean data in, cleared goods out.
See validation in action. Watch a demo
Top comments (0)