Relationship visualizer

The relationship visualizer shows an intuitive graphical representation of the entire relationship network with the contracting party at the center of the view. The visualizer presents all the information like type and direction of relationship, aggregated ownership percentage, and others that a user needs to understand and investigate relationships that a contracting party may have.

Related parties grid and actions

The related parties grid presents a quick yet detailed summary of all the related parties associated with the customer and key attributes of the relationship such as type of relationship, KYC significance, controlling nature, percentage of ownership, and status of the related party.

The grid is also a central location form where you can add, update, or delete the related parties. The intelligent background processing supplements each of the actions that, among many other tasks, perform the key functions of aggregating the attributes and building the relationship network by bringing in or deleting from the case all the indirect parties that a particular related party implies.

The related party’s grid is available throughout the Capture, Enrich, and Due Diligence stages through the Action menu. You can add or update the related parties in any stages that are mentioned above, and the system makes necessary adjustments to the due diligence processes as required.

Case orchestration

All the related party cases, direct or indirect, are direct subcases to the main due diligence case for the contracting party.

Based on the roles, direction of relationship, and aggregated or derived attributes such as Risk, AML CDD Profile, KYC Significance, and Controlling flags, related parties must undergo various levels of due diligence. The application does not just handle and maintain the due diligence on the related parties that are added upfront but also adapts to the slightest change that might happen during the due diligence phase and reacts by updating or lowering the level of due diligence or even withdrawing the due diligence cases when they are no longer required.

For example, as the system evaluates the due diligence cases for the related parties, the cases may increase the risk of the contracting party, which, at run time, affects the due diligence levels for all the related parties. In another scenario, a change in the related party data through the related party’s grid could render the related party non-KYC Significant, in which case the corresponding due diligence case shall be withdrawn.