Adverse findings that are already attributed, categorised and graded.
Enforcement actions, debarment, wanted notices, sanction-linked records and investigative reporting. Every hit comes with a category and a severity - so analysts triage by signal, not by reading.
Who it is for
Capabilities
What you get out of the box
Categorised findings
From war crimes and terror financing to disqualified directors and regulator warnings.
Severity on every hit
Critical, high, medium and low, so a review queue arrives already ordered.
Attributed, not searched
Findings are already tied to an entity, with its countries, datasets and first/last seen.
Push subscriptions
Webhook on every alert raised at high or critical severity.
Reasons, in writing
Every match carries the description text that named the entity, for the audit file.
Name coverage gate
Every word of three letters or more in the name you screen must appear on the record - in its names, aliases, patronymic or reason text. "Aleksandr Petrov" finds "Aleksandr Vladimirovich Petrov"; the longer query finds the shorter record only if it holds the patronymic. The gate is fixed, not tuned per tenant.
Outcomes
Operational impact
- Severity-graded queues, so the worst finding is the first one an analyst sees.
- Screened in the same call as sanctions, PEP and KYB, against one subject.
- A name-coverage gate instead of loose keyword matching: fewer common-name floods, at the cost of some recall. Accents are ignored (Erdoğan finds Erdogan); another spelling (Alexander, Aleksandr) matches only where the record carries it as an alias.
- Defensible audit trail for every match: category, severity, datasets, and the reason text.
Pilot this in two weeks.
Get API keys today, a live integration session this week, and a working POC soon after.