Source-to-Pay Process: Stages and Controls
8 min read
The source-to-pay process explained stage by stage, from need identification and sourcing to PO, invoice matching and payment, with who owns each stage and the control that keeps it honest.
The source-to-pay process in one paragraph
The source-to-pay (S2P) process is the end-to-end procurement cycle that takes a business need through supplier sourcing, award, purchasing, receipt, invoice verification and payment.
It is one connected flow rather than separate departments passing paper to one another. A need is identified, suppliers are found and qualified, prices are competed, a supplier is awarded, goods or services are ordered and received, the invoice is checked against what was ordered and received, and the supplier is paid. For a short definition, read what is source-to-pay or the glossary entry. This guide goes into the stages, the owners and the controls.
The source-to-pay process map
Organizations draw the process differently, but the logic is consistent. Seven stages cover almost every variant.
Step 1: Identify the need and plan spend
A department determines what it must buy, how much and by when, and the request is approved against its internal rules.
Step 2: Find and onboard suppliers
Suppliers are discovered, qualified and approved, and their documents and details are recorded.
Step 3: Run a sourcing event
Quotes are collected through an RFQ, tender or reverse auction so suppliers compete on comparable terms.
Step 4: Award and contract
The winning supplier or suppliers are selected, the reason is recorded, and a contract or rate agreement is put in place where needed.
Step 5: Requisition, approve and order
Requisitions are approved, combined where sensible, and converted into purchase orders that the supplier acknowledges.
Step 6: Receive and match the invoice
Goods or services are receipted, and the invoice is checked against the PO and the receipt before it is approved.
Step 7: Pay and reconcile
Approved invoices are scheduled for payment, paid, and tracked to completion.
Analytics and supplier performance review sit across all seven stages rather than at the end. They are how the process improves.
Stage 1: need identification and spend planning
Everything starts with a demand. A plant needs spare parts, a site needs housekeeping services, a department needs packaging for the next quarter. The first control is that the need is described in terms a supplier could quote against: what, how many, to what standard, by when and for which location or cost center.
This is also where planning pays off. If five sites each raise small requests for the same category, combining them creates a larger, more attractive requirement and avoids five separate sourcing events. The owner of this stage is the requesting department or site, working with procurement. The output is an approved purchase requisition or a documented sourcing request. The control is approval routed by value, type or department, so spending begins only with the right authority.
Stage 2: supplier discovery and onboarding
A sourcing event is only as good as the suppliers in it. Discovery means finding suppliers who could meet the requirement. Onboarding means collecting their company details, legal and bank information, tax and compliance documents and any certifications, and approving them before they can transact.
Many organizations run onboarding as a separate project, then wonder why sourcing and payment keep hitting missing documents. The more reliable approach keeps one supplier record that sourcing, purchasing and payment all use. The owner is procurement or a vendor management function, with finance reviewing bank and tax details. The output is an approved supplier with documents on file. The control is that only approved suppliers can be invited to sourcing events or issued purchase orders. Vendor management is the capability that supports this stage, and the vendor onboarding checklist lists what to collect.
Stage 3: sourcing events through RFQ, tender or auction
Sourcing is the competitive heart of the process. Which format you use depends on the requirement:
- An RFQ fits a defined requirement where price and terms decide. See the RFQ process step by step.
- A two-envelope RFQ or tender fits requirements where technical qualification must come before price.
- A reverse auction fits a fixed specification and a qualified supplier pool where live competition on price is acceptable.
The owner is the buyer or sourcing lead. The input is the approved need and the supplier shortlist. The output is a set of comparable quotes or bids. The controls are sealed submissions, identical information for every supplier, and a recorded evaluation. The common failure is a sourcing event run in email and spreadsheets, where the proof of fairness is a mailbox.
Stage 4: award and contract
Award turns comparison into a decision. The buyer may give the whole requirement to one supplier, or split it across several, and should record why. The reason for an award is the single most useful piece of audit evidence in the process, because it explains choices that look odd out of context.
Where the relationship will repeat, a contract or rate agreement records price, duration, payment terms, service levels and renewal. A contract sets the terms once, so every later purchase order inherits them rather than renegotiating each time. Contracts typically sit with procurement, with legal and finance reviewing and approving. The control is approval before commitment, and a clear version history if terms change.
Stage 5: requisition, approval and purchase order
Here the sourcing decision becomes an order. Approved requisitions may be consolidated so that purchases of the same kind go out together, then converted into purchase orders. The PO states what is ordered, from whom, at what price and on what terms, and the supplier accepts it, rejects it or asks for a change.
Approval workflows do the heavy lifting in this stage. A well-built workflow routes each document by conditions such as value or type, requires the right number of approvers at each step, and leaves a history of who approved what and when. Changes after issue are handled as amendments with a revision history, not by overwriting. The owner is procurement, with approvers across departments. The control is that no PO is issued without the required approvals, and every change leaves a trace. See the procure-to-pay page for how this half of the cycle works in Krayuv.
Stage 6: receipt, invoice and three-way match
When goods arrive or services are performed, the receiving site records a goods receipt note (GRN) against the PO, noting what actually came in. When the supplier's invoice arrives, finance checks it against two documents: what was ordered and what was received. That comparison of PO, receipt and invoice is three-way matching.
It exists to answer three questions: did we order this, did we receive this, and is the invoice for this? Differences become exceptions that someone resolves with a recorded note rather than ignoring. Services work the same way using a service entry in place of a goods receipt. The owners are the receiving site and accounts payable. The control is that an invoice is not approved for payment until the match is reviewed and exceptions are resolved. Duplicate and tax checks on the invoice belong here too.
Stage 7: payment and reconciliation
Payment completes the cycle. Approved invoices are scheduled for payment, in full or in part, by a chosen method and date. Payments typically follow their own approval step before release, and the status moves from scheduled, to approved, to processing, to completed, with cancellation recorded when a payment is stopped. Finance also needs visibility of upcoming outflows so cash can be planned.
The owner is finance or treasury. The control is separation of duties: the person who approves an invoice should not be the only person who authorizes its payment. Reconciliation then closes the loop by confirming that what was paid matches what was approved.
Stage, owner, input, output and control at a glance
| Stage | Typical owner | Input | Output | Key control |
|---|---|---|---|---|
| 1. Need and planning | Requesting department | Business demand | Approved requisition | Approval by value or type |
| 2. Supplier onboarding | Procurement and finance | Supplier details and documents | Approved supplier record | Only approved suppliers can transact |
| 3. Sourcing event | Buyer | Approved need, shortlist | Comparable quotes or bids | Sealed, identical information |
| 4. Award and contract | Buyer, with legal and finance | Evaluated quotes | Award decision, contract | Recorded reason, approval |
| 5. Requisition to PO | Procurement, approvers | Awarded terms | Acknowledged purchase order | Approval workflow, amendment history |
| 6. Receipt and match | Receiving site, accounts payable | PO, goods receipt, invoice | Matched, approved invoice | Match review, exception resolution |
| 7. Payment | Finance | Approved invoice | Completed payment | Payment approval, separation of duties |
Where the process breaks and the control that fixes it
- Buying outside the process. Fix with approved requisitions and visible workflows so the compliant route is also the easy one.
- Quotes that cannot be compared. Fix with a standard RFQ format and sealed, like-for-like comparison.
- Unvetted suppliers. Fix with an approval gate on the supplier record before any invitation or PO.
- Approvals that stall. Fix with an inbox for approvers, delegation and visibility of where a document is waiting.
- Paying for goods not received. Fix with receipt-based matching before invoice approval.
- No audit trail. Fix by keeping approval and change history in the same system as the transaction.
- Disconnected systems. Re-keying between sourcing, purchasing and finance multiplies errors; a single connected flow removes the handoffs.
Source-to-pay versus procure-to-pay
The two terms overlap, and the difference is where the process begins. Procure-to-pay covers the downstream half: requisition, PO, receipt, invoice and payment, starting once a supplier is already known. Source-to-pay adds the upstream half: spend planning, supplier discovery and onboarding, sourcing events and award. The source-to-pay vs procure-to-pay guide compares them in more depth.
If most of your spend goes to suppliers you already know and the issue is control after the order, procure-to-pay may be enough. If you also want better pricing and fairer supplier selection, you need the sourcing stages connected to the rest, which is what Krayuv source-to-pay is built for. To compare tools and modules, read source-to-pay applications.
Measuring the process
Measure the flow, not only the total. Cycle time between stages shows where work waits, for example from requisition to PO, from PO to receipt and from invoice to payment. Approval compliance shows whether purchases follow the route. Match exceptions show how often invoices disagree with orders and receipts. Contract utilization shows whether negotiated terms are used. Savings and auction results show the value of sourcing.
Procurement analytics brings these views into dashboards for spend, vendors, cycle time, savings and compliance. The procurement KPIs resource explains which indicators matter and how to read them. Start with a small set, agree on definitions and review them regularly.
Frequently asked questions
What are the steps in the source-to-pay process?
Identify the need and plan spend, find and onboard suppliers, run a sourcing event, award and contract, requisition and order, receive goods and match the invoice, then pay and reconcile.
What is the difference between sourcing and procurement?
Sourcing is the part of procurement that finds, qualifies and selects suppliers, usually through RFQs, tenders or auctions. Procurement is the broader function that also covers purchasing, receiving, invoice handling and payment.
Who owns each stage of source-to-pay?
Requesting departments own the need, procurement owns sourcing, supplier management and ordering, receiving sites own receipts, and finance owns invoice verification and payment. Approvers from several functions take part along the way.
What is the difference between S2P and P2P?
Procure-to-pay starts after the supplier is chosen, covering requisition through payment. Source-to-pay adds the upstream work of supplier discovery, onboarding, sourcing events and award.
What systems support source-to-pay?
Organizations use a single suite, a set of specialized tools, or ERP modules. What matters is that sourcing, purchasing, matching and payment share the same supplier and transaction data.
Where does contract management sit in the process?
Contracts usually follow the award decision and set the terms that later purchase orders inherit. Renewal and performance review continue across the life of the relationship.
How do you measure a source-to-pay process?
Track cycle time between stages, approval compliance, invoice match exceptions, contract utilization, savings from sourcing events and supplier performance. Agree on definitions first so numbers are comparable over time.
Can small teams use source-to-pay?
Yes. The stages exist in every purchase, however small. A smaller team can adopt the stages that matter most first, such as sourcing and approvals, and add the rest over time.
Keep reading
- Source-to-Pay Applications: Modules and Buying GuideWhat source-to-pay applications include, how a suite differs from point tools and ERP modules, and the questions and scorecard to use before you buy.
- What is Source-to-Pay?A plain-language breakdown of the Source-to-Pay (S2P) process — every stage from sourcing a supplier to paying them, and why organizations treat it as one connected system.
- Source-to-Pay vs. Procure-to-Pay: what's the difference?Source-to-Pay and Procure-to-Pay are often used interchangeably, but they describe different scopes of the procurement process. Here's the exact boundary between them.
Have a specific procurement problem in mind?
Book a short call and we'll talk through it directly.
