Study guide
14.3 Communicating Monitoring Results: KPIs, KRIs, OKRs, and Management Information
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.3 Communicating Monitoring Results: KPIs, KRIs, OKRs, and Management Information
Key Takeaways Explain This Topic AI
KPIs measure performance, such as backlog age and SAR timeliness, while KRIs warn of rising risk, such as fast growth in high-risk segments.
An OKR pairs a qualitative objective with measurable, time-bound key results, often set quarterly.
SAR conversion rates and QA error rates measure the effectiveness of monitoring, not just analyst throughput.
Monitoring MI should explain changes in context, such as rule changes or customer growth, and should never set SAR quotas.
Last updated: October 2026
CAFCA sub-topic 3.9 covers best practices for communicating transaction monitoring trends and results , including KPIs, OKRs and other statistics . Monitoring generates a lot of data. The skill lies in turning it into information that leaders can act on, and that partner banks and supervisors trust.
Who needs monitoring MI and why
Audience What they need to decide
Board or risk committee Is financial crime risk within appetite? Are resources adequate? Are issues being fixed?
Senior management Where to invest (staff, tools, tuning); which products or corridors to restrict
Partner bank Is the FinTech's programme effective? Are referrals timely? Do they need to step in?
- Regulators Evidence of effectiveness, timeliness and governance
- Operations leads Daily staffing, queue priorities, quality issues
- Building the metric set
Operational KPIs (efficiency and timeliness):
Alert volumes by scenario, product and segment.
Alerts closed per analyst, and handling time.
Backlog size and ageing , for example 0 to 10, 11 to 20, 21 to 30 and more than 30 days.
Service-level adherence for triage, investigation and SAR filing.
Effectiveness measures:
Escalation rate (alert to case) and SAR conversion rate (case to SAR) by scenario.
SAR timeliness : the share filed within the legal deadline.
QA error rate : the share of closures that fail quality review.
True-positive yield by rule: which scenarios produce useful outcomes, and which only create noise.
Law enforcement feedback, information requests received, and funds frozen or losses prevented, where measurable.
Coverage measures:
Scenario coverage mapped to the risk assessment: is each high-risk typology monitored?
Data feed completeness : share of transaction streams ingested, and exceptions.
Model and rule changes made, tested and validated.
Key risk indicators (KRIs) are forward-looking warnings, such as growth in high-risk customers, new corridors, rising fraud claims, staff turnover in the investigations team, or backlog growth faster than capacity.
OKRs for monitoring improvements
An OKR links a qualitative objective to two to five measurable, time-bound key results . OKRs are often set quarterly.
Objective : Clear the investigation backlog without lowering quality.
KR1: Alerts older than 30 days reduced to zero by the end of Q2.
KR2: QA pass rate at 95% or above every month.
KR3: Median time from alert to disposition under 5 business days.
Objective : Improve detection of mule networks.
KR1: Device-link scenario live and validated by the end of Q3.
KR2: Share of mule SARs generated by the new scenario reported monthly.
Good OKRs target outcomes and quality, not raw volume. Never set SAR quotas. A target of "file 20% more SARs" pushes defensive filing and weakens the value of the reports.
Communicating trends well
Show trends over time , not single snapshots.
Normalise : alerts per 1,000 customers or per million transactions, so that growth does not mislead.
Explain changes : "SAR conversion fell from 8% to 3% after the new velocity rule went live in March. Most new alerts are low-risk subscription payments, and tuning is scheduled."
Compare with appetite using clear thresholds, such as red-amber-green status against board limits.
State actions, owners and dates , so that MI drives decisions.
Keep SAR-sensitive details out of broad distribution. Report aggregates, not customer-level SAR information, outside the restricted circle.
A sample monthly MI layout
- Section Content
- 1. Headline Three to five sentences: status against appetite, key changes, decisions needed
- 2. Volumes and capacity Alerts by scenario (normalised), staffing, handling time, backlog ageing chart
- 3. Effectiveness Escalation and SAR conversion by scenario, SAR timeliness, QA results
- 4. Coverage and data Feed completeness, rule changes and validation status, open model issues
- 5. Risk outlook KRIs, emerging typologies, upcoming product launches that affect monitoring
- 6. Actions Open remediation items with owners, due dates and status
Partner banks often specify the MI they want in the programme agreement. Agree definitions early, so that the FinTech's figures and the bank's own analysis tell the same story.
Pitfalls
Vanity metrics , such as "alerts closed", without any quality or outcome measures.
Unexplained spikes or drops , which raise doubts about data integrity.
Metrics that conflict with each other . Rewarding speed alone can push analysts into shallow closures.
Different definitions across reports. Fix them in a metric dictionary.
Realistic exam scenario
A neobank's board pack shows "Alerts closed: up 40%" and the status "green". It does not show that alerts older than 30 days doubled, that QA failures reached 18%, or that a payment stream was missing from monitoring for three weeks. The pack misleads. The MLRO should redesign the MI to cover backlog ageing, QA results, data-feed completeness and explained trends against appetite, with actions and owners.
Common exam traps
Confusing KPIs with KRIs. Performance measures look back; risk indicators warn of what is coming.
Setting SAR targets.
Reporting absolute numbers without normalising for growth.
Including customer-level SAR details in widely circulated reports.