What is source-to-pay (S2P)?

What does source-to-pay mean?

Source-to-pay means the whole procurement cycle, from deciding what to buy and from whom to paying the supplier’s invoice. It covers spend analysis, sourcing and contracting on the upstream side, and requisitions, purchase orders, receipts, invoices and payments on the downstream side, run as one chain. Supplier management runs alongside both: it starts before the first sourcing event, when suppliers register and are qualified, and continues for as long as they are used.

The term is written source to pay, source-to-pay or S2P, and it is used in two senses. As a process, it is the route a purchase travels; as a software category, it names the suites built to run that route. The upstream half is often called source-to-contract, and the downstream half procure-to-pay. What procurement means in general is defined on the home page; the steps of a single purchase are set out in the procurement process guide.

In procurement, the point of the word is the hyphen: source-to-pay says that the sourcing decision and the payment belong to the same chain. A buyer negotiates a price in a sourcing event; that price goes into a contract; requesters order at that price from a catalogue; accounts payable checks the invoice against it. When the chain breaks at any link, the negotiated price stays on paper.

What are the stages of source-to-pay?

Source-to-pay runs through eight stages. Seven follow one another from spend analysis to payment; supplier management is not a step after the contract but runs alongside all of them, starting before the first sourcing event, because only registered and qualified suppliers are invited to bid. The table gives each stage in brief, with what it produces and where it is explained in detail; a step-by-step guide to the source-to-pay process, with owners and controls, is in preparation.

Where does procure-to-pay fit within source-to-pay?

Procure-to-pay is the downstream half of source-to-pay: it starts when a need is requested and ends when the invoice is paid, using suppliers and prices already agreed. Source-to-pay adds the upstream half, which decides those suppliers and prices. Gartner’s definition of the procure-to-pay feature inside a source-to-pay suite stops at invoice processing “up to OK to pay”, with payment itself a separate feature. A detailed comparison of source-to-pay and procure-to-pay, with source-to-contract, is in preparation.

Why does source-to-pay matter?

Source-to-pay matters because most procurement value is decided upstream and lost downstream. A sourcing team can negotiate a lower price, a rebate or a service level, but the money is only saved if orders go to that supplier at that price and the invoice is checked against it. A 2023 study by World Commerce & Contracting with Deloitte, covering more than 1,200 organisations, put average value erosion at 8.6% of contract value: value agreed in contracts and never captured.

• Price compliance: contract prices reach the catalogue and the purchase order, so invoices can be checked against them.
• Traceability: an invoice can be followed back to the order, the contract and the sourcing event that set the price, which shortens audits and disputes.
• Supplier data: one supplier record serves sourcing, ordering and payment, instead of a copy per system that drifts apart.
• Spend visibility: spend analysis reads the same orders and invoices that procure-to-pay creates, so the next sourcing round starts from accurate data.

Organisations rarely get there in one move. Many run sourcing in one tool, contracts in another and ordering in the ERP; source-to-pay then means connecting them through shared supplier and contract data, even before any suite is bought.

What is a source-to-pay system?

A source-to-pay system, also called a source-to-pay solution or suite, is software that runs the whole cycle in integrated modules sharing 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 for goods and services across an enterprise, typically sold as cloud software as a service, modular, and independent of the customer’s ERP or financial system.

Gartner estimates that spending on source-to-pay software will grow at a compound annual rate of 16.3% over five years, to about $18.7 billion in 2029. The same report notes that the differences between suites are often not obvious and depend on specific requirements. Organisations choose between a full suite, separate best-of-breed tools connected by integration, and the procurement modules of their ERP; the trade-offs are set out in the procurement software guide. A guide to choosing source-to-pay software, with a selection method, is in preparation, and the procure-to-pay software guide covers the downstream tools on their own.

What does source-to-pay automation cover?

Source-to-pay automation means letting the system carry out the repetitive steps of the cycle and route only the exceptions to people. It works best where volumes are high and rules are clear: requests, catalogue orders, order transmission, invoice capture and matching. It works least well where judgement is the job, such as choosing a sourcing strategy or negotiating terms.

Electronic documents make the downstream automation possible. Peppol, for example, defines an electronic order and order response in which an accepted order has the status of a contract, and the EU’s VAT in the Digital Age package, adopted in March 2025, lets member states make electronic invoicing mandatory under certain conditions. How procure-to-pay tools handle these steps is covered in the procure-to-pay software guide; a guide to procurement automation software is in preparation.

What do AI and “smart” source-to-pay technology add?

“AI smart source-to-pay technology” is a marketing phrase rather than a category: it describes suites that add machine learning, generative AI or agents to the steps above. Machine learning classifies spend and flags unusual invoices; generative AI drafts sourcing documents and reads contracts; agents carry out multi-step tasks, such as chasing a supplier or preparing a routine sourcing event, within limits set by people. Gartner’s January 2026 report lists agentic and generative AI among the differentiators buyers look at, along with intake and process orchestration, configurability and ease of use for internal users and suppliers.

The test for any AI feature is which step it changes and how its output is checked. Generative models can state false content with confidence, a risk NIST’s Generative AI Profile calls confabulation; in source-to-pay, a wrong renewal date or a misread invoice line becomes a missed notice period or an overpayment. The AI in procurement guide sets out the use cases by step, their limits and how to evaluate them.

Who runs source-to-pay: operations and services?

Source-to-pay operations is the team that runs the cycle day to day: procurement operations or a buying desk handling requests and orders, accounts payable handling invoices and payments, a master data team keeping supplier and catalogue records clean, and system administrators maintaining the tools. In larger organisations these roles often sit in a shared service centre, with category managers and contract managers upstream deciding what the operations team buys against.

Implementation services

Outside help to configure and connect source-to-pay software, migrate data and onboard suppliers, usually for a fixed project.

Managed services

An outside team runs part of the operation on the organisation’s own systems, such as catalogue maintenance, supplier onboarding or invoice exception handling, under service levels.

Outsourcing

A provider takes over whole stages, such as tactical buying or accounts payable, with its own staff and often its own tools; the organisation keeps the policy, the budget decisions and the strategic sourcing.

Whichever model is chosen, the organisation keeps ownership of its data, its supplier relationships and the controls on payment. Write those into any services contract, with the right to take the work back.

What are source-to-pay best practices?

• Keep one supplier record for sourcing, ordering and payment, verified at onboarding and changed only through a controlled request.
• Load every negotiated price into the ordering system as a catalogue or contract line, so that the award reaches the purchase order.
• Give every request one entry point, and route it by value and category to an existing contract, a quotation or a tender.
• Link each purchase order to its contract and each invoice to its order, so that any payment can be traced back to the decision that set its price.
• Measure the chain, not the stages: the share of spend under contract, the share of invoices matched first time, and the time from request to payment.
• Choose the rollout order from where the supplier master data lives. If it stays in the ERP, SAP for example, projects often start with sourcing (RFx events, auctions) and contracts, then procure-to-pay; requisitions belong to procure-to-pay, not to sourcing. Connect the two halves through shared data before adding modules.