Communicate with customs: what to automate, what stays human, and what the data needs

Software can already transmit declarations built from structured shipment data and match duty statements and broker invoices to the ledger. People must still own classification of unclear goods, valuation judgments and any reply that carries legal weight. None of it works until product and shipment data is clean.

What the work looks like on the ground

Communicating with customs is mostly paperwork with consequences. An entry is filed, often through a broker. Duties and import taxes are assessed and paid. Officers sometimes ask questions, place holds or request documents. Later, errors surface and need amending. Refunds and drawback claims flow back the other way. Finance sits in the middle because every one of these events touches cash, the ledger and the audit file.

The documented process usually shows a clean line from shipment to filing to payment. The real one has loops. A broker emails a query at an awkward hour. A supplier's invoice shows a different value from the purchase order. Someone in logistics answers an officer directly and nobody in finance hears about it.

Steps software can run now

Transmission is the easiest win. When the product master holds a confirmed tariff code and country of origin, and the commercial invoice arrives as structured data, a system can assemble and submit the declaration without anyone retyping fields. Status updates from the customs portal or the broker can feed a single tracking view, so holds and releases appear without someone chasing them by phone.

Payment handling also automates well. Duty statements and broker invoices can be matched against the entry, the purchase order and the receipt record. Anything that fails the match should be held, not paid, and routed to a named reviewer. Payment dates and amounts can be calculated by the system once the rules for deferment accounts or periodic statements are set up correctly.

Reconciliation is the other strong candidate. A routine that compares what customs says was charged with what was posted to the ledger, entry by entry, catches drift long before an auditor does.

Where AI helps but should not decide

Classification is the obvious place AI is being tried. A model can read a product description and propose a tariff code with its reasoning. That saves a specialist real effort on routine items. It should stay a proposal. A wrong code repeated across many entries becomes a liability, and the importer of record carries it.

Drafting is similar. AI can prepare a first reply to a routine information request, pull the relevant documents and summarise prior correspondence on the same product. A person reads it before it leaves.

Steps that need a person

Some decisions turn on judgment that no system holds. Valuation is the clearest case. Related-party pricing, royalties, assists supplied to a manufacturer and post-import price adjustments all change the declared value, and each needs someone who understands the commercial arrangement behind the numbers.

Disclosures of past errors need a human owner too. Deciding whether to correct quietly through an amendment or make a formal voluntary disclosure involves legal advice and an appetite for risk that belongs to named people.

Then there is the relationship itself. During an audit or a dispute over a penalty, officers deal with people. Tone, timing and what is offered up front matter. Software can organise the file. It cannot hold the conversation.

What the data must look like first

Before automating anything, check the product master. Each item that crosses a border needs a tariff code, an origin and a person accountable for keeping both current. If codes live in a broker's spreadsheet and nowhere else, automation will simply copy the broker's mistakes faster.

Shipments need a reliable link to the entry number and to the ledger posting. Without that thread, matching fails and every exception lands back on a desk.

Party data matters more than people expect. Importer numbers, broker identifiers and supplier records should agree across the purchasing system, the logistics system and finance.

Finally, documents must be retrievable. Customs can ask for records long after the goods have been sold. If invoices, packing lists and correspondence sit in personal inboxes, no workflow will find them on request.

Questions to ask the people who run it

• Who actually decides the tariff code when a new product is introduced, and where is that decision written down?
• When an officer contacts the business, who hears first, and how does finance find out?
• Which broker invoices get paid without being checked against the entry, and why?
• How are post-import price changes from suppliers reflected in declared values, if at all?
• What happens when a duty statement does not match the ledger? Who fixes it, and how long does it usually sit?
• Are there products that everyone knows are classified inconsistently but nobody has raised?
• Where would the team look tomorrow if customs asked for the full record of an old entry?
• Which steps are done from memory by one experienced person who has never been asked to write them down?

APQC's Process Classification Framework® (PCF) is an open standard developed by APQC, a nonprofit that promotes benchmarking and best practices worldwide. To download the full PCF or to view definitions and measures, please visit www.apqc.org/pcf.