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.
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.
Previous topic Data model Next topic Supporting infrastructure