Skip to main content

Product Lifecycle Date Tracking

Fenergo now allows for the capture of three system-calculated, read-only date fields in the Product domain — recording when each product was onboarded, last updated, and offboarded. These dates are tracked individually per product, ensuring accuracy across all lifecycle events. Each field would need to be added to a product policy to be visible and will need a specific datakey. See user guide for more information on configuration steps.

Advanced Reporting - Draft and Historical Data

Users can query product drafts (productdraftdata) and entity drafts (entitydraftdata) in Advanced Reporting. This will expose in-flight products and entities captured during journeys before verification occurs as well as historic drafts. Draft data for associations (relatedpartiesdraft) can now also be queried.

Account Data in Proposed Changes

Users reviewing a journey can now see Investment Account and Bank Account changes directly on a new Accounts tab in the Proposed Changes task. The Accounts tab shows a field-level comparison between the verified baseline and the current journey draft for each account, covering Investment Account data, Bank Account data, related parties and linked bank accounts on Investment Accounts. Current journey data or previously verified data can be accepted individually or in bulk.

Tags and References in Product Requirement Sets

Tags and References can now be added to Product Requirement Set requirements, bringing the Product domain in line with the capability already available in Policy. Tags are a flexible way to group requirements — labels you define to suit however you want to group them, applied across requirement types and jurisdictions so that every requirement matching one or more tags can be retrieved and reviewed together. References let you record the external legislation or internal documentation behind a requirement.

Custom Dashboards

Custom Dashboards lets users build their own configurable, interactive dashboards from their reporting data. Any saved query, including one generated with KYRA:Report, can be added as a data source for a widget arranged on a flexible grid. Depending on the widget used, different actions and formats are supported.

KYRA:Report

KYRA:Report is a new digital agent that lets users build and run reports using natural language. Rather than writing SQL, users describe the data they need in plain language and KYRA:Report generates the query, runs it, and returns the results ready to preview, refine, save, schedule or analyse. The agent is schema-aware, resolving the correct fields and parameters for your tenant, and retains conversation history so users can resume a session or reuse a query later.

ETL Screening — production release

ETL Screening is now available on all production tenants. Clients migrating from a legacy KYC system can use ETL to load historic screening data — including screening entities, match records, and adjudicated decisions — directly into the Fenergo Screening domain, enabling resolution reuse and NoMatch suppression from day one without requiring a full re-screen.

Screening V2: Enhanced Hit Resolution and Materiality Assessment

Screening V2 introduces two redesigned screening tasks across On Demand Screening (ODS) and Ongoing Screening (OGS). A new ODS: Screening Resolution & Materiality task combines hit resolution, hit classification, and materiality assessment — including, for the first time, materiality at Related Party (RP) level with one consistent outcome stored per RP. A new two-stage OGS: Screening Resolution & Client Selection task formalises the review of hits from periodic screening and drives the right downstream work per affected client.

References on Data Group Domain Policy

Administrators can now add, edit, and remove References, including type, description, and URL, for Data Group Domain Policy field-level entries. This brings the Data Group Domain Policy configuration in line with the References capability available across the wider Policy module.

KYRA:Screen: Screening Instructions

KYRA:Screen now includes a configurable Screening Instructions page, giving compliance and configuration teams direct control over how the agent evaluates and resolves screening hits — without any code changes required.

This enhancement doesn't require any actions to enable — System Default Instructions are applied automatically. We strongly recommend reviewing them and amending or supplementing them with custom instructions specific to your organisation before your next screening run.