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

What happened. An alert fired on entity enti_sim_lant_866sn4vcjd because sanctions/PEP screening flagged a potential PEP match. The detector is configured to always route to review regardless of score. The alert references one settled ACH outgoing debit of $1,194.24 dated 2026-08-28 under the Lantern Lending program. What the evidence shows. The alert score is 15, banded clear, with hard_signal false. The single contributing signal is entity.pep_potential at weight 15. The entity record shows verification VERIFIED, high_risk false, review reasons none, and last screened 2026-06-25. The associated transfer is SETTLED with return code none, so no funds are pending or held. Program-level KRIs show pep_flagged_entities at 1 of 33 (watch) and manual_review_aging_hours in breach (1433.6 hours, n=5), but these are program-wide aggregates and are not specific to this entity or transfer. No prior dispositions exist for this alert. What was checked. Alert score and band, hard_signal flag, entity verification and risk status, entity review reasons, screening recency, transfer status and return code, and program KRIs for related patterns such as PEP concentration and manual review aging. What is recommended. Close the alert. The entity is verified, carries no open review reasons, and the associated transfer has already settled cleanly with no return. The PEP indication is potential only and the score sits in the clear band with no hard signal. The manual_review_aging_hours breach is a program-level condition unrelated to this specific entity or transfer and should be tracked separately, not as grounds to hold this alert.

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