Most procurement teams can point to a strong sourcing event that “saved 8%” and still admit they can’t reliably see whether the business actually bought on that deal. That gap—between negotiated intent and what really happens in ordering, invoicing, and payment—is the problem source-to-pay (S2P) is meant to close.
Source-to-pay, defined
Source-to-pay (S2P) is the set of connected processes that starts with identifying and selecting suppliers (sourcing) and ends with paying them (pay). It links upstream commercial decisions—supplier choice, contracts, pricing, service levels—to downstream execution—requisitions, purchase orders, goods receipts, invoice matching, and payment.
S2P is not a single software module and it isn’t the same as procure-to-pay (P2P). P2P usually covers the operational buying and payment steps. S2P includes P2P, but adds the upstream work that makes buying controllable: supplier discovery, competitive events, negotiation, contracting, and supplier onboarding.
Why teams bother: the practical outcomes
When S2P is working, you feel it in very unglamorous places: fewer “urgent” exceptions, fewer emails asking which supplier to use, fewer invoices stuck because the PO is missing or the price doesn’t match. It also makes spend analysis less of a quarterly archaeology project because transactions and contracts are tied together.
The trade-off is real: tighter processes can irritate stakeholders if the buying experience is clunky or approvals are over-designed. The best S2P programs treat user experience as a compliance tool—make the right path faster than the workaround.
The S2P process, step by step
Different organizations label the steps differently, but the flow is consistent: decide what to buy and from whom, formalize the deal, then execute purchases and pay accurately.
Spend and demand insight: understand what is being bought, by whom, and why (often using spend classification and stakeholder input).
Supplier discovery and qualification: identify potential suppliers, assess risk and capability, and confirm basics like tax, banking, and compliance requirements.
Sourcing event: run an RFx or auction (where appropriate), compare offers, and document the decision logic—not just price.
Negotiation and award: agree commercial terms, SLAs, and governance; select the supplier(s).
Contract management: create, review, approve, sign, and store contracts so pricing and terms can be referenced during buying and invoicing.
Catalogs and guided buying (where relevant): turn negotiated items/services into an easy ordering path.
Requisition and approval: capture the need, route approvals based on policy, budget, and risk.
Purchase order (PO) creation and dispatch: issue the PO so supplier and buyer share the same reference for price, quantity, and terms.
Receipt and service entry: confirm goods received or services delivered so payment is tied to actual performance.
Invoice capture and matching: match invoice to PO and receipt (2-way or 3-way match), resolve exceptions, and apply tax rules.
Payment and reconciliation: pay on agreed terms, manage early payment discounts where sensible, and reconcile to the ledger.
Supplier performance and continuous improvement: track delivery, quality, responsiveness, and compliance; feed learnings into the next sourcing cycle.
S2P vs. P2P vs. O2C: stop mixing them up
Procurement teams often inherit messy terminology. Here’s the clean mental model: S2P is the full procurement journey from supplier selection to payment. P2P is the execution portion (requisition-to-payment). Order-to-cash (O2C) is the mirror process on the sales side—how your organization takes orders, invoices customers, and collects cash.
Why it matters: if you’re trying to fix invoice exceptions but contracts and catalogs aren’t maintained, you’re treating symptoms. If you’re running great sourcing events but POs aren’t used, you’ll struggle to prove savings and control risk.
What “good” looks like (and what usually goes wrong)
A common mistake is treating S2P as a documentation exercise: policies, templates, mandatory fields. That produces compliance theatre—people click through, then buy off-system because it’s faster. Another failure mode is over-automation: workflows that assume every buy is predictable, even when the business needs flexibility for one-off services or urgent maintenance.
Good S2P is boring in the best way. Stakeholders can find the right supplier quickly, approvals are proportionate to risk and value, and exceptions are handled through clear rules (tolerances, escalation paths, and ownership). Procurement can trace transactions back to contracts and can explain variances without spending days pulling spreadsheets.
How technology fits without becoming the whole story
S2P suites and integrated tools typically cover sourcing, supplier management, contract lifecycle management, procurement (requisitioning, catalogs, POs), and invoice-to-pay. Integration with ERP and finance systems matters because payment, tax, and accounting controls usually live there.
Still, tools won’t fix unclear decision rights. If category managers can’t enforce preferred suppliers, if budget owners don’t approve in time, or if master data is neglected, the system becomes a mirror of dysfunction—just more expensive. Start with the operating model (who decides, who executes, who owns data), then configure technology to match.
A simple test to see where you stand
Ask three questions and see how hard they are to answer: (1) What percentage of spend is on contract—and actually bought through that contract path? (2) How many invoices require manual intervention, and why? (3) Can you tie supplier performance issues back to specific POs, receipts, and contract terms? If those answers are fuzzy, S2P isn’t “missing”—it’s fragmented.