Product Updates

A set of Portal UX Improvements have been introduced to enhance clarity, guidance, and visual feedback for end users. These enhancements make the Portal easier to navigate and more intuitive, while maintaining alignment with client branding across visual modes. Enhancements include: Task-Level Guidance: New inline guidance messages now display at the top of each task screen to help users understand what information is required. Configurators can add this through the Task Description field in Journey Builder, linking to predefined guidance text from Global Policy. This feature supports Data, Document, Related Party, Product, Review, and ID&V tasks in external journeys and stages only. High Contrast Mode Enhancements: High Contrast Mode now reuses the tenant’s configured brand colours (Primary, Error, Warning, Info, Success, and Hyperlink). Each colour automatically adjusts to achieve a minimum 4.5:1 contrast ratio, maintaining WCAG 2.1 compliance while keeping full brand alignment. Reopen Indicators: A new Reopen icon has been added to completed tasks, helping users easily identify where they can take further action. The icon is visible on hover and fully accessible using keyboard navigation (Tab, Enter, or Space). When activated, the task reopens in an editable state and updates the journey’s progress indicator accordingly. User Guide Reference: Configuring the Fenergo Portal > Configuring User Guidance in the Portal

This feature will allow clients to create alerts that are not necessarily transaction driven. Alerts can be created via API against an entity. These alerts can be assessed in alert tasks with supporting commentary and documentation.

The ‘Search Exclude Client Entities’ toggle allows configurators to filter out entities marked with the Client role from duplicate search results, ensuring only non-client entities can be linked where appropriate. User Guide Reference: Related Party Management Related Party Adaptive Experience

Added requirement for If-None-Match header in endpoint request, to ensure rejecting conflicting uploads under the same url. POST /api/transactions/batch/generate-upload-url

Added new property Thresholds to RiskFactorGroupRiskAssessmentViewModelDto. Affected Endpoints​ GET /riskquery/api/risk-model GET /riskquery/api/risk-model/{id} GET /riskquery/api/risk-model/{id}/version/{versionNumber} POST /riskcommand/api/risk-model POST /riskcommand/api/risk-model/{id} PUT /riskcommand/api/risk-model/{id}

The Portal now supports displaying multiple configured categories of information on the Entity Profile Page (V2). Depending on role configuration, users can view all relevant categories for each entity type (Company, Individual, or Other) in a clear, organised layout, instead of being restricted to a single category view. User Guide Reference: Configuring the Fenergo Portal > Display Multiple Categories

Access Layers on Accounts introduces the ability to capture access layers on investment accounts and bank accounts via manual capture or dynamic configuration. User Guide Reference: Investment Account Management Guide & Access Management Guide

Portal users can now be assigned up to five roles, allowing them to access multiple dashboards within the Portal. This update provides greater flexibility and visibility across different dashboards while maintaining secure, role-based permissions. User Guide Reference: Using the Fenergo Portal > Enabling Multiple Roles to be assigned

New "AutonomyLevel" property added to BatchMetadataDto. Depending on the value, the matches will be auto-resolved using an AI Agent when they come back from the provider, and auto-close the Screening Results task. Possible values: Manual (default), Semi-Autonomous, Fully Autonomous New "LastActionedBy" property added to MatchDto. This new proporty will be used to identify who actioned the resolution of the match, i.e Screning Agent, Screening Provider or manually by user (manuallyByUser@test.com). Affected Endpoints​ POST /api/batch (BatchMetadataDto) PUT /api/batch/id/matches (MatchDto) GET /api/v3/batch/{batchId}/entity/\{entityId\}/match (MatchDto)

Updated ThresholdDto and RiskFactorGroupThresholdDto models to include ThresholdColor property. Affected Endpoints​ GET /riskquery/api/threshold-model GET /riskquery/api/threshold-model/{id:guid} GET /riskquery/api/threshold-model/{id:guid}/version/{versionNumber:int} POST /riskcommand/api/threshold-model POST /riskcommand/api/threshold-model/{id:guid} PUT /riskcommand/api/threshold-model/{id:guid} GET /riskquery/api/risk-model GET /riskquery/api/risk-model/{id} GET /riskquery/api/risk-model/{id}/version/{versionNumber} POST /riskcommand/api/risk-model POST /riskcommand/api/risk-model/{id} PUT /riskcommand/api/risk-model/{id}

Roscha from Fenergo demonstrates how to bulk create risk configuration items via a .csv file.

Portal administrators can now configure how investment accounts are displayed to Portal users with the introduction of a new Filter Investment Accounts toggle. This control ensures that users either see all onboarded investment accounts or only those linked to funds they are explicitly entitled to, improving security and oversight across dashboards. User Guide Reference: Using the Fenergo Portal > Investment Accounts

Karl from Fenergo demonstrates how to use ETL to create and update product to entity associations.

Karl from Fenergo demonstrates how to use ETL to create and update product to entity associations using etl.

