Financial controlling that gets sharper every month

Most growing companies don't have a dedicated controller. Controlling lives in one person's spreadsheets, the numbers arrive late, and they only ever look backward — and running a growing company on a blurry, backward-looking financial picture is how cash-flow surprises sink otherwise healthy businesses. The pain shows up as three concrete problems. We show how to turn controlling into a continuous loop that attacks all three: it collects the data, validates it, builds the financial picture, explains what changed — and gets sharper at forecasting cash and margins every month.

The problem we see

Below a certain size, "controlling" usually means one capable person — the owner, an accountant or a part-time CFO — rebuilding the same spreadsheets every month. The numbers exist, but they're scattered across the accounting system, the bank, invoicing, a CRM and a few Excel files. Someone exports them, pastes them together, fixes what doesn't match, and a week into the new month finally has last month's picture.

Studies of finance teams put roughly 75% of their time on gathering and cleaning data, and only about 25% on actual analysis. In a small company without a controller, that ratio is even worse — the person who should be interpreting the numbers spends their time assembling them.

Three real problems this solves — and who has them

1. No live cash view — the founder rebuilds a cash spreadsheet every month-end

Who has it: a €6M e-commerce brand where the founder rebuilds a cash spreadsheet every month-end, juggling supplier prepayments against marketplace payouts, and only notices a squeeze when a big stock order and a VAT payment land in the same week.

Cash-flow problems are the most-cited cause of small-business failure — the widely-quoted ~82% figure (U.S. Bank via SCORE) — and the 2024 Fed Small Business Credit Survey found 44% of small firms missed a payment because of a cash-flow problem in the prior year. Running blind on cash isn't an inconvenience; it's the top correlate of going under.

How we solve it: it connects bank, invoicing, AP and ERP, validates the feeds and keeps an always-current cash position plus a rolling forward forecast — replacing the monthly copy-paste rebuild, with AI explaining in plain language why cash moved and when the next dip is coming. Nothing is auto-paid; a human decides.

2. Last month's numbers arrive a week late, so decisions run on stale data

Who has it: a €12M services firm where the external accountant delivers last month's P&L on the 10th–12th — by which point the MD has already committed to a new hire and a fleet lease without knowing the previous month's margin actually slipped.

For SMBs the month-end close routinely takes 6–10 business days, and 59% take six or more (Numeric). By the time the picture is "ready" the team is a third of the way into the next month, looking backward instead of ahead.

How we solve it: because it ingests and validates source data continuously, it produces a current-month P&L and margin picture that doesn't wait for a formal close, and AI narrates what changed versus last month and versus forecast — opening the decision window days earlier.

3. Margins by product/project/customer are unknown, and slow payers aren't flagged

Who has it: a €10M project firm with a healthy headline margin where two of its five biggest projects are quietly run at a loss and the rest carry them — so the founder keeps selling more of the loss-makers because they look like growth.

A single blended margin hides the money-losers. Meanwhile late payment is a structural drain in Europe: the EU Payment Observatory reports average payment periods exceeded 60 days in 2024 with more than half of companies reporting resulting difficulties, and estimates EU SMEs could unlock over €100 billion a year if paid on time. Without segment margins and a forecast, both the loss-making project and the customer drifting from net-30 to net-65 stay invisible until cash is already tight.

How we solve it: it tags revenue and cost to product, project and customer for true segment margins, forecasts cash and margins on a rolling basis, and flags anomalies early — a slipping margin, a customer's DSO creeping up — and the forecast gets sharper every month by comparing what it predicted to what actually happened.

The Europe-specific figures (EU Payment Observatory) are the most authoritative here; the "82%" cash-flow stat is widely cited but a hardened popularization. The real numbers for your business come out of the free diagnostic.

The idea: a controlling loop that gets sharper every month

All three problems share one root: the financial picture is rebuilt by hand, so it's late, blurry and trapped with one person. Make it continuous and the rest follows.

Controlling shouldn't be a spreadsheet rebuilt from scratch each month. It should be a loop that runs continuously, keeps a human in control, and gets sharper from the gap between what it predicted and what actually happened.

The goal isn't another dashboard. It's a controlling process that gets sharper the longer it runs.

How it works

