// Module 04 · Monitoring

Monitoring sensors.

Ongoing transaction and activity monitoring driven by configurable rules and scenarios, testable against your own historical data

Live Detection · Active Cadence · 5 min
// Overview

Overview

The Monitoring system provides continuous transaction and suspicious-activity monitoring through a configurable rule and scenario engine, surfacing risk early.

Detection scenarios you configure run on a scheduled cadence — every five minutes — over ingested and imported transactions, so suspicious patterns surface shortly after the activity reaches the platform.

Every rule can be tested against your historical data before it goes live, and every alert traces back to the exact logic that raised it — transparent, examiner-friendly detection.

// Features

Key Features

Configurable, testable detection across your transaction activity.

01

Rule & Scenario Engine

Deterministic rules and scenarios you configure in the UI to detect suspicious patterns — transparent, examiner-friendly logic.

02

Scheduled Monitoring

Detection scenarios run on a five-minute scheduled cadence over ingested and imported transactions.

03

Historical Backtesting

Test rules against your historical data and review rule-performance statistics before enabling them.

// Outcomes

Benefits

01
Early Risk Detection
Scheduled scenario runs every five minutes surface suspicious activity shortly after it lands, rather than in end-of-day review.
02
Configurable Scenarios
Business users build detection conditions in the UI — thresholds, patterns, and typologies — without vendor code changes.
03
Fresh Coverage
Scheduled runs every five minutes keep the monitoring picture close to current activity.
04
Backtesting Confidence
Test every rule against historical data and review its performance statistics before it goes live.
05
Alert-Ready Output
Scenario hits become alerts with severity, SLA clocks, and skill-weighted routing the moment they are raised.
06
On-Premises Deployment
Runs entirely on your own infrastructure — your IIS and SQL Server — so the monitoring database stays under your control.
// i/o surface

Integrations

How Monitoring connects with the systems around it — inbound activity feeds, downstream destinations, APIs, and the jobs that keep detection on schedule.

Inputs
  • Core banking extracts
  • Transaction bulk-ingest API
  • Imported transaction files
  • Client profile data
Outputs
  • Alert management
  • Case management
  • Regulatory reporting
APIs
  • Transaction ingest API
  • Alert management API
  • Case management API
Scheduled Jobs
  • Scenario execution · 5-minute cadence
  • Rule execution
  • Alert escalation & SLA checks
// illustrative targets

Performance Metrics

60%
Faster Reviews
Reduction in alert review time
80%
Fewer False Positives
Reduction in false positive alerts
85%
Detection Accuracy
True match identification rate
99%
Monitoring Coverage
Transactions evaluated by scheduled scenarios
Illustrative targets
// Next step

Ready to enhance your monitoring capabilities?

Discover how our monitoring system can protect your organization

Request a Demo
// FAQ

Frequently Asked Questions

What does Monitoring track?

Monitoring evaluates the transactions your institution loads — wires, payments, cash — against the rules and scenarios you configure, raising alerts on hits.

How does detection work?

Detection is a deterministic rule and scenario engine: you define conditions in the UI, test them against historical data, and every alert traces back to the exact logic that fired. AI in AmlShield is a separate, opt-in assist layer for investigation summaries and narratives — audited on every use, never making detection decisions.

Is monitoring real-time?

Monitoring runs as scheduled jobs on a five-minute cadence rather than inside the payment path. In practice, suspicious activity surfaces within minutes of reaching the platform.

What transaction volume can it handle?

Detection runs over the transactions your institution brings in through the bulk-ingest API and file imports; capacity is assessed for your data volumes during implementation.

How does Monitoring connect to alerts and cases?

Scenario hits are routed into alert management for triage with severity and SLA, and confirmed suspicious activity flows into case management with complete audit trails.

Can detection thresholds be tuned?

Yes. Rule conditions, thresholds, and scenario parameters are fully configurable, and you can backtest any change against historical data before enabling it.

// Ready when you are

Ready to Transform Your AML Compliance?

Join leading financial institutions using AML SHIELD to combat financial crime