What does a good week cash flow forecast example look like for a small business?

A week cash flow forecast is a short-horizon projection of the money moving in and out of your business over the next seven days, usually broken down by day. It answers one question: will the balance in your bank account stay above zero every single day this week? For small and mid-sized businesses, this weekly view is often more useful than a monthly or quarterly forecast because most cash crises develop on a daily timescale — payroll hits Friday, a customer pays late Tuesday, VAT leaves the account on the 25th, and suddenly a business that looks profitable on paper cannot make payroll.

Below is a complete, practical walkthrough of what a weekly forecast looks like, how to build one step by step, where the common mistakes hide, and how spreadsheet-based forecasting compares with AI-assisted tools that connect directly to your bank feeds.

Also worth reading: Can AI cashflow transparency for SMBs turn small business finance into a savings engine? · Can AI Be Your Small Business's Personal Financial Advisor? · How Should a Small Business Budget for an AI Pilot in 2026?

A Worked Example: Seven Days of Cash Flow

Here is a realistic example for a small services company with about 12 employees, starting Monday 24 August 2026 with an opening bank balance of £48,200. The forecast lists expected inflows (customer receipts, refunds) and outflows (payroll, suppliers, tax, rent) day by day, then calculates a running closing balance.

This single table tells you everything a lender or an owner needs to know. The business ends the week roughly £14,300 lower than it started, driven by two large outflows clustered on Thursday and Friday — the VAT bill and payroll. If invoice #1042 slips by even three days, the Friday closing balance drops to around £24,900, which is still solvent but thin. That sensitivity is exactly what a weekly forecast exists to expose before it becomes a problem.

Notice also what the example deliberately includes: dated invoices with expected receipt days, not vague 'sales' figures; specific payment obligations with their actual debit dates; and a running balance rather than just weekly totals. A forecast without dates per line item is not really a forecast — it is a summary.

Why Weekly Beats Monthly for Most SMBs

Monthly forecasts smooth over the timing mismatches that actually kill small businesses. Research into business failure consistently points to cash-flow insolvency rather than balance-sheet insolvency as the proximate cause of collapse — a firm can own valuable assets and still be unable to pay a debt when it falls due. On a monthly grid, £40,000 of inflows against £38,000 of outflows looks comfortable. Split across weeks, those same flows might reveal a week where £25,000 goes out before a penny comes in.

The weekly cadence matters for three reasons. First, most recurring obligations cluster: payroll typically runs fortnightly or monthly on fixed dates, VAT quarters land on set deadlines, and rent debits on the 1st. Second, customer payment behaviour varies by weekday — many businesses batch their payment runs on particular days, so your receivables arrive in lumps you can predict once you have observed them for a few cycles. Third, a weekly rhythm creates a management habit: reviewing cash every Monday morning takes fifteen minutes and catches problems while there is still time to react, whether that means chasing an invoice, delaying a purchase, or arranging an overdraft before you need it.

There is a counterargument worth acknowledging. Weekly forecasting is more work than monthly, and for very stable businesses — subscription revenue, predictable salaries, no seasonality — the extra granularity adds little. Some firms run a hybrid: a rolling 13-week forecast updated weekly at the aggregate level, with a detailed day-by-day view only for the current week and the next one. EY's work on cash disciplines emphasises exactly this point: the value comes from the discipline of regular review and variance tracking, not from the granularity itself.

How to Build Your First Weekly Forecast: Step by Step

Start with your actual bank balance, not your accounting software's ledger balance. The ledger includes unpresented cheques and pending transactions; the bank knows the truth. Note the balance as of a specific date and time.

Next, list every known inflow for the coming week with its expected date. This means open invoices with due dates, adjusted for each customer's real payment behaviour — if a client always pays ten days late, put their receipt ten days after the due date, not on it. Add any scheduled income such as card settlement batches, which typically arrive one to three business days after the transaction date depending on your processor.

Then list every known outflow with its debit date: payroll and its associated taxes, supplier payment runs, loan repayments, rent, insurance premiums, subscription charges, and tax obligations. Check your direct debit schedule carefully; irregular items like quarterly VAT or annual insurance renewals are the ones people forget. HMRC's VAT deadline, for instance, falls one month and seven days after the quarter end, so a quarter ending 30 June means payment on or before 7 August — easy to miss if you only think monthly.

Finally, build the running balance: opening balance plus cumulative net flow for each day. Then stress-test it. Ask what happens if your largest expected receipt arrives five days late, or if an unexpected £5,000 expense lands Wednesday. If either scenario pushes you below a safety floor — many advisers suggest keeping at least one full payroll cycle, or roughly 8–13% of annual operating costs, as liquid buffer — you have identified next week's action item while it is still actionable.

