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.

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.

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 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 (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.

Transaction Monitoring now supports Advanced Reporting, giving compliance teams direct query access to TM data via a structured dataset. Users can build custom reports and exports across alerts, alert assessments, alerted transactions and transaction assessments.

The dataset is exposed as a set of queryable tables. Each table is documented with its available fields and can be joined to build cross-entity or cross-alert views.

Transaction Monitoring APIs route through the unified Fenergo SaaS API gateway (TMProxy) and share the same OAuth 2.0 authentication flow as CLM and other Fenergo SaaS APIs. Integrators with existing Fenergo SaaS credentials can call TM APIs without a separate authentication setup.

When an entity is deleted in CLM, all associated Transaction Monitoring data is now automatically purged as part of the data deletion process. This includes alerts and all related notes, comments, assessments, attachments, and outcomes. Once removed, they no longer appear in any alert grid. Suspicious Activity Reports (SARs) and whitelist entries for the deleted entity are also fully removed.

Transactions contained within alerts are reviewed at the point of deletion: if the counterparty is not a Fenergo entity, the transaction is removed from both CLM and TM; if the counterparty is an onboarded Fenergo entity, the transaction is retained. A periodic housekeeping process additionally clears any orphaned transactions that remain in the alerted transaction store without an associated alert.

The Observability dashboard gives Transaction Monitoring clients a single place to monitor the health of transaction ingestion and rule execution. It reports on the volume and outcome of transactions and scheduled rule runs over a selected time range, helping operational teams confirm that data is flowing in correctly and that rules are running as expected.

The dashboard adapts to how your tenant ingests data. Real-time tenants see transaction ingestion metrics, while batch tenants see file and batch processing metrics. Both tenant types see rule execution metrics. Data shown on the dashboard is retained for 30 days.

A set of improvements to Entity Whitelisting, making it easier to create, manage, and monitor whitelist entries from the Alerts Dashboard.

• Expiry notifications: the Whitelist button now shows a health indicator for entries pending approval, expiring within 7 days, or expired. Only visible to users with the approve permission.
• Active whitelist chip on alerts: a Whitelisted N chip appears next to the main entity name in an alert when N active whitelists exist, with a hover popover and quick access to the drawer.
• Whitelist Source: each entry now records whether it was created manually or from an alert (with a link to the originating Alert ID).
• Status summary header: the Whitelist drawer now shows a count per status at the top; clicking a status filters the list.
• Expired request handling: requests that pass their expiry date without being actioned are marked Expired with a banner; Approve/Reject buttons are removed.
• Wildcard display: wildcard entries now show All rules or All counterparties with a globe icon instead of All.
• Request Notes character counter: the Notes field now displays a live count against the 500-character limit.