Why seeing your cash flow once a month is not cash flow management — and what happens when you close that gap.
A company can look completely healthy on Monday and be in crisis by Friday. Not because something catastrophic happened. Not because the business is failing. But because the people running it were looking at last month's numbers while this week's cash was moving in the wrong direction.
Most small and mid-size companies review their cash position once a month — when the accountant closes the books. The monthly report lands, someone glances at the bank balance, and the conversation moves on. Everything looks fine.
What the monthly report doesn't show is what happens in the 29 days between reports. Where the money actually goes. Which clients are paying late. Which supplier payments are queuing. What the account balance will look like on the 25th — when payroll runs.
This isn't a hypothetical. I've seen versions of this scenario more than once in my 30 years. The details change. The structure is always the same.
At no point did the company have a revenue problem. Every invoice in this scenario gets paid — eventually. The business is healthy. What failed was the information system. Nobody was looking at cash position daily. Nobody flagged the collision between the VAT auto-debit and Friday payroll. The monthly report showed a strong month. The weekly reality was a different story.
Reporting tells you what happened. Management changes what's about to happen. Most small businesses have the first. Almost none have the second — because real-time cash management requires someone watching the numbers every day, and nobody has time for that on top of everything else.
"A monthly cash flow report is a history book. By the time it's published, you can't change any of the events in it."
The gap between reporting and management is exactly where most cash crises live. Not in bad businesses. In businesses that are doing fine — but finding out too late that something was about to go wrong.
The answer depends on your cash cycle, your payment terms, and how many large outflows hit in any given week. But here is a practical framework based on what I've seen work — and what I've seen fail — across dozens of companies.
| Review frequency | What you catch | What you miss | Verdict |
|---|---|---|---|
| Monthly | End-of-month balance, trends over time | Any intra-month crisis. Every week-level collision. | High risk |
| Weekly | Week-end position, upcoming large payments | Mid-week surprises, same-day payment collisions | Acceptable |
| Daily | Current balance, today's inflows/outflows | Very little — most crises visible 1–2 days ahead | Good |
| Real-time + alerts | Balance, projections, anomaly flags — automatically | Almost nothing — system flags before human needs to look | Optimal |
The reason most companies stay at "monthly" isn't that they don't know daily is better. It's that daily cash monitoring requires someone to actually do it — pull the bank data, reconcile it against expected payments, check the forward projection. That's 30–45 minutes of work every day. Work that competes with everything else on the accountant's plate.
A well-built cash flow agent doesn't wait to be asked. It connects to the bank feed, accounting system, and payroll schedule. It runs every morning — automatically. By the time the CEO arrives at their desk, there's already a summary: current balance, expected inflows this week, scheduled outflows, and a flag if the projected balance drops below a set threshold at any point in the next 14 days.
"The payroll crisis in that Friday scenario was visible on Tuesday — if anyone had been looking at a 5-day cash projection. An agent looks at it every day. That's the entire point."
In the scenario above, a basic cash flow agent would have flagged the problem on Wednesday morning: projected balance Friday after payroll — negative €8,300. Flag: payroll at risk. Action required. That's a solvable problem on Wednesday. It's a crisis on Friday at 4pm.
The technology for this isn't new. The API connections to bank feeds have existed for years. What's new is that building and running this kind of monitoring system no longer requires a developer, a BI team, or an enterprise software contract. It can be set up by a finance person who is willing to spend a few hours on the architecture. That's what I've been building — and what the rest of this series covers.
Post #5 walks through the exact setup of the cash flow agent I built — what it connects to, what it sends, and what it cost in time to configure.
How often does your company review cash flow?
No spam. One post per week. Unsubscribe any time.