The Provider Priorities tab on the External Data Configuration screen now displays only the options relevant to each organisation's setup. Organisations using KYRA:Source continue to have full access to the Rules configuration, while those that do not will see only the default provider setting.
When data is imported via an external provider through KYRA:Source, the audit trail now records the name of that provider — for example, "Orbis" — in the Source field, replacing the previous generic label. Auditors and KYC analysts can accurately trace the origin of each imported data point to its source provider.
KYRA:Docs — Document Data Extraction V2 brings the review of extracted entity data, data groups, and related parties into a single, unified task. Reviewers can now compare extracted information against the current entity record, understand the outcome assigned by KYRA:Docs, and record an explicit resolution before any changes are applied. This release replaces the legacy extraction experience with a more controlled, transparent, and auditable review process — supporting both standard and Maker-Checker journeys.
Configurators can now include product types in a Shared Data Template. When a Group Onboarding journey runs, verified products of those types on the Group entity are automatically shared to each in-scope child entity — removing the need to create products separately for every member of a joint account or entity group.
Two new Policy Engine sources are now available: Investment Account Fund and Investment Account Fund Share Class. Configurators can use these sources to trigger data and document requirements and conditional values directly on the investment account based on the linked fund and linked share class.
Users with the Unassign Journey or Task Owner permission can now clear a Journey Owner or Task Owner assignment without needing to immediately assign a replacement, returning the owner field to an unassigned state while preserving the team assignment.
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.
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.
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 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.