9 posts tagged with "Associations"

The related party duplicate search within journeys has been enhanced to support searching by data group fields such as Address Details and Tax Identifiers. Previously, users could only search using standard policy fields, requiring separate searches outside the journey to verify identity using critical identifiers. Configurators can now designate one or more data groups as part of the duplicate search scope on the Related Parties, Related Parties Data & Documents, and Hierarchy Capture task types in Journey Schema Builder. When configured, users will see additional input fields for those data groups in the search panel when adding a related party. Providing all mandatory data has been entered, users may search using only policy field values, only data group field values, or a combination of both. Matching entities are returned in the existing Potential Duplicates panel. This reduces the risk of duplicate related party creation, improves data integrity, and keeps users within the journey workflow throughout the onboarding process.

KYC Analysts will now see a warning message when the combined first-level ownership of Related Parties to a main client exceeds 100% in the hierarchy. The warning appears inline as a brief toast message when adding new related parties and as a banner at the top of the task. This applies to both the Related Parties and Hierarchy Capture task types. The warning is informational only and does not block data entry.

To allow for STP scenarios, the Related Party Data & Documents task has been enhanced to support task autocompletion configuration.

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

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

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

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

Gives users the ability to remove multiple associated entities from the Related Party hierarchy in a single action, with permission-based access, confirmation and progress modals, and changes finalised after the Verify Related Party Associations V2 task.

An update has been applied so the Related Party Scoping Rules can now be located under the Journey management menu option.

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

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

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

A new option has been introduced in the Related Parties task in Journey Builder that will allow the restriction of entity group associations to only be permitted to members of the entity group. Once enabled, the search will return results from verified members of the entity group in journey.