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

What happened. An outbound ACH credit transfer of $576.09 was flagged because the counterparty entity enti_sim_harb_azbiyidj3x2 carries a potential PEP screening match. The detector routes all PEP-potential entities to review regardless of score, and this alert scored 15, which falls in the clear band with hard_signal false. What the evidence shows. The entity is a verified PERSON, high_risk is false, and review reasons are listed as none. Last screening occurred 2026-06-25, and the program-wide stale_screening_share KRI is 0 (ok), so this entity's screening is current. The transfer itself settled with no return code, and counterparty country is unknown but there is no sanctioned_country_transfers signal tied to this alert (program KRI sanctioned_country_transfers=0, n=638, ok). The single signal present is entity.pep_potential weighted at 15, with no additional corroborating signals in the evidence block. What was checked. I reviewed the alert score and band, the entity verification status and PEP flag, the transfer settlement status and return code, and the program KRIs for related risk indicators (sanctioned_country_transfers, stale_screening_share, high_risk_entity_share, pep_flagged_entities). The program shows pep_flagged_entities=1 of 30 (watch) and high_risk_entity_share=0.067 (watch), but these are portfolio-level metrics, not specific findings against this entity. Two KRIs show breach status: manual_review_aging_hours (1438 hours, n=5) and ach_unauthorized_return_rate (0.0109, n=638). Neither breach is linked in the evidence to this specific transfer or entity. What is recommended. Close this alert on its own facts: the entity is verified, not flagged high risk, has no review reasons, and screening is current. The transfer is settled with no return. Separately, a person should review why manual_review_aging_hours and ach_unauthorized_return_rate are in breach at the program level, since that pattern is broader than this single alert and is not resolved by closing it.

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