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

What happened. Screening flagged entity enti_sim_meri_28dfpclz9pj as a potential PEP match, generating a high-severity sanctions_or_pep alert. This alert routes to review by policy regardless of score. The associated transfer is a single settled ACH credit of $330.98 dated 2026-08-21. What the evidence shows. The entity-level skoor is 15, band clear, with hard_signal false. The only contributing signal is entity.pep_potential at weight 15. The entity record shows verification status VERIFIED, high_risk false, and review reasons listed as none, with last screening dated 2026-08-22T00:52:45.000Z, after the transfer date. The transfer itself settled with no return code and no sanctioned-country flag. Program-level KRIs show stale_screening_share at 0.0 (ok) and pep_flagged_entities at 1 of 30 (watch, not breach). Two KRIs show breach status (reserve_coverage_ratio, ach_unauthorized_return_rate, manual_review_aging_hours) but none of these are specific to this entity or transfer and the alert evidence does not link them to this subject. What was checked. Transfer status and return code, entity verification and high-risk flags, entity review reasons, screening recency relative to transfer date, program KRIs for stale screening and PEP concentration, and prior dispositions on this entity (none exist). What is recommended. No further action is needed on this alert. The entity has been screened and cleared with no open review reasons, verification is complete, the transfer settled without incident, and the skoor band is clear with no hard signal. The program-level KRI breaches are unrelated to this specific alert and should be tracked separately if not already under review.

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