What makes a savings number Finance-credible? Three things. Most pipelines have one.
A consistent baseline. The baseline is what you're measuring savings against. Prior cost, budget line, or competitive bid, all three are legitimate. The problem is when different initiatives use different methods and nobody documents which one or why. Finance can't validate a number when the starting point shifts by owner.
A clean audit trail. Not a comment in a spreadsheet cell. An actual record of what the baseline was, where it came from, when it was set, who approved it. Something that holds up six months later when the person who entered it has moved to a different role.
Methodology applied before the number is entered. Most teams audit savings after the fact. By then the context is gone, the documentation is thin, and reconstructing the logic takes days. Finance-credible numbers are built on methodology that's enforced at the start, before anyone types a figure.
Most procurement pipelines have the number. They're missing the two things that make it defensible.
The baseline is the foundation
Every savings calculation starts with a baseline. It's the reference point that defines what "before" looks like, so you can measure how much better "after" is. The math is simple. The complication is that there are several legitimate ways to set the baseline, and they produce very different numbers for the same initiative.
Prior cost baselines work well for renegotiations. If you're renewing a contract and you pushed the rate down, the baseline is what you were paying, and the saving is the difference. Budget baselines make sense for new spend that didn't exist last year. Competitive bid baselines apply when you're running a sourcing event and the saving is the gap between the market rate and what you negotiated.
None of these approaches is wrong. The problem is inconsistency, when the choice of baseline shifts from initiative to initiative without documentation. A $400K saving calculated against prior cost and a $400K saving calculated against a budget line are two different things. Adding them together and presenting the total as a single number gives Finance no way to understand what they're looking at.
The audit trail has to exist in real time
The other piece that most procurement teams are missing is an audit trail that was built as the work happened, not assembled after someone asked for it.
When Finance questions a savings figure, the typical response is to go back through the spreadsheet, find the relevant emails, dig up the supplier quote, and try to reconstruct the logic from whatever documentation exists. That process takes time, assumes everything was saved correctly, and depends on people who may no longer be in the same role. It's a fragile way to defend a number that represents real work.
An audit trail that was built in real time doesn't have these problems. The baseline is documented when it's set. The approval is attached when it happens. The supporting data is linked at the time of entry. Six months later, when Finance asks, everything is already there. The answer to "walk me through the methodology" is a few clicks, not a few days.
That's the standard Clero holds every initiative to. Not because Finance demanded it, but because procurement teams deserve to walk into those conversations with the same confidence in their documentation as they have in their work.