Procurement savings you can prove.
ProcSave reconciles your savings tracker with actual spending, calculates what was really realized, and gives Finance the evidence to approve it.
Early design-partner access. No spam.
Savings reconciliation
Illustrative preview
Nobody can say which savings actually landed
Forecast savings live in one file. Actual spend lives in another. By the time Finance asks, the two have drifted apart and the answer is a week of manual work.
Where the numbers live
- Savings_Tracker_FY26.xlsx200,000
- ERP_spend_export.csv18,412
- RE: Q1 approvalsn/a
Three sources, no agreement
The numbers live in three places
A savings tracker, an ERP export, and an approval thread. None of them agree, and none of them is the record.
Matched by hand
- Nordic Paper ASNordic Paper A/S
- Contract #4417Contract 4417-B
Reconciliation is done by hand
Someone rebuilds the comparison every quarter, matching supplier names and contract numbers row by row.
Packaging RFP
No supporting evidence
Source rows unavailable. Baseline not recorded.
The figure cannot be defended
Six months later nobody can reconstruct where a number came from, so Finance discounts it.
One place to prove what was realized
Reconciliation
Compare forecast against actual spend
ProcSave reads the tracker your team already keeps, matches it to your spend export, and applies your savings rules. Every figure opens to the rows behind it.
- Reads your existing spreadsheet, no template to adopt
- Normalises supplier names, currencies and dates
- Flags low-confidence matches instead of averaging them away
- Shows the inputs behind every calculated figure
Evidence
Hand Finance something they can sign
Realized savings are routed for review with the calculation, the source rows and the supporting documents attached. The decision stays with the number.
Supplier matching
- Nordic Paper ASMatched
- Contract #4417Review
- Packaging RFPMatched
18 of 21 resolved
Everything between the spreadsheet and the sign-off
Import your tracker
Reads the savings spreadsheet your team already maintains.
Import actual spend
Takes an ERP or accounts payable export for the same period.
Match suppliers
Resolves names, contracts and projects across both sides.
Compare forecast
Shows forecast against realized for every initiative.
Explain variance
Opens any difference down to the rows that caused it.
Keep the evidence
Source rows and documents stay attached to each result.
Route for approval
Finance approves, rejects, or sends an item back with a note.
Rules, not guesses
The figure comes from rules you can read, never from a model.
AI helps with the messy work. You control the final number.
Reconciliation falls apart when nobody can explain where a figure came from, so ProcSave splits the work and keeps the parts that need judgement with people.
AI maps
Files, suppliers, contracts and spreadsheet columns. Every suggestion carries a confidence level and can be corrected.
Rules calculate
Savings are produced by explicit rules with visible inputs. The same inputs always give the same figure.
Humans review
Low-confidence matches and unusual variances are queued as exceptions rather than absorbed into a total.
Finance approves
The final value is whatever Finance signs off. ProcSave records who approved it and when.
Everything we can say for now
ProcSave is procurement savings tracking software. It takes the savings tracker your team already keeps, reads your actual spending data, and works out how much of the forecast saving really landed. The result is a single view of forecast, realized, and Finance-approved savings, with the supporting evidence attached to each number.
No. Most tools help you record what you expect to save. ProcSave starts from the tracker you already have and compares it against what was actually spent. The job it does is reconciliation and proof, not forecasting.
With rules you can read. Each initiative gets a baseline, a comparison period, and a matching set of actual spend lines. ProcSave applies the rule, shows the inputs it used, and lets you open any figure to see the underlying rows. Nothing is a black box, and every calculation can be traced back to source data.
No. AI helps with the messy work: reading files, mapping spreadsheet columns, and suggesting which supplier, contract, or project a spend line belongs to. Those suggestions carry a confidence level and can be corrected. The savings figure itself is produced by rules, reviewed by your team, and approved by Finance.
Two things to start. Your existing savings tracker, as an Excel or Google Sheets export, and a spend export covering the same period, usually from your ERP or accounts payable system as CSV or Excel. Contracts and price lists are useful as evidence but are not required to get a first reconciliation.
Yes. Realized savings are routed to Finance for review. Each item can be approved, rejected, or sent back with a comment, and the decision is recorded alongside the evidence and the calculation that produced it.
Not on day one, and that is deliberate. ProcSave reads the tracker you already maintain rather than asking your team to rebuild it. Over time most of the manual reconciliation work moves into ProcSave, but your spreadsheet keeps working throughout.
Procurement teams of roughly three to twenty people in companies with 500 to 5,000 employees, tracking twenty or more savings initiatives in Excel or Google Sheets, and reporting those savings to Finance. It is aimed at teams who need the rigour of an enterprise savings platform without the cost and rollout of one.
ProcSave is in active development with a small group of design partners. We are not announcing a launch date, because we would rather get the reconciliation logic right with real trackers and real spend data first. Request a pilot and we will tell you honestly where things stand.
It starts with a 15 minute call about how your team tracks savings today. If it looks like a fit, we run a reconciliation on one recent period using your own tracker and spend export, then walk through the result together. You keep the output either way, and you tell us what is wrong with it.
Know which savings actually happened.
Turn your existing tracker and spending data into a Finance-ready view of realized savings.
Early design-partner access. No spam.