To support scalability, the behaviour of Related Party Access Layers Inheritance has been updated to use the overall hierarchy association, rather than the journey context. This means that entities will inherit from their closest 'Client' parent entity, which is not necessarily the root entity in journey. From March 2026, any tenant that enables this functionality will have this new behaviour applied. A migration will need to be performed for any clients already using the existing functionality and permission will be required before applying. Please reach out to your representative to begin this process.

ETL Post Processing enables automatic recalculation of Dynamic Access Layers (DAL) and Jurisdiction assignments for entities created or updated during ETL migrations, ensuring migrated data aligns with standard platform governance and policy rules.

This capability can be enabled per ETL project using Post Load Actions. Once ETL Load completes, the recalculations run asynchronously and apply to all entities included in the migration.

• Dynamic Access Layers: Re-evaluates and applies rule-based access control for supported entity types.
• Jurisdictions: Recalculates jurisdiction applicability, adds newly applicable jurisdictions, and updates policy versions.

ETL Virtual Documents enables the bulk migration of both Entity and Product virtual documents into Fenergo, allowing document records to be created and linked without requiring a physical file upload. This supports structured document metadata ingestion, validation, and association to the correct legal entity or product with appropriate classification and access controls.

This feature introduces the ability to optimise the Related Party Data & Documents Task evaluation to not evaluate the full hierarchy when pre-processing via the Related Party Scoping Rule. The rule must follow specific configuration restrictions in order to apply the logic and allow only direct associations to be evaluated and therefore reducing the pre-processing time.

Data Protection Regimes have been enhanced to support conditional retention durations. This allows for dynamic retention period calculation, such as having a longer retention period for the Norway Jurisdiction when the entity has a High Risk Rating. Where no conditional rules are configured (or none are matched), the regime’s default retention duration continues to apply.

Task reassignment notifications can be missed when users do not add a comment during reassignment. This release introduces a dedicated notification toggle so users can be notified when a task is reassigned to them, regardless of whether a comment is provided.

This release enables you to:

• Configure a new Journey notification toggle: Tasks are Assigned to Me
• Notify the newly assigned user when a task is reassigned to them via the UI, even when no comment is added
• Include system-generated context in the notification: Task reassigned from X to Y
• Include the reassignment comment in the notification only when a comment exists
• Record the reassignment event in:
  • Task Activity Log
  • Journey Activity timeline

This feature introduces the ability to delete bank accounts after they have been verified in a journey.

This feature introduces the ability to view investment accounts associated to bank accounts within the bank account task.

When an entity undergoes partial data deletion, the data for an offboarded jurisdiction is deleted, having reached the end of it's retention period. With this deletion, related products may also be selected to delete. When using Dynamic Access Layers, if the deleted data was an input to the Entity's Access Layers, they will now be re-evaluated based on the remaining data.

Feb 24, 2026

Leveraging the existing ETL feature we have developed a process for allowing you to create scheduled and in progress reviews for entities that you migrate into Fenergo, in order to persist the existing review schedules you have in your source system.