Indirect procurement software: how to choose it
Short answer
Indirect procurement software runs the buying of what an organisation uses to operate, from laptops to consultants: requests, catalogues, approvals, orders, receipts and invoices for many occasional requesters.
Key takeaways
- Indirect procurement software is judged by the people who use it least: hundreds of employees who buy a few times a year. If ordering is hard for them, they buy outside the system.
- Indirect buying runs through several channels: catalogues, punchout to supplier websites, free-text requests, quotes, services with a statement of work, contract call-offs and cards. The software must route each request to the right one.
- Start with a channel map: for each category, the usual request, the channel, the approver and the threshold. It becomes your requirements and your demo script.
- Several kinds of tools do this work, often together: ERP purchasing, procure-to-pay suites, intake and orchestration layers, quote tools for tail spend, cards and spend analysis.
- Test AI and machine learning on your own requests and invoice lines. Count the wrong answers, and check that a person can see and correct each one.
What is indirect procurement software?
Indirect procurement software is the set of tools that runs the buying of goods and services an organisation needs to operate, such as IT, office supplies, facilities, marketing and consultants. It takes requests from employees, sends each one to the right buying channel, collects approvals, issues orders, records receipts and passes invoices to finance.
CIPS, the professional body for procurement, defines indirect procurement as the buying of goods or services that are not directly part of the final product or service. What that covers, with examples and the direct vs indirect comparison, is explained in what is indirect procurement. This page is about the software. It is one part of the wider procurement software market, so it uses the same selection method with indirect buying in the tests.
A simple situation shows the job. On Monday, a new sales manager needs a laptop, a designer needs a photographer for an event, and facilities needs the boiler repaired under the maintenance contract. Three requests, three different channels: a catalogue item, a quote from two or three suppliers, and a call-off against a contract. Indirect procurement software should take all three from the same request screen and handle each one in the right way.
Why does indirect buying ask different things of software?
Direct procurement buys materials for production, usually from a few planned suppliers, by trained buyers, against forecasts and bills of materials. Indirect procurement is the opposite on almost every point. The software choice follows from these differences:
| Feature of indirect buying | What it means in practice | What the software must do |
|---|---|---|
| Many occasional requesters | Most employees order a few times a year and never read the procurement policy | Offer one simple request screen, guide the user, and apply the policy in the background |
| Many categories | IT, facilities, travel, marketing, professional services, MRO, each with its own rules | Route by category, value and supplier, with a different approval path where needed |
| Many channels | Catalogues, punchout, free-text requests, quotes, contracts, cards | Support each channel and send each request to the right one |
| Services, not only goods | Consultants, agencies, cleaning, temporary staff, delivered over weeks or months | Hold a statement of work, milestones and the confirmation that the service was delivered |
| Long tail of suppliers | Many suppliers used once or twice a year | Onboard small suppliers quickly, or steer buying to approved ones |
| Spend outside the system | Purchases with non-approved suppliers, which CIPS calls maverick spend | Make the approved route easier than the side route, and show what still escapes |
In indirect procurement the main risk is not a bad order but no order: people who find the tool hard buy around it.
That is why the first test of indirect procurement software is ease for the occasional user, not the number of features for the buyer. A tool that a buyer finds powerful but a project manager finds confusing will lose spend to cards, emails and invoices without purchase orders.
Which buying channels must indirect procurement software support?
A buying channel is the route a request takes from need to order. Most organisations use the same handful. The software must support each one you use, and decide which one applies to each request:
- Catalogue
- Items and prices agreed with a supplier, loaded into the buying system. The requester picks an item; the price and supplier are already approved.
- Punchout
- The requester opens the supplier’s own website from the buying system, fills a basket, and the basket returns as lines of a request. In the cXML standard, the buying system starts the session and receives the basket back. See punchout catalogs.
- Free-text (non-catalogue) request
- The requester describes a need that no catalogue covers. A buyer checks it, finds a supplier or asks for quotes.
- Quote request
- For one-off or tail purchases, the tool or a buyer asks two or three suppliers for a price. CIPS describes tail spend as low-value, often one-off purchases that may not be under contract. See tail spend management.
- Services request
- A request for work, with a statement of work, a start and end date, milestones and a way to confirm delivery before the invoice is paid.
- Contract call-off
- An order against an existing contract or blanket purchase order, for example monthly cleaning or maintenance.
- Purchasing card
- A company card for low-value purchases without a purchase order, within limits and blocked categories. See p-cards.
Public examples show how organisations combine these channels. North Carolina’s state eProcurement system offers a guided buying view with three types of items: catalogue items from statewide term contracts, punchout catalogue items from suppliers’ own websites, and non-catalogue items, which users add by hand when no catalogue item exists or the vendor is not on a statewide contract.
The University of California, Riverside writes the channel rules as thresholds. Punchout orders are limited to $10,000. Non-catalogue requisitions of $10,000 or less follow one route; above $10,000 they go to a professional buyer for review and approval. The purchasing card is the preferred method for unrestricted purchases under $10,000, and some categories cannot be bought by card at any value. Rules like these are what the software must apply without the requester having to know them.
What does a channel map look like?
A channel map lists, for each indirect category, the usual request, the channel it should take, who approves and what the software must do. It is the most useful document to write before looking at any tool. The example below is fictional, for a company of about 2,000 employees; the thresholds are examples, not advice.
| Category | Typical request | Channel | Approval | What the software must do |
|---|---|---|---|---|
| Office supplies | Paper, toner, desk items | Punchout to the contracted supplier | Budget holder above $500 | Return the basket as request lines with the contract price |
| IT equipment | A laptop for a new employee | Catalogue of standard models | Manager, then IT | Show only approved models; send the order to IT for set-up |
| Software subscriptions | A design tool for five users | Free-text request to IT and procurement | Manager, IT security, procurement | Check whether the organisation already has the tool; record the renewal date |
| Professional services | A consultant for three months | Services request with statement of work | Budget holder, procurement above $25,000 | Hold milestones and confirm delivery before paying |
| Facilities maintenance | Repair of a boiler | Call-off against the maintenance contract | Facilities manager | Draw down the contract value and match the invoice to it |
| One-off small purchases | A photographer for an event | Quote request to three suppliers | Budget holder | Collect the quotes, record the choice and onboard the supplier if new |
| Travel incidentals, low-value items | A train ticket, a book | Purchasing card | None below the card limit | Block restricted categories and import card lines for coding |
Each row of the map becomes one requirement and one demonstration test: if a tool cannot run a row, you know before you sign.
Two numbers complete the map: how many requests each channel receives per month, and how much money passes through it. A channel with many small requests needs speed and automation; a channel with few large ones needs control and an audit trail. If you do not have the numbers, a spend analysis of last year’s invoices gives a first estimate by category and supplier.
Which kinds of software handle indirect procurement?
No single kind of tool covers every channel equally well. Most organisations combine two or three of the kinds below. The vendors in each kind, and how they describe their suites, are listed in the procurement software guide.
| Kind of tool | Strong at | Often weak at | Read more |
|---|---|---|---|
| ERP purchasing module | Orders, receipts and invoices in the same system as the accounts | Simple requests for occasional users; punchout and guided buying vary by product | Procure-to-pay software |
| Procure-to-pay or e-procurement suite | Catalogues, punchout, approvals, orders, receipts, invoice matching | Complex services and the long tail, depending on the product | Procure-to-pay software |
| Intake and orchestration layer | One request screen in front of several systems; routing to IT, legal, security and procurement | It relies on other systems for orders and payment | Procurement automation software |
| Quote and tail spend tool | Fast quotes from several suppliers for one-off purchases | Contracts, catalogues and invoices | Tail spend management |
| Services and contingent workforce tool | Statements of work, timesheets, temporary staff | Goods and catalogues | Vendor management systems |
| Cards and expense tools | Low-value purchases without a purchase order | Control before the purchase; supplier choice | P-cards |
| Source-to-pay suite | Sourcing, contracts, suppliers and procure-to-pay in one platform | Cost and project size for smaller organisations | Source-to-pay software |
Choose the kind of tool from your channel map: the channels with the most requests decide what the core tool must do best.
The intake layer deserves a word. Some organisations already have an ERP or a procure-to-pay suite but still receive requests by email and chat. An intake tool puts one form in front of these systems, asks a few questions, and sends the request to the right team and the right channel. It does not replace the system that issues the purchase order; it decides what happens before it.
How do you choose indirect procurement software?
The general method is the one in the software procurement process guide. For indirect procurement, eight steps make it concrete:
- Write the channel map: categories, typical requests, channels, approvers and thresholds, as in the example above.
- Count the volumes: requesters, requests per month by channel, suppliers used in the last year, invoices with and without a purchase order.
- Write the policy rules the tool must apply: thresholds, required approvals, blocked categories, when a quote is needed. Take them from your procurement policy.
- Shortlist by kind of tool, using the table above. Decide first whether you need a full suite, a layer on top of your ERP, or a combination.
- Send each vendor the same script: ten to fifteen real requests taken from your map, with your approvers and your suppliers. Ask them to load it before the demonstration.
- Check the supplier side: how a new small supplier is onboarded, how a catalogue or a punchout is set up, and what it costs the supplier.
- Check the finance side: budgets, cost centres, the link to the ERP, and how invoices are matched to orders and receipts.
- Run a pilot with one department and two or three channels. Measure the share of requests that went through the tool, the time from request to order, and the questions users asked.
Ask real occasional users to try the request screen during the demonstration: an assistant, an engineer, a marketing manager. Their first five minutes tell you more about adoption than any feature list.
Which tests show whether a tool fits indirect buying?
Scripted scenarios make vendors comparable. These seven cover the channels and the usual problems of indirect buying. Run each one live, on your data, and note what needed a buyer’s help:
- A new employee orders a laptop: only approved models appear, the manager approves on a phone, and IT receives the order.
- A requester fills a punchout basket that contains an item outside the contract: the tool flags it before approval.
- A requester types “photographer for the sales event in March”: the tool asks the right questions and sends a quote request to suppliers, or to a buyer.
- A consultant is hired for three months: the statement of work holds milestones, the budget holder confirms each milestone, and only then can the invoice be paid.
- An invoice arrives with no purchase order number: the tool shows who must deal with it and how it is matched or approved. See three-way match.
- A software subscription is due for renewal: the tool warns the owner before the notice date and shows the current users and cost.
- A cardholder tries to buy in a blocked category: the purchase is refused, and the requester is shown the right channel.
Which criteria decide the choice?
| Criterion | Why it matters for indirect buying | How to test it |
|---|---|---|
| Ease for occasional users | Adoption decides how much spend the tool sees | Let three real employees place three requests without training |
| Coverage of your channels | Each missing channel sends spend outside the tool | Run every row of your channel map |
| Policy rules | Thresholds and approvals must work without the requester knowing them | Change a threshold during the demonstration and repeat a request |
| Services handling | Services are delivered over weeks or months, with no item to count on receipt, so they are hard to control | Run the consultant scenario end to end |
| Supplier enablement | Catalogues and punchout depend on suppliers doing work | Ask what a small supplier must do and pay to be connected |
| Finance integration | Orders, receipts and invoices must reach the accounts without retyping | Follow one order into your ERP test system |
| Reporting | You need to see spend by category, channel and supplier, including what escaped | Ask for a report of requests that ended without a purchase order |
| Cost and contract | Pricing by user, by module or by spend changes the total over the years | Price your volumes for five years, with set-up and supplier fees |
Weight ease of use and channel coverage first: a tool that few employees use controls little, whatever else it can do.
What do AI and machine learning add to indirect procurement software?
Indirect buying has many small transactions and much free text, which is where AI features are most often offered. Three uses are common, and each can be tested:
- Machine learning that classifies spend: it reads invoice and order lines and assigns a category, often in a taxonomy such as UNSPSC, which has four levels (segment, family, class and commodity). Test it on a sample of your own lines and count the wrong categories.
- Generative AI, including GPT-style assistants, that reads a free-text request: it asks follow-up questions, suggests a catalogue item or routes the request to the right channel. Test it with your vaguest real requests.
- Agents that collect quotes for small purchases: they find suppliers, send the request and compare answers within set limits. Test who approves the final choice and what is recorded.
The limit is accuracy. NIST’s Generative AI Profile, NIST AI 600-1, lists confabulation among the risks of generative AI: content that is confidently stated but false. In indirect buying, that can be a wrong category in the spend report or a request sent to the wrong approver. Ask each vendor to show where a person sees and corrects the AI’s answer, and whether the correction improves the next one. How to evaluate AI features in general is covered in AI procurement software and AI in procurement.
Questions
What are examples of indirect procurement?
Laptops and software for employees, office supplies, cleaning and building maintenance, marketing agencies, consultants, travel, insurance and spare parts for machines. All help the organisation run without becoming part of what it sells. The categories are listed in what is indirect procurement.
Is indirect procurement software the same as procure-to-pay software?
Largely, but not entirely. Procure-to-pay software runs the steps from request to payment for any purchase. Indirect procurement software adds what indirect buying needs: guided requests for occasional users, many channels, services and the long tail. Many organisations use a procure-to-pay suite as the core and add tools around it.
What is procurement process management software?
The term usually means software that manages the steps and approvals of a purchase, often an intake and orchestration layer that routes requests between procurement, IT, legal and finance. For indirect buying it is one kind of tool among several, and it relies on other systems to issue orders and pay invoices.
Do small companies need indirect procurement software?
Not always. A company with a few requesters can often manage with its accounting system, cards and a simple approval rule. The need grows with the number of requesters, the number of suppliers and the share of invoices that arrive without a purchase order.
How long does it take to implement indirect procurement software?
It depends on the scope more than on the tool. A request and approval layer for one department can start in weeks; a suite with catalogues, punchout suppliers, ERP integration and invoice matching across several countries takes months. Supplier enablement is often the slowest part, so plan it from the start.
New guides on eProcurement Toolkit
One short email when a guide on this line is added or revised. Nothing else.
Coming soon: sign-up opens with the first email.