Skip to main content

Document Management – Configurable Metadata Columns in Document Requirements Grid

This enhancement introduces the ability to configure and display custom metadata fields as additional columns within the Linked Documents and Matching Documents grids. This provides greater visibility of document-level data directly in the UI, reducing the need for users to open individual document records. Users can configure up to two text-based metadata fields (excluding rich text) via the Document Metadata Configuration screen. Once enabled, the selected fields will appear in the relevant document grids, with values truncated for readability and full text available via tooltip on hover. This enhancement applies to document requirements using the Document V2 framework.

New Secondary Identifier for LexisNexis and custom screening providers

A new secondary identifier field is now available for LexisNexis and any custom screening provider: Passport Number. This must be enabled in the screening provider's Secondary Identifier Configuration in order to use. For LexisNexis Ongoing Screening (OGS), the Batch Formats configured in Bridger must be updated to include Passport Number for it to be sent and used in OGS. The updated Batch Format files can be downloaded from the User Guide.

Mandatory Comments on Document Waiving

A new configuration setting has been added to allow administrators to require users to enter a comment when waiving a document. This setting can be enabled from the Document Requirement Metadata configuration screen. When turned on, users will not be able to complete a waiver without providing a comment. The configuration applies to all waiver tasks going forward and supports improved compliance tracking.

User Guide Reference: Document Management -> Mandatory Comments on Document Waiving

Journey Cancellation Comment Configuration

A new configuration option has been added to allow tenant-level control over whether users are required to provide comments when cancelling a journey. A user with the journey edit permissions can now enable or disable the "Require comments when cancelling a journey" setting from the journey configuration panel. When enabled, users must enter a comment before cancelling a journey. The setting is applied automatically across all in-flight journeys, with no need for manual saving.

User Guide Reference: Configuring Journeys -> Mandatory Comment on Journey Cancellation

Enabling Parallel Risk tasks Within Journey Builder

This feature removes the validation that prevented users from adding a Risk Assessment task (of any type) to a process within a stage that was configured with process completion order set to 'In any order'. This allows you to complete jurisdictional KYC requirements within the same stage, improving overall onboarding times by better supporting parallel work effort.

Document Assignment

The new Document Assignment task enables more flexible and controlled document sharing across entities during the onboarding journey. It replaces the limitations of Shared Templates and Entity Groups with a more dynamic, user-driven approach.

Bank Account Risk Assessment

This feature will introduce a new Bank Account Risk Assessment task to Fenergo SaaS that will calculate bank account risk for each bank account that has been added or edited within a journey, along with the aggregated risk of all bank accounts associated with an entity.

Related Party Data & Documents Task

As part of the Related Party Adapted Experience, a new Related Party Data & Documents task is now available. This task is designed to work with the existing Related Parties task, and will separate the additional data and document requirement capture that is needed for particular entities in the hierarchy. Related Party Scoping Rules have been introduced to control those entities in scope within the new task.

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

Hierarchy Extraction for IDP

This enhancement to Intelligent Document Processing allows for the extraction of related parties from uploaded documents. IDP now has the capability to build out rich, complex related party hierarchies within the existing IDP flow.