10-Point Import Declaration Errors Checklist

A declaration can be accepted by CDS or ROS and still create a problem later. A commodity code may trigger the wrong duty treatment, an understated customs value can lead to a post-clearance query, and a missing licence can leave goods held at the frontier. This import declaration errors checklist is designed for the operational point that matters most: before the declaration is submitted and the lorry, container or consignment is waiting.

For regular UK-Ireland movements, the best approach is not to rely on one final pair of eyes. Build these checks into the order, shipping and declaration process, then make sure the person submitting the entry has the information and authority to resolve exceptions.

Why small declaration errors become expensive

Customs declarations bring together commercial, transport and regulatory data. Much of it is supplied by different people: a supplier provides an invoice, a warehouse confirms quantities, a freight forwarder supplies movement details, and an importer decides the customs procedure. When those details do not align, the declaration may be delayed, rejected or accepted with an error that becomes a compliance risk.

The immediate cost is often storage, demurrage, missed delivery slots or disruption to production. The longer-term cost can be more serious: incorrect duty and VAT accounting, lost preference, customs debt, amendments and audits. A short pre-submission control is usually far cheaper than correcting an entry after release.

Import declaration errors checklist: 10 checks before submission

1. Confirm the importer and declarant details

Check that the importer’s EORI is valid for the territory where the declaration is being made and that the business named on the commercial paperwork is the party shown on the entry. Do not assume that the buyer, consignee and importer of record are always the same entity.

Also confirm who is acting as declarant and whether the required customs representation is in place. Indirect representation has different responsibilities from direct representation, so this is not simply an administrative field. If an agent is submitting declarations, the authority and instructions should be current and documented.

2. Match the goods description to the commodity code

A vague description such as “parts”, “samples” or “equipment” is rarely enough to support classification. The description should identify what the goods are, what they are made of, their function and, where relevant, model, composition or intended use.

The commodity code must reflect the actual product, not the code used on an old shipment or suggested on a supplier invoice without review. Similar goods can have different codes depending on material, technical specification or purpose. Where classification is uncertain, pause and obtain a defensible decision rather than treating the tariff code as a best guess.

3. Check quantities, units and packaging data

The invoice quantity, packing list quantity and declared quantity should reconcile. This sounds basic, but partial shipments, back orders, split consignments and different units of measure regularly create errors.

Pay particular attention to supplementary units required by the tariff. A declaration can contain the correct number of cartons but the wrong net mass, litres, square metres or number of items. Net mass should relate to the goods themselves, excluding packaging. Gross mass and package details must also reflect the transport documentation where those data elements are required.

4. Establish the customs value properly

Customs value is not always the amount shown at the bottom of the invoice. The starting point is commonly the transaction value, but additions may be needed for costs such as freight, insurance, commissions, assists, royalties or packing, depending on the terms and circumstances of the sale.

Incoterms matter here . For example, freight may be included in an invoice price even though part of the journey falls outside the customs valuation basis. Currency conversion, discounts, related-party sales and goods supplied free of charge also need careful treatment. Keep evidence showing how the value was calculated, not just the final figure entered on the declaration.

5. Separate country of origin from country of dispatch

Origin and dispatch are different concepts. Goods dispatched from an EU member state may have originated elsewhere, while goods moving from Great Britain to Northern Ireland may require a separate assessment of origin, procedure and applicable requirements.

Where a preferential duty claim is being made under a trade agreement, confirm that the goods meet the relevant rules of origin and that the required proof or statement is available. A supplier’s country on an invoice is not proof of preferential origin. If the evidence is incomplete, it may be safer to declare without preference and consider a repayment claim later if eligibility can be substantiated.

6. Use the correct customs procedure and additional codes

The procedure code tells customs why the goods are entering the territory and what treatment is being requested. A standard free-circulation import is different from inward processing, customs warehousing, temporary admission, returned goods relief or a declaration linked to a prior procedure.

Check the procedure code, any additional procedure codes and all supporting document codes together. An apparently minor mismatch can result in the wrong duty outcome or invalidate a relief claim. If goods are being discharged from a special procedure, make sure the previous declaration reference and discharge information are correct before submission.

7. Identify licences, certificates and controlled goods requirements

Commodity coding can trigger measures beyond customs duty. Depending on the goods, you may need licences, health certificates, catch certificates, import permits, safety documentation or other regulatory evidence.

Do not leave this check until the goods have arrived. Controlled products may include food and animal products, plants, chemicals, dual-use goods, firearms, waste, cultural goods and products subject to sanctions restrictions. The precise requirement depends on the product, origin, destination and use. Where a licence is required, check its validity, quantity limits and that the declaration data matches the licence exactly.

8. Reconcile the commercial and transport documents

The invoice, packing list, purchase order, bill of lading or CMR, arrival information and customs entry should tell the same commercial story. Compare supplier and buyer names, invoice number and date, currency, goods description, package count, weights and transport reference.

Discrepancies are not always errors. A transport document may show a consolidator, or an invoice may cover more goods than the shipment. The key is that the difference is understood and the declaration represents the actual consignment. Record the explanation so a colleague, agent or customs officer can follow the audit trail.

9. Check duty, import VAT and payment instructions

Before submission, review the calculated duty and VAT against a realistic expectation. A zero duty result should have a clear reason, such as a valid preference claim, relief, suspension or tariff measure. An unexpectedly high charge can reveal an incorrect code, origin, value or procedure.

For UK imports, confirm whether import VAT will be paid at the border or accounted for through postponed VAT accounting, and ensure the importer has authorised the intended method. For Irish declarations, confirm the correct ROS arrangements and financial account details. A declaration is not operationally complete if the payment route cannot support release of the goods.

10. Validate references, timing and record keeping

The final check is practical: are the declaration references, transport references and border movement details correct for the route? Depending on the movement, this may include a master or house transport reference, vehicle registration, inventory reference, MRN, Goods Movement Reference,PBN details or safety and security data.

Submit early enough to resolve a rejection without stopping the movement. After acceptance, retain the declaration, acceptance messages, invoices, valuation evidence, origin records, licences and correspondence in an organised file. Customs records need to support the entry years after the shipment has been delivered.

Turn the checklist into a working control

A checklist only improves compliance when it is owned. Assign clear responsibility for product classification, valuation, origin evidence, document collection and final declaration approval. For a small importer, one trained administrator may perform several roles. For a 3PL or freight forwarder, responsibilities may sit across customer service, customs operations and transport planning.

It also helps to classify checks by risk. Routine repeat products with stable supplier data may need an exception-based review, while a new supplier, new commodity, changed Incoterm or preferential origin claim should trigger a fuller check. This avoids slowing every shipment while focusing attention where the exposure is highest.

Customs software can reduce transcription errors by storing product data, applying validation rules and connecting directly to government systems. It does not replace informed judgement. Teams still need training to recognise when a code, value, origin claim or procedure needs escalation. Custran supports businesses that want to process declarations in-house, use an agency service, or combine both approaches when internal capacity changes.

The most useful closing habit is simple: treat every correction as a process signal. If the same error appears twice, update the product record, supplier instruction or staff guidance before it affects the next consignment.