What Source-to-Pay means

The useful definition

Source-to-Pay connects the strategic work of understanding demand, selecting suppliers, and contracting with the operational work of requesting, ordering, receiving, invoicing, paying, and managing supplier outcomes.

The connected Source-to-Pay flow

Select each stage to see the decision, document, data, and risk that move through the lifecycle.

Understand demand

Strategic

Understand what the organisation needs, why it needs it, what is already being bought, which suppliers are used, and whether demand can be avoided, consolidated, standardised, or challenged.

Main decision What outcome is required and whether buying is necessary

Typical document Business case, requirement, spend analysis

Core data Spend, supplier, contract, demand, usage, budget

Risk if disconnected Duplicate demand, fragmented spend, and unnecessary purchases

S2P vs S2C vs P2P

These terms describe connected but different sections of the wider commercial lifecycle.

The umbrella lifecycle

Source-to-Pay connects the complete commercial journey.

It links spend and demand insight, sourcing, supplier selection, contracting, purchasing, receipt, invoicing, payment, supplier performance, and future renewal decisions.

Demand Sourcing Contracts Buying Payment Performance

The strategic front half

Source-to-Contract shapes the supplier and commercial agreement.

It usually includes market analysis, sourcing strategy, supplier engagement, competitive events, evaluation, negotiation, award, contracting, and handover into delivery.

Market insight RFx Evaluation Negotiation Contract

The operational execution layer

Procure-to-Pay turns approved demand into a controlled payment.

It typically covers the request, approval, requisition, purchase order, receipt, invoice validation, exception management, supplier payment, and accounting record.

Request Approval PO Receipt Invoice Payment

The continuous layer

Supplier management should connect every stage, not sit at the end.

Supplier onboarding, risk, data, performance, obligations, relationships, improvement, resilience, renewal, and exit all provide feedback into future demand and sourcing decisions.

Onboarding Risk Performance Obligations Renewal

Where Source-to-Pay value leaks

Most leakage appears between stages, when information, ownership, or negotiated value fails to move forward.

01

Unclear demand

The organisation approaches suppliers before clarifying the outcome, volume, usage, budget, or existing capability.

02

Fragmented spend

Similar needs are bought across different teams, suppliers, contracts, and systems without one view of demand.

03

Contract terms do not reach buying

Negotiated prices, discounts, service levels, catalogues, and controls are not translated into the operational process.

04

Off-contract buying

Employees bypass preferred suppliers because the approved route is unclear, slow, inaccessible, or poorly designed.

05

Late purchase orders

Orders are created after work begins or after an invoice arrives, weakening budget, approval, and commitment controls.

06

Invoice exceptions

Price, quantity, tax, receipt, supplier, or PO differences create manual investigation and payment delay.

07

Missed commercial benefits

Rebates, credits, tiered pricing, service remedies, and payment discounts are not measured or claimed.

08

Unmanaged renewals

Contracts renew without checking performance, demand, pricing, risk, market alternatives, or the continuing business need.

Who owns what?

Select a role to see where its responsibility sits across the Source-to-Pay lifecycle.

Lifecycle ownership

Requester

Defines the business need, contributes requirements, confirms receipt or acceptance, and helps determine whether the supplier outcome solves the original problem.

Demand

Sourcing

Contract

Request

Order

Receipt

Invoice

Performance

Three-way matching

A common control compares the purchase order, receipt, and invoice before payment is approved.

Should this invoice be paid automatically?

Purchase order 100 units at £25 each Total: £2,500

Goods receipt 95 units received 5 units outstanding

Supplier invoice 100 units at £25 each Total: £2,500

Diagnose maverick spend

Maverick spend is often treated as an employee behaviour problem. Frequently, the process itself is the cause.

Scenario

Employees keep buying software on personal cards even though the organisation has an approved purchasing process. What should be investigated first?

Source-to-Pay maturity assessment

Rate each statement from one to five to see how connected your lifecycle currently is.

Employees have one clear route to request anything.

Requests are guided to the correct workflow based on value, risk, category, and business need.

Contract terms flow into catalogues, orders, and invoices.

Operational buying reflects negotiated pricing, suppliers, service levels, and controls.

Supplier data is consistent across connected systems.

Supplier identity, risk, contracts, orders, invoices, and performance can be connected reliably.

Routine transactions process without unnecessary manual work.

Approvals, ordering, receipt, matching, and payment use rules, tolerances, automation, and exception handling.

Supplier performance and spend feed future decisions.

Sourcing, renewal, demand, and negotiation use realised performance and transaction data.

