The Complete Guide to Controlling Indirect Spend with Source-to-Pay Software

Last reviewed: November 2026

Quick answer: Source-to-pay (S2P) software helps control indirect spend by moving control to the point of request, before money is committed. Staff buy from approved suppliers through guided buying and catalogues, requests are checked against budget and routed through approval workflows that reflect your delegations, and invoices are matched to purchase orders and receipts before payment. Because every step happens in one platform, procurement and finance can see committed and actual spend across every department, site and supplier, and act on it while there is still time to change the outcome.

In this guide

• Key definitions
• Why indirect spend slips out of control
• How source-to-pay software controls indirect spend
• Indirect spend in the public sector
• What to look for in a source-to-pay platform
• Implementation checklist
• How to measure progress
• Frequently asked questions

Key definitions

Why indirect spend slips out of control

Direct spend is usually concentrated, planned and closely watched. Indirect spend is different. It is spread across many suppliers, categories and budget holders, and much of it is bought by people whose main job isn't procurement. Four patterns account for most of the loss of control.

Decentralised buying

In councils, universities, health services and multi-site enterprises, purchasing happens across departments, campuses, depots and business units. That is often the right model, because the people closest to the work know what they need. Without a shared system, though, each area develops its own way of buying, its own supplier relationships and its own workarounds, and procurement loses a consistent view.

Tail spend

Low-value purchases rarely justify a formal process on their own, so they tend to happen on cards, by email or directly with suppliers. Over a year they add up to a large number of transactions and suppliers that nobody has reviewed, with little leverage on price and limited insight into what was bought.

Off-contract purchasing

Even when good contracts exist, staff often don't know about them or find them harder to use than ordering from a familiar supplier. The result is spend leaking away from negotiated pricing, panels and preferred suppliers, which weakens the value of the sourcing work already done.

Visibility that arrives too late

When orders are placed outside a system, finance often learns about the purchase when the invoice arrives. By then the money is committed. Reporting built on invoices and ledger codes shows what happened, but not in time to change it, and coding is often too broad to show which supplier or category the money went to.

How source-to-pay software controls indirect spend

Source-to-pay software addresses these problems by connecting every stage of buying, from finding a supplier to paying an invoice, in one platform. Control comes from five capabilities working together.

1. Spend visibility from request to payment

When requisitions, purchase orders, receipts and invoices sit in one system, spend becomes visible at the moment it is requested, not weeks later. Procurement and finance can see what is being bought, from which suppliers, by which departments, and how much is committed against each budget. That visibility supports better forecasting, because historical and committed spend can be reviewed together.

Line-level data from catalogues and purchase orders also gives a more accurate picture of categories than invoice coding alone. Over time, it shows where spend is concentrated, which suppliers could be consolidated and where a new contract would make a difference.

2. Policy compliance built into the buying process

Policies work best when they are applied as people buy, not checked afterwards. Source-to-pay platforms do this through guided buying: staff search catalogues from approved suppliers at negotiated prices, and the system applies the right rules for the category, value and supplier. For purchases that aren't in a catalogue, structured request forms collect the information needed and route the request through the right process, such as requesting quotes from several suppliers.

The aim is to make the compliant path the easiest one. If staff can find what they need in a few clicks, they have little reason to buy around the system.

3. Approval workflows that reflect your delegations

Approval workflows turn financial delegations into rules the system applies every time. Requests can be routed by value, department, cost centre, category or funding source, with more than one approver where policy requires it. Budget checks at the requisition stage mean approvers see the budget position before they say yes.

The key is timing. Approval before the purchase order is issued is real control. Approval recorded after the invoice arrives is only a record. For a deeper look at automating these stages, see our complete guide to procure-to-pay automation.

4. Supplier control

Controlling indirect spend depends on controlling which suppliers receive it. A source-to-pay platform holds one supplier record for the organisation, so the same supplier isn't set up several times under different names. Procurement decides which suppliers are available to buy from, and catalogue changes can be reviewed before staff see new products or prices.

Supplier self-service portals reduce the admin of keeping records current, because suppliers can update their own company, tax and bank details. Connecting sourcing and contracts to purchasing also means the outcome of a tender or quote flows into how people buy, instead of sitting in a separate file.

5. Invoice matching that closes the loop

The final control point is payment. Matching each invoice against its purchase order and receipt confirms that the organisation is paying the agreed price for goods and services that actually arrived. Rules-based matching clears invoices within tolerance automatically, so accounts payable can focus on exceptions. Invoices without a purchase order can be routed through an exception workflow so the purchase is authorised before it is paid.

Indirect spend in the public sector

