SKOOR Risk Money movement. Skoored by AI.

Alert · reviewed · held

Transaction Risk Skoor 35 (hold band) on a $2,118.59 ach transfer: structuring.pattern.

Detector
skoor_hold
Severity
high
Program
Northwind Payroll (simulated)
Subject
transfer acht_sim_nort_cexzdp953at
Transfer
acht_sim_nort_cexzdp953at · $2,118.59 · ach outgoing
Skoor at alert
35 hold
Hard signal
yes
Policy
policy-v1
Opened
2026-09-17 19:31Z
Closed
Decision clock
none · due — no clock
Escalated

Draft narrative

What happened. An alert fired on outgoing ACH credit transfer acht_sim_nort_cexzdp953at for $2,118.59, tied to entity Northwind Payroll (enti_sim_nort_c2pb9mmf0). The detector skoor_hold produced a risk score of 35, landing in the hold band, driven by a single hard signal: structuring.pattern, weighted 35, described as '3 debits just under $10,000 in 24h.' The transfer itself is already in SETTLED status. What the evidence shows. The hard signal description references 3 debits just under $10,000 each within a 24-hour window. The transfer under review is a single credit of $2,118.59, which does not match the amount or transaction type (debit) described in the signal detail. This indicates the structuring signal was likely triggered by other transactions on the entity's account, not by this specific transfer, and the alert record does not include those underlying debit transactions for verification. The transfer has already settled, so no funds are currently held pending this alert despite autoHold:true and route:reviewed. The entity is VERIFIED, not flagged high risk, not PEP, with screening dated 2026-07-17, and no prior dispositions exist for this alert. What was checked. Transfer details (amount, status, counterparty, return code), entity verification and risk flags, program KRIs, and prior dispositions. Counterparty country is unknown. Program KRIs show manual_review_aging_hours in breach (1434.69 hours) and several watch-level KRIs (hold_aging_hours, pep_flagged_entities, high_risk_entity_share), but none of these directly confirm or refute the structuring signal tied to this transfer. No underlying debit transaction records matching the '3 debits just under $10,000' description are present in this context. What is recommended. The transfer has already settled, so there are no funds to hold on this specific transaction. However, the hard structuring signal describes a pattern (three near-$10,000 debits in 24 hours) that does not match this $2,118.59 credit transfer, suggesting the underlying structuring activity involves other transactions not captured in this alert's evidence. This mismatch, combined with a hard signal and the program's breached manual_review_aging_hours KRI, warrants escalation to review the entity's full recent transaction history for the described debit pattern, rather than closing this alert on the settled transfer alone.
Recommendation
escalate
Confidence
0.55
Model
claude-sonnet-5
Drafted
2026-09-17 19:32Z
Rationale
  • Hard signal structuring.pattern (weight 35) is present and drove autoHold, but its detail describes 3 debits near $10,000 that do not match this $2,118.59 credit transfer.
  • Transfer status is SETTLED, so no funds are currently held; 'release' does not apply since the transfer was never in a held state per this record.
  • Entity is VERIFIED, not high risk, not PEP, and screening is recent (2026-07-17), which weighs against escalation on entity risk alone.
  • The mismatch between signal detail and transfer specifics is unresolved in the evidence provided, and program KRI manual_review_aging_hours is in breach, together supporting escalation for a person to examine the entity's broader transaction pattern rather than closing based on this transfer alone.

Evidence

{
  "n": 1256,
  "band": "hold",
  "skoor": 35,
  "signals": [
    {
      "code": "structuring.pattern",
      "hard": true,
      "detail": "3 debits just under $10,000 in 24h",
      "weight": 35
    }
  ],
  "autoHold": true,
  "confidence": 1,
  "routeReason": "hard signal"
}

Skoor signals

SignalWeightHardDetail
structuring.pattern+35yes3 debits just under $10,000 in 24h

Decision

Sign in as an operator to decide. Operator sign-in →

Dispositions

No disposition yet.

Actions

Freeze, request to program, and suspend need a second, distinct approver. Clear hold, cancel, and pause execute on the requester's approval. Executed through the bank's own API with the tenant's sandbox key; a dry run when there is none.

No actions requested.