Calculate transaction monitoring alerts and analyst needs

Enter transaction volume, alert rate and team capacity to see alerts, true hits, analysts needed and backlog at a chosen threshold.

Transactions and alerts

The payments business, its transactions and its team are made up.

Review team
Alert threshold
← TighterLooser →

Analysts needed

42
Alerts a day1,000
True hits a day40
Backlog growth a day160
Backlog after 30 days4,800

1,000 alerts a day need 42 analysts, the team of 35 reviews 840 a day, so the rest wait and the backlog grows.

Alerts and analysts across thresholds

Today’s threshold raises 1,000 alerts a day with 40 true hits, and the threshold on the slider raises 1,000 alerts with 40 true hits.

Get the result by email

Set alert rules and thresholds in your business’s decision rules, then test each change on past transactions before it goes live. Start your trial

How alerts and analysts are calculated

Alerts are transactions multiplied by the alert rate, then adjusted by the slider. True hits are alerts that are not false positives and fall more slowly than alerts as the threshold tightens, while analysts needed are review hours divided by an analyst’s review hours.

Today’s alerts = Transactions a day × Alert rate today
Today’s true hits = Today’s alerts × (1 − False positive share)
Alerts a day = Today’s alerts × Alerts as share of today’s
b = log(True hits kept when alerts halve) ÷ log(50%)
True hits a day = Today’s true hits × (Alerts as share of today’s)^b
Review hours = Alerts a day × Minutes per alert ÷ 60
Analysts needed = ⌈Review hours ÷ Review hours per analyst⌉
Alerts the team can review = Analysts on team × Review hours per analyst × 60 ÷ Minutes per alert
Backlog growth a day = max(0, Alerts a day − Alerts the team can review)
Backlog after 30 days = Backlog growth a day × 30

The same formulas apply to the numbers above.

Today’s alerts = 250,000 × 0.4% = 1,000
Today’s true hits = 1,000 × (1 − 96%) = 40
Alerts a day = 1,000 × 100% = 1,000
b = log(80%) ÷ log(50%) = 0.322
True hits a day = 40 × 1^0.322 = 40
Review hours = 1,000 × 15 ÷ 60 = 250.0
Analysts needed = ⌈250.0 ÷ 6⌉ = ⌈41.7⌉ = 42
Alerts the team can review = 35 × 6 × 60 ÷ 15 = 840
Backlog growth a day = 160 → Backlog after 30 days = 4,800

True hits at another threshold are an estimate based on the share kept when alerts halve, not a measurement. Analysts needed are rounded up to whole people.

Transaction monitoring alert calculator

Transaction monitoring reviews transactions for activity that may be suspicious. This calculator estimates alerts from transactions and the alert rate, then estimates true hits from the false positive share.

For fraud transaction monitoring or suspicious transaction monitoring, the alert load shows how many alerts the team needs to review. Compare that with the team’s capacity, then use the threshold slider to see how alerts and estimated true hits change.

Common questions

How many AML analysts do I need for transaction monitoring?

The calculator divides daily review hours by the hours an analyst spends reviewing alerts each day, then rounds up to whole people. Review hours come from the alerts and the time spent on each alert.

What is the transaction monitoring false positive rate?

It is the share of alerts that turn out not to be suspicious once reviewed. The calculator uses that share to estimate the true hits among the alerts.

How do I estimate an alert backlog?

Backlog growth is the alerts a day minus the alerts the team can review, when that difference is above zero. The calculator also shows the backlog after 30 days at that growth rate.

How does threshold tuning affect transaction monitoring alerts?

The slider changes alerts as a share of the alerts at today’s threshold. The calculator estimates true hits at the new threshold using the share of true hits kept when alerts halve.

What is transaction monitoring?

Transaction monitoring reviews transactions for activity that may be suspicious. This calculator estimates the alerts raised at a threshold and the true hits among them.