Monitoring Rules

Defines the automated transaction-monitoring rules (mfi.aml.monitoring.rule) that scan activity for red flags - structuring, velocity spikes, threshold breaches and unusual patterns. Each rule sets its conditions and the alert it raises when triggered. Tuning these rules controls the balance between catching risk and generating noise.

Workflow

Open Monitoring Rules under Compliance.
Create a rule and choose its pattern (velocity, structuring, threshold).
Set the thresholds, look-back window and target population.
Define the alert severity the rule raises on a hit.
Activate the rule and review the alerts it produces to tune it.

Fields reference

Every field on this screen, drawn from the live data model.

Field	Type	Required	Description
Parameters `parameters`	Long text	—	JSON-encoded rule parameters
Name `name`	Text	Yes	Name
Rule Type `rule_type`	Choice: Velocity, Amount Threshold, Round Amount Pattern, Dormant Reactivation, Unusual Pattern, Cross Border, Cash Intensive, Structuring	Yes	Rule Type
Severity `severity`	Choice: Low, Medium, High, Critical	Yes	Severity
Has Message `has_message`	Yes/No	—	Has Message
Sequence `sequence`	Number	—	Sequence
Action `action`	Choice: Alert Only, Block Transaction, Escalate to Compliance	—	Action
Active `active`	Yes/No	—	Active
Lookback Days `lookback_days`	Number	—	Lookback Days
Description `description`	Long text	—	Description

Notes & rules

Rules detect structuring, velocity and threshold-breach patterns.
Each rule maps to the alert severity it generates.
Look-back windows let rules assess cumulative behaviour.
Tuning thresholds manages false-positive volume.

Technical model: mfi.aml.monitoring.rule · Record: AML Transaction Monitoring Rule