Source-to-pay vs procure-to-pay: what is the difference, and where does source-to-contract fit?
Short answer
Procure-to-pay runs from purchase request to supplier payment; source-to-pay adds source-to-contract before it, so the suppliers and prices chosen upstream are the ones ordered and paid.
Key takeaways
- Procure-to-pay (P2P) is the operational cycle from requisition to payment. Source-to-contract (S2C) is the upstream cycle from spend analysis to a signed contract. Source-to-pay (S2P) is both, run as one chain.
- S2C runs once per category every few years; P2P runs for every single order. Different people own them: category managers upstream, buyers and accounts payable downstream.
- The contract is the handover. Supplier record, prices, payment terms and the contract reference must reach the ordering system, or the negotiated price stays on paper.
- Most problems show up downstream but start upstream, or the other way round. Invoices above the contract price are often a handover failure, not an accounts payable failure.
- In software, Gartner counts procure-to-pay as one feature of a source-to-pay suite, ending at invoice approval, and sourcing as the one mandatory feature.
What is the difference between source-to-pay and procure-to-pay?
Procure-to-pay covers the buying and paying: requisition, approval, purchase order, receipt, invoice, matching and payment. Source-to-pay covers the whole cycle: it adds the upstream work that chooses suppliers and fixes prices, called source-to-contract. Procure-to-pay is therefore one part of source-to-pay, not an alternative to it.
Source-to-contract, written S2C, runs from understanding what the organisation spends to signing the contract: spend analysis, strategic sourcing through an RFQ, an RFP or a tender, negotiation, award and contract management. Procure-to-pay, written P2P, then uses that contract every time someone needs to buy. The full definitions are on the source-to-pay and procure-to-pay guides; this page compares the three terms.
A simple test tells them apart. Ask whether the question is about one order or about how a whole category is bought. “Can I order this monitor, and who approves it?” is a procure-to-pay question. “Which two suppliers should provide all our monitors for the next three years, and at what price?” is a source-to-contract question. “Does the price on this invoice match the price we negotiated?” is a source-to-pay question, because it needs both halves to answer.
How do source-to-contract, procure-to-pay and source-to-pay compare?
The three terms differ in scope, rhythm, documents and owners. Source-to-contract is project work that runs category by category; procure-to-pay is a flow that runs for every order; source-to-pay is the name for both when they share supplier and contract data. The table compares them point by point.
| — | Source-to-contract (S2C) | Procure-to-pay (P2P) | Source-to-pay (S2P) |
|---|---|---|---|
| Question it answers | From which suppliers, and on what terms, do we buy this category? | How does this order get approved, received and paid? | Do the terms agreed upstream reach every order and invoice? |
| Starts with | Spend data and a business need for a category | A requester’s need | Spend data and a business need |
| Ends with | A signed contract or framework agreement | A paid and reconciled invoice | A paid invoice that traces back to its contract |
| Main stages | Spend analysis, sourcing strategy, RFI, RFQ or RFP, evaluation, negotiation, award, contract | Requisition, approval, purchase order, receipt, invoice, match, payment | All of them, with supplier management alongside |
| Main documents | Category strategy, tender documents, bids, evaluation report, contract | Purchase requisition, purchase order, goods receipt, invoice, payment run | All of them, linked by supplier and contract references |
| How often it runs | Once per category, every one to five years, plus renewals | Every order, every day | Continuously |
| Usual owners | Category managers, buyers, legal, budget holders | Requesters, buyers, receivers, accounts payable | Procurement and finance together |
| Typical measures | Savings negotiated, spend under contract, sourcing cycle time | Share of spend on purchase orders, first-time match rate, time from request to payment | Contract price compliance, savings actually captured |
| Software category | Sourcing and contract tools (strategic sourcing suites) | Procure-to-pay systems, ERP purchasing, accounts payable tools | Source-to-pay suites, or connected tools |
Source-to-contract decides the terms once; procure-to-pay applies them to every order; source-to-pay is the promise that both use the same suppliers, prices and references.
Process models draw the same line in different words. The CIPS procurement and supply cycle, for example, puts specification, market analysis, strategy, tender, evaluation and contract award before delivery, receipt and contract performance. The names change between organisations; the split between deciding the terms and using them does not.
Where does source-to-contract hand over to procure-to-pay?
The handover is the signed contract. Everything that source-to-contract decided must be loaded into the system that raises purchase orders and pays invoices. If it is not, requesters keep ordering from old suppliers, and accounts payable checks invoices against the purchase order instead of the contract. The table lists what passes and what goes wrong when it does not.
| Decided in source-to-contract | Used in procure-to-pay | What goes wrong if it does not pass |
|---|---|---|
| The awarded supplier, qualified and registered | Supplier record in the ordering and payment system, with verified bank details | Orders go to the old supplier, or a new record is created in a hurry without checks |
| Prices, discounts and price-review rules | Catalogue items or contract lines on the purchase order | Requesters type free-text orders and the supplier invoices list prices |
| Payment terms | Payment term on the supplier record and the order | Invoices are paid on the supplier’s standard terms, earlier or later than agreed |
| Contract reference, ceiling and end date | Reference on each purchase order, spend tracked against the ceiling | Spend goes over the framework maximum or continues after the contract has ended |
| Delivery, service levels and tolerances | Receipt rules and matching tolerances | Short deliveries are paid in full; late deliveries are never recorded |
A contract that is not loaded into procure-to-pay protects nobody: the price, the terms and the ceiling must live where orders and invoices are checked.
The opposite flow matters too. Procure-to-pay produces the orders, receipts and invoices that the next sourcing round reads. If orders are free text and invoices have no purchase order, spend analysis cannot tell what was bought, and the next category strategy starts from a guess. The three-way match and the purchase order are where the contract price is enforced downstream.
What does one category look like across the three?
Take laptops in a company of about 1,500 employees. The figures are invented for the example. The first four steps are source-to-contract, the last five are procure-to-pay; together they are source-to-pay.
- Spend analysis (S2C). Last year’s invoices show about 600 laptops bought from five resellers, with prices for the same model differing by up to 20%.
- Sourcing strategy (S2C). The category manager decides to standardise on three models and run one competitive tender for a two-year framework with two suppliers.
- Tender and award (S2C). An RFP goes to qualified resellers. Bids are scored on price, delivery time and warranty service, and two suppliers are awarded.
- Contract (S2C). The framework is signed with fixed unit prices, a price review after 12 months, 30-day payment terms, a five-day delivery commitment and a maximum value.
- Requisition (P2P). A team leader picks a laptop from the catalogue that holds the framework prices. The request is routed to the budget holder for approval.
- Purchase order (P2P). The approved request becomes a purchase order to the framework supplier, with the contract reference on it.
- Receipt (P2P). IT records the delivery and the serial number when the laptop arrives.
- Invoice and match (P2P). The invoice is matched against the order and the receipt. It carries the contract price, so it passes without a query.
- Payment (P2P). The invoice is paid on day 30, and the spend is recorded against the framework ceiling.
Remove one link and the saving disappears. If the framework prices never reach the catalogue, step 5 becomes a free-text request, the order goes to whichever reseller the team leader knows, and the invoice is paid at that reseller’s price. Nothing in procure-to-pay is broken, and the tender was a success, yet the company pays the old prices. This is the gap that the word source-to-pay names.
Which part should an organisation work on first?
Start where the problem shows up, then check whether its cause sits in the other half. Many symptoms appear in accounts payable but start in sourcing or contracting, and some sourcing failures are really ordering failures. The table links common symptoms to where they usually start.
| Symptom | Where it usually starts | Where to look first |
|---|---|---|
| Each department buys the same item from different suppliers at different prices | Source-to-contract: no category strategy or no contract | Category management |
| Invoices arrive with no purchase order number | Procure-to-pay: orders placed by email or phone | Purchase requisition and purchase order |
| Invoices show prices above the contract | The handover: contract prices not loaded as catalogue or contract lines | Contract data in the ordering system |
| Contracts expire and services continue without one | Source-to-contract: no contract register or renewal alerts | Contract management |
| Many small suppliers used once | Both: no easy route to existing contracts for low-value needs | Tail spend management |
| Nobody trusts the spend figures | Procure-to-pay data: free-text orders and uncoded invoices | Spend analysis |
Fix the half where the cause sits, not the half where the symptom appears; the handover between them is the most common blind spot.
Many organisations start with procure-to-pay because its problems are visible every day and its savings come from fewer errors and less rework. Others start with sourcing and contracts because the money is decided there. Neither order is wrong if the two halves share one supplier record and one set of contract data from the start.
How do software categories map to S2C, P2P and S2P?
Software follows the same split. Strategic sourcing suites cover the upstream half: in 2015, as reported by Supply Chain Digest, Gartner defined them as integrated solutions that support “upstream” procurement activities, built from spend analysis, e-sourcing, contract management and supply base management. Procure-to-pay systems cover the downstream half. Source-to-pay suites aim to cover both on one data model.
In its Magic Quadrant for Source-to-Pay Suites (January 2026), Gartner defines the market as an integrated set of solutions to source, contract, request, procure, receive and pay. Sourcing is the only mandatory feature. Procure-to-pay is listed as a common feature that covers purchase requests, purchase orders, catalogues, goods receipts and invoice processing “up to ‘OK to pay’”; payments are a separate feature. A suite may therefore be strong upstream and light downstream, or the reverse.
Many organisations keep purchase orders and payments in their ERP and add sourcing and contract tools on top, connected by supplier and contract data. How to choose a suite is explained in the source-to-pay software guide; the downstream tools on their own are covered in the procure-to-pay software guide, and the upstream tools in the e-sourcing and contract management software guides.
What do S2P, P2P, S2C and similar terms mean?
- Source-to-pay (S2P)
- The whole procurement cycle, from spend analysis and sourcing to paying the supplier, run as one chain. Also written source to pay.
- Procure-to-pay (P2P)
- The downstream cycle from purchase requisition to payment. Purchase-to-pay is another name for the same cycle.
- Source-to-contract (S2C)
- The upstream cycle from spend analysis to the signed contract: sourcing strategy, RFI, RFQ or RFP, evaluation, negotiation, award and contract.
- Order-to-cash
- The supplier’s side of procure-to-pay: sales order, delivery, invoice and cash collection. A guide comparing it with procure-to-pay is in preparation.
The differences between the RFI, the RFQ and the RFP used in source-to-contract are set out in the RFI vs RFP vs RFQ guide.
Questions
Is procure-to-pay part of source-to-pay?
Yes. Procure-to-pay is the downstream half of source-to-pay, from requisition to payment. Source-to-pay adds source-to-contract before it, which chooses the suppliers and agrees the prices that procure-to-pay then uses for each order.
Which comes first, source-to-contract or procure-to-pay?
For a given category, source-to-contract comes first: the contract must exist before orders can use it. In practice both run at the same time, because procure-to-pay keeps ordering against current contracts while category managers re-source the ones that expire.
Does an organisation need a source-to-pay suite to run source-to-pay?
No. Source-to-pay is a way of running procurement, not a product. An organisation can run it with separate sourcing, contract and ordering tools, or with its ERP, as long as supplier records and contract prices are shared between them and every order and invoice can be traced back to its contract.
Where does supplier management fit?
Supplier management runs alongside both halves. Suppliers are registered and qualified before they are invited to bid, their performance and risk are followed during the contract, and their records are used for orders and payments. It belongs to source-to-pay as a whole, not only to one half.
Is accounts payable part of source-to-pay?
Yes, through procure-to-pay. Accounts payable owns the invoice, matching and payment steps at the end of procure-to-pay, and therefore at the end of source-to-pay. It is not part of source-to-contract, but it depends on it for the contract prices and payment terms it checks invoices against.
New guides on the procure‑to‑pay 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.