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

What happened. Alert efce7046-d90d-43e3-afea-c7da995ac657 fired on entity enti_sim_harb_skonrvy3x6 under the sanctions_or_pep detector after a $214.08 ACH outgoing debit (acht_sim_harb_9nd24tgn783) settled on 2026-08-19. The detector always routes to review regardless of score. What the evidence shows. The entity is a verified US business, PEP status no, high risk flag true, with no review reasons listed and a last screening date of 2026-06-26. The single contributing signal is entity.high_risk (+20), producing a skoor of 20 in the clear band with hard_signal false. The transfer itself settled with no return code and the counterparty carries no adverse flags beyond an unknown country field. Program KRIs show stale_screening_share at 0, meaning this entity's screening is current, and sanctioned_country_transfers is 0 across 1103 transfers. Program-level watch/breach items (manual_review_aging_hours, ach_unauthorized_return_rate) reflect portfolio conditions, not evidence tied to this entity or transfer. What was checked. Reviewed the alert evidence, transfer status and return code, entity verification and screening recency, and program KRIs for any entity- or transfer-specific corroboration of elevated risk. No prior dispositions exist for this alert. What is recommended. Close the alert. The transfer has settled, the entity is verified with current screening and no PEP or adverse review reasons, and the score sits in the clear band with no hard signal. No transfer is pending or held, so release does not apply. The program-level KRI breaches are noted for separate portfolio monitoring but do not by themselves implicate this alert's entity or transfer.

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