What is Source to Pay (S2P)?

Source to pay (S2P) describes every step involved in a business purchase, starting with the decision to source a supplier and ending when finance pays the invoice. The term matters because most companies split these steps across different teams, tools, and inboxes, which is exactly where purchases stall, teams miss renewals, and spend goes untracked.

If you work in finance, procurement, legal, or IT, you already live inside the source-to-pay process, even if nobody at your company calls it that. The Slack message asking "any update on the DocuSign renewal?" is an S2P problem. So is the unknown invoice that nobody remembers approving.

What are the stages of source to pay?

S2P breaks into two halves: the upstream work of choosing and setting up a supplier, and the downstream work of buying from them and paying them. With modern orchestration tools, these stages now overlap more than this list would suggest, but these are the basic elements of a source to pay process.  

Upstream (source to contract):

1. Intake. Someone in the business decides they need a product or service, whether that is a new HR platform or a contract with a design agency, and they make this request.
2. Sourcing. The team finds potential suppliers, runs comparisons, and often issues an RFP (request for proposal, a formal document asking suppliers to bid).
3. Negotiation and contracting. Procurement and legal agree pricing, terms, and service levels, then sign the contract.
4. Supplier onboarding. The company collects the supplier's tax details, banking information, security certifications, and compliance documents, then sets them up in its systems.

Downstream (procure to pay):

1. Requisition and approval. An employee raises a purchase request, and the right people (typically a budget holder, finance, and sometimes IT security or legal) approve it.
2. Purchase order. The company issues a PO, a formal document authorising the purchase at an agreed price.
3. Receiving. Someone confirms the goods arrived or the supplier delivered the service.
4. Invoicing and payment. The supplier sends an invoice, finance matches it against the PO and the receipt, and accounts payable pays it.

Each stage looks simple on its own. The difficulty is the handoffs. The sourcing decision lives in a spreadsheet, the contract sits in legal's shared drive, the approval happens over email, and the invoice lands in an accounts payable tool that has never heard of any of it. When the pieces do not connect, finance discovers spend after the money has already been committed.

How is source to pay different from procure to pay?

Procure to pay (P2P) covers only the downstream half: raising a purchase request, approving it, issuing the PO, and paying the invoice. Source to pay includes all of that plus the upstream work of sourcing suppliers, negotiating contracts, and onboarding vendors.

The distinction matters when you are evaluating software or designing a process. A P2P tool assumes the supplier already exists in your system and the deal is already done. It automates the transaction but has no view of how the company chose the supplier, which terms it negotiated, or whether anyone checked the vendor's security posture before signing.

An S2P approach starts earlier, at the moment someone says "we need to buy something." That timing is the whole point. By the time a purchase reaches the P2P stage, someone has already made the important decisions: which supplier, at what price, on what terms. If procurement and finance only see purchases at the invoice stage, they can process spend but they cannot influence it.

This is why the industry has shifted toward S2P as the standard framing. Controlling spend requires involvement before the company signs the contract, not after the invoice arrives.

Why does source to pay matter for finance and procurement teams?

A connected S2P process gives you three things a fragmented one cannot.

Visibility before commitment. When every purchase starts with a structured intake request, finance sees spend before anyone signs the contract rather than discovering it in the monthly card statement. That is the difference between managing spend and reporting on it.

One record per supplier. With sourcing, contracting, onboarding, and payment connected, you can answer questions that are otherwise painful: What do we actually pay this vendor across all contracts? When does the renewal notice period expire? Did security ever review them? In a fragmented process, answering those questions means archaeology across five systems and someone's leaver inbox.

Compliance built into the flow. The process applies vendor risk checks, data privacy reviews, and approval policies automatically at the right stage instead of depending on someone remembering to loop in legal. The review happens because the process requires it, not because a diligent employee thought to ask.

This is the problem intake and orchestration platforms like Omnea exist to solve: giving employees one place to request any purchase, then routing that request through the right approvals, reviews, and renewals so the full source-to-pay process runs in one connected flow instead of across email threads and disconnected tools.

Do you need a single platform for the whole S2P process?

The stages needs to be connected.They don’t necessarily need to be connected by one monolithic suite doing every stage.

Legacy S2P suites promised a single system for the entire process, and many enterprises bought them on this premise. In practice, adoption is the weakest point, and impacts every stage that follows. If raising a request takes 40 fields and three logins, employees route around the system, and a process nobody follows provides no control at all. 

The more workable model for most mid-market and enterprise companies is an orchestration layer that sits across best-in-class tools: an intake and workflow platform connected to your contract repository, ERP (enterprise resource planning system, where finance records transactions), and accounts payable tooling. The employee experience stays simple, and the data flows between systems automatically.

A useful starting question for any team: can you trace your last significant purchase from the original request through to the paid invoice without opening more than one system? If the answer is no, you have found the gap in your source-to-pay process, and closing it is where the real control over spend begins.