Product · Spend Intelligence

Spend analysis software for every category you buy

See what you spend by category, supplier, plant and contract status, worked out from your order lines at the moment you open the page.

A reporting layer, not a data warehouse. It reads the purchase orders you already hold rather than a nightly extract — and it tells you where the numbers stop being reliable.

Spend · as the order lines stand Illustrative
System updatedRead when you open the page — there is no cube to rebuild
The grid · category down, plant across Illustrative
Rows
Category · top level
Columns
Plant
Measure
Quantity × unit price, per line
Tab
Overall · direct and indirect sit beside it
Grand totalCompared against an independent sum of the same linesReconciles
System updatedAny two of seven dimensions, changed from two dropdowns
What is missing · counted, not hidden Illustrative
Category coverageShare of spend carrying a category from your own treeOn the page
Uncategorised linesListed highest value first, with order and supplierTo fix
No plant on the lineGets its own bucket rather than leaving the totalBucketed
Mixed currenciesShown as a dimension — nothing is convertedAs transacted
Rule appliedThe gaps are on the front of the page, not in a footnote
The patterns · worked out for you Illustrative
Tail suppliersEveryone past eighty per cent of spend, category by category80%
Consolidation candidateA category carrying ten or more tail suppliersFlagged
Price outlierA supplier fifteen per cent or more off its peers for the same part15%
What moved the quarterSplit into price, volume and mix, with the reason in wordsExplained
Human decisionWhat to do about it is a decision, and it is yours

The grid reads your order lines when you open the page. There is nothing to rebuild.

The same question. A pivot table, or a page.

Most spend analysis is an export, a clean-up and a pivot that is out of date before it is shared.

A quarterly export
A page you open
A quarterly exportSomeone pulls an extract and spends a week cleaning it
A page you openThe page reads your order lines as they stand
A quarterly exportThe pivot is rebuilt by hand every quarter
A page you openTwo dropdowns change the cut
A quarterly exportThe view is as old as the extract
A page you openThe view is as current as your last purchase order
A quarterly exportCategories are mapped in the spreadsheet, then lost
A page you openCategories come from your own tree, and the gaps are counted
A quarterly exportNobody can check whether the total is right
A page you openThe grid total is checked against an independent sum, and the page says so
A quarterly exportThe findings live in one analyst’s file
A page you openEveryone with access opens the same page

The cut

Seven ways to slice it. Any two at a time.

The grid takes one dimension down the side and one across the top. These are the seven it can use, and what each one is counted from.

Month Time

Spend by month. The seasonality view carries twenty-four of them so you can see the shape of a year rather than a quarter.

Top level Category

Your own category tree, bucketed at its top level. Direct and indirect are read from the category, not guessed from the description.

Supplier Supplier

The supplier on the order, or its parent company where you have set the parent link. Rolling up to a parent is one level, not a full hierarchy.

Plant Plant or location

The plant the order was raised for. Lines with no plant get their own bucket rather than disappearing from the total.

Code Cost centre or GL

The code as it sits on the order line. Where there is no cost centre the GL code is used instead.

As transacted Currency

The currency each line was raised in. Nothing is converted, so this dimension shows you the mix rather than hiding it.

On or off Contract status

Whether the order is linked to a contract. This is what contract coverage is counted from, and what the off-contract views are built on.

How a number gets made

Six steps. The last one is yours.

Five of them are arithmetic you can check. The decision about what to do is not automated, and this page is honest about where it stops.

  1. 01 System

    The orders are already in scope

    Every purchase order raised in Proconomy counts from the moment it exists. Orders pulled from your ERP join them when a sync runs.

  2. 02 System

    Lines are read, not pre-aggregated

    Each line counts as quantity times unit price, never a header total. There is no nightly build and no stored spend table, so the page reflects what the lines say now.

  3. 03 Rule

    The grid is totalled, then checked

    Row, column and grand totals are computed, then compared against an independent sum of the same lines. The page tells you whether the two reconcile.

  4. 04 System

    What is missing is counted, not hidden

    Lines with no category, no plant or no cost centre get their own bucket. Category coverage and contract coverage are shown as a share of spend.

  5. 05 System

    The patterns are worked out for you

    Supplier concentration, the tail beyond eighty per cent of spend, price spread for the same part across plants, and a three-month category outlook.

  6. 06 Human

    You decide what to do about it

    Nothing starts from this page. What the numbers show becomes an action you record and track, or a sourcing event you open yourself in the sourcing module.

Core capabilities

What spend analysis software has to get right.

The pivot

Any two of seven dimensions, and a total that proves itself

  • One dimension down the side, one across the top, changed from two dropdowns
  • Row, column and grand totals, with an independent check on the grand total
  • Overall, direct and indirect each get their own tab

Category coverage

How much spend carries a category, and exactly which lines do not

  • Coverage is shown as a share of spend, not a count of lines
  • The highest-value uncategorised lines are listed with their order and supplier
  • Direct and indirect come from your own tree rather than from our guess

