QuickBooks Financial Signals Library
Cash Flow Signals
Cash problems are rarely surprises to the data — only to the people reading it monthly. These four signals are visible in QuickBooks days to weeks before they become decisions made under pressure.
4 signals · Last reviewed July 22, 2026
The monthly Statement of Cash Flows explains what already happened. Cash review is a different exercise: it asks what is changing now — how fast cash is moving, whether anything moved that shouldn't have, and whether the next three weeks of committed outflows clear the balance that will actually be there.
Each signal below can be checked manually from standard QuickBooks reports. The discipline is doing it on the days you're busy, which is when the signals are most likely to be forming.
1.Cash runway compression
The number of weeks your current cash covers shrinking faster than your revenue and collections pattern explains.
Why it matters
Runway rarely disappears in one event — it compresses gradually while attention is elsewhere, and monthly reporting discovers it weeks late. Caught early, compression is a scheduling problem: sequence payments, accelerate specific collections. Caught late, the same numbers are a crisis.
Common causes
- Collections slowing while spend holds constant
- One-time outflows — tax payments, annual premiums — landing in a cluster
- Growth spending committed ahead of the receipts it depends on
- A seasonal trough arriving on schedule but unplanned-for
QuickBooks records to pull
- Bank balances and the bank register
- Statement of Cash Flows
- A/R Aging Summary and expected receipt dates
- Upcoming bill due dates and the payroll calendar
How to investigate
- Compute weekly net cash change over the trailing four to eight weeks from the Statement of Cash Flows or bank register.
- Divide current cash by the average weekly net burn when that number is negative — that's the runway in weeks.
- List committed outflows for the next three weeks: bills due, payroll, tax drafts.
- Overlay expected collections using customers' actual payment behavior, not invoice due dates.
- If coverage is thinner than your comfort line, sequence payments and start specific collection calls now — not at month-end.
False positives to rule out
- One unusual week distorting the trailing average
- A large deposit in transit that hasn't posted
- An intentional, planned drawdown — equipment, inventory, distributions
Questions to ask next
- Which single action — one collection call, one payment deferral — buys back the most weeks?
- Which committed outflows can actually move without damage?
- Is this a pattern forming or a one-time event passing through?
Illustrative example — not customer data
Cash covered eleven weeks at the start of the month and seven weeks today. Nothing dramatic happened — two large customers quietly slipped from 28-day to 45-day payment while spend held flat. The compression was visible daily; the month-end report would have announced it three weeks from now.
How Flash covers this signal
Flash tracks cash position and runway trend nightly against the company's own history, and flags compression in the morning brief with the drivers attached. Read-only analysis — the decisions stay yours.
Related: QuickBooks Cash Flow Insights
2.Large or off-pattern cash outflow
A cash outflow that is large for your company, off-pattern for that vendor or account, or unrecognized by the person reviewing it.
Why it matters
This one signal catches three different problems while they're still fixable: keying errors (a $500 charge entered as $5,000), autopays for canceled services still drafting, and unauthorized activity. In all three, recovery odds decay by the day.
Common causes
- Keying errors on amount entry
- Autopay continuing after a service was canceled
- Unauthorized or fraudulent ACH and card activity
- Legitimate but unbudgeted spend nobody flagged
QuickBooks records to pull
- The bank register and bank feed
- Check Detail and expense reports
- The vendor's transaction history
How to investigate
- Review yesterday's outflows in the bank register above your materiality line.
- For each: confirm you recognize the vendor, the purpose, and the approver.
- Compare the amount against that vendor's history — is this multiples of their normal charge?
- Verify a supporting document exists: bill, receipt, contract, or approval.
- Escalate anything unrecognized to the account holder the same day; contact the bank immediately for unauthorized items.
False positives to rule out
- Annual or quarterly charges that look unusual only against a monthly cadence
- Known payments that shifted timing
Questions to ask next
- Who approved this, and does the amount match what they approved?
- Which document supports it?
- Is this vendor's charge history consistent with the amount?
Illustrative example — not customer data
A $4,800 ACH posts against a software vendor that has billed $480 a month for two years — one keystroke at renewal. Caught in the next morning's register review, refunded within the week. Caught at month-end, it's a support-ticket archaeology project.
How Flash covers this signal
Flash compares each outflow against that vendor's history and the company's own patterns every night, and flags off-pattern outflows with the record attached. It flags candidates — it cannot move, block, or reverse money.
Related: Vendor spend spike
3.Undeposited funds aging
Customer payments recorded in QuickBooks and sitting in Undeposited Funds ("Payments to deposit") without reaching the bank.
Why it matters
Revenue looks collected while the cash isn't in the bank. Aging undeposited balances hide three distinct problems: deposit runs not happening, physical checks lost or forgotten, and payments recorded twice — once as a payment, once as a direct bank deposit — which overstates income.
Common causes
- Deposit runs simply not made on cadence
- Payments recorded while the physical check sits in a drawer
- Deposits keyed directly to the bank account while the payment stays ungrouped
- Processor settlement timing never cleaned up
QuickBooks records to pull
- The Undeposited Funds account register
- Deposit Detail report
- Bank-feed deposit transactions
How to investigate
- Open the Undeposited Funds account register.
- Sort by date and flag anything older than your normal deposit cycle — two to five business days for most companies.
- Match aged items against bank-feed deposits: an item already deposited but recorded separately means income is double-counted.
- Physically locate items that genuinely haven't been deposited.
- Group and record the deposit, or fix the mismatched entries.
False positives to rule out
- Normal processor settlement lag of one to three days
- Weekend batches posting Monday
Questions to ask next
- Is the payment physically in hand, in transit, or already at the bank under another entry?
- Is any income being counted twice?
- Who owns the deposit cadence, and what broke it?
Illustrative example — not customer data
$6,300 sits in Undeposited Funds across nine checks, the oldest 24 days. Two were already deposited and keyed straight to the bank — income counted twice — and one check is simply in a drawer.
How Flash covers this signal
Flash watches undeposited balances age every night and flags aged items and double-count patterns as candidates in the morning brief. Corrections stay in your hands.
Related: Reconciliation backlog
4.Payroll-window liquidity squeeze
Committed outflows — payroll above all — landing inside a window where projected cash is thin.
Why it matters
Payroll is the one payment you never want to be sequencing under pressure. The same squeeze that is a routine scheduling exercise ten days out is a crisis at two days out. The information difference between those two situations is zero; the timing difference is everything.
Common causes
- Payroll, tax drafts, and rent clustering in the same week
- A large AP run scheduled without checking the cash calendar
- An expected receivable slipping past the window
QuickBooks records to pull
- Payroll schedule and typical run amounts
- Bill due dates and scheduled payments
- Bank balances
- A/R expected receipts
How to investigate
- Map the next three weeks: payroll dates and amounts, tax drafts, rent, committed AP.
- Overlay projected receipts conservatively — use each customer's actual payment behavior, not due dates.
- Compute the low-water mark: the projected balance on the worst day.
- If the mark is thin: move discretionary payments, accelerate one or two specific invoices by phone, and arrange any transfers early.
False positives to rule out
- Over-conservative receipt assumptions triggering alarms every cycle — calibrate to actual cadence
- Intercompany or owner transfers that are planned but not yet recorded
Questions to ask next
- What is the exact low-water date and amount?
- Which discretionary payments can move a week without damage?
- Which single customer call most improves the window?
Illustrative example — not customer data
Payroll on the 14th, the sales-tax draft on the 15th, rent the same day — and projected cash on the 15th is less than one payroll. Seen on the 5th, this is a scheduling exercise. Seen on the 13th, it's the worst day of the quarter.
How Flash covers this signal
Flash projects committed outflows against cash position nightly and flags squeeze windows in advance in the morning brief. It cannot move money or delay payments — it makes sure you see the window while it's still wide.
Related: QuickBooks Cash Flow Insights
Run these checks by hand — or wake up to them done
Everything above works with nothing but QuickBooks and a schedule. Flash Daily Insights runs the same comparisons nightly through a read-only connection and delivers the candidates in a morning brief — what changed, what looks wrong, what to do next. It never changes your books.