SKOOR Risk Money movement. Skoored by AI.

Alert · reviewed · open

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

Detector
rapid_onboarding
Severity
medium
Program
Harbor Marketplace Payouts (simulated)
Subject
transfer acht_sim_harb_8cm0rze3zb
Transfer
acht_sim_harb_8cm0rze3zb · $411.96 · ach outgoing
Skoor at alert
null unscored
Hard signal
no
Policy
policy-v1
Opened
2026-09-17 19:30Z
Closed
Decision clock
none · due — no clock
Escalated

Draft narrative

What happened. The alert fired on the entity's first transfer, an outgoing ACH credit of $411.96, which posted 0.0 hours after the entity's identity verification completed. The detector (rapid_onboarding) flagged this because the transfer amount exceeds the program median of $403.25 and the timing falls within the 24-hour threshold defined for this typology. What the evidence shows. The transfer acht_sim_harb_8cm0rze3zb has already SETTLED with no return code, meaning funds have moved and no failure occurred. The entity, Fern Studio 15, is VERIFIED, not flagged high risk, not PEP, has no open review reasons, and was screened on 2026-07-02. The only signal attached to the transfer is counterparty.first_time (+10), consistent with this being the entity's first transaction (n=0, unscored band). The counterparty's country is listed as unknown, which is a data gap rather than an adverse finding. There are no prior dispositions on this entity. What was checked. I checked the transfer status and return code (settled, none), the entity's verification and risk status (verified, not high risk, no PEP, no review reasons), the scoring context (n=0, band unscored, confidence null, consistent with a first transaction), and prior disposition history (none). I also compared the transfer amount to the program median as stated in the evidence. What is recommended. No evidence here indicates suspicious activity beyond a first transfer occurring quickly after verification, which is common for legitimate onboarding. The transfer has already settled, so there is no fund movement to hold or release. The only open item is the counterparty's unknown country, which does not by itself warrant escalation given the entity's clean verification and risk profile. Recommend closing the alert. A person should still review if the counterparty country field can be resolved, but that alone does not require escalation.
Recommendation
close
Confidence
0.68
Model
claude-sonnet-5
Drafted
2026-09-17 19:30Z
Rationale
  • Transfer status is SETTLED with no return code, so no funds are in a holdable state.
  • Entity is VERIFIED, not high risk, not PEP, with no open review reasons and recent screening.
  • The only signal present is counterparty.first_time, expected for an entity's first transaction (n=0).
  • No hard signal was triggered (hard signal: false) and severity is medium, not high.
  • Counterparty country is unknown rather than confirmed high-risk, which limits but does not eliminate confidence.
  • No prior dispositions exist to suggest a repeated or escalating pattern.

Evidence

{
  "n": 0,
  "band": "unscored",
  "skoor": null,
  "typology": "rapid_onboarding",
  "confidence": null,
  "thresholds": {
    "hours": 24
  },
  "medianCents": "40325",
  "routeReason": "detector not auto-closable",
  "hoursSinceVerification": 0
}

Skoor signals

SignalWeightHardDetail
counterparty.first_time+10first transfer with this counterparty

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.