CDS Customs Declarations Software Checklist 2026

What this checklist covers

• Data quality and tariff alignment
• Validation rules for CDS submissions
• Integrations and reference data setup
• Go-live and operations playbook

Data quality first

• Tariff codes: confirm HS/commodity codes and duty/VAT rates are current for your goods.
• Parties: clean EORI, VAT, addresses, and contact info (consignor/consignee/agent).
• Licences and docs: map which commodities need certificates, OGDs, or special procedures.
• Incoterms: standardize allowed terms and defaults per customer or trade lane.
• DG: ensure UN numbers, classes, packaging groups, and special provisions are present.

Validation rules to enforce

• Required fields by declaration type: DUCR/MUCR, CPC, procedure codes, packages, weights.
• Country logic: ensure origin/destination match Incoterms and licence requirements.
• Valuation: currency, method, adjustments (freight, insurance, assists).
• Measures: net mass vs. supplemental units (litres, pieces, m2, etc.).
• Prohibitions/restrictions: embargo checks and licences triggered by tariff + country.

Integrations and reference data

• HMRC connectivity: stable channel for CDS API/submission and acknowledgements.
• Tariff service: scheduled refresh of UK tariff data and measures.
• Carrier/forwarder data: reuse shipment data to avoid double entry.
• Accounting: map duties/VAT to ledgers; export C79/VAT evidence.
• Document store: archive declarations, endorsements, and evidence with audit trails.

Go-live playbook

1. Pilot a small lane: one trade lane, real commodities, real parties.
2. Parallel run: submit in CDS and compare to legacy/exported drafts for a week.
3. Exception handling: define who resolves rejections, time-to-fix targets, and escalation.
4. Templates: prebuild declaration templates per customer/route to cut errors.
5. Training: short role-based guides for data entry, validation, and resubmission flows.