Red Flags for Terrorist Financing: Test Your CFT Detection Skills
True / False
True / False
Select all that apply
Put in order
True / False
Select all that apply
Put in order
Select all that apply
Put in order
True / False
Select all that apply
Disclaimer
This quiz is for educational purposes only. It does not replace official safety training, certification, or regulatory compliance programs.
CFT Red-Flag Misreads That Lead to Missed SARs and Weak Sanctions Decisions
These are the failure patterns that most often show up in quality assurance (QA) reviews, FIU feedback, and examiner criticism when institutions assess potential terrorist financing (TF).
1) Treating TF like “big-dollar” money laundering
- Mistake: Waiting for large structuring patterns or obvious layering before escalating.
- Avoid it: Weight velocity, donor dispersion, rapid in-and-out movement, and purpose inconsistency against the customer’s KYC and expected activity—even when amounts are small.
2) Clearing sanctions hits on one non-matching field
- Mistake: Closing a possible match because the country, spelling, or middle name differs.
- Avoid it: Reconcile all available identifiers (DOB ranges, aliases, addresses, nationality, document numbers), and assess ownership/control exposure (including OFAC’s “50 Percent Rule” logic where applicable).
3) Using the “NPO” label as a substitute for analysis
- Mistake: Auto-high-risking every charity (or defaulting domestic charities to low risk).
- Avoid it: Apply a risk-based view: mission, governance, fundraising channels, beneficiaries, delivery methods, and geographic exposure. Compare outbound counterparties to stated programs.
4) Accepting customer explanations without testing them
- Mistake: Closing on a plausible story (“helping friends,” “donations,” “travel money”).
- Avoid it: Corroborate with documents/data: payroll, invoices, travel records, beneficiary lists, counterparties, device/IP signals, and prior alert history.
5) Fragmenting alerts and under-documenting decisions
- Mistake: Treating each alert as isolated, producing thin narratives and inconsistent dispositions.
- Avoid it: Link related cases across time, accounts, and counterparties; preserve evidence; and write decisions so a reviewer can reproduce your logic from the record.
Decision Drills: Terrorist Financing Signals vs. Normal Customer Behavior
Use these short drills to practice the same judgment calls the quiz targets: separating innocuous activity from TF indicators, deciding when to escalate, and capturing the facts you would need for a defensible case file.
Drill 1: Funnel-account pattern into an MSB corridor
A low-income personal account receives multiple same-week cash deposits from unrelated individuals, then wires most funds to a money services business tied to a higher-risk corridor.
- Decide: What specific facts make this different from routine remittance behavior?
- Document: Which KYC gaps and counterparties must be verified before disposition?
Drill 2: NPO with conflict-zone outflows
A domestic education charity advertises local programs, but most donations are quickly sent to a single overseas organization operating in an active conflict area.
- Decide: What would you seek to validate (program spend, beneficiaries, governance, third-party due diligence)?
- Escalate: What would trigger a sanctions re-screen or enhanced review of the foreign counterparty?
Drill 3: P2P transfers with concerning memo fields
A customer with ordinary retail activity begins sending frequent low-value P2P transfers; the notes include coded language and cause-based fundraising references.
- Decide: Which indicators are behavioral (frequency/velocity) versus content-based (memos/notes)?
- Control check: What monitoring or keyword governance questions should be raised?
Drill 4: “False positive” sanctions hit with partial identifiers
Screening generates a potential match to a designated individual; the name is close, and the address is in a different country than the customer’s stated residence.
- Decide: What minimum identifier set is needed before you can clear (or confirm) the hit?
- Risk note: How would you explain the decision to an auditor in one paragraph?
Drill 5: Multiple related customers, each “clean” in isolation
Three customers share devices and contact details, use different products (cards, wires, cash), and each triggers small anomalies across several months.
- Decide: What linkage evidence matters most (shared addresses, payees, instruments, digital fingerprints)?
- Narrative: What is the unifying typology you would articulate if you file?
Terrorist Financing Detection: 5 Analyst Takeaways That Improve CFT Outcomes
- Prioritize inconsistency over size. TF risk often shows up as behavior that conflicts with the customer’s stated purpose, income, and expected geography—not as large-dollar thresholds.
- Sanctions decisions require full-identifier discipline. Don’t clear a hit on a single mismatch; reconcile aliases, DOB ranges, addresses, and ownership/control exposure before you disposition.
- Use NPO context, not labels. Compare a charity’s public mission and program footprint to actual inflows/outflows, delivery channels, and overseas counterparties, then apply a risk-based control response.
- Test explanations with evidence. A plausible customer story is not a control; you need corroboration (documents, third-party sources, transaction linkage, and historical pattern comparison).
- Build cases across time. Link related alerts and entities so your escalation or SAR narrative reflects the full TF typology and decision rationale, not disconnected events.
CFT Glossary for Terrorist Financing Red-Flag Reviews (with Examples)
- CFT (Countering the Financing of Terrorism)
- Controls designed to detect and disrupt financial support for terrorist actors. Example: “We enhanced CFT monitoring for rapid pass-through transfers to higher-risk corridors.”
- SAR (Suspicious Activity Report)
- A report to FinCEN documenting suspicious transactions/patterns. Example: “The case was escalated for SAR consideration due to donor dispersion and conflict-zone counterparties.”
- Sanctions screening “potential match”
- An alert indicating possible alignment between a party and a sanctions list entry, requiring investigation. Example: “We treated the hit as unresolved until DOB and alias checks were completed.”
- OFAC 50 Percent Rule
- Guidance concept that entities owned 50% or more (in aggregate) by blocked persons are considered blocked, even if not named on a list. Example: “We reviewed ownership after finding an SDN-linked controller.”
- MVTS/MSB (Money Value Transfer Service / Money Services Business)
- Non-bank providers that transmit money or value (e.g., remittance providers). Example: “The customer’s wire activity concentrated through a single MVTS inconsistent with stated purpose.”
- Funnel account
- An account receiving funds from multiple sources and quickly sending onward, often with limited economic rationale. Example: “Unrelated cash deposits followed by near-total outgoing wires indicated potential funneling.”
Authoritative References for FATF CFT Standards, FinCEN Expectations, and Sanctions Controls
- FATF — Terrorist Financing Risk Assessment Guidance — Practical guidance on identifying TF threats/vulnerabilities and applying a risk-based approach across sectors, including banking, MVTS, and NPO exposure.
- FinCEN Advisory (FIN-2024-A001) — Iran-Backed Terrorist Organizations Red Flags — Detailed indicators, typologies, and reporting expectations to support alert triage and SAR decision-making.
- FFIEC BSA/AML Examination Manual — Appendix F: Money Laundering and Terrorist Financing Red Flags — Examiner-facing red-flag examples that help align case documentation with supervisory expectations.
- U.S. Treasury (OFAC) — Framework for OFAC Compliance Commitments — Core components regulators expect in a sanctions compliance program, including screening, escalation, and testing.
- United Nations Security Council — Consolidated List — Official UN consolidated sanctions list references, formats, and update information useful for global sanctions controls.
Terrorist Financing Red Flags (CFT) FAQ: SAR Judgment, NPO Risk, and Sanctions Controls
How is terrorist financing different from “traditional” money laundering in transaction monitoring?
Terrorist financing often presents as low-dollar, high-frequency, fast-moving activity with weak economic purpose (e.g., rapid pass-through, donor dispersion, or atypical corridors) rather than large-dollar structuring. The quiz emphasizes behavioral context (customer profile, velocity, counterparties, geography) because TF risk can be missed when analysts rely on amount thresholds alone.
What evidence should I capture before escalating a TF concern for SAR consideration?
Capture a reproducible fact set: timeline of transactions (in/out and time-to-spend), sender/beneficiary attributes, links across accounts/customers, KYC/EDD profile gaps, sanctions screening outcomes, and any corroboration or contradictions to the stated purpose. The goal is not to “prove TF,” but to document why the pattern lacks a reasonable lawful purpose and what checks were performed.
How should analysts handle alerts involving non-profit organizations (NPOs) without over-flagging?
Use FATF’s risk-based logic: evaluate the NPO’s mission, governance, fundraising channels, and how funds reach beneficiaries. Elevated risk is driven by delivery to conflict areas, opaque intermediaries, unusual cash intensity, or mismatch between public program claims and actual outflows—not the NPO label itself.
What makes a sanctions “false positive” determination defensible during QA or an exam?
A defensible clearance shows that you assessed multiple identifiers (not just name), considered aliases and transliterations, and evaluated whether ownership/control creates indirect exposure. Your notes should explain which identifiers were verified, which were unavailable, and why the remaining risk is low enough to clear under your policy.
Do I need certainty that activity is terrorism-related before escalating or filing?
No. CFT controls are designed to identify suspicion based on facts and reasonable inference, then escalate for appropriate review and reporting under your institution’s procedures. If you want broader practice on SAR reasoning across typologies, use the AML Practice Questions quiz to reinforce narrative and evidence standards.
How do FATF standards and U.S. expectations (FinCEN/OFAC) fit together in day-to-day alert work?
FATF sets the global baseline for a risk-based AML/CFT program, while U.S. regulators (including FinCEN under the BSA and OFAC for sanctions) expect documented, consistently applied controls: monitoring calibrated to TF typologies, timely escalation, well-supported SAR decisions, and disciplined sanctions screening/escalation. For a broader standards view beyond TF-specific red flags, see the AML/CFT Compliance Quiz.