The assessment status and flag

• In progress:

  Assessments get this status as soon as onboarding begins, and they keep it until the entity either passes or fails the assessment. During this time, the entity is undergoing due diligence. A series of due diligence tasks are created, for example, to verify the entity's identity or bank account, which will need to be passed for the assessment to pass.

• Failed:

  If the entity fails the assessment, this typically marks the end of the assessment lifecycle; however, it is possible to manually revert the decision.

• In review:

  Assessments are in review if, at any time, the entity no longer meets the requirements of a due diligence task or if a new task is added to the assessment. Assessments that are in review need to have their incomplete tasks passed before they can be passed again and return to the Passed stage.

• Passed:

  These assessments have passed the onboarding process and are now in ongoing monitoring. If the entity data changes so that the entity no longer meets the requirements of a due diligence task, or if a task expires, the assessment moves to In review.

• Canceled:

  Assessments that are in review can be manually canceled when the entity doesn't pass the incomplete tasks. You can also cancel assessments that have passed. Assessments that are In progress can only be Passed or Failed, as shown in this lifecycle diagram:

  

Calculating risk and Requires risk score are only used if you're using risk. Contact our Client Service team to learn more.

The possible assessment flags are listed here. Only one flag is displayed for an assessment. If multiple flags apply, the first applicable flag in this list is displayed:

• Automating:

  The workflow is being applied. New tasks or task versions are being created for the assessment. Any checks configured to run automatically are being run. Although manual action can be taken at this time, no manual action is required right now.

• Calculating risk:

  The assessment’s total risk score is being calculated by checking the entity’s details against the risk factor rules in the assessment’s risk model. No manual action is required at this time.

• Requires risk score:

  Entity data is needed to calculate the score for a required risk factor. For the assessment to progress, the missing entity data must be added to the entity. Note that if you're using our new smart policies, this state only occurs if the assessment reaches a workflow branch that uses the risk score or risk level property and the risk model could not calculate a risk score or level for the assessment.

• Requires data:

  The workflow doesn't have the data required to choose its next branch. For example, if the branch rule is "Is the country of address one of 'United Kingdom' or 'Canada'?", the assessment will have this state if the entity doesn't have a country of address. Note that this state is only used if you're using the new smart policies.

• External response required:

  An external party must provide more information or upload a document to run a check. This can happen during an external information request, which is used to send an email request directly from the entity, or during registration flows, which are used to gather information at the beginning of the entity's journey.

  • Waiting for associate response: More information or documentation about an associate must be provided.

• Waiting for checks:

  A manually run check is being performed. Although other manual actions can be taken at this time, no action is required right now. Note that if the workflow is running checks automatically, the assessment is Automating instead.

  • Waiting for checks (associate): A manually run check on an associate is being performed.

• Needs manual completion:

  All automatic checks have been run by the workflow, but one or more tasks are incomplete or failed. For the assessment to progress, the incomplete tasks must be completed manually or the assessment must be failed manually.

• Waiting on escalations:

  One or more escalation teams need to approve the escalation before the assessment can be passed manually. Note that assessments with escalations cannot be passed automatically by the workflow.

• Ready for decision:

  All tasks are passed and the assessment is ready to be passed. For the assessment to progress, it must be passed manually.

• Decided:

  The assessment is currently passed, failed, or canceled. No manual action is required at this time. If the assessment has been passed, ongoing monitoring is taking place.

• Nearing expiry:

  The assessment is currently passed but has at least one task version that's due to expire in 30 days or less.