Topic starter
25/10/2026 10:59 am
TL;DR: Coverage gaps, weak escalation, and noisy queues let suspicious activity pass for years, Unit21 found, when AML transaction monitoring drifts from the risk profile. Instant payments and uneven vertical risk mean the control needs tuning, investigation, and filing discipline.
Editorial analysis by NHI Mgmt Group, based on content published by Unit21: “AML transaction monitoring: a complete guide”.
Key questions
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.
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.
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.
Glossary terms: Transaction Monitoring, Policy Tuning, Suspicious activity report, Placement, Layering, and Integration
Explore further
View Full Forum → | NHI Foundation Course → | Our Services → | Read the full analysis →
This topic was modified 7 days ago by NHI Mgmt Group
27/10/2026 7:16 pm
Transaction monitoring is a governance system, not a queue. The article shows that alert generation alone does not equal control effectiveness. If gaps are ignored for years, the organisation has a control design problem, an escalation problem, and a leadership problem at the same time. Practitioners should treat monitoring as an end-to-end lifecycle that includes ownership, change control, and auditability.
A question worth separating out:
A: Accountability normally sits with the regulated firm, not the monitoring tool. Compliance, fraud, risk, and operations leaders must define ownership for rule design, alert review, escalation, and reporting. Governance should also make clear who approves tuning changes, who signs off on exceptions, and who responds when monitoring gaps create regulatory or financial exposure.
👉 Read our full editorial: Transaction monitoring fails when coverage gaps go unescalated
This post was modified 7 days ago by NHI Mgmt Group