Spreadsheet Versus AI-Assisted Forecasting Tools

Most businesses start in a spreadsheet, and for good reason: it is free, fully transparent, and forces you to understand your own numbers. The trade-off is maintenance. Spreadsheets do not update themselves, they break silently when someone edits a formula, and they depend entirely on whoever built them showing up every week.

Bank-connected tools earn their fee mainly through automation and pattern recognition: they pull transactions daily, categorise them, and project forward using each customer's historical payment lag rather than invoice due dates. That last capability alone often improves forecast accuracy materially, because the gap between contractual due dates and actual receipts is where most weekly forecasts fail. Tools in this category range from lightweight cash-flow apps bundled with accounting platforms to dedicated forecasting products; the U.S. Chamber of Commerce's reviews of visualisation and planning tools note that integration with your existing bookkeeping system should be the first selection criterion, ahead of features.

Whichever route you choose, insist on transparency. A forecast whose assumptions you cannot inspect is a black box, and black boxes fail quietly. Whether the model lives in cell C14 or in a vendor's cloud, you should be able to answer: why does the tool think this customer pays on day 42?

Common Mistakes That Ruin Weekly Forecasts

The most frequent error is forecasting sales instead of cash receipts. Revenue recognised in your accounts is not money in the bank. A £20,000 invoice raised Monday contributes nothing to this week's balance unless it will actually be collected this week. Always forecast collections, using observed payment lags per customer segment.

The second mistake is ignoring weekend and bank holiday timing. A payment due Saturday does not clear until the next business day; the late-August bank holiday in the UK shifts settlements by a full day. Businesses that model calendar days rather than banking days systematically overstate early-week balances.

Third is optimism bias on the inflow side and precision bias on the outflow side. People round inflows up and treat outflows as exact. A useful discipline: haircut uncertain inflows by 10–20%, and add a contingency line of 3–5% of weekly outflows for the genuinely unexpected — the emergency equipment repair, the duplicate charge, the refund you did not see coming.

Fourth is failing to reconcile forecast versus actual. A forecast you never compare against reality teaches you nothing. Each Monday, spend five minutes comparing last week's projected closing balance with the actual one. If you are off by more than about 10% consistently, your assumptions are wrong somewhere — usually collection timing — and that finding is more valuable than the forecast itself.

When to Act on What the Forecast Shows

A weekly forecast is only useful if it triggers decisions. Set explicit thresholds in advance. If the projected minimum balance for the coming week falls below one payroll cycle, act immediately: accelerate collections by calling the two largest outstanding customers personally, defer discretionary purchases, and check available credit headroom. If the shortfall is structural — recurring negative weeks for six or more consecutive weeks — the issue is profitability or working capital structure, not timing, and the response is pricing, cost base, or financing changes rather than tactical chasing.

Timing windows matter. Banks generally need several business days to arrange overdraft extensions or short-term facilities; asking on Thursday for money needed Friday rarely works. Invoice finance providers typically advance 80–90% of an approved invoice within 24–48 hours, but onboarding and credit checks take longer the first time. Tax authorities offer time-to-pay arrangements, but applying early is far easier than negotiating arrears. The whole point of seeing a squeeze two weeks out is that two weeks is enough time to fix it cheaply.

Conversely, do not overreact to single-week dips that are explained by known timing — the quarterly VAT cluster, the fortnightly payroll overlap. Mark these in your forecast so the pattern is visible and nobody panics unnecessarily. The goal is calm, evidence-based decisions, not constant firefighting.

Costs, Effort, and Getting Started This Week

The financial cost of weekly forecasting can be effectively zero. A spreadsheet template takes two to four hours to build properly the first time, then fifteen to thirty minutes per week to maintain once your templates and customer payment profiles are established. Paid tools run roughly $20–150 per month at small-business tier, with mid-market products higher; the return case rests on avoided overdraft fees, better-negotiated supplier terms from paying predictably, and fewer emergency borrowing events. An overdraft drawn in panic routinely costs 1–3 percentage points more than one arranged in advance, and late tax payment penalties compound monthly.

If you are starting today, begin with the worked example above as your template. Pull your actual bank balance, list this week's dated inflows and outflows, compute the running balance, and write down your two biggest uncertainties. Next Monday, compare the result to reality and adjust. By week four you will have a forecast accurate enough to plan against, and by week eight you will wonder how you operated without it. The businesses that survive cash squeezes are rarely the ones with the best products — they are the ones that saw the squeeze coming.