Contract coverage

The share of spend running through an agreement, and the share going round it

  • An order counts as on-contract when it is linked to one — a binary, not a score
  • Off-contract spend breaks down by category, by supplier and by transaction
  • Each off-contract category carries a suggested next step in plain words

Tail spend

The suppliers sitting past eighty per cent of spend, category by category

  • Suppliers ranked by spend; everyone after the eightieth percentile is tail
  • A category with ten or more tail suppliers is flagged as a consolidation candidate
  • The figure shown is the tail spend in those categories — not a saving

Price spread for the same part

What you pay for one part across plants, and across suppliers

  • A heat map of part against plant, and a cross-plant benchmark for one part
  • A supplier is flagged when its average price sits fifteen per cent or more off its peers
  • Those peers are your own suppliers for that part — nothing is compared to the open market

Why the number moved

Quarter on quarter, split into price, volume and mix

  • A waterfall showing which of the three moved the total
  • A written explanation of the change sitting beside it
  • Twenty-four months of monthly spend for the seasonal pattern underneath

Where spend sits between documents

Requisition, order, receipt, invoice — and the value stuck between them

  • A flow across the four document stages, by value rather than by count
  • Shows where spend is committed but not yet received or invoiced
  • Needs requisitions, receipts and invoices in Proconomy to be complete

A written briefing

Ask a question about your spend and get an answer with suggested actions

  • Written from your own order, invoice, supplier and contract data
  • Each suggestion can be accepted or rejected, and a rejection asks for the reason
  • Producing it sends that spend data to our AI provider — your IT team will want to know

Features

Spend analysis software that holds its own rules.

Five groups of features, and not one of them depends on someone remembering the policy.

Numbers that check themselves

Every measure has a definition you can read, and the total proves itself.

  • Spend is quantity times unit price on each line, never a header total
  • The grand total is compared against an independent sum, and the page says whether it reconciles
  • Contract coverage is spend on orders linked to a contract, divided by total spend
  • Thresholds are stated outright — eighty per cent for tail, fifteen per cent for a price outlier
  • Nothing here writes back to your ERP or changes an order

How the numbers are built

Definitions you can check. Not a black box.

  • Spend is the sum of quantity times unit price on each order line. It is never a header total, so a line corrected after the order was raised is reflected as soon as it changes.
  • The grid total is compared against an independent sum of the same lines, and the page states whether the two reconcile rather than leaving you to trust it.
  • Contract coverage is spend on orders linked to a contract, divided by total spend for the year to date. Nothing in it is estimated.
  • Price variance is the average spread around each part’s own mean price. It measures spread, not a gap against a contracted or target price, and we would rather name that than let it be read as savings.
  • The tail threshold is eighty per cent, the consolidation flag is ten suppliers, and the price outlier flag is fifteen per cent. Those numbers are fixed rather than tuned per customer.
  • The three-month category outlook is a straight-line fit over the last twelve months. It is arithmetic, not a model, and it labels its own confidence.
  • Nothing on this page writes back to your ERP or changes an order. It reads.

What it will not do

The boundaries, including the awkward ones.

Some of these are deliberate and some are simply not built. Each one says which, because you will find out either way.

It does not take a spend file

There is no CSV or Excel upload and no data-warehouse connection. It reports on the purchase orders held in Proconomy, including those pulled in from your ERP. If the spend you most want to analyse will never have an order in Proconomy, this is not the tool that will analyse it.

It does not classify your spend for you

Categories come from the category already on the order line. There is no automatic classifier running over historical spend, no confidence score and no correction queue. What you get instead is the list of uncategorised lines, highest value first, so somebody can go and fix them.

It does not convert currencies in the grid

Each line counts in the currency it was raised in, so a mixed-currency organisation gets a mixed-currency total. You can cut the grid by currency, which shows you the mix rather than solving it. This one is a gap, not a design decision.

You cannot click a number and see the orders behind it

The grid is a grid. There is no drill-through from a cell to the transactions that make it up. The off-contract view is the exception — its transaction table links to each order and supplier.

It does not export

No CSV, no Excel, no PDF out of the spend grid. If your month-end pack needs a file, this will not produce one today.

It does not restrict spend by plant or category

Access is by organisation, and on some pages by role. A plant manager cannot be limited to their own plant’s spend, and there is no mechanism that would do it. Ask us about this before you open the page to a wide audience.

It does not calculate savings

It shows spend, concentration and price spread. It does not model a saving, track one, or report what an identified opportunity turned into. The consolidation figure is the spend sitting in those categories, not money you would keep.

It does not benchmark you against the market

Price comparison is internal. The peers a supplier is measured against are your own suppliers for the same part. There is no external index and no cross-customer data.

Nothing is launched from a finding

