Free Cash Flow Forecast Template With Real Examples

cash flow forecast template is a key topic in modern project management and teamwork. A business can report a profitable month and still miss payroll. The reason is timing: a customer invoice may count as revenue when earned, while the cash arrives weeks later; payroll, rent, taxes, and supplier bills still leave the bank on their due dates. A cash flow forecast makes that timing visible before it becomes a crisis.

This guide explains how to build and maintain a cash flow forecast, how it differs from a budget or profit forecast, and how to read a 13-week model. The worked example uses realistic but illustrative numbers; replace them with your own bank, invoice, payroll, and payment data. It is an operating tool, not accounting, tax, or investment advice.

What is a cash flow forecast, and what question does it answer?

A cash flow forecast is a dated estimate of cash receipts and cash payments over a future period. It answers: “How much money should be available, and when?” It is different from a profit report, which follows accounting rules for recognizing revenue and expenses whether or not cash has moved.

A forecast can be a simple spreadsheet or a connected finance model. Its value comes from the logic and timely inputs, not from elaborate software. At minimum, it should show a starting bank balance, expected inflows, expected outflows, and a closing balance for each period.

How is cash flow different from revenue, profit, and a budget?

Revenue is the value of goods or services earned under the accounting basis being used. Profit subtracts recognized costs from recognized revenue. A budget is an approved plan for income and spending. A cash forecast focuses on the dates money is expected to clear the bank. These views overlap, but they are not interchangeable.

Suppose a consultancy completes $30,000 of work on June 20, invoices on June 30, and expects payment on July 30. The revenue may belong in June under accrual accounting; cash does not arrive in June. If $12,000 of payroll is due June 28, a June profit figure may look acceptable while the June bank balance falls. A cash forecast makes the mismatch explicit.

When is a forecast most useful?

It is especially useful when receipts are uneven, customers pay on terms, payroll is fixed, a large purchase is approaching, or financing depends on demonstrating a credible plan. It can also show when a business has cash to hire, repay debt, build a reserve, or invest—provided the model includes restrictions, tax obligations, and upcoming commitments.

A forecast does not guarantee cash will arrive. Its job is to identify exposure early enough to act: follow up a late invoice, delay a discretionary purchase, negotiate supplier timing, or arrange financing before an urgent shortfall.

How do you build a cash flow forecast step by step?

Start with verified cash, forecast receipts and payments by their likely bank dates, and calculate a closing balance for each period. Keep source data and assumptions visible so another person can trace how every important number was produced.

1. Choose the horizon and time buckets

For near-term control, use a rolling 13-week forecast with one column per week. Weekly buckets are detailed enough to reveal payroll and supplier timing without pretending you know the exact daily position months ahead. For strategic planning, extend the view by month for 12 months or more, but treat later periods as less certain.

Choose a consistent week-ending date and define whether the opening balance is measured at the start of the week or after the prior week closes. Be consistent about weekend and holiday payment dates. A bank holiday can move a planned receipt or debit, so the settlement date matters more than the invoice date.

2. Establish the opening cash balance

Use cleared balances from all relevant bank accounts as of one stated cut-off. Reconcile transfers between accounts so the same money is not counted twice. Separate cash that is legally restricted, held for a specific purpose, or unavailable under a loan covenant; showing it as freely spendable can create a dangerously optimistic result.

If a bank statement shows $84,000 but $6,000 of uncleared payments are already committed, document how the forecast treats them. Either start with the bank’s cleared balance and place those payments in the forecast, or start with a reconciled available balance and do not count them again. Write down the method.

3. Forecast receipts on expected collection dates

List material inflows by customer, invoice, expected amount, and expected clearing week. Use the best evidence available: contractual due dates, customer payment behavior, confirmed remittance advice, recurring billing records, and collection-team updates. Do not simply copy the revenue budget into the receipts line.

