Skip to main content

Notice of Change: Alert Disposition

Change Notice Date: October 30th, 2026

Change Target Date: December 31st, 2026

Fenergo is updating the way alert dispositions are structured within the platform. This change affects how outcomes are recorded at both transaction and alert level, and introduces a new bulk disposition capability for transaction monitoring alerts.

What Does This Mean for You as a Fenergo User?​

Alert Disposition Model​

Transaction-level outcomes are simplifying. Currently, each transaction within an alert is assessed with a detailed outcome such as Fraud, Suspicious Activity, or False Positive. From December 31st, 2026, transactions will instead be marked as either Suspicious or Not Suspicious. The detailed categorisation moves to the alert level.

Alert-level outcomes will carry the detail. Once transactions have been assessed, analysts will select the specific outcome for the overall alert — for example, Fraud, Terrorism Financing, or Money Laundering — from a configurable list. This list is defined and maintained by each client, giving organisations the flexibility to tailor available outcomes to their own typology and regulatory requirements.

The existing rule whereby a single Suspicious transaction causes the alert to be assessed as a True Positive is retained. Outcome detail is now captured at the alert level rather than the transaction level.

Bulk Transaction Disposition​

Analysts will now be able to disposition all transactions within an alert in a single action, rather than working through transactions page by page. This applies to alerts containing up to 1,000 transactions, removing the previous limitation of dispositioning 20 or 50 transactions at a time.

Alert Outcome Scoping in Journey Configuration​

Because the detailed outcome is now captured at the alert level, it becomes available as a scoping condition within the alert assessment journey. Journey tasks can be scoped using the Last Assessment Outcome field on the Alert Assessment source, enabling differentiated task assignment, SLA rules, or workflow routing based on the specific nature of the alert. This capability was not available under the previous model.

Why Are We Making This Change?​

The previous model placed detailed outcome information at the transaction level, where it was not directly accessible for alert-level reporting, scoping, or routing. Moving this detail to the alert level makes it available across the platform in a more meaningful way — enabling richer journey configuration, cleaner reporting, and a more consistent analyst experience. The simplified transaction-level outcome (Suspicious / Not Suspicious) retains the information needed to drive alert assessment logic while reducing the cognitive overhead of per-transaction categorisation.

The bulk disposition capability addresses a longstanding friction point for analysts working high-volume alerts, where page-by-page assessment significantly extended review time.

Need Help or Have Questions?​

If you have any questions or require support with this transition, please contact your Fenergo Client Partner, who will be happy to assist you.

# Notice of Change: Alert External ID and Entity Validation

Change Notice Date: November 6th, 2026

Change Target Date: November 20th, 2026

In the current model, when an external alert is raised, the External ID field accepts a free-text string of any format. No validation is applied to the value supplied, so clients may be using a variety of identifiers such as reference numbers, system-generated codes or other text values. This External ID was not propagated anywhere before this change. There are also further validation checks applied to the Entity.

What This Change Means for You as a Fenergo SaaS User​

Following this change, the External ID will work as follows:

  • GUID format required: The External ID on an external alert must be a valid GUID (e.g. 3f2504e0-4f89-11d3-9a0c-0305e82c3301). Free-text strings will no longer be accepted.

  • Validation on alert creation: Validation is applied when an external alert is raised. If the External ID is not a valid GUID, the request will be rejected and the alert will not be created. However please note that the External ID is not mandatory, but if provided must be a valid GUID.

  • Advanced Reporting: The External ID is now available in Advanced Reporting. Going forward, values in this field will be in GUID format.

  • The entity validation change means that each message sent to the Event Ingress Create Alert business process goes through additional validations.

    • The first validation is on the Event Ingress API and is synchronous. It checks the parity between the EntityId field in the top most scope and MainEntityId inside the payload property. These properties must match, and mainEntityId must be present in the payload as a valid GUID. In case of a mismatch (or a missing one) the appropriate response from Event Ingress will be returned.
    • The second validation is inside the Create Alert Business Process. Main Entity will be validated against the Entity Data store, and in case the Entity is not found the request will be deemed failed, with the reason in the failure message. As this part is asynchronous, you will not see it in the Event Ingress response

Potential Impact to Clients​

