Study guide

14.1 The Alert Investigation Process: From Unusual to Suspicious and When to Escalate

ACAMS Certified AML FinTech Compliance Associate CAFCA

Track your progress as you read

Finished sections get a check mark.

1 Chapter 1: CAFCA Exam Overview and Study Strategy

1.1 CAFCA Exam Format, Official Domains, and Study Strategy

2 Chapter 2: Domain 1: FinTech Business Models and Their Vulnerabilities

2.1 Neobanks, Challenger Banks, and Digital Banking Models 2.2 Payment Processors, Gateways, and Merchant Acquirers 2.3 Buy Now, Pay Later (BNPL) and Alternative Credit 2.4 BaaS Architecture, Embedded Finance, and Program Structures

3 Chapter 3: Domain 1: Financial Crime Types and the Regulatory Perimeter

3.1 Types of Financial Crime and Predicate Offences 3.2 Licensing, Registration, Charters, and Regulatory Sandboxes 3.3 Virtual Asset Service Provider (VASP) Framework & FinCEN MSB Rules

4 Chapter 4: Domain 1: Global AML Frameworks and Sources of Guidance

4.1 U.S. Regulatory Architecture: BSA, PATRIOT Act, and AMLA 2020 4.2 European Union Regulatory Framework: AMLD6, the AML Package, and MiCA 4.3 International Standards: UK FCA, Singapore MAS, and Hong Kong HKMA 4.4 Sources of Guidance for Building Anti-Financial Crime Processes

5 Chapter 5: Domain 1: Risk Management Framework, Risk-Based Approach, and Data Protection

5.1 Risk Management Framework: Lines of Defence, Policies, Assurance, and the MLRO 5.2 Risk-Based Approach, Risk Assessment, Risk Appetite, and Types of Risk 5.3 Handling Sensitive Information: PII, SPII, Privacy Laws, and Breach Reporting

6 Chapter 6: Domain 1: Bank Partners and Internal Threats

6.1 Regulatory Expectations and Enforcement on Sponsor Banks 6.2 How Banks Risk-Rate FinTechs: Onboarding, Ongoing Oversight, and De-Risking 6.3 Controlling Internal Threats: Insider Fraud, Collusion, and Data Misuse

7 Chapter 7: Domain 2: CIP, KYC, CDD, and EDD

7.1 Customer Identification Program (CIP) Under USA PATRIOT Act §326 7.2 The FinCEN CDD Rule & Beneficial Ownership Standards 7.3 KYC to EDD: Applying CDD and Enhanced Due Diligence Across Customer Types

8 Chapter 8: Domain 2: Identity Verification, Data Sources, and Device Data

8.1 Digital Onboarding & Electronic KYC (eKYC) Foundations 8.2 Biometric Face Matching and Liveness Detection 8.3 Verification Data Sources and How to Judge Their Reliability 8.4 Device Fingerprinting, Geolocation, and Behavioral Biometrics

9 Chapter 9: Domain 2: Onboarding Screening, Risk Ratings, and Fraud Red Flags

9.1 Screening at Onboarding: Sanctions Lists, PEPs, and Known Fraudsters 9.2 Customer Risk Ratings: Factors, Data Sources, and How Scoring Models Work 9.3 Detecting Synthetic Identity Fraud and Ineligible Applicants 9.4 Deepfakes, Generative AI Threats, and Scam Typologies

10 Chapter 10: Domain 3: Payment Screening

10.1 OFAC Sanctions Regimes & the 50 Percent Rule 10.2 Real-Time vs. Batch Screening Architecture in High-Velocity Rails 10.3 Screening Logic: Fuzzy Matching, Phonetics, and PEP Controls

11 Chapter 11: Domain 3: Transaction Monitoring Systems and Red Flags

