Bank Statement Freshness: The 60-Day Rule That Delays Closings
July 10, 2026 · LendPacket team
Bank statements prove liquidity and cash flow AS OF a date — and that proof decays. Most credit policies treat a business or personal bank statement as reliable for about 60 days from the statement's closing date (not from the day the borrower uploaded it — a distinction that quietly wrecks timelines).
The math that matters
A statement covering June 1–30 is "dated" June 30. Under a 60-day policy it supports the file until about August 29 — regardless of whether the borrower uploaded it July 1 or August 20.
Why files collect statements twice
- The team requests "2 months of statements" on day one. ✔️
- The file takes 75 days to reach final underwriting (appraisal, SBA queue, CPA delays).
- The statements are now expired; the request goes out again — usually discovered by the underwriter, at the worst moment.
Three fixes that work
- Track the statement date, not the upload date. Your system (or spreadsheet) should record June 30, not "uploaded July 3."
- Set an expiry alarm. 60 days after the statement date, someone — ideally software — should flag it and re-request automatically.
- Tell borrowers up front that long files need one refresh of bank statements and interims. Framed at kickoff it's routine; sprung at closing it feels like incompetence.
This is exactly what a staleness engine automates: LendPacket reads the closing date printed on each statement, stamps the expiry, flags the file the day it lapses, and (if you enable it) emails the borrower for a fresh copy without anyone on your team touching it.
Stop chasing documents by hand.
Magic-link uploads, AI review on every document, automatic staleness tracking. 14-day free trial, no card.