The Journey Audit Drawer now includes tabs to show audit records for Entity and Product data changes made in this specific journey. Alongside the existing journey lifecycle events under the Journey tab, reviewers can see entity field-level draft changes made within the journey on a new Entity Data Changes tab, and product field-level draft changes on a Product Data Changes tab (available where the Product domain is enabled in the tenant). An Only show edited fields toggle keeps the view focused on changes that matter, hiding fields that have only their initial draft state.

Policy V2 Edit Mode introduces full configuration capabilities, allowing users to create, edit, review, and publish Policy V2 configurations using workspaces and version-controlled drafts.

In August last year, we replaced the table component used in many areas of Fenergo, including data groups. The new component came with an integrated "+" button to add new entries to the table. For Data groups, Customer feedback told us we no longer needed the original named add buttons (same function), so we have now removed them leaving the standard "+" icon inside the table as the single Add control. This change applies to all editable Data Group contexts and does not affect existing functionality, configuration, permissions, or read-only views.

The Data Protection Dashboard Matches tab now supports bulk offboarding, allowing users to action multiple orphan entities in a single step. The Actioned tab has also been updated with a direct link to each entity's initiated offboarding journey.

Clients using Automatic Offboarding with policies scoped by Related Products conditions will now see more consistent outcomes for their client entities during Ongoing Screening journeys. Policy evaluation calls made during Ongoing Screening journeys now include the Related Products data source, bringing them into line with all other journey types.

This means that policies referencing Related Products data are evaluated with the correct data available throughout the Ongoing Screening lifecycle, and automatic offboarding decisions accurately reflect whether scoping conditions are genuinely met.

Entity results in the global top-bar search now display all configured status chips that are indexable directly in the search dropdown. Previously, only the default "Client" chip was shown regardless of the statuses configured against an entity.

Where an entity has more than three configured roles, up to three render inline with a +N more affordance to surface the rest.

The Investment Account Risk Assessment task enables automatic risk calculation for each Investment Account linked to an Investor entity. Using a configurable risk model, risk configuration model, and threshold model, the task scores each in-scope account independently and persists the results to Investment Account-level datakeys — making per-account risk scores and ratings available for use in policy conditions, entity risk models, and journey routing rules.

Completed Investment Account Risk Assessment and Bank Account Risk Assessment tasks will now display a read-only Assessment Outcome banner showing the Aggregate Risk Category and Aggregate Risk Score.

When it is imperative that a user create at least one investment account in the Investment Account task, a configuration toggle can now be enabled in Investment Account task properties to enforce investment account creation. If the user attempts to complete the Investment Account task and no investment accounts have been created against the entity, they will be presented with a validation error and cannot complete the task until at least one investment account has been created.

Multi-Publish now supports Bank Account Data and Investment Account Data as additional publish domains. When either option is selected in the Publish to Entity task definition in Journey Builder, the full Account draft is pushed to the corresponding verified Account record on task execution. Partial publishing is not supported. All existing Multi-Publish constraints apply.

Clients migrating to Fenergo from a legacy KYC system arrive with years of historic screening activity, runs conducted against providers such as RDC, WorldCheck One and LexisNexis, with adjudicated match decisions and materiality assessments already captured in their source system. Without migrating this data, analysts would be forced to re-screen every entity from scratch and rebuild years of compliance decisions from Day 1.

ETL Screening addresses this by enabling clients to load their historic screening data directly into the Fenergo Screening domain.ETL Screening is currently available as a Beta feature while we conduct performance testing. It can be enabled on request, clients interested in this feature should contact their Fenergo representative.