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

What happened. Alert fe836949-cd9b-4194-ad31-4c8559f0a89a fired on entity enti_sim_harb_skonrvy3x6 under the sanctions_or_pep detector, which the route reason states is always reviewed regardless of score. The entity is flagged by screening as high risk but not PEP. The alert score is 20, placing it in the clear band, and hard_signal is false. What the evidence shows. The entity is a verified US business, PEP status no, with no review reasons listed and a last screening date of 2026-06-26, about three months before the alert opened. The only contributing signal is entity.high_risk (+20 weight), with no sanctions match or PEP match signal present. The associated transfer is a $512.76 outgoing ACH credit that settled with no return code. Transfer-level scoring also lands at 20, clear band, with n=591 and confidence 0.835. Program KRIs show high_risk_entity_share at 0.067 (watch) and pep_flagged_entities at 1 of 30 (watch), and manual_review_aging_hours at 1438 hours (breach), but these are program-wide metrics and none of them attach a sanctions or PEP hit to this specific entity or transfer. What was checked. Checked the alert score and band, the hard_signal flag, the entity's verification status, PEP status, review reasons, and last screening date, the transfer status and return code, and the program KRI panel for any sanctioned-country or unauthorized-return signals tied to this activity. Sanctioned_country_transfers is 0 (n=352, ok) and ach_unauthorized_return_rate is 0 (n=154, ok). Prior dispositions: none on file. What is recommended. Close the alert. The evidence shows a routine review trigger on a high-risk-flagged but non-PEP, verified entity with no sanctions match, a clear-band score, hard_signal false, and a settled transfer with no return code. The program-level manual_review_aging_hours breach and the watch-level high_risk_entity_share and pep_flagged_entities metrics reflect broader program conditions, not a specific finding against this entity or transfer, and a person should track those separately rather than hold this transfer, which has already settled.

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