User Guide Reference: ISDA Amend

At the checkpoint, users can go back and refresh any governed screening stage — not only the one that expired — or continue without rescreening. Going back is recorded to the audit trail like any other reopen; continuing without rescreening is reflected in the task's completion record instead. Verify Screening Period is available for both Screening V1 tasks and the ODS: Screening Resolution & Materiality (v2) task.

User Guide Reference: Screening->Verify Screening Period

User Guide Reference: External Authentication

The Screening Results table now includes a Select visible control: clicking the header checkbox selects exactly the hits on the current page. A selection bar displays the count selected and offers the option to expand the selection to the full result set across all pages via Select all [N] matches, or clear it. The ✓✓ icon invokes bulk resolution — opening the existing resolution drawer where the analyst captures Resolution, Reason, and Comments before resolving. Each resolved hit writes a complete audit record identical to individual resolution. The existing single-match resolution behaviour is unchanged.

This behaviour is available on both the V1 and V2 versions of the ODS: Screening Match Resolution and OGS: Screening Match Resolution tasks.

User Guide Reference: Using ODS: Screening Resolution & Materiality — Bulk selection

The EVA integration follows the same operational pattern as other supported providers such as Orbis and Kompany. EVA Curated provides commercial registry and ownership data, including UBO calculations and director information, while EVA Register surfaces registry-filed data directly from national company registers. Both sources can be used together in multi-provider configurations.

User Guide Reference: Using External Data Sources — Moody's EVA Operation

Configuration Guide Reference: Configuring External Data Sources — Configuring Moody's EVA

Where an entity is screened On Demand under more than one Configuration Set, Ongoing Screening results are now processed and routed separately for each set, rather than a single Journey Schema handling every alert.

User Guide Reference: Configuring WCO -> Enabling a Configuration Set for Ongoing Screening

The 'Related Entity' tile displays the name of the individual or legal entity the Investment Account was captured against. By clicking the name in the tile, the user will be navigated to their Entity Profile Page.

User Guide Reference: Related Entity Tile

This release enables you to:

• De-select Managed Relationship in the Agency ETL task's Data Types, so users no longer upload, map or validate a Managed Relationship file. Existing Managed Relationships are reused, and new draft ones are created where none exist.
• Use the new Autoname MRs toggle in the Agency ETL task's Task Content settings, enabled by default, to name new Managed Relationships "MR - [Investment Manager Legal Entity Name] - [Underlying Principal Legal Entity Name]" where no name is supplied.

A supplied legalEntityName is never overwritten, and generated names are limited to 200 characters, with the Underlying Principal Legal Entity Name cropped where necessary.

User and Configuration Guide Reference:

• Agency Bulk Upload

This release enables you to:

• Use the new Autoname New MRs setting on the project's Project Details page, enabled by default for new ETL Agency Migration projects.
• Have names generated for Managed Relationships created automatically during the Underlying Principal Load, and for new Managed Relationship records supplied without a legalEntityName.
• Keep full control of naming — a supplied legalEntityName is never overwritten, existing Managed Relationships are not renamed, and the setting can be turned off until Load starts.

Generated names are limited to 200 characters, with the Underlying Principal Legal Entity Name cropped where necessary.

User Guide Reference: ETL Extract Transform Load -> ETL Agency Migration

This release enables you to:

• Enable Journey Launch separately on the Investment Manager and Underlying Principal data types, from a new Launch Journeys tab.
• Select the Journey Type to launch, and optionally add filter conditions to control which records are in scope.
• Track each record's outcome — Launched, Failed, Skipped or Unprocessed — on the Launch Journeys tab, and reconcile outcomes using the Journey Launch report for each data type.

Journey Launch works as it does in standard ETL, respecting Journey Schema scoping and Journey Launch Controls. It is not available for Managed Relationships, Managed Products or Agency Associations.

User Guide Reference: ETL Extract Transform Load -> ETL Agency Migration

Administrators can now update the email address of a user who signs in via Single Sign-On (SSO) directly from the User Details page, keeping Fenergo in sync whenever a user's email changes on their organisation's side. The change is provisional until the user signs in again via SSO with the new address, which confirms it automatically; a pending change can also be cancelled before that happens, reverting the user back to their original email.

User Guide Reference:

• Change SSO User Email
• Cancel Email Change

When Risk Details is enabled on a Review & Approvals V2 Profile, a Risk Details Configuration section is now available within the profile. Configurators can select which risk sub-tabs are displayed in the task:

• Entity Risk — selected by default, preserving the previous behaviour.
• Product Risk — displays results from a Product Risk Assessment task run earlier in the journey.
• Related Party Risk — displays results from a Related Party Risk Assessment task run earlier in the journey.

Each sub-tab shows the output of the corresponding risk assessment task, provided that task was completed earlier in the same journey instance. Risk sub-tab data is always scoped to the current journey — historic risk assessment results from previous journeys are never displayed. If no applicable risk assessment task precedes the Review & Approvals task, the corresponding sub-tab will be empty.

The Product Risk sub-tab follows the scope of the Product Risk Assessment task in the journey. If that task has Only Assess Products Created/Updated Within Journey enabled, only results for those products are shown. If it has Save to Entity enabled, product risk scores may flow into a downstream Entity Risk Assessment — and the Entity Risk sub-tab will reflect this if the Entity Risk Assessment runs before the Review & Approvals task.

User Guide Reference: Review & Approvals — Risk Details Panel

• Risk Assessment data source — a new Risk Assessment data source is available to table components in Template Configuration. Administrators select which Risk Assessment task in the journey the data should come from using the new Risk Assessment Task dropdown on the Automated Document Generation task's properties, alongside Template Category. The resulting table lists each risk factor group, factor, and input value from the assessment, with rating, weight, weighted score, and algorithm available as optional columns. If the configured Risk Assessment task has not yet run, the table renders empty rather than causing document generation to fail.
• Related Parties (All Levels) data source — templates can now surface a main entity's complete related-party network, not just its direct relationships. This new data source traverses the entity's full association graph and returns a row for every related party found at any depth, along with its level, path, relationship, and ownership percentage. The existing Related Parties data source is unchanged and continues to return direct associations only. Note: the 2,000 related-party record limit is a single combined limit shared across Related Parties, Related Parties (All Levels), and Investment Account Related Parties — not a separate allowance per data source.
• Word content paste reliability — pasting content copied from a Word document into the Template Designer no longer disrupts the editor when the source document contains page breaks; pasted content now retains its formatting.
• Loop Component files carried over by Configuration Exchange — a Loop Component's uploaded template file is now copied into the target tenant when imported via Configuration Exchange, so an imported loop renders using its configured template rather than falling back to the default loop template. The file's contents are copied exactly; copying the original file name is not currently supported, so the file appears as template.txt in the target tenant. This does not affect the generated documents.

User Guide Reference: Document Generation

Administrators can now manage R&A V2 Profiles through a draft/publish lifecycle. Configuration changes are made in a draft and do not take effect on new journeys until explicitly published. Journey cases are bound to the profile version active at initiation and are unaffected by subsequent changes. A complete version history is maintained per profile, with every published and rejected version retained and viewable. Published versions can be archived, with the most recent non-archived version automatically becoming active. All existing R&A V2 Profiles were automatically migrated to a first published version on release.

R&A V2 Profiles are now also available as a selectable configuration type in Configuration Exchange, bringing profile promotion into the standard governed SDLC workflow alongside other configuration types.

User Guide Reference: Review & Approval Profile Versioning

This is controlled by a new Persist Documents toggle in the Investment Account task properties, disabled by default. When enabled, eligible documents are re-linked automatically based on Document DataKey matching, and are displayed and can be managed in the same way as manually linked documents. Documents excluded due to expiry configuration remain available under Matching with an Expired chip for manual linking.

User Guide Reference: Investment Account Management: Persisting Investment Account Documents Across Journeys

As part of this change, the API version is no longer entered as part of the Web Service Url field on the LexisNexis Credentials tab of the Screening Provider Configuration screen. Only the base LexisNexis web service URL is now required — for example https://staging.bridger.lexisnexis.eu. The API version is applied automatically by Fenergo SaaS.

Existing LexisNexis credentials are migrated automatically, so no action is required from configurators. If the Web Service Url is edited after this release, enter the base URL only and click Save & Test to re-verify the credentials.

There is no change to screening behaviour, search criteria, results, or Ongoing Screening as a result of this upgrade.

User Guide Reference: Configuring LexisNexis — LexisNexis Credentials

User Guide Reference: Review & Approvals

Any draft changes against an offboarded account are not applied to it: the "Current Verified Data" held at the point of offboarding is retained. Conflicts relating to the offboarded account are resolved automatically and are not surfaced in the Conflict Resolution task.

User Guide Reference: Investment Account Management Guide

• Import and export to Word — Templates can now be imported straight from a .docx file and exported back out to Word. Drafting a template in Word — reusing existing branded document templates, styles, and formatting — instead of rebuilding it by hand can dramatically cut template creation time, especially for long or heavily formatted documents. This is a huge quality-of-life win for anyone configuring templates. Full Screen, Print, Download to PDF, and Code View are grouped alongside these in a ⋯ icon in the template editor toolbar.
• No-code conditional logic — Configurators can mark a text, table, or loop component as hide-when-empty directly in Template Configuration, so blank fields and their surrounding rows or sections no longer need to be hidden with hand-written HTML.
• Template preview — A Preview button in the Template tab renders the template as HTML using sample data, without running a journey. This saves configurators from having to trigger a journey or a document generation task just to check what a template will look like.
• Journey Documents data source — Templates can now list the documents uploaded against the main entity during the journey via a new Journey Documents data source, with filtering available on document type, uploader, and upload or update date. A generated report can now reflect everything gathered during that journey.
• Journey-level data on documents — Data captured at the journey level (not written back to the entity) can now be selected and rendered in a text component, for the main entity and for related parties.
• Template versioning aligned with the journey — An Enable Versioning toggle on the Document Generation task lets a journey lock to the template version that was current when the journey started, instead of always using the latest version — preventing blank fields when a template is updated mid-journey.
• Loop Component configuration now included in Configuration Exchange — Loop Component configuration can now be promoted from a lower environment to a higher one (for example, dev to UAT to production) via Configuration Exchange, instead of having to be manually recreated in every environment.
• Localisation Code now effective — The Localisation Language setting in Template Configuration now applies to generated documents without requiring HTML changes.
• Special character language rendering — Text in languages with special characters, such as Chinese, Japanese, and Korean — including values sourced from external data providers — now renders correctly in generated documents instead of appearing blank.
• Higher capacity for large entities — Document Generation now supports a higher number of related parties and related products per entity, with documents generated safely (via a truncation warning) rather than failing when an entity's related data exceeds the supported limit.
• Empty field placeholder — A Show "-" for empty fields toggle in Template Configuration renders a dash in place of a blank value for text components and table cells, instead of leaving the field empty.
• Token highlighting, tooltip, and validation warning — Tokens in the template editor are now underlined teal (valid) or red (invalid), with a hover tooltip showing token details. A warning banner lists any tokens that won't render correctly, so mistyped tokens are caught during authoring rather than at document generation.
• Component Library reliability fix — Republishing a component no longer causes previously-selected components to reappear as "Available"; matching is now based on component content rather than a volatile internal identifier.