For invoices with uncertain timing, use a probability-weighted estimate only if the probability has a clear basis. For example, a $20,000 invoice with an estimated 70% chance of arriving in week 4 contributes $14,000 to a probability-weighted planning view. But a cash-at-risk scenario should also show the full $20,000 arriving late or not arriving within the horizon. Averages can hide a shortfall.

Include other receipts where relevant: card settlements net of fees, grants when conditions and dates are met, tax refunds when sufficiently evidenced, loan proceeds only when committed, and owner contributions only when approved. Exclude unsigned deals and speculative financing from the base case.

4. Forecast payments by due date

Start with fixed and committed items: payroll and employer costs, rent, utilities, debt service, supplier invoices, subscriptions, insurance, and tax payments. Then add variable costs using an operational driver, such as units shipped, billable hours, commissions, or planned hiring. Include one-off items such as equipment deposits, annual renewals, and project milestones.

Distinguish a purchase order, an invoice, and a cash payment. A purchase order may indicate a future commitment; an invoice may have a due date; the bank debit may clear later. Use the expected cash date, and preserve enough detail to see the underlying commitment. Do not move a payment date merely to make the forecast balance work.

5. Calculate the roll-forward

For every period, use the same simple identity:

Closing cash = Opening cash + Total receipts − Total payments

Then carry the closing cash into the next period as its opening balance. In a spreadsheet, one row per cash line and one column per week makes the arithmetic easy to inspect. A separate reconciliation line for transfers and financing prevents unexplained adjustments from hiding in the totals.

6. Check, challenge, and assign ownership

Ask budget owners to confirm their major assumptions and dates. Check the forecast against bank activity, accounts receivable, accounts payable, payroll calendars, and signed contracts. Name one owner responsible for maintaining the model, and name owners for material assumptions. Shared responsibility without a clear owner often means stale data.

What should a cash flow forecast template include?

A practical template includes the time period, opening balance, categorized receipts, categorized payments, net movement, closing balance, assumptions, source, owner, and actual-versus-forecast variance. The level of detail should help somebody decide what to do without making updates so laborious that they stop happening.

Use categories that match how decisions are made. If supplier payments are the main source of uncertainty, split them by vendor or due-date group. If customer receipts are the risk, show the largest invoices individually. Too much detail for immaterial lines makes a template harder to maintain; too little detail hides the drivers.

How do you build a filled 13-week cash flow forecast?

The example below shows an illustrative service business starting with $50,000 of available cash. Each weekly total includes expected receipts and all forecast payments. All amounts are in thousands of dollars, and the closing balance is calculated using the roll-forward formula. It is a base-case forecast, not a guarantee.

The arithmetic can be checked row by row. Week 1 closes at $50,000 + $18,000 − $22,000 = $46,000. Week 2 opens at $46,000 and closes at $46,000 + $12,000 − $20,000 = $38,000. After 13 weeks, receipts total $285,000, payments total $300,000, and net cash use is $15,000; therefore $50,000 − $15,000 = $35,000 at the end. The lowest weekly closing balance is $27,000 in week 12, so that week—not just the final balance—deserves attention.

Suppose the business sets an internal minimum operating cash floor of $30,000. That is a management threshold for this example, not a universal rule. The base case falls $3,000 below the floor in week 12. Management can now investigate the specific week: $18,000 of receipts are expected, while payments are $26,000. If a $12,000 customer payment scheduled in week 13 has weak evidence, shifting it later would deepen the trough. The correct response is to verify collection timing, test alternatives, and decide early—not to edit a formula until the warning disappears.

This example also demonstrates why totals alone are insufficient. The 13-week net movement is only negative $15,000, but the path includes a $27,000 low point. A business may not be able to use week 13’s eventual recovery to pay a week 12 obligation. Cash timing is the point of the forecast.

How should you model scenarios and cash runway?

Use a base case that reflects the most evidence-supported dates, then build downside and upside cases by changing explicit drivers. A scenario is useful when it explains what would have to happen for cash to improve or deteriorate; a hidden blanket percentage adjustment is harder to challenge.