Fenergo’s Agentic Platform introduces a suite of Digital Agents that automate high-volume Client Lifecycle Management tasks. By embedding AI into the heart of the platform, our Agents bring automation, intelligence, and governance together-helping institutions reduce cycle times, improve accuracy, and focus their skilled staff on the cases that truly matter. There is huge potential in reducing manual workloads and creating value from your data by deploying our trusted Agents. Key Details​ Screening Agent: Automates screening hit resolution with configurable autonomy (manual, semi, full). Data Sourcing Agent: Retrieves and enriches data/documents from third-party providers. Autocompletion Agent: Autocompletes Data, Document, and Related Parties tasks, based on all necessary information already being captured. Significance Agent: Evaluates the significance of data changes using AI. Document Agent: Automates classification, extraction, and validation of client documents at scale. Central Agent Configuration: Provides a single hub to enable, configure, and manage autonomy levels and instances of each Agent across journeys. Implications​ Enables straight-through processing (STP) across multiple compliance workflows. Provides audit-ready transparency with explainable AI rationales for decisions. Reduces manual workload, freeing staff for higher-value analysis and client service. Improves compliance accuracy through consistent, policy-driven decisions. Delivers operational insights into automation performance, exceptions, and optimization opportunities. Client Adoption Guidelines​ Begin with semi-autonomous mode to maintain human oversight while measuring automation impact. Gradually increase autonomy as confidence grows and outcomes align with risk appetite. Review detailed user guides to understand configuration, autonomy modes, and dashboards. Validate configurations in lower environments before enabling in production. User Guide References​ Fenergo Digital Agents – Introduction Screening Agent User Guide Data Sourcing Agent User Guide Autocompletion Agent User Guide Significance Agent User Guide Document Agent User Guide

This enhancement is a production release of ETL support for creating and updating products and their entity associations. User Guide Reference: ETL Extract Transform Load -> ETL Products

Get trx batch validation results endpoint added to check results of batch validation step. GET /api/transactions/batch/validation-result/{{batch-id}} Added reject_on_invalid parameter to the generate-upload-url endpoint to allow rejecting entire batch if any transaction is invalid. POST /api/transactions/batch/generate-upload-url

The Data Deletion feature has been enhanced to ensure that entity records with outbound associations (i.e. where the entity is a Related Party to another entity) are not fully deleted. Instead, Client-specific data and documents are removed, while Related Party information is preserved. This ensures compliance with data protection regulations while maintaining critical relationship data. Key Details​ Related Party-mapped data, documents (and corresponding audit records) are retained, even if they are also mapped to Client requirements. Client-only data, documents, and audit records are deleted. Global policy is automatically reinstated and marked In Scope on the entity profile. Associations (inbound and outbound) are retained. Related Party Launchpad journeys are preserved while Client journeys are deleted. The Data Deletion Execution task applies the rules for Full Deletion, Partial Deletion, and Related Party Preservation. Implications​ Related Party records remain available for downstream processes, reporting, and integrations, even after Client-specific data is removed. Some Related Party data may still be deleted if it was only in scope due to another Client’s jurisdiction. All Global and explicitly in-scope Related Party requirements are preserved. No new configurations or feature flags are required. User Guide Reference​ Data Protection User Guide – Deleting Data

New endpoint to retrieve Data Deletion Processes with pagination. Returns data deletion processes sorted by tenant with pagination support. Data Protection Query API​ POST /dataprotectionquery/api/datadeletionprocess/paged

Added new Thresholds property to Risk Factor Groups in the risk model. Affected Endpoints​ GET /riskquery/api/risk-model GET /riskquery/api/risk-model/{id} GET /riskquery/api/risk-model/{id}/version/{versionNumber} POST /riskcommand/api/risk-model POST /riskcommand/api/risk-model/{id} PUT /riskcommand/api/risk-model/{id}

Removed HalleyEnableDraftsAndEntitiesV2Endpoints feature flag. Affected Endpoints​ POST /entitydataquery/api/v2/entity/get-entities-list POST /entitydataquery/api/v2/entity/search-entity-drafts

Updated response to include basic AccessLayers data for InaccessibleEntities for verified and draft entities. Affected Endpoints​ POST /entitydataquery/api/v2/entity/get-entities-list POST /entitydataquery/api/v2/entity/search-entity-drafts

This feature introduces the ability to enable ID&V capture within the Related Party Data & Documents task. User Guide Reference: Journey Management Related Party ID&V validation

This feature introduces the ability for Portal users to view investment account information directly from the Entity Profile Page (V2). This includes account data, documents, bank accounts, and related parties, all tailored based on Portal user role configuration. Users with the appropriate access will see a new Investment Accounts tab on the Entity Profile Page (V2), enabling quick and easy role-based access to detailed investment account details. User Guide Reference: Using the Fenergo Portal > Display Investment Accounts

Added investment account properties to role configuration: EntityPageConfig: EntityPageDisplayInvestmentAccounts (optional) InvestmentAccountPageConfig (mandatory if EntityPageDisplayInvestmentAccounts = true) InvestmentAccountsSections (optional) InvestmentAccountDataCategory (mandatory if InvestmentAccountsSections = "Data") InvestmentAccountDocumentType (mandatory if InvestmentAccountsSections = "Documents") Affected Endpoints​ POST /api/portal-roles/createrole PUT /api/portal-roles/updateroledetails GET /api/portal-roles/portalRole/{id} GET /api/portal-roles/portalRoles