12 posts tagged with "Transaction Monitoring"

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.

My Recent Alert Activity Widget​

A new collapsible Alert Assessment Activity panel is available on the My Alerts dashboard, showing the 10 most recently assessed alerts by default. Select View More to expand to 20. Hover over an alert to see a quick popover, or open it directly in the right-hand drawer. The panel is collapsed by default and will collapse automatically when the drawer is opened.

Configurable entity data​

A new Right Hand Drawer Display dropdown is available in the Entity Profile Configuration area, allowing configurators to select which requirement category is shown in the entity panel on the Alert Details page. The panel title updates to reflect the selected category name. If no category is selected, existing behaviour is preserved.

Financial Crime Risk (FCR) tab​

The FCR tab is now available in the entity right-hand drawer on the Alert Details page, consistent with the entity profile page. Visibility follows existing FCR permissions.

Live Search Across Dashboards and Grids​

Search inputs now update results automatically as you type so there is no need to press Enter or click search.

The Transaction Monitoring Observability API now supports on-demand Transactions Data Export, enabling users to request and retrieve a report of transaction IDs ingested on a specific date. This provides a structured mechanism to reconcile which transactions have been received by Transaction Monitoring for a given day.

Exports return transaction identifiers (modification IDs) only for the requested date.

Exports are generated asynchronously:

1. Trigger a report for a chosen date and receive a trigger_id
2. Use the trigger_id to retrieve the report once it is ready

Note: This export is not a substitute for alert data sources.

We have introduced a number of usability enhancements to the Alert Dashboard to improve analyst workflow and efficiency:

• Activity Log Sorting: Sorting functionality has been added to the Activity Log.
• Alert Assessment Initiation: Users can manually trigger an alert journey.
• Alert Grid Configurability: Users can customise the columns displayed on the Alert Dashboard. Documented in the Alert Visibility section.
• Alert Source Column: Alert Source is now available in Alert grids.
• Alert Status in Alert Details: Alert status is now visible within the Alert Details view.
• Closed Alert Status Visibility: Status is now displayed for closed alerts.
• Copy to Clipboard (External ID): A copy icon has been added to External ID fields for ease of use.
• Entity ID in RHD: Entity ID is now displayed in the Entity Right Hand Drawer, with a copy-to-clipboard option.
• Frozen Columns: Key columns, including selection and row actions, are fixed to improve navigation across wide datasets.
• Hover Row Actions: Row-level actions are now available on hover for quicker interaction.
• Improved RHD Behaviour: The Right Hand Drawer now pushes content rather than overlaying it.
• Previous Assessments Relocation: Previous assessments have been repositioned for improved usability.
• Search by External ID (Alerted Transactions Grid): Users can search by External ID within the Alerted Transactions grid.
• Search by External ID (Entity Transactions Grid): Users can search by External ID within the transaction grid on the entity profile page.
• Sending and Receiving Partner Columns: Sending Partner and Receiving Partner are now available as columns within transaction grids.
• Transactions Grid Filtering: Users can filter transactions within the transaction grid to refine results.

These updates provide greater flexibility and streamline interaction with alert data across different investigation scenarios.

Entity Whitelisting allows an entity to be exempt from alert investigation for a specific counterparty and a specific rule, for a defined period. While the whitelisting is active, future alerts that match the same rule, entity, and counterparty are treated as whitelisted and do not need to be assessed in the same way.

Whitelists can be created as:

• Manual Whitelists which are created from the Alerts Dashboard.
• Whitelists from an alerted transaction within an alert.

The audit trail of a Whitelist can be found on the main entity profile in the audit drawer.

Policy fields that use conditional logic driven by values derived from core customer fields, such as Age from Date of Birth may feed directly into the entity risk assessment and may also be used in business rules. Instead of refreshing these values in the context of a journey, these fields can be updated as part of the behavioural risk re-evaluation flow. These fields will be refreshed before any risk processing runs, so the latest values are used by the risk model and downstream rule logic.

These update are part of the iterative customer experience enhancements being delivered within the Transaction Monitoring (TM) case management module in Fenergo. The primary objective of these enhancements is to consolidate all information required for an analyst/ investigator to assess an alert efficiently, accurately and quickly. The case management view has been designed to provide optimal user experience, ensuring the most relevant information is readily available within the alert and presented with suitable context to determine whether the activity is suspicious.

As a result, analysts can now easily access and navigate between Alert, Entity, and Transaction information, while maintaining full visibility of the ongoing investigation. This seamless context switching reduces friction, improves efficiency, and supports more informed and consistent alert decisioning by keeping all relevant alert, entity, and transaction information in a single, unified view, removing unnecessary navigation.

• Addition of the Right-Hand drawer with three different context Entity, Alert and Transaction
• Addition on information popover for Alerts and Transaction, allowing users to see a summary of either and the ability to access the RHD
• Alert page enhancements, addition of Entity details, reorganisation of page, enhanced view
• Update of EPP Alerts grid
• Improvement of Alert Assessment flow, using the RHD
• Addition of Counterparty names to Alert
• Addition of Transaction Summary to Transactions grid
• Addition progress bar to Alert Assessment
• Addition and extension of Alert Activity to RHD
• Add Entity Risk to Alert views

Manual Alerts allow authorised users to create Transaction Monitoring (TM) alerts directly from the Fenergo user interface without relying on the detection engine or external API integrations. This capability supports operational and investigative scenarios where an analyst determines that an alert should be raised.

Manual Alerts can be created as:

• Transactional Manual Alerts – linked to one or more selected transactions.
• Non-Transactional Manual Alerts – created at entity level without associated transactions.

Once created, alerts follow the standard Alert Assessment workflow.