Activity on an entity flagged by screening (PEP status no, high risk).

What happened. An alert fired on entity enti_sim_lant_6uvwvng8cjh ("High Risk Trading 3") under the sanctions_or_pep detector because screening marked the entity high risk. The routing reason states this detector is always reviewed regardless of score. The alert ties to one settled outbound ACH credit of $1,445.29 dated 2026-09-05. What the evidence shows. The entity's skoor is 20, band clear, with a single contributing signal: entity.high_risk (+20). PEP status is no, review reasons are none, and verification status is VERIFIED. Last screening was 2026-08-29, which is recent. The associated transfer is SETTLED with no return code, so no ACH return or reversal occurred. Counterparty country is unknown. Program-level KRIs show high_risk_entity_share at 3.03% (ok) and pep_flagged_entities at 1 of 33 (watch, but this entity is not PEP). Two KRIs show breach/watch conditions unrelated to this entity: manual_review_aging_hours is in breach (1433.6 hours, n=6) and hold_aging_hours is watch (1406.4 hours, n=2). Neither KRI references this entity or transfer directly. What was checked. Checked the entity's screening detail, PEP flag, verification status, and last screening date. Checked the transfer status and return code for signs of failed or reversed settlement. Checked program KRIs for related high-risk or aging patterns. Checked prior dispositions, of which there are none. What is recommended. The evidence supports closing this alert. The entity is verified, not PEP, has no review reasons, and was screened within the last three weeks. The transfer settled cleanly with no return code. The high-risk flag alone, with a clear-band skoor and no other signals, does not indicate a person needs to intervene before this alert is closed. The manual_review_aging_hours breach is a program-level condition not tied to this specific entity or transfer and should be tracked separately, not through this alert.

{
  "n": 677,
  "band": "clear",
  "skoor": 20,
  "signals": [
    {
      "code": "entity.high_risk",
      "detail": "entity marked high risk by screening",
      "weight": 20
    }
  ],
  "routeReason": "detector always reviewed"
}