Cash flow statements are moving from monthly reports to standing views

Cash was always the number small businesses cared about most and the one they had the least information about. The bank balance was known and everything else was guesswork until the accountant produced a statement months later.

That gap is closing. Most claims about it overstate what the tools do. This page sets out what is structurally different in how cash flow statements are produced and how cash is tracked and forecast, which systems keep a standing view running in the ledger, and what each change asks of the person doing the work.

What counts as a standing view

A standing view is a cash flow statement that lives inside the ledger and refreshes as the bookkeeping is entered, instead of being assembled at period end. QuickBooks Online ships one as its cash flow planner; Xero ships one as its short-term cash flow view. Both build it from open invoices, open bills and recurring transactions already in the books, so the view is only as current as the coding behind it.

What to take away

The direct method becomes affordable

Listing actual cash received from customers and paid to suppliers used to mean summarizing a bank statement by hand. Feeds and coded transactions do that continuously. A statement of where the money actually came from and went is now producible without the reconciliation exercise it used to require.

This is a real gain for owners, because the direct method reads like the question they asked. What it does not do is explain the gap between profit and cash, which is the indirect method's whole purpose. Both are worth having, and the relationship between them is the arithmetic set out in the cash flow statement guide.

The condition attached is coding quality. A direct statement is only as good as the classification of each receipt and payment. A feed that codes by supplier name will put an occasional payment in the wrong section without comment.

The standard behind both statements

ASC 230, the US GAAP topic for the statement of cash flows, covers both methods and encourages, without requiring, the direct one. IAS 7 is the international equivalent for anyone reporting under IFRS. Neither standard has changed; what has changed is the cost of the data underneath.

Forecasting moves inside the ledger

Forecasts used to live in a spreadsheet built once a quarter and abandoned. Now they are produced from the ledger: open invoices with their due dates, open supplier bills, recurring transactions, and a projection of the rest.

The improvement is that the forecast is never out of date. The risk is specific and worth naming. A forecast built from open invoices assumes customers pay on their due dates, and most of them do not. A forecast built from recurring transactions assumes the last twelve months repeat, and annual payments made once do not appear as recurring.

Check two things in any forecast the system produces: what it assumed about collection timing, and whether the annual items are in it. Adjusting the collection assumption per customer, based on actual behavior, is the one change that makes an automatic forecast worth reading.

The evidence comes from the aged report described in the accounts receivable guide.

The thirteen week view becomes ordinary

A rolling short horizon forecast, updated weekly, was once something only businesses in difficulty produced. It has become a normal management habit, partly because producing it is now cheap.

The horizon is long enough to include a quarterly obligation. It is short enough that assumptions are mostly known commitments, not guesses about sales.

The quarterly obligations that matter most here are the IRS ones: employers file Form 941 each quarter, and most owners make quarterly estimated tax payments with Form 1040-ES. The IRS publishes the due dates for both, and your accountant can tell you which apply to you. For a small business, use a rolling three months with annual items marked on it.

What makes it work is being honest about which lines are committed and which are hoped for. A forecast that mixes the two reads as more certain than it is. The discipline of separating them is what the exercise actually teaches.

Outflow timing becomes a setting

Payment runs initiated from inside the accounting system mean the date money leaves is decided by a rule: pay on entry, pay on due date, pay weekly. That rule is set once and then applies to everything.

This is an improvement over paying whenever someone remembered, and it moves a judgment into a configuration screen where nobody revisits it. A setting that pays everything on entry is an interest free loan to every supplier, made permanently, by whoever clicked the option.

The decision belongs with the terms actually agreed, which is the subject of the accounts payable overview. For a worked example of what a written payment rule looks like, the Prompt Payment Act is the rule the federal government pays its own suppliers under: it requires agencies to pay a proper invoice within 30 days and to pay by the discount date when a discount is worth taking.

What has not changed

The last row is where most of the value still sits. Everything above makes the arithmetic cheaper. None of it knows that one customer always pays two weeks late, and the person keeping the books does.

Common questions