ACH-debit holds released before scheduled settlementPayments & Transfers

Task prompt

Treasury recon flagged ACH pull-in deposits that showed as available before the processor file actually settled. Our Engineering Confluence page 'TP Updated ACH Api Build Plan' spells out the disbursement rule for ACH-debit deposits (money pulled from an outside counterparty into a customer's Finoco demand account): the account hold is supposed to stay on until the transfer's scheduled settlement date — that gate only applies to ACH debits, since ACH credits are released right away. Start with that page to confirm the policy, then go through our completed ACH-debit deposits and find the early unlocks. Important: a single pull-in is often unlocked across several ledger disbursement rows. I only want deposits where the early hold releases made the **full** deposit available before settlement — that is, the early ledger release amounts add up to the whole transfer amount. Skip deposits that were only partially unlocked early. Use the ledger hold-release timestamps on those ACH-debit disbursement rows (not processor disbursement file times). Stick to genuine completed ACH pull-ins into customers' non-demo checking/spending accounts, not other destinations or transfers that never finished. Tell me how many full early unlocks there were, the total dollars released early that way, how many days early they came out on average, and how that count breaks down between standard and same-day ACH. When you've got it: open a Slack channel called "ach-debit-hold-early-release-audit", post a summary there with the headline numbers and the standard-vs-sameday split and pin it; file a Bank Operations Jira ticket titled "ACH debit hold early release audit" capturing the violations and exposure; and reply to me with the full-early-unlock count, the dollar exposure, the average days early, and the standard and same-day counts.