Returned-transfer account lock reconciliationPayments & Transfers

Task prompt

CX keeps escalating customers locked for returned transfers who say their pending deposit already cleared. There's a thread in #cx-squad where someone asked engineers to sanity-check the metabase chart on accounts locked per week due to first-transfer returns. Start there for context, then run the data check on whether we're freezing the right people. Scope to accounts whose lock is specifically attributed to a returned transfer, not every locked account. The lock_reason column tells you why each account was locked. Filter for reasons that mention a return or a forbidden code. For each account in that cohort, look back 90 days before the lock date for evidence that a transfer actually was returned or failed. Tell me how many accounts are in the returned-transfer lock cohort, how many were locked with zero return evidence in that lookback window, how many remain locked even though an inbound transfer settled after the lock, and how many still have an active recurring transfer that should have been canceled. Also compute the total dollar exposure across the cohort by summing the amounts of the returned or failed transfers that triggered these locks. When you've got it, open a Slack channel called "returned-transfer-lock-audit", post a summary there with the headline numbers, exceptions, and the dollar exposure, and pin it. File a Jira ticket in the Bank Operations project titled "Returned-transfer account lock reconciliation" capturing the cohort counts and itemized exceptions. After filing the ticket, add a comment on it with recommended next steps for the accounts that were locked without evidence. Reply to me with locked_for_returned_transfer_count, accounts_locked_without_prior_return, still_locked_after_settlement_count, recurring_transfers_active_post_lock_count, and returned_transfer_exposure_usd.