The alert

A lead for an analyst, not a decision

This is what surfaces at the top of the queue. It says which segment moved, on which measures, on which day, and what the statistics behind it were. What it never says is whether to file. That judgement stays where the regulation puts it.

A
AML TriageAPP#eng-alerts
🔴 Structuring score jumped +168%segment=money-services-business
Baseline
18.245
Now
48.911
Confidence
99.9%
Started
Aug 13
Institution
Segment monitoring, 14 series
Segment
money-services-business
Accounts in segment
2,140
Share of alert queue
4.1%
Likely cause · Four independent behavioural measures on segment=money-services-business changed within two days of each other on Aug 13: deposit velocity roughly doubled while average ticket fell 42%, and cross-border share more than doubled. Splitting deposits and moving them out is the classic shape of structuring. No transaction-monitoring rule fired on it in isolation, and total alert volume is flat because this segment is 4.1% of the queue. This is a ranked lead for review, not a filing determination.
  1. 1.Pull the 2,140 MSB accounts ranked by contribution to the deposit-velocity shift.
  2. 2.Review the top decile against the existing structuring rule to see why it stayed silent.
  3. 3.Log the suppressed low-rank alerts with their q-values so the sample is auditable.
AcknowledgeFalse positiveCUSUM · q < 0.0001 · BH-corrected
A
AML TriageAPP#eng-alerts
🔴 Cash deposits per account per day jumped +107%segment=money-services-business
Baseline
3.456
Now
7.150
Confidence
99.9%
Started
Aug 14
Institution
Segment monitoring, 14 series
Segment
money-services-business
Accounts in segment
2,140
Share of alert queue
4.1%
Likely cause · Four independent behavioural measures on segment=money-services-business changed within two days of each other on Aug 13: deposit velocity roughly doubled while average ticket fell 42%, and cross-border share more than doubled. Splitting deposits and moving them out is the classic shape of structuring. No transaction-monitoring rule fired on it in isolation, and total alert volume is flat because this segment is 4.1% of the queue. This is a ranked lead for review, not a filing determination.
  1. 1.Pull the 2,140 MSB accounts ranked by contribution to the deposit-velocity shift.
  2. 2.Review the top decile against the existing structuring rule to see why it stayed silent.
  3. 3.Log the suppressed low-rank alerts with their q-values so the sample is auditable.
AcknowledgeFalse positiveCUSUM · q < 0.0001 · BH-corrected
The audit rule

Nothing is deleted. Every alert the engine ranks low is still in the queue, still dispositionable, and still carries the q-value and the detector trace that put it there. An examiner asking why an alert was deprioritised gets the same answer every time, in the same format, from the record rather than from somebody’s memory.