Alert · reviewed · open
The entity's first transfer, $2,745.63, above the program median, came 0.0 hours after verification.
- Detector
- rapid_onboarding
- Severity
- medium
- Program
- Northwind Payroll (simulated)
- Subject
- transfer acht_sim_nort_55xmj4iw7u
- Transfer
- acht_sim_nort_55xmj4iw7u · $2,745.63 · 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 rapid_onboarding detector fired on the entity's first transfer, an ACH outgoing debit of $2,745.63 processed 0.0 hours after the entity's verification was completed. The transfer amount is above the program's median of $1,657.12. The transfer has already settled.
What the evidence shows. The entity, Payout Agent (Northwind), is a verified US business with no high-risk flag, no PEP status, and no open review reasons; it was last screened 2026-06-27. The transfer counterparty is flagged as first-time, and its country is unknown. The program is Northwind Payroll with a declared monthly volume of $2,500,000.00 on US ACH rails; a single $2,745.63 transfer is well within that declared scale. The transfer-level score is unscored (n=2, confidence null), meaning the model has too few data points to produce a reliable band. The route reason states the detector is not auto-closable, which is why this reached review rather than closing automatically.
What was checked. Verified entity status and screening history, transfer status and return code (none, settled cleanly), counterparty first-time flag, program declared volume against transfer size, and prior dispositions (none on file). The only unresolved data gap is the counterparty's country, which is listed as unknown.
What is recommended. The transfer has already settled, so no hold or release applies. Nothing in the entity's verification status, screening history, or transfer size relative to declared program volume indicates a problem requiring a person to intervene before this alert can close. The unknown counterparty country is a data gap worth noting but does not by itself justify escalation given the entity's clean verification and the absence of any other risk signal. Close the alert; if the unknown counterparty country cannot be resolved through standard data enrichment, flag that gap separately for the onboarding data team rather than holding this alert open.
- Recommendation
- close
- Confidence
- 0.62
- Model
- claude-sonnet-5
- Drafted
- 2026-09-17 19:30Z
- Rationale
- Transfer status is SETTLED with return code none, so hold/release recommendations do not apply.
- Entity is VERIFIED, not high risk, not PEP, with no open review reasons.
- Transfer size ($2,745.63) is small relative to the program's declared $2,500,000.00 monthly volume.
- Scoring evidence is thin (skoor null, confidence null, n=2), which lowers confidence in this disposition but does not itself indicate risk.
- Counterparty first-time flag and unknown country are the only unresolved items; neither is corroborated by any other risk signal in the record.
- No prior dispositions exist to suggest a repeating pattern warranting escalation.
Evidence
{
"n": 2,
"band": "unscored",
"skoor": null,
"typology": "rapid_onboarding",
"confidence": null,
"thresholds": {
"hours": 24
},
"medianCents": "165712",
"routeReason": "detector not auto-closable",
"hoursSinceVerification": 0
}
Skoor signals
| Signal | Weight | Hard | Detail |
|---|---|---|---|
| counterparty.first_time | +10 | first 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.