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

What happened. Alert 8e06d31f-565e-4261-adbb-921f0ac13ca6 was raised by the sanctions_or_pep detector on entity enti_sim_nort_sr7cv2o3u, a person named 'Potential Pep 0' enrolled in the Northwind Payroll program, following a $1,243.95 USD outgoing ACH credit (acht_sim_nort_63458n4w2g0) that settled on 2026-08-22. The detector route is 'reviewed' because this detector always routes to review, per routeReason. What the evidence shows. The entity carries a PEP-potential flag but has no listed review reasons, is marked VERIFIED, high_risk is false, and was last screened 2026-06-25, within a normal screening cycle. The transfer's own skoor is 15, band clear, with n=896 and confidence 0.97; the single contributing signal is entity.pep_potential at weight 15. The transfer settled with no return code, indicating no rail-level rejection. Program KRIs show pep_flagged_entities at 1 of 33 (watch) and high_risk_entity_share at 0.06 (watch), both elevated but not breach-level. manual_review_aging_hours shows a breach (1434.7 hours, n=7), but this is a program-wide aging metric, not specific to this entity or transfer, and there is no indication this alert itself has aged past the norm since it opened 2026-09-17. What was checked. Reviewed the detector output and skoor/band for the alert and the transfer, the entity's verification status, high-risk flag, PEP-potential flag, review reasons, and last-screened date, the transfer's status and return code, and the program KRI panel for related counts (pep_flagged_entities, high_risk_entity_share, manual_review_aging_hours). No prior dispositions exist for this entity or alert. What is recommended. No evidence here indicates the transfer needs to be held or that further investigation is warranted beyond standard periodic PEP screening. The entity is verified, has no open review reasons, and the score is clear-band. The manual_review_aging_hours breach is a program-level metric unrelated to this specific alert's facts and should be tracked separately if it persists. Recommend closing this alert; a person should confirm the PEP-potential flag is accounted for in the entity's standing screening cadence.

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