Skip to content
5 transaction monitoring mistakes that keep fincrime teams up at night
Jade ThirdEye7 Jul 255 min read

5 Transaction Monitoring Pitfalls Keeping FinCrime Teams Up at Night

Recent years have provided sobering reminders of what happens when transaction monitoring goes wrong. TD Bank's staggering $3 billion penalty for leaving 92% of transactions unmonitored and NatWest's £265 million fine for systematic failures in monitoring suspicious cash deposits demonstrate that even established institutions can make fundamental errors in their approach to transaction monitoring.

For mid-sized financial institutions across Australia, New Zealand, and the UK, these high-profile failures offer crucial lessons. The stakes are high – compliance costs continue to rise across the industry, yet an estimated $2 trillion in illicit transactions still flow through the global financial system annually.

We've identified five critical mistakes that continue to trip up financial institutions when implementing transaction monitoring systems. Here's what to watch out for – and how to avoid becoming the next cautionary tale.

1. Building on Shaky Foundations: Inadequate Risk Assessment

The most fundamental mistake institutions make is rushing into technology selection without conducting a thorough risk assessment. This isn't about ticking a regulatory box – it's about understanding your specific vulnerabilities before you choose the tools to address them.

Your risk assessment should examine your transaction types and volumes, customer profiles, product mix, delivery channels, and geographical exposure. A building society focused on residential mortgages faces different risks than a credit union offering personal loans to diverse communities. Yet, too many institutions select transaction monitoring systems based on what worked for other organisations rather than what fits their unique risk landscape.

A lack of effectiveness often occurs when AML rule selection is not risk-based – many rules are implemented because they're available in a vendor solution, but without a solid foundation in an AML risk assessment.

The consequences of this mistake extend far beyond compliance. Without a solid risk assessment as the foundation, you'll end up with monitoring rules that generate thousands of false positives while missing genuine threats – the kind of systematic failures seen in major enforcement actions.

2. Choosing Rigid Systems That Can't Adapt

The regulatory landscape isn't static, and neither should your transaction monitoring system be. Regulators across Australia, New Zealand, and the UK are intensifying their focus on financial crime prevention, with enhanced expectations for robust monitoring and reporting systems. Yet many institutions choose systems that lock them into inflexible frameworks.

The key question isn't whether your system can handle today's requirements – it's whether your compliance team can quickly adapt rules when regulations change tomorrow, when criminal tactics evolve, or when you gain new insights from your data. Can they test new scenarios safely before deploying them? Can they adjust thresholds without waiting weeks for vendor support?

Real-time capabilities have become table stakes, but true flexibility goes deeper. Your system should allow for dynamic parameterisation based on customer segments, risk ratings, and business lines. The ability to easily modify monitoring rules without extensive IT involvement isn't a luxury – it's essential for staying ahead of both regulatory changes and evolving criminal tactics.

3. Underestimating Data Quality and Model Compatibility

Often, AML implementation projects uncover data architecture issues with source systems that need to be addressed as part of the project to ensure adequate and accurate data is flowing into the AML transaction monitoring system. This discovery typically happens after contracts are signed and implementation timelines are set, creating costly delays and compromises.

The mistake isn't just about data quality – it's about data model compatibility. Many vendors offer standardised data models that require you to transform and restructure your data to fit their framework. This approach can limit your ability to utilise all available information in your monitoring rules and may force you to exclude valuable contextual data.

Before committing to any system, ensure the vendor can tailor their data model to your specific needs rather than forcing you into a one-size-fits-all approach. Your monitoring effectiveness depends on your ability to incorporate KYC data, customer and behavioural information, and transaction context, not just basic financial transaction details.

4. Viewing Vendors as Software Providers Rather Than Partners

For mid-sized institutions, the relationship with your transaction monitoring vendor often matters as much as the software itself. Unlike tier-one banks with extensive in-house expertise, you'll rely heavily on vendor guidance for implementation, ongoing support, and regulatory updates.

This is where many institutions make a critical error: they evaluate vendors purely on features and price, overlooking the human element. When compliance challenges arise – and they will – do you have access to senior staff who understand your business, or will you be relegated to a generic helpdesk?

The vendor you choose takes on significant responsibility for helping you protect your institution and customers. Look for providers with demonstrated expertise in your markets, named contacts rather than call centres, and a track record of supporting institutions through regulatory changes. The cheapest option often proves to be the most expensive when you factor in the hidden costs of inadequate support.

5. Ignoring Total Cost of Ownership and Operational Impact

The final mistake is focusing on initial pricing while ignoring the total cost of ownership. Transaction monitoring systems don't just require upfront investment – they demand ongoing resources for rule management, alert investigation, and system maintenance.

A system that generates excessive false positives might have a lower licence fee, but the operational costs can be crippling. A large number of generated alerts are closed as false positives, driving up operational costs unnecessarily and leading to resources being wasted on investigating non-criminal activities.

Consider the full operational picture: training requirements, ongoing vendor support costs, integration expenses, and the impact on your team's productivity. A more expensive system that reduces false positives by 50% might deliver better value than a cheaper alternative that overwhelms your analysts with irrelevant alerts.

 

Getting It Right: A Balanced Approach

The institutions that succeed with transaction monitoring take a balanced approach that considers technology, process, and partnership equally. They start with a comprehensive risk assessment, prioritise flexibility and partnership over features and price, and think long-term about operational sustainability.

Most importantly, they recognise that transaction monitoring system selection is a strategic decision with long-term implications. The effort involved in implementation, data integration, and staff training makes switching systems a significant undertaking, making the initial decision all the more critical.

Ready to avoid these costly mistakes? Our comprehensive Transaction Monitoring Buyers Guide provides detailed evaluation frameworks, vendor assessment criteria, and implementation best practices specifically designed for mid-sized financial institutions.

Download your copy here to access the complete checklist, which guides your selection process and helps you choose a system that truly fits your needs.

Financial crime is relentless – but with the right approach and the right partner, you can stay ahead of both regulatory requirements and criminal threats.