TABLE OF CONTENTS


What are automation rules?

Automation Rules are conditions that, when met, trigger an action in your workflow. Examples include:

  • Running an individual verification as soon as all required details are entered

  • Automatically screening an entity when a case is created

  • Sending out a client risk assessment when a case is submitted


These rules work alongside your compliance rules, so make sure your compliance setup supports the automations you want to use.



Billing impact of automation rules

Any verification, screening, or report triggered by Automation Rules will count towards billing, exactly as if you had run the check manually. Keep this in mind when setting up rules that may apply to large case volumes.


Available Automations

Below is the full list of automations you can configure:

  1. Run individual verification check: Runs the verification check when all required fields for the individual are completed. 

  2. Send verification form: Sends the Electronic Identity Verification (EIV) form when specified conditions are met.

  3. Send risk assessment: Sends either the client or matter risk assessment once the case is submitted. 

  4. Run entity screening check: Triggers the screening of an entity. (Ensure screening requirements are added manually or via compliance rules.)

  5. Run company credit check: Runs a company credit check. (Requires the Company credit check requirement to be added via compliance rules.)

  6. Auto-unwrap entities - Automatically unwrap the company to a certain layer.
  7. Change case status (to Ready for Review or Completed): Moves the case to ‘Ready for Review’ or 'Completed' once all requirements are completed and all individuals/entities are marked as Pass or Not Needed.

  8. Auto review case: Moves the case to Completed when a user marks the case as Ready for Review.




How to create an automation rule

Follow these steps to create an automation:

  1. Go to Settings > Manifest > Automation Rules.
  2. Click +Add Rule.
  3. Give your automation a Name. e.g. “Auto-run screening for API cases”
  4. Select the Automation you want to set up.
  5. Under When, add conditions for when the automation should trigger. You can layer multiple conditions to build more complex rules.
  6. (Optional) Add exceptions under Except when to prevent the automation from running in certain scenarios.
  7. Click Save. Your automation will now run whenever the conditions are met.



Understanding 'When' and 'Except when' conditions


Case risk level is one of: 

  • Low 
  • Medium 
  • High 

Case risk level is based on the Matter risk assessment outcome OR the 'Case risk assessment' input within via the 'Case details' tab of the relevant case. 


Case source is one of: 

  • Web 
  • API 


CDD level is one of:

  • Simplified
  • Standard
  • Enhanced 


CDD level is set via the Case details tab within the relevant case. 


Entity client risk is one of:

  • Low
  • Medium
  • High


Entity client risk is based on the outcome of the Client risk assessment within the relevant case. 


Entity is registered in:

  • Choose from our drop down country list or 'Select all'


Based on the 'Registered country' field within 'Entity details'.  


Entity property is one of:

  • Non-beneficially held  

The 'non-beneficially held' tag is automatically applied to certain entities during the 'unwrap' process if the entity is holding shares on behalf of another person or entity. This applies only to entities which have specified this arrangement with the relevant register.  


Entity type is one of:

  • Choose from our drop down entity list or 'Select all' 
  • Determine whether the rule should run based on 'Any' or 'All' entities within the case 

    • ANY: The automation runs if any of entities in the case meet the condition (e.g. case includes a private company) 

    • ALL: The automation runs only if all of the entities in the case meet the condition (e.g. all entities in the case are private companies) 


Entity type is set via the 'Entity type' field within the Entity details. 



Entity verification result is one of:

  • Adverse media is a match
  • Sanction screening is a match
  • Warning screening is a match 
  • Fitness & probity screening is a match 
  • Determine whether the rule should run based on 

    • ANY: The automation runs if any of entities in the case meet the condition (e.g. case includes a private company)

    • ALL: The automation runs only if all of the entities in the case meet the condition (e.g. all entities in the case are private companies)


Entity verification result is based on the outcome of an entity screening check. 



Individual client risk is one of: 

  • Low 
  • Medium
  • High


Individual client risk is set via the outcome of the Client risk assessment within the relevant case. 


Individual verification result is one of: 


  • Address check is fail
  • Adverse media screening is match 
  • Anti-tampering result is fail
  • Anti-tampering result is warning
  • Biometric result is fail
  • Biometric result is warning
  • DOB check is fail
  • Fitness & probity screening is match
  • Government ID check is fail
  • Name check is fail
  • PEP screening is match
  • Sanction screening is match
  • Warning screening is match

Individual verification result is based on the outcome of the verification check. This is triggered by either the completion of the EIV form or by clicking 'run checks' within the personal details. 


Office is one of: 

  • Choose from the drop down office list or 'Select all' 

This is based on the office selected during case-submission, or can be updated manually through the 'Case details' tab of the relevant case. 


Registration authority is:

  • Choose either 'Canada', 'United States of America' or 'Germany' 
  • Select from the relevant registration authorities for each of the above countries
  • Determine whether the rule should run based on

    • ANY: The automation runs if any of entities in the case meet the condition (e.g. case includes a private company registered in Delaware)

    • ALL: The automation runs only if all of the entities in the case meet the condition (e.g. all entities in the case are private companies registered in Delaware)


Verification type is one of:


  • Select from the verification types your team have configured e.g. screening only, KYC (name, dob, address) etc.


Common Use Cases 

Here are some examples of how automation can streamline your workflows:

  • New case creation: Automatically run verifications and screenings when a new case is created.

  • Risk-based workflows: Send additional verifications or escalate reviews if the case risk rating increases.

  • Status updates: Automatically move low-risk cases through to Completed when all requirements are finished.

  • Auto approve: Push a case to Completed immediately after review.

  • API-specific automation: For API-submitted cases, automatically send verification forms or run checks without manual input.


Case-level logic: ANY vs ALL

When configuring case-level automations (e.g. Auto review case, Change case status), you’ll see an ANY/ALL setting:

  • ANY: The automation runs if any of the listed conditions are true.

  • ALL: The automation runs only if all conditions are true.


Example:
If you want a case to move to Ready for Review when any entity is registered in a FATF High-Risk Country, set the logic to ANY.


Troubleshooting: Why isn't my automation running?

If an automation doesn’t trigger, check the following:

  • Required fields missing: Make sure all mandatory fields are complete for verifications.

  • Requirements not linked: Confirm that screenings or reports are added via compliance rules.

  • In progress items: Automations will not run if requirements are marked In Progress. They must be Completed or Not Needed.

  • Case updates: If case details are changed after a rule runs, the automation may restart or behave differently.

  • Conditions don’t align: Review your rule’s conditions to confirm they match the case setup.

If issues persist, review the rule configuration or test with a simple condition to ensure the base automation is working.