A cash forecast that starts as a spreadsheet is fine. A cash forecast that stays a spreadsheet, updated by hand after every approval, is a second job.

The model is only as current as the last paste. If invoices live in a queue, the forecast should read that queue.

You do not need a data warehouse to stop copying due dates into a workbook every Friday.

Let the queues feed the model

Approved payables with due dates are cash out. Open receivables with expected collect dates are cash in. A simple forecast is those two lists over the next few weeks.

Scenarios still belong in a sheet if you need them: delay a customer, pull a vendor forward. The base case should not require a paste.

What to stop copying

Stop copying invoice status. Stop copying due dates. Stop renaming files Forecast_v18.

Keep the sheet for assumptions: hiring, a one-time tax, a delayed customer you are not ready to put on the invoice yet.

• Feed AP due dates from the live queue.
• Feed AR expected dates from the same system.
• Leave one-off assumptions in a workbook, labeled as assumptions.

A forecast people will actually open

Controllers ignore models they cannot trust. Trust comes from seeing the same invoices they already approved. If the forecast disagrees with the queue, they will use the queue.

So make the forecast a view of the queue, then add the few assumptions on top. Do not rebuild invoices inside the model.

Weekly, not theatrical

A weekly look at the next four weeks is enough for most teams. A 13-tab model that nobody opens is not a forecast. It is storage.

If a number in the model cannot be traced to an invoice or a labeled assumption, drop it.

• Trace every outflow to an approved invoice or a named exception.
• Review four weeks, every week, from the same board.
• Delete lines you cannot source.

When the sheet is still useful

Use a workbook for board packs, tax timing, and scenarios that are not yet invoices. Do not use it as the AP system of record.

If two people maintain two forecasts, pick the queue as the source and let the sheet be a view.

• Keep scenarios in a labeled workbook.
• Do not maintain a second AP list inside that workbook.
• Point everyone at the same operations queue for base cash.

Forecast in Control

Control builds a simple forecast from payables and receivables already in the queues. It is not a full FP&A suite. It is the base case you can defend.

Keep the spreadsheet for the few assumptions that are not yet invoices. Let the queue do the rest.

• Let live AP and AR queues feed the base forecast.
• Keep unlabeled paste-work out of the model.
• Use Control for the queue-backed base case, and a sheet only for named assumptions.