The most damaging financial conversation an owner can have with themselves is “the bank balance is fine, we're fine.” The bank balance is the most lagging, least diagnostic number in the business. It tells you where cash is right now and nothing about where it's going.
The view that should replace it: cash position calibrated against the next 14 (or 30) days of known inflows and outflows. We'd call it a rolling cash dashboard. For smaller SMEs it's a single screen; for larger or multi-entity operations it's a structured view that rolls up across accounts. Either way, the principle is the same: show the operator the cash trajectory, not just the cash snapshot.
This piece walks through how to build it, what to put on it, and the discipline that keeps it useful.
Why month-end isn't enough
A typical SME runs cash awareness on three timeframes:
- Bank balance — checked daily by some owners, weekly by most. Tells you where cash is right now.
- Month-end cash report — produced after close, often 6-14 days into the following month. Tells you where cash was a month ago.
- Annual cash flow statement — produced with annual accounts. Tells you where cash was a year ago.
Every one of these is backward-looking. None of them answer the question that actually matters operationally: “based on what I know is coming in and going out in the next two weeks, am I going to have a problem?”
For F&B and retail SMEs especially, cash can move materially day to day — a slow Tuesday, a large delivery platform payout, payroll going out, a supplier prepayment. The bank balance alone obscures any of that.
The structure: cash on hand plus next-14-days
The view that solves this is usually three sections:
Section 1: cash on hand, by account
Every operating bank account, with its current balance, aggregated to a single “cash on hand” figure. For most SMEs this is two to four accounts (operating DBS, expense card via Aspire, possibly a SGD savings account for reserves, possibly a foreign currency account for overseas suppliers).
The view should call out anything unusual — an account balance lower than its typical floor, for example.
Section 2: expected inflows in next 14 days
- Card settlement deposits — typically T+1 to T+2 from the merchant
- Delivery platform payouts — typically weekly, on a fixed day
- Outstanding invoices due in the window — receivables with a known due date
- Any pre-agreed lump-sum receipts (a catering deposit, a wholesale settlement, a refund from a supplier)
The total is your expected inflow. The component lines let you see which ones to chase if cash is tight.
Section 3: known outflows in next 14 days
- Payroll runs in the window (mid-month and end-of-month for most SMEs)
- CPF payment by the 14th of the next month
- Supplier payments scheduled in the AP system
- Rent (usually monthly, on a known date)
- Recurring subscriptions and known auto-debits
- GST F5 payment if due in the window
- Any pre-committed lump sums (equipment purchase, lease payment)
The total tells you your expected cash outflow.
Section 4: net position in 14 days
Cash on hand + expected inflows − known outflows = projected cash position at end of the 14-day window. If positive and above your operating buffer, you're fine. If tight, the dashboard shows you exactly where the tightness is and what you can do about it.
The data sources
For most SMEs, the dashboard pulls from:
- Bank feeds in Xero — cash on hand, by account, refreshed daily
- Xero AR aging — receivables due in the next 14 days
- Xero AP scheduled payments — supplier payments scheduled
- Payroll system — payroll runs scheduled
- Card merchant + delivery platform schedules — predictable settlement cycles
- Manual entries for known one-offs — a big catering deposit, a lease payment, anything non-recurring
When everything is in Xero with the right tags and the right reconciliation discipline, the dashboard largely builds itself. When records are split across systems and spreadsheets, the dashboard requires manual assembly and stops being maintained after the third week.
What to include — and what to leave off
Include
- Cash position by operating account
- 14-day rolling forecast (the structure above)
- Optional: 30-day or 13-week view for larger SMEs
- Operating buffer threshold (the floor below which cash position becomes a concern)
- Days of runway at trailing 30-day burn rate
- Flag for any major non-recurring outflow in the window
- Comparison to same period last month (is cash trending up or down?)
Leave off
- P&L metrics that aren't cash — net profit, EBITDA, etc. (different dashboard)
- Speculative forecasts beyond two weeks (rapidly degrades in accuracy)
- Pre-calculated ratios you wouldn't act on (current ratio, quick ratio — useful for reporting, not operating)
- Bank account balances at irrelevant levels of granularity (every credit card transaction)
For multi-outlet F&B and retail
Multi-outlet operators have one additional discipline: cash should be visible by entity if there are multiple legal entities, and by outlet if the operating account structure permits. Most SMEs run a single operating account per legal entity, so the entity-level view is usually sufficient — but if cash is being moved between outlets (via intercompany loans or shared accounts), the dashboard should surface that.
For larger operators, the dashboard becomes a 13-week rolling cash forecast — a structure familiar from fractional CFO work, adapted to the operator's actual cash cycle. The same principles apply at greater scope.
The discipline that keeps it useful
Three operational habits make the difference between a dashboard that owners trust and one they stop checking after two weeks:
- Bank reconciliation daily, not monthly. If reconciliation is monthly, the cash-on-hand view is always lagging. Bank feeds + auto-rules + a few minutes a day from the bookkeeper is enough.
- Receivables aging maintained continuously. Invoice due dates have to be accurate. Invoices that were paid but not allocated, or invoices that are disputed and won't be paid, both pollute the forecast.
- Known one-offs entered as they're committed. A new lease, a big equipment order, a catering contract — entered into the forecast as a scheduled outflow or inflow at the moment of commitment, not at the moment of payment.
When the underlying data is clean, the dashboard is accurate. When the underlying data drifts, the dashboard becomes a false sense of security — which is worse than no dashboard at all.
What changes when an operator can see cash live
Three decisions get easier:
- Supplier payment timing. An operator who can see the next 14 days knows when to pay a supplier on day 30 vs. negotiate to day 45 vs. settle early for a discount.
- Headcount decisions. Hiring an additional staff member is a known recurring outflow. The dashboard shows immediately what the cash impact looks like across the next quarter.
- Investment decisions. A new outlet, a piece of equipment, a marketing campaign — each is a cash commitment. The dashboard shows whether the commitment fits.
The conversation shifts from “we have S$X in the bank” to “here's our cash trajectory for the next two weeks.” That's a different quality of decision.
How AI agents help
A live cash dashboard requires the underlying data to stay clean, which is exactly where AI agents earn their place. Our pattern:
- Receipt Catcher keeps supplier invoices flowing in promptly so AP scheduling is accurate
- Vendor Chaser follows up on overdue receivables so the AR aging is real
- Outlierflags any cash transaction that doesn't look right (a late platform payout, a larger-than-usual supplier outflow) before it distorts the dashboard
Humans still own the forecast judgement — “is this big catering deposit really committed or is it contingent?” — but the routine maintenance of the underlying data is automated. See how AI reduces admin for the broader pattern.
The bank balance is a snapshot. The dashboard is a trajectory. Once an owner has the second, they stop relying on the first. The decisions get better.
— The Acuitas team