| Field | Value |
|---|---|
| Description | A CFO, a head of procurement, and a commercial director read the same spend report and reach three different conclusions. Here is why. |
| Key Takeaway | A single spend report, built from one dataset, is routinely asked to answer three different questions at once: whether the budget holds, whether a category can be negotiated or consolidated, and whether a tender is priced competitively. A report built around one of those questions will quietly fail the other two, since each persona needs the same underlying data aggregated, classified, and presented in its own way. |
| Pearstop's view | A spend report that fails a CFO or a head of procurement is rarely a sign the report was built wrong. It is usually a sign one report was asked to do the job of three. |
| Pearstop's solution | Pearstop classifies spend to UNSPSC and matches every line to its contract and supplier record once, so a GL-level view, a category-level view, and a competitive view can all be generated from the same reconciling dataset. |
| Next step | Before your next board review, check whether the spend report in front of you was built to answer the specific question being asked of it, or a different one. |
Why one report cannot serve three readers equally
The same spend dataset sits behind a CFO's budget review, a head of procurement's renewal planning, and a commercial director's tender pricing. Each of them opens the same file, or the same dashboard, expecting an answer to a different question entirely.
What does a CFO actually need from spend data
A CFO reads spend data primarily at the general ledger level, watching for budget variance and overall financial exposure by department or cost centre. Spend reporting designed for this audience typically shows that a certain total was spent in a period, without the commodity-level detail that would explain which specific categories drove the number. That level of aggregation is exactly what a CFO needs to do their job, and exactly what makes the same report useless for the next two readers.
What does a head of procurement actually need from the same data
A head of procurement needs the opposite granularity: every line coded to a UNSPSC category, matched to a contract and a supplier, so a renewal conversation or a consolidation case can be built against a specific category rather than a department total. The GL total that satisfies a CFO tells a procurement lead nothing about whether three suppliers in the same category should become one.
What does a commercial director actually need from the same data
A commercial director, pricing a tender or defending a margin, needs the data read competitively. What does this category actually cost against the market, and where is the organisation's cost position relative to a bid it is preparing. The same spend figures, viewed through this lens, are a competitiveness question rather than a budget question or a consolidation question.
Where this exact gap surfaced
One hard FM client of ours ran directly into this during a board review. We will refer to them as Ferrow Services. A single spend report had been built for the CFO's quarterly review, aggregated by cost centre, and the head of procurement was asked in the same meeting to explain a renewal case using the identical document.
What happened when one report tried to answer two questions
The report could not support the question it was being asked. Cost centre totals said nothing about which specific supplier or category was driving a renewal decision, and the head of procurement had to reconstruct the category-level view from a separate spreadsheet, live, in front of the board. The underlying spend data was accurate throughout. The report simply was not built to answer the question asked of it in that room.
Why this is a structural problem, not a reporting mistake
Ferrow Services had not made an error in building the report. They had built a correct answer to one question and were then asked a second, unrelated question of the same document. Whereas a GL-level report and a category-level report both draw from the same underlying transactions, they require different levels of classification to actually answer their respective questions, and no single flat report can hold both views at once without being built for that from the start.
What this cost beyond the awkwardness of the meeting itself
The immediate cost was a board meeting that ran long and landed a renewal decision without the confidence a clean category view would have given it. The slower cost was less visible - the head of procurement's separate spreadsheet, rebuilt live, became the version of truth people trusted going forward, even though it had never been reconciled against the CFO's cost-centre figures. Two versions of the same spend now existed in the organisation, each believed by a different audience, with nobody tasked with checking whether they actually agreed.
Why the misalignment is common, not unusual
Ferrow Services is far from an isolated case. Industry research on spend data governance has found that the average organisation maintains three to five competing sources of truth for the same financial data.
Why do finance and procurement end up with different numbers from the same spend
Finance, procurement, and commercial teams routinely view the same spend data through different lenses, whether budget, compliance, or supplier value. Without a shared definition of basic terms such as savings or risk, each team's version of the report drifts slightly further from the others over time. This drift compounds. A small classification inconsistency that does not matter at GL level can misstate an entire category at the procurement level.
What shared definitions actually need to cover
Beyond the classification itself, the three readers need to agree on what basic terms mean before any of their reports can be compared reliably. A saving booked by procurement against a negotiated rate card is not automatically a saving the CFO's budget will show, if the volume assumptions behind it differ from what finance is actually forecasting. Agreeing what "saving," "risk," and "on-contract" mean across all three functions removes a second source of drift that reclassifying the data alone will not fix.
What is the actual fix for this misalignment
Three separate reports maintained in parallel compound the original drift rather than solving it. One classified dataset, coded consistently to UNSPSC and matched to contract and supplier records, is the actual fix. A GL-level view, a category-level view, and a competitive-pricing view can each be generated on demand from it, all genuinely reconciling to the same underlying numbers.
What this means for building a spend report
A report built to serve all three readers starts from the most granular, consistently classified version of the data. Every aggregation the CFO needs, the procurement lead needs, and the commercial director needs to be generated from that single classified base rather than from three independently maintained files.
How does Pearstop address this specific gap
Pearstop classifies spend to UNSPSC and matches every line to its contract and supplier record once. This means a GL-level summary for the CFO, a category-level breakdown for procurement, and a competitive benchmark view for the commercial director can all be produced from the same underlying dataset.
What changes once all three views reconcile to one dataset
A board conversation like the one Ferrow Services had stops requiring someone to reconstruct a second view live in the room. The CFO's number, the procurement lead's category breakdown, and the commercial director's competitive position all trace back to the same classified transactions. Accordingly, a disagreement in the room becomes a conversation about strategy rather than a dispute about whose spreadsheet is correct.
Does this earn its place in spend reporting
A spend report that works for a CFO and fails a head of procurement does not reflect the building of an incorrect report, but rather means one report was asked to do the job of three. The simple fix sits in the data underneath the report.
Veelgestelde vragen
Why do finance and procurement see different numbers in the same spend report?
Finance typically reads spend at general ledger level, watching budget variance by cost centre, while procurement needs every line coded to a category and matched to a contract and supplier. The same underlying transactions, aggregated differently for each question, can look like disagreeing numbers even when both views are accurate.
What should a CFO expect to see in a spend report that a procurement lead does not need?
A CFO needs cost-centre or departmental totals that show budget variance and overall financial exposure for a period. That level of aggregation deliberately hides the commodity-level detail a procurement lead needs for a renewal or consolidation case, which is why the same report rarely satisfies both readers at once.
How many versions of spend data does a typical organisation maintain?
Industry research on spend governance has found that the average organisation maintains three to five competing sources of truth for the same financial data, with each one reflecting a different team's lens on budget, compliance, or supplier value rather than a single reconciled dataset.
Can one spend report actually serve a CFO, a head of procurement, and a commercial director at once?
Yes, provided it is generated from a single, consistently classified dataset rather than three reports maintained separately. A GL-level summary, a category-level breakdown, and a competitive-pricing view can all be produced from the same classified transactions, which keeps all three genuinely reconciling to one source.
How does Pearstop solve the problem of spend data serving multiple audiences?
Pearstop classifies spend to UNSPSC and matches every line to its contract and supplier record once, so a CFO's budget summary, a procurement lead's category breakdown, and a commercial director's competitive view can each be generated from that same underlying dataset instead of three separately maintained files.
What should a board do when a spend report cannot answer the question being asked of it?
Treat it as a signal that the report was built for a different audience, not that the underlying numbers are wrong. The fix is reclassifying the spend data consistently enough to support every required view, rather than rebuilding a new report for each meeting as questions arise.
Not sure which UNSPSC code to use?
Paste any product or service description and get the correct 8-digit code instantly — or explore the full UNSPSC tree to understand the hierarchy.
Rae Thomas
Director of Operations, Pearstop
Rae heads up operations at Pearstop, in both the traditional and non-traditional sense. She's as committed to the internal success of the business as she is to the value clients get out of it, which is why she leads delivery on most projects and is the main point of contact for clients throughout.
LinkedIn →Further reading
The UNSPSC Mandate Nobody Budgeted For
A head office UNSPSC mandate rarely comes with budget or expertise attached. Here is how to scope it properly before it stalls as an unowned spreadsheet project.
Read more →ProcurementYou've classified your spend. Now what?
Charge lines like freight and fuel surcharges don't fit a product taxonomy, but dropping or misclassifying them quietly breaks your spend category totals.
Read more →
