When it is imperative that a user capture at least one bank account in the bank account task, a configuration toggle can now be enabled in Bank Accounts task properties to enforce bank account creation. If the user attempts to complete the bank account task and no bank accounts have been captured against the entity, they will be presented with a validation error and cannot complete the task until at least one bank account has been captured.

This release introduces a field to change the frequency of the ISDA Amend Scheduler, enabling greater configurability in the automated monitoring of ISDA Amend Protocol updates.

The Alert Confidence score from the GRID/RDC provider is now displayed within the Profile tab of a Grid screening result in Fen-X.

When the Default Investment Account Name toggle is enabled, Investment Account names will now automatically regenerate each time the Investment Account task is saved or completed, ensuring names stay consistent with the latest Investor, Fund, and Fund Product data. A new Update Investment Account Names During Verification toggle is also available in the Verification Task configuration, allowing names to be refreshed across all draft Investment Accounts during the verification process.

To allow for STP scenarios where clients wish to validate the Related Party Data & Document compliance and not make any changes to the hierarchy, an update has been made to Journey Builder validation to allow the configuration of the Related Party Data & Documents task without the Related Parties or Hierarchy Capture task in these STP journeys. Existing validation will apply where the task is configured alongside the Related Parties or Hierarchy Capture task in a journey.

User Guide Reference: Related Party Management->Related Party Adapted Experience

A small enhancement has been introduced to Audit so that the when a value is verified in a journey, the event now includes the Journey Id. Please note this is on a go forward basis.

ETL reconciliation reports now include document-level detail on every row, so any row can be traced back to the specific document it relates to. Each row records the Document Model ID, the unique identifier of the document in Fenergo, alongside the Document Path for uploaded documents or the URL for virtual documents.

The additional columns apply to Entity Documents, Product Documents, Entity Virtual Documents, and Product Virtual Documents reconciliation reports, removing the need to cross-reference the original migration bundle when investigating failed loads or post-migration queries.

ETL now automatically triggers journeys for migrated Individual and Company entities once a data load completes, allowing migrated entities to resume in-progress activities such as Risk Assessment, Screening, and Due Diligence without manual intervention.

Journey Launch is configured per entity type, with an optional filter to control which entities are in scope. A Journey Launch report is generated for each entity type, detailing the outcome for every evaluated entity to support reconciliation.

The Entity Profile Page Journeys tab now includes a Completed On column in the Journeys grid, displaying the date a journey was completed in DD MMM YYYY format. The column supports sorting, and a Date Completed field is displayed in the task status hover-over when a task is in a completed state. No additional permission configuration is required.

SLA calculations now support working day configuration. Previously, SLA deadlines were calculated using all calendar days, including weekends and non-working days. A new SLA Configuration screen has been added under Management → Journey, allowing configurators to select which days of the week are considered working days and set a Reference Timezone. When configured, SLA timers will only count business days — pausing on non-working days and resuming on the next available working day. For example, a 2-day SLA triggered on a Friday with Monday-to-Friday working days will result in a Tuesday deadline. The system default remains all seven days selected, preserving existing behaviour until a change is made. Two new permissions have been introduced: SLA Working Days Access (view) and SLA Working Days Edit (modify and save). No changes have been made to the existing journey, stage, or task-level SLA configuration.

User Guide Reference: Configuring Working Days for SLAs