Consolidated supplier spend reporting across cost centres
Problem
Budget holders across departments raise purchase orders separately, each against their own cost centre in the finance and ERP system. The same supplier ends up entered under several near-identical names, because whoever raises the order types it from memory: Acme Ltd, Acme Limited, ACME UK. Nobody can produce a single total for what the organisation spends with that supplier without exporting every ledger and cleaning the names by hand, which happens, if it happens at all, once a year when finance closes the books. A supplier crossing a tender threshold, or three departments buying the same category from different suppliers at different prices, goes unnoticed until an auditor or a new controller stumbles on it months later.
Product idea
A reporting layer that pulls purchase order and invoice lines from the finance and ERP system into one data model, matches supplier name variants to a single supplier record, and lets a procurement lead or controller ask plain questions: total spend with a supplier this year, spend by category, which cost centres are buying from suppliers nobody else recognises. It flags when combined spend across cost centres approaches a threshold the organisation sets itself, presented as a figure to review rather than a compliance judgement. It does not raise purchase orders, approve spend, or write anything back to the ERP; it sits alongside it as a read-only view built for the question nobody currently has time to answer.
Who it is for
Procurement leads sponsor it. Finance managers, financial controllers and budget holders use the query surface before committing to a new supplier, a renewal, or a category review.
Possible first version
A web dashboard that ingests a manually exported CSV of purchase order and invoice lines from finance, runs fuzzy matching to group supplier name variants into single records for review and merge, and shows spend broken down by supplier, category and cost centre. Includes a natural-language query box answering questions against that data. Out of scope for version one: any live connection to the ERP or procurement system, automatic threshold alerts routed anywhere, and multi-currency consolidation. Every figure traces back to the uploaded export, and re-running it means uploading a fresh one.
- Build classification
- Workflow application
- Rough effort
- 4-6 week first release
- Roles involved
- Procurement lead, Finance manager, Financial controller, Budget holder
- Relevant to
- Professional club, League office, Federation / governing body, Venue & stadium operator, Collegiate athletics
- Systems in play
- Finance and ERP systems, Procurement and purchase order systems, Spreadsheets
- Product framing
- Analyse data
Questions we get asked
What do we need to hand over before this can tell us anything useful?
A period export from the finance and ERP system covering purchase order and invoice lines, ideally the last twelve months, with supplier name, cost centre, category and amount on each line. The first run also needs someone from procurement or finance to sit with the supplier matching for an hour or so, because automatic grouping will get most near-duplicates right but not all of them, and nobody should trust a total spend figure that hasn't had at least one human pass over it.
Does this replace our ERP or procurement system?
No. It is read-only reporting sitting alongside the finance and ERP system, not a replacement for it. It never raises a purchase order, approves spend or writes anything back. The ERP or procurement system stays the system of record for every transaction; this tool exists purely to answer a question that system was never built to answer quickly, which is what a given supplier actually costs once every cost centre is added together.
Our finance team already pulls this into a spreadsheet at year end. Why build another tool?
Because a year-end export tells you what already happened, after the decisions that mattered were made. The value here is being able to ask the same question in March, before a renewal is signed or a third department quietly starts buying from a fourth supplier in the same category. If nobody in procurement or finance would actually run that query mid-year, this saves little beyond tidying up work finance already does once a year, and is not worth building.
Who has to keep the supplier list clean once this exists?
Usually the procurement lead, and it is an ongoing task rather than a one-off setup. New invoices bring new name variants, and automatic matching will occasionally group two different suppliers together or miss a genuine duplicate, so someone needs to review and merge on a regular cadence, weekly or monthly depending on volume. Nobody should assume this runs itself once the first import is clean.
Is this your workflow?
Tell us one sports workflow that still runs on paper, spreadsheets, WhatsApp or an outdated system. We will map it and show you what a simpler product looks like.
Tell us about itMore in Finance, procurement & vendors
- Delegated approval authority register and expiry trackerA register that tracks who holds delegated financial approval authority and at what threshold, flags entries before they lapse, and exports audit-ready evidence instead of a scramble through old emails.
- Expense approval delegation and escalation routerA rules-driven router that reassigns expense approvals to a backup when the named approver is unavailable, so claims stop sitting unopened in an inbox.
- Invoice to purchase order match and exception queueA rules-driven workflow that matches invoice lines to purchase orders automatically and routes only the mismatches to a queue, instead of a clerk checking every line by eye.