Alert backlog

Spec sheet // Glossary // ALERT BACKLOG
Glossary / A / Alert backlog
Glossary · Transaction monitoring

Alert backlog

Also called alert queue backlog, investigation backlog

Definition

An alert backlog is the build-up of transaction monitoring or screening alerts that have not been reviewed within a firm's own deadlines. Backlogs grow when alert volumes outrun analyst capacity. They delay suspicious activity reports and can leave criminal funds moving through accounts unchecked.

ALERTS RAISEDTRIAGEINVESTIGATIONSAR FILED
Fig. 1 · Alert backlog
BSA SAR rule · POCA section 330
Key rulesBSA SAR rule · POCA section 330
Applies toUS banks
RegionsUK · US · Global
01

How it works

Monitoring systems generate alerts that go into work queues for analysts. Firms set service levels for each stage, such as first review within a set number of days. When volumes spike after a new scenario, a merger or a data fix, or when staff are short, the queue ages. Teams then add staff, prioritise by risk score, close duplicate alerts and tune rules that produce mostly false positives.

Late reviews mean late reports. US rules require a suspicious activity report within 30 calendar days of initial detection. UK law requires disclosure as soon as practicable. Supervisors read a large or ageing backlog as a sign of weak systems and controls. Backlogs have featured in enforcement actions and remediation programmes overseen by independent monitors or skilled persons.

Step 1MeasureCount open alerts by age and risk.
Step 2PrioritiseWork the highest-risk and oldest alerts first.
Step 3Add capacityBring in extra analysts or automation for triage.
Step 4Tune rulesCut scenarios that produce mostly false positives.
Step 5ReportTrack the backlog to senior management and board.
02

The rules

US · 1 April 1996, recodified 1 March 2011BSA SAR rule31 CFR 1020.320, reports by banks of suspicious transactions

Requires a SAR within 30 calendar days of initial detection, extendable to 60 days if no suspect is identified.

US banks
UK · 24 February 2003POCA section 330Proceeds of Crime Act 2002, section 330, failure to disclose in the regulated sector

Makes it an offence not to disclose knowledge or suspicion of money laundering as soon as practicable after it arises.

Firms and staff in the UK regulated sector
03

Common questions

What causes an alert backlog?

Usually too many alerts for the available analysts. Common triggers are new or badly tuned scenarios, data fixes that release old alerts, business growth and staff turnover. High false positive rates make each of these worse.

Is an alert backlog a breach of the rules?

A backlog itself is not named in the rules. The risk is what it causes. Late reviews can mean suspicious activity reports filed after legal deadlines and weak systems and controls, both of which supervisors act on.

How do firms clear a backlog?

They add temporary capacity, prioritise alerts by risk and age, close duplicates and automate first-level triage. Lasting fixes come from tuning scenarios and thresholds so fewer low-value alerts reach analysts.