Skip to main content

CX Updates

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

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.

Behavioural Risk

Behavioural Risk solution in Fenergo has been extended, to cater for multiple risk models. This feature will improve and extend the behavioral risk capabilities by adding the following:

  • Allow for the creation of multiple instances of the Risk Configuration in the Transaction Monitoring domain
  • Each separate instance of the configuration will have configurable scoping conditions
  • The data source type of ‘Current Entity’ can be used in the scoping conditions
  • Each separate instance can be uniquely named

Behavioural Risk

The Behavioural Risk Feature is a capability that identifies changes in an entity's actual transactional behaviour compared to their declared Expected Activity. When material deviations are detected, the system re-evaluates risk and can automatically trigger a journey if a higher risk threshold is reached. The feature operates as a nightly automated process, comparing expected activity held on the verified entity profile against actual transactional data observed over a 12-month period.

Specifying entity IDs in trxs sent to the single transaction ingestion API

Going forward, the single transaction ingestion API will no longer accept transactions that include both the entity's by_external_id and the embedded entity's external_id. For example, the following construction is no longer allowed:

{ 
  ...
  "receiver": {
    "by_external_id": "B7FA3237-72F6-49B3-9BA9-D35AC74F54EC",
    "external_entity_type": "business",
    "business": {
      ...
      "external_id": "3CB6FBC9-7106-42C2-988B-C6F363E58381",
      ...
    }
  },
  ...
}

In such cases the API will respond with:

"Only provide an entity by_external_id value or an embedded entity external_id value, not both."

Please only specify the entity via the by_external_id, e.g.:

{
  ...
  "receiver": {
    "by_external_id": "B7FA3237-72F6-49B3-9BA9-D35AC74F54EC"
  },
  ...
}

Or via the embedded entity object, e.g.:

{
  ...
  "receiver": {
    "external_entity_type": "business",
    "business": {
      ...
      "external_id": "3CB6FBC9-7106-42C2-988B-C6F363E58381",
      ...
    }
  },
  ...
}

Optimise rule execution logic inside ANY TRUE condition groups

An optimisation has been implemented to ensure more robust and predictable rule execution when using the ANY-true and ALL-true operators.

As part of this optimisation, ANY-true groups will only exit the rule execution when all referenced parameters in the conditions have null values or if they all result in a 'not present' result , while ALL-true exits execution when any referenced field is null or results in a not-present result .

Fields that are present but do not meet the specified condition are evaluated normally and impact only the condition outcome, not rule execution flow.

For example :

ANY-true: (field x == a; field y == b) -> exit if x is None AND y is None ALL-true: (field x == a; field y == b) -> exit if x is None OR y is None

Grid Alignment

Alert Grids Realignment of alert grids:

  • Ensuring All Alerts, My Alerts, Grouped Alerts and Alerts with this transaction grids are aligned and contain the relevant dataset including Alert Score and Stage
  • Ensuring each alert grid has the full set of available action, per row and in bulk
  • Aligning sorting and filtering on each grid, default sorting by date
  • Introducing saved filters
  • Extend default view to 20 rows with option to extend to 50
  • Include closed alerts on dashboard
  • Improve bulk select usability

Transaction Grids Realignment of tramsaction grids:

  • Ensuring transaction grids are aligned and uniform
  • Add external id
  • Add sorting and filtering, default sorting by date

Other CX Enhancements

  • Add Alert Outcome chip to confirmation modal and completed alert
  • Add sticky tabs to Alert dashbaord