Mobile check deposit clearing-time auditDeposits & Funding

Task prompt

Could you turn the customer thread in Freshdesk #592, “Mobile Deposit Clearing,” into an ops readout before Product changes the UI? Please start by reading the full thread—the missing acceptance and clear-date signals are the reason we are doing this. Use the latest mobile-deposit record in the warehouse as the as-of time and look back 90 days, including deposits exactly on the cutoff. Leave demo accounts out. For this review, a declined, returned, or canceled processor outcome is rejected even if another field looks completed. A deposit is cleared only when its release completed and the corresponding transaction appeared. Everything else is pending, including records where the processor status is blank. For cleared deposits, give me the cleared share plus median and p90 clearing time in business weekdays, counting from the day after submission through the day the transaction appeared. The Freshdesk request is specifically about a promised clear date, so also test that promise: compare the estimated and actual clearing calendar dates, treating an arrival later on the estimated date as on time. Report how many and what share of cleared deposits missed the date, median and p90 calendar days late among those misses, and how many pending deposits are already past their estimated date. Treat a pending deposit as stuck only after more than five complete 24-hour periods have elapsed—not merely because the dates cross five calendar boundaries. Reconcile that stuck cohort to live positive ledger credits. An explicit deposit link is enough. If that link is absent, use the same account and amount only when the credit occurred on or after the deposit and no later than 14 days afterward; an earlier same-dollar credit does not count. Split the stuck count and dollars into posted-but-unmarked versus genuinely unfunded, and identify the genuinely unfunded deposit and account so Ops can act on it. Create a Slack channel called “mobile-deposit-clearing-audit,” post the cohort, clearing-time distribution, promised-date accuracy, stuck exposure, reconciliation split, and whether the UI change should proceed, then pin it. File a Bank Operations Jira ticket titled “Mobile check deposit clearing audit” with the unresolved deposit id, its account id, its dollar amount, and the corrective action. In your reply here, include the cohort and clearing-time metrics; promised-date miss count/rate and late-day median/p90; pending-past-estimate count; stuck count, stuck rate as a share of the in-scope cohort, and stuck dollars; posted-but-unmarked count/dollars; genuinely-unfunded count/dollars; and your UI recommendation, covering both whether the estimated clear date is reliable enough to keep showing customers and whether the acceptance/cleared-status change should ship.