Communicating with customs: what each role knows and where it breaks

Customs knowledge is split. The broker knows what was declared. Trade compliance knows what should have been declared. Payables sees duty only as a line on a broker invoice. The ledger sees a total. Trouble starts when one of them answers a customs query using only their slice.

The broker holds the declaration

The customs broker files the entry. It knows the tariff codes actually used, the values declared, the origin claimed and any preference applied. It also holds the correspondence with the customs officer: queries, holds, requests for documents. Much of this never reaches the importer's own systems. The broker sends a summary invoice, and the detail stays in its portal or its inbox.

Brokers classify fast and in volume. When product data is thin, they make a reasonable guess and move the freight. That guess then becomes the company's legal position.

Trade compliance holds the intent

The trade compliance lead knows the binding rulings the company holds, the classification decisions it has defended before, and which suppliers qualify for preferential origin. This person usually knows what ought to have been filed. Often they do not see what was filed until an audit or a demand letter arrives, because entries flow from broker to logistics without crossing their desk.

Logistics and procurement hold the physical and commercial facts

Logistics knows where the goods are and why they are stuck. Procurement knows the commercial terms: who pays duty under the agreed Incoterm, and whether the price leaves out tooling, royalties or design work that customs counts as part of value.

Neither group tends to think of these as customs facts. A buyer who agrees a separate tooling payment with a supplier has changed the dutiable value. Nobody tells the broker.

Payables sees an invoice, not an entry

Accounts payable receives the broker's bill. It mixes the broker's own fees with duty and import VAT paid on the company's behalf. The clerk matches it to a purchase order if one exists, routes it for approval and pays.

Payables cannot tell whether the duty is correct. It can only tell whether the bill resembles the last one. When an invoice fails validation and is held, some brokers stop advancing duty, and goods wait at the port while finance and logistics argue about whose problem it is.

The ledger and tax see balances

The controller sees duty as a cost, often folded into inventory or freight. The tax team needs import VAT kept apart so it can be recovered, and needs the authority's own statement to support that claim.

Reconciling the authority's statement of duty and VAT charged against what the ledger recorded is the step most often skipped. Without it, an overpayment or a missing VAT credit stays invisible until someone outside the company finds it.

Where the gaps turn into trouble

Customs questions arrive at whoever is named on the paperwork, which is rarely the person able to answer. A query on value goes to logistics, who forwards it to the broker, who guesses again. A demand for additional duty lands in payables as an unfamiliar invoice. It is either paid without challenge or left aside until interest and penalties build.

Adjustments after import are another weak point. When a supplier issues a credit note or a transfer price is trued up at the period close, the declared value is no longer right. Finance knows. Customs does not, unless someone files a correction, and nobody owns that decision.

Audits expose the scatter. An auditor asks for the full file behind a sample of entries, and the commercial invoice, the packing list, the broker's worksheet and the payment proof sit in different places owned by different people.

Changes to this process tend to fix one slice and damage another. A new payables workflow speeds up broker invoices but strips out the duty detail tax needs. A cheaper broker improves turnaround and loses the classification history the previous one carried.

Questions to ask the people who run it

What is written down and what happens on a busy day are often different. These questions surface the gap:

• When the customs authority sends a query, who actually replies, and where do they find the entry details?
• For a new product, where does the broker's tariff code come from, and does anyone check it before the first shipment?
• What happens to goods awaiting clearance when a broker invoice is on hold?
• How are duty, import VAT and broker fees separated in the books, and who does the splitting?
• Does anyone compare the authority's statement with the ledger? What happens to the differences?
• When a price changes after the goods have cleared, who decides whether customs needs to be told?
• Which payments to suppliers sit outside the purchase price, and does the broker ever hear about them?
• If an auditor asked today for everything behind one entry, who would assemble it, and from which systems?
• Which customs letters have arrived recently that nobody was sure how to handle?

The answers usually show that the person closest to the declaration is furthest from the money, and the person paying the duty has never seen the entry. Any redesign has to put those facts in the same place before it improves speed.

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.