This may be a change for clients who currently supply a non-GUID string as the External ID. Those clients must update their integrations to send a valid GUID before this change takes effect, otherwise external alerts will fail validation and will not be raised. Key Points:

  • The External ID on external alerts must now be a valid GUID.
  • Validation is enforced when an external alert is raised; non-GUID values will be rejected.
  • Clients using a free-text External ID must update their integrations to use a GUID.
  • The External ID is now available in Advanced Reporting.
  • The entity validation change means that each message sent to the Event Ingress Create Alert business process goes through additional validations.

Notice of Change: R&A Profile Versioning

Change Notice Date: September 22nd, 2026

Change Target Date: September 21st, 2026

Fenergo has introduced version control for Review & Approval V2 Profiles. Administrators who create and maintain R&A Profiles will notice a change in how profile configuration is managed from this release.

What Does This Mean for You as a Fenergo User?​

Profile configuration can no longer be saved and applied immediately. All changes to an R&A V2 Profile must now be made in a draft, which does not affect live journeys until it is published through a two-step approval process. A separate administrator with the Approve permission must review and publish the draft before it takes effect.

Journey cases are bound to the profile version active at the point of initiation and are unaffected by any subsequent configuration changes, including new published versions.

All existing R&A V2 Profiles have been automatically migrated to a first published version (V1). No manual action is required as a result of this migration.

Configuration teams should identify administrators with the Approve permission who will be responsible for reviewing and publishing drafted profile changes going forward.

Why Are We Making This Change?​

Previously, changes to an R&A Profile took effect immediately across all journeys using that profile, including those already in progress. This created risks around approval integrity and auditability — reviewers could unknowingly sign off on a task whose configuration had changed mid-review, with no record of what the profile contained at the time. Version control eliminates this risk, ensuring every case is assessed against a stable, auditable configuration, and that every change to a profile is deliberate and attributable.

Need Help or Have Questions?​

If you have any questions or require support with this transition, please contact your Fenergo Client Partner, who will be happy to assist you.

Notice of Change: Exclusion of Offboarding and Offboarded Products from Product Risk Assessment

Change Notice Date: August 26th, 2026

Change Target Date: September 29th, 2026

Fenergo is improving how the Product Risk Assessment task treats products that are leaving a client relationship. Products that are being offboarded, that have already been offboarded, or that are marked for deletion will no longer contribute to product risk assessments.

This change addresses long-standing feedback from clients: a product that a customer is in the process of closing, has already closed, or that is pending removal no longer represents live exposure, and continuing to score it can overstate an entity's product risk — and, where product risk feeds entity risk, the entity's overall risk position.

For tenants with the Product domain enabled, the change is available in all non-live tenants from August 26th, 2026, and will be enabled in all live tenants from September 29th, 2026. This communication serves as notice ahead of that rollout.

What Does This Mean for You as a Fenergo User?​

Once this change is in effect, a product is excluded from the Product Risk Assessment task if its lifecycle status is any of the following:

  • Offboarding
  • Offboarded

Excluded products are removed before the Product Risk Assessment begins. They are excluded from re-calculation of their individual risk score/rating, and they do not contribute to the aggregate product risk written back to the entity when Save to Entity is enabled.

Because a product's lifecycle status also tells you where it sits in the review cycle, the two exclusions apply to different populations: only a draft product can carry a status of Offboarding, and only a verified product can carry a status of Offboarded.

