How to Build a Startup Cash Flow Forecast
A cash-flow forecast estimates when money enters and leaves the business and how much cash remains. It differs from a profit forecast because invoices, stock purchases, loan repayments and other items affect cash at different times from accounting revenue or expense.
Use weekly periods when near-term timing is important and monthly periods for a longer planning horizon. Maintain the forecast from actual bank balances and a clear list of assumptions.
Start with available opening cash
Reconcile bank balances at the forecast start date. Identify restricted balances or funds held for others separately. Do not count an undrawn loan, an expected investment or an overdue invoice as cash already available.
Then list receipts by expected payment date. Separate collected sales, contracted customer payments, uncertain pipeline and financing. Use the customer’s payment behavior and actual terms where known. A forecast can include uncertainty, but it should not hide that uncertainty inside one confident number.
Build the forecast from a dated receipt register
Create a list of expected customer receipts before summarizing them into periods. Record the customer, invoice or contract reference, amount, due date, expected payment date and confidence basis. Keep unpaid historic invoices visible rather than repeatedly moving them forward without explanation.
Separate scheduled receipts from sales opportunities. A signed order with a deposit due differs from a proposal awaiting approval. If pipeline is included in a scenario, label it as an assumption and show the effect if it does not convert. Do not let an estimated probability obscure a payment that cannot arrive before a procurement process finishes.
For payment processors, consider when funds settle into the usable bank account and any reserve or restriction relevant to the actual arrangement. The sale date is not necessarily the cash date. Verify the provider’s terms and account behavior instead of using a generic settlement assumption.
Schedule payments when they are due
Include payroll and associated obligations, supplier invoices, rent, software, insurance, taxes, loan interest and principal, capital purchases and planned distributions where applicable. Avoid duplicating card purchases and the later card settlement. State whether tax amounts are included and obtain local accounting advice on their treatment.
For each period, closing cash equals opening cash plus receipts minus payments. The next period’s opening cash equals the previous closing balance. Use a consistent sign convention so an outflow is not accidentally subtracted twice.
Prepare a commitments register for payments
List known obligations before adding discretionary plans. Include supplier invoices, payroll, taxes, debt payments and contracted subscriptions with their timing. Separate items already committed from spending the team can still choose not to incur.
For planned purchases, show deposits, intermediate payments and final balances when applicable. A single total in the delivery month can conceal an earlier funding need. If an item is purchased by card, avoid counting both the purchase as a bank outflow and the later settlement of the same amount.
Discuss tax and accounting treatment with the appropriate adviser. The forecast can show expected payments without determining the underlying legal liability. Record the source of each amount, especially where a deadline or estimate comes from someone outside the team.
Worked example: a three-week forecast
All amounts below are hypothetical currency units. Opening available cash is 30,000.
| Period | Opening cash | Receipts | Payments | Closing cash |
|---|---|---|---|---|
| Week 1 | 30,000 | 8,000 | 12,000 | 26,000 |
| Week 2 | 26,000 | 4,000 | 18,000 | 12,000 |
| Week 3 | 12,000 | 20,000 | 10,000 | 22,000 |
The forecast ends above zero, but week two is the low point. If an internal reserve is 15,000, the team needs an action before that week. If 10,000 of week-three receipts arrives a week late, week-three closing cash becomes 12,000 rather than 22,000.
Inspect dates within each week too. A payroll payment on Monday and a customer receipt on Friday cannot offset each other in time merely because they sit in the same column. For a tight period, switch to daily detail.
Inspect the lowest balance, not only the closing column
Calculate the minimum within the forecast horizon and identify which receipts it depends on. If one large receipt arrives just before a major payment, test a delay. A positive ending balance may rely on timing with little room for error.
Extend the hypothetical three-week example. If the 20,000 expected in week three includes a single 15,000 invoice, delaying that invoice leaves only 5,000 of receipts that week. Starting from 12,000 and paying 10,000 would produce closing cash of 7,000. The business needs to understand that dependency before assuming week three restores its reserve.
When timing is tight, use daily detail around the relevant dates. Keep the rest of the model simpler if that remains sufficient. Granularity should resolve a decision rather than make the spreadsheet harder to maintain everywhere.
Build scenarios from explicit assumptions
Create a base case and a downside. Change concrete drivers such as payment delays, lower order volumes, supplier deposits or a missed renewal. Avoid making every line move by the same percentage when the mechanisms differ.
Attach proposed actions to the forecast with their dates and costs. Negotiating payment terms may help, but it is not a saving until the counterparty agrees. An expected financing round should remain separate from committed funds. A forecast that assumes every rescue action succeeds will conceal the decision it is meant to inform.
Act on the low point
Use the forecast to choose when to collect, negotiate, reduce uncommitted spending or seek appropriate finance. Review the consequences of delaying payments and avoid treating statutory or contractual obligations as optional. If the business may be unable to meet obligations, obtain local professional advice promptly.
Create a response ladder with realistic dates
Choose actions before the forecast breaches a meaningful threshold. For each action, record the decision date, owner, expected cash effect, implementation delay and dependencies. A negotiated payment extension is not confirmed until agreed.
Possible actions include correcting overdue invoices, changing a prospective purchase, narrowing a planned project or seeking suitable finance. Consider customer, supplier and legal consequences. Do not treat nonpayment of obligations as an ordinary savings lever.
Show the cost of the response too. Emergency shipping, refinancing or changing suppliers may improve one timing problem while creating another. Where financial distress is possible, seek local professional advice early using the full facts and proposed actions.
Update from actual results
Replace completed periods with actual receipts and payments. Explain material differences: timing, volume, price, unexpected costs or an incorrect assumption. Correct the underlying driver rather than simply changing the final balance.
Assign one owner to maintain the model and another person to review important inputs where feasible. Keep a dated version or change record. A spreadsheet with many formulas can still be unreliable if nobody knows which receipts are speculative.
Use variance analysis to improve assumptions
For completed periods, compare actual receipts and payments with the forecast version used for decisions. Explain differences as timing, volume, price, new commitments or errors. A receipt delayed one week should not be mistaken for a permanent revenue loss, although repeated delay can still be consequential.
Track assumptions that repeatedly fail. If a customer routinely pays later than terms, use a realistic expected date while continuing appropriate collection work. If forecast sales consistently arrive too early, revise the buying-cycle assumption instead of repeatedly increasing confidence in the same schedule.
Keep an owner and review cadence appropriate to cash pressure. A stable business may update less frequently than one approaching a tight payment week. Everyone who can create significant commitments should know how those commitments enter the forecast.
Maintain a usable model
Keep input cells, calculations and actuals distinguishable. Include checks that opening balances roll forward and that totals reconcile. Protect formulas where useful without making the model impossible for the owner to update.
The forecast should be simple enough to explain. If nobody can identify why next month’s cash changes, add an explanation before adding more scenarios. Reliable dated inputs and clear decisions usually matter more than a visually elaborate model with unexplained assumptions.
Connect the forecast with funding choices and downturn scenarios. Your next step is a dated near-term forecast with a clearly identified minimum balance, uncertainty range and owner for the first required response.