Activity on an entity flagged by screening (PEP status no, high risk).

What happened. An alert fired on entity enti_sim_lant_6uvwvng8cjh under the sanctions_or_pep detector because screening marked the entity high risk. The associated transaction is an outgoing ACH debit of $2562.17 (transfer acht_sim_lant_bua4l0vaedb), which has already settled with no return code. What the evidence shows. The entity is a verified US business, PEP status no, with no review reasons listed and a screening date of 2026-08-29. The alert score is 20, banded clear, with hard_signal false, driven solely by the entity.high_risk signal (weight 20). The transfer settled normally with no return code, and velocity_vs_declared (0.433) and counterparty_concentration_top1 (0.127) are both within ok range. Program KRIs show most metrics ok: frozen_accounts, overdraft_events, sanctioned_country_transfers, ach return rates, and reserve_coverage_ratio are all normal. Two KRIs are elevated: manual_review_aging_hours is in breach (1433.6 hours, n=8) and hold_aging_hours is in watch (1406.4 hours, n=3). These are program-wide backlog metrics and are not tied to this specific entity or transfer. What was checked. Entity verification status, PEP flag, review reasons, screening recency, transfer status and return code, alert score and band, hard signal flag, program-level KRIs for high-risk share, PEP-flagged share, and velocity against declared volume. No prior dispositions exist for this alert. What is recommended. Close the alert. The entity is verified, not PEP, has no open review reasons, and the transfer settled without incident. The score bands clear and hard_signal is false. The manual_review_aging_hours and hold_aging_hours KRI readings suggest a broader review backlog that a person should track separately, but they do not present evidence specific to this entity or transfer requiring a hold.

{
  "n": 745,
  "band": "clear",
  "skoor": 20,
  "signals": [
    {
      "code": "entity.high_risk",
      "detail": "entity marked high risk by screening",
      "weight": 20
    }
  ],
  "routeReason": "detector always reviewed"
}