There is no button here that opens a sourcing event, a supplier review or a contract action. You can record an action against a finding and track it to done, but the page will not start the work for you. If that is the capability you are buying, say so early.

Two spend questions. Two honest answers.

1

What do we spend on one category, across every plant?

Set the rows to Category and the columns to Plant. Every order line is grouped by its top-level category and the plant it was raised for, with row, column and grand totals and the reconciliation check beside them. Then switch to the direct tab for the price heat map, which shows whether the same part costs different money at different sites.

2

Which categories are spread across too many suppliers?

The tail view ranks suppliers by spend and marks everyone past the eightieth percentile as tail. A category carrying ten or more of them is flagged as a consolidation candidate, with the tail spend in that category shown beside it. That figure is what is in play, not a saving — what to do about it is a decision you make in the sourcing module.

Where the data comes from

It reads your orders. It does not become your warehouse.

Orders raised in Proconomy count immediately

Anything ordered through intake, sourcing or procure-to-pay is in scope the moment the order exists. No load step, no waiting for a build.

ERP orders arrive through a connector

Connectors exist for SAP S/4HANA, Oracle Fusion Cloud, Microsoft Dynamics 365, SAP Ariba, Coupa, GEP SMART and a configurable REST endpoint. They pull suppliers, parts, orders, receipts and invoices.

A sync is started by a person or by your system

Someone with the right role runs it, or your system calls our webhook. There is no timer running quietly in the background, and we would rather tell you that than let you plan a month-end around one.

Orders pulled from an ERP arrive without a category

The sync brings the part, quantity, price, currency and plant — not the category or the cost centre. Those lines land as uncategorised until somebody assigns them, which is exactly why category coverage sits on the front of this page.

Your ERP stays the system of record

The connectors only pull. Nothing here writes to your ERP, changes an order or touches your books.

Bring one category and we will show you its real shape.

Your own orders, your own tree. You will see the coverage gaps as quickly as the totals, which is the part most demonstrations leave out.

Request a demonstration

Security, compliance and recognition

Checked by auditors. Judged by the industry.

Where each compliance programme stands, and what the procurement industry has given us so far.

Security and compliance

Awards

Five, presented on stage at three industry events.

  • Autonomous Procurement Platform of the Year
  • Procurement Technology Innovation Award
  • Unified Procurement and Supplier Management Platform
  • Procurement Startup of the Year
  • AI in Procurement or Supply Chain Award — Solution Provider

See the events and the trophies

Before you book anything. Answered honestly.

What is spend analysis software?

Spend analysis software takes the purchases an organisation has already made and makes them answerable — what was bought, from whom, for which site, under which agreement, and how that has moved over time. The useful version does two things most spreadsheets cannot: it stays current without somebody rebuilding it, and it is explicit about which parts of the picture are incomplete, so a category manager knows which numbers they can take into a negotiation.

Does this replace our ERP?

No, and it is not trying to. Your ERP keeps the books and remains the system of record. This reads purchase orders — the ones raised in Proconomy, plus any pulled in from your ERP through a connector — and reports on them. Nothing here writes back, changes an order or posts anything.

Can we upload a spend file, or connect our data warehouse?

No. There is no CSV or Excel upload for spend and no warehouse connection. Spend has to arrive as purchase orders, either raised in Proconomy or pulled from your ERP. A prospect whose main need is analysing historical extracts from systems they will never run orders through is a poor fit for this, and we would rather say so now.

Does it classify our spend automatically?

No. The category comes from the category already on the order line, against your own tree. There is no classifier running over historical spend, no confidence score, and no model learning from your corrections. What the page gives you instead is category coverage as a share of spend, and the list of uncategorised lines ranked by value so the gap can be closed by hand.

How current are the numbers?

For orders raised in Proconomy, as current as the orders themselves — the page recalculates when you open it, and there is no cube to rebuild. For orders pulled from your ERP, as current as the last sync, and a sync runs when a person starts one or your system calls our webhook. There is no scheduled sync today.

Can we see spend across all our entities in one view?

Not in the grid. The grid reports one organisation at a time, and a group user picks one subsidiary at a time on the briefing page. If a consolidated group-level rollup across every entity is what you are buying, that is not what this does today and you should press us on it rather than assume.

Can we export the analysis to Excel?

Not from the spend grid — there is no CSV, Excel or PDF export control on it. If a file is part of how your month-end pack gets produced, raise it during evaluation so we can be clear about what would have to change.

Does our spend data go to an AI provider?

For the written briefing, yes. Producing it sends order lines, invoices, supplier names, prices and contract values to our AI provider. The grid, the coverage figures, the tail analysis and the price comparisons involve no AI at all — they are arithmetic over your own data. Your IT and finance teams usually want that split spelled out, so it is here rather than in a follow-up email.

One category. One honest picture.

No slides. Your own orders, and a straight answer about which numbers you can take into a negotiation.

Someone from client success replies, not a sales sequence. If we are not a fit we will say so on the first call.