Sanctions Evasion

Overview

Sanctions Evasion is conduct intended to conceal, reroute, misdescribe, or structure activity so that sanctions restrictions or controls are avoided. Its operational purpose is to enable a prohibited or restricted person, jurisdiction, sector, or transaction to obtain funds, goods, services, technology, or access. It should be considered alongside Chain Hopping. The relevant distinction is an accidental compliance error, because evasion generally involves deceptive behavior, concealment, intermediaries, false documentation, or deliberate circumvention.

A typical workflow is as follows: Methods can include front companies, third-country intermediaries, altered payment messages, nominee ownership, split transactions, false invoices, chain hopping, mixers, or changes in shipping and routing. Controls connect the separate signals into one case.

Core controls include ownership and network analysis, transaction monitoring, document verification, geolocation, device and counterparty linkage, adverse media, staff escalation, and reporting procedures.

In payment and crypto operations, A payment may appear to involve an unlisted party while benefiting a blocked person or supporting prohibited trade. Crypto does not remove sanctions obligations and can add cross-chain concealment techniques.

Evidence should include communications, ownership links, routing changes, payment fields, wallet exposure, device or IP indicators, invoices, shipping records, timing patterns, analyst reasoning, and reports. Rule-by-rule screening can miss coordinated behavior that becomes suspicious only when multiple parties and transactions are viewed together.

It is used to enable a prohibited or restricted person, jurisdiction, sector, or transaction to obtain funds, goods, services, technology, or access. It differs from an accidental compliance error, because evasion generally involves deceptive behavior, concealment, intermediaries, false documentation, or deliberate circumvention.

Implementation of Sanctions Evasion should map conduct intended to conceal, reroute, misdescribe, or structure activity so that sanctions restrictions or controls are avoided to the applicable entity, product, customer, transaction, and jurisdictional scope. Evidence for conduct intended to conceal, reroute, and misdescribe should preserve the governing requirement, policy version, control execution, exception decision, owner, and review date. Material changes affecting the Sanctions Evasion context and conduct intended to conceal, reroute, and misdescribe should trigger reassessment instead of silent reuse of an outdated conclusion.