​

Check Orchestration

The check framework automatically creates, executes, and tracks verification requirements for each entity in a case. Checks are the system’s way of verifying facts about a person or company through external providers.

​

How checks are created

When a case entity is created (either through the API or as part of case creation), the orchestration service automatically:

1. Reads the verification type configuration for the entity type and role
2. Filters by due diligence level (CDD vs EDD)
3. Creates the appropriate records based on execution method

​

Check types and categories

​

Execution modes

Checks execute in one of three modes depending on the provider configuration:

​

Check status lifecycle

​

Check results

Every completed check produces one of three results:

​

Check reuse (Verify Once, Reference Many)

When a new case creates checks for an entity that has already been verified, the system evaluates existing checks for reuse:

1. Look up completed, passing checks for the same entity and check type
2. Verify the check has not expired (based on validity period)
3. If valid, create a Reused check referencing the original

This avoids redundant provider calls while maintaining full audit provenance.

​

Alert generation

Checks that return Refer or Fail automatically generate alerts:

​

Next steps

• Alert Management. How generated alerts are triaged and resolved.
• Entity Lifecycle. How entity roles drive check requirements.
• Checks Data Model. Full field reference for check resources.