Why Xero Can't Tell You Next Month's Cash

"How much cash will we have in eight weeks?"

It's the most common question a CEO asks finance, and one of the hardest ones to answer well out of Xero. Open the platform, click Reports, scroll down. You'll find a Cash Summary. A Short-Term Cash Flow. A Statement of Cash Flows tucked behind the Reports endpoint. Every one of them tells you, with varying levels of detail, what already happened. None of them tells you what's about to.

The Xero cash flow forecast is one of those reports that looks like it should exist, almost does, but never quite gets there. And in practice, the finance team ends up building it from scratch every month — in a spreadsheet that breaks every quarter and gets handed around like a cursed object.

This post is about what Xero actually gives you on cash flow, where it stops, and what a usable cash flow forecast off Xero data needs to look like if it's going to survive a real eight-week window.

What Xero gives you natively

Xero's cash reporting is reasonable for compliance and ad-hoc lookups, less so for forecasting. The three things you'll actually find:

Cash Summary. A backward-looking summary of cash movements in the period — receipts, payments, transfers, by account. Useful for a quick "where did the cash go this month" answer. Not a forecast.

Statement of Cash Flows. The accounting-textbook three-section view: operating, investing, financing. Built from the P&L and movements on the balance sheet, indirect-method by default. Closer to what an auditor wants than what an operator needs.

Short-Term Cash Flow. This one's the closest thing Xero ships to a forecast. It projects 7 or 30 days ahead, using your current bank balance plus the bills and invoices already entered into Xero with their due dates. If you ask it what your cash position looks like next Wednesday based on what's already in the system, it'll tell you.

That last one is genuinely useful — for the use case it was built for. But it only forecasts on the basis of what's already booked. It doesn't know that payroll runs on the 25th. It doesn't know that your biggest customer pays 22 days late, not on the due date. It doesn't know that GST is due next quarter. It doesn't know that you're planning to hire two engineers in June.

In other words, it answers "given everything sitting in the ledger right now, what does cash look like in the next month?" It does not answer "given how this business actually behaves, what does cash look like over the next thirteen weeks under base, upside, and downside assumptions?"

Those are very different questions. The second one is the one that matters.

Why most cash flow forecasts get built in Excel

Because the forecast you need lives mostly outside Xero. A useful cash flow forecast is a model — a set of assumptions about how the future will behave — sitting on top of the historical and committed data Xero holds. Xero is the data source, not the model.

The pattern is almost identical from one finance team to the next. Someone — usually the CFO or financial controller — owns a spreadsheet. The spreadsheet has tabs for AR aging, AP aging, a payroll schedule, a list of recurring direct debits, scheduled tax payments, and a "manual entries" tab for one-off things the team knows about. Each tab feeds a master forecast tab that lays out weekly closing cash for the next 13 or 26 weeks.

It works. It also takes a serious chunk of time to update, breaks when the person who built it goes on leave, and quietly drifts out of sync with reality between months. Then the board meeting comes around, someone asks what the cash position is in November, and the file gets opened with a small prayer.

What a real cash flow forecast actually needs

After looking at a fair number of these, the components that show up in any forecast that holds are pretty consistent. Roughly eight moving parts.

1. Weekly granularity, not monthly. Monthly forecasts hide the trough. A month can end with $200k of cash and still have had a week in the middle where cash dipped below the payroll run. The 13-week view is the standard for a reason — it's long enough to plan, short enough to be defensible, and weekly is the right resolution for spotting the dips.

2. An opening cash balance per account, not a single line. If you've got an operating account, a savings account, a USD account, and a tax-reserve account, the forecast needs to track them separately. Aggregate cash hides liquidity problems. The forecast that matters is the one for the account that actually pays the bills.

3. Inflows modelled by expected collection date, not invoice date. This is the single biggest mistake in most spreadsheet forecasts. Xero shows invoices by due date. Your customers pay on a different schedule. A useful forecast applies a collection profile per customer (or customer segment): top-10 customer X pays at due + 14 on average; small customers pay at due + 7; one specific account pays 45 days late, every time. Get this layer right and your forecast suddenly tracks reality. Get it wrong and you're showing the board a fiction.

