Why "the client pays on Fridays" is the riskiest line in a cash forecast

A cash forecast is only as good as the assumption feeding it, and the assumption almost everyone gets wrong is the same one: that a client who says "we pay on Fridays" will actually pay on Friday.

Roughly 49% of invoices sent by small businesses get paid late. That's not a rounding error to wave off when mapping the next six weeks of a bank balance: it's the single biggest reason a forecast can say everything's fine right up until it isn't.

The gap is not a bookkeeping error, either. Standard accounting counts revenue the moment an invoice goes out, whether or not the client has actually paid it: accurate for tax purposes, and close to useless for knowing what you can spend this week. A forecast built on invoice dates instead of payment dates just carries the same mistake into a new spreadsheet.

The safe-estimation rule that keeps a forecast honest

The Cash Flow System for Small Businesses illustrates the fix with two freelancers who hear the identical promise from a client and handle it differently.

Leo finishes a project Monday and invoices $3,000. The client says payments go out Fridays. Leo enters the full $3,000 into week one of his forecast, sees a healthy ending balance, and buys a new desk. Friday comes and goes: the client's bookkeeper was out sick. Leo now has a negative balance and a bounced-check fee.

Maya hears the same promise and applies what the book calls the safe-estimation rule: assume the check runs late, and discount the amount for the risk of revisions or delay. She enters $2,500 into week three instead of $3,000 into week one. When her forecast shows things are tight without that money, she skips the desk. When the payment is delayed exactly like Leo's was, she's fine, because she never spent money she didn't yet have.

The forecast itself is a simple weekly roll-forward (beginning cash, plus expected inflows, minus known outflows, equals ending cash, which becomes next week's beginning cash) repeated six weeks out. Each week's numbers split into hard obligations, the bills you're certain about, and soft income, the money you're merely expecting, which is exactly where Maya's discipline comes in: soft income gets the haircut, hard obligations get taken at face value. Each ending balance then gets a color:

• Green: positive with a real buffer. Proceed as planned.
• Yellow: positive, but thin enough that one late payment or surprise expense flips it. Delay non-essential spending and double-check outstanding invoices.
• Red: projected negative. Stop and fix it now, while there are still weeks of runway to act in.

The point of running this six weeks out rather than checking the bank balance daily is that a red week found in week four is a problem you have a month to solve, not a crisis you're already inside.

Where people go wrong

Leo's mistake (entering the optimistic number instead of the realistic one) is the first failure mode, and it's the one that undoes the whole exercise even when the spreadsheet itself is built correctly.

The second is treating a red light as a verdict rather than a warning. In the book's framing, seeing a negative ending balance in week five feels like discovering you've already failed. It isn't: it's a working system doing exactly its job, four weeks before the shortfall would have hit with no notice at all. A red light found early is closer to a save than a loss.

The third is fixing the immediate gap without checking what it moved. Delaying a payment or pulling from a buffer to green up week four can quietly create a new red week five or six later, and the fix only counts once the whole six-week timeline is recalculated and confirmed clear. Where this forecasting habit fits alongside the business-model and pricing decisions that determine how money arrives in the first place is covered in the money and pricing guide.