For the example above, a downside case might assume that $12,000 of week 13 receipts arrive in week 15 instead. The 13-week ending cash becomes $23,000, and the lowest balance may occur in week 13. An upside case could move a confirmed $8,000 collection from week 8 to week 6, but it should only be treated as an upside if the customer confirms payment. Keep each change visible in an assumptions log.

Cash runway is a rough way to express how long current cash may last, often used by businesses with recurring net cash outflows. A simple estimate is available cash divided by average monthly net cash burn. If an early-stage firm has $240,000 of available cash and has used an average of $40,000 net per month over the last three months, the simple estimate is six months. This is not a substitute for a dated forecast: a large tax bill, annual renewal, or customer collection can make actual runway materially shorter or longer.

A sensible scenario set usually asks:

• Base: What happens if expected collections and planned payments occur on the current best estimates?
• Downside: Which few plausible changes create the earliest or largest cash gap—for example, a major customer paying 30 days late or an urgent repair?
• Upside: What improves if a specific, evidenced receipt lands early or discretionary spending is deferred?

Do not combine every imaginable bad outcome into a single theatrical worst case. Use a severe but plausible case to plan actions, and identify the trigger that would cause the team to move from base to downside assumptions. A forecast is not useful if no one knows when its scenario should change.

Which assumptions matter most, and how do you test them?

The most important assumptions are usually collection timing, sales conversion, payroll dates and headcount, supplier terms, taxes, debt payments, and one-off commitments. Record an assumption’s value, evidence, owner, date reviewed, and what would invalidate it.

Test one driver at a time to understand its impact, then combine only scenarios that could realistically occur together. In the example, moving $12,000 out of week 13 reduces the end-of-horizon cash from $35,000 to $23,000. If the cash floor is $30,000, the change creates a $7,000 gap at the end; it does not mean the company should assume the receipt will never arrive. The scenario makes the exposure measurable and gives the team a collection target or financing amount to discuss.

How often should you update the forecast and explain variance?

For a short-term 13-week cash forecast, weekly updates are a practical starting point; update more often when liquidity is tight or payment activity changes quickly. Reconcile the prior week’s forecast with cleared bank activity, then roll the horizon forward by one week. Monthly review alone can miss a short-term trough between reporting dates.

A disciplined weekly cycle can take four steps:

1. Close actuals: Import or verify cleared receipts and payments through the cut-off date. Identify transfers and uncleared items consistently.
2. Compare: For each material line, calculate actual minus forecast and distinguish amount variance from timing variance.
3. Explain: Record the reason, owner, and corrective action. “Customer paid $10,000 one week late; account manager confirmed Friday remittance” is useful; “timing” alone is not.
4. Reforecast: Adjust future dates or amounts only when new evidence supports the change. Preserve a dated prior version so forecast accuracy can be reviewed.

A timing variance is not automatically a permanent loss. If a $15,000 receipt expected in week 4 arrives in week 5, week 4 is $15,000 worse than forecast and week 5 is $15,000 better, assuming it arrives in full. An amount variance is different: if only $12,000 arrives, the remaining $3,000 is still outstanding or disputed. Tracking the two separately avoids treating a delayed receipt as if it vanished—or assuming a short payment will catch up without evidence.

Useful measures include the lowest forecast cash balance, the week it occurs, total net cash movement, overdue receivables, and the size and age of forecast errors on material items. Do not optimize for a single accuracy score. A forecast may have a reasonable average error but still miss the one week in which payroll cannot be met.

What are the benefits and trade-offs of cash forecasting?

A forecast improves visibility and decision lead time, but it depends on data quality and can create false confidence if users treat estimates as facts. The best method is the simplest model that is updated reliably and makes uncertainty visible.

