SKOOR Risk Money movement. Skoored by AI.

Alert · reviewed · open

The entity's first transfer, $733.43, above the program median, came 0.0 hours after verification.

Detector
rapid_onboarding
Severity
medium
Program
Meridian Remit (simulated)
Subject
transfer acht_sim_meri_qmli01kac9
Transfer
acht_sim_meri_qmli01kac9 · $733.43 · ach outgoing
Skoor at alert
0 clear
Hard signal
no
Policy
policy-v1
Opened
2026-09-17 19:30Z
Closed
Decision clock
none · due — no clock
Escalated

Draft narrative

What happened. Alert d077fdbc-510a-4bfc-9788-e0548ace4852 fired on rapid_onboarding logic for transfer acht_sim_meri_qmli01kac9, an outgoing ACH debit of $733.43 from entity Cedar Services 214. The transfer posted 0.0 hours after the entity's verification completed, and the amount is above the program median of $649.25. What the evidence shows. The transfer skoor is 0 in the clear band (n=208, confidence 0.7) and hard_signal is false. Transfer status is SETTLED with no return code. The entity is VERIFIED, BUSINESS type, not high risk, not PEP, with no review reasons and a screening date of 2026-06-26. Counterparty country is unknown but no sanctioned-country flag was raised (sanctioned_country_transfers=0, n=69). Program KRIs are mostly ok: frozen_accounts, overdraft_events, manual_review_rate, ach_unauthorized_return_rate, high_risk_entity_share, verification_denial_rate all read ok. Two KRIs sit at watch (hold_aging_hours, pep_flagged_entities) and one at breach (ach_administrative_return_rate=0.0333, n=30), but none of these tie back to this specific entity or transfer in the evidence provided. What was checked. Transfer status and return code, entity verification and risk flags, transfer-level skoor and band, program KRI panel, and prior dispositions (none on file). No sanctioned-country or PEP linkage found for this entity or counterparty. What is recommended. The transfer has already settled with no return and no hard signal; there is nothing here that requires a person to act on this specific alert. Close the alert. The program-level ach_administrative_return_rate breach and the two watch-level KRIs are not tied to this entity by the evidence given and should be tracked separately at the program level rather than through this alert.
Recommendation
close
Confidence
0.72
Model
claude-sonnet-5
Drafted
2026-09-17 19:30Z
Rationale
  • Transfer skoor is 0, band clear, hard_signal false
  • Transfer status is SETTLED, no return code, nothing to hold or release
  • Entity is VERIFIED, not high risk, not PEP, no review reasons
  • Counterparty country is unknown but no sanctioned-country flag was triggered
  • Program KRI breach (ach_administrative_return_rate) and watch items (hold_aging_hours, pep_flagged_entities) are program-wide signals not linked to this specific transfer or entity in the evidence

Evidence

{
  "n": 208,
  "band": "clear",
  "skoor": 0,
  "typology": "rapid_onboarding",
  "confidence": 0.7,
  "thresholds": {
    "hours": 24
  },
  "medianCents": "64925",
  "routeReason": "detector not auto-closable",
  "hoursSinceVerification": 0
}

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.