Who knows what in export and import control, and where it breaks

Sales knows what was promised to the customer. Logistics knows what physically left the dock. Trade compliance knows the classification and licence rules. The broker knows what was declared to customs. Finance knows what was invoiced, paid and booked. Trouble starts at the handoffs, where these versions quietly stop matching.

Sales holds the commercial terms

The salesperson negotiated the deal. They know the Incoterm, who pays freight and duty, and whether the price includes installation, tooling or software. They also know the side conversations: a free replacement part, a sample shipped ahead of the order, a discount agreed by phone.

None of that reliably reaches the shipping file. A sample goes out with no commercial value on the paperwork. A bundled price hides a software licence that carries its own export restrictions. The customs value then reflects the invoice line, not the real transaction, and the gap only surfaces when an auditor asks.

Logistics sees the physical goods

Warehouse and shipping staff see what actually goes in the box. They notice substitutions, split shipments and the spare part added at the last minute. They know which carrier turned up and what the driver signed for.

What they usually lack is the reason any of it matters. A substituted component may have a different tariff code or a different country of origin. A split shipment may need a second licence entry. Floor staff are measured on getting goods out on time, so a screening hold feels like an obstacle, and workarounds grow around it.

Trade compliance owns the rules

The compliance function maintains product classifications, origin determinations, licence records and restricted party screening. It knows which items are controlled, which destinations need extra care, and which free trade agreements apply.

Its blind spot is the order book. Compliance often learns about a transaction only when a shipment is already staged. It may not know that the end user differs from the buyer, or that a distributor plans to re-export. Classifications are set once when a product is created and rarely revisited when engineering changes the design. The master data ages while everyone assumes it is current.

The broker works from what was sent

An outside customs broker files the declarations. Brokers know the tariff schedules, the filing systems and the habits of the local customs office. They see every entry across all shipments, which no single internal team does.

But a broker can only declare what the paperwork tells them. If the commercial invoice is wrong, the entry is wrong. Many brokers pick a classification themselves when none is supplied, and that choice may never be checked against the internal record. The company remains liable for the declaration regardless of who typed it.

Finance, tax and the ledger

Accounts payable sees broker invoices, duty charges and freight bills. Accounts receivable sees customer invoices. Tax tracks import VAT recovery and duty drawback. Treasury may manage the deferment account or guarantee that customs draws on.

Finance rarely sees the entry itself. Duty gets coded to freight, or to a general expense line, and never gets matched to the shipment that caused it. Import VAT goes unreclaimed because the supporting customs document never reached the tax team. Overpaid duty on goods that qualified for preference sits unnoticed. When auditors request evidence for a sample of transactions, nobody can assemble the invoice, the entry, the proof of export and the payment without chasing several departments.

Where the gaps meet

Most failures are not one team getting its own job wrong. They come from two teams holding different truths about the same shipment. The declared value differs from the booked revenue. The product shipped is not the product classified. The party screened is not the party that receives the goods.

Controls built inside one function rarely catch this. A reconciliation that ties customs entries to the ledger, run on a regular cycle with someone accountable for breaks, catches far more than any single approval step. So does a documented cycle memo that shows, end to end, which system or person passes each piece of data to the next.

Questions to ask the people who run it

Written procedures describe the intended flow. These questions tend to reveal the real one.

• When a shipment is urgent, what step gets skipped, and who decides?
• Who tells the broker the tariff code, and what happens when nobody does?
• How are samples, warranty replacements and returns documented for customs?
• When engineering changes a product, who checks whether its classification still holds?
• Where does duty land in the ledger, and has anyone ever matched it back to the entries?
• Who receives the customs documents that support import VAT recovery?
• If a screening hit appears on a staged order, who can release it, and is that recorded?
• Has the broker ever corrected an entry after filing, and did anyone internally learn why?
• What would an auditor be unable to find today if they picked a shipment at random?

The answers will differ by person. That difference is the map of where the process actually needs work.

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.