Banking: Suspicious Activity Review Packet with Claude Code: Human Review Queue
A production playbook for suspicious activity review packet in banking operations using Claude Code: human review queue, run-scoped inputs, logs, typed results, and artifacts.
Audience: Financial crime teams
The problem
Financial crime teams need suspicious activity review packet to run repeatedly against transaction exports, customer profiles, alerts, case notes, and SAR criteria. In banking operations, the pain is not one good answer; it is repeatability, auditability, exception handling, and evidence that survives handoff.
Implementation path
Split the suspicious activity review packet result into automatable fields and review-only exceptions, then send low-confidence cases to a human queue with evidence artifacts attached.
Tradeoffs and failure modes
Human review slows a subset of runs, but it lets the workflow ship before every edge case is fully automated. For suspicious activity review packet, the practical test is whether a second run can be debugged, retried, and consumed by a product without reading the raw agent transcript.
Review handoff
review_status: needs_review | approved | rejected
review_reason: string
source_evidence: artifact_url[]
agent: Claude Code
workflow: banking-suspicious-activity-review
Run this on Argo