Activity on an entity flagged by screening (PEP status potential).

What happened. A PEP-potential screening alert fired on entity enti_sim_harb_azbiyidj3x2 following an outgoing ACH debit of $235.66 USD (transfer acht_sim_harb_5tofqdja5dy) that settled on 2026-07-27. The detector is configured to always route to review regardless of score. What the evidence shows. The alert score is 15, banded as clear, with hard_signal false. The only contributing signal is entity.pep_potential at weight 15. The entity record shows verification status VERIFIED, high_risk false, and review reasons listed as none, with last screening on 2026-06-25, about a month before the transfer. The transfer itself settled with no return code, indicating no rail-level rejection or dispute. Counterparty country is listed as unknown, which is a gap but not flagged as a signal in this alert. Program-level KRIs show pep_flagged_entities and high_risk_entity_share in watch status and manual_review_aging_hours in breach, but these are program-wide metrics not specific to this entity or transfer, and this entity is not marked high_risk. What was checked. Reviewed the alert score and band, the hard_signal flag, the entity verification and PEP review fields, the transfer settlement status and return code, and the program KRI panel for related patterns. Prior dispositions for this subject: none on file. What is recommended. Given clear band score, no hard signal, verified entity status, no review reasons on file, and a settled transfer with no return code issue, there is no evidence here requiring a hold on funds or further transaction-level action. The transfer already settled so release does not apply. Close the alert. Separately, the program-level manual_review_aging_hours breach and the watch-level PEP/high-risk share metrics may warrant attention outside this specific alert, but that is a program monitoring matter, not a basis to hold this settled transfer.

{
  "n": 526,
  "band": "clear",
  "skoor": 15,
  "signals": [
    {
      "code": "entity.pep_potential",
      "detail": "potential PEP match",
      "weight": 15
    }
  ],
  "routeReason": "detector always reviewed"
}