Skip to main content

Customer statuses

In the ComPilot Dashboard, each onboarded customer has a status, as described in the following table.

note

Customers who are not yet onboarded will not have a status until all their data is submitted and checked by the ComPilot Rules Engine.

StatusDescription
ActiveCustomer has passed KYC, AML screening, and your own business rules
FailedCustomer has failed the automatic KYC for various reasons (such as blurred ID, or missing information) and has the possibility of re-onboarding after the gaps are filled
RejectedCustomer is rejected for various reasons (such as prohibited country, or positive sanctions hit) and does not have possibility of re-onboarding
To be reviewedThere is some information, such as are positive AML screening results, that need to be investigated
EscalatedA senior member of the team is involved with the investigation
DormantCustomer has not been active for six months or more
TerminatedCustomer's account has been closed and a note has been added with the reason

Customer statuses are set automatically by two sets of rules.

  • Rules that are embedded into ComPilot that function as preset decisions to help you with KYC, AML, and KYT screenings
  • Rules that you can set using the ComPilot Rules Engine.

Customer screening (through ComPilot AML or the ComplyAdvantage provider) can also set customer statuses.

The flows and decisions that are embedded into ComPilot are as follows.

  1. The customer is assessed by the KYC provider.
    • If the customer is approved
      • Risk score is not set
      • Onboarding level is set to KYC
      • Customer is assessed by the ComPilot Rules Engine
    • If the customer is not approved
      • Risk score is not modified
      • Status is set to Failed
      • Onboarding level is set to KYC
      • Processing stops here
  2. The customer is assessed by the ComPilot Rules Engine.
    • If the customer is approved
      • Risk score is set to Low
      • Status is set to Active
      • Onboarding level is set to Onboarded
      • Customer is assessed by AML screening
    • If the customer is not approved
      • Risk score is set to High
      • Status is set to Rejected
      • Onboarding level is set to Onboarded
      • Processing stops here
  3. The customer goes through AML screening
    • If there are no AML hits, there are no changes to the status, risk score, and onboarding level
    • If there are AML hits
      • Risk score is left at Low (the rules engine decision is left until a human decision is made)
      • Status is set to To be reviewed
      • Onboarding level is left at Onboarded