Source-to-Pay (S2P)
Source-to-Pay (S2P) is the complete procurement cycle, from identifying a need and selecting a supplier through to paying that supplier. It is the superset of procure-to-pay (P2P): where P2P starts at the requisition, S2P starts further upstream with spend analysis, supplier discovery and qualification, RFQ or tender, negotiation, award and contracting — and only then runs the transactional flow of requisition → purchase order → goods receipt → invoice → matching → payment.
The point of managing sourcing and buying as one cycle is that the decisions made upstream govern everything downstream. A price agreement negotiated in the sourcing stage becomes the price the purchase order is raised against; a supplier qualification becomes the check that stops an unapproved vendor being ordered from; a contract term becomes the tolerance three-way matching enforces before an invoice is paid. Split across disconnected systems, that chain breaks and savings negotiated on paper never reach the ledger.
S2P is normally delivered either as a dedicated procurement suite or as the procurement and accounts-payable modules of an ERP. The ERP-native route has the advantage that budgets, stock, projects and the general ledger are already in the same system, so a commitment raised at PO stage is visible to finance the moment it is made rather than at month end.
Sourcing and buying are usually run by different teams on different systems, and that gap is where negotiated savings leak away — the contract says one price, the invoice says another, and nobody notices. Managing the whole span as one cycle means the supplier qualification, the agreed price and the contract tolerance all follow through into the purchase order and the payment check, so what was negotiated is what actually gets paid.
& sourcing
& contract
& PO
& matching
A ship manager buying spares and stores across a 40-vessel fleet. Each vessel had been requisitioning locally, so the same cooling-water pump impeller was being bought at whichever chandler the agent in that port happened to use. A spend analysis in WHIZERP groups eighteen months of purchase history by category, vessel, port and supplier, and the pattern is immediately visible: one part number, 60 orders, nine ports, eleven different prices, and a spread of more than 40% between the highest and lowest.
The upstream half — where source-to-pay earns its name. That analysis drives a category strategy rather than another one-off order. A single RFQ goes out to a shortlist of OEM distributors and chandlers with genuine coverage across the fleet trading pattern, screened first on class approvals, certification, financial standing and their own delivery and quality history held in the system. Quotations return into WHIZERP and are compared on landed cost across the relevant ports, not just unit price, because a cheaper impeller delivered to the wrong side of a trading route is not cheaper.
The award becomes a control, not a document. The winning supplier is put on a framework price agreement — agreed prices, lead times and port coverage — and that agreement is loaded into the system rather than filed. From that point a vessel requisition is a call-off against it: the purchase order is priced automatically from the agreement, routed for approval by value and checked against the vessel opex budget before it is committed.
Closing the loop. On delivery the goods receipt is posted against the order, and the supplier invoice is three-way matched against the PO and receipt within the tolerance the contract defines. An invoice priced above the agreement does not quietly pass — it is flagged as a contract variance. That last step is the difference between a negotiated saving and a realised one, and it is why the sourcing and buying halves have to be one cycle rather than two systems.
What is the difference between source-to-pay and procure-to-pay?
Procure-to-pay covers the transactional cycle from requisition to payment. Source-to-pay adds the upstream stages in front of it — spend analysis, supplier discovery and qualification, RFQ or tender, negotiation, award and contracting.
What are the stages of source-to-pay?
Spend analysis, supplier discovery and qualification, RFQ or tender, negotiation and award, contracting, requisition, purchase order, goods receipt, invoice, three-way matching and payment.
Is source-to-pay the same as source-to-settle?
Broadly yes — they describe the same span. Source-to-settle is the finance-side name for it, emphasising that the cycle is not closed until the invoice is settled and the ledger reconciled.
Why run sourcing and purchasing in one system?
Because the upstream decisions are only worth anything if they are enforced downstream. A negotiated price agreement has to become the price the purchase order is raised at, and the tolerance the invoice is matched against — otherwise the saving exists on paper and never reaches the ledger.
Do you need a separate procurement suite, or can an ERP do source-to-pay?
Both routes work. An ERP-native source-to-pay has the advantage that budgets, stock, projects and the general ledger already sit in the same system, so a commitment is visible to finance the moment the purchase order is raised rather than at month end.