Technology performs defined work, not only routes tasks.

Guard-railed automation or autonomous execution completes suitable commercial and operational activities.

0/30

Complete the assessment. Rate all six areas to reveal your current Source-to-Pay maturity.

The Source-to-Pay technology stack

Source-to-Pay is a business lifecycle, not necessarily one software product. Different layers support different decisions and actions.

01

Intake and orchestration

Captures requests, guides employees, gathers context, and coordinates work across procurement, finance, legal, risk, and IT.

02

Spend and category intelligence

Classifies spend, reveals demand patterns, identifies suppliers, supports benchmarks, and informs category strategy.

03

Sourcing

Supports market engagement, RFx events, auctions, evaluation, supplier communication, and negotiation.

04

Contract lifecycle management

Creates, negotiates, approves, signs, stores, extracts, monitors, and renews supplier agreements and obligations.

05

E-procurement and ERP

Manages suppliers, budgets, requisitions, approvals, purchase orders, receipts, commitments, and accounting records.

06

Invoice and payment automation

Captures invoices, validates data, performs matching, manages exceptions, schedules payment, and supports financial controls.

07

Supplier management

Supports onboarding, master data, risk, performance, relationships, resilience, improvement, and supplier collaboration.

08

Autonomous execution

Performs defined sourcing, negotiation, supplier, or operational work within approved data, controls, rules, and escalation paths.

Follow one purchase through S2P

Make the key decisions as a software requirement moves from demand to payment and renewal.

Decision 1 of 4

Marketing requests a new analytics platform, but three similar tools already appear in the spend data.

What should happen before suppliers are approached?

Decision 2 of 4

A supplier wins the sourcing process with tiered pricing and a committed implementation plan.

What must happen before operational buying begins?

Decision 3 of 4

The supplier invoice is higher than the purchase order because additional licences were activated.

How should the P2P process respond?

Decision 4 of 4

Renewal is approaching, but adoption is low and the business is still paying for unused licences.

What should inform the renewal decision?

Source-to-Pay glossary

S2P Source-to-Pay: the connected lifecycle from demand and sourcing through payment and supplier management.

S2C Source-to-Contract: market analysis, sourcing, evaluation, negotiation, award, and contract creation.

P2P Procure-to-Pay: request, approval, purchase order, receipt, invoice, exception management, and payment.

Requisition An internal request to purchase goods or services before an order is placed with a supplier.

Purchase order A formal order confirming supplier, item or service, quantity, price, and commercial reference.

Goods receipt A record that goods or services have been delivered and accepted.

Three-way match Comparing the purchase order, receipt, and supplier invoice before authorising payment.

Invoice exception A mismatch or control issue that prevents an invoice from being processed automatically.

Maverick spend Spend made outside approved suppliers, contracts, systems, or purchasing processes.

Catalogue An approved list of goods or services, suppliers, descriptions, prices, and buying terms.

Spend under management Spend influenced through approved procurement strategies, suppliers, contracts, and processes.

Touchless invoice An invoice processed without manual intervention because the data and matching controls are satisfied.

Contract compliance Buying and supplier delivery that follow agreed contractual prices, terms, obligations, and routes.

Value leakage The gap between negotiated or expected value and the value actually realised in operation.

Check your understanding

Which activity most clearly belongs to Procure-to-Pay?

Choose the best answer.

Common questions

Is Source-to-Pay one software platform? +

Not necessarily. Source-to-Pay is a business lifecycle. It can be supported by one suite, an ERP, several specialist tools, an orchestration layer, autonomous execution, or a combination.

Is Source-to-Pay the same as Procure-to-Pay? +

No. Procure-to-Pay usually covers the operational transaction from request or requisition through payment. Source-to-Pay also includes the strategic sourcing and contracting activity that shapes the supplier and agreement.

Where does supplier management sit? +

Across the full lifecycle. Supplier onboarding, risk, data, performance, obligations, relationships, renewal, and exit should influence demand, sourcing, buying, and payment decisions.

Why is three-way matching useful? +

It checks that the organisation ordered the item or service, received it, and was invoiced consistently before payment is authorised. Tolerances and exceptions should reflect the organisation’s controls and operating model.

Does automation fix a broken S2P process? +

Automation can remove effort and improve consistency, but it will also scale unclear ownership, poor data, weak controls, and bad process design. The operating model needs to be understood first.

What is the biggest S2P failure? +

Treating the stages as separate departments and systems. The lifecycle loses value when demand, contracts, supplier data, orders, invoices, performance, and renewal decisions cannot inform one another.