Ask a customs broker where the time goes on an entry and the answer is almost never "filling in the declaration". Entering data into a filing system is mechanical and fast.

The time goes into everything before that: assembling a document set that arrives piecemeal from several parties, working out which document is authoritative when they disagree, classifying goods, applying the right valuation, checking whether anything requires a permit, and chasing whoever sent the invoice that does not match the packing list.

That is the work worth automating, and it is a reconciliation problem rather than a form-filling one.

The document set and why it disagrees

A typical import file involves a commercial invoice, a packing list, a transport document, a certificate of origin where preferential treatment is claimed, and a variable set of regulatory certificates depending on the goods.

They routinely disagree, for ordinary reasons: the invoice was issued before the shipment was finalised; the packing list reflects what was actually loaded; the transport document describes the goods in the carrier's own shorthand; quantities are expressed in different units; the invoice includes charges that may or may not be dutiable.

A person resolves these by knowing which document governs which field, which discrepancies are material, and which require going back to the shipper. That knowledge is largely codifiable.

The pipeline

Ingest and identify. Documents arrive by email, from portals, and from forwarders' systems, often as a mixed bundle. Split, classify, and associate to the correct shipment — which, as in other domains, is a multi-signal matching problem rather than a lookup.

Extract per document type, with provenance. Invoice: parties, terms, currency, line items with descriptions, quantities, unit prices, amounts, and any charges. Packing list: package details, quantities, weights, marks. Transport document: carrier, vessel or flight, ports, container and package details, gross weight. Certificates: issuing body, references, validity.

Normalise. Units to a common basis, currencies with the applicable rate and date, party names resolved against master data, descriptions cleaned.

Reconcile. This is the core step. Compare quantities, weights, package counts, values and descriptions across documents, applying a precedence model that says which document governs which field, with defined tolerances for the differences that do not matter.

Classify and value. Determine the tariff classification for each line and the customs value under the applicable basis, including which charges are dutiable.

Check requirements. Identify goods subject to permits, licences, restrictions or prohibitions; check whether the required documents are present and valid.

Produce the declaration, with every field traceable to a source document and region, and every unresolved discrepancy listed as an exception.

Reconciliation is the valuable part

A reconciliation engine that knows the precedence rules and the tolerances turns hours of cross-checking into a list of the genuine discrepancies.

Two design points make the difference between useful and irritating.

Tolerances must reflect reality. Minor weight differences between an invoice and a transport document are normal. A materially different package count is not. Set tolerances from actual data and from what the relevant authority treats as significant, and tune them by watching what reviewers dismiss.

Discrepancies must be actionable. A flag that says "quantity mismatch" is a starting point. A flag that says "invoice line 4 states 240 units; packing list states 200 units in 10 cartons of 20; transport document confirms 10 cartons" tells the broker both what the discrepancy is and, usually, which value is right.

Classification: assist, do not decide

Tariff classification is a legal determination with financial and compliance consequences, and it depends on the actual nature of the goods rather than on the words in the invoice description.

The appropriate automation is a strong assist: propose candidate classifications with the reasoning and the relevant notes, prioritise the shipper's and importer's own history for the same goods, flag where the description is too vague to classify, and surface previous rulings or determinations that apply.

Classification history is the most valuable input and the most underused. The same importer shipping the same goods from the same supplier should classify consistently, and a system that surfaces prior classifications for matching line descriptions is both more accurate and more defensible than one reasoning from the description alone.

What should not happen is silent automated classification of unfamiliar goods. A wrong classification is a compliance exposure that surfaces at audit, long after the entry cleared.

Valuation and charges

Customs value depends on the transaction value plus or minus specified adjustments — which charges are included depends on the delivery terms and on the applicable rules.

The mechanical parts automate well: reading the delivery terms, identifying charges on the invoice, applying the rules for which are dutiable, converting currency at the correct rate for the correct date. The judgement parts — related-party transactions, assists, royalties, unusual commercial arrangements — do not, and should route to a person with the relevant facts assembled.

Where errors are expensive

Customs errors have a long tail. An entry clears, and the problem appears at audit years later as a duty assessment with penalties and interest.

That changes the design priority. In most document workflows the cost of an escaped error is bounded and near-term. Here it is delayed and can be large, which justifies tighter thresholds, more human confirmation on classification and valuation, and complete retention of the evidence for every filed field.

The retention point is practical rather than theoretical: when an entry is questioned years later, the ability to show exactly which document supported each declared value, with the document itself, is the difference between a straightforward response and an expensive reconstruction.

Measuring it

  • Time from document receipt to a filed entry, split into assembly, reconciliation and filing.
  • Discrepancy detection rate, and the share that were genuine.
  • Discrepancy false-alarm rate per rule — the number that determines whether brokers keep using it.
  • Classification consistency for repeated goods, which is both a quality and a compliance measure.
  • Post-entry amendment rate, the honest outcome measure.
  • Query and hold rate from the authority, which reflects filing quality directly.

Want to see a filing prepared from raw documents?

Send us a real shipment file — invoice, packing list, bill of lading, certificates. We will show the reconciled declaration.

Book a Demo