A saving without a baseline is a discussion.
The subject here is not the buying process but its financial side: what a commercial term does to the result, what a payment term does to liquidity, and whether a reported saving can be evidenced at year end.
Recorded beforehand, or it does not count.
A savings programme without a recorded starting basis produces a discussion at year end, not evidence. FinanceOS attaches the saving to a measure with a baseline and an owner.
The baseline is fixed beforehand
Quantity, price, terms and period are recorded before the measure runs. After the fact, a baseline is an opinion.
The saving has an owner
Who committed to it, by when, against which measure. Without an owner a commitment becomes an expectation.
It can only be claimed once
Counting the same saving twice is the most common way programmes add up on paper and never arrive in the result.
The effect is measured, not reported
Realised against promised, on the same measure, with the same period boundary.
The same discipline applies in Investment, Cost & Value for value delivered and in Sustainability & ESG Finance for a disclosure. It is an evidence model, not a procurement topic.
What this domain is responsible for.
Three quantities, three recipients.
The contribution of this domain is the connection: what is decided in procurement arrives at three places in the finance function.
01 · Terms
Price, tier, rebate → result
02 · Payment terms
Due date and discount → liquidity
03 · Commitment
Order and framework → budget and forecast
04 · Matching
Order, receipt, invoice → approval
05 · Baseline
Measure with an owner → evidenced saving
Where this domain appears on the horizontal axis.
A domain on its own is a responsibility. It becomes visible where a business record runs through it.
Operational procurement stays in your purchasing system.
Demand, tendering, supplier selection and order processing are not the subject of this domain.
Your purchasing system
Demand, tendering, purchase order.
Your ERP
Goods receipt, invoice posting, supplier account.
Your supplier portal
Communication and master data.
FinanceOS
Terms, payment days, commitment, baseline, evidence.
What FinanceOS contributes is the connection of terms, payment days and commitment to liquidity and result — and the evidence discipline that makes a saving provable.
What is verified in the product in this domain today
Commitment and matching
Verified in the product
Commitment from order and framework agreement, matching of order, receipt and invoice.
Saving against a baseline
Pilot or validation
A measure with a baseline and an owner, with a lock against double counting.
Supplier risk from a finance view
In active development
The assessment of financial dependency per supplier.
What is not marked, we do not claim.
Maturity per capability is stated on the product status page. What we can evidence today
How do you evidence a reported saving today?
If the answer is a spreadsheet somebody maintains, that is the entry point. Thirty minutes on a live savings programme.