ANELGO GLOBAL LOGISTICS
Shipping guides / Guides · Export declaration errors checklist

Export Customs Declaration Errors Checklist: Common Mistakes to Spot Before Filing

Guides · Export declaration errors checklist · Reviewed November 18, 2026 · 10 minute read

Blank export declaration documents with a red pencil and a checklist clip on a wooden desk, with a port softly blurred in the background
Illustrative AI-generated image.

A vague product name, a code that does not match the name, or a declared value that does not match the invoice is the most common reason an export declaration is returned. This checklist lists thirty common errors in four stages, to spot and fix before the declaration is filed.

How to use this checklist

This page covers common errors only: the mistakes that appear again and again on an export declaration — a vague product name, a code that does not fit the name, a wrong quantity unit, a declared value that does not match the invoice, and origin papers that do not match the declaration. It does not repeat the export customs declaration elements checklist on this site, which checks each field one by one before the declaration is filed. It does not repeat the export declaration rejection checklist, which covers the reasons a filed declaration is turned back. It does not repeat the US import customs declaration errors checklist, which covers the same errors on the import side. Use this page to spot the errors; use those pages for the field-by-field check, the rejection reasons and the import side.

Work through the four stages in order, with the declaration draft, the commercial invoice, the packing list and the transport paper copy open beside this page. Read each field on the declaration against the same field on the invoice and the packing list, and ask, for each field, what the error would look like if it were wrong. Where a field looks wrong, mark it on the file and ask the broker in writing which version is right before the declaration is filed.

An error on the declaration is often a copy error: a figure copied from an earlier shipment, a name copied from a sales sheet, or a code copied from a different product. The exporter supplies the goods data, the broker files the declaration, and the forwarder passes on the transport papers, so an error can enter at any of those three points. Ask for every figure, code and name in writing before the declaration is filed, and keep the written answers with the declaration file.

Stage 1 — Vague product names

Stage 1 covers the most common error of all: a product name that does not describe the goods. A name that is vague, or that is a trade name only, tells the reader nothing about what is in the shipment, and it is the error most often found on a returned declaration.

Read the name on each line beside the goods it describes, and ask whether a stranger could tell what the goods are from the name alone. Where the name is a trade name or a brand name only, ask the supplier for the plain description of the goods. Where the name on the declaration differs from the name on the invoice, stop and ask the supplier in writing which version is right.

Stage 2 — Code does not match the name

Stage 2 covers the error where the code and the product name point in different directions: the code covers one kind of goods and the name describes another. A code copied from an earlier shipment, or read apart from the name beside it, is a common reason a declaration is returned.

Check the code on each line against the tariff schedule, and read the product name beside the code to see whether the name describes the goods the code covers. Where the code is uncertain, ask the broker in writing which code the declaration should use, and keep the written answer with the declaration file.

Stage 3 — Wrong quantity, unit and value

Stage 3 covers the figure errors: a quantity unit that does not fit the goods, a quantity that differs between the declaration and the invoice, or a declared value that does not match the invoice. A single wrong figure can hold the whole declaration.

Compare the quantity, the unit, the unit price and the value on the declaration against the same figures on the invoice and the packing list, line by line. Check the currency on the declaration against the currency on the invoice, and check the value basis against the trade terms. Where a figure differs between two papers, stop and ask the broker in writing which paper is right.

Stage 4 — Origin and filing errors

Stage 4 covers the remaining errors: origin papers that do not match the declaration, trade terms that differ between the papers, and fields left blank or copied from an earlier filing. An origin statement without papers to support it is an error on its own.

Check the trade terms and the origin against the invoice and the papers that support the origin. Check the exporter, the consignee and the port against the booking and the transport paper. Read the whole declaration once more from the first line to the last, with the invoice and the packing list beside it, and mark every field filled or marked not applicable.

Which error should be fixed first?

Every declaration has one error that needs the closest look, and it depends on the goods: a shipment with a vague name needs the name fixed first, a shipment with a code question needs the code fixed first, a shipment with a value error needs the value fixed first, and a shipment where the origin is claimed needs the origin fixed first. The table points to the right stage for each case.

CaseWhen it appliesWhat to check first
Vague product nameThe name is a trade name only, or a vague word stands as the whole nameStart at Stage 1, write the plain description of the goods beside the trade name, and ask the supplier to confirm it in writing
Code does not match the nameThe code covers one kind of goods and the name describes anotherStart at Stage 2, check the code against the tariff schedule with the broker, and read the name beside the code
Declared value does not match the invoiceThe value, the unit price or the currency differs between the papersStart at Stage 3, compare the value, the unit price and the currency against the invoice, and check the value basis against the trade terms
Origin claimed without papersThe declaration states an origin that the papers do not supportStart at Stage 4, check the origin statement against the papers that support it, and attach those papers with the declaration

Common reasons declaration errors happen

Most declaration errors share the same few causes. A figure or a code is copied from an earlier shipment for different goods, so the declaration describes goods that are not in this shipment. A name is copied from a sales sheet, so the declaration carries a trade name that does not describe the goods. The declaration, the invoice and the packing list are prepared by different people, so the same field is written differently on each paper. A figure is typed from memory instead of read from the invoice, so the value on the declaration does not match the value on the invoice.

The fix is the same in each case: stop copying from earlier shipments, read each field from the paper that states it, and compare the declaration against the invoice and the packing list line by line before the declaration is filed. Write the plain description beside any trade name, check the code against the tariff schedule for the goods as shipped, and ask the broker in writing where a field is still in question. Keep the written answer with the declaration file, so the next shipment starts from a correct declaration rather than a copied one.

What this checklist cannot decide

This checklist cannot decide which code applies to a given product, or which product name a customs office will accept: those follow the tariff schedule, the goods themselves and the broker who files. It cannot say whether a declaration with an error will be returned, and it cannot set the declaration result: that follows the papers, the code and the customs check.

It also cannot replace the broker's advice on a specific declaration. Where a request names an error this checklist does not cover, or a code is disputed, ask the broker in writing before the next step. It cannot file a declaration for goods never booked, and it cannot turn a declaration filed with the wrong goods data into a correct one without a fresh check of the papers.

Export guides on this site

Related guides

Official references

Note: This guide provides general logistics planning information. It is not legal, customs, tax, safety or carrier acceptance advice. Requirements, services and schedules depend on the actual goods, route, contract, provider and current rules. Verify shipment-specific questions with the responsible carrier, customs broker or authority before dispatch.

For a route-specific logistics review, provide the product, origin, destination, packed dimensions, weight and ready date.

Request a shipment review ↗

Frequently asked questions

What is the most common error on an export declaration?

A product name that does not describe the goods. A trade name only, or a vague word such as parts or accessories standing as the whole name, tells the reader nothing about what is in the shipment. Write the plain description of the goods beside the trade name, and ask the supplier in writing to confirm that the name describes the goods as shipped.

How can an error be spotted before the declaration is filed?

Read the declaration against the invoice and the packing list line by line, with all three papers open at once. Compare the name, the code, the quantity, the unit, the value and the origin on each line, and read the code beside the name it belongs to. An error found while the papers are still open can be fixed before the declaration is filed; an error found after filing follows the request route instead.

Who can confirm that a declared element is right?

The broker who files the declaration can check each element against the papers, and the supplier can confirm the name and the code for the goods as shipped, but only the customs office that reads the declaration decides whether an element is right. Ask the broker in writing where a field is in question, and keep the written answer with the declaration file.

← More shipping guides