User Guide Reference: Document Generation

When a stage, process, task, or task assignment with an Investment Account scoping condition is reached in a journey, the journey engine evaluates the condition against the investment accounts linked to the entity.

User Guide Reference: Investment Account Management

Journey Builder administrators can configure Checkpoint tasks to complete automatically under two conditions: when no related party journeys have been launched, or when all launched related party journeys have reached a Completed or Cancelled state. When System Autocompletion is configured, the Complete button is disabled in the task view and an informational banner is displayed to the user. Auto-completed tasks are attributed to the system in the audit log using the existing autocompletion audit identifier. Autocompletion is opt-in and controlled per task via the Automation tab on the Related Party Checkpoint task in Journey Builder — existing journey templates default to Manual Completion and are unaffected unless actively updated.

User Guide Reference: Related Party Management — Automating the Related Party Checkpoint Task

Selecting 'All Data' immediately displays any Onboarding-status drafts for the entity, pinned above verified products. Typing 3 or more characters and pressing Enter searches across all product properties, filtering the table to display matching products. Switching between Table Data and All Data clears the search field and any column filters and resets the table to that scope's default view.

This capability is available to any user with existing access to the Product tab or Managed Products tab. There is no configuration required and no tenant-level toggle. This is not available within the nested Product table within the Underlying Principals tab - the existing search experience is unchanged here.

User Guide Reference:

• Using the Legal Entity Profile Page

We've added a 'Product' entity type to the existing Legal Entity Profile Configuration page.Previously the modal displayed all categories in a fixed order. When no categories are configured for 'Product' entity type, the current state experience applies (all categories, fixed order).

User Guide References:

• Working with Legal Entities and Policy->Using the Legal Entity Profile Page->"Product" Tab
• Configuring Legal Entities and Policy->Configuring the Legal Entity Profile Page->Configuring the Product Entity Type

There are two parts to the configuration. The document template carries the tag for each recipient, for example \s1\ for the first signer, which is covered in the Document Generation guide. The DocuSign account then needs a Document Custom Field whose Auto-Place Text uses {r} in place of the recipient number, for example \s{r}\, with the corresponding field type selected and the Shared checkbox ticked. If a tag has no matching shared custom field, it will still appear in the document but no signing field will be created on the envelope.

• User Guide Reference: eSignature Guide
• User Guide Reference: Document Generation Guide

For entities screened against WorldCompliance Data Plus, this release enables reviewers to:

• See structured screening data — PEP, Sanctions, Enforcements, Adverse Media, State-Owned Enterprise, Registration and other segments — presented as clear tables in the screening profile tab
• View additional entity details in the Screening List panel, including the screening list name, file build date, entity created and last updated dates, position and entity status
• See screening categories (PEP, Sanctions, Adverse Media, Enforcements, and Other) derived automatically from the returned data

Where a client is configured to screen against both WorldCompliance Data Plus and WorldCompliance – Full and the same entity is returned by both, only the WorldCompliance Data Plus result is shown, and resolving it also resolves the matching WorldCompliance – Full result — so the same entity is not reviewed or actioned twice.

The client's screening provider configuration determines which dataset is used. WorldCompliance – Full (Legacy) screening continues to work exactly as before.

User Guide Reference: Using LexisNexis OOTB Integration — WorldCompliance Data Plus

Previously, changes to journey level data were not part of the audit record and were not visible to reviewers. The new 'Journey Data Changes' tab lists each journey level data field that has been populated within the journey along with its current value, who last updated it and when, and expanding a field reveals its full history of changes within that journey. It follows the same layout as the 'Entity Data Changes' and 'Product Data Changes' tabs, and requires no additional permissions to view.

User Guide Reference: Audit in Fenergo -> Journey Level Audit

Please note: Journey level data audit records are new with this release and will be recorded from the release of this feature on a go-forward basis only.

This removes the need for analysts to re-enter the same classification separately for every client relationship affected by a single confirmed match. This capability is managed by Fenergo Support or Product at the tenant level; there is no client-facing configuration screen. When enabled, resolving a hit as Match during OGS Stage 1 also displays a Classification Data panel using the same fields as On-Demand Screening. Analysts working the downstream On-Demand Screening tasks that this match triggers are not asked to re-enter that classification.

User Guide Reference: Using OGS: Screening Resolution & Client Selection — Stage 1 — Screening Resolution

User Guide Reference: Related Party Management->Configuration

This is feature will affect how product risk is calculated and does not have a configurable opt-in mechanism. For tenants with the Product domain enabled, the change is available in non-live tenants from 26 August 2026 and will be enabled in all live tenants from 29 September 2026. To have it applied to your live tenant earlier, contact your Fenergo Client Partner.

Previously, the Product Risk Assessment made no distinction based on where a product sat in its lifecycle. A product a client had asked to close was assessed on the same footing as one they had just opened, which could overstate an entity's product risk and, where product risk feeds entity risk, its overall risk position.

With this change, products with 'Offboarding' and 'Offboarded' states will be excluded from their own risk being recalculated and from any aggregation of product risk to the root entity. Any risk score or rating already stored against an excluded product remains unchanged — it is simply not refreshed.

Excluded products are not displayed in the task, but they are transparently recorded on the assessment result under excludedAggregateAssessments, with each entry carrying the product's aggregateId and lifecycleStatus. Surfacing excluded products directly in the task view is planned for a future enhancement.

This change applies only to assessments executed on or after the date it is enabled for your tenant. Existing product risk scores, ratings and the entity risk values derived from them are not recalculated, restated or migrated.

Notice of Change: Exclusion of Offboarding and Offboarded Products from Product Risk Assessment

User Guide Reference: Using the Product Risk Assessment Task

This release enables you to:

• Configure, per provider, a Supporting document action item for entity — On Demand Screening only — added to screening tasks as Optional or Required (when hits are returned), with a selectable Document type
• Configure, per provider, a Supporting document field for hits added to the match resolution form (applies to both On Demand and Ongoing Screening), with a selectable Document type
• Set the configuration once per provider, available for every provider, including custom screening providers and Manual Screening

When the entity action item is Required, the document is mandatory to complete the entity's screening if that provider returned hits for the entity, and optional when the provider returned no hits. This is independent of the match outcome and of the resolution state.

User Guide Reference: Configuring Screening Functionality — Supporting Documents

When the checkpoint task is active, it displays a read-only list of all monitored Product RP child journeys and their current statuses. Once all listed child journeys are in a Done or Cancelled state, the Complete button becomes actionable and the user can manually complete the checkpoint task to allow the parent journey to proceed.

User Guide Reference: Configuring Journeys — Product Related Party Checkpoint

This setting is not enabled by default. Administrators can opt in by enabling the Exclude indirect shareholder associations toggle on the Provider Config screen.

User Guide Reference: Configuring External Data Sources — Excluding Indirect Shareholder Associations

This behaviour is not enabled by default. Administrators can opt in by enabling the Include inactive companies toggle on the Provider Config screen. Once enabled, analysts can retrieve the full Orbis profile for an inactive entity and complete CDD directly within the Fenergo journey.

User Guide Reference: Configuring External Data Sources — Including Inactive Companies

This release introduces automatic de-escalation. When you set a new materiality status on an assessment for an entity that is currently escalated, the escalation clears as part of that same action — there is no extra step, prompt, or new screen to interact with. Every de-escalation is recorded in the audit trail alongside the entity's other history.

User Guide Reference: Using ODS: Screening Resolution & Materiality — De-escalation

See user guide for the full configuration guide and behaviours to note with this new functionality:

Entity User Guide Reference: Working with Policy User Guide->Clear Field Value if Trigger Condition Is Not Met

Product User Guide Reference: Product Enablement User Guide->Product Field Value Reset

This release introduces a Materiality Assessment entitlement that can be switched off for a client. When it is, the materiality action, the Material/Immaterial/Escalated status chips and Materiality filter, the reassessment warning, and the requirement to complete materiality before finishing the task are no longer shown, along with the Materiality column on the Screening Assessment Outcomes tab. Escalate is unaffected and continues to work as before. This is managed by Fenergo Support or Product; there is no client-facing configuration screen.

User Guide Reference: Using ODS: Screening Resolution & Materiality — Materiality assessment

This release enables you to:

• Add an optional Classification data column to the results table from table configuration, appearing as the last item in the column list
• See the Classification Data field values for each hit, concatenated in the order they are configured for that hit's category
• Sort and filter on the column using the same table tools as any other column
• Rely on the column staying disabled by default on every existing and new view until you turn it on

The column is empty for v1 screening tasks and for any v2 hit with no Classification Data recorded, since Classification Data is a v2-only concept.

User Guide Reference: Using ODS: Screening Resolution & Materiality — Classification data column

This release enables you to:

• Configure one or more trigger conditions on a Classification Data field, referencing a Policy field on the main entity of the journey or on the entity of the match
• Show or hide a Classification Data field automatically based on those conditions, using the combination logic already defined in your policy configuration — no new configuration screen or rules engine required
• Rely on hidden fields being excluded from mandatory-field validation, so analysts are never blocked by a field that doesn't apply to their case
• Set a Classification Data field's Target Entity to Client or Related Party, so classification data can be captured specifically about a Related Party in addition to the Client (configured as two independent field definitions, one per Target Entity)

User Guide Reference: Configuring ODS: Screening Resolution & Materiality — Classification Data setup

