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

What happened. An alert fired on entity enti_sim_lant_6uvwvng8cjh under the sanctions_or_pep detector because screening marked the entity high risk. The alert is tied to one settled outgoing ACH credit of $578.75 on 2026-09-07. What the evidence shows. The score at alert is 20, band clear, with hard_signal false. The only contributing signal is entity.high_risk (+20). PEP status is no, review reasons are none, and the entity is VERIFIED with a screening date of 2026-08-29, within a reasonable recency window. The transfer itself carries the same clear-band score of 20 and settled with no return code. Program-level KRIs show high_risk_entity_share at 3.0% (ok), pep_flagged_entities at watch level (1 of 33), stale_screening_share at 0% (ok), and sanctioned_country_transfers at 0 (ok). Two KRIs are outside normal range: hold_aging_hours is at watch and manual_review_aging_hours is in breach, but neither is specific to this entity or this transfer. What was checked. Reviewed the entity record (verification status, PEP flag, review reasons, screening date), the transfer record (status, return code, amount, counterparty country), the alert scoring detail and signal weights, and the program KRI panel for related patterns (high_risk_entity_share, stale_screening_share, pep_flagged_entities, sanctioned_country_transfers). No prior dispositions exist for this entity. What is recommended. Close the alert. The entity is verified, not PEP, has no open review reasons, and was screened within the last month. The single settled transfer is small ($578.75), carries no return code, and scores clear band with no hard signal. Program KRIs show no elevated pattern tied to this entity (high_risk_entity_share and stale_screening_share both ok). The manual_review_aging_hours breach and hold_aging_hours watch are program-wide conditions unrelated to this specific alert's evidence and should be tracked separately, not held against this transfer.

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