CFO

Availableapp.erp.io/cfo/cash-flow

Cash flow

A forecast built from what is committed plus what is expected. The gap between those two is where the risk lives.

Committed
Open AR and AP
Expected
From history
Scenarios
What-if on the same base
Runway
Cash over net burn

What the forecast is made of

ComponentSourceConfidence
Cash todayReconciled bank balances.Fact
Money coming inOpen invoices, adjusted for how that customer actually pays.Good
Money going outOpen bills and recurring costs.Good
Expected revenuePatterns in your history.Estimate
Everything elseNot visible to the ledger.Missing

The value of the first three lines is that they are near-certain, and most short-horizon cash surprises are actually in them — an invoice you knew about, from a customer who always pays at 60 days rather than 30. Adjusting expected receipts by each customer's actual behaviour is where most of the accuracy comes from.

app.erp.io/cfo/cash-flow
Cash flow

13 weeks · base case

Scenario
Projected closing cash by month
April£104k
May£93k
June£99k
July£84k
August£73k
A 13-week forecast. Committed items are solid; expected ones are estimates.

Scenarios

A scenario applies changes to the base forecast — hire two people, lose the largest customer, delay a purchase, raise prices by five percent — and shows the effect on runway. Scenarios do not alter anything; they are a view.

  1. Model the bad one first. The scenario worth having ready is the one you would not choose.
  2. Change one thing at a time, at least initially. A scenario with six changes tells you nothing about which mattered.
  3. Check what the base assumes before layering onto it. A scenario built on an optimistic base is optimistic twice.
  4. Re-run after the close, when provisional figures become final.
The forecast cannot see what you have not recorded

A signed contract that has not been invoiced, a price rise agreed verbally, a redundancy planned for June, a tax payment on a date the ledger has never seen — none of these are in the forecast. That is not a defect; it is the boundary of what a ledger knows. The forecast is a floor to reason from, not a prediction.

What this does not do

No pipeline-weighted revenue

CRM opportunities do not feed the forecast.

No tax calendar

Payment dates are not known unless recorded as bills.

No multi-currency forecasting

One base currency.

No saved scenario comparison

Scenarios are views, not stored versions to compare side by side.

Questions

How far out does it forecast?

Weeks to months. Accuracy falls off sharply past the committed items.

Does it use invoice due dates or payment behaviour?

Behaviour where there is enough history, due dates otherwise.

Can we export the forecast?

Yes.