What is a false positive in AML?

A false positive in AML is an alert, from screening or transaction monitoring, that turns out on review not to indicate the risk it was raised for: a name match that is a different person, or a flagged payment that has an ordinary explanation. False positives make up most alert queues, and clearing them consumes most analyst time.

Why do false positives matter once agents act?

Every alert must be reviewed and disposed of with a reason. When queues are full of false positives, analysts rush, real cases wait and backlogs attract regulatory attention. Agents are an obvious answer, and alert work is a core job for compliance agents in the second line: they can read each alert, gather context and show why a match is or is not plausible.

The risk is turning that help into silent closure. An agent that closes alerts on its own is deciding what is suspicious, and every closure it gets wrong is a missed case nobody will see again. Whether an AI agent can reduce false positives in AML screening depends on keeping disposition with a person or, at most, giving an agent a narrow, certified capability for the plainest cases.

How do false positives arise?

Mostly from design choices that are deliberate. Screening uses fuzzy name matching so that misspellings and transliterations are caught; that also catches thousands of people who share a common name. Monitoring rules use thresholds set low enough to catch real laundering; those thresholds also catch payroll runs, property purchases and seasonal trade.

Firms accept many false positives to avoid missing true ones. The work is to clear them quickly and consistently, with a clear reason recorded on each, using an AML alert disposition record.

An example from a screening queue

Take a bank whose overnight rescreen raises an alert because a long-standing customer shares a common name with a sanctioned individual. The agent compares identifiers: the customer was born several decades after the listed person, lives in a different country, and has held the account for years with salary payments and household bills. It drafts a disposition with each mismatched identifier listed and recommends closure.

The analyst reads the draft in under a minute, agrees and closes it. The reason, the evidence and both the agent's recommendation and the analyst's decision are on file.

How is a false positive different from a false negative?

A false positive is an alert that should not have fired. It costs time. A false negative is a case of real laundering or a real sanctions match that raised no alert at all. It costs far more: the activity goes through, unreviewed.

The two trade off. Tuning rules to cut false positives tends to raise false negatives. That is why any change that reduces alert volume, including an agent recommending closures, should be tested against known true cases first. An agent that clears ten thousand false positives and one true match has not reduced risk.

Which terms sit next to false positive?

• True positive: an alert that, on review, does indicate the risk.
• Disposition: the recorded decision on an alert, with reasons.
• AML is the wider programme these alerts serve.

Where Pryme fits

In Pryme, a screening agent typically drafts dispositions at depth 2, and a named analyst decides. If a firm wants the agent to close a narrow class of plain mismatches itself, that is a separate capability, certified in Attest on the firm's own past alerts, including its true matches, and it lapses after 90 days.