ETL Entity Documents enables the bulk migration of regulatory and KYC documents into Fenergo, allowing documents to be securely uploaded, validated, virus-scanned, and linked to the correct legal entity with the appropriate metadata and access controls.

The Screening Results Key Details tab has been enhanced to support multiple identity values and fully structured identification details returned by LexisNexis. Users can now view all Dates of Birth, Nationalities, Citizenships, Places of Birth, and Identification attributes (including issuance country, issue date, and expiry date) for Individuals and Companies. This enhancement removes the need to cross-check screening hits directly in LexisNexis, as all available identity information is now clearly presented within Fenergo.

Users can now configure Ongoing Monitoring for D&B for both the Client entity and its Related Parties using the D&B CMPBOL package. DunsId can now be used as a search parameter, and in the automated deduplication process of Related Parties. Data mapping files also added to the user guide.

The Significance Agent Results task now supports configurable autocompletion, allowing tasks to automatically complete when all returned results meet defined significance criteria. This enables greater automation and allows Significance Agent outputs to drive downstream journey logic via the Significance Engine.

Autocompletion is optional and controlled through Central Agent Configuration, ensuring tasks can remain manual where review is required.

Agency Bulk Upload introduces a new Agency ETL task within the Agency Request journey, allowing customers to onboard large volumes of Underlying Principals, Managed Relationships and Products for an Investment Manager using CSV files instead of manual UI entry.

By embedding our Extract Transform Load (ETL) capabilities directly into Agency Requests, customers can process high-volume agency onboarding while still using the standard Agency data model, connected journeys and policy-driven validation.

Accounts can now be surfaced in the Conflict Resolution task. This will give users the ability to resolve conflicts on both investment accounts and bank accounts.

The Review & Approvals Task enables users to review, comment on, and approve entity, product, related party, document and risk data directly within Fenergo.

It replaces email-based reviews with an auditable, collaborative task that supports threaded comments, configurable approval options, and data comparison views.

This release introduces enhanced support for mandatory and non-mandatory Data Groups within ETL, enabling users to clearly understand which datagroups require input during migration. A new Mandatory column is now displayed in the Datagroups grid, indicating whether the data requirements the data group is linked to is mandatory or not for the selected entity type.

This improvement ensures that users are only required to provide data where necessary, streamlining the migration process and reducing confusion when optional datagroups appear without data. Mandatory datagroups must be fulfilled before progressing, while non-mandatory datagroups no longer block workflow completion.

Product Access Layers (PALs) and Product Field Access Layers (PFALs) introduce a dedicated security model for product data. These controls allow clients to restrict which products a user can see, and which product fields they can view, based on Business Related and Geographic access layer entitlements.

This ensures product visibility is governed independently of the owning Entity, providing stronger information barriers and more precise access control across all product-related features.

Multi-Publish now supports the Related Party domain. When selected in the task definition, the Multi-Publish task will publish all Related Parties connected to the entity at the point of execution. Partial publishing is not supported. This enables updated Related Party information to be made available earlier in the journey, while the full Related Party verification process can still run later in the workflow.