Topic starter
25/10/2026 10:59 am
TL;DR: Transaction monitoring breaks when coverage gaps, weak escalation, and noisy queues let suspicious activity pass for years, according to Unit21. The control is not just alerting: it is a governed lifecycle that links risk assessment, tuning, casework, and filing.
Editorial analysis by NHI Mgmt Group, based on content published by Unit21: “AML transaction monitoring: a complete guide”.
Key questions
Q: What breaks when AML monitoring is not aligned to different financial verticals?
A: A single enterprise-wide rule set often misses the differences between banks, fintechs, payments, and BNPL environments.
Q: When should organisations prioritise real-time fraud monitoring over batch reviews?
A: Organisations should prioritise real-time fraud monitoring whenever compromise can quickly become monetary loss, such as account takeover, instant payments, or onboarding abuse.
Q: What are the signs that an AML monitoring programme is failing?
A: Common warning signs include excessive false positives, delayed alert handling, weak coverage of cross-border activity, and repeated suspicious patterns that are never escalated.
Practitioner guidance
- Build monitoring from a documented risk assessment Tie customer types, products, geographies, and transaction channels to explicit laundering risk before setting rules or thresholds.
- Separate screening from monitoring logic Keep pre-transaction screening distinct from behavioural monitoring so prohibited counterparties do not get treated as behavioural anomalies.
- Test rules against real outcomes Measure which alerts led to filings, which were cleared, and how threshold changes affect volume before they go live.
Bottom line: AML transaction monitoring fails most often because coverage, escalation, and calibration drift away from the actual risk profile, not because the control is missing entirely.
Explore further
View Full Forum → | NHI Foundation Course → | Our Services → | Read the full analysis →