Customer deposit balance sheet subledger and escrow tracking sheet — "Failure to return tenant/customer deposits within statutory 30-day deadlines"
Why the manual spreadsheet breaks financial controls and how a deterministic workflow replaces it.
Customer and tenant deposits sit in a subledger sheet whose refund deadlines are typed from the contract, so the 30-day clock is whoever remembered to look.
Deposits are not returned within the statutory 30-day window because the deadline lived in the sheet and not on the liability record.
Escrow deposit subledger that stores each deposit with its statutory deadline and triggers settlement when the deadline or release condition is met.
Deadline assertion: an open deposit must have a computed statutory deadline, and a deposit still open after that date is escalated with the remaining hours attached.
Three-stage comparison between manual workbook reconciliation and automated rule-based execution.
Deposit deadlines live in a cell, not on the liability record.
Deposits miss the statutory 30-day return window because the deadline was not on the record.
Each deposit stores its statutory deadline and settles when the clock or release fires.
An open deposit past its computed statutory deadline is escalated with remaining hours attached.
Adjacent spreadsheet failure modes in the same APQC Category 9 process group.
Stripe, Adyen, and PayPal merchant clearing reconciliation workbooks
Daily check deposit scan log and manual remittance matching spreadsheet
Accounts receivable aging schedule and unallocated cash spreadsheet
Scope the replacement architecture for manual tracking of customer security deposits and refund deadlines or combine multiple failure modes in the directory.