11.1 Hybrid Transaction Monitoring: Rules Engines vs. Machine Learning 11.2 FinTech Typologies: Mule Networks, Funnel Accounts, and Rapid Pass-Through 11.3 Fraud-AML Convergence: BIN Attacks, ATO, and Credential Stuffing 11.4 Model Risk Management Under SR 11-7 & System Optimization

12 Chapter 12: Domain 3: Payment Methods and Transaction Risk Characteristics

12.1 Common Payment Methods, Crypto, and High-Risk Transactions Such as Aggregation 12.2 Transaction Risk Characteristics: Reversibility, Convertibility, Fund Integrity, and Privacy Coins 12.3 Wallet Types, Custody Architectures, and Counterparty Risks 12.4 Stablecoins, On/Off Ramps, and Asset-Referenced Tokens

13 Chapter 13: Domain 3: Monitoring Crypto Transactions

13.1 Blockchain Analytics & Transaction Tracing 13.2 The FATF Travel Rule for Virtual Assets 13.3 DeFi, Mixers, and Smart Contract Sanctions

14 Chapter 14: Domain 3: Alert Investigation, Audit Trails, and Monitoring MI

14.1 The Alert Investigation Process: From Unusual to Suspicious and When to Escalate 14.2 Building an Audit Trail for Suspicious Activity Reviews 14.3 Communicating Monitoring Results: KPIs, KRIs, OKRs, and Management Information

15 Chapter 15: Domain 4: Investigations and Customer Communication

15.1 Talking to Customers During Investigations and Offboarding: Financial Crime Risk vs Policy Breach 15.2 Reviewing KYC, Transactions, Open Sources, and Documents to Build an Investigation 15.3 Analytical Principles in Investigations: Avoiding Confirmation Bias and Other Traps

16 Chapter 16: Domain 4: SARs and STRs

16.1 SARs and STRs: What They Are, When and Where to File, and Why They Matter 16.2 Writing Effective SAR and STR Narratives

17 Chapter 17: Domain 4: Law Enforcement, Regulators, and Banking Partners

17.1 Operational AML Governance and Third-Party Risk Management 17.2 Working With Law Enforcement, Banking Partners, Regulators, and Other Third Parties 17.3 Types of Law Enforcement Requests: Subpoenas, Court Orders, 314(a), and International Requests 17.4 How Banking Partners' Terms of Service Relate to the FinTech's Own Terms

18 Chapter 18: Domain 5: Scaling Anti-Financial Crime Strategies

18.1 Assessing New Products and Features Before Launch 18.2 Refreshing the Financial Crime Risk Assessment as the Business Scales 18.3 Changes That Should Trigger a Financial Crime Risk Assessment Review 18.4 Record Retention Rules and Secure Data Storage 18.5 Outsourcing Controls: Surge Capacity, RegTech, and Independent Testing

14.1 The Alert Investigation Process: From Unusual to Suspicious and When to Escalate

Key Takeaways Explain This Topic AI

Unusual activity departs from the customer's expected pattern; suspicious activity is backed by facts that give reasonable grounds to suspect crime or evasion.

US SAR rules cover transactions where the institution knows, suspects or has reason to suspect illegal funds, evasion, no apparent lawful purpose, or facilitation of crime.

In England and Wales, R v Da Silva (2006) held that suspicion means a possibility that is more than fanciful, which is a low threshold.

Investigators should escalate when red flags stay unresolved, when sanctions, PEP or insider links appear, or when activity matches a known typology.

Last updated: October 2026

CAFCA sub-topic 3.5 covers the investigatory process for alerts , including determining unusual and suspicious activity and determining escalation . The exam rewards a structured, documented, timely process that never tips off the customer.

Unusual versus suspicious

Unusual : the activity departs from what was expected for this customer, or from their peer group. Examples are a sudden spike, a new corridor, or an odd time of day. Unusual activity is a reason to look , not a conclusion.

