Sanctions & Trade Controls Interface
Some onboarding and payment reviews require controls beyond name screening: goods, services, customs codes, end-use and restricted trade exposure.
The control sits at the intersection of AML, sanctions compliance, payments and trade finance.
1. When the control is triggered
Use this interface when the customer, counterparty or transaction involves physical goods, controlled technology, trade finance, import/export activity, high-risk jurisdictions, sanctions-sensitive sectors or goods descriptions that require classification.
2. Inputs reviewed
| Input | Review purpose |
|---|---|
| Goods description | Identify whether the product is ordinary, dual-use, restricted or inconsistent with the customer's profile. |
| HS / customs / TARIC / TN VED-style code | Map the code to product classification and trade-control restrictions. |
| Origin, destination and routing | Assess sanctions, embargo, diversion and geographic exposure. |
| Counterparties and logistics providers | Screen parties involved in the trade chain. |
| End-use and end-user | Assess whether stated use and final recipient are plausible and permitted. |
3. Review workflow
- Collect goods description, code, invoice, contract and shipping route.
- Check the code and description against official or approved trade-control sources.
- Screen parties, banks and logistics entities.
- Compare the transaction with the customer's business model and expected activity.
- Escalate sanctioned, restricted, unclear or inconsistent results for manual review.
- Preserve code search, source evidence, date, result, decision and reviewer sign-off.
4. Boundary
This is a sanctions and financial-crime interface, not a full customs-law engine. AML Bible explains the control and evidence logic; applicable legal restrictions must be checked through official sources, Regulation Map context and company policy.