Skip to main content

Comparison Operators, Empty-Value Operators and Same-Side Identifiers in Detection Rules

Detection rules in Transaction Monitoring now support factor operators that compare two numeric fields on the same transaction, for example Redemption Amount is at least 80% of Assets Under Management, with no Previous transactions configuration needed. New is undefined and is defined operators let rule authors detect fields that are null, missing or empty, and can be combined with does not contain in an any true group so that transactions with no value are no longer missed.

Scheduled rules that use a dynamic main entity can now use same-side transaction identifiers, such as same sender AND same receiver, and can mix them with reverse-role identifiers in a single filter group. Identifiers must use the same field on both sides and cannot be set on nested filter groups.

These enhancements introduce no new or changed permissions.

TM Alerts Performance Upgrades

Transaction Monitoring alert pages now respond faster and more predictably, including the first time you open one after a quiet period (cold start). We have upgraded the infrastructure behind Alerts so it stays ready to serve requests, which removes the occasional slow first load that some users experienced.

The improvement applies across the alert investigation journey, from the Alerts dashboard through alert assessment, transaction details and entity whitelist indicators. Typical page loads are quicker, and response times for the slowest page loads have improved by around 50%.

Cross-Region Disaster Recovery for Transaction Monitoring

Transaction Monitoring now supports cross-region disaster recovery, available on request and subject to configuration. In addition to the existing in-region, multi-Availability Zone resilience, Transaction Monitoring environments configured for cross-region DR can be recovered in a secondary AWS region in the event of a full region outage, extending business continuity beyond a single AWS region.

Previously, Transaction Monitoring DR was confined to the primary AWS region, and recovering from a full region outage required manual intervention and redeployment to a new region.

info

Cross-region DR is not enabled by default. It is available on request and is configured per environment. To request cross-region DR, or for details on the recovery region and recovery objectives, please contact your Fenergo representative.

Alerts Dashboard Summary for Transaction Monitoring

The Alerts Dashboard now opens with a summary of alert workload on both the My Alerts and All Alerts tabs, so users can see where attention is needed before working through the list.

Summary cards above the grid show team-wide metrics on All Alerts (open alerts and average score, unassigned alerts, SLA status, and alerts closed in the period) and personal metrics on My Alerts (average time to assess, oldest open alert, SLA status, and entity risk profile). A charts panel presents the same data visually, with an SLA status breakdown on both tabs plus Assigned vs Unassigned on All Alerts and Risk profile on My Alerts. The Summary for dropdown filters the cards and charts to the last 7, 30 or 90 days, and both panels can be collapsed.

Performance Upgrades

The Transaction Monitoring side panel now opens faster and transfers less data, so users can get to the information they need sooner when investigating an alert.

Sections in the side panel now load only when they are needed. The Transactions section no longer retrieves data until it is expanded, and the values in filter dropdowns are retrieved only when a dropdown is opened. In our comparison, total server processing time when opening the panel is around 50% faster.

No configuration is required. The improvements apply automatically.

Aggregated Alert Enhancements: Advanced Reporting & Whitelisting

Advanced Reporting and whitelisting have been extended to support aggregated alerts (alerts triggered when multiple rules in a rule group fire together, as distinct from individual alerts triggered by a single rule).

Advanced Reporting now includes an aggregate scope field on the alerts table, plus two new tables — alert_rules and alert_rule_transaction_links — so the contributing rules and transactions behind an aggregated alert can be reported on individually or joined back to the alert.

The aggregated alert detail UI now shows rule-level and transaction-level whitelist indicators. When every transaction across every rule in the group is covered by an active whitelist entry, the alert automatically transitions to Whitelisted status.

Alert SLA Status for Transaction Monitoring

Transaction Monitoring alerts now display a service level agreement (SLA) status alongside their existing status, so compliance teams can see, filter and prioritise alerts by SLA urgency without opening each one individually. This applies to alerts whose assessment process has an SLA configured.

Each alert shows an SLA status badge (In Progress, Approaching Due, Overdue, Paused, or Completed Overdue), with overdue time, committed allowance, and due date available on hover. SLA status is also filterable on the All Alerts and My Alerts views, with a Task SLA column on My Alerts for task-level status, and is included in Advanced Reporting to match the live dashboard and task view.

Aggregated Alerts and Rule Groups

Rule Groups allow detection rules to be configured together so that when multiple rules within the same group fire against the same entity, the resulting alerts are consolidated into a single Aggregated Alert. This gives investigators a complete view of connected suspicious activity within one investigation workflow.

Aggregated Alerts are identified by a dedicated icon in the Alerts Dashboard, with the Business Rule column displaying the Rule Group Name and the number of rules triggered. On the Aggregated Alert Assessment page, investigators can review the combined score, a full breakdown of triggered rules in the Business Rule Group section, and use a quick filter on the transaction grid to focus on the activity relevant to each individual rule.

ETL Alerts

ETL Alerts enables the bulk migration of historical or externally generated alert records into Fenergo via CSV upload. Institutions transitioning from legacy Transaction Monitoring systems can use this capability to seed pre-existing alert data into the platform, ensuring a complete and uninterrupted alert history from day one.

ETL Financial Crime Reports

ETL Financial Crime Reports (FCR) enables the migration of historical FCR records from legacy compliance systems into Fenergo via the ETL pipeline. Migrated records are created in Closed status with a source value of Migrated, preserving the original submission dates and external identifiers from the source system.