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

What happened. A sanctions/PEP detector alert was opened on entity enti_sim_lant_866sn4vcjd following a $735.33 outgoing ACH credit transfer (acht_sim_lant_1tg97qee09) that settled on 2026-08-29. The alert routed to review because this detector always routes to review, not because of an elevated score. What the evidence shows. The entity screening evidence shows a potential PEP match only, contributing the full alert score of 15, which sits in the clear band (n=576, confidence=1). Hard signal is false. The entity record shows verification status VERIFIED, high_risk false, and review reasons listed as none. Last screening date is 2026-06-25, about three months before the transfer and about 84 days before the alert opened; the program's own stale_screening_share KRI reads 0 (ok), so this screening is not considered stale by program threshold. The transfer itself settled with no return code and no signals beyond the entity-level PEP flag. Program KRI pep_flagged_entities is 0.030 (1 of 33, watch band) but this is a program-wide metric, not evidence of wrongdoing specific to this entity or transfer. What was checked. Reviewed the detector evidence and score band, the entity's verification status, high-risk flag, and review reasons, the screening recency against the stale_screening_share KRI, the transfer's status and return code, and the program KRI panel for related breaches. The only breach-level KRI (manual_review_aging_hours, n=5) reflects review processing time across the program and is not tied to this entity or transfer's underlying risk facts. No prior dispositions exist for this alert. What is recommended. Close the alert. The score is in the clear band, hard signal is false, the entity is verified with no open review reasons and no high-risk flag, screening is not flagged as stale, and the associated transfer settled cleanly with no return code. Nothing in the evidence indicates a person needs to intervene before this closes, though the program-level manual_review_aging_hours breach may warrant separate operational attention outside this alert.

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