New

Peaky raised €1.1M, led by JK Invest

→

All articles

Company

/

Written by Ser Cappelle (CEO/CFO & Co-Founder at Peaky)

The business changes before the numbers do.

Supplier price increaseNewH
Cost of your three main components up 9% since 1 October.
−€280K gross margin
ExternalJust now
Supplier price increaseNewH
Cost of your three main components up 9% since 1 October.
−€280K gross margin
ExternalJust now

A supplier sends a new price list. A key customer gives notice. A hire is pushed back six weeks. A storm delays a shipment by ten days.

None of these show up in your P&L on the day they happen. Some take a month. Some take a quarter. But every one of them has already changed your numbers. You just cannot see it yet.

The lag nobody plans for.

Finance sees the business through the books. And the books are, by design, a record of what has already happened.

An invoice is booked when it arrives. Revenue is recognised when it is earned. Payroll lands when salaries are paid. The close happens weeks after the month ends. Each step is correct. Each step is also late.

So there is always a gap between the moment something changes in the business and the moment it becomes visible in the numbers. Call it the reporting lag. In most companies it is somewhere between three and eight weeks. Longer for anything that runs through contracts, advance payments or annual settlements.

That gap is where the expensive surprises live.

Four examples.

The supplier price increase. Purchasing agrees to a 7% increase on a key raw material in March. The first invoices at the new price arrive in April. They are booked in May's close. Gross margin is discussed at the June review. By then, three months of production have run at a margin nobody planned for, and the price list for customers has not moved.

The customer who left. A large customer tells their account manager they are moving to a competitor at the end of the contract. Sales knows in week one. The CRM is updated in week three. The revenue disappears from actuals two months later. The forecast still includes them until someone notices.

The delayed hire. Two engineers were planned to start in February. They start in April. Payroll is lower than plan, which looks like good news. But the product launch that depended on them slips by a quarter, and the revenue behind it slips too. The cost saving shows up first. The revenue loss shows up later, and is much bigger.

The energy bill. Consumption rises and market prices swing, but the monthly advance payment stays the same. The P&L shows a stable energy line all year. Then the annual settlement arrives.

In every case, the information existed early. It just lived outside finance: in purchasing, in sales, in HR, in a supplier portal. It reached the numbers late, and finance found out last.

Why faster closing does not fix it.

The usual answer is to close faster. Monthly instead of quarterly. Five days instead of fifteen. It helps. It does not solve the problem.

A faster close shortens the time between the books and the report. It does nothing about the time between the business and the books. The supplier price increase still has to be invoiced before it can be closed. The lost customer still has to stop paying before it shows up as lost revenue.

You can make the old process faster. Four days or four minutes, you are still waiting for the numbers.

Watch the causes, not just the results.

The alternative is to stop waiting for the result and watch the cause.

Every number in your plan rests on assumptions. A price per unit. A start date. A contract value. A churn rate. Those assumptions do not live in the accounting system. They live in the systems where the business actually runs: the CRM, the HR system, billing, purchasing, contracts.

When you connect the plan to those systems, the order changes. The supplier price increase is visible the moment purchasing agrees to it, not when the invoice is closed. The customer churn is visible when the CRM changes, not when the revenue stops. The late hire is visible when the start date moves, along with what it does to the launch and the revenue behind it.

This is what we mean by causal intelligence: connecting a change to its causes and to its financial consequences, while there is still time to act on it.

What changes for finance.

Three things.

The surprise becomes a signal. Instead of discovering a variance at the close, finance gets a heads-up when an assumption starts to drift, with the impact on revenue, margin and cash.

The explanation comes first. Because the cause was seen first, the "why" is already known when the number moves. Nobody has to work backwards through three systems to explain it to the board.

The window stays open. A price increase spotted in March can still be passed on to customers in April. One spotted in June mostly cannot. The value of seeing change early is not the information itself. It is the decisions that are still possible.

The real job.

Finance carries the responsibility for the numbers. It also carries the pressure when they surprise people.

The business will keep changing before the numbers do. That part is not going away. What can change is how long finance has to wait to find out.

Read more: What is drift in financial planning.

Previous

Why Peaky is not another FP&A tool.

Next

How CFOs lose their Sundays (and how to get them back).

Keep exploring

Getting started

From your Excel plan to a live plan in a day.

Integrations

The systems Peaky connects to, and what each one brings in.

The Forecast Audit

Nine questions to find out whether your forecast is a report or a tool.

Peaky app icon

Sync or sink.

Ask AI for a summary of this website