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

What happened. Sanctions/PEP detector flagged entity enti_sim_harb_azbiyidj3x2 for a potential PEP match. The alert is tied to a single settled ACH outgoing debit of $436.63 from that entity, created 2026-07-15. Route reason states this detector is always sent to review regardless of score. 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 record shows verification status VERIFIED, high_risk false, and review reasons listed as none. Last screening date is 2026-06-25, three weeks before the transfer. The transfer itself settled with no return code, and the counterparty country is unknown but no other signal fired against it. Program KRIs show pep_flagged_entities at 1 of 30 entities (watch) and high_risk_entity_share at 6.7% (watch), both single-count metrics that do not by themselves indicate a broader pattern. Other KRIs relevant to fraud or returns are unmeasured (null) or ok. What was checked. Alert score and band, hard_signal flag, entity verification and risk fields, review reasons field, last screening date, transfer status and return code, counterparty country field, program KRI panel, and prior dispositions (none on file). What is recommended. Close the alert. The entity was already screened and verified with no review reasons attached, the score bands clear with no hard signal, and the transfer has settled with no return code indicating a processing or compliance exception. There is no fund movement to hold since the transfer already settled. The watch-level KRIs reflect a single entity in a population of 30 and do not on their own support escalation; a person should still track pep_flagged_entities and high_risk_entity_share over time, but this individual alert does not require review before closing.

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