Skip to content
  • There are no suggestions because the search field is empty.

Alerts Definitions | spektr Helpcenter

Alerts Definitions

Understand the different alerts

Written by Yuri Beckers
Updated over 4 months agoYuri Beckers


Alert Categories and types
​

Alerts with hits


​Alert with hits
These alerts have hits, like alerts from AML service or multiple KYB hits for instance. They are triggered by a service call that return multiple hits.
​
​Sanction
There is at least one detected hit returned from an AML service about this entity being on sanctioned list.
​Can be applied to: Companies, Individuals and owners and controllers (OCs).
​

PEP
There is at least one detected hit returned from an AML service about this person being a PEP.
​Can be applied to: Individuals and owners and controllers (OCs).
​

Warning
There is at least one detected hit returned from an AML service about this entity being on warning list.
​Can be applied to: Companies, Individuals and owners and controllers (OCs).
​
​Exclusion
There is at least one detected hit returned from an AML service about this entity being on exclusion list.
​
This is fitness and probity (specific to Ireland and should be deleted from the CA checks)
​Can be applied to: Companies, Individuals and owners and controllers (OCs).
​

Adverse Media
There is at least one detected hit returned from an AML service about this entity having adverse media.
​Can be applied to: Companies, Individuals and owners and controllers (OCs).
​
​Multiple KYB hit
There are at least 2 hits detected by a KYB service, This happens when a company number is not provided and the user has to choose one out of many potential match.
​Can be applied to: Companies
​

Alert with change


​Alert with change
These alerts do not have hits, like alerts from a KYB service that find a new value for an existing field on the record. They are triggered by that comparison of two different values for the same fields (or a new fields all together)

Manual review alert


These are triggered every time the Alert step is executed and the user has defined a list of stuff that needs to be done on them.
​
​Manual review alert
This is simply an alert trigger placed on a specific path in a process for a user to review the information processed/collected so far.
​Can be applied to: Companies, Individuals and owners and controllers (OCs).


​Alert Status
​​

Open


​Definition:
This is the default status, the alert hasn’t been looked at yet.
​
​Logic for alert with hits:
- None of the hit is solved (all have “potential match” status)
- No comments written
- Hasn’t been re-assigned
​
​Logic for alert without hits:
- No comments written
- Hasn’t been re-assigned

In Progress

Definition:
The hits on the alerts are starting to be resolves, or there are comments... in short something is happening on it.
​
​Logic for alert with hits:
- At least one hit is solved (all have “potential match” status)
- Or at least one comment has been written
- And hasn’t been re-assigned


​Logic for alert without hits:
- At least one comment has been written
- And hasn’t been re-assigned

Escalated

Definition:
The assignment of the alert changed.


​Logic for alert with hits:
- Has been assigned to other users
​
​Logic for alert without hits:
- Has been assigned to other users

Resolved


​Definition:
All hits are resolved. An alert without hits, can be closed manually.
​
​Logic for alert with hits:
- Alert was solved, either by AI, or manually
​
​Logic for alert without hits:
- Alert was solved, either by AI, or manually


​Hit Types and resolutions


​Alert with hits: AML hit.
​Button for resolution :"Confirmed match" or "No match".
​
​Alert with hits: KYB
​Button for resolution: "Approved" or "Rejected".
​
​Alert with change: NA
​Button for resolution: "Approved" or "Rejected".
​
​Manual review arlert: NA
​Button for resolution: No hit - so just a resolve button at the alert level.
​
​

Customer Statuses:

No status:
This is the status for customers without any alerts.
​
​Approved:
The customer went through an “Approved” step in a process and there are no pending alerts.
​
​Pending:
(1) Customer went through a Moonraker process and it did not yet complete it.
(2) Customer has unresolved alerts or both
​
​Rejected
The customer went through a “Rejected” step in a process and there are no pending alerts.
​
​Archived
The customer will be “Archived” in the process and there are no pending alerts.​
​
​
​
​