Field notes
Reading a CDS extract without losing the procedure code
A Customs Declaration Service extract is a kindness and a trap. It lets a trader leave the broker portal, but it also invites a well-meaning analyst to treat every column as if it were a sales ledger. Procedure codes are the first casualty. They arrive as four-digit strings, sometimes with a leading zero that a spreadsheet helpfully strips, and they explain whether goods were released to free circulation, entered a warehouse, or moved under a special procedure.
When we prepare a reporting pack, we freeze those codes as text before any chart is drawn. A month that mixes 4000-series releases with warehousing or inward processing will otherwise produce a duty total that finance cannot reconcile to the broker invoice. The chart is not wrong in a mathematical sense; it is answering a question nobody asked.
The practical habit is dull and worth repeating. Ask the person who exports the file which column is the procedure code, whether supplementary declarations are in the same sheet, and whether any lines are messages rather than goods. Then print one page of codes next to the duty column and sit with operations for twenty minutes. If a warehousing line is still in the “duty paid” chart after that conversation, the mistake is ours, not the extract’s.
None of this requires a new system. It requires a named person, a frozen export, and the humility to leave a code visible in the pack even when it makes the pie chart less pretty.