Spend intelligence: how it works and what to require
Proconomy spend intelligence combines procurement and transaction data from ERP and related systems into one connected view by category, supplier, plant, entity and period. It highlights fragmentation, off-contract buying and supplier concentration, and lets an authorised user launch the sourcing or supplier workflow directly from what the data shows.
Spend questions you cannot answer today. Answered from your own data.
Not a dashboard. Twenty-four findings that lead directly to an event, a negotiation or a supplier decision.
Consolidation and leverage
- The same material bought by several plants at different prices
- One category split across suppliers with no volume commitment
- Fragmented tail spend inside a managed category
- Group volume that has never been aggregated to a negotiation
- Duplicate suppliers created across entities
- Categories buying below the threshold that would trigger an event
Contract leakage
- Spend running outside an agreement you already negotiated
- Contracted price not applied at the point of order
- Agreements approaching renewal with no utilisation
- Off-catalogue buying where a catalogue exists
- Rebate and volume tiers not being reached
- Purchases from suppliers whose agreement has lapsed
Risk and concentration
- Single-source exposure by category and by plant
- Supplier concentration measured across the group, not per entity
- Spend with suppliers whose qualification has expired
- Geographic concentration in a category
- New suppliers introduced without going through onboarding
- Spend growth with a supplier under a corrective action
Planning and budget
- Category spend against plan by entity
- Price movement on a commodity across periods
- Demand seasonality feeding event timing
- Cost centre behaviour ahead of budget cycles
- Savings pipeline against realised outcomes
- Categories with no owner assigned
Analysis that ends in a report. Or analysis that opens an event.
Eight mechanisms, and the one that matters is the last.
| Mechanism | What it has to do |
|---|---|
| Multi-source ingestion | Transaction, purchase order, invoice and supplier data from every ERP instance and entity, without consolidating those systems first. |
| Classification with review | Transaction descriptions and supplier names are mapped to a category structure your team recognises. Low-confidence mappings go to a category owner rather than into a report, and corrections are retained. |
| Supplier normalisation | The same supplier appearing under several names, codes and entities is resolved to one record, which is what makes group concentration measurable at all. |
| Group-to-line drill-down | From a group total to a single transaction through entity, plant, category and supplier, without exporting to a spreadsheet. |
| Opportunity identification | Fragmentation, off-contract activity, concentration and price variance surfaced as named opportunities against a category and an owner. |
| Opportunity to event, in one step | An identified opportunity opens a sourcing event with the suppliers, volumes and history already attached — which is the step that usually never happens. |
| Role and entity scoped access | Group leadership sees consolidated spend; a plant team sees its own. The same data, bounded by permission. |
| Tracking from identified to realised | The link between an opportunity, the event it produced and the outcome that followed, so a savings pipeline can be reviewed rather than asserted. |
A description of what the practice requires, not a feature list.
One engine. Different leakage by sector.
Where the money is going that should not be, by industry.
Automotive
Commodity and tier concentration across programmes, and the same component bought under different part numbers by different plants.
Building materials
Delivered cost by plant for the same material, where logistics makes the lowest ex-works price the wrong answer.
Industrial equipment
Project versus repeat spend split, and MRO categories bought locally that could be aggregated.
Consumer electronics
Component-level exposure across SKUs, so an end-of-life notice can be assessed against every product that uses the part.
Five questions. Asked on your own messy data.
A prepared dataset proves nothing about your classification problem.
- Run classification on your own messy data, not a prepared set. What proportion needs human review, and where does that review happen?
- Show how the same supplier under four different names across three entities is resolved into one record.
- What happens after an opportunity is identified? If the answer is "export it", the analysis will not change anything.
- Can a plant see its own data without seeing another plant's, from the same model?
- How is a corrected classification retained, and does the correction improve later mappings?
Definitions. Asked and answered.
No. Proconomy reads procurement and transaction data from connected systems and holds the analysis context. The source systems remain authoritative, and approved outcomes are written back to them.
Low-confidence mappings go in front of a category owner rather than into a report. Every confirmation and correction is retained, so the structure gets more reliable as your own team uses it. Accuracy on your data is something we measure with you during scoping, on your categories.
Yes. Access is role- and entity-based. Group leaders can see consolidated spend while plant teams see the context relevant to their operation.
Insight-to-action. An authorised user can launch a sourcing, supplier or contract workflow directly from what the data shows, and the link between the opportunity and the completed action is tracked.
It shows you where the money is going that should not be: the same material bought from four suppliers at three prices, spend running outside agreements you already negotiated, and concentration you had not measured. The value is in your own data, and you will see it on your own data in the first session.
Spend analysis is the process of collecting, cleaning, classifying and examining purchasing data to understand what an organisation buys, from whom, at what price and under which agreements. It is used to identify consolidation opportunities, contract leakage, supplier risk and categories that have never been competitively sourced.
Spend under management is the proportion of total third-party spend that is actively governed by procurement — bought through approved routes, against negotiated agreements, with visibility of supplier and price. Spend outside that boundary is typically where price variance and compliance findings concentrate.
Spend analysis describes the historical picture. Spend intelligence extends it to what should be done next and connects the finding to the action — opening a sourcing event, flagging a lapsed agreement or raising a concentration exposure — so the analysis produces work rather than a report.
Tail spend is the large number of low-value transactions that together account for a small share of value but a large share of transactions and suppliers. It is usually unmanaged because the effort of running a sourcing event exceeds the value of any single purchase, which is what changes when event setup effort falls.