Excluded products are not displayed within the Product Risk Assessment task. For full transparency, they are recorded on the assessment result under excludedAggregateAssessments (visible when retrieving the assessment via API or using your browser's dev tools), with each entry carrying the product's aggregateId and lifecycleStatus. This allows you to confirm when and why products were excluded from any given assessment. Surfacing excluded products directly within the task view is planned for a future release.

  • What to expect:

    • This change applies only to risk assessments executed on or after the date it is enabled for your tenant. Existing product risk scores and ratings, and the entity risk values already derived from them, are not recalculated, restated or otherwise altered. No historical data is changed, and no backfill or migration is performed. Values change only when the Product Risk Assessment is next triggered for that entity — within a new journey, for example. At that point:
      • If the task is configured to calculate risk for draft products ('Only Assess Products Created/Updated Within Journey' is enabled), the system will only calculate product risk for those with a status of 'Onboarding' or 'In Review', it will exclude any with a status of 'Offboarding' (any previously stored product risk score/rating on that product will remain unchanged).
      • If the task is configured to aggregate Product Risk to the Entity ('Save to Entity' is enabled) the system will exclude the stored risk scores/ratings of products with 'Offboarding' and 'Offboarded' status from that aggregate.
  • Validating ahead of the target date:

    • The change is live in non-live tenants from August 26th, 2026. We encourage you to use the period before September 29th to run your existing journey schemes in a non-live tenant and compare the product risk and entity risk outputs against your current production values, so that any change in risk position is understood and agreed with your risk and compliance stakeholders in advance. If your tenants use any mitigating configuration to adapt for the past inclusion of 'Offboarding' and 'Offboarded' products, you can unwind that configuration as part of your testing.
  • No action is required to receive this change:

    • It will apply automatically to all Product domain enabled tenants after 29th September — there is no opt-in, no configuration change, and no journey scheme update needed. We do not anticipate that any client will need to opt out, as the revised behaviour leads to a more accurate reflection of product risk that has been highly requested by our customers.
  • Enabling earlier:

    • If you have completed your review and would like the change applied to your live tenant before September 29th, 2026, please contact your Fenergo Client Partner and we will arrange it.

Why Are We Making This Change?​

Product risk exists to describe the risk an institution actually carries through the products a client holds. Until now, the Product Risk Assessment task made no distinction based on where a product sat in its lifecycle — a product a client had asked to close was assessed on exactly the same footing as one they had just opened.

Where an offboarding product carried a high risk rating, it could still affect an entity's aggregate product risk, and therefore its entity risk, even though the institution's exposure to that product was winding down. Reviewers may have needed to override risk ratings to ensure the appropriate level of due diligence was applied.

Excluding offboarding and offboarded products produces a product risk outcome that reflects the client's live relationship. This makes risk outcomes easier to evidence to reviewers, auditors and regulators, and removes a recurring source of unnecessary manual explanation for analysts.

Need Help or Have Questions?​

If you have any questions or require support with this transition, please contact your Fenergo Client Partner, who will be happy to assist you.

Notice of Deprecation: Legacy REST Integration Surfaces

Change Target Date: 31st August 2026​

Fenergo will be deprecating a set of legacy REST integration surfaces across TM Alerts and Financial Crime Reporting. All deprecated endpoints have direct GraphQL equivalents available via the Supergraph and the FCR Supergraph subgraph.

What Does This Mean for You as a Fenergo User?​

Once these changes are in effect, the following REST endpoints and standalone GraphQL APIs will no longer be available:

TM Alerts​

  • Standalone TM Alerts GraphQL API (/tmalerts/graphql) — superseded by the Supergraph.
  • Alert assessments — assess transactions, complete assessment.
  • Comments & activity trail — comments and file attachments.
  • File upload — create alert file upload URL.
  • Alert reads — get alert by ID, journey, or entity.
  • Nested reads — transactions, comments, and alerts-by-transaction.

Financial Crime Reporting​

  • Standalone FCR GraphQL API — superseded by the FCR Supergraph subgraph.

Why Are We Making This Change?​

These legacy REST surfaces have been superseded by GraphQL equivalents that offer greater flexibility, consistency, and performance. Consolidating integrations onto the Supergraph reduces surface area, simplifies maintenance, and ensures all clients benefit from a single, unified API layer.

What Action Do You Need to Take?​

If your integration relies on any of the endpoints listed above, you should migrate to the equivalent GraphQL operations via the Supergraph before the change target date. Your Fenergo Client Partner can provide guidance on the available GraphQL alternatives.

Need Help or Have Questions?​

If you have any questions or require support with this transition, please contact your Fenergo Client Partner, who will be happy to assist you.

Notice of Deprecation: TM Removal of Alert Metadata Configuration

Change Target Date: May 31st, 2026

Fenergo will be removing the Alert Metadata Configuration section within the Reference Data domain. Due to low usage, this section is no longer required and will be retired at the end of May 2026.

What Does This Mean for You as a Fenergo User?​

Once this change is in effect, the Alert Metadata Configuration section will no longer be available within the Reference Data domain.

Why Are We Making This Change?​

This section has seen low usage across the platform and is no longer considered necessary. Removing it allows Fenergo to streamline the Reference Data domain and reduce unnecessary complexity for users.

Need Help or Have Questions?​

If you have any questions or require support with this transition, please contact your Fenergo Client Partner, who will be happy to assist you.

Notice of Deprecation: TM Removal of Alerted Transactions

Change Target Date: May 31st, 2026

Fenergo will be removing the Alerted Transaction tab in the Alerts Dashboard. An extension of the information available here will be available in Advanced reporting so this tab is no longer useful. Furthermore, removing this information from the Alerts page will enhance the performance of the page. All transactions are available from the Entity profile transaction tab.

What Does This Mean for You as a Fenergo User?​

Once this change is in effect, the Alerted Transactions tab will no longer be available in the Alerts dashboard. Alerted transaction information is available in Advanced Reporting.

Why Are We Making This Change?​

There are multiple reasons for this change, firstly the need for this tab has been mitigated by adding Alerted Transactions to Advanced Reporting, secondly removing this information will have a positive impact on the performance of the Alert Dashboard.

Need Help or Have Questions?​

If you have any questions or require support with this transition, please contact your Fenergo Client Partner, who will be happy to assist you.

Notice of Change: Limiting In-Progress Journeys Per Entity

Change Notice Date: April 27th, 2026

Planned Target Date: June 4th, 2026

Fenergo will be introducing limits on the number of journeys that can be in progress simultaneously for a single entity. This change is designed to protect platform performance and prevent unintended automation from generating excessive workload.

What Does This Mean for You as a Fenergo User?​

Once this change is in effect, the following limits will apply per entity:

  • A maximum of 1,000 total in-progress journeys per entity.
  • A maximum of 500 in-progress journeys of the same journey type per entity.

If either limit is reached, the system will reject new journey creation requests with a 400 Bad Request API response. A validation error will be returned within Fenergo indicating whether the total limit or the per-journey-type limit has been exceeded.

If you encounter one of these errors, review and resolve existing in-progress journeys for the affected entity before attempting to create new ones.

Why Are We Making This Change?​

This change has been introduced to maintain system stability and mitigate the risk of uncontrolled journey creation caused by configuration or process issues. By capping the number of in-progress journeys per entity, Fenergo can ensure consistent platform performance across all clients and reduce the impact of accidental or automated over-creation of journeys.

Need Help or Have Questions?​

If you have any questions or require support with this transition, please contact your Fenergo Client Partner, who will be happy to assist you.

Notice of Change: Rollback Documents as a Data Source in Policy

Change Notice Date: April 2nd, 2026

The recently released Document Metadata Policy Trigger Condition feature has been removed from the platform. Following release, we identified an issue that affects environments with high volumes of documents, and in order to protect the platform stability for all clients we have made the decision to remove this feature at this time while we work on a more robust solution. If you have already begun configuring this feature, please reach out to your Fenergo representative who will be happy to advise on alternative approaches in the interim. We apologise for any disruption this may cause.

Notice of Change: Significance Task Types New Permission

Change Notice Date: March 19th, 2026

Change Target Date: End of April, 2026

Fenergo will be introducing an update to the permissions required to interact with and complete the Significance Engine Results and KYRA:Signal Results Task Types. This communication serves as notice before the change is rolled out to production environments.

The updated implementation will introduce a new dedicated permission, Significance Task Edit, which will be required to override Significance outcomes and complete the task.

What Does This Mean for You as a Fenergo User?​

Once this change is enabled, users will require the Significance Task Edit permission in order to interact with and complete the Significance tasks.

For any tenants already using Significance Task Types, users who currently have Significance Rule Access will continue to be able to view, edit, and complete the task. This is to ensure continuity of access during the transition period.

Why Are We Making This Change?​

Following the recent separation of configuration and operational permissions, we identified the need to introduce a dedicated task permission, allowing configurators to better control which users can overwrite outcomes within the task, without granting access to underlying configuration.

This approach mirrors what we already do in other areas of the application and maintains the separation between configurational and operational users while providing greater flexibility and control over task interaction.

Need Help or Have Questions?​

If you have any questions or require support with this transition, please contact your Fenergo Client Partner, who will be happy to assist you.