Skip to main content

How Do I Run and Manage Checks?

Checks are the verification tasks that run against each entity in a case. Some run automatically when a case is created. Others require manual action or document uploads. This guide covers how to view, manage, and take action on checks.

What you’ll learn

  • How to view check requirements for an entity
  • What each check status means
  • How to trigger a manual re-run
  • How to waive a check with a documented reason
  • How reused checks work
  • What happens when a check fails

How do I view checks for an entity?

Open a case and click on any entity in the entity panel. The Requirements section shows all checks and documents for that entity in a grouped list:
SectionWhat it shows
IdentityID verification, biometric match, address verification
ScreeningPEP/sanctions, adverse media, watchlist checks
CompanyRegistry lookup, credit check (for company entities)
FinancialSource of wealth, transaction monitoring
EDDEnhanced due diligence checks (only shown when EDD is required)
DocumentsRequired document uploads (Certificate of Incorporation, proof of address, etc.)
Each check shows:
  • Check name — e.g., “PEP/Sanctions Screening”
  • Status badge — color-coded (green for Complete, blue for In Progress, grey for Pending, red for Failed)
  • Result — Pass, Refer, or Fail (once complete)
  • Provider — which service ran the check (e.g., WorldCheck, Kyckr)
  • Date — when the check was completed or last updated

What does each status mean?

StatusColorMeaningAvailable actions
PendingGreyNot yet startedRun, Waive
QueuedBlueWaiting to be processedView
In ProgressBlueCurrently executingView
Awaiting ClientOrangeCustomer needs to take action (e.g., complete identity verification at a URL)View, Cancel
Awaiting DocumentOrangeWaiting for a document uploadUpload, Waive
CompleteGreen/RedFinished with a result (Pass, Refer, or Fail)View Results
FailedRedTechnical failure after retriesRetry, Waive
WaivedGreySkipped with a documented reasonView reason
ReusedPurpleResult carried over from a valid previous checkView source
CancelledGreyNo longer needed

How do I run a check manually?

Most API checks run automatically when a case is created. But you may need to trigger a manual run in these situations:
1

Find the check

Open the entity’s requirements panel and locate the check you want to run.
2

Click Run

Click the Run button next to the check. This is only available for checks in Pending or Failed status.
3

Wait for results

The check moves to In Progress. For API checks, results typically arrive within 10-30 seconds. The status updates automatically — no need to refresh.For checks that require customer action (like identity verification), the status changes to Awaiting Client and a verification URL is generated.
4

Review the result

When the check completes, it shows a result:
  • Pass — no issues found
  • Refer — issues found that need review (an alert is generated)
  • Fail — the check could not be completed successfully
If the result is Refer or Fail, an alert is automatically created and appears in the alert queue.

How do I waive a check?

Sometimes a check is not applicable and should be skipped. For example, a source of wealth check may not be required for low-risk entities, or a document may be available through other means.
  1. Click Waive next to the check
  2. Enter a reason explaining why the check is being waived
  3. Select the reviewer who approved the waiver (for audit purposes)
  4. Click Confirm
Waivers are logged in the audit trail. Every waiver must have a documented reason. Compliance auditors will review waivers during regulatory examinations.

How do reused checks work?

When a new case is created for an entity that was recently verified, the system checks for existing valid results:
  • Validity period — each check type has a validity window (e.g., identity checks are valid for 365 days, screening for 90 days)
  • Reuse criteria — the previous check must be Complete with a Pass result and within its validity period
  • Display — reused checks show a purple “Reused” badge, the original check date, and a link to the source case
Reused checks save time and reduce costs by avoiding redundant provider API calls.
Reused checks are read-only. If you need a fresh result for a reused check, click Run New Check to create a new check that calls the provider again.

What happens when a check fails?

Technical failures (provider timeout, API error, network issue) are handled automatically:
  1. The system retries up to 3 times with increasing delays
  2. If all retries fail, the check status changes to Failed with an error message
  3. An API Failure alert may be generated depending on configuration
  4. You can manually Retry the check or Waive it if the failure is not recoverable

What’s next?