Study guide
18.5 Outsourcing Controls: Surge Capacity, RegTech, and Independent Testing
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
18.5 Outsourcing Controls: Surge Capacity, RegTech, and Independent Testing
Key Takeaways Explain This Topic AI
Outsourcing a financial crime task never outsources accountability; regulators hold the firm responsible for outsourced controls.
Surge-capacity vendors should handle defined first-level tasks under the firm's procedures and QA, while SAR decisions stay with the firm's MLRO or BSA officer.
RegTech tools and their models need due diligence, configuration control and validation; a vendor's model is still the firm's control.
Independent testing of the AML programme must be carried out by competent people who did not design or run the controls being tested.
Last updated: October 2026
CAFCA sub-topic 5.5 covers the considerations of outsourcing controls , with three named examples: surge capacity , RegTechs and independent testing of the compliance framework . Outsourcing helps FinTechs scale quickly, but it is a frequent cause of failure when firms treat it as handing off the problem.
The principle: accountability stays in-house
Regulators across jurisdictions take the same line. The firm can delegate tasks but remains responsible . Examples include the UK FCA's systems and controls rules on outsourcing (SYSC 8), the EBA Guidelines on outsourcing arrangements (2019), the US interagency third-party guidance, and MAS outsourcing guidelines. Supervisors expect due diligence before signing, contracts that protect access and audit rights, ongoing oversight, and exit plans.
Three types of outsourcing
Type Typical use Benefits Key risks Core controls
Surge capacity (managed services or contract analysts) Clearing backlogs; launches; remediation look-backs Fast scale; flexible cost Quality drift; insider risk; inconsistent decisions; data security Firm procedures and templates; training and certification; QA sampling; limited access; escalation to in-house staff
RegTech tools eKYC, sanctions and PEP screening, transaction monitoring, blockchain analytics, case management Specialist capability; speed "Black box" models; poor configuration; vendor outage; data residency Due diligence; configuration ownership; validation and tuning; SLAs; fallback procedures
Independent testing and audit Annual or risk-based programme testing; outsourced internal audit Independence; expertise Narrow scope; weak follow-up Defined scope; competence and independence checks; board reporting; issue tracking
Surge capacity done well
Scope : vendor analysts work defined first-level tasks, such as triage and documented closure under clear rules. SAR decisions stay with the firm's MLRO or BSA officer , and complex cases are escalated in-house.
Standards : they use the firm's procedures, templates and decision criteria, not the vendor's own.
Onboarding : screening of vendor staff, training on the firm's products and typologies, and certification before live work.
Quality : higher QA sampling at first, calibration sessions, and pay or targets tied to quality as well as volume.
Security : least-privilege access, no local downloads, monitoring of user activity (Chapter 6), and removal of access at the end of the engagement.
RegTech: buying a tool is not buying compliance
Due diligence : capability, data sources, coverage, security certifications, financial stability, sub-processors and data location.
Configuration ownership : the firm sets the thresholds, lists, rules and match settings, and documents why. Vendor defaults are a starting point, not a decision.
Validation : test detection on known cases, run parallel tests before cut-over, and validate models, including any machine learning scoring. The firm needs enough explanation from the vendor to defend outcomes to examiners (Chapter 11).
Change management : the vendor must notify the firm of model or list changes, which the firm then tests.
Resilience : SLAs, outage procedures (fail-closed for sanctions), and contingency plans.
Concentration risk : relying on one vendor for onboarding, screening and monitoring creates a single point of failure.
Independent testing
US BSA programmes must include independent testing . The UK Money Laundering Regulations require an independent audit function where appropriate to size and nature. Good practice:
Independence : testers did not design or operate the controls they test. They may be internal audit, an outside firm or another qualified independent party.
Competence in the FinTech's products, technology and typologies.
Risk-based scope : risk assessment, CDD and beneficial ownership, screening, monitoring (including data integrity and rule logic), alert and SAR processes, training, governance and MI. It should also cover outsourced and vendor-run controls.
Frequency : risk-based. Many firms test every 12 to 18 months, more often after major change.
Reporting to the board or audit committee, with management responses and tracked remediation.
The contract checklist
Scope and service levels; quality standards; data protection and confidentiality, including how SAR-related material is handled; audit and access rights for the firm, its partner bank and regulators; sub-contracting approval; incident notification; business continuity; termination and exit assistance; data return and deletion; and the regulatory notification duties that apply to material outsourcing in some regimes.
Realistic exam scenario
To clear a 20,000-alert backlog, a FinTech hires a managed-service vendor whose analysts close alerts three times faster than the in-house team. QA then finds that 22% of vendor closures lack a rationale and that two missed SAR-worthy cases. The firm should pause bulk closures, re-review the affected population, strengthen vendor training and templates, and raise QA sampling. It should tie the vendor's targets to quality and report the issue to the board and partner bank. It cannot blame the vendor in place of fixing the control. Accountability remains with the firm.
Common exam traps
"The vendor is responsible for compliance failures." The firm is accountable.
Running vendor defaults without documenting why they fit.
Letting surge analysts make SAR decisions.
Independent testers who also designed the controls.