EU Sanctions DD WHY.3: Geographic Mismatch Detection
What This Control Requires
Is there a geographic mismatch between where the order was placed and where delivery is requested?
In Plain Language
The European Commission circumvention guidance specifically flags situations where the stated end-user is in a different country from where the order originates. When an order comes from Germany but delivery is requested to UAE for an 'end-user' in Kazakhstan, each handoff needs verification.
Legitimate reasons exist for geographic mismatches - multinational companies use centralised procurement, regional distribution hubs serve multiple countries, and group purchasing organisations place orders on behalf of affiliates. But each mismatch should be documented with a clear commercial explanation.
The red flag is not the mismatch itself but the absence of a convincing explanation. When the ordering entity, delivery destination, and stated end-user are all in different countries without clear commercial logic, the transaction warrants enhanced scrutiny.
How to Implement
For each transaction, cross-reference three geographic data points:
1. The ordering entity's jurisdiction - where is the buyer legally established? 2. The delivery destination - where are goods or services being shipped to? 3. The stated end-user location - where is the final user of the goods or services?
If these three locations are not the same, document the commercial explanation for each mismatch: - Centralised procurement (the buyer purchases for multiple group entities in different countries) - Regional distribution hub (delivery to a warehouse that serves multiple markets) - Technical installation (goods delivered to a factory or project site different from the buyer's HQ) - Transit and consolidation (goods pass through a logistics hub)
Apply enhanced scrutiny when: - The delivery destination is a circumvention hub or borders a sanctioned territory - The ordering entity has no apparent connection to the delivery destination - The stated end-user is in a higher-risk jurisdiction - The explanation for the mismatch is vague or changes over time - Multiple transactions show different delivery destinations but the same ordering entity
Document the analysis for every transaction where geographic mismatch is identified. Escalate to compliance when the explanation is unsatisfactory.
Evidence Your Auditor Will Request
- Geographic cross-reference records comparing order origin, delivery destination, and end-user location
- Commercial justification documentation for identified geographic mismatches
- Enhanced scrutiny records for mismatches involving circumvention-hub destinations
- Escalation records for cases where geographic mismatch lacked satisfactory explanation
- Trend analysis showing patterns of geographic mismatches across the counterparty portfolio
Common Mistakes
- Not systematically comparing order origin, delivery destination, and end-user location
- Accepting geographic mismatches without requesting an explanation
- Failing to apply enhanced scrutiny when the delivery destination is near a sanctioned territory
- Not tracking mismatch patterns across transactions to identify systematic diversion
- Treating each transaction in isolation rather than looking at counterparty-level patterns
Related Controls Across Frameworks
| Framework | Control ID | Relationship |
|---|---|---|
| EU Sanctions DD | EU Sanctions DD GEO.3 (related mapping) | Related |
| EU Sanctions DD | EU Sanctions DD WHY.1 (related mapping) | Related |
| EU Sanctions DD | EU Sanctions DD GEO.2 (related mapping) | Related |
Frequently Asked Questions
How common are legitimate geographic mismatches in international trade?
What if the buyer is a trading company or distributor?
Should we decline all transactions with geographic mismatches?
Track EU Sanctions DD compliance in one place
AuditFront helps you manage every EU Sanctions DD control, collect evidence, and stay audit-ready.
Start Free Assessment