Insights from the Royal Bank of Canada Case
Context: First-Party Fraud Detection
McKenzie’s Mission: Reduce false positives from 85:1 to 10:1
Important
The Connected Explosion: “Ten fraudsters sharing 10 common data elements can create 100 false identities; if they defraud 4 financial instruments per identity with $5,000 credit limit, potential loss = $2 million”
Important
Traditional Fraud Detection Limitations:
Individual attribute checking misses organized fraud patterns:
Tip
Network Analysis Advantage:
Reveals the connected explosion - fraudsters’ coordination creates detectable signatures:
Note
Fraudsters’ greatest strength (coordination) becomes their Achilles’ heel (detectability through network patterns)
16 Fraud Detection Rules Applied to 13,731 Customers
Key Performance Metrics:
| Rule | Positive Hits | True Positives | Detection Rate | False Positive Rate |
|---|---|---|---|---|
| R1 | 3,221 | 189 (45.5%) | 45.5% | 17:1 |
| R27 | 2,057 | 169 (40.7%) | 40.7% | 12:1 |
| R18 | 9,107 | 84 (20.2%) | 20.2% | 108:1 ⚠️ |
Caution
The Core Trade-off:
Neither single rule achieves the 10:1 target
1. Precision Enhancement Through Combined Rules
2. Cost-Benefit Analysis
Must balance: - Average cost of undetected fraudster ($2M potential loss per ring) - Average cost per investigation ($500-2000 per positive hit) - Data processing costs (ETL: 30TB weekly, 5 days processing time)
3. System Performance Optimization
The Multi-Dimensional Optimization Problem:
Technical Dimensions:
Business Dimensions:
Strategic Dimensions:
Tip
Real Outcome: By end of 2015, RBC reduced false positive ratio to 24:1 (progress but still above 10:1 target). In March 2016, discontinued SNA to revamp ETL infrastructure.
1. Context Matters More Than Algorithms
2. Trade-offs Are Inherent
3. Network Analysis Reveals Hidden Patterns
Note
This case demonstrates why business analysts need both technical skills (modeling, optimization) and business judgment (trade-off management, stakeholder communication)