Not because you are unprepared. Because the data is not where you can reach it.
The CFO asks: "Why are we 18% over on IT services this quarter across all business units?"
You know the number is roughly right. But you cannot explain it on the spot.
Getting the answer means pulling ERP reports, tracing invoices, cross-referencing department trackers, and figuring out which charges drove the variance.
That takes time. Which means your answer comes the next day - or later.
The CFO remembers this.
It is not a competence problem. It is an access problem. The data that would answer the question is buried in invoices that have never been properly read.
Three things consistently prevent an immediate answer.
When the CFO asks a question, the answer is technically there. But assembling it from the available systems takes hours.
Every invoice processed as it arrives. Supplier, item, amount, date - linked to the budget line it belongs to. Not waiting for month-end.
Finance needs to see all departments, all suppliers, all categories - not one cost centre at a time. The question is rarely about one department.
When a budget line is over, the reason should be visible immediately - which invoices, from which supplier, for what item. No digging required.
If the CFO asks about a supplier relationship - volume, pricing, trends - that should be answerable from invoice history, not a procurement meeting.
The goal is not to prepare for every possible question. That is impossible.
The goal is to have the data structured so that any reasonable question has an immediate answer.
That means:
When the data is structured this way, the CFO question becomes an opportunity - not a scramble.
Variance explanations ("why is this 20% over?"), supplier comparisons ("are we paying too much for X?"), and cross-department questions ("which business unit is driving the IT cost increase?") are the most common.
Yes - if the data is structured correctly. When actuals come from invoices continuously, not from a month-end close, you already have the answer before the question is asked.
Late and disputed invoices are a real issue - but they are also invisible in current setups. With invoice-based tracking, they show up immediately, which means they can be flagged before the period closes.
Onpoint is not a replacement for the ERP. It runs alongside it, giving you live visibility during the month. ERP handles the official numbers at close. Onpoint handles the questions in between.
It is an option. Some finance teams share a CFO-level dashboard view. Others use Onpoint as their own tool and surface answers via their existing reporting. Both work.
How to get a single spend picture across all departments without the ERP.
AccuracyWhy Finance and department numbers never align - and what actually fixes it.
PlanningWhy department budgets are built on estimates - and how to build them from real actuals instead.
Live invoice data, mapped to budget lines, across every department.