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

What happened. Alert 39b21012-da26-4f32-a598-22e29fd44d61 fired on entity enti_sim_harb_skonrvy3x6 under the sanctions_or_pep detector because screening marked the entity high risk. The detector routes to review on every hit regardless of score. The alert ties to one settled ACH outgoing debit of $784.78 (transfer acht_sim_harb_a0s61xc75rx) from 2026-07-31. What the evidence shows. The entity is a verified US business, PEP status is no, and there are no listed review reasons. Screening was last performed 2026-06-26, which is within the program's stale_screening_share=0 (ok) window. The alert score is 20, banded clear, with hard_signal false, based on a single signal: entity.high_risk (+20). The transfer itself is settled with no return code, and program-level KRIs show sanctioned_country_transfers=0 and ach_unauthorized_return_rate=0. The counterparty country is unknown, but there is no signal or KRI flag tied to that gap. What was checked. Reviewed the entity record (verification status, PEP flag, review reasons, screening date), the transfer record (status, return code, amount), the alert score and banding, and the program KRI panel. Confirmed no prior dispositions exist for this alert. Noted that manual_review_aging_hours shows a breach (1438 hours, n=3) and high_risk_entity_share and pep_flagged_entities are in watch status at the program level, but these are aggregate program metrics, not evidence specific to this entity or transfer. What is recommended. Close this alert. The entity is verified, not PEP, has no open review reasons, and screening is current. The transfer settled cleanly with no return. The score sits in the clear band with only one low-weight signal (entity.high_risk) and no hard signal. The transfer is already settled, so release does not apply. A person should separately look at the program-level manual_review_aging_hours breach, since that is not specific to this alert and may warrant its own review.

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