For councils, universities, health services and government agencies, indirect spend control is also about accountability. Public sector buyers in Australia and New Zealand work within frameworks such as the Commonwealth Procurement Rules, state and territory procurement policies, local government requirements and the New Zealand Government Procurement Rules. These place a strong emphasis on value for money, probity and the ability to show how decisions were made.

Source-to-pay software supports this by keeping a digital record of each step: who requested a purchase, who approved it, which supplier was used and how the price compared with alternatives. When an audit or review comes around, that trail is already in place rather than being reconstructed from emails and spreadsheets.

Public sector organisations also tend to have many occasional buyers spread across sites. That makes ease of use and broad user access especially important, because a system that only a few people can use, or that is hard to use, quickly pushes spend back outside it.

What to look for in a source-to-pay platform

When evaluating platforms for indirect spend control, focus on how well each one changes buying behaviour, not just how many features it lists.

• Guided buying and catalogue coverage. A familiar shopping experience, with approved suppliers and negotiated prices, is the strongest lever on off-contract spend.
• Support for non-catalogue and one-off purchases. Quotes, services and tail spend need a clear path through the system too.
• Configurable approval workflows. Rules should match your delegations by value, department, category and funding source.
• Budget checks and committed spend reporting. Budget holders need to see their position before they commit spend.
• Connected sourcing, contracts and purchasing. Sourcing outcomes and contract pricing should flow into everyday buying.
• Supplier onboarding and enablement. Find out how much of the work the vendor takes on to get your suppliers transacting electronically.
• Invoice matching. Automated matching against purchase orders and receipts, with exception workflows for invoices that don't match.
• ERP integration. Proven integration with the finance system you run, which should remain the system of record.
• Licensing that supports broad access. Per-user pricing can push organisations to limit access, which sends occasional buyers back to workarounds.

If you're already comparing vendors, our comparison of source-to-pay platforms for indirect spend control in decentralised organisations looks at how leading platforms approach these criteria.

Implementation checklist

1. Set the baseline. Pull 12 months of spend data to understand your main categories, top suppliers, tail spend and where purchases happen outside a purchase order.
2. Agree the policy. Confirm which spend must go through the platform, the approval thresholds and the exceptions, and simplify the policy where you can before configuring it.
3. Name an executive sponsor. Someone senior in procurement or finance should hold business units to the agreed process.
4. Prioritise suppliers. Start with the suppliers that carry the most indirect spend and transactions, and plan how the long tail will be onboarded. Our supplier onboarding guide covers this in more detail.
5. Configure approvals and budgets. Set up workflows and budget checks that reflect how each area actually works.
6. Integrate with finance. Connect the platform to your finance system so coding, budgets and payments stay in sync.
7. Train people in context. Show each group how to buy what they actually buy, and provide support beyond go-live.
8. Measure and follow up. Track adoption by department each month and work with the areas that fall behind.

How to measure progress

A small set of measures shows whether indirect spend is coming under control. Track them monthly and by department or site so you can see where to focus.

• Spend under management: the share of indirect spend flowing through the platform and agreed contracts.
• Purchase order compliance: the share of invoices with a matching purchase order raised before the purchase.
• Catalogue and contract spend: the share of spend going to approved suppliers at negotiated prices.
• Active supplier count: whether the number of suppliers is consolidating over time.
• Approval cycle time: how long requests wait for approval, which shows whether controls are slowing buyers down.
• Invoice exceptions: the share of invoices that need manual handling.

Frequently asked questions

How does source-to-pay software help control indirect spend?

It moves control to the point of request. Staff buy from approved suppliers through guided buying, requests are checked against budget and approved before a purchase order is issued, and invoices are matched to orders and receipts before payment. Because it all happens in one platform, spend is visible across the organisation while it can still be influenced.

What is the difference between direct and indirect spend?

Direct spend goes into the products or services an organisation delivers. Indirect spend covers everything needed to run the organisation, such as IT, facilities, office supplies and professional services. Indirect spend is usually spread across more suppliers and buyers, which makes it harder to control.

How do you reduce off-contract spend?

Make contracted suppliers the easiest option. Put them in a searchable catalogue at negotiated prices, require purchase orders for agreed categories, and route requests for non-contracted suppliers through approval. Then track contract spend by department and follow up where it is low.

Is source-to-pay software only for large enterprises?

No. Mid-sized organisations and public sector bodies with decentralised buying can benefit just as much, because they often have many occasional buyers and limited procurement resources. The right platform should be quick to adopt and simple enough for people who only buy a few times a year.

Do we need to replace our ERP to use source-to-pay software?

No. A source-to-pay platform typically integrates with your existing finance system, which remains the system of record. The platform manages sourcing, purchasing and invoice workflows, then passes approved, coded transactions to the ERP.