Where trade preference processing breaks

Trade preference processing usually breaks where origin evidence passes between teams. Supplier declarations lapse unnoticed, and product changes reach customs filings before anyone rechecks qualification. The damage shows up as duty paid and later reclaimed, or as verification requests answered from memory because the supporting file was never complete.

Procurement hands over a supplier without origin data

Buyers onboard suppliers for price, quality and delivery. Origin is rarely on their checklist. The trade team learns about a new source only when a part appears on an import entry or in a bill of materials that needs qualifying.

By then the purchase order is live. Chasing a declaration from a supplier who has already been paid is slow and awkward.

How to tell: new part numbers sit in a holding status with no origin flag. Trade staff keep a personal list of suppliers to chase. Preference is claimed on finished goods while some inputs have no evidence behind them at all.

Supplier declarations expire quietly

Standing declarations cover a fixed validity window. Renewal depends on someone remembering. When that person moves on, the reminders stop, and claims continue on evidence that no longer covers the shipment dates.

This is the failure that hurts most in an audit, because the claim looked fine at the time.

How to tell: the declaration repository has no expiry field, or the field exists and nobody reports on it. Renewal requests go out in a rush just before a customs review.

Engineering changes bypass the qualification check

A product qualifies under a rule of origin based on its inputs. Swap a component, move an assembly step to another plant, or change a tariff heading on a subassembly, and qualification can flip. Engineering change processes seldom route to trade compliance.

How to tell: qualification records carry an older bill of materials revision than production uses. Origin determinations are dated well before the latest design change. Nobody can say who approves a sourcing switch from a preference standpoint.

Classification drifts between systems

The tariff code in the product master, the code the broker files, and the code used for the origin calculation should match. Often they do not. Brokers correct codes on their side to clear goods, and the correction never flows back.

How to tell: broker entries show codes absent from the master data. Customs queries mention a heading the internal team does not recognise.

The broker claims, or fails to claim, on assumption

Brokers act on standing instructions. If the instruction says claim preference for a product family, they claim it, whether or not this shipment qualifies. If the instruction is silent, they pay full duty to avoid risk.

How to tell: preference claims are uniform across a product family even where inputs differ. Full duty is paid on goods the trade team believes qualify. Duty reports from the broker are never reconciled against qualification records.

Exceptions turn into the real process

A spreadsheet built for a single urgent shipment becomes the place where qualification lives. Manual overrides in the trade system get approved once and then copied forward. Over time the documented workflow describes something nobody actually does.

How to tell: overrides outnumber system determinations. Staff refer to the spreadsheet by a nickname. Leave cover is impossible without the person who built it.

Refund claims fall behind

When evidence arrives late, the fix is to pay full duty now and claim a refund afterwards. Refund windows close. Finance often books the duty as a cost and never sees the recoverable amount.

How to tell: the trade team holds a backlog of unfiled post-entry claims. Finance cannot point to a receivable or accrual for expected refunds.

Verification requests expose the gaps

Customs authorities, or the importing customer, ask for proof of origin. The answer needs cost data, bills of materials, supplier declarations and production records that live with different owners.

How to tell: responses are assembled from scratch each time. Deadlines are extended by request. Cost accountants are surprised to learn their figures support an origin claim.

Questions to ask the people who run the process

The documented workflow often shows a clean handoff. The people doing the work can describe what happens instead.

• When a new supplier is added, at what point does anyone ask for an origin declaration, and who asks?
• Which declarations are renewed because a system prompts it, and which because someone remembers?
• Who hears about an engineering change before it reaches production?
• What does the broker do when a shipment arrives with no clear instruction?
• Where is the file that is used when the system answer looks wrong?
• When duty is paid in full on goods that should qualify, who decides whether to file for a refund?
• If customs asked tomorrow for proof on a recent claim, whose help would be needed to answer?
• Which overrides have been in place so long that nobody remembers why?

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.