Institutional · Post-Execution Monitoring

Sidian Sentry

The gap this closes

Most MAS-regulated institutions run post-execution AML/CFT monitoring with legacy rule-based systems designed for human transaction volumes. Alert queues become unmanageable at AI transaction speeds. STR drafting at scale is time-consuming and inconsistent.

Post-execution AML/CFT transaction monitoring for MAS-regulated institutions. Real-time pattern detection, automated MAS STR drafting, and a permanent compliance archive — available standalone or integrated with the Guardian SDK.

How It Works

Sentry runs continuously after every transaction — detecting patterns, raising alerts, and generating STR documentation automatically.

Step 1
Transaction executes in your infrastructure
A transaction completes through your existing payment system. Sentry operates post-execution — it does not block or slow the transaction flow.
Step 2
Sentry monitors continuously
Sentry applies MAS AML/CFT Notice-aligned monitoring rules to every transaction in real time — not in batch.
Step 3
Pattern analysis across transaction history
Sentry surfaces patterns that single-transaction checks cannot detect — velocity anomalies, counterparty clustering, structuring behaviour, and drift from established customer profiles.
Step 4
Alert triggered — compliance team notified
When a concern is detected, your compliance team is alerted immediately with full transaction context.
Step 5
MAS STR draft generated automatically
Sentry generates a pre-populated MAS Suspicious Transaction Report draft — ready for your team to review, amend, and submit to STRO.
Illustrative sandbox environment — sample data shown for concept demonstration only. Not live transaction data or a production compliance metric.
Guardian SGSV Compliance Dashboard — Sandbox
Sentry — quarantine & human-in-the-loop
Quarantine engine — STR automation with human-in-the-loop review
Quarantine Rate
2.6%
of all Guardian transactions
HITL Approved
298
cleared as false positive
SLA Compliance
94.2%
resolved within SLA window
STR Filing Rate
18.7%
of quarantined cases
Why Sentry

Not a Legacy Monitoring System.

Three structural limitations in standard post-execution monitoring become critical when AI agents are initiating transactions at machine speed.

Legacy monitoring was calibrated for human transaction volumes
Rule-based systems and batch review workflows were designed for the alert volumes that human operators produce. At AI transaction speeds, alert queues become unmanageable and the genuinely suspicious patterns get buried.
Post-execution detection is too late for the highest-risk scenarios
In sanctions breach and structuring scenarios, the damage occurs at execution — not at detection. A monitoring system that flags a suspicious transaction after the funds have moved cannot prevent the harm.
Pattern detection at machine speed requires continuous analysis
Structuring patterns and counterparty clustering schemes can complete themselves before a batch monitoring system has assembled enough data to surface them. Sentry analyses every transaction in real time.
MAS Examination

When MAS asks for your monitoring records

Without Sidian Sentry
Monitoring ran in batch. No per-transaction monitoring record was generated at the time of execution. The institution cannot produce a complete, real-time audit trail.
With Sidian Sentry
Every transaction has a real-time monitoring record — rules applied, alert status, pattern analysis, and any STR actions taken. Export the complete archive for the requested period in minutes.
Regulatory Context

The MAS Requirements Sentry Addresses

MAS AML/CFT Notice
Suspicious Transaction Reporting
What MAS requires
MAS-regulated institutions are legally required to file Suspicious Transaction Reports with STRO when they have reason to suspect money laundering or terrorist financing.
How Sentry satisfies it
Sentry detects the alert and automatically generates a pre-populated STR draft — including narrative, transaction data, counterparty details, and supporting evidence.
MAS AML/CFT Notice
Transaction Monitoring Obligations
What MAS requires
Financial institutions must monitor transactions on an ongoing basis to detect unusual or suspicious patterns. Rule-based monitoring alone is inadequate for AI-driven transaction flows.
How Sentry satisfies it
Sentry monitors every transaction in real time and analyses patterns across transaction history — velocity, counterparty clustering, structuring behaviour, and deviation from customer profiles.
MAS Technology Risk Management
AI Transaction Oversight
What MAS requires
MAS TRM Guidelines require institutions deploying AI in financial operations to maintain oversight mechanisms and complete audit trails for AI-influenced transactions.
How Sentry satisfies it
Sentry provides an immutable record of every transaction monitored, every alert raised, and every STR draft generated. Seven-year retention. Fully exportable.

Post-Execution. Always On. MAS-Aligned.

MAS STR Drafting — Minutes, Not Hours
When a transaction triggers a monitoring alert, Sentry generates a pre-populated STR — narrative, transaction details, and supporting evidence. Your compliance team reviews and submits to STRO.
Pattern Detection Across Transaction History
Sentry analyses transaction history to surface patterns that single-transaction checks cannot detect — velocity anomalies, network clustering, and behavioural drift.
Compliance Record Archive — 7 Year Retention
All monitoring decisions, alerts, escalations, and STR drafts retained in an immutable archive for seven years. Ready for MAS examination at any time.
Configured to Your Risk Appetite
Alert thresholds, monitoring rules, and escalation workflows configured to your institution's own AML/CFT risk appetite statement.
Complete the picture

Sentry monitors everything after execution.
The Guardian SDK validates compliance before.

Together they provide full-spectrum coverage. One Guardian SGSV compliance engine. Two deployment layers. No gap.

Deployment Options

Two Ways to Deploy Sentry

Sentry works standalone or alongside the Guardian SDK for full-spectrum coverage.

Path A — Standalone
Sentry only
Deploy Sentry as your primary post-execution AML/CFT monitoring layer. Works with any existing payment infrastructure.
AI Agent
your system
→
Payment Rail
your infrastructure
→
Sentry
monitors here
Real-time monitoringSTR auto-drafting7-year archivePattern detection
Path B — Full-Spectrum
Guardian SDK + Sentry
Add Sentry to a Guardian SDK deployment for complete coverage. One Guardian SGSV engine — no gap between the two layers.
AI Agent
your system
→
Guardian SDK
pre-execution
→
Payment Rail
your infrastructure
→
Sentry
post-execution
Pre-execution complianceCLEARED/HELD decisionsFull-spectrum auditNo compliance gap

Enquire About Sidian Sentry

Tell us about your institution's AML/CFT monitoring requirements.

Select…
Select…

Or email info@sidian.sg directly.