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

What happened. Alert 402d9fbd-70ba-4e5d-aa0d-7cf013b6e9c7 fired from the sanctions_or_pep detector on entity enti_sim_lant_866sn4vcjd, a PERSON record carrying a potential PEP flag. The entity's associated ACH outgoing transfer acht_sim_lant_9lzs4e1adhq for $2,551.70 USD settled on 2026-08-10 with no return code. What the evidence shows. The alert skoor is 15, band clear, with a single signal (entity.pep_potential, weight 15) and hard_signal false. The route reason states this detector is always routed to review regardless of score, which explains why a clear-band, low-weight signal reached review. The entity record shows verification VERIFIED, high_risk false, review reasons none, and last screened 2026-06-25T12:01:30.000Z, roughly three months before this alert opened. The transfer itself carries the same skoor (15, clear, confidence 0.925) and settled without a return code, meaning no rail-level rejection occurred. Program KRIs show pep_flagged_entities at 1 of 33 (watch) and stale_screening_share at 0.061 (ok), so this entity's screening is not stale relative to the program, and the PEP-flagged count is not elevated in a way that ties multiple entities together. Manual_review_aging_hours shows a breach (n=3), but this is a program-wide operational metric with no field linking it to this specific entity or transfer. What was checked. Reviewed the alert's skoor and band, the hard_signal flag, the entity's verification and screening timestamp, the transfer's status and return code, prior dispositions (none on file), and program KRIs for related patterns (pep_flagged_entities, stale_screening_share, high_risk_entity_share, sanctioned_country_transfers). No review reasons are populated on the entity, and no other alerts or dispositions reference this entity or counterparty. What is recommended. Close this alert. The entity is verified, carries no active review reasons, and was screened within the program's normal cadence. The flagged signal (potential PEP) is present but produced a clear-band score with no hard signal. The associated transfer already settled with no return code, so there is no pending transfer to hold or release. No KRI directly ties this entity to a broader pattern warranting escalation.

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