Geographic Risk

1. Practical definition #

Geographic exposure risk is the ML/TF/PF, sanctions, corruption, supervision and enforcement risk associated with the geographies connected to a customer, UBO, counterparty, transaction, goods route, end user, source of funds or source of wealth.

This is a risk-factor module, not a jurisdictional legal module. It does not tell the reviewer what any country-specific legal rules require.

2. Why this matters for AML practitioners #

A customer may appear low risk in isolation but become higher risk when connected to weak AML controls, sanctions exposure, conflict, corruption, terrorism financing, proliferation financing or opaque corporate registries. FATF requires risk-based assessment of customers, countries/geographic areas, products, services, transactions and delivery channels.

3. Trigger events #

  • Customer residence, incorporation or operation in higher-risk geography.
  • UBO/controller linked to higher-risk geography.
  • Funds originate from or move through higher-risk geography.
  • Counterparty or bank located in higher-risk geography.
  • Goods route, transshipment point or end user involves higher-risk geography.
  • FATF high-risk or increased-monitoring exposure.
  • UN sanctions/TFS exposure.

4. Source basis #

  • SRC-FATF-001: risk-based approach and higher-risk geographic risk factors.
  • SRC-FATF-002: FATF high-risk and increased-monitoring lists.
  • SRC-UN-001: neutral TFS screening baseline.
  • Institution-specific policy layer: institutions may add domestic risk lists, sanctions lists or internal scoring outside the open knowledge base.

5. Geographic exposure dimensions #

Dimension Review question
Customer Where is the customer based, incorporated or operating?
UBO/control Where are the UBOs, controllers and key decision-makers linked?
Funds Where do funds originate, pass through and end?
Goods/services Where are goods produced, shipped, transshipped, delivered or used?
Banks/payment route Which banks, PSPs, VASPs or intermediaries are involved?
Sector link Is the geography connected to corruption, conflict, cash intensity, smuggling, sanctions evasion or PF-sensitive trade?

6. Practitioner workflow #

  1. Identify all relevant geographies: incorporation, residence, operation, UBO, bank, counterparty, goods route, end user and source of funds.
  2. Check FATF high-risk and increased-monitoring sources.
  3. Check UN sanctions/TFS exposure.
  4. Check internal risk appetite and institution-specific policy, if configured.
  5. Identify sector-specific geographic issues.
  6. Combine geography with other risk factors: ownership opacity, PEP, adverse media, transaction pattern and product risk.
  7. Decide whether normal CDD, EDD, MLRO review or no-go route is required.
  8. Record source date because geographic risk changes.

7. Risk levels #

Level Example Required action
Low No high-risk exposure identified Normal CDD if no other triggers
Medium Weak or indirect link to higher-risk geography Document rationale and consider targeted questions
High Direct FATF increased-monitoring exposure or corruption/sanctions proximity EDD and senior review
Critical FATF call for countermeasures, UN sanctions/TFS exposure, PF-sensitive evasion pattern MLRO/legal process

8. Evidence to collect #

  • Customer and UBO locations.
  • Counterparty and bank locations.
  • Goods route / payment route map.
  • FATF list check with date.
  • UN sanctions/TFS check with date.
  • Internal policy score, if configured.
  • Analyst rationale for risk level.

9. Example output #

# Geographic Risk Note

Customer/counterparty: [name]
Relevant geographies: [list]
Exposure type: [residence/incorporation/UBO/funds/bank/goods route/end user]
FATF status: [none/high-risk/increased monitoring]
UN TFS exposure: [none/possible/confirmed]
Combined risk factors: [PEP/sanctions/adverse media/ownership/transaction/sector]
Risk level: [low/medium/high/critical]
Recommended action: [normal CDD/targeted review/EDD/MLRO escalation]
Evidence index: [links/files/screenshots]

10. Boundary #

Boundary: this is a reusable geographic-risk workflow, not a country legal guide. Local obligations come from Regulation Map and institution policy.

11. Digital infrastructure as geographic exposure #

Geographic exposure can also appear through public digital infrastructure records. Website IP geolocation is only one signal. Public MX, TXT/SPF, DMARC, DKIM, NS, CNAME, SOA and PTR records may reveal email, DNS, hosting, SaaS or relay providers connected to geographies not declared by the customer.

The reviewer treats this as Digital Jurisdiction Exposure: a supporting KYB/EDD indicator that should be added to the evidence pack when relevant.

Related article: Digital Jurisdiction Exposure

12. Country risk is not only blacklist risk #

Country risk should not be based only on blacklists, grey lists, nationality or place of incorporation. A safer source-based view combines several layers:

Layer What it adds Example source type
FATF list status Whether the jurisdiction is subject to FATF high-risk or increased monitoring status. FATF public statements and lists
Mutual evaluation findings How the jurisdiction performed against technical compliance and effectiveness measures. FATF / FSRB mutual evaluation reports
National risk context What threats, vulnerabilities and sector risks the jurisdiction has identified. National Risk Assessment publications
Sector exposure Whether the customer activity sits in a higher-risk sector for that jurisdiction. NRA, regulator guidance, typologies
Transaction route exposure Whether funds, goods, counterparties or intermediaries pass through higher-risk routes. Transaction, shipping, payment and counterparty evidence
Customer-specific facts Whether this customer has specific risk factors independent of the country. KYC/KYB evidence, ownership, activity, adverse media

The key rule is:

country context informs risk;
it does not replace customer-specific evidence.

A country may have weaknesses in AML/CFT supervision without every customer from that country being high-risk. Equally, a customer in a lower-risk jurisdiction can still present high risk through ownership, activity, sanctions proximity, adverse media or transaction behaviour.

Basel AML Index as a supporting indicator#

The Basel AML Index can be used as one comparative jurisdiction-risk input alongside FATF status, mutual-evaluation findings, National Risk Assessments and customer-specific exposure.

  • Source ID: SRC-BASEL-INDEX-001.
  • Use: comparative context and independent benchmarking.
  • Do not use it as a legal classification, a substitute for FATF, an automatic EDD trigger or a customer-level risk score.
  • Record the edition, methodology cut-off date and date accessed.

A jurisdiction indicator informs the review; it does not decide the customer outcome.