Due Diligence¶

Permissions¶

Compliance Officer	Advanced User	Standard User	Data Entry Operator	Billing Officer	Auditor

Standard User Permissions

Whilst Compliance Officers, Advanced Users and Standard Users can perform due diligence and risk level assessments, Standard Users are able to assess and make due diligence decisions on scan results performed by themselves.

Recording Due Diligence and Risk Level Assessments¶

You can record due diligence decisions, add notes and risk level assessments against matched profiles for both individual and corporate entities scanned for your organisation. This process is integrated into the screening process and is accessible via Individual Scan > Scan Results and Corporate Scan > Scan Results.

If you have included a unique reference Client ID during screening, you will see a button for the Decision (Risk) and Comment beneath the profile image.

By default, all results are flagged as Not Reviewed until a decision is applied. The options available are as follows:

Status	Icon	Description
Not Reviewed		Default status until a decision is applied. The number in the box indicates the number of matches for the individual or company entity which are not reviewed.
Match		The number in the box indicates the number of matches for the entity which are recorded as match.
Unsure		The number in the box indicates the number of matches for the entity which are recorded as unsure.
No Match		The number in the box indicates the number of matches for the entity which are recorded as no match.
High		Indicates at least 1 recorded high risk level profile. Risk level applies to Matched and Not Sure decisions only.
Medium		Indicates at least 1 recorded medium risk level profile. Risk level applies to Matched and Not Sure decisions only.
Low		Indicates at least 1 recorded low risk level profile. Risk level applies to Matched and Not Sure decisions only.

Understanding the Due Diligence Summary¶

Example of an individual scan which resulted in 25 matching profiles and all matching profiles have not yet been reviewed:

Before due diligence:

After due diligence:

On completion of due diligence, this was found that 23 profiles are not true matches, 1 profile cannot be certain of a match and 1 matched profile. The assessed risk level for this individual is considered low risk:

Add Due Diligence Decisions to Matched Profiles¶

Due diligence decisions, risk level assessments and comments can be applied to a single profile or multiple profiles at once.

You can also replace with a new decision against the profile by adding a new match decision. A history of the decisions will be retained for auditing purposes.

If your organisation has predefined risk levels set, the associated risk levels are displayed as a guideline with a recommended risk score. You may elect the risk level based on your own risk assessment.

The Compliance Officer can define the risk levels for the categories and subcategories within the Organisation administration screens. Refer to Risk Settings for details.

Overriding an ID Verification Outcome¶

An ID Verification outcome is a due diligence decision of its own. You can override any outcome to Verified or Not Verified and record why. This is most common on a Review Required result, where glare or an unclear image capture prevents a confident read and you can confirm the details yourself.

To record an override, open the scan result from Individual Scan > Scan Results and click the verification outcome. The Override Verification Outcome panel opens.

You can revert any applied decisions through the Remove Override option.

Fields	Description
Provider Result	The outcome as it was first returned. An override never changes it. Where the scan covers both checks, the original ID Check and FaceMatch results are shown side by side.
Shown on the scan today	The outcome the scan carries now. It appears beside Provider Result once an override exists. Where the scan covers both checks, the current ID Check and FaceMatch outcomes are shown side by side.
Override Verification Outcome	Select `Verified` or `Not Verified` to record an override, or `Remove Override` to remove the current override so the original outcome applies again. An option that would not change anything is unavailable, and the panel gives the reason. `Remove Override` is unavailable until an override exists. A value the verification already carries is unavailable, because there is nothing to override.
Add Comment	Your reason for the action, up to 200 characters. A comment is required on every action.
Override History	Every action against the verification, in order, with the User, the Date, the value Before, the value After and the Comment. The entries cannot be removed or edited. Where the scan covers both checks, the Before and After columns each carry the ID Check value and the FaceMatch value together.

Points to note:

The override replaces the outcome everywhere a single verification outcome is shown. This includes the Scan Results list, the Data Management list, the scan result, the reports, the exports and the API. It is marked (Overridden), so it is never mistaken for the original outcome.
Where the scan covers both ID Check and FaceMatch, one override replaces both statuses, and the panel tells you so before you record it. Where the scan covers one check only, the override applies to that check.
An override must change the outcome, so a value the verification already carries is offered as unavailable rather than accepted.
The verification evidence is never altered. The ID Check detail, the FaceMatch status, and the document and liveness evidence are kept and shown exactly as received.
You can override a verification in any status, including Pending, Incomplete and Not Requested. This covers an individual who does not complete the verification and is identified another way.
Use the Override Includes filter on Scan Results to find verifications by whether the outcome was overridden.

API version

The override is available through API v3 only. A client that reads results over API v2 continues to receive the original outcome, so the value it records can differ from the outcome shown in the application. To read the override, move the integration to API v3.

Fields	Description
Provider Result	The outcome as it was first returned. An override never changes it. Where the scan covers both checks, the original ID Check and FaceMatch results are shown side by side.
Shown on the scan today	The outcome the scan carries now. It appears beside Provider Result once an override exists. Where the scan covers both checks, the current ID Check and FaceMatch outcomes are shown side by side.
Override Verification Outcome	Select `Verified` or `Not Verified` to record an override, or `Remove Override` to remove the current override so the original outcome applies again. An option that would not change anything is unavailable, and the panel gives the reason. `Remove Override` is unavailable until an override exists. A value the verification already carries is unavailable, because there is nothing to override.
Add Comment	Your reason for the action, up to 200 characters. A comment is required on every action.
Override History	Every action against the verification, in order, with the User, the Date, the value Before, the value After and the Comment. The entries cannot be removed or edited. Where the scan covers both checks, the Before and After columns each carry the ID Check value and the FaceMatch value together.