How to Submit CDS Declarations Correctly

The pressure usually starts when the goods are ready, the haulier is asking for clearance status, and someone realises a CDS entry still has not been submitted. That is why understanding how to submit CDS declarations matters so much. It is not just an admin task. It affects whether your goods move on time, whether duty is calculated properly, and whether your business avoids costly rework after the fact.

For many UK importers, exporters and intermediaries, CDS can feel harder than CHIEF ever did, mainly because the data requirements are more structured and less forgiving. But the process is manageable when you break it down into the operational steps that sit behind a valid declaration. The key is getting the data right before you ever press submit.

How to submit CDS declarations without delays

Submitting through CDS starts well before the actual transmission to HMRC. In practice, the declaration is only as good as the information feeding it. If your commodity code is wrong, if your valuation does not match the commercial paperwork, or if the procedure code does not fit the movement, the system may reject the declaration or accept it with errors that create problems later.

The first job is to confirm what kind of declaration you are making. That sounds obvious, but it is where many delays begin. An import declaration into free circulation is not the same as a temporary admission, a customs warehousing movement, or a supplementary declaration. Exports have their own requirements again. The declaration type determines which data elements are mandatory and how HMRC expects the transaction to be reported.

Once the declaration type is clear, you need the core shipment data in place. That usually includes the EORI number, importer or exporter details, declarant details, Incoterms, invoice values, currency, origin, gross and net mass, package information, transport details, and any licences or document references that apply. If the movement is through a port using GVMS or another border process, the customs data also needs to align with the wider transport workflow. A technically correct declaration can still cause disruption if the transport references do not match what the carrier or port system expects.

The data you need before you submit

If you want to know how to submit CDS declarations accurately, start by looking at data quality rather than software screens. Most submission issues come from missing or inconsistent source information.

Commodity codes are one of the biggest risk areas. The code drives duty, VAT treatment, measures, licensing and sometimes even whether the goods can move at all. If you are relying on an old code, a supplier description that is too vague, or an internal stock code with no customs logic behind it, the declaration may be wrong from the outset. The same goes for customs value. Charges such as freight, insurance, assists or commissions may need to be considered depending on the terms of sale and the type of movement.

Procedure codes matter just as much. They tell HMRC what customs treatment you are claiming, and they need to fit the actual movement and the trader’s authorisations. A simple free circulation import may be straightforward, but inward processing, returned goods relief or customs warehousing require more care. If the procedure code is wrong, the declaration can still look complete while creating a compliance problem in the background.

It is also worth checking whether additional procedure codes, document codes or statement references are required. These are easy to miss when teams are under pressure, especially if declarations are being handled by staff who only submit entries occasionally. This is where a well-structured software workflow or a trained customs resource can make a real difference.

The practical submission process in CDS

At the point of submission, the declarant enters or uploads the required data into software connected to CDS, validates the entry, and transmits it to HMRC. Most businesses do not work directly in raw government messaging. They use customs software that translates operational data into the right CDS format and returns the response messages in a usable way.

A practical workflow usually looks like this. First, create the declaration record and choose the right movement type. Next, populate the trader, goods, value and transport data. Then apply the correct commodity codes, procedure codes and document references. After that, run validation checks before transmitting to HMRC.

If the declaration is accepted, CDS will issue response messages that confirm the status of the entry and, where relevant, the calculation of duties and taxes. Depending on the movement, you may then need to link the declaration to a port inventory, GVMS movement, safety and security process, or downstream transit step. Submission is only one part of the operational chain.

If the declaration is rejected, the response message will normally identify the field or rule that failed validation. Some rejections are simple formatting issues. Others point to a deeper problem, such as an invalid combination of procedure code and authorisation type, or a mismatch between declared values and data rules. The fastest way to deal with these is to treat them as process issues, not one-off mistakes. If one declaration failed for a certain reason, there is a fair chance the next one will too unless the source data or internal guidance is corrected.

Common mistakes when learning how to submit CDS declarations

One common mistake is assuming that invoice data can be copied straight into the declaration without adjustment. Commercial invoices are essential, but they are not written to customs data standards. They may use incomplete product descriptions, group several items in ways that do not fit tariff classification, or omit details needed for valuation.

Another frequent problem is using the wrong declarant model. Some businesses submit entries in-house but are unclear whether they are acting as declarant in their own name or through an intermediary arrangement. That distinction matters because it affects legal responsibility and the structure of the declaration.

There is also the issue of timing. Some teams wait until the goods are physically at the port before starting the entry . That can work for simple, repeat movements, but it leaves very little room if anything is missing. For higher-volume operations or mixed consignments, it is better to prepare declarations earlier and use a workflow that flags missing data before the vehicle is due to travel.

A final issue is overconfidence with repeat products. Businesses often assume that because a commodity moved successfully last month, nothing needs checking this month. But tariff measures, licensing conditions, values and commercial arrangements can change. Customs compliance is repetitive, but it is not static.

When to submit in-house and when to ask for support

There is no single right operating model for every business. Some companies should process their customs declarations in-house because they have predictable flows, trained staff and a need for direct control. Others are better served by an agency model, especially if volumes are low, movements are irregular, or specialist procedures are involved.

A hybrid model often works best in practice. Routine declarations can be managed internally through easy to use software, while more complex entries, audits or exception handling are escalated for expert review. That gives businesses control without leaving operational teams exposed when customs rules become less straightforward.

This is particularly relevant for UK and Ireland trade, where customs entries often sit alongside ferry booking data, border references, transit movements and safety filings. The declaration itself may be only one piece of a wider operational chain. If your team is spending too much time keying data, chasing missing references or correcting the same errors repeatedly, the problem may not be staff effort. It may be that the customs process needs better system support, better training, or both.

Building a reliable CDS process

The most reliable CDS submissions come from a repeatable process, not from individual heroics. That means clear ownership of commodity code governance, standard rules for valuation and Incoterms, documented procedures for import and export scenarios, and a system that validates data before it reaches HMRC.

Training matters as well. Customs is one of those functions where small misunderstandings can have large operational consequences. Giving staff a checklist helps, but it is rarely enough on its own. They need to understand why certain data matters and what to do when a shipment does not fit the standard pattern.

For businesses scaling up post-Brexit customs activity, this is where a practical partner can add value. Custran’s approach is built around making customs simple, whether that means helping a business process declarations in-house, supporting staff with training, or stepping in with agency support when extra resource is needed.

If you are working out how to submit CDS declarations more consistently, focus less on the final button press and more on the process behind it. Good customs performance comes from accurate data, the right controls and support that fits the way your operation actually runs. When those pieces are in place, declarations stop being a daily fire fight and start becoming part of a steady, dependable trade flow.