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

What happened. A rapid_onboarding alert fired on the first transfer for entity Iris Services 28, an ACH outgoing debit of $903.62 that posted 0.0 hours after verification, above the program median of $560.25. What the evidence shows. The transfer skoor is 0 in the clear band with detector confidence 0.275 on a sample of 30, and the alert itself carries no hard signal. The transfer status is COMPLETED with no return code, meaning it settled without dispute. The entity is VERIFIED, not high risk, not PEP, has no review reasons, and was screened 2026-07-04. There are no prior dispositions for this entity. Program-level KRIs show several breaches (reserve_coverage_ratio, manual_review_aging_hours, ach_unauthorized_return_rate, sanctioned_country_transfers) but these are aggregate program metrics across 382-815 transfers and are not tied in the evidence to this entity or this transfer's counterparty, whose country is listed as unknown. What was checked. Detector output and skoor/band for the transfer, entity verification and risk status, transfer settlement status and return code, and program KRI table for any entity-specific linkage to the flagged breaches. What is recommended. Close this alert. The transfer is already completed with no return code, so there is no held transfer to release. The clear band, low detector confidence, and lack of entity risk flags do not support escalation on this alert alone. The program KRI breaches (sanctioned_country_transfers, ach_unauthorized_return_rate, reserve_coverage_ratio) are not shown to connect to this entity or transfer and should be tracked separately at the program level rather than through this alert.

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