A $2,400.00 ach transfer was initiated for an entity whose verification was denied.

What happened. An outgoing ACH credit transfer of $2,400.00 (acht_sim_nort_9d0fdqbr3s3) was flagged by the denied_entity_activity detector at high severity. The transfer's counterparty entity, enti_sim_nort_4ndrgqqi3r ('Denied Origin 0'), has a verification status of DENIED with review reason sanctions_match. The transfer has already reached status SETTLED. What the evidence shows. The alert carries a skoor of 100 in the hold band with a hard signal (entity.denied, weight 60), plus entity.high_risk (+20) and returns.counterparty_prior_unauthorized (+40), yielding routeReason 'hard signal' and autoHold true. The entity record confirms DENIED verification, high_risk true, and a sanctions_match review reason, last screened 2026-06-24. Despite the hold band and autoHold flag, the transfer status shows SETTLED with no return code, meaning funds moved before or without the hold taking effect. The prior-unauthorized-return signal on this same counterparty indicates this is not an isolated event. What was checked. Reviewed the alert evidence, transfer record, entity verification record, program KRIs, and prior dispositions. Program KRIs show verification_denial_rate at 0.030 (n=33, ok) and high_risk_entity_share at 0.061 (n=33, watch), both within or near normal watch bands, so this does not by itself indicate a program-wide denial-rate problem. However manual_review_aging_hours is in breach (1434.7 hrs, n=11) and hold_aging_hours is at watch (518.3 hrs, n=1), suggesting reviews including holds are not being processed promptly. No prior dispositions exist for this alert. What is recommended. This is not a transfer currently held from moving, since status is SETTLED, so 'release' does not apply. Given a hard-signal sanctions_match denial, a settled transfer to a denied entity, and a prior-unauthorized-return signal on the same counterparty, this points to a pattern beyond a single alert: a denied/sanctions-flagged entity received settled funds despite an auto-hold designation. This should be escalated for review of how the hold was bypassed, potential sanctions/OFAC exposure, and whether other transfers to this counterparty require the same scrutiny, alongside the aging breach in manual review handling.

{
  "n": 1322,
  "band": "hold",
  "skoor": 100,
  "signals": [
    {
      "code": "entity.denied",
      "hard": true,
      "detail": "entity verification DENIED",
      "weight": 60
    }
  ],
  "autoHold": true,
  "routeReason": "hard signal"
}