Processing trade preferences: how the process runs step by step

Processing trade preferences means proving goods qualify for reduced duty under a trade agreement, then claiming or granting that benefit shipment by shipment. Trade compliance owns the origin rules. Procurement gathers supplier evidence. The customs broker files claims. Finance confirms the savings and keeps the audit trail.

The steps in order

1. Decide which agreements matter. Trade compliance maps the shipping lanes where an agreement exists between the origin and destination countries. Finance supplies duty paid by lane so the team can see where a claim is worth the effort. Some lanes are dropped here because the saving would not cover the cost of proving origin.

1. Confirm tariff classification. The product data team or trade compliance assigns each item its tariff code. Get this wrong and everything downstream fails, because the rule of origin is tied to the heading.

1. Request origin evidence from suppliers. Procurement sends declaration requests to vendors of purchased parts and finished goods. Some suppliers answer quickly. Others need chasing, and a few refuse outright. Buyers own the follow-up because they hold the commercial relationship.

1. Qualify manufactured goods. For items the business makes itself, trade compliance tests the bill of materials against the product-specific rule. That may be a change in tariff heading or a regional value content test. Cost accounting provides material and conversion costs. Engineering confirms the bill reflects what is actually built.

1. Store the result in master data. A master data analyst flags each item and agreement combination as qualifying or not, with a validity window. Shipping and import systems read this flag, so a stale entry causes wrong claims at scale.

1. Issue proof of origin on exports. The export desk prints an origin statement on the commercial invoice or arranges a certificate from the issuing body. Where an approved exporter number is required, it must appear on the document. Customers often ask for supplier declarations covering a period of shipments. Customer service routes those requests to trade compliance.

1. Claim the preference on imports. Logistics instructs the customs broker which shipments qualify. The broker enters the preference indicator on the entry. Proof of origin should be in hand before filing. The broker sees only what logistics passes along, so gaps here are common.

1. Recover missed claims. When a qualifying shipment entered at full duty, trade compliance files a post-entry refund request within the window the destination country allows. Accounts receivable or treasury watches for the refund and matches it to the original entry.

1. Reconcile duty and report the benefit. The finance team compares duty paid against the duty that would have applied without preference. Results feed landed cost, product margin and the case for keeping the programme funded.

1. Retain records and answer verifications. Trade compliance keeps the qualification files, supplier declarations and shipping documents for the retention period each authority sets. When customs sends a verification request, the team assembles the file and may need a supplier to open its own records.

1. Revalidate after any change. A new supplier, a design change or an amended agreement can break qualification. Procurement and engineering are meant to notify trade compliance, which reruns the analysis and updates master data.

Where the work actually stalls

Supplier responses are the usual bottleneck. Buyers treat the declaration request as an administrative chore and it slips behind price and delivery issues.

The handoff between master data and the broker is the other weak point. If the flag is correct but logistics never tells the broker, the preference is lost. If the flag is wrong and the broker files anyway, the business faces duty, interest and possibly penalties after an audit.

Cost data also ages. A value content calculation built on last year's costs may no longer pass, and nobody reruns it unless a trigger exists.

Questions to ask the people who run it

• When a supplier does not return a declaration, what happens next, and who decides to stop claiming on that part?
• How does the broker learn that a shipment qualifies? Is it a standing instruction, a field on the order, or an email someone remembers to send?
• Who updates the origin flag when engineering changes a bill of materials, and how do they find out the change happened?
• Which agreements are claimed in practice, and are any listed in the procedure but never used?
• How often are refund requests filed for missed claims, and who spots them?
• Where do the qualification files live? Could the team produce one for a specific shipment if an auditor asked tomorrow?
• What does the export desk do when a customer demands a certificate the item has not been qualified for?
• Which cost figures feed the value content test, and when were they last refreshed?
• Has a verification request ever come in? What went wrong, and what changed afterwards?
• Are there workarounds, spreadsheets or personal trackers that the documented procedure does not mention?

The answers to the last question usually reveal how the process really runs. Informal trackers often hold the only accurate picture of supplier status, and removing them during a redesign without replacing their function creates new gaps.

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.