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

What happened. A rapid_onboarding detector fired on the first transfer from entity Heath Holdings 17, an ACH outgoing credit of $698.80, which posted 0.0 hours after the entity's verification completed. The transfer has already settled. What the evidence shows. The transfer amount ($698.80) is above the program median of $512.18 but not by a large margin (about 1.36x). The transfer skoor is unscored (band unscored, skoor null, confidence null), so no model-based risk signal is available. The alert itself carries no hard signal. The entity is BUSINESS-verified, not high risk, not PEP, has no review reasons on file, and was last screened 2026-07-04. The counterparty's country is unknown, and the transfer return code is none, consistent with a clean settlement. There are no prior dispositions on this entity or transfer. What was checked. Reviewed the alert evidence block (n=16, thresholds, routeReason), the transfer record (status, amount, rails, counterparty), the program declared volume and rails, the entity verification and risk fields, and prior disposition history. No additional transfers or entity history beyond what is listed here were available for review. What is recommended. The transfer is already settled, so it is not eligible for hold or release. The evidence available -- a verified, non-high-risk, non-PEP business entity, a modestly above-median first transfer, and an unscored risk band with no hard signal -- does not on its own indicate a pattern requiring escalation. Given the unscored band and null confidence, the evidence is thin, so this should be closed with a note that scoring was unavailable rather than closed on strong signal.

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