1. Connect the sources — accounting/ERP, bank statements, invoicing, CRM and the few spreadsheets that already hold the truth.
2. Validate before showing — the system checks missing entries, duplicates, unusual movements and mismatches between sources, instead of pushing bad numbers into a report.
3. Build the picture — a clean, current view of cash, P&L, and margins by product, project or customer — without the monthly copy-paste.
4. Explain & forecast — AI summarizes what changed in plain language and projects cash and margins forward, with links back to the source numbers.
5. Human decides — the owner or finance lead reviews, asks questions and makes the call. Nothing is auto-posted or auto-paid.
6. Measure & improve — the loop compares each forecast to what actually happened and adjusts, so next month's projection is better than last month's.

Where exactly AI helps

AI is not the accounting engine. The numbers come from your real ledgers and clear rules. AI helps around the parts that normally eat a controller's week:

• pulling messy data from different systems into one consistent picture,
• explaining why a number moved (not just that it did),
• forecasting cash and margins, and updating the forecast as reality comes in,
• flagging anomalies worth checking — a margin slipping, a customer paying slower,
• answering plain-language questions over the numbers ("why is cash lower than last month?"),
• turning the picture into management notes a non-finance owner can act on.

For example, AI shouldn't invent a forecast and present it as fact. But it can say:

"Cash is projected €40k tighter by month-end than last month, mainly because two large customers shifted from 30- to 45-day payment, and material costs rose 6%. At the current run-rate you stay positive, but a delayed payment from your top customer would put you under your buffer."

That turns a spreadsheet into a decision.

What "gets sharper every month" actually means

This is the part a static dashboard never does. Each cycle, the loop writes down what it expected — cash at month-end, margin on a project, when a customer would pay — and then compares it to what actually happened.

Over a few months that feedback compounds:

• forecasts stop being a straight-line guess and start reflecting your seasonality and payment behaviour,
• the loop comes to recognise which customers really pay late versus which just look late,
• it gets better at telling which cost movements are noise and which are a trend,
• the explanations sharpen, because the system knows which signals mattered last time.

The controller doesn't start from zero every month. The loop carries forward what it worked out before.

What we measure

A controlling loop should be measured from the first version — including the cost of controlling itself.

What we measure	Why it matters
Time to a current financial picture	Days-after-month-end shrinking shows the manual work is gone
Forecast accuracy over time	The core proof the loop is actually improving
Cash visibility	Whether there's a real-time view instead of a guess
Margin coverage	How much of revenue has a known margin (product/project/customer)
Anomalies caught early	Slipping margins or slow payers spotted before they hurt
Hours spent assembling vs. deciding	The ratio the whole loop is meant to flip

Why it works better than a month-end Excel

A spreadsheet can hold the numbers. It can't run the process, and it never improves on its own. A controlling loop gives you:

• a current picture instead of one that's a week late,
• a forecast that improves instead of a static guess,
• early warnings instead of surprises at month-end,
• margins you can see instead of argue about,
• controlling that doesn't break when one person is on holiday,
• time spent deciding, not assembling.

You don't need a full FP&A team or an enterprise system to start. One company, its real ledgers and bank feed, and one recurring controlling cycle is enough to show whether the loop is worth scaling.

Who it makes sense for

This makes sense for companies that have outgrown "the accountant sends a report" but can't yet justify a full controlling department. Especially if:

• there's no dedicated controller and finance leans on one person,
• the cash position is never quite clear in real time,
• decisions are made on last month's numbers, or on gut feeling,
• margins by product, project or customer are fuzzy,
• the owner or part-time CFO spends more time building reports than using them.

Good controlling shouldn't just tell you what happened last month. It should tell you what's coming, flag what needs attention — and get better at both every time the month closes.

The payback is concrete: a current cash position instead of a guess, decisions made days earlier on numbers you trust, and the money-losing project or slow-paying customer caught before it hurts — for a fraction of a controller's cost, with a human always in the decision seat. One company's ledgers and bank feed are enough to prove it.

Controlling is only as good as the reporting under it — see why manual reporting isn't business intelligence, and our AI solutions overview shows where a controlling loop fits.

Want to see it on your own numbers? Get a free diagnostic — we map your controlling on one company and show you exactly what we'd build, the impact and the cost. No obligation.