Three procurement teams. Three baselines. Three different definitions of savings. All three are hitting their targets. None of their numbers are comparable.
Team A baselines against last year's actual spend. A 10% reduction is a hard saving.
Team B baselines against the budget line. Came in under? Saving. Even if spend went up year over year.
Team C baselines against the lowest competitive bid. The saving is the gap between what they could have paid and what they negotiated.
All three methods are legitimate. All three produce completely different numbers for the same type of initiative. Now put all three teams inside the same company and ask them to roll up a portfolio total. That number means nothing. It's three methodologies wearing one spreadsheet.
This is why Finance pushes back. Not because they distrust procurement, but because the number they're handed doesn't have a consistent methodology behind it. And without that, they can't validate it.
The fix isn't an audit after the fact. It's locking the baseline method at the start of every initiative, before anyone enters a number. That's the first thing Clero does.
Why all three methods are valid but the mix isn't
Each of those baseline approaches has a legitimate use case. Prior cost works well for renegotiations where there's a clear historical spend to measure against. Budget-based baselines make sense for new spend categories where there's no prior cost on record. Competitive bid baselines are the right tool when you're running a new sourcing event and the saving is the gap between what suppliers offered and what you negotiated.
The issue isn't which method a team uses. It's that using different methods across different initiatives, or across different teams, makes the totals incomparable. A $500K saving calculated against prior cost and a $500K saving calculated against a budget line are not the same thing. They might both be real and defensible, but they can't just be added together and handed to a CFO as a single number without explanation.
The rollup problem is a design problem
When Finance pushes back on a savings number, procurement often reads that as skepticism. Usually it isn't. Finance would love to be able to validate the number quickly and move on. The problem is that a mixed-methodology total doesn't give them a path to do that. They'd have to go line by line, understand which method was used for each initiative, and rebuild the calculation themselves. Nobody has time for that.
The result is a discount. Finance applies a conservative haircut to account for the methodology uncertainty, and the number that gets reported up the chain is smaller than what procurement delivered. That gap, between what was actually achieved and what got credited, is one of the most persistent frustrations in procurement leadership.
Consistency is the starting point
Methodology consistency doesn't mean every team has to use the same baseline method for every initiative. It means the method is defined and documented at the start, applied correctly, and visible when someone needs to verify it. When that's in place, a multi-team rollup is credible because Finance can see exactly how each line was calculated.
That's what Clero is built to do. The baseline method is set when an initiative is created, not cleaned up after the quarter closes. The result is a portfolio total that actually means something when you put it in front of leadership.