False Positives (in AML)

False Positives (in AML)

Definition

False positives in AML are alerts from transaction monitoring or screening systems that, after review, turn out not to involve suspicious activity or a true sanctions or PEP match. They consume analyst time and can delay legitimate payments, so reducing them without missing true risk is a central goal of AML tuning.

How it works

Any detection system balances sensitivity against precision. Broad rules and loose fuzzy-matching thresholds catch more true risk but also flag more legitimate activity. A false positive arises when an alert is reviewed and closed because the activity is explained (for example, a name match with a different date of birth, or a large payment consistent with the customer's known business). The opposite error, a false negative, is a missed true risk and carries regulatory and legal exposure.

Requirements by jurisdiction

No regulator sets a target false-positive rate, but each expects detection to be risk-based and well governed.

  • US: The FFIEC manual expects filtering criteria and thresholds to be reasonable, tailored to the institution's risk, documented, periodically reviewed and independently validated. OFAC enforcement actions have cited both failures: weak matching that missed listed parties, and alerts wrongly closed as false positives because of resourcing backlogs.

  • EU: Under the AMLR, applicable from 10 July 2027, monitoring must be proportionate to risk, and AMLA guidance will shape supervisory expectations for monitoring quality.

  • UK: The MLR require risk-based monitoring, and the FCA has reviewed firms' sanctions systems and controls, including screening calibration.

Common challenges

Poor data quality, missing secondary identifiers, generic thresholds applied to all customer segments, and rules that are never retired all inflate false positives. Tuning too aggressively risks suppressing genuine alerts, so changes need evidence and approval.

How teams handle it in practice

Teams measure alert outcomes by rule, segment customers so thresholds match expected behavior, enrich data to discount name matches automatically, and test proposed threshold changes against historical true positives before deploying them. FATF's 2021 report on new technologies notes that machine learning can reduce false positives and help identify complex cases, provided it is explainable and well governed. Compliance platforms like Corsa can pre-investigate alerts with AI agents so analysts spend time on likely true positives.

How Corsa helps:

AI Agents →

Frequently asked questions

What is an acceptable false positive rate?

Regulators do not set one. They expect institutions to justify their thresholds based on risk and to show that tuning does not cause genuine suspicious activity to be missed.

Can you simply raise thresholds to reduce false positives?

Only with evidence. Tuning should be tested against historical true positives, documented, and approved, because missed suspicious activity is a regulatory failure.

Do false positives matter for sanctions screening?

Yes. Wrongly closing a true match as a false positive can lead to a sanctions violation, which OFAC has cited in enforcement actions.

Automate this in your compliance workflows

Corsa unifies monitoring, cases, risk scoring and AI agents in one compliance OS.

The AI-native compliance & risk operating system for banks and financial institutions — unifying data, automation and decisions in one place.

© 2026 Corsa. All rights reserved.

The AI-native compliance & risk operating system for banks and financial institutions — unifying data, automation and decisions in one place.

© 2026 Corsa. All rights reserved.

The AI-native compliance & risk operating system for banks and financial institutions — unifying data, automation and decisions in one place.

© 2026 Corsa. All rights reserved.