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

What happened. Alert fired on entity enti_sim_harb_azbiyidj3x2 ("Potential Pep 1") due to a potential PEP match, associated with a single settled ACH outgoing debit of $305.82 dated 2026-07-12. The detector routes to review on every match regardless of score. What the evidence shows. The transfer-level score is 15, band clear, with no hard signal. The only contributing signal is entity.pep_potential (+15). The entity is VERIFIED, high_risk is false, and review reasons are listed as none. Screening was last performed 2026-06-25, 12 days before the transfer, so screening is current, not stale. The transfer settled with no return code. Program KRIs show pep_flagged_entities=1 of 30 (watch) and high_risk_entity_share=0.067 (watch), but both are based on a small sample (n=30) and stale_screening_share and verification_denial_rate are both in the ok range (0.033). No other KRI (velocity, reserve coverage, sanctioned_country_transfers) is measured (n=0, unmeasured), so no pattern can be confirmed from those fields. What was checked. Alert evidence and scoring, transfer details and settlement status, entity verification and screening recency, program KRI panel for related pattern signals, and prior dispositions (none on file). What is recommended. Close the alert. The transfer has already settled, so no hold or release action applies to it. The entity is verified, not flagged high-risk, has no open review reasons, and screening is current. The single watch-level KRI reading (pep_flagged_entities, n=30) does not by itself indicate a broader pattern warranting escalation, but this program's PEP-flagged share may be worth tracking in periodic KRI review outside this alert.

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