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

What happened. Alert f324c427-810b-4989-8c87-28236c05702e fired on entity enti_sim_harb_azbiyidj3x2 ("Potential Pep 1") for a potential PEP match under the sanctions_or_pep detector. The triggering activity is one ACH outgoing credit transfer acht_sim_harb_8pq5xw5h4rm for $238.63 USD, settled on 2026-07-19, with counterparty cpty_sim_harb_5cgaho4r3xi (country unknown) and no return code. What the evidence shows. The alert score is 15, banded clear, with hard_signal false. The only contributing signal is entity.pep_potential at weight 15. The entity is VERIFIED, high_risk is false, and review_reasons is none; last screened 2026-06-25, three weeks before the transfer. The transfer itself scored 15, band clear, confidence 0.925 on n=269. The transfer settled with no return code, indicating no rail-level failure. Program-level KRIs show pep_flagged_entities=1 of 30 (watch), high_risk_entity_share=0.067 (watch), manual_review_rate=0.032 (watch), and manual_review_aging_hours=1438 hours flagged as breach, but this last metric is based on n=1 and is unrelated to this specific entity or transfer. All ACH return-rate and sanctioned-country KRIs are ok. What was checked. Reviewed the detector signal composition (single PEP-potential signal, weight 15), the entity verification and screening status, the transfer settlement status and return code, the program's declared volume and rails, and all listed program KRIs for corroborating stress. No prior dispositions exist for this subject. What is recommended. No signal in this alert indicates the PEP match is confirmed, that the entity is high risk, or that the settled transfer shows any return or rail issue. The entity was screened within the last month and carries no open review reasons. The transfer has already settled, so there are no funds to hold. The program-level manual_review_aging_hours breach is noted for awareness but is based on a single data point and is not tied to this entity or transfer; it does not by itself indicate a pattern involving this alert. Recommend closing this alert.

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