This release enables you to:

• See a Material (red), Immaterial (neutral) or Escalated (amber) status chip on each entity in the list, alongside a Company / Individual entity-type icon
• Filter the list from a Filters modal by Materiality (Material, Immaterial), Case status (In progress, Escalated, Completed) and Entity type (Company, Individual), combining selections across groups
• See active filters as removable tokens with a count badge, and clear them individually or all at once
• Search the list by entity name

User Guide Reference: Using ODS: Screening Resolution & Materiality — Entity list: status indicators, filtering and search

ETL Agency Migration brings agency migration into the same self-service, preview-and-validate experience clients already use for standard ETL. It complements standard ETL rather than replacing it — where an Investment Manager or Underlying Principal is also a client, its full client record is still migrated through a standard ETL project.

This release enables you to:

• Create a dedicated ETL Agency Migration project, managed separately from standard ETL so that agency data types are never mixed into a client migration and each project validates against the policy appropriate to it.
• Migrate each participant in the Agency Data Model as its own data type — Investment Manager, Underlying Principal, Managed Relationship and Managed Product — rather than loading them all as generic Company records.
• Supply your agency combinations through the Agency Associations step, a structured input matrix identifying the Investment Manager, Underlying Principal, Managed Relationship and Managed Product on each row.
• Have the Agency Data Model built for you — six associations are created for every Agency Associations row, with no need to define relationship types or relationship properties yourself.
• Let the system create Managed Relationships automatically for each unique Investment Manager and Underlying Principal pairing, reusing any that already exist, or supply your own named Managed Relationships with full policy data.
• Verify the integrity of the whole model before loading, using the new Agency Validation step — resolving identifiers against existing verified records and detecting unresolved references, orphaned entities, Managed Relationship conflicts and Managed Product ownership conflicts.
• Work through the familiar ETL steps for every data type — Select Data Source, Filter Data, Map System Fields, Map Policy Fields, Map Lookups, Data Groups, Preview and Validation.
• Use the existing ETL Validation, Cross-Validation and Reconciliation reports, notifications and Post Load Actions throughout, with no new report types or notification templates to learn.

Access is controlled by the ETL Agency Migration Administrator permission, which is fully separate from the standard ETL permission.

User Guide Reference: ETL Extract Transform Load -> ETL Agency Migration

Visibility of individual accounts is enforced by the reviewer's Entity and Search access layers, and existing Review & Approvals commenting, permissions, and approval decision behaviour apply consistently across both account types.

User Guide Reference: Review & Approvals

First, categories and tabs with no field-level differences between in-flight and verified data can be optionally hidden by default through the Journey Schema, reducing information overload and helping reviewers focus only on what requires a decision. This behaviour applies to journeys triggered after deployment and can be toggled via task properties.

Second, fields whose values are controlled by conditional value rules can be optionally classified and badged as "Calculated" directly on the task and made read only so the user cannot change their value, ensuring greater transparency and trust in the review process. This behaviour applies to fields at the entity level only currently.

User Guide Reference: Conflict Resolution and Proposed Changes User Guide->Hide Panel and Calculated Fields

Previously, Risk Model factor group thresholds required a minimum value of zero. This constraint has been removed so that group-level thresholds are consistent with Configuration Model and overall Threshold Model behaviour, both of which already supported negative ranges.

User Guide Reference: Configuring Risk Functionality — Assign a Custom Threshold to the Collection

When the task becomes active, it evaluates product RP associations for all draft products in the journey, filters by the configured association types, deduplicates by RP entity, and launches exactly one child journey per unique qualifying RP entity. If no qualifying RP entities are identified, the task transitions to Done immediately without launching any child journeys.

The task is configured in Journey Builder with two mandatory fields: Journey Type, which determines the journey schema applied to each qualifying RP entity at launch time, and Product Association Types, which filters which product RP associations are evaluated at runtime. The following task sequence must be followed in the schema: Product Related Party Launchpad → Product Related Party Checkpoint → Merge Product RP Drafts → Verify Product RPs → Verify Products.

The Products domain must be enabled for the tenant for the Product Related Party Launchpad task type to be available in Journey Builder.

User Guide Reference: Configuring Journeys — Product Related Party Launchpad

User Guide Reference: Investment Account Management

The Provider Priorities tab on the External Data Configuration screen is now available, allowing administrators to configure a default provider for use with the External Data Entity Enrichment Task. Organisations using KYRA:Source have access to additional Rules configuration within the same tab.

User Guide Reference: Configuring External Data Sources

Previously, all data imported via KYRA:Source was attributed to a generic system label in the audit trail Source field, making it impossible to identify which external provider supplied a given data point. With this update, the provider name is automatically captured at the point of import and displayed in the audit trail, giving compliance teams a clear and accurate record of data provenance. This applies to all KYRA:Source imports regardless of journey type. Audit trail entries for manually entered data are unaffected and continue to display the operator as the source. Existing audit trail entries are not backfilled — the change applies to imports occurring after deployment.

Key Details​

• Unified Review Task: Entity data, data groups, and related-party hierarchy updates are reviewed in one place, replacing the previously fragmented experience.
• Source Traceability: Every extracted value is supported by full traceability — including document reference, page number, and AI rationale — so reviewers always understand why a value was extracted.
• Explicit Resolution: Reviewers must record a decision on every extracted item before the task can be completed. No changes are applied without an explicit resolution.
• Flexible Reviewer Control: Extracted values can be accepted, rejected, edited, or replaced with a custom value before being committed to the record.
• Improved Related-Party Handling: Reviewers can compare potentially matching records, correct extracted information, and control whether an existing record is retained, updated, or replaced.
• Maker-Checker Support: Changes are written only after the Checker completes their review, with no data committed during the review stage.
• Automatic Task Completion: Tasks with no eligible content to extract complete automatically, removing unnecessary steps.
• Document Scope Controls: Extraction can be limited to documents uploaded in the current journey and to the latest document versions only.

Implications​

• Ensures no extracted data is applied to the entity record without a deliberate reviewer decision, reducing the risk of unintended changes.
• Provides full traceability from extraction through to resolution, supporting compliance and governance requirements.
• Improves reviewer confidence through source evidence and AI rationale surfaced directly in the task.
• Supports Maker-Checker workflows natively, enabling institutions to apply appropriate oversight controls to document-driven data updates.

Client Adoption Guidelines​

1. Create a draft of the relevant journey, remove the legacy Document Data Extraction task, and add Document Data Extraction V2 to a journey containing Documents V2.
2. Enable the required entity-data and related-party extraction settings on the new task, and disable the extraction settings on the document upload and related party task if applicable.
3. For Maker-Checker journeys, link a separate Checker task in Journey Builder before publishing.
4. Validate the configuration in a lower environment before enabling on production tenants.
5. Review the detailed user guides available via the community portal for full configuration and workflow guidance.

User Guide References​

• Fenergo Digital Agents – Introduction
• Fenergo KYRA:Docs – User and Configuration Guide
• KYRA:Docs User Guide

Managed Products and Fund-to-MR products are always excluded from sharing. Each shared product is an independent record on the child entity, linked back to the Group entity via an automatic Owner association.

User Guide Reference:

See Sharing Products Across Entity Groups for full configuration steps.

User Guide Reference: Investment Account Management

This capability is available from the Journey Hub, the Journey Dashboard, and the Advanced Dashboards. Journey Owner can be unassigned at individual journey level from the Journey Hub and the Journey Dashboard. Task Owner can be unassigned individually from the Journey Hub, or across multiple tasks in bulk from the Journey Dashboard task list and the Tasks Advanced Dashboard. In all cases, team assignments are preserved — only the owner user field is cleared.

The action is controlled by the new Unassign Journey or Task Owner permission in the Journey section of Security Configuration. Users without this permission do not see the Unassign option.

User Guide Reference: Configuring Journeys — Unassigning Journey Owner and Task Owner

The three new fields are:

• Product Onboarded Date — recorded the first time a product reaches an onboarded status in a client onboarding or lifecycle event management (LEM) journey. This date is not overwritten by subsequent lifecycle events.
• Product Update Date — recorded when a change is made to product data and then the change gets verified.
• Product Offboarded Date — recorded when a product's status changes to offboarded.

All three fields should be made read-only and not edited by users. They can be made visible in the EPP product tab via secondary identifiers, and within Product tasks in journeys. In the audit table the dates can be tracked via the Lifecycle Status which will show the status value and the date it was updated.

User Guide Reference:

• Product System Date Fields
• Configuring Product System Date Fields

User Guide Reference: Advanced Reporting User Guide

User Guide Reference: Conflict Resolution and Proposed Changes

Tags and References are configured on the requirement and are available on Data, Document and Ownership and Control requirements. Tags and References added to product requirements are returned in the Product Policy API responses and are carried across when a Product Requirement Set is transferred through Configuration Exchange. Product tags are maintained separately from Policy tags.

User Guide References:

• Configuring Policy User Guide
• Product Enablement User Guide

User Guide Reference: Custom Dashboards

User Guide Reference: KYRA:Report

User Guide Reference: ETL Extract Transform Load -> ETL Screening

This release enables you to:

• Resolve screening hits with a Match / No Match decision, a reason, and optional supporting evidence
• Classify confirmed hits by PEP tier, jurisdiction, sanctions type, or other configurable classification data
• Assess materiality at entity and Related Party level, with one consistent outcome stored per RP
• Reuse a previous materiality assessment where the same match has already been assessed
• Apply a defined sanctions proceed flow and escalation process for confirmed matches
• Upload and preview supporting documents at entity and match level
• Review Ongoing Screening results in two stages — resolve hits per entity in Stage 1, then select which clients require a downstream ODS journey in Stage 2
• Trigger downstream ODS journeys for selected clients, with OGS-raised hits clearly highlighted
• Auto-complete the screening task when no hits are returned from the provider
• View historical screening match decisions and materiality outcomes directly on the Entity Profile page via the new Screening Assessment Outcomes tab, without opening completed tasks

User Guide References: Screening & Materiality Assessment v2 — Overview | Using ODS: Screening Resolution & Materiality | Using OGS: Screening Resolution & Client Selection | Configuring ODS: Screening Resolution & Materiality | Configuring OGS: Screening Resolution & Client Selection

