Transaction Monitoring
The Transaction Monitoring module evaluates transactions in real-time against a configurable rule library. Alerts are generated automatically and managed through a full lifecycle workflow.
Adding transactions
You can add transactions individually or via CSV import:
POST /api/transactions
{
"entity_id": 123,
"amount": 9500.00,
"currency": "GBP",
"transaction_type": "wire_transfer",
"direction": "outgoing",
"counterparty_name": "Unknown Corp",
"transaction_date": "2026-02-01T10:00:00Z"
}For bulk import:
POST /api/transactions/import Content-Type: multipart/form-data file: transactions.csv
Rule types
FLD supports 7 rule types. Configure them in Transaction Monitoring → Rules:
| Rule Type | Description |
|---|---|
| Threshold | Alert when transaction amount exceeds a threshold |
| Velocity | Alert when volume/count in a time window exceeds limits |
| Structuring | Detect structured transactions below reporting thresholds |
| Geographic Risk | Alert on transactions with high-risk jurisdictions |
| Counterparty | Alert on transactions with specific counterparties |
| Time of Day | Alert on transactions outside normal business hours |
| Round Number | Alert on suspiciously round transaction amounts |
Alert lifecycle
Alerts progress through these stages:
- Open — newly generated, awaiting review
- Under Investigation — analyst has started review
- Escalated — flagged to MLRO or Compliance Manager
- SAR Created — suspicious activity report filed
- Closed — No Action — false positive, no further action
- Closed — SAR Filed — SAR filed and case closed
Pattern detection
FLD establishes behavioural baselines per entity and flags deviations. Navigate to Transaction Monitoring → Patterns to view detected patterns.
Creating a SAR from an alert
From any alert detail page, click Create SAR to pre-populate a SAR report with the alert data, entity details, and transaction records.