Cash-flow modeling guide

Cash Flow Modeling for Companies

A cash-flow model shows how money may move over time. It helps you see when cash actually comes in, when it has to leave, and which parts of the path still depend on an assumption.

A useful model answers more than “how much?” It also answers “when?”, “recorded or expected?”, and “what changes if this assumption moves?”

Timing comes first

Revenue timing and cash timing are different tracks

The same business activity can affect revenue, expenses, and cash in different periods. A model needs to preserve those differences.

A deal may be signed in January, invoiced in February, and paid in March. Revenue context can matter before the cash arrives, but it does not fund payroll in the meantime.

Costs also move on their own schedule. Payroll may leave every month while an annual software renewal creates a larger payment in one period. Averaging both can hide the month when pressure is highest.

A cash-flow model therefore keeps the accounting or commercial event visible while following the separate date when money enters or leaves the business.

Illustrative timeline

One activity, different financial dates

TrackJanFebMarApr

Revenue / accountingDeal signedInvoice sentExpense incurredReview period

Cash timingNo receipt yetNo receipt yetCash arrives
Payroll leaves
Tool renewsNext cash position

Illustrative timing only. Revenue and accounting context are not presented as cash received, and the amounts are not product UI.

Model structure

Build the current cash path before the possible path

The recorded layer explains the cash position created so far. The planning layer shows what might happen if expected receipts and future assumptions occur.

Conceptual model

Recorded cash path and separate planning layer

Starting cashRecorded position

Received cashMoney that arrived

Cash outflowsPayments and obligations

Cash positionMovement over time

Expected receipts + future assumptions + scenariosSeparate planning inputs produce a possible path, not available cash.

Planning framework, not a literal RunwayCal formula. Expected receipts and scenario assumptions stay outside recorded cash until realized.

Keep it current

A model goes stale when timing assumptions stay frozen

The total may still look reasonable while the dates underneath it have stopped matching the business.

Customer pays 20 days late

The revenue context may be unchanged, but the cash arrives in a later period.

Planned hire moves one month

Payroll pressure starts later, so the possible cash path must move with it.

Annual renewal lands early

The annual cost may be familiar, but the earlier cash date changes the near-term position.

Update the model when a material date, amount, or assumption changes. Do not rewrite what already happened to make the plan look right. Keep actual cash movement intact and revise the possible path.

From cash to runway

Cash position is the starting point, not the whole conclusion

Runway changes when the cash position or spending pattern changes. It is a planning measure, not a safety guarantee.

Bank balance alone does not show which obligations are already known or how payment timing may affect the next period. Runway also cannot be understood without the burn or spending pattern used in the calculation.

RunwayCal keeps actuals and planning assumptions separate across Planner and Scenarios. That supports a reviewable model, but finance and leadership still own the inputs, interpretation, and decision.

Revenue is not the same as cash received.
Expected receipts are not available cash.
Plans and scenarios do not overwrite actuals.
Runway is not a prediction guaranteed to hold.

Continue the question

Test the timing before relying on the plan.

Keep received cash, obligations, expected receipts, and scenarios in distinct lanes as you review the possible path.

Explore RunwayCal Explore Planner