4. Outflows split by category, with the right treatment for each.

• AP — by due date, optionally with a "we delay these by N days" lever for stretched payment.
• Payroll — on actual payroll dates, not in monthly lumps.
• Recurring direct debits — rent, software, utilities — by their scheduled dates, not their accounting periods.
• Tax — GST/VAT, corporate income tax, withholding tax, on their actual payment dates.
• Capex and one-offs — separately, because they're discretionary and the lever to defer is real.

5. Scenario layers. Base, upside, downside as a minimum. A useful forecast lets you flex two or three assumptions — collection days, top-line growth, a major contract slipping — and see the cash trough move. If the only number you can show the board is a single forecast line, you're flying blind on sensitivity.

6. Variance tracking against prior forecast. This is the part that turns a forecast from a document into a discipline. Every month, last month's forecast becomes a thing you compare actuals against. The variances tell you where your assumptions are systematically wrong — and your future forecasts get better as a result.

7. Drill-back to the source. A forecast number is a question, not an answer. When the CEO asks "why is week 7 lower than week 6?", the answer should be one click — payroll plus the GST payment plus a known capex item — not an investigation. The line items need to be traceable to the underlying records, not assembled by hand.

8. Multi-entity, where relevant. Most groups care about both legal-entity-level cash (where the obligation sits) and group-level cash (whether the group can move funds around to cover it). The forecast should support both views, and ideally show intercompany sweeps as planned movements rather than mystery deltas. The same problem we've covered for multi-entity P&L consolidation applies to cash forecasting one layer deeper.

The workarounds, ranked

In practice, finance teams end up with one of three approaches.

The Excel/Sheets model. The default. Powerful, fully bespoke, completely under your control. Also fragile, time-consuming to update, and one staff change away from being unmaintainable. The model only works for as long as the person who built it is around to feed it.

Third-party forecasting tools. Float, Fluidly, Helm, Cashflow Frog, Pulse, Syft's cash flow features, Spotlight Forecasting. These tools pull from Xero, apply a forecasting layer, and produce a 13-week or longer view. Some are good, especially if your business behaves the way the tool's template expects. The ceiling tends to come on customer-specific collection logic, multi-account treatment, scenario flexibility, and reporting layouts that match your existing board pack.

Custom-built reporting on top of Xero. Pull the raw data — AR, AP, recurring billing, payroll, tax — apply your own forecasting logic, output to wherever your team works. Costs more upfront. Doesn't get re-templated against your reality every quarter.

None of these are wrong. The right choice depends on how complex your cash flow is and how much your forecast needs to look like your forecast.

Where this sits in the rest of your reporting

A cash flow forecast doesn't live in isolation. It sits next to the budget vs actual P&L (which feeds the assumptions about revenue and cost), the monthly management accounts (which provide the historical baseline the forecast extrapolates from), and the group consolidation (if there's more than one entity). When any one of these is built fresh each month, the others start to drift. When they share a layer underneath, the forecast updates automatically as the actuals close.

The teams that have the cleanest cash flow reporting are almost always the teams that have the cleanest management reporting under it. There isn't a separate shortcut.

Where Cheetah fits

Most of the cash flow work we do at Cheetah starts the same way: someone shows us the spreadsheet they update every Friday afternoon, and we encode the logic — the collection profiles, the payroll dates, the tax schedule, the recurring DDs, the scenario levers — directly into a report that pulls live from Xero. The Friday afternoon spreadsheet stops being a spreadsheet. It becomes a generated output, in the same format the team is used to, with the same assumptions, but updated from source rather than assembled by hand.

If you're rebuilding your 13-week forecast every month from scratch, that's the exact shape of problem Cheetah was built for. Worth a look.

The short version

Xero stores everything you need to build a cash flow forecast. It just doesn't ship one. The Short-Term Cash Flow report covers a narrow case well; the rest is on the finance team. A forecast that survives contact with reality needs weekly granularity, per-account opening balances, collection-date-aware inflows, dated outflows by category, scenarios, variance tracking, and drill-back. Build it once into a layer that connects to Xero, and you stop rebuilding it forever. Build it again every month in a spreadsheet, and the spreadsheet starts running you.