This enhancement doesn't require any actions to enable — System Default Instructions are applied automatically. We strongly recommend reviewing them and amending or supplementing them with custom instructions specific to your organisation before your next screening run.

User Guide Reference: KYRA:Screen User Guide → Screening Instructions

• Default — every OGS-enrolled entity is screened against every OGS-enabled Configuration Set, with hits segregated into a separate journey per set (category-based segregation, single shared Accept List).
• Per Configuration Set — entities are subscribed to specific Configuration Set(s) and screened only by those (jurisdiction-based segregation, dedicated Accept List per set).

Each Configuration Set can be mapped to its own Journey Schema with its own SLAs, team assignment, and routing.

User Guide Reference: Configuring LexisNexis -> Multiple Configuration Sets and Ongoing Screening Pre-Requisites

User Guide Reference: Audit in Fenergo -> Entity Level Audit

User Guide Reference: ETL Extract Transform Load -> ETL Delete Associations

This is supported in products within the Manage Products task data requirements and data groups. We will add support within the Products section of the Agency Request Details task next.

User Guide References:

• Configuring Policy User Guide
• Product Enablement User Guide

User Guide Reference: Investment Account Management

User Guide Reference: Comments on LE and Journey

Previously, external validation applied only when users updated Data Group fields through the journey UI. Validation is now also enforced when Data Groups are updated programmatically — including through data migrations, ETL processes, and API integrations. Existing adapter configuration does not need to change; the broader enforcement is applied automatically.

User Guide Reference: Configuring Journeys — Multi-Field External Validation in Custom External Adapters

This extends the existing Document Generation capability which already supports Entity Data, Related Parties, Associations, Products, Deals, and Collateral — to cover the full breadth of investor data required to generate subscription and onboarding documents.

This release enables you to:

• Include Related Bank Accounts in generated documents — surface bank account data linked to the main entity using Table and Loop components
• Include Related Investment Accounts in generated documents — surface investment account data linked to the main entity
• Surface Investment Account Related Parties, Bank Accounts linked to Investment Accounts, Funds, and Share Class as nested data sources within Related Investment Accounts — each available as Table or Loop components in the Component Library
• Apply filter conditions at the component level to narrow results to a specific account, fund, or share class instance
• Use all new data sources with both HTML Override and Template Designer template approaches
• Add these sources to new or existing document templates without affecting existing component or template configuration

All investment account data sources are available to tenants with Accounts enabled. Tenants without this will not see these sources in the Component Library.

User and Configuration Guide Reference:

• Document Generation

The following enhancements are now available in the Template Designer:

