Process trade preferences: when a claim outlives the origin behind it

The most common failure is a preference claim that keeps running after the goods stop qualifying. A supplier swaps a component or a declaration lapses, and nobody reruns the origin check. Reduced duty continues to be claimed on entries while the legal basis for it has quietly disappeared.

How it starts

Preferential treatment under a trade agreement depends on origin. Origin depends on the bill of materials, where each input came from, and what processing happened where. Those facts change all the time. The preference flag on a product master record usually does not.

A typical sequence looks like this. Procurement finds a cheaper resin from a non-agreement country. Engineering approves the substitution. The part number stays the same, so the customs team sees no new item and no prompt to recalculate. The broker keeps filing the claim because the master data says the product qualifies.

Supplier declarations cause the same drift from another direction. They are collected once, filed, and assumed to roll forward. When one expires or the supplier's own sourcing shifts, the claim rests on a document that no longer says what it needs to say.

Neither event is dramatic. That is why it persists. Each team did its own job correctly, and the gap sits between them.

How it gets spotted

Sometimes the customs authority finds it first, through a verification request asking for proof of origin. When the file cannot support the claim, the problem surfaces in the worst possible way: under deadline, with an external party watching.

Internal detection is better and usually comes from one of these places:

• A reconciliation between preference claims on entries and the list of products with current, valid origin determinations. Claims with no matching determination stand out quickly.
• A supplier declaration register that shows expiry. Any active claim relying on an expired declaration is a lead worth chasing.
• Engineering change notices or new vendor setups touching a product that carries a preference flag.
• A customer asking for an origin statement and the team discovering the supporting analysis is stale.

Finance can also notice it indirectly. A duty line that stays flat while sourcing costs move sharply is a hint that the origin picture changed and the customs side did not follow.

Fixing the claims already made

Start by stopping new claims on the affected products. Change the master data, tell the broker in writing, and confirm the next entries file at the full rate. Speed matters more than elegance at this point.

Then rebuild the origin determination from current facts. Pull the actual bill of materials, confirm the source of each input, and apply the agreement's rule for that tariff classification. Some products will turn out to qualify after all, perhaps under a different rule or with fresh supplier evidence. Others will not.

For entries that claimed preference without support, work out which shipments are affected and when the change took effect. This is often the hardest part, because the date a component was swapped is buried in purchasing history. Once the scope is known, the usual route is a correction or voluntary disclosure to the customs authority, paying the duty owed. Involve tax and legal before filing. Disclosure rules and the treatment of penalties differ by country, and the way the correction is presented matters.

If goods were exported under preference to customers abroad, the problem may be theirs too. Origin statements issued to them may need withdrawing, and they may face their own duty corrections. Tell them early.

Stopping it coming back

The durable fix links origin to the events that change it. Engineering change control and new supplier onboarding should both check whether the affected item carries a preference claim. If it does, the change waits for an origin review or triggers one automatically.

Supplier declarations need an owner and a renewal routine tied to their expiry, with active claims suspended when evidence lapses. Origin determinations themselves should carry a review date and the bill of materials version they were based on, so a mismatch is visible.

It also helps to make the duty saving visible to procurement. A sourcing decision that looks cheaper per unit can cost more once the lost preference is counted.

Questions to ask the people who run it

What is written down and what happens on the floor often diverge here. Ask the people involved directly:

• When a component changes, who tells the customs team, and how do they find out in practice?
• Where do supplier declarations live, and who notices when one expires?
• Does the broker ever claim preference based on their own records instead of instructions from here?
• Which products were qualified once and never looked at again?
• If a verification request arrived tomorrow, which origin files would be hardest to defend?
• Has anyone ever turned off a preference claim, and what prompted it?
• Do procurement staff know which items depend on agreement origin when they choose a new source?

Hesitation on any of these usually points to where the next lapsed claim is sitting.

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.