Signing is not the same as receiving.
Most engagements end at signature, which is precisely where the risk of not receiving what you negotiated begins. An agreement is a statement about invoices that have not been issued yet, and nothing verifies that they match unless somebody checks them against the terms.
The saving is a forecast until an invoice proves it
Between an executed agreement and a realised saving sit configuration steps, effective dates, credit applications, tier changes and billing mechanics — each an opportunity for the outcome to diverge quietly from the intent. Divergence is rarely dramatic. It shows up as a rate that does not match the schedule, a credit that never applies, a discount landing on the wrong scope. All small, all persistent, and all invisible without a deliberate comparison.
Nobody owns the comparison
Procurement's involvement ends at signature. Finance receives an invoice with no visibility of the negotiated terms. Engineering never saw the agreement. The comparison sits between three functions and is therefore performed by none of them.
The baseline gets rewritten in hindsight
Without a baseline locked before negotiation, the saving is measured against a number that is itself in dispute after the fact — and every party remembers a different one.
Consumption changes mask the terms
Spend moves for many reasons at once. A discount landing incorrectly is easily absorbed into normal variance, and stays absorbed until someone reconciles the terms specifically rather than watching the total.
It requires holding the terms and the billing data side by side
Verification is not complicated analysis. It is precise, repeated work that requires access to both the agreement and the billing detail, plus a baseline that was fixed before anyone knew the outcome — which is the part most organisations no longer have by the time they want to check.
- 01
A baseline established after the result is known is not a baseline, and any saving measured against it can be argued in either direction.
- 02
Discounts and credits apply through mechanics that are not always visible in summary reporting, so verification requires line-level billing data.
- 03
Effective dates and ramp schedules mean the first correct invoice may be months after signature — and the intervening months are where errors survive undetected.
- 04
Commitment tracking against a spend obligation needs continuous measurement, not an annual check when the shortfall is no longer recoverable.
- 05
Definitions decide the number: hard reduction, repricing and cost avoidance are different things, and conflating them produces a figure finance will not accept.
- 06
Anything self-certified by the party being paid for it will be disputed, which is why the verifying signature has to belong to the client's own finance function.
What verification compares
Verification is a reconciliation: the terms as executed against the invoices as issued, measured from a baseline locked before the negotiation began.
- 01The baseline, locked and countersigned before negotiation opened
- 02Executed agreement terms: rates, discount schedule, inclusions, effective dates
- 03Line-level billing data for each period after the effective date
- 04Realised effective rate per service, compared against the negotiated schedule
- 05Credit application: whether credits applied, to what, and at what rate of drawdown
- 06Commitment tracking against any spend obligation, measured continuously
- 07Support tier and its billing basis after the agreement took effect
- 08Commitment instrument benefit landing where the model assumed
- 09Ramp compliance where the agreement is staged
- 10Savings categorised: hard reduction, repricing, and cost avoidance kept separate
- 11Variance between modelled and realised outcome, with each cause identified
- 12Any term not yet reflected in billing, tracked until it is
What we determine
Whether the terms are being applied
Line by line, whether the executed rates, discounts and credits appear correctly on the invoices — and where they do not, exactly which term is not landing and what it is costing per month.
The realised saving, by category
Hard reduction, repricing and cost avoidance reported separately rather than combined, because they mean different things to the P&L and combining them produces a number finance will not sign.
Variance and its causes
Where the outcome diverges from the model, each cause attributed — a billing error, a consumption change, or a modelling assumption that did not hold. The distinction determines who fixes it.
Commitment trajectory
Whether you are tracking to meet any spend obligation, measured continuously, so a shortfall is visible while there is still time to act rather than at the point it becomes a liability.
The verification instrument is a reconciliation your own controller or CFO signs. Not our claim about what we saved you — your finance function's statement, reconciling the locked baseline to the executed agreement and the invoices that followed.
- Whether to raise a billing correction, with the evidence already assembled
- Whether realised savings match what was modelled, and where they do not
- Whether commitment obligations are on track or need intervention
- Which modelling assumptions proved wrong, so the next decision is better informed
- Whether credits are drawing down as expected or expiring unused
- What the verified new baseline is for the next commercial cycle
What we hand over
The savings certificate
A one-page reconciliation from locked baseline to executed agreement to realised billing, signed by your own controller or CFO. Client-verified, not self-certified.
Term application register
Every negotiated term with its billing status — applied, partially applied, or not yet landed — tracked monthly until each one reconciles.
Variance analysis
Modelled versus realised, with every difference attributed to a cause and a route to remedy where one exists.
Check them
Stage 00 is a 30-minute qualifying call at no cost. If the timing or the estate does not justify an engagement, we say so on that call.