The spend baseline comes before the savings claim
Every procurement function claims savings. Few can show a baseline that finance signed. Until that exists, every number is negotiable.
Nexolve TechnologiesDelivery team
The argument that repeats every year
Procurement reports savings. Finance asks where they show up in the P&L. Procurement answers with a spreadsheet; finance answers with scepticism. The cycle repeats at every budget review, and both sides leave with less trust than they brought.
The root cause is almost never effort or intent. It is that the two functions are counting from different baselines, with different category trees, refreshed at different times.
What a real baseline looks like
A spend baseline is a reconciled cube: last-twelve-months spend, by category, supplier and entity, tied back to the general ledger. Finance signs it. Savings are then measured as movements against that signed position, using a methodology — price reduction, demand reduction, avoidance — that was agreed in advance.
This is unglamorous data work: supplier normalisation, category mapping, entity reconciliation. It takes weeks, not days. It is also the only version of savings reporting that survives a CFO question.
Where to start
Start with the top categories by addressable spend, not with a perfect taxonomy. Baseline those, agree the methodology on one live sourcing event, and expand. A baseline that covers 80 percent of spend and is signed beats a perfect model nobody trusts.
Tools help — we run this on SpendConsole and SAP Analytics Cloud — but the signature from finance is the deliverable, not the dashboard.
