The Small Business Operating Handbook
Chapter 6 of 10 · 10 min read
Build a practical thirteen-week cash forecast
Forecast dated inflows and outflows, identify gaps early and plan payment decisions before a cash shortfall.
The bank balance is a snapshot. The cash forecast is a calendar of what must happen next. A profitable business can still struggle when customers pay later than suppliers, employees or tax authorities require payment.
Use weekly time buckets
Create thirteen columns for the next thirteen weeks. Start with the reconciled opening bank balance. Add expected customer receipts in the week likely to be paid, not merely the invoice due date. Subtract payroll, suppliers, rent, tax, debt payments, equipment and other cash outflows in their expected weeks.
Closing cash = opening cash + actual or forecast cash received − cash paid.
The next week’s opening cash equals the preceding week’s closing cash. Maintain a separate line for restricted or reserved funds so the report does not overstate spendable cash.
Three classifications for each line
Confirmed: banked cash, approved payment or reliable contractual due date. Expected: credible but uncertain payment based on customer history. Possible: opportunity not yet ordered or likely to slip. A prudent model keeps possible receipts out of the survival baseline and shows them separately.
Worked cash illustration
Suppose opening cash is $14,000. In week one the business receives $4,000 and pays $11,000: closing cash is $7,000. Week two receives $2,000 and pays $9,000: closing cash is $0. If $3,000 of week-two payments must occur before the $2,000 receipt lands, the account can run short before the weekly closing balance suggests. For tight cash, forecast daily within high-risk weeks.
Weekly operating rhythm
Every Monday: reconcile the bank; mark actual receipts and payments; update overdue invoices; confirm payroll and statutory obligations; review the minimum forecast balance; agree action owners. Every Friday: compare forecast against actual, investigate surprises and move the thirteen-week window forward.
Response hierarchy when the forecast goes negative
First verify that the dates and balances are correct. Then contact customers about legitimate outstanding amounts, discuss supplier terms before the due date, remove discretionary commitments, accelerate approved invoicing or adjust delivery timing. Financing is a separate decision with costs and risks; do not assume it is the default answer.
Never defer legally required employee entitlements or taxes without obtaining suitable advice about permitted arrangements. Record payment commitments and communications.
Minimum cash floor
Decide on an operational reserve that reflects the business’s largest near-term commitments, volatility, refund risk and payment concentration. A reserve is useful only if the weekly model tests against it. Do not assume that a universal number of months fits every organisation.
Exercise
Build a sheet with rows Opening cash | Customer receipts | Other receipts | Payroll | Suppliers | Rent and overheads | Taxes | Debt and assets | Closing cash | Available reserve | Variance. Highlight every week below the chosen cash floor. Document the action and owner for each highlighted week.
Cash-flow examples use simplified timing and exclude GST mechanics where not stated.
Extended study: professional practice
Create a reliable opening position
A forecast begins from a reconciled bank balance, not a figure remembered from the banking app. Compare bank accounts with the bookkeeping ledger, investigate unpresented transactions and separate restricted or earmarked amounts such as tax provisions and customer money that has an associated obligation. If several bank accounts serve the business, consolidate them only after eliminating internal transfers. Record the opening date and distinguish cleared funds from money still in transit. The forecast is only as trustworthy as its starting position, so one unexplained difference should be investigated before making large payment decisions.
Schedule receipts by expected collection
For each open customer invoice, record amount, due date, payment history, dispute status, person responsible and the most plausible cash date. An invoice due on Friday might arrive next Tuesday. If the customer has disputed quality, do not model it as certain. New sales prospects should remain in a separate scenario until sufficiently committed; optimistic expected revenue is not immediately available bank cash. Keep a visible distinction between invoiced, contractually committed, forecast and speculative receipts. When customers pay partial amounts or deductions, enter the actual amount and track the remaining claim separately.
Forecast all payments, including irregular ones
Create groups for supplier payments, employee costs, superannuation, tax, insurance, finance commitments, licences, rent, asset purchases and refunds. Check supplier statements and contracts for dates that do not occur monthly. For instance, an annual insurance renewal can be missed by a forecast based only on recent average expenses. Payment timing may depend on payment method, cut-off date or weekends. Do not assume money will arrive on the same day a bill must leave. If a large obligation has no confirmed amount, record a conservative estimate with the reason and refresh it.
Use forecast variance as evidence
After each week, compare actual cash receipts and payments with last week’s forecast. Classify differences as timing, volume, price, missing item or recording error. If a $5,000 receipt moved from week one to week three, the total over thirteen weeks may be unchanged while short-term liquidity deteriorates. Preserve the prior forecast to assess accuracy instead of overwriting history without a trace. Track cumulative variance and repeated causes. A recurring late-paying customer should change future collection assumptions even when the contractual due date has not changed.
Prepare a cash response playbook
When the projected balance falls below the agreed floor, first check the records and assumptions. Next prioritise legitimate collection of overdue invoices, identify avoidable discretionary spending, revise new purchases, communicate early about supplier arrangements and correct invoicing delays. For cash constraints affecting wages, tax, super or other legal obligations, obtain qualified advice immediately rather than quietly delaying payment. Record the actual decisions, approvals and revised forecast after each action. Last-minute decisions often carry higher cost, so the playbook should be rehearsed before a crisis.
A three-week practical example
Assume week one opening cash of $21,000, receipts of $6,000 and payments of $11,000: closing $16,000. Week two receipts of $2,000 and payments of $13,000: closing $5,000. Week three receipts of $14,000 and payments of $9,000: closing $10,000. The lowest weekly closing position is $5,000, but daily payment timing might be worse. Now delay $8,000 of week-three receipts into week five: week-three closing cash becomes $2,000. The example illustrates why a forecast should contain timing assumptions and why a reserve floor triggers action before the balance reaches zero.
Operational worksheet
Create a ledger with date, counterparty code, explanation, expected week, likelihood, amount, GST treatment, evidence and owner. Establish a weekly rule for marking each line confirmed, changed or unresolved. Run a thirteen-week base case and at least one delayed-receipts scenario. The weekly review should produce the lowest projected cash balance, the next three largest payments, the five largest expected receipts and named actions for every uncertainty. See the official Australian Government cash-flow guide for supporting educational resources.
Primary learning references
- Australian Government small-business guidance.
- ATO for current Australian tax and super requirements.
- Fair Work Ombudsman for employment requirements.
Study note: Worked numbers and scenarios are educational illustrations, not actual client records or promises of commercial results.
Implementation laboratory: liquidity planning and cash response
Define a realistic starting point
Before changing anything, create a baseline record dated at the beginning of the exercise. State what is currently happening, who owns the process, what happens when it fails, and what evidence is available. For this topic, give special attention to tax and payroll falling due before customer receipts. A single recent incident is not necessarily a representative trend, so look for several examples where available. If the process is entirely new, say that there is no observed baseline and use a synthetic rehearsal rather than describing assumptions as history.
Write a one-sentence objective in the form: “Over the next four weeks we want to improve [measurable outcome] while maintaining [quality or safety requirement].” Avoid using a vague outcome such as working harder, being more professional or creating growth. A useful objective contains an observable difference and a control that prevents apparent efficiency from concealing new problems.
Identify the people and decision boundaries
Consider the different responsibilities of the accounts receivable, purchasing, owner and accountant. In a microbusiness one individual may hold several roles, but those roles should still be conceptually separated. Identify who prepares the information, who checks it, who approves a change, who carries it out and who records the result. If outside advice is required, identify the point at which the process must pause for that advice. Avoid giving software or an AI assistant implicit authority to make legal, financial or employment commitments.
Prepare a short responsibility table with the columns Input owner, Process owner, Independent check, Final approver and Backup contact. For a sole trader, the independent check may be a periodic external professional review instead of a second employee. The objective is accountability, not artificial complexity.
Build a small evidence package
An evidence package should contain the current procedure, one or more real or simulated examples, relevant figures, the expected output and a list of known exceptions. Remove confidential personal information from teaching materials. For a real business, store operational evidence in an approved private location with access limited to the people who need it. Link each figure to its source instead of copying it manually between documents without a reference.
Separate observed facts from forecasts and estimates. An observed payment date is a fact; a future customer’s payment is an assumption, even when it is a reasonable one. A change in accounting classification or business circumstances may alter which facts are comparable. Mark missing information explicitly and assign responsibility for collecting it.
Work through an exception rather than only the easy case
Normal scenarios are useful for learning the steps; exceptions test the quality of the process. Imagine that tax and payroll falling due before customer receipts occurs just before an important customer or statutory deadline. Which facts would you need immediately? Which decisions can be made under the existing authority? Which tasks could be paused safely? How would the customer, supplier, employee or adviser be informed where appropriate? What written record would be necessary to explain the response later?
Run the situation twice. First follow the present procedure. Then follow the improved procedure and compare clarity, elapsed time, error risk and confidence in the information. Note where the new approach merely moves work to another person. An effective improvement should not reduce one person’s workload by hiding costs or risk elsewhere.
Choose a review metric and define it precisely
The principal indicator for this exercise is minimum projected cash and weekly forecast accuracy. State the numerator, denominator, measurement period and data source where applicable. Decide what level of movement would be meaningful before seeing the results. Pair a speed or output measure with at least one quality indicator. For example, a process that closes actions more quickly but increases uncorrected mistakes has not clearly improved.
Review results using a small table: Period, Baseline or target, Actual, Difference, Reason, Corrective action and Owner. Do not infer causation from a single good week. Demand, seasonality, staff absence or unusual orders can affect outcomes independently of the process change.
Put an approval gate before an irreversible action
The major decision boundary is payment prioritisation during an emerging shortfall. Before crossing it, prepare a concise decision note: the available options, evidence, total cash exposure, dependencies, legal or customer obligations, reversibility, downside risk and the person authorised to approve. If information is missing, a smaller pilot may be preferable to a permanent commitment. Refusing to invent an uncertain input is a sign of a trustworthy process.
Agree a review date and an exit rule. An exit rule might limit an experiment to a fixed amount of money, a defined sample size or a certain number of weeks. The rule should be proportionate to the risk rather than copied from another business. Keep written approval evidence for consequential commitments and use specialist advice where required.
Complete a four-week practice cycle
First week: Describe the present method and collect baseline evidence. Do not redesign everything at once. Check whether the records can support minimum projected cash and weekly forecast accuracy and choose one narrow intervention.
Second week: Create the new procedure, checklist or template. Test it on a simple example and on a difficult exception. Document each correction and identify whether missing inputs or ambiguous responsibility caused the problem.
Third week: Conduct a limited live pilot where appropriate and authorised. An example of a suitably narrow outcome for this topic is advancing invoice follow-up and delaying a discretionary purchase. Measure time, quality and unintended consequences. Keep the ability to return to the prior process if the pilot fails.
Fourth week: Compare results, collect feedback from the people affected and write a decision: adopt, refine, retest or stop. Assign an owner and future review date. If no clear benefit appears, keep the evidence but do not claim success. The purpose of a pilot is to learn accurately, not to defend the original idea.
Reflection and transfer
Explain the principle to someone who has not read the chapter, without using jargon. Ask them to reproduce the calculation, review or process from your instructions. Any point requiring your verbal rescue is an opportunity to improve the documentation. Then consider where the same logic applies in another process: setting clear inputs, acknowledging uncertainty, naming decision rights, measuring outcomes and checking the effect on both money and people.
Completion evidence: a dated baseline, one-page procedure, exception test, recorded results and approved next action. These five records convert general business advice into a verifiable operating improvement.