Building a trade compliance programme that survives an audit

Ownership and authority to stop a shipment

The first component is a named person accountable for the area, with a reporting line that does not run through the function whose revenue depends on shipping. Without authority to hold a transaction, a compliance role can only document decisions it disagreed with. Senior sponsorship matters here because the moments that test a programme are commercially inconvenient by definition.

Master data decided once, not per shipment

Commodity codes, control classifications, origin determinations and preference eligibility are product attributes, and they belong in the product master where every transaction can inherit them. Deciding them shipment by shipment guarantees inconsistency, because two people looking at the same product on different days will not reach the same answer. Governance means a defined process for setting an attribute, recording the reasoning, and reviewing it when the product or the rules change.

Transaction controls that run automatically

Party and destination screening at order acceptance and again before despatch, licence checks tied to product attributes, blocks on shipping to destinations that require an authorisation the business does not hold, and validation that the documents required for a lane have been produced. Controls embedded in the order process work because nobody has to remember them; controls written in a manual are exercised in proportion to how busy the team is.

Records, retention and reconstruction

Retention periods run for years, and the test is whether a specific transaction can be reconstructed: what was shipped, to whom, under what classification and origin, on what authority, and who decided. Storing documents is not the same as being able to retrieve the story. A useful exercise is to pick a shipment from a year ago at random and try to assemble the file, which reveals gaps faster than any policy review.

Training, monitoring and voluntary disclosure

Training targeted at the people who make the decisions, meaning engineers who classify, salespeople who take end-use information and buyers who agree terms, is worth more than a general course. Periodic internal review, sampling entries and screening decisions, is how errors are found before an administration finds them. Where an error is identified, most regimes treat a disclosure made voluntarily very differently from one prompted by an enquiry, which makes the ability to find your own mistakes a financially significant capability.

Frequently asked questions

How large does a business need to be before this is worth doing?

The trigger is exposure rather than headcount. A small company exporting technical products to many destinations carries more control risk than a large one importing a single low-duty commodity. The programme should be scaled to the transactions, and even a very small operation benefits from written classifications and a screening step.

Does having a programme reduce penalties if something goes wrong?

Administrations commonly take the presence and quality of internal controls into account when deciding how to respond to an error, and a documented programme supports an argument that a failure was isolated rather than systemic. It is not a shield, and a programme that exists only on paper is worse than none because it evidences that the risk was recognised and not managed.

What is the most common gap?

The link between technical knowledge and shipping decisions. Classification, control status and origin all depend on facts held by engineering and purchasing, while the decisions are executed by logistics. Programmes that fail usually fail at that handover rather than at the frontier.