Suspicious : after review, the facts give reason to suspect that the funds come from crime, that the activity is designed to evade reporting, that it has no business or apparent lawful purpose, or that the account is being used to facilitate crime. These four limbs reflect the US SAR rule. In the UK, suspicion is a low threshold. In R v Da Silva (2006) the Court of Appeal described it as a possibility that is more than fanciful. Proof is not required.

Many alerts are unusual but explained: a bonus, a house sale, a seasonal business. The investigator's job is to find out whether the explanation fits the facts and can be corroborated .

The investigation workflow

Stage Key questions Typical outputs

1. Triage (L1) Is the alert valid, or caused by bad data? Is it a duplicate? Are there linked alerts or open cases? Is there an obvious, verifiable explanation? Close with rationale, or move to review

2. Customer review Who is the customer? What did they say about purpose and expected activity? What is their risk rating and prior history? Profile summary; baseline comparison

3. Transaction analysis Who are the counterparties? What are the amounts, timing, velocity, geography and payment methods? Does a known typology fit? Flow summary, charts, counterparty list

4. Information gathering What do internal data show (other accounts, devices, IPs, fraud claims)? What does open-source research show? Do we need a carefully worded request for information to the customer? Evidence file with sources

5. Assessment Is there a credible, corroborated legitimate explanation? Which red flags remain? Written analysis separating facts, inferences and conclusions

6. Decision Close, keep under watch, escalate to a case (L2), restrict or exit, or refer for SAR/STR? Decision, approver, timestamps

  • 7. Quality assurance Did the work meet the standard? QA score; feedback
  • Escalation criteria

Escalate from L1 to L2 investigation, or to the MLRO or SAR decision-maker, when:

Red flags remain unresolved after reasonable enquiry, or the explanation cannot be corroborated .

Activity matches a known typology : funnel account, rapid pass-through, structuring, transaction laundering or scam victim behaviour.

There is a sanctions nexus (escalate at once to sanctions handling), PEP involvement, adverse media, or a link to existing SARs or law enforcement requests .

Insider involvement is suspected.

Amounts, counterparties or geographies breach escalation thresholds in the procedure.

The customer refuses or evades reasonable information requests.

Escalation is not an accusation. It moves the decision to someone with authority and context.

Timeliness and interim actions

Clocks. In the US, the 30-day SAR clock starts at the initial detection of facts that may constitute a basis for filing . That is not when the alert fires, but reviews must not be delayed unreasonably. Other regimes require reporting "promptly" or "as soon as practicable".

Interim protection. Where policy, contract and law allow, apply holds, limits or freezes to stop further loss. A confirmed sanctions match must be blocked or rejected straight away (Chapter 10).

UK consent. If the firm wants to carry out a transaction involving suspected criminal property, it may need a defence against money laundering (DAML) from the NCA before proceeding (Chapter 4).

Contacting the customer without tipping off

Requests for information are allowed and often useful, for example asking for an invoice, the purpose of a payment or a contract. Phrase them neutrally, as routine account checks, and never mention suspicion, alerts or reports. If questioning would alert the customer to an investigation, take advice from the MLRO first (Chapter 15).

Realistic exam scenario

An alert flags a student account that received 15 P2P credits of US$500 to US$900 from unrelated senders over two days, all forwarded within 30 minutes to a crypto exchange. The customer says, "My friends paid me back for concert tickets." There is no evidence of ticket purchases, several senders have filed scam reports, and the device has been seen on two other accounts. The explanation is not corroborated and does not fit the facts. The pattern matches a mule or funnel typology. The investigator should escalate to an L2 case. Possible actions are restricting outbound transfers, linking the related accounts, and referring the case for a SAR decision.

Common exam traps

Closing because the customer offered an explanation. Explanations must fit the facts and be corroborated.

Waiting for proof before escalating. Suspicion, not proof, is the standard.

Treating "unusual" as automatically "suspicious". It is the trigger for review, not the conclusion.

Telling the customer an alert was raised. That is tipping off.