• Inline token insertion — type {{ to trigger a searchable autocomplete dropdown of available data keys, or {% to insert a loop component, directly at the cursor position without leaving the keyboard.
• Auto-save — the editor automatically saves a draft every 60 seconds in the background, protecting against loss of work during longer authoring sessions.
• Drag-and-drop reordering — block content elements can be repositioned within the editor via drag-and-drop, removing the need for cut-and-paste when restructuring templates.
• Alphabetical component sorting — text, table, and loop component dropdowns are now sorted alphabetically by component key, making lookup faster and more predictable.
• Code beautifier — switching to code view now displays formatted, indented HTML, making code view a practical editing surface rather than a raw output.
• Extended toolbar — the editor toolbar now includes find and replace, special character insertion, a live word and character count, print preview, and a keyboard shortcuts reference panel.
• Quick Insert — a contextual + button appears in the editor left margin on empty lines, providing a shortcut for inserting block elements without scrolling to the toolbar.
• Page Border toggle — a Page Border toggle is now available in the Layout tab of Template Configuration. When enabled, the PDF renderer wraps each page with a solid border.

User Guide Reference: Document Generation

Previously, the Automated Document Generation task would fail entirely when an entity had more than 50 direct related party associations. This limit was misaligned with the real-world data structures of clients with complex corporate structures, including funds, trusts, partnerships, and large ownership populations.

The following changes have been made:

• The maximum number of direct related party associations processed for Related Party Data has been raised from 50 to 500.
• The maximum number of related products processed for Related Products Data has been raised from 50 to 500.
• When an entity exceeds either limit, the task no longer fails. Instead, the document is generated using the first 500 records for the affected data set.
• When truncation occurs, a user-visible warning is displayed that includes the actual count and the applied limit.

Note: Document Generation continues to support direct relationships to the main entity only. Nested related party connections (second- and third-level associations) are not included in generated documents.

User Guide Reference: Document Generation

User Guide Reference: Document Management->Document Requirement Autolinking

On the end user side within a journey, if data group fields are added to the search request then we will change the view in the data group. The search modal will show a two-tab layout: a Search tab presenting the search box alongside any configured data group fields, and a Details tab where the selected result is populated for review and saving. Where multiple providers are configured for the same data group, results are aggregated into a combined grid.

User Guide Reference: Multi Field External Search and Details API

User Guide Reference: Audit in Fenergo-> Journey Level Audit

**User Guide Reference:**User Guide Reference: Policy V2 Edit Mode

This won't affect any direct user or API interactions in the Fenergo app, however we have received early feedback that some customers needed to update automated testing that utilised the original Add button.

User Guide Reference: Using Data Groups

This release enables you to:

• Select and action multiple orphan entities from the Matches tab. Each entity row now includes a checkbox. Users can select one or more entities and trigger offboarding for all eligible selected records in a single action.
• Navigate directly to offboarding journeys from the Actioned tab. A new Journey column provides a hyperlink to the offboarding journey for each actioned entity, opening in a new tab.

User Guide Reference:

• Data Protection Dashboard

This means that policies referencing Related Products data are evaluated with the correct data available throughout the Ongoing Screening lifecycle, and automatic offboarding decisions accurately reflect whether scoping conditions are genuinely met.

No configuration changes are required. All tenants using Related Products in their policy scoping conditions will benefit automatically.

Where an entity has more than three configured roles, up to three render inline with a +N more affordance to surface the rest.

User Guide Reference: Configurable Statuses

Completed Investment Account Risk Assessment and Bank Account Risk Assessment tasks will now display a read-only Assessment Outcome banner showing the Aggregate Risk Category and Aggregate Risk Score.

User Guide Reference: Investment Account Risk Assessment Task User Guide

Configuration Guide Reference: Investment Account Risk Assessment Task Configuration Guide

User Guide Reference: Investment Account Management

User Guide Reference: Multi-Publish

ETL Screening addresses this by enabling clients to load their historic screening data directly into the Fenergo Screening domain.ETL Screening is currently available as a Beta feature while we conduct performance testing. It can be enabled on request, clients interested in this feature should contact their Fenergo representative.

User Guide Reference: ETL Extract Transform Load -> ETL Screening

This release introduces automation support for the OGS: Unsubscribe from Ongoing Screening task, allowing the system to intelligently handle unsubscription for eligible entities and RPs without user intervention.

User Guide Reference: Configuring the Autocompletion Agent

Until now, the relatedparties dataset projected only the association type. For standard related party associations this type is the business relationship (for example Director or Shareholder). For Product and Agency associations, however, type is a fixed value (product or agencyRequest) used to set those associations apart, and the meaningful relationship was not available in reporting.

This release enables you to:

• Report on the specific Product relationship for an entity (for example Owner, Guarantor or Co-signer) using the new subtype column
• Report on the specific Agency relationship for an entity (for example Underlying Principal) using the new subtype column
• Distinguish Product and Agency associations from one another, and from standard related party associations, within the same dataset
• Query historic associations as well as new ones — existing records have been backfilled so the subtype column is populated across the full dataset

The existing type column is unchanged, so reports and extracts that rely on it today continue to behave exactly as before. For standard related party associations the subtype column is empty.

The FenX assistant has also been updated to interpret these relationships. When you ask for entities with a given Product or Agency relationship, the assistant now constrains its generated query to the subtype column for those associations, while continuing to use type for standard related party relationships.

User Guide Reference:

• SQL — Related Parties and Products examples
• Advanced Reporting in Fenergo

Note: KYRA:Policy can only be enabled on one tenant at a time. Contact your Fenergo representative to have it enabled on your tenant.

User Guide Reference: KYRA:Policy User Guide

User Guide Reference: Document Data Extraction — Default Value Selection Mode

User Guide Reference: KYRA:Docs User Guide — Additional Considerations

Both events apply to Journey-, Stage-, and Task-level SLAs and include the affected entity identifiers, due date-time, approaching threshold, current SLA status, and the Journey/Stage channels. For Task-level events, the payload also carries the configurator-defined TaskKey to make routing in high-volume consumers straightforward.

SLA Event Notifications are opt-in via a new Enable SLA Event Notifications toggle on the Journey Configuration modal in Journey Builder, gated by the existing Journey Configuration Edit permission. The toggle is off by default to preserve existing behaviour.

User Guide Reference: Configuring Journeys → Enabling SLA Event Notifications

Developer Guide Reference: Event Registry → SLA approaching due / SLA past due

User Guide Reference: Permission Catalogue

The new toggle, "Restrict task reopening to assigned team", is available in the Journey Configuration panel (accessed via the cog icon on the Journey page). It is disabled by default, preserving existing reopen behaviour. When enabled, any user who does not belong to the team assigned to a task will be prevented from reopening it. Tasks with no assigned team are unaffected by this restriction.

User Guide Reference: Configuring Journeys

User Guide Reference: Related Party Management->Related Parties Task

Screening Provider Configuration (Screening Domain)​

Screening Provider Configuration is now available as a selectable item within the Screening domain of Configuration Exchange. Configurators can import Secondary Identifiers and Configuration Sets for the following providers:

• World-Check One (WCO)
• Grid
• LexisNexis

Previously, these configurations had to be manually re-entered in each tenant environment, introducing the risk of inconsistency between Dev, UAT, Pre-Prod, and Production. With this release, provider configurations can be promoted through the standard Configuration Exchange workflow alongside other screening setup.

Key behaviours:

• Secondary Identifiers (screening attribute mappings) and Configuration Sets (provider operational parameters) appear as two selectable sub-types under Screening Provider Configuration within the Screening domain.
• Provider configurations are not versioned — they are always imported as the latest active setup from the source tenant.
• Credentials (API keys, usernames, passwords) are automatically excluded from exports and will never be transferred across environments.
• Required dependencies — including Country Reference Data Lists (ISO Alpha-2/Alpha-3), Linked Lookups (Screening Resolution Status/Reason), and provider-specific lookup values — are automatically detected and imported before the provider configuration, without manual pre-setup.
• If a provider is not yet enabled in the target tenant, the configuration is imported in a Disabled state and a warning is recorded in the Import Log.
• The Import Log displays provider name, configuration type (Secondary Identifier / Configuration Set), and import status (Imported / No Change / Failed) for each item.

Permissions required (no new permissions introduced):

• Configuration Exchange Access — to view the Screening Provider Configuration tab
• Configuration Exchange Edit — to perform imports
• Screening Configuration Access — to view provider configurations in the source tenant
• Screening Configuration Edit — to apply imported configurations in the target tenant

Related Party Scoping Rules (Journey Domain)​

Related Party Scoping Rules (RPSRs) are now available as a selectable configuration type within the Journey domain of Configuration Exchange. Configurators can import RPSR definitions across tenant environments without manually recreating rule logic, eliminating configuration drift between environments.

Key behaviours:

• RPSRs appear in the Bulk Selection modal under the Journey domain with type "Related Party Scoping Rule".
• This is an import-only capability — RPSRs cannot be exported individually.
• Imported rules are always imported in a Published state and are immediately available for selection in Journey Builder. The "Import in a Published State" toggle has no effect on RPSRs.
• A new version is created in the target tenant on each import, incremented from the latest existing version. A traceable Version Note is generated automatically: "Imported from [Source Tenant Name] (Version [x]) via Configuration Exchange Record: [Import Record Name]."
• Draft versions of an RPSR in the target tenant are not overwritten — these will log as "No Change."
• Required dependencies (Relationship types, Entity Types, Association Types, Requirement Categories) are automatically detected and imported before the RPSR itself.
• When a Journey Schema and its referenced RPSRs are included in the same import record, task references within the Journey Schema are automatically remapped to the newly imported RPSR IDs — no manual reassignment required.
• Availability is controlled by the environment feature toggle "Enable RPSR Import". When this toggle is OFF, RPSRs will not appear in the Bulk Selection modal.
• Related Party Scoping Rules are also now supported in Configuration Release Hub (CRH) under the Journey domain, enabling CRH-based environment promotion workflows.

Permissions required (no new permissions introduced):

• Configuration Exchange Access — to view the Imports menu
• Configuration Exchange Edit — to select and add RPSRs to an import record
• Configuration Exchange Publish — required to execute the import (RPSRs always import in published state)
• Journey Access / Edit / Approve — required in source and target tenants per the standard import flow

User Guide References:

• Configuration Exchange
• Configuring Screening Functionality
• Related Party Adapted Experience

User Guide Reference: KYRA:Source

The new toggle, "Require reason when cancelling a journey", is available in the Journey Configuration panel (accessed via the cog icon on the Journey page). It is disabled by default, preserving existing cancellation behaviour. When enabled, the 'Reason for Cancellation' dropdown in the Journey Cancellation modal displays a required indicator and submissions cannot be made without a cancellation reason.

Configuration Guide Reference: Configuring Journeys

User Guide Reference: Working with Journeys->Working with the Autocompletion Agent

The new toggle, "Require comments when reassigning a task", is available in the Journey Configuration panel (accessed via the cog icon on the Journey page). It is disabled by default, preserving existing reassign behaviour. When enabled, the comment field in the Reassign modal displays a required indicator and submissions without a comment are rejected with a validation error.

This requirement applies to both single task reassignment and bulk task reassignment, including the Bulk Reassign action available in Advanced Dashboards (Tasks and Journeys dashboards).

User Guide Reference: Configuring Journeys

A toast notification confirms the name of the restored filter on login. The Tasks and Journeys dashboards each independently persist their own saved filter selection.

Key behaviours:

• If a saved filter has been deleted since your last session, the dashboard loads with no filter applied and no error is shown
• Views persistence is unaffected — Views and saved filters continue to work independently

User Guide Reference: Advanced Dashboards User Guide

Users can manage their notification preferences from their profile page under the Technical heading, including opting in or out of in-app notifications and email alerts for these messages.

User Guide Reference: ISDA Amend

To add or remove datasets under the same Match ID or to look for a new Match, the user can click the entity name to open the search with the previous criteria pre-populated and ready to return the latest data.

User Guide Reference: ISDA Amend

This release enables you to:

• Configure Dynamic Access Layer rules using Lifecycle Status. On the 'Current Product Metadata' source for the Product data type, Lifecycle Status is now selectable as a field with operators 'Equals', 'Not equals', 'In' and 'Not in', and the values Onboarding, Onboarded, In Review, Offboarding and Offboarded.
• Re-evaluate Product Access Layers at verification. When the Verify Products V2 task is completed, Product Access Layers are re-evaluated using the expected post-verification lifecycle status of the product. A draft in Offboarding becomes Offboarded; any other draft status becomes Onboarded. All other rule conditions continue to be evaluated against the latest draft data. The result is applied before the product transitions to verified state.

User Guide References:

• Dynamic Access Layers
• Product Lifecycle Status (Configuration)

Key Details​

• Product Scoping Rules now follow the same import behaviour as other rule dependencies in Configuration Exchange.
• When a journey schema containing a Manage Products task with an assigned Product Scoping Rule is imported, the rule is captured automatically as a dependency. The dependency defaults to the latest version available at the Configuration As Of date and can be overridden if required.
  • The latest version of the Product Scoping Rule available in the target tenant (i.e. likely the imported dependency) is the version applied the Manage Products task in the imported journey schema. This may not be the same as the version configured against that Manage Products task in the source tenant Journey Schema (i.e. if the dpendency version was different).
  • We already warn users when a newly published Task Display Product Scoping Rule is linked to one or more Manage Products task in Journey Schemas that may need to be updated to the latest version.
  • Journey schemas should reference the latest version of a Product Scoping Rule except where a specific version is required for A/B testing in lower tenants.

User Guide Reference​

• Product Enablement – Configuration Exchange

Key Details​

• A Legal Hold can be created, viewed, modified or removed from the Entity Profile Page ellipsis menu. Only one Legal Hold may exist per entity at a time.
• Each Legal Hold captures a Reason (Reference Data lookup), Details, Duration (in months) and Responsible Team. The Start Date is set on creation and the Expiry Date is derived from Start Date + Duration.
• Legal Hold Active and Legal Hold Expired status chips appear on the Entity Profile header so the current state is visible at a glance.
• The Data Deletion Scheduler excludes entities with an active Legal Hold, and the Delete Entity Data API rejects deletion attempts for those entities. Expired or removed Legal Holds no longer block deletion.
• Advance expiry notifications are sent to members of the Responsible Team at 30, 15, 5 and 1 days before the Expiry Date, subject to the user's permissions and notification settings.
• All Legal Hold lifecycle events (Create, Modify, Remove) are fully audited. Audit entries are immutable and persist after the Legal Hold is removed or the entity is deleted.

Implications​

• Entities subject to legal or regulatory preservation can no longer be deleted accidentally, either by the scheduler or via the Delete Entity Data API.
• New permissions (Legal Hold Access, Legal Hold Edit, Legal Hold Delete) have been added under the Entity Data domain and must be assigned to the relevant roles before the feature is used.
• Legal Hold audit events are available in Advanced Reporting and via audit query capabilities. They are intentionally excluded from the Entity Profile audit drawer.

User Guide Reference​

• Legal Holds User Guide
• Data Protection – Data Deletion Execution
• Deleting Data – Triggering a Journey

User Guide Reference: Essential Fenergo SaaS User Guides -> Working with Journeys

This release enables you to:

• Apply Product Access Layers to Conflict Resolution. Where Product Access Layers are in use, products and conflicted product fields a user is not entitled to see are hidden from the Conflict Resolution task. Hidden conflicts are resolved automatically using the same defaulting rules as visible conflicts — the user is not required to do anything with them, is not blocked from completing the task, and is not shown any message, count, or icon indicating that conflicts are hidden.
• Default product field selections by category. When configuring the Conflict Resolution task in Journey Builder, you can select one or more Product Categories whose conflicted fields should default to "Current Verified Data" rather than the standard "This Journey". A user with Edit permissions in the task can still change the selection on any visible conflict.

User Guide Reference: Conflict Resolution and Proposed Changes

• User Guide Reference: Configuring Journeys -> Configuring the Autocompletion Agent

We're introducing a warning toast that monitors product field changes and alerts the user when current inputs will result in an access layer they lack, recommending to finalise all required inputs for the product before saving. This mitigates the risk of an inaccessible and incomplete product that may otherwise block task completion.

This release enables users:

• To be informed when inputs will result in losing access to the product
• To ensure all required inputs are provided before saving
• To be aware of why a product may become inaccessible and later, hidden
• To make corrections in the event of an input mistake

User and Configuration Guide Reference:

• Product Enablement – Access Layers

Purpose values are configurable via the Reference Data Editor under the 'Bank Account Purposes' reference data list. If the toggle is subsequently turned off, any previously captured purpose values remain visible as read-only in the Account Purpose column and are not removed.

User Guide Reference: Investment Account Management Guide

When the toggle is disabled (the default), existing behaviour is preserved: Investment Accounts are immediately excluded from entity evaluation as soon as they are marked as Pending Offboarding.

User Guide Reference: Investment Account Management Guide

The page introduces a new Evaluate Investment Account at Verified Offboarding tenant-wide toggle (disabled by default), and hosts the Show Investment Account Associations toggle, which has been relocated from Entity Profile Configuration with its existing behaviour preserved.

User Guide Reference: Investment Account Management Guide

User Guide Reference: Document Management -> Restrict File Size and File Type

User Guide Reference: Investment Account Management

User Guide Reference: ISDA Amend

User Guide Reference: Investment Account Management

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

User Guide Reference: Audit in Fenergo-> Entity Level Audit

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.

User Guide Reference: ETL Extract Transform Load -> ETL Documents

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.

User Guide Reference: ETL Extract Transform Load -> Journey Launch

User Guide Reference: Entity Profile->"Journeys" Tab

User Guide Reference: Configuring Working Days for SLAs

User Guide Reference: Ad-hoc Reviews in the Review Domain

User Guide Reference: Transitioning from Journey Schedules to Review Domain

User Guide Reference: Static Access Layer Validation in ETL

Access logs are captured for:

• Entity records
• Alerts
• Alerted Transactions (transactions contributing to an alert)
• Suspicious Activity Reports (SARs)

User Guide Reference: Advanced Reporting User Guide

User Guide Reference: Document Management V2 User Guide->Document Archiving

• User Guide Reference: Product Enablement User Guide

User Guide Reference: ETL Extract Transform Load

Three additional formats are now supported:

• yyyy/MM/dd (e.g., 2024/03/15)
• yyyy.MM.dd (e.g., 2024.03.15)
• yyyy-MM-dd (e.g., 2024-03-15)

User Guide Reference: ETL Extract Transform Load User Guide

User Guide Reference: ETL Extract Transform Load -> ETL Documents

User Guide Reference: Stable journey IDs

The updated naming formats are:

• No Fund linked: EntityName_Account
• Fund linked, no Product: EntityName_FundName_Account
• Fund and Product linked: EntityName_FundName_ProductType_Account

The name updates dynamically as Fund Product linkages are added or changed. If the generated name exceeds the configured character limit, it is truncated from the end. No new toggles or permissions are required - this behaviour is governed entirely by the existing Default Investment Account Name toggle. The tooltip text for this toggle has also been updated to reflect the new logic.

User Guide Reference: Investment Account Management

User Guide Reference: Configuring Policy

We've made 2 key changes:

• Navigating away from a draft product will save, without triggering validations: This minimises obstructions to the user when they are providing quick updates to multiple products.
• 'Save' button is now 'Save Product': When you click the 'Save Product' button, this will save and validate only that product. This gives users discretion over when they validate input, checking for completeness when ready. Previously, this operation saved and validated all products which took time and could make the experience less focused.

The 'Complete' action will continue to save and validate all product drafts to ensure the task can be safely closed.

• User and Configuration Guide Reference: Product Enablement User Guide - Manage Products Task

Where applicable, the most recently saved resolution for the same match is automatically populated to reduce repeat analyst dispositioning.

User Guide Reference: Screening resolution re-use

To maintain compatibility, the existing Linked Lookup fields remain as-is, now labelled with a 'Legacy' prefix. This ensures that existing field configuration persists without intervention.

User Guide Reference: Reference Data User Guide

IMPORTANT This feature is enabled in all tenants and will require adoption from all clients. From the end of May 2026 our SaaS request process for creating API Client IDs on your behalf will cease and you will be responsible for creation and maintenance going forward.

User Guide Reference: API Client Management

User Guide Reference: Digital Subscriptions User Guide

Configuration Guide Reference: Digital Subscriptions Configuration Guide

• ETL Map Lookups step accepts NULL as a valid input for lookup fields.
• Users can proceed to Preview and Load when NULL is provided.
• Existing lookup values are cleared in the target record when NULL is processed.
• Behaviour is now consistent across lookup and non-lookup field types in ETL migrations.

User Guide Reference: ETL Extract Transform Load -> ETL Map Lookups

What’s new​

A new toggle is available on Scoping Rules Configuration for Connected Journey rules:

• Separate journey per matching product
  • Off (default): Current behaviour is unchanged. All products matching the rule are grouped into one connected journey
  • On: When the Product Journey Launchpad task is triggered, the platform creates a separate connected journey for each individual product that matches the rule

Why this matters​

Previously, connected journeys were always grouped per matching rule, which is efficient for region or product-family rollups. This enhancement supports scenarios where each product must follow its own parallel process from launch, even when scoping characteristics are shared.

How it works​

• The toggle is available only for Product Scoping Rules of type Connected Journey.
• The toggle does not apply to Product Scoping Rules of type Task Display.
• Behaviour is evaluated when the Product Journey Launchpad task runs and evaluates products against Connected Journey Product Scoping Rules.

Versioning and backwards compatibility​

• The toggle is Off by default for:
  • new rules
  • new versions of existing rules
• The toggle is also visible in read-only views of historical published versions created before this release (for consistency and auditability).

Permissions​

No new permissions are introduced. Viewing and editing this toggle is governed by existing permissions for creating and editing Product Scoping Rules.

User and Configuration Guide Reference​

Product Enablement User Guide - Product Connected Journeys

This release enables you to:

• Add a Product Journey Checkpoint task to a Journey Schema in Journey Builder.
• Pause a parent journey until all connected product journeys launched from the same parent are finalised.
• View the set of launched connected journeys directly within the checkpoint task and navigate to them (subject to existing access permissions).

Configuration rules and validation​

• A Journey Schema can contain only one Product Journey Launchpad task.
• A Product Journey Checkpoint task can be added only to a Journey Schema that contains a Product Journey Launchpad task.
• The checkpoint must be placed in a sequential stage and process that occurs after the stage containing the Launchpad task.
• If a user attempts to save a Journey Schema that violates these placement rules, the save fails and an error toast is displayed:
  • Product Journey Checkpoint must be placed in a sequential stage and process that comes after the Product Journey Launchpad task
  • The invalid journey elements are highlighted in red.

Runtime behaviour​

When the Product Journey Checkpoint task becomes active, it identifies all connected journeys launched by the Product Journey Launchpad task from the same parent journey and displays them in a table with the following columns:

• Journey (the Product Scoping Rule name that triggered the connected journey)
• Name (the connected journey instance name; hyperlink to open, subject to permissions)
• Journey Status
• Application Status
• Started

Completion logic​

• The Complete button is disabled by default.
• The Complete button is enabled only when all listed connected journeys have a Journey Status of Complete or Cancelled.

Funds with status Pending Offboarding are still returned in search results and may be linked as normal.

Where an Investment Account is already linked to a Fund that subsequently becomes Offboarded, the existing link is preserved. A warning message is displayed above the Fund grid to notify the user that the linked Fund has been offboarded.

User Guide Reference: Investment Account Management

User Guide Reference: Investment Account Management Guide

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

• Dynamic Product Access Layers: Re-evaluates and applies rule-based access control for Products. Where Products satisfy a Dyanmic Access Layer rule with 'Product' data type, the associated Access Layers will be assigned. If no rules are met by a product or if the toggle is disabled in the ETL project, then default access layers (Enterprise and Global) will be applied.

User Guide Reference: ETL Extract Transform Load -> ETL Post Processing

User Guide Reference: Access Management Guide

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.

User Guide Reference: ETL Extract Transform Load -> ETL Post Processing

User Guide Reference: ETL Extract Transform Load -> ETL Virtual Documents

User Guide Reference: Configuring Screening

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

Key Details​

• Data Protection Regimes now include an optional Conditional Retention Durations section alongside the existing default retention duration.
• Conditional retention rules use the standard Logic Engine pattern with Main Entity and Main Entity Metadata data sources.
• At offboarding, conditional retention sets are evaluated in order; the first matching set determines the applied retention period, otherwise the default applies.
• The applied retention selection is stored on the Data Deletion Process, including new properties to support audit of the returned retention period:
  • dataProtectionRegimeId
  • conditionalRetentionDescription (when a conditional set was applied)
  • appliedConditions (Logic Engine conditions from a satisfied condition set are capstored as JSON text).
• Advanced Reporting has been extended to expose these additional Data Deletion Process properties via the Data Protection reporting table.

Implications​

• Existing Data Protection Regimes continue to behave as before where no conditional retention durations are configured.
• Offboarding outcomes are more auditable: the applied regime, retention period, and (where relevant) the evaluated conditions are captured for review and reporting.

User Guide Reference​

• Data Protection User Guide – Data Protection Regimes and Offboarding

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

User Guide Reference: Investment Account Management Guide

User Guide Reference: Investment Account Management Guide

Key Details​

• We've added the partial deletion of data as an event trigger to re-evaluate against Dynamic Access Layer rules for 'Entity' Access Layers.

User Guide Reference​

• Access Management User Guide – Events Applicable for Dynamic Assignment of Access Layers

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.

User Guide Reference: Creating Reviews with ETL Migration

User Guide Reference: KYRA:Screen

User Guide Reference: Document Management ->Managing Documents

When the Automatic Re-onboarding Toggle is disabled, re-onboarding continues to require users to explicitly select the jurisdictions they intend to re-onboard on the Journey Launchpad; only selected jurisdictions return to scope. To make this clearer, the Re-onboarding Journey Hub now displays messaging when scoping criteria are met for a jurisdiction that was not selected for re-onboarding.

When the Automatic Reonboarding Toggle is enabled, partially offboarded jurisdictions automatically return to scope once their trigger conditions are met again, while fully offboarded jurisdictions still require a Re-onboarding Journey to reapply the client chip and re-evaluate policy scoping. Data deletion schedules will be paused while an offboarded jurisdiction is being reonboarded.

User Guide Reference: Entity Profile->"Documents" Component

Screening results for each alias are consolidated under a single legal entity, with clear traceability of which name triggered each match. This enhancement reduces manual overhead, improves screening coverage, and increases transparency by removing the need to submit and reconcile multiple screening requests for the same entity.

User Guide Reference: Alias Screening

• User Guide Reference: Advanced reporting in Fenergo

• User Guide Reference: eSignature Guide

User Guide Reference: Related Party Management Related Party Adaptive Experience

User Guide Reference: Digital Subscriptions User Guide

Configuration Guide Reference: Digital Subscriptions Configuration Guide

User Guide Reference: Digital Subscriptions User Guide

Configuration Guide Reference: Digital Subscriptions Configuration Guide

User Guide Reference: Digital Subscriptions User Guide

Configuration Guide Reference: Digital Subscriptions Configuration Guide

User Guide Reference: Digital Subscriptions User Guide

Configuration Guide Reference: Digital Subscriptions Configuration Guide

User Guide Reference: Digital Subscriptions User Guide

Configuration Guide Reference: Digital Subscriptions Configuration Guide

User Guide Reference: Digital Subscriptions User Guide

Configuration Guide Reference: Digital Subscriptions Configuration Guide

User Guide Reference: Digital Subscriptions User Guide

Configuration Guide Reference: [Digital Subscriptions Configuration Guide](/docs/user-guides/ 3-other-clm-documentation/34-digital-subscriptions/2-digital-subscriptions-configuration-guide.md)

User Guide Reference: KYRA:Source

User Guide Reference: KYRA:Source

User Guide Reference: Investment Account Management Guide

User Guide Reference: KYRA:Source

User Guide Reference: ETL Extract Transform Load -> ETL Entity Documents

User Guide Reference: External Data Configuration User Guide: Ongoing Data Monitoring.

Autocompletion is optional and controlled through Central Agent Configuration, ensuring tasks can remain manual where review is required.

User Guide Reference: KYRA:Signal

By embedding our Extract Transform Load (ETL) capabilities directly into Agency Requests, customers can process high-volume agency onboarding while still using the standard Agency data model, connected journeys and policy-driven validation.

This release enables you to:

• Use Agency ETL task to bulk upload Underlying Principals, Managed Relationships and Products for high volume Agency Requests (up to 1,000 Underlying Principals and 5,000 Products per journey).
• Leverage powerful ETL capabilities, so you are not tied to a single file structure and can preview and validate your data before it's loaded:
  • Upload CSV files per data type and Data Group.
  • Filter data to target specific subsets of larger files.
  • Map System Fields and Policy / Product Policy fields (with Automap and mapping memory).
  • Map non-aligned values to Fenergo lookups using Map Lookups.
  • Use Preview and Validation, including date handling via Date Parse.
• Reduce duplication through a configurable Duplicate Search step for Underlying Principals:
• Upgrade your existing Agency Request Journey. This task is used in place of the existing UI tasks. You can simply update your existing Agency Request Journey by replacing the existing UI tasks (Add Parties to Request and Agency Request Details) with the Agency ETL task. If you want retain a journey for low volume processing, we recommend using different journey types so that users can easily pick the experience they want.

User and Configuration Guide Reference:

• Agency Bulk Upload

• User Guide Reference: Change Management Guide

It replaces email-based reviews with an auditable, collaborative task that supports threaded comments, configurable approval options, and data comparison views.

User Guide Reference: Review & Approvals

This improvement ensures that users are only required to provide data where necessary, streamlining the migration process and reducing confusion when optional datagroups appear without data. Mandatory datagroups must be fulfilled before progressing, while non-mandatory datagroups no longer block workflow completion.

User Guide Reference: Mandatory vs Non-Mandatory Data Groups

This ensures product visibility is governed independently of the owning Entity, providing stronger information barriers and more precise access control across all product-related features.

This release enables you to:

• Control visibility of product records using Product Access Layers
• Restrict visibility of specific product fields using Product Field Access Layers
• Automatically assign Product Access Layers using Dynamic Access Layer Rules
• Enforce access consistently across:
  • Manage Products
  • Agency Request Details
  • Entity Profile Page (Product, Managed Products, Underlying Principals, Audit – Product)
  • Proposed Changes and Conflict Resolution
  • Product Query APIs
  • Advanced Reporting

User and Configuration Guide Reference:

• Access Management – Product & Product Field Access Layers

User Guide Reference: ETL UI - Map Lookups

Managing configuration across multiple tenants can be challenging when relying on manual, ad-hoc imports. Configuration Release Hub introduces a modern, centralised mechanism for creating, versioning and deploying configuration, enabling clients to maintain configuration in a single source tenant (typically Dev) and promote versioned snapshots to higher environments through controlled, repeatable processes.

Using Configuration Bundles, customers can group related configuration changes into publishable versions that are safely stored and imported via API. This ensures consistent deployment across UAT, Pre-Prod and Prod, supports stronger governance, and aligns configuration management with standard SDLC and CI/CD practices.
This enables predictable, auditable configuration promotion and reduces risk by eliminating uncontrolled tenant-to-tenant changes.

This Beta release enables you to:

• Maintain all configuration centrally in a designated source tenant (e.g., Dev)
• Create Configuration Bundles and publish versioned snapshots of configuration
• Automatically calculate and validate required dependencies
• Promote configuration to higher environments exclusively via API, enabling CI/CD automation
• Track import progress with per-item results and access detailed logs for troubleshooting
• Improve governance by decoupling configuration creation from configuration deployment

Current Beta Limitations:

• Supported Domains and Configuration Types are limited (expanding incrementally)

• Bundles cannot be deleted or cloned

• Removing items from a bundle is single-select only

• No UI for initiating imports or viewing import history (API only)

• User and Configuration Guide Reference: Configuration Release Hub – Functional User Guide

User Guide Reference: KYRA:Screen

User Guide Reference: LexisNexis Configuration Guide

User Guide Reference: Document Management ->Document Deferral

User Guide Reference: Journey Launch Controls Per Team

Key Improvements​

• Aligned User Experience
  The Related Party modal within the Investment Account task now follows the same layout, flow, and interaction pattern as the standard Related Party capture task.
  This provides a familiar, streamlined experience for users performing related party capture across different task types.

• Simplified Search and Link Process
  Users can perform a search using minimal input, a search is permitted when at least one field in the Related Party Basic Details panel is populated.
  Search results are displayed inline within the modal, enabling users to immediately review and either link an existing entity or create a new one.

• Consistent Validation and Save Logic
  Mandatory validations are enforced at the point of saving. The relationship between the investment account and the related party is only created when the user selects Save.

Impact​

• The behaviour and layout of the Related Party modal in the Investment Account task are now consistent with the standard Related Party capture process.
• This optimisation improves usability and reduces training overhead by providing a single, unified approach to capturing related party data across Fenergo tasks.
• Relationships captured within the Investment Account task remain specific to that account and do not trigger global related party verification.

Documentation References​

• Investment Account Management User Guide

User Guide Reference: Review Manager User Guide

If colours not configured, system default applies.

User Guide Reference: Working with Risk Functionality

• Individuals: SSN, Driver’s License
• Companies: EIN

These must be enabled in the LexisNexis Secondary Identifier Configuration in order to use them. For LexisNexis Ongoing Screening (OGS), the Batch Formats configured in Bridger must be updated to include these secondary identifiers for it to be sent and used in OGS. The updated Batch Format files can be downloaded from the User Guide.

User Guide Reference: Configuring LexisNexis

This enhancement is available without configuration changes, but it does not apply retroactively to tasks completed before this date. To access the updated view, the task must be re-run.

User Guide Reference: Working with Related Party Risk

When toggled on, the system will insert this text into the legalEntityName field for Managed Relationships that are in scope for an Agency Request journey and currently have no name (new or existing). This text can be overwritten if you have configured the Agency Request Details or Managed Relationship Details tasks to include the legalEntityName data requirement for MR's.

The toggle to enable this is found on the Add Parties to Request task (where MRs are created).

User Guide Reference: Agency User Guide (Configuring Agency Requests)

User Guide Reference: Change Management user guide (Conflict Resolution Review)

User Guide Reference: Related Party Management Related Party Adaptive Experience

User Guide Reference: Investment Account Management Guide & Access Management Guide

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

Key Details​

• KYRA:Screen: Automates screening hit resolution with configurable autonomy (manual, semi, full).
• KYRA:Source: Retrieves and enriches data/documents from third-party providers.
• KYRA:Complete: Autocompletes Data, Document, and Related Parties tasks, based on all necessary information already being captured.
• KYRA:Signal: Evaluates the significance of data changes using AI.
• KYRA:Docs: 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​

1. Begin with semi-autonomous mode to maintain human oversight while measuring automation impact.
2. Gradually increase autonomy as confidence grows and outcomes align with risk appetite.
3. Review detailed user guides to understand configuration, autonomy modes, and dashboards.
4. Validate configurations in lower environments before enabling in production.

User Guide References​

• KYRA Digital Agents – Introduction
• KYRA:Screen User Guide
• KYRA:Source User Guide
• KYRA:Complete User Guide
• KYRA:Signal User Guide
• KYRA:Docs User Guide

User Guide Reference: ETL Extract Transform Load -> ETL Products

User Guide Reference: Journey Management Related Party ID&V validation

User Guide Reference: External Data Functional Configuration Guide: Mapping Tool Operation.

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

User Guide Reference: Journey Management Related Party Launchpad v2 Scoping Rules

User Guide Reference: Alias Screening

User Guide Reference: Advanced Reporting

User Guide Reference: ETL Extract Transform Load -> ETL - UI

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

User Guide Reference: ETL Extract Transform Load -> ETL Investment and Bank Accounts

User Guide Reference: Document Management ->Document Management V2 -> Preventing persistence of Expired Documents Document Management ->Document Management V2 -> Preventing persistence of Expired Documents

User Guide Reference: Using Related Party Management User Guide > Related Party Management

• Developer Hub: Rate Limiting Events

User Guide Reference: ISDA Amend

User Guide Reference: Document Management -> Configurable Metadata Columns in Document Requirements Grid

User Guide Reference: Configuring LexisNexis

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

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

User Guide Reference: Configuring Risk Functionality -> Risk Configuration in Journey Builder

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

User Guide Reference: Document Management -> Document Assignment

User Guide Reference: Working With Risk Functionality -> Using The Bank Account Risk Assessment Task

• Configuration Guide Reference: Configuring Risk Functionality -> Configuring The Bank Account Risk Assessment Task

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

User Guide Reference: KYRA:Docs -> Hierarchy Extraction

User Guide Reference: ETL Extract Transform Load User Guide for Products

You can now build sophisticated rules using data from the Investment Manager, the Underlying Principal, and associated Products to determine precisely when reliance is appropriate. This allows you to fully automate the application of your organisation's specific KYC Reliance policy, dynamically triggering KYC due diligence activities based on the outcome of your rules.

This achieved with 3 new data sources that are available in Product domain:

• Current Product Metadata (is this an agency Product where KYC Reliance should be assessed)
• Related Investment Managr (does the IM assocated with the Product meet the conditions for KYC Reliance)
• Related UP Owner (if applicable, does the product owner (UP) meet the conditions for KYC Reliance)

User Guide Reference: Agency User Guide (Agency Request)

User Guide Reference: Agency User Guide (Configuring Agency Requests)

User Guide Reference: ETL Extract Transform Load User Guide

User Guide Reference: ETL Extract Transform Load User Guide for Associations

• Configure task messaging and required actions to align with your brand and process needs.
• Review identity verification results, such as document checks, face match, and liveness-directly within Fenergo SaaS.
• Manage configuration consistency across environments using Config Exchange.
• Support data retention policies with automatic deletion of ID&V data upon entity offboarding

User Guide Reference: Digital ID&V

• Leverage AI to compare basic details (e.g., name, date of birth, nationality) against extracted ID document data.
• Return clear match outcomes: Full Match, Partial Match, or No Match, with field-level comparison.
• Automatically fail the verification if a Partial or No Match is detected
• Provide a similarity score to quantify how closely the captured and extracted details align

User Guide Reference: Digital ID&V

• Automatically complete ID&V tasks when all checks pass with a full match or when any check fails.
• Eliminate unnecessary manual reviews for straightforward verification outcomes.
• Maintain full process visibility with autocompleted tasks accessible in the journey view.
• Trigger follow-on actions or tasks based on outcome, supporting end-to-end workflow automation.

User Guide Reference: Digital ID&V

Users will benefit from the improved visibility into task progress. We have added 3 components to give users clearer guidance when performing Agency tasks:

• Indication when the 20-fund limit has been reached
• Adding a Product to a fund is now mandatory
• Visual status indicators to pinpoint where attention is needed

User Guide Reference: Agency User Guide (Configuring Agency Requests)

User Guide Reference: Access Management User Guide/Security Configuration

Managed Relationship entities represent the relationship between an Agent and Underlying principal. Our customers can use this entity to capture data or documents from the agent that are applicable for the associated Underlying Principal.

We've added the Managed Relationship entity association to the Related Parties card of the Underlying Principal's EPP. This allows users to navigate directly to the MR from the UP. The Entity Profile for the MR displays a sub-set of relevant tabs and is configurable via tenant Entity Profile Configuration so that it can be optimised for MR data.

User Guide Reference: Agency User Guide (Agency Request)

Users typically look for a specific Underlying Principal so that they can review their associated products. This new tab supports that workflow by displaying all Underlying Principals whose products are managed by the selected Agent. Users can:

• Use Search and filter to quickly find the Underlying Principal(s) they need
• Expand an Underlying Principal to view their products in a nested table
• Search and filter within the product table as well

This experience is configurable. Displayed columns for Underlying Principals are sourced from the ‘Indexed’ fields in the ‘Basic Details’ category of the Entity Profile. This category can be updated in the Entity Profile Configuration page for Company entities.

To ease the transition, both Agency Products and Underlying Principals tabs will be available for the next two weeks, after which the Agency Products tab will be deprecated.

User Guide Reference: Agency User Guide (Agency Request)

This approach enables you to: - Configure journeys that support Product Orchestration activities (Product specific Approvals, gather additional product data and documents, trigger activities with legal and tax teams, integrate with other systems using Integration Hub and Flow Studio) - Streamline Parent Journey activities by outsourcing product-specific or jurisdiction specific tasks to the Product Journey - Use Product Journeys to activate products as soon as their specific due-diligence threshold has been met.

• User and Configuration Guide Reference: Product Enablement User Guide - Product Connected Journeys

• Reonboarding Journeys (Partial and Full Jurisdictions)
• Update multiple inflight journeys with single event
• Products – Initial support for importing Product Data. Supports Create, Update, Delete/Offboard operations for Products. Product ID and status available in Event details via IntegrationHub. Support for Product Related Parties, Product to Product Relationships, and Product Datasources planned for a subsequent release.
• Support for Journey Level Data which allows clients to configure entity attributes that exist only in a journey and will not be verified. Useful for storing temporary data like Integration Statuses.
• Enforcing Request Validations - previously request validations were only logged in Integration Hub. Now error-severity issues will force the event to fail fast.

User Guide Reference: DataImport Overview

• Stateless Integrations - Calling system does not need to know an Entity's state in Fenergo. There is an option to provide a unique identifier (e.g. centralized MDM) if available to decide if entity should be created or updated.
• Multiple Entities per event - VerifiedImport allows for multiple entities per message.
• Lookups Resolver - Lookup values can be provided as value, id, or custom column from the reference list definition.
• Message Simplicity - External Systems need only provide incoming datakey and value. Fenergo will use internal policy configuration to determine data types and validations

User Guide Reference: DataImport Overview

• Configuration Exchange to support promoting Flows between environments
• Policy Adapter Initiators. Implement your own policy adapters like Custom Search Providers, Custom Validation Providers, and Custom Task Providers using Integration Flows
• Added a new endpoint to allow Custom Authentication schemes for API-initiated Flows for outside systems that are unable to support Fenergo's default endpoint using OAuth. Includes support for IP Whitelisting, shared secret, and HMAC authentication
• Added support for ASync flows to enable new integration patters such as HTTP Long-Polling and HTTP Callbacks (see task enhancements)
• Enhanced Schemas. Schemas can now be generated from OpenAPI specification docs and can be leveraged from Transformer code
• New and Enhanced Tasks
  • Wait - Pauses Flow Execution for a configurable amount of time (1s – 5m). Use this when polling an API until some condition met.
  • Flow Invoker - Use this to trigger another flow to run in parallel or wait for completion
  • End - Formally return response data from a Flow Execution. Used in External Data Adapter, Policy Adapter, and Flow Invoker triggered Flows
  • Supergraph - Added support for Entity-based queries
  • HTTP Invoker - Added support for Callback pattern. HTTP Task will pause the flow and wait for a callback from outside system before resuming.
  • Trasformer - Added support for schemas, encrypting/decrypting functions.

User Guide Reference: Integration Flows Overview

User Guide Reference: [Using Shared Data User Guide > Bulk Entity Management](/user-guides

User Guide Reference: Using Legal Entity Groups User Guide > Selective Journey Launching

User Guide Reference: Managing Documents -> Document Management

User Guide Reference: ETL Extract Transform Load User Guide for Associations

User Guide Reference: ETL Extract Transform Load User Guide

User Guide Reference: ETL Extract Transform Load User Guide and Configuration Exchange User Guide

User Guide Reference: Entity Profile->Entity Profile Export

• Search Connected Journeys by Entity Name
• Filter by Journey Status (i.e. 'In Progress')
• Scroll bar will automatically appear when the number of Connected Journeys Requires it.

• **User Guide Reference:*- Working with Journeys User Guide - Connected Journeys View

User Guide Reference: Agency User Guide (Agency Request)

User Guide Reference: ETL Extract Transform Load User Guide

User Guide Reference: Advanced Dashboards User Guide

User Guide Reference: Agency User Guide (Agency Request)

User Guide Reference: ETL Extract Transform Load User Guide

• User and Configuration Guide Reference: Product Enablement User Guide - Manage Products task

When disabled, Dynamic Access Layers are calculated upon Entity Draft creation, Journey Cancellation, and completion of specific journey tasks. Enabling the toggle triggers recalculation whenever an Entity Draft Update event occurs (e.g., on save). However, users who are lacking the resulting access layers could lose access to an in-progress task, so a journey's task assignments should align to the inputs collected that can result in updated access layers.

User Guide Reference: Access Management User Guide

User Guide Reference: Business Metrics User Guide - Task Metrics

User Guide Reference: ISDA Amend

User Guide Reference: Advanced Dashboards User Guide

User Guide Reference: KYRA:Docs -> Extracted Values

User Guide Reference: Using KYRA:Docs -> Managed Knowledge Base

User Guide Reference: ETL Extract Transform Load User Guide

With simple and intuitive out-of-the-box tooling, Flow Studio empowers users to design, deploy, and maintain integration workflows without the need for external middleware or complex coding. Clients can quickly develop and deploy a complete end-to-end solution faster than ever before!

User Guide Reference: Integration Flows Developer Guide

User Guide Reference: Advanced Dashboards User Guide

User Guide Reference: Screening User Guide

User Guide Reference: ETL Extract Transform Load User Guide

• Offboarding Journeys (Partial and Full)
• DataGroups – Resolve Lookup Values by ID
• Associations – Support for Custom Properties
• New behavior "ImportBehavior.DelayedCompleteTask" bypasses task validation for EventResponseParams at start of processing - when task is running in parallel and might not be available at start of event
• Bypass entity resolving and always create a new entity by providing an empty guid (00000000-0000-0000-0000-000000000000) in place of Entity.Id

User Guide Reference: DataImport Overview

• Added Association.Properties to expose custom properties in Association Records

User Guide Reference: KYRA:Signal User Guide

User Guide Reference: Credit Screening User Guide

User Guide Reference: Financial Analysis User Guide

User Guide Reference: Bulk Upload User Guide > Custom Journey Types

User Guide Reference: Conflict Resolution and Proposed Changes User Guide->Conflict Resolution Review

User Guide Reference: Conflict Resolution and Proposed Changes User Guide->Related Parties Conflicts

User Guide Reference: Financial Analysis User Guide

User Guide Reference: Financial Analysis User Guide

User Guide Reference: Financial Analysis User Guide

User Guide Reference: Financial Analysis User Guide

User Guide Reference: Financial Analysis User Guide

User Guide Reference: Permissions Catalogue

• User Guide Reference:Virtual Documents User Guide

User Guide Reference:

Document Management->Document Management V2->Configuring Document Management V2

Document Management->Using Intelligent Document Processing->Configuring Intelligent Document Processing

User Guide Reference: Document Management->Document Management V2->Configuring Document Management V2 Document Management->Using Intelligent Document Processing->Configuring Intelligent Document Processing

User Guide Reference: Configuring Legal Entities and Policy->Configuring the Legal Entity Profile Page->Common Configuration Working with Legal Entities and Policy->Using the Legal Entity Profile Page->Documents Component and Documents Tab

User Guide Reference: Configuring Legal Entities and Policy->Configuring the Legal Entity Profile Page->Common Configuration Working with Legal Entities and Policy->Using the Legal Entity Profile Page->Documents Component and Documents Tab

User Guide Reference: Document Generation User Guide

User Guide Reference: Document Generation User Guide

User Guide Reference: Document Generation User Guide

User Guide Reference: Document Generation User Guide

• JourneyInstance.relatedEntityDrafts lists Entity Drafts of Related Parties created by the Association Task for a given Journey. By default the Main / Lead entityDraft of the journey is excluded from the list but can be overridden by setting includeMainDraft = true in query

• EntityDraft.draftProperties makes Journey-scoped data available in schema

User Guide Reference: Supergraph Developer Guide

• User and Configuration Guide Reference: Product Risk Assessment Configuration Guide

Further we've introduced the 'Current Product' source for Logic Engine conditions configured Trigger Conditions or Conditional Values. This source allows conditional behaviors to be driven based on product requirements in the product the datagroup is linked to.

User Guide Reference: Data Group User Guide

User Guide Reference: Advanced Dashboards User Guide