Why Department Budgets are built on last year's guesses

Last year's estimates plus 5%. That is most budget processes. It does not have to be.

By Jeppe Jørgensen, Founder — Onpoint

How most department budgets get built

Every year, the same cycle.

Finance sends out a budget template. Managers fill it in. They look at last year's numbers, add a growth assumption, adjust for anything they remember, and submit.

Finance aggregates, queries the big numbers, and eventually a budget is approved.

The result: a budget built on last year's estimates, adjusted by gut feel, with almost no reference to what was actually spent - line by line, item by item.

It is a guess. A structured, well-intentioned guess. But still a guess.

Why the guesswork problem is structural

Managers do not use actual spend data because they cannot access it in a useful form.

ERP data is not manager-friendly Cost centre totals in the ERP do not tell a manager what they spent on IT, travel, or facilities. The categories are accounting categories - not the categories managers think in.
Invoice detail is inaccessible The real data - what was bought, from whom, at what price, how often - lives in PDF invoices. Nobody has extracted it into a budget-ready format.
No line-level history Even managers who want to budget from actuals cannot do it. They have totals. They need item-level patterns.

The budget process starts with a blank template. It should start with last year's invoice data.

What a budget built on actuals looks like

Start from last year's invoice lines

Not cost centre totals - the actual items purchased, from each supplier, at each price. This is the real baseline for next year.

Identify recurring spend patterns

Some costs repeat monthly. Others are quarterly or annual. Invoice history shows the pattern clearly - no guessing required.

Adjust for known changes

Price increases, planned new purchases, headcount changes - apply these to a real baseline, not a round number.

Spot the anomalies from last year

One-off costs, inflated invoices, items that should not recur - visible in invoice history, so they are not accidentally baked into next year's budget.

What Finance gains from actuals-based budgeting

The benefit is not just accuracy. It is defensibility and speed.

Defensible numbers Every budget line traces back to real invoices. When the CFO questions a number, the answer is: here are the specific items that drove it last year.
Faster process When managers start from pre-populated actuals rather than blank templates, the back-and-forth of queries and revisions drops significantly.
Fewer mid-year surprises Budgets built on guesses break mid-year. Budgets built on actuals track reality more closely - because they started from reality.
Cross-department consistency Finance can apply consistent category structures across all departments when the data comes from invoices - not from however each manager chose to label things.

Summary

Most budgets are built from last year's estimates, not actual spend data
Invoice detail is inaccessible to managers in a budget-ready format
Starting from invoice line history eliminates the guesswork baseline
Recurring patterns, one-off items, and price trends are all visible in invoice data
Finance gets defensible numbers and a faster process - with fewer mid-year surprises

Frequently asked questions

Is it realistic to build a department budget from invoice data?

Yes. Invoices already contain everything you need: what was bought, from whom, at what price, on what date. Extracting that into a budget-ready format is the missing step - and it no longer requires manual work.

What about costs that do not come with invoices - internal allocations, payroll?

Invoice-based actuals cover external spend. Internal allocations and payroll typically come from separate systems. The budget combines both - Onpoint covers the external invoice layer.

How far back should invoice history go for budget planning?

Twelve months is typically enough to capture seasonal patterns and recurring costs. Two years helps identify trends. More than that, and the data becomes less relevant to current contracts and prices.

What if last year was unusual - a project year, a restructure?

You can filter or adjust for it. The value is not in copying last year blindly - it is in having a real baseline to adjust from, rather than a blank estimate.

Does this require Finance to change their budget process?

The core process stays the same. The difference is that managers start from pre-populated actuals instead of blank templates. Finance reviews real numbers rather than estimates - which typically reduces revision cycles.

Related resources

Planning

Build next year's budget from what you actually spent.

Invoice history, mapped to budget lines. No estimates. No guessing.

Use Onpoint Free See how it works