Study guide

15.2 Reviewing KYC, Transactions, Open Sources, and Documents to Build an Investigation

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

15.2 Reviewing KYC, Transactions, Open Sources, and Documents to Build an Investigation

Key Takeaways Explain This Topic AI

Investigations start by checking the KYC profile: identity, beneficial owners, stated purpose and expected activity, and risk-rating history.

Transaction analysis looks at counterparties, flows, timing, velocity, geography and amounts against the customer's baseline and peer group.

Customer-supplied documents should be checked against independent sources and for internal consistency before they are relied on.

Open-source research covers adverse media, corporate registries, court records and public online footprints, recorded with URL, date and capture.

Last updated: October 2026

CAFCA sub-topic 4.2 asks how to review KYC information, transactions, open-source research and documentation to inform an investigation. A good investigator builds an evidence picture that a reviewer can follow. Every conclusion should trace back to a source.

1. Start with the KYC file

Identity and verification : what was verified, with what sources, and were there any discrepancies at onboarding?

Ownership and control for entities: beneficial owners, directors and signatories, and any changes.

Stated purpose and expected activity : occupation or business model, expected volumes, countries and payment methods.

Risk history : rating changes, prior alerts and their dispositions, PEP or sanctions screening results, prior RFIs.

Ask: does the activity under review fit the person or business described in the file?

2. Analyse the transactions

Lens Questions Techniques

Volume and value How much has moved, over what period, compared with the baseline and with peers? Totals, averages, month-on-month change

Counterparties Who sends and who receives? Are they repeat, related, high-risk, or new? Counterparty lists; link charts

Flow pattern In and immediately out? Funnel? Circular? Fan-in or fan-out? Flow diagrams; dwell-time calculation

Timing and velocity Bursts, night-time activity, activity just after onboarding or after dormancy Timelines; heat maps

Amounts Round numbers, amounts just below thresholds, repeated identical values Frequency tables

Geography and channel High-risk corridors, VPN or location mismatches, new channels Maps; IP and device summaries

Instruments Card, ACH, instant, crypto, cash, prepaid; reversible funding with irreversible exits Method breakdown

3. Use digital and device evidence

Shared devices across accounts, IP addresses in unexpected countries, emulator signals, and logins just before suspicious transfers can link apparently unrelated customers or point to account takeover (Chapter 8).

4. Test documents

Customers may provide invoices, contracts, payslips, bills of lading or bank statements. Before relying on them:

Check consistency : do the dates, amounts, names and descriptions match the transactions?

Check against independent sources : does the supplier exist in a corporate registry? Does the employer exist? Does the invoiced amount match the payment exactly?

Look for tampering : odd fonts, misaligned figures, file metadata showing recent editing, or templates reused across customers.

Ask whether a genuine business would produce this document. A US$90,000 "consulting invoice" with no description of services is weak evidence.

5. Do open-source research properly

Adverse media : search the names of the subject, the business and the directors with risk keywords (fraud, laundering, sanction, bribery, arrest, court). Prefer reputable outlets and primary records.

Corporate registries : incorporation date, officers, filings, dissolution status, shared addresses with other companies.

Court and regulator records : judgments, enforcement notices, insolvency.

Online footprint : website age and content (archive services can show history), domain registration, public social media consistent with the declared business, and whether the address exists.

Method and ethics : use public information only. No fake profiles, pretexting or hacking. Record the URL, date and a capture of each item (Chapter 14).

6. Check internal records

Other accounts held by the subject or by linked people, complaints and fraud claims against the account, chargebacks, previous RFIs, partner-bank referrals and law enforcement requests. Previous SARs may be visible only in the restricted SAR repository, so follow the access rules.

7. Visualise links

When several accounts, devices or counterparties are involved, draw a link chart : nodes for people, accounts, devices, addresses and wallets, and edges for payments or shared attributes. Charts reveal hubs, such as a device used by eight "unrelated" customers, and show directions of flow that tables hide. Keep the underlying data with the chart so that every link can be traced to a record. Many case-management tools build these graphs automatically, but the analyst must still check that each link is real. Two customers sharing a public Wi-Fi address is weaker evidence than two customers sharing a device identifier.

Building the picture

Summarise the evidence in a chronology. Mark what supports and what contradicts each explanation, rate the reliability of each source, and identify the gaps that further enquiry could close. Chapter 15 covers how to avoid bias when weighing the evidence.

Realistic exam scenario

A business account opened as a "marketing consultancy" receives 120 payments from individuals in three countries and sends funds out to a crypto exchange. Open-source checks show the company website was copied from another firm's site and the domain is two months old. A director appears in a court judgment for investment fraud. The customer later provides invoices that all use the same template with different names. Together, the evidence contradicts the stated business and supports escalation for a SAR decision. Each finding is recorded with its source.

Common exam traps

Relying on customer documents without testing them.

Using a single news article as proof. Corroborate it.

Ignoring the KYC baseline and judging transactions in isolation.

Unrecorded open-source findings.