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 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 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 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 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.

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 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.

This enhancement enables Ongoing Screening (OGS) to be configured per Configuration Set in LexisNexis, with two operational modes available via the new OGS Mode toggle:

• Default — every OGS-enrolled entity is screened against every OGS-enabled Configuration Set, with hits segregated into a separate journey per set (category-based segregation, single shared Accept List).
• Per Configuration Set — entities are subscribed to specific Configuration Set(s) and screened only by those (jurisdiction-based segregation, dedicated Accept List per set).

Each Configuration Set can be mapped to its own Journey Schema with its own SLAs, team assignment, and routing.

The Entity Profile Audit Drawer now includes an "RP Associations" tab, showing the audit trail for standard Entity-to-Entity association records (Related Parties) — including additions, removals, and relationship type changes. This enhancement doesn't require any actions to enable.

ETL now supports the bulk deletion of existing association records using the new Delete Associations data type. Combined with the existing Associations data type, this also enables a net update to an association's relationship type in a single ETL project — deleting the old relationship and creating the new one in the same load.