How do you choose procurement spend management software?
Short answer
Procurement spend management software controls spending before money is committed, from request and approval to order, card and invoice; choose it by the spend channels it must control.
Key takeaways
- Procurement spend management software checks each purchase before the organisation is committed to pay: request, approval, budget, supplier, order or card, then the invoice.
- Four kinds of product use the label: source-to-pay suites, intake and procure-to-pay platforms, finance platforms built around cards, and spend analysis tools that only look at past spend.
- Start from your own spend, split by channel: orders, invoices with no order, cards, subscriptions, expenses and payments with no invoice. The largest uncontrolled channel tells you which family to test first.
- Test the software on your own situations, such as a split purchase under an approval limit or an invoice with no order, not on the vendor’s demonstration script.
- The criteria that decide are the channels covered, the approval and budget rules, the link to your ERP and supplier records, the requester’s effort, and the data you keep when you leave.
What is procurement spend management software?
Procurement spend management software is a platform that controls company spending with suppliers before the money is committed. It takes the request, applies the approval and budget rules, sends the need to a contract, catalogue, order or card, and checks the invoice before payment. Most products also report on the spend they handled.
A simple case shows what it changes. A marketing manager wants a design tool at €80 a month. Without the software, she pays with her own card, claims it back as an expense, and nobody in procurement or IT knows the subscription exists. With it, she fills in a short request; the platform sees that the company already has a contract for a similar tool and offers a licence on it. If she still needs the new tool, the request goes to her manager and to IT, and a card with a monthly limit is issued for that supplier only.
The word “spend management” is used loosely. CIPS defines spend management as managing how to spend money to best effect, through processes such as contracting, outsourcing and performance monitoring; the spend management guide explains the whole discipline. Software that only analyses past spend, without controlling new purchases, is covered in the spend analysis software guide. This guide is about the platforms that act before the money goes out.
Which kinds of product are sold as procurement spend management software?
Four kinds of product use the label. They differ in where they start: a sourcing and contract process, a purchase request, a company card, or a pile of past invoices. The starting point decides which spending they control well and which they leave to other systems.
Disclosure: the author works as an Ivalua consultant. This comparison relies on public documentation and, where stated, first-hand use.
| Family | Where it starts | What it controls before payment | Examples, as vendors describe their scope |
|---|---|---|---|
| Source-to-pay suite | Sourcing, contracts and suppliers, then ordering and invoices | Purchases against contracts and catalogues, approvals, orders, invoice matching; often supplier onboarding and risk | Coupa (“AI-Native Agentic Spend Management Platform”); GEP (“agentic spend management platform” for the full source-to-pay lifecycle); SAP (source-to-pay suite under its spend management products) |
| Intake and procure-to-pay platform | The employee’s purchase request | Request forms, approval rules, budgets, purchase orders, receiving, invoices; some add cards | Precoro (“agentic procurement & AP centralization platform”); Procurify (“from request to payment”, with spending cards); Zip (“from intake to pay”) |
| Finance platform built around cards | Company cards and expenses | Card limits per person or supplier, expense rules, supplier bills; some add purchase requests | Brex (cards, expenses, bill pay); Ramp (cards, expenses, procurement, accounts payable); Spendesk (cards, expenses, supplier invoices, purchase requests) |
| Spend analysis tool | Past invoices and orders from many systems | Nothing before payment: it shows where money went | See the spend analysis vendors guide |
Pick the family from the spending you most need to control: contracts and suppliers point to a suite, requests and orders to an intake platform, cards and expenses to a finance platform.
The examples come from each vendor’s own website, as read on the dates shown. They say what vendors claim to offer, not how well it works, and inclusion is not a recommendation. The families overlap more each year: suites add intake, intake platforms add cards, and card platforms add purchase requests. Gartner lists intake management and payments among the common features of source-to-pay suites, next to procure-to-pay and spend analytics.
Which spend channels must the software control?
A spend channel is the route by which money leaves the organisation: a purchase order, an invoice that arrives with no order, a company card, a recurring subscription, an employee expense, a payment with no invoice. Each channel needs a different control before the money is committed. A platform that controls orders well may see nothing of cards.
| Channel | Control before commitment | Question to ask |
|---|---|---|
| Purchase order against a contract or catalogue | Approved request, budget check, contracted supplier and price | Can a requester find the contracted item in two clicks, and is the price taken from the contract? |
| Invoice with no purchase order | Hold the invoice until an approved order or a named approver exists | What happens on screen when an invoice arrives with no order number? |
| Purchasing or company card | Limit per card, per supplier or per merchant type; receipt and coding after each payment | Can we issue a card for one supplier, with a monthly limit, from an approved request? |
| Software and other subscriptions | Request and approval before the first payment; renewal date known in advance | Does the platform warn the owner before a renewal, and can it stop a duplicate subscription? |
| Employee expense | Policy limits and receipt check before reimbursement | Are expenses in the same rules and reports as orders and cards, or in a separate tool? |
| Payment with no invoice | Approved payment request with a reason and a named approver | Can a deposit, fee or one-off payment be requested and approved in the same platform? |
List your channels before you look at products: a platform is only as useful as the share of your spend that passes through it.
The worked example below shows how to read your own data. A fictional services company has €40.0 million of yearly spend with suppliers. Twelve months of accounts payable, card and expense data are split by the route each payment took.
| Channel | Annual spend (€ million) | Control before commitment today | What it points to |
|---|---|---|---|
| Purchase orders raised before the invoice | 24.0 | Yes: approval in the ERP | Keep; check that the new platform links to the ERP |
| Invoices with no purchase order | 7.5 | No: approved after the work is done | Intake and order control |
| Purchasing and company cards | 3.0 | Partly: limits per card, no request | Card limits from approved requests |
| Subscriptions paid by direct debit or card | 1.5 | No: found at renewal | Request before the first payment; renewal alerts |
| Employee expenses | 2.0 | Yes: expense policy and receipts | Keep the current expense tool unless it must merge |
| Payments with no invoice (fees, deposits) | 2.0 | Partly: signature on a paper form | Payment request workflow |
| Total | 40.0 |
Here €9.0 million, 22.5% of spend, has no control before commitment, and most of it is invoices with no order: test intake and order control first, not cards.
The total checks: 24.0 + 7.5 + 3.0 + 1.5 + 2.0 + 2.0 = €40.0 million, and 7.5 + 1.5 = €9.0 million without any control before commitment. A company whose largest gap is card spending would read the same table the other way and start with a card platform.
How do you choose procurement spend management software?
Choosing procurement spend management software means measuring your channels, writing the rules the platform must apply, and asking a short list of vendors to run your own situations. The steps below fit a company or a public body; a public buyer also follows its own procurement rules to buy the software.
- Split twelve months of spend by channel, as in the worked example, and mark which channels have a control before commitment today.
- Write the rules the platform must apply: approval limits by amount, entity and category, budget checks, which suppliers may be used, and when an order is required. The procurement policy is the usual source.
- Choose the family to test first from the largest uncontrolled channel, and note the systems it must connect to: ERP, supplier records, card issuer, expense tool.
- Build a long list in that family, and shorten it on connectors to your ERP, hosting and data protection, and references with similar systems.
- Send each finalist six to ten of your own situations, with the expected result, and ask them to run them live with your rules loaded.
- Ask two or three requesters, not only procurement, to raise real requests during the trial and time them.
- Compare the total cost over three to five years: subscription, connectors, card or payment fees, implementation and the internal time to keep rules and catalogues current.
Step six often decides the result. Spend control works only if the compliant route is also the easy one. If raising a request takes longer than paying by personal card and claiming it back, people will keep doing that, and the platform will report clean figures on a shrinking share of spend.
Which scenarios should a demonstration cover?
A demonstration is useful only if it runs your situations with your rules. The scenarios below cover the points where products differ most; change the amounts, entities and suppliers to match your own organisation.
| Scenario | Expected result | What it checks |
|---|---|---|
| A requester asks for laptops that are in the IT catalogue under a contract | The request is sent to the catalogue item at the contract price, with no new supplier | Guided buying and use of existing contracts |
| Two requests of €4,900 for the same service, a day apart, under a €5,000 approval limit | The platform flags the pair and sends it to the higher approver | Detection of split purchases |
| A request would take the department over its remaining budget | The approver sees the remaining budget and the request is held or escalated | Budget check before commitment |
| The request needs a supplier the company has never used | Supplier onboarding starts, and no order or card payment is possible until it is complete | Link between requests and supplier checks |
| An invoice arrives with no order number | The invoice is held and sent to a named owner to approve or reject | Control of invoices with no purchase order |
| A software subscription renews in 60 days | The owner is warned and asked to renew, change or cancel | Control of recurring spend |
| The requester tries to approve his own request, or a buyer changes a supplier’s bank details and approves the payment | The platform refuses, or sends the step to another person | Segregation of duties |
| Finance asks how much was spent last quarter outside any approved request | A report by channel and department, traced to the documents | Reporting on what the platform does not control |
The split purchase, the invoice with no order and the self-approval tests show whether the rules are enforced or only displayed.
The self-approval test reflects a basic control. The US Government Accountability Office’s Standards for Internal Control treat segregation of duties as a control activity: no one person should control all key steps of a transaction. A platform should make that rule hard to break, not only report it after the fact.
Which criteria decide the selection?
The criteria that decide are those that change how much spend passes through the platform and whether its rules hold. The table gives the question and the evidence to ask for each one.
| Criterion | Question | Evidence to request | Warning sign |
|---|---|---|---|
| Channels covered | Which of our channels does the platform control before commitment, and which does it only report? | Your channel table, with each channel run in the trial | Cards or invoices with no order covered only by a partner product |
| Approval and budget rules | Can we load our approval limits by amount, entity and category, and change them ourselves? | Your policy loaded and edited by your team during the trial | Every rule change made by the vendor as a project |
| ERP and supplier records | Which system holds the supplier record, the budget and the accounting codes, and how do they stay in step? | A data flow for orders, invoices, suppliers and budgets with your ERP version | Supplier records kept in two places with no owner |
| Requester effort | How long does a requester take to raise a normal request? | Timed requests by your own staff | A form that asks the requester for accounting codes |
| Cards and payments | Who issues the cards and who makes the payments: the vendor, a partner bank or your bank? | The contract parties and the flow of money | Funds held by a party not named in the contract |
| Reporting | Can we measure the share of spend that went through an approved request? | That measure on the trial data | Reports only on spend inside the platform |
| Data ownership and exit | Do we keep requests, approvals, orders and rules if we leave? | Export format and contract clause | History that stays with the vendor |
| Pricing model | Is the price by user, by spend, by transaction, by module, or a mix, and how is the vendor paid on card use? | A priced proposal for your volumes over the full term | Low entry price with fees for each entity, connector or module |
Weight channels covered, rule enforcement and requester effort highest: together they decide how much of your spend the platform will actually control.
How is it different from spend analysis and procure-to-pay software?
Spend analysis software looks back: it collects past invoices from many systems and classifies them, but it does not stop a purchase. Procure-to-pay software is one family of spend management software: it runs requests, orders, receipts and invoices. Procurement spend management software is the wider label, and it may also cover cards, subscriptions, expenses and payments with no invoice.
Use the right guide for the need. To choose an analysis tool, read spend analysis software. If the need is clearly orders and invoices, the procure-to-pay software guide goes deeper on that family, and the source-to-pay software guide on full suites. For the many small purchases outside contracts, the tail spend management guide describes the buying channels; Gartner keeps a separate market for tail spend solutions, built for spend on noncritical goods and services from suppliers that procurement does not actively manage.
What changes for a public buyer?
A public buyer needs the same controls, plus a few rules that the platform must support. In the US federal government, FAR 13.201(b) makes the government purchase card the preferred method to buy and pay for micro-purchases, so the card channel and its limits are central, not an exception. In the European Union, Article 5(3) of Directive 2014/24/EU forbids splitting a procurement to keep it below the thresholds unless objective reasons justify it, so the platform must help show that repeated small purchases of the same kind are added up.
Public bodies also need a full record of who requested, approved and paid each purchase, kept for audit. Ask how long the platform keeps that record, in which country, and how an auditor can read it without a licence.
Questions
Is procurement spend management software the same as expense management software?
No. Expense management software handles what employees paid themselves and claim back, such as travel and meals, after the money is spent. Procurement spend management software controls purchases from suppliers before they are committed. Some finance platforms combine both, which helps when cards and expenses are a large share of spend.
Can our ERP do procurement spend management?
Often in part. Most ERPs have requisitions, purchase orders, approval workflows and budget checks. They are usually weaker on the requester’s experience, on card and subscription control, and on guided buying. Test the ERP module first on the same scenarios, and buy a separate platform only for the channels it cannot control.
Does a small company need procurement spend management software?
Not always. A small company with one entity and few suppliers can control spend with an approval rule, a few company cards with limits and a check of invoices against orders in its accounting tool. A platform helps when the number of requesters, entities or subscriptions makes those checks hard to keep up by hand.
What does procurement spend management software cost?
Prices are rarely published and depend on the number of users, entities and modules, the spend handled, and sometimes card or payment fees. Ask each finalist for a priced proposal on your own volumes over the full term, including connectors to your ERP and the internal time to keep rules and catalogues current.
New guides on the strategic sourcing line
One short email when a guide on this line is added or revised. Nothing else.
Coming soon: sign-up opens with the first email.