Classification drift: a common failure in export and import control

A common failure in controlling exports and imports is classification drift. A product changes, but its tariff code and export control classification in the item master stay as they were. Goods then cross borders under the wrong code. The wrong duty gets paid, or a licence requirement is missed entirely.

How it starts

The trigger is almost never a trade decision. It is an engineering change, a new supplier, a repackaged kit or a firmware update that adds encryption. The product team updates the bill of materials and the specification. Nobody tells the trade compliance desk, because nothing in the change workflow asks whether the customs code still holds.

The item number usually stays the same. That is the trap. Shipping systems pull the classification from the item record, and the record looks perfectly valid. Brokers file entries on the data they receive. Export screening runs against the old control code and clears the order.

Mergers and system migrations make it worse. Classifications get copied across in bulk, often from whichever source was easiest to load, and the original rationale for each code is lost along the way.

Where it shows up

Rarely in the trade team's own reports. The first hint tends to come from outside.

A customs broker queries an entry because the declared description no longer fits the code. A customs authority issues a request for information or opens a post entry review. A customer abroad reports that their own import was held because the paperwork did not match the goods.

Finance can catch it earlier, if anyone looks. Duty paid per item starts to move for no commercial reason. Landed cost variances appear on a product line that has not changed price. Duty drawback or preferential origin claims get rejected, and the rejections sit unexplained in an accounts payable queue.

Internal control reviews are another route. When auditors ask for supporting documents on a sample of shipments, the team pulls the classification ruling or worksheet for each item. Sometimes that file describes a product the company stopped making long ago.

Questions to ask the people who run it

The written procedure usually says classifications are reviewed on change. Practice often differs. These questions tend to expose the gap:

• When engineering changes a product, who tells the trade desk, and how? Is it a field in the change request or a hallway conversation?
• Who is allowed to edit the tariff and export codes in the item master, and does anyone review those edits?
• When a broker queries an entry, where does that query go? Does it ever reach the person who owns the item record?
• Is there a written rationale behind each classification, or only the code itself?
• How do new items get a code when the specialist is unavailable? Is there a default, or a copy from a similar item?
• Who in finance looks at duty variances, and what do they do when one cannot be explained?

Listen for workarounds. A planner who copies codes from a sister product to keep an order moving is a sign the control is too slow, not just that someone broke a rule.

Fixing the records already wrong

Start by fencing the problem. Identify every item touched by the change and every shipment since the change took effect. Hold further exports of affected items until the correct control status is confirmed, because an unlicensed export is far harder to unwind than an overpaid duty.

Reclassify with evidence. Document the product as it now exists, the code chosen and the reasoning. Have a second qualified person check it.

Then deal with the history. Underpaid duty may call for a correction filing or a voluntary disclosure. Overpaid duty may be recoverable through a refund claim. Export errors need legal advice on disclosure before anyone contacts an authority. Finance should book the adjustments and keep the trail, since auditors will ask how the correction was quantified and approved.

Record the findings and the adjustments in the cycle memo for the process. That memo is what the next audit will test against.

Stopping it coming back

The durable fix sits upstream. Add a mandatory trade review step to the product change workflow, with the trade desk as an approver for any change to materials, function, origin or software. Make the change record unable to close until that approval exists.

Lock the classification fields in the item master so only trade staff can edit them, and log every edit. Store the rationale alongside the code, not in a personal folder.

Route broker queries and customs correspondence into a shared queue that the item owner can see. Give finance a standing report of unexplained duty variances and a named contact on the trade desk to send them to.

Finally, test the control. Pull a sample of recently changed items as part of routine compliance review and confirm that each one went through trade approval. Where one did not, treat it as a finding and trace why the workflow let it through.

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.