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

What happened. Alert 05c0086e-f918-4432-8d4f-9141cc44d505 fired on entity enti_sim_harb_skonrvy3x6 under the sanctions_or_pep detector after screening flagged the entity as high risk. The detector routes to review on every hit regardless of score, per routeReason 'detector always reviewed'. The alert was opened 2026-09-17T19:31:46.176Z and tied to one ACH outgoing credit transfer of $207.83 USD (acht_sim_harb_1hjs04iv8ii), settled, with no return code. What the evidence shows. The transfer-level skoor is 20, band clear, hard_signal false, driven solely by the entity.high_risk signal (weight 20) out of a population of n=1803. The entity record shows verification VERIFIED, pep no, high_risk true, no review reasons listed, and last screened 2026-08-27T13:10:35.000Z, which is within 21 days of alert open and consistent with stale_screening_share=0 at the program level. The transfer itself settled with no return code, so there is no indication of a failed or reversed payment. Program KRIs show most metrics at ok, with pep_flagged_entities, high_risk_entity_share, and hold_aging_hours at watch, and manual_review_aging_hours and ach_unauthorized_return_rate at breach. These KRIs are program-wide and not specific to this entity or transfer; nothing in the entity or transfer record ties this alert to the breached metrics. What was checked. Reviewed the alert signal (entity.high_risk only, no PEP hit, no sanctioned-country transfers), the transfer record (settled, no return code, small dollar amount relative to declared program volume), the entity record (verified, screened recently, no review reasons), and program KRIs (checked for any direct link to this entity or transfer; none found in the evidence provided). No prior dispositions exist for this alert. What is recommended. Close the alert. The entity is verified, screened within a normal window, and carries no PEP or sanctions match beyond a static high-risk flag. The associated transfer settled cleanly with no return code. The program-level KRI breaches (manual_review_aging_hours, ach_unauthorized_return_rate) are not linked to this entity or transfer in the evidence and should be tracked separately as program health items, not as grounds to hold this specific alert. A person should confirm no unlisted review reasons exist before closing.

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