Product Updates

Clodagh from Fenergo gives a demo of the Bank Account Risk Assessment task, which calculates 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.

Karl from Fenergo demonstrates how to use ETL to create and update investment and bank account records while establishing relationships between investment accounts, bank accounts, funds, and investors.

Orbis users can now map a 'directPercentageLabel' field which will capture non-numerical Direct Percentage values, for display in the Related Parties Task when configured. User Guide Reference: External Data Functional Configuration Guide: Mapping Tool Operation.

Georgina discusses the new Related Party Data & Documents task - splitting hierarchy capture from ID&V data/doc collection, with scoping rules and mandatory enforcement.

This enhancement introduces the ability to bulk upload risk configuration items using a CSV file. It reduces the manual effort of uploading items one by one by allowing configurators to prepare a CSV file of values and their associated risk levels, then uploading them all at once. User Guide Reference: Working with Risk Functionality > Bulk Creation of Risk Configuration Items

Roscha from Fenergo provides an overview of the recent Trader Portal Enhancements. She demonstrates the enforcement of Product Capture, Maintenance Requests, and touches on the consolidation of configuration between the standard and trader portal.

Roscha from Fenergo demonstrates how to configure the enhanced styling and formatting that Email Template V2 introduces. Additionally, this video covers the configuration of rich text editor and how it displays in the Portal.

The Alias Screening feature allows you to screen entities using multiple names, such as aliases (AKA) or former names (FKA), within a single inquiry. This enables a multi-name screening capability that streamlines compliance operations and improves traceability and transparency. Alias Screening is available for both WCO and custom screening providers. User Guide Reference: Alias Screening

The new Related Party Launchpad v2 allows clients to configure scoping rules for both new and existing related parties, enabling due diligence on verified and net new entities while leveraging existing Fenergo policy logic. It also supports multiple Related Party Launchpad tasks within a journey, allowing more than one set of related party journeys to be triggered. User Guide Reference: Journey Management Related Party Launchpad v2 Scoping Rules

Roscha from Fenergo demonstrates how to use and configure Portals Outreach Requests Dashboard. Additionally, this video covers the data completion checks on related parties functionality.

This feature introduces screening tables to Advanced Reporting, enabling users to query, analyse, and report on PEP, Sanctions, Adverse Media, and Enforcement outcomes. It provides end-to-end visibility across screening processes, enhancing risk and compliance reporting. User Guide Reference: Advanced Reporting

Emma from Fenergo demonstrates the new Alias Screening feature that allows users to screen entities using multiple names, such as aliases (AKA) or former names (FKA), within a single inquiry. Alias Screening is available for both WCO and custom screening providers.

Emma from Fenergo demonstrates the integration of screening tables into Advanced Reporting, which provides users with the ability to query, analyse, and report on screening-related data.

Added validations in the Screening Receptor when a batch is created and results are sent back from the provider to check: That all the entities being returned for the batch search results to the receptor belong to the batch. That the match.providerId returned for the batch search results to the receptor exists in the list of the batch providers. Also, added fields to the Screening Command API in order to support implementation of Alias Screening. For all the endpoints, entityAliases can be sent as null or an empty list if not using Alias Screening. Affected Endpoints​ POST /api/batch Added entityAliases to CreateBatchEntityDto (within CreateBatchDto). POST /api/entity Added entityAliases to CreateEntityDto. Added entityAliases to EntityCreatedDto (response). PUT /api/entity/{entityId} Added entityAliases to UpdateEntityDto. POST /screeningreceptor/api/receptor Validations explained above

Salesforce now supports the Unsubscribe from Ongoing Screening task, allowing users to remove entities currently enrolled in ongoing screening. User Guide Reference: Salesforce User Guide > Ongoing Screening Unsubscribe Task

Portal administrators can now configure a custom font family to be applied globally across the Portal UI. This enhancement allows organisations to align the Portal’s look and feel with their brand identity by uploading font files for multiple styles and weights. User Guide Reference: Configuring the Fenergo Portal > Fonts

This feature introduces Mandatory Search Parameters which ensure that entity searches in the Salesforce Plugin cannot be executed unless all mandatory fields are completed. This aligns with the behaviour in Fenergo's “New Request” screen. User Guide Reference: Salesforce User Guide > Mandatory Search Parameters

Portal administrators can now enforce access restrictions on the Search Dashboard, ensuring that Portal users only see and interact with entities they are explicitly permitted to access. If no filters are configured, users can access all entities retrieved from Fenergo. When filters are applied, users are strictly limited to entities matching their assigned filter values. Attempted access to restricted entities (e.g., via saved URLs) is blocked, and users are redirected to the Search Dashboard with an explanatory message. User Guide Reference: Configuring the Fenergo Portal > Configuring Portal Dashboards > Search Dashboard

Affected Endpoints​ Added optional properties to role configuration POST /api/portal-roles/createrole - EntityPageConfig - EnableAccessLayers (optional) PUT /api/portal-roles/updateroledetails - EntityPageConfig - EnableAccessLayers (optional) GET /api/portal-roles/portalRole/{id} - EntityPageConfig - EnableAccessLayers (optional) GET /api/portal-roles/portalRoles - EntityPageConfig - EnableAccessLayers (optional) Added optional properties to user endpoints GET /api/portal-users/getPortalUserDetails - AccessLayersConfig (optional) GET /api/portal-users/getPortalUserDetailsWithoutLinkedEntities - AccessLayersConfig (optional) PUT /api/portal-users/updateUserDetails - AccessLayersConfig (optional)

This enhancement introduces the ability to assign static access layers during data migration by utilising the BusinessAccessLayer and GeographicAccessLayer fields. These fields can now be included in the data source and mapped in the system fields section, allowing for manual assignment of access layers across supported data types. Static access layers are not supported for Product and Associations data types. User Guide Reference: ETL Extract Transform Load -> ETL - UI

Allow users to upload a single document against multiple Related Parties in the Related Party Data & Documents task. After selecting the relevant entities, users upload the document via a modal, complete required metadata, and track progress through a real-time upload indicator. Once complete, the document is linked to any matching requirements, and the grid updates automatically to reflect satisfied requirements and updated statuses. User Guide Reference: Using Related Party Management User Guide > Related Party Adapted Experience

As part of the Docs V2 Task in Salesforce, Acceptable Document Types and Document Descriptions are now supported. This will allow Admin to input acceptable document type descriptions, allowing Salesforce users like Relationship Managers to know what documents they need to prepare. User Guide Reference: Salesforce User Guide > Acceptable Document Descriptions

This enhancement introduces ETL support for the creation and management of investment and bank account data, enabling seamless migration into Fenergo. Users can now create and update account records while establishing relationships between investment accounts, bank accounts, funds, and investors. User Guide Reference: ETL Extract Transform Load -> ETL Investment and Bank Accounts

Alert Groups​ Alert groups can be created from the All Alerts/My Alerts dashboard and viewed on the new Groups tab. Bulk Assignment​ Alerts can be assigned in bulk. Bulk Assessment​ Alerts which are assigned to a user can be assessed in bulk. Entity Access layers for Alerts​ Alerts access is controlled based on entities access layers.

This enhancement introduces a configuration option to prevent the persistence of expired documents within document-related tasks. Once enabled, out-of-date documents will be flagged with an 'Expired' chip, giving greater visibility to document status and helping users easily identify expired documentation. User Guide Reference: Document Management ->Document Management V2 -> Preventing persistence of Expired Documents Document Management ->Document Management V2 -> Preventing persistence of Expired Documents