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.

The release introduces a new Map Lookups step in ETL, allowing users to automatically transform their data source lookup values into their corresponding lookup values defined in Fenergo. This ensures that imported attribute, such as Country, Industry, or Risk Ratings ,are consistently mapped to Fenergo’s configured lookup lists, enhancing data quality and preventing validation errors in downstream processes.

Note: this beta release available to customers by request

Managing configuration across multiple tenants can be challenging when relying on manual, ad-hoc imports. Configuration Release Hub introduces a modern, centralised mechanism for creating, versioning and deploying configuration, enabling clients to maintain configuration in a single source tenant (typically Dev) and promote versioned snapshots to higher environments through controlled, repeatable processes.

Using Configuration Bundles, customers can group related configuration changes into publishable versions that are safely stored and imported via API. This ensures consistent deployment across UAT, Pre-Prod and Prod, supports stronger governance, and aligns configuration management with standard SDLC and CI/CD practices.
This enables predictable, auditable configuration promotion and reduces risk by eliminating uncontrolled tenant-to-tenant changes.

Fenergo’s Screening Agent is now available for Ongoing Screening, in addition to On Demand Screening.

A new address type: “Business” is now supported for Individual entities during LexisNexis screening, allowing clients to screen Sole Traders using either their Residential or Business addresses.