Benefits: It reveals timing gaps before they occur, supports collections and payment conversations, helps compare hiring or investment timing, and gives managers a shared view of assumptions. A weekly model can also expose operational causes, such as delayed project acceptance holding up invoices.

Trade-offs: A detailed model takes time to maintain; small businesses may not have clean invoice dates or reliable payment histories. Forecasts can look precise despite uncertain inputs. A highly aggregated model is faster but may hide which customer or vendor causes the trough. The answer is not always more rows: show large and uncertain items separately, group stable recurring costs, and label uncertainty honestly.

A spreadsheet is often sufficient when one owner can reconcile data and the number of material transactions is manageable. Accounting or treasury software may help when multiple entities, currencies, bank accounts, or approval workflows make manual consolidation risky. More automation can reduce copying, but it does not decide whether a pipeline opportunity is likely to close or whether cash is restricted. Human review remains necessary.

What mistakes make a cash flow forecast unreliable?

The most common failures are mixing accrual revenue with expected cash receipts, using an unreconciled opening balance, omitting irregular bills, and changing assumptions without recording why. Each makes the forecast easier to read but less useful for decisions.

• Treating booked sales as cash: Include the expected collection date, not just the signed contract or invoice date.
• Counting the same item twice: Reconcile opening cash, uncleared payments, inter-account transfers, and loan proceeds.
• Ignoring irregular obligations: Add insurance renewals, tax installments, annual software, equipment deposits, and debt maturities.
• Using averages to erase a trough: Monthly totals can conceal that payroll is due before the month’s largest customer receipt.
• Putting uncertain receipts in the base case as certain: Separate confirmed, likely, and speculative money; test late or missing payments.
• Making the model balance by assumption: Do not defer a vendor payment or accelerate collections without evidence and an owner responsible for the action.
• Failing to compare forecast with actual: Without a variance loop, the same mistaken assumption repeats next week.
• Confusing cash with profit: Financing can raise cash without creating revenue, and depreciation can reduce accounting profit without an immediate cash payment.

The forecast should be challenged, not defended. If it repeatedly predicts receipts earlier than they arrive, change the collection assumption using actual history. If actual vendor payments routinely exceed the model, examine the cause—scope, price, tax, or coding—rather than adding an unexplained buffer to every week.

How can teams keep forecast ownership and actions clear?

Give one person responsibility for publishing the current forecast, but require input from the people who own receipts and payments. The owner should keep assumptions, due dates, and action decisions connected so the forecast leads to follow-through instead of becoming a static finance file.

For example, an account manager can own confirmation of a $25,000 customer receipt; procurement can confirm whether a $9,000 supplier deposit is contractually due; the finance owner updates the model and flags the resulting low point. Record the action next to the forecast line, with a date to revisit it. This makes the forecast operational without making every department edit formulas.

Teams that coordinate project delivery alongside financial commitments may find a shared workspace useful for assigning owners, tracking milestone dates, and reviewing progress. Doitify supports project and team management, including tasks, owners, schedules, reports, and finance management features. It can help teams coordinate the work behind forecast assumptions, but it is not a replacement for accounting controls, a bank reconciliation, or professional cash-management advice. Disclosure: Doitify is our product; consider whether its project-management capabilities fit your workflow before adopting it.

Conclusion

A useful cash flow forecast is not a promise that every payment will happen on schedule. It is a transparent, dated model that links opening cash to receipts, payments, and closing cash, then improves as actual results reveal which assumptions were wrong.

Start with a reconciled bank position, build a 13-week view around expected clearing dates, and identify the lowest projected balance. Challenge the receipts and irregular payments that drive that low point, test a plausible downside, and assign owners to the actions. Review actual-versus-forecast weekly when liquidity is important. That routine turns a spreadsheet into an early-warning system—and gives you time to make decisions while options are still available.

If this post on cash flow forecast template was helpful, you might also enjoy How to Track Project Progress: Metrics That Matter and Project Manager vs Business Analyst: Key Differences Explained (2026).