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.

Previously, unsubscribing related parties (RPs) from Ongoing Screening (OGS) during an offboarding journey was entirely manual. Users had to individually review and unsubscribe each RP, which at volumes of thousands or tens of thousands of offboardings, represented a significant burden of repetitive analyst work.

This release introduces automation support for the OGS: Unsubscribe from Ongoing Screening task, allowing the system to intelligently handle unsubscription for eligible entities and RPs without user intervention.

Advanced Reporting now exposes the association subtype for related party records through a new subtype column on the relatedparties dataset. This makes it possible to report on the specific business relationship behind Product and Agency associations, which previously could not be distinguished from one another.

Until now, the relatedparties dataset projected only the association type. For standard related party associations this type is the business relationship (for example Director or Shareholder). For Product and Agency associations, however, type is a fixed value (product or agencyRequest) used to set those associations apart, and the meaningful relationship was not available in reporting.

The Screening Results table now renders the LexisNexis source as a clickable hyperlink, allowing investigators to navigate directly to the corresponding alert in the LexisNexis (Bridger) portal without leaving Fen-X or manually copying the Alert ID.

This release introduces the Policy Agent, a new Fenergo Digital Agent that automates the analysis of policy documents. Analysts can upload a PDF policy document, review AI-extracted requirements classified by entity type, field type, and confidence level, and compare them against existing Fenergo Policy configuration — all within a single, auditable workflow. Results from the Extracted Policy Requirements and Policy Comparison screens can be exported to Excel for offline review or internal sign-off.

Note: The Policy Agent can only be enabled on one tenant at a time. Contact your Fenergo representative to have it enabled on your tenant.

User Guide Reference: Policy Agent User Guide

A new configuration toggle — Default To Existing Value — has been added to the Document Data Extraction task in Journey Builder. When enabled, the current system value is pre-selected in the analyst review panel instead of the extracted value from the uploaded document. This gives configurators control over the analyst's starting position when reviewing extracted data, helping to prevent existing entity data from being unintentionally overwritten. If a field has no current system value, the extracted value is pre-selected as a fallback. The toggle is disabled by default